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 Orders. Specifically, the "Get by Key" operation for the Purchase Order resource retrieves detailed information about a single purchase order identified by its unique key (DocEntry). This is useful when you need to fetch exact data for a specific purchase order from SAP, such as for auditing, reporting, or further processing in an automation workflow.
Practical examples:
- Retrieve a purchase order by its document entry number to verify its status before proceeding with payment.
- Fetch detailed purchase order data to update another system or trigger notifications.
- Use the node in workflows that require conditional logic based on purchase order details.
Properties
| Name | Meaning |
|---|---|
| DocEntry | The unique identifier (document entry number) of the purchase order to retrieve. |
Output
The node outputs a JSON object representing the purchase order data retrieved from the SAP Service Layer. The structure corresponds directly to the SAP entity's fields and includes all available details for the specified purchase order.
- The output is under the
jsonproperty. - If an error occurs during retrieval, the output will contain an
errorfield with the error message. - No binary data is produced by this operation.
Dependencies
- Requires connection credentials to the SAP Service Layer API, including:
- Base URL of the SAP Service Layer instance.
- Username and password for authentication.
- Company database name.
- The node performs a login 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, check the correctness of the SAP credentials and network accessibility to the SAP Service Layer.
- Invalid DocEntry: Providing a non-existent or incorrect
DocEntrywill result in an error response from SAP. Verify the document entry number exists. - Network issues: Timeouts or connection errors may occur if the SAP Service Layer endpoint is unreachable.
- Permission issues: Ensure the SAP user has sufficient permissions to read purchase orders.
- Error messages: Errors are returned in the output JSON under the
errorkey. Review these messages to identify issues such as invalid parameters or server errors.
Links and References
- SAP Business One Service Layer Documentation
- OData Query Options (for
$select,$filterusage in other operations)