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, for the "Purchase Request" resource and the "Create" operation, it allows users to create new purchase requests in SAP by sending a JSON payload representing the purchase request details.
Common scenarios where this node is beneficial include automating procurement workflows, integrating external systems with SAP purchasing modules, or programmatically creating purchase requests based on business logic or incoming data streams.
For example, a company could use this node to automatically generate purchase requests when inventory levels fall below a threshold, or to create purchase requests from an external vendor management system.
Properties
| Name | Meaning |
|---|---|
| JSON Body | The JSON content sent as the body of the HTTP POST request to create the purchase request. This should contain all necessary fields according to SAP's Purchase Request API schema. |
Output
The node outputs an array of JSON objects corresponding to each input item processed. Each output item contains:
json: The JSON response returned by the SAP Service Layer after creating the purchase request. This typically includes details of the newly created purchase request such as its unique identifier and status.pairedItem: Metadata linking the output to the original input item index.
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 identifier.
- The node performs a login request to obtain session cookies used for subsequent API calls.
- The node uses HTTP methods (POST) to interact with the SAP Service Layer REST endpoints.
- No additional external dependencies beyond the configured SAP Service Layer API credentials.
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 accessible.
- Invalid JSON Body: Ensure the JSON body matches the expected schema for a purchase request in SAP. Malformed or incomplete JSON will cause API errors.
- API endpoint errors: Errors returned from SAP may indicate issues such as missing required fields, invalid values, or permission problems.
- Network issues: Connection timeouts or SSL errors can occur if the SAP Service Layer endpoint is unreachable or has certificate issues.
- To resolve errors, check the error message returned in the output JSON under the
errorfield for guidance.
Links and References
- SAP Business One Service Layer Documentation
- SAP Service Layer API Reference
- OData Protocol (used by SAP Service Layer)
If you need details about other operations or resources, feel free to ask!