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 various purchase-related entities, including Purchase Requests. Specifically, the "Close" operation for Purchase Requests allows users to mark a purchase request as closed via the SAP Service Layer API.
Typical use cases include automating the lifecycle management of purchase requests within SAP Business One environments. For example, after all necessary approvals and processing steps are completed, a purchase request can be programmatically closed to prevent further modifications or processing.
Practical examples:
- Automatically closing purchase requests once related purchase orders are created.
- Closing purchase requests in bulk based on certain criteria or workflow triggers.
- Integrating SAP purchase request status updates into broader ERP automation workflows.
Properties
| Name | Meaning |
|---|---|
| DocEntry | The unique identifier (number) of the Purchase Request document to close. This is required. |
Output
The node outputs the JSON response returned by the SAP Service Layer API after attempting to close the specified Purchase Request. The output structure corresponds directly to the API's response and typically includes details about the updated Purchase Request or confirmation of the close action.
If an error occurs during the API call, the output will contain an error field with the error message describing what went wrong.
No binary data output is produced by this node.
Dependencies
- Requires connection credentials to the SAP Service Layer API, including:
- Base URL of the SAP Service Layer endpoint.
- Username and password for authentication.
- Company database name.
- The node performs a login POST request to obtain session cookies used for subsequent API calls.
- The SAP Service Layer must be accessible from the n8n environment where this node runs.
Troubleshooting
- Authentication errors: If login fails, verify that the base URL, username, password, and company database are correct and that the SAP Service Layer is reachable.
- Invalid DocEntry: Providing a non-existent or incorrect DocEntry number will result in an error from the SAP API indicating the document was not found.
- Permission issues: Ensure the user account has sufficient permissions to perform the Close operation on Purchase Requests.
- Network issues: Connection timeouts or SSL errors may occur if the SAP Service Layer endpoint is unreachable or uses self-signed certificates. The node disables strict SSL verification (
rejectUnauthorized: false) but network connectivity must still be ensured. - API errors: Any other errors returned by the SAP Service Layer will be included in the output's
errorfield. Review these messages for troubleshooting.
Links and References
- SAP Business One Service Layer Documentation
- SAP Service Layer API Reference (search for Purchase Requests endpoints)
- OData Query Options (used for
$selectand$filterparameters)
Note: The node dynamically constructs the API endpoint URL and HTTP method based on the selected resource and operation. For the "Close" operation on Purchase Requests, it sends a POST request to /PurchaseRequests({DocEntry})/Close with appropriate session cookies for authentication.