Actions88
- Purchase Credit Note Actions
- Purchase Invoice Actions
- Purchase Delivery Note Actions
- Purchase Down Payment Actions
- Purchase Order Actions
- Purchase Quotation Actions
- Purchase Request Actions
- Purchase Return Actions
- Purchase Tax Invoice Actions
Overview
This node integrates with the SAP Service Layer to manage purchase-related documents in SAP Business One. Specifically, for the Purchase Credit Note resource and the Delete operation, it allows users to delete a purchase credit note identified by its unique document entry number (DocEntry). This is useful in scenarios where a purchase credit note was created erroneously or needs to be removed from the system.
Practical examples include:
- Automatically cleaning up test or draft purchase credit notes.
- Removing duplicate or incorrect purchase credit notes as part of an automated workflow.
- Integrating with other systems to synchronize deletions of purchase credit notes.
Properties
| Name | Meaning |
|---|---|
| DocEntry | The unique identifier (number) of the purchase credit note to delete. Required property. |
Output
The node outputs a JSON object representing the response from the SAP Service Layer API after attempting to delete the specified purchase credit note. Typically, this will contain confirmation of deletion or error details if the operation failed.
If the deletion is successful, the output JSON usually contains status information confirming the removal. If there is an error (e.g., the DocEntry does not exist), the output JSON will contain an error field with the error message.
No binary data output is produced by this operation.
Dependencies
- Requires connection to an SAP Service Layer instance.
- Needs credentials including base URL, username, password, and company database name to authenticate against SAP.
- The node performs a login request to obtain session cookies used for subsequent API calls.
- The SAP Service Layer API must support DELETE requests on the
/PurchaseCreditNotes({DocEntry})endpoint.
Troubleshooting
Common issues:
- Invalid or missing
DocEntry: The node requires a valid document entry number; otherwise, the API call will fail. - Authentication failures: Incorrect credentials or connectivity issues to the SAP Service Layer will prevent login and subsequent operations.
- Permission errors: The user associated with the credentials may lack rights to delete purchase credit notes.
- Network or SSL issues: The node disables strict SSL verification (
rejectUnauthorized: false), but network problems can still cause failures.
- Invalid or missing
Error messages:
- Errors returned from the SAP API are captured and returned in the output JSON under the
errorkey. - Common error messages might include "Document not found", "Access denied", or "Invalid session".
- Errors returned from the SAP API are captured and returned in the output JSON under the
Resolutions:
- Verify that the
DocEntrycorresponds to an existing purchase credit note. - Check and update SAP credentials and ensure the user has appropriate permissions.
- Confirm network connectivity and SAP Service Layer availability.
- Review SAP logs for more detailed error diagnostics if needed.
- Verify that the
Links and References
- SAP Business One Service Layer Documentation
- SAP Service Layer API Reference
- OData Protocol Overview (for
$selectand$filterusage in other operations)
Note: This summary focuses exclusively on the Purchase Credit Note resource and the Delete operation as requested.