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 Requests and other related purchase entities. Specifically, for the Purchase Request resource and the Get by Key (Select) operation, it retrieves a single purchase request identified by its unique key (DocEntry) and allows selecting specific fields to return.
Common scenarios where this node is beneficial include:
- Fetching detailed information about a particular purchase request by its identifier.
- Retrieving only relevant fields from a purchase request to optimize data transfer and processing.
- Integrating SAP purchase request data into workflows for reporting, auditing, or further automation.
Practical example:
A user wants to get the total amount and vendor code of a specific purchase request with DocEntry 1234. They can use this node to query that purchase request and specify the fields DocTotal,CardCode in the select property, receiving only those fields in the output.
Properties
| Name | Meaning |
|---|---|
| DocEntry | The unique identifier (number) of the purchase request to retrieve. Required. |
| Select | Comma-separated list of fields to return from the purchase request (used as OData $select). Examples: DocEntry,CardCode,DocTotal. Optional; if empty, all fields are returned. |
Output
The node outputs an array of JSON objects, each representing the retrieved purchase request data. The structure corresponds to the fields requested via the Select property or all fields if none specified.
Example output JSON snippet when selecting DocEntry and CardCode:
{
"DocEntry": 1234,
"CardCode": "V1000"
}
If the node encounters an error during the request, the output JSON will contain an error field with the error message.
The node does not output binary data.
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 requests.
- No additional external dependencies beyond the SAP Service Layer API and valid credentials.
Troubleshooting
Authentication errors:
If login fails due to invalid credentials or incorrect company database, the node will return an error message indicating authentication failure. Verify credentials and company DB settings.Invalid DocEntry:
If the specifiedDocEntrydoes not exist, the SAP Service Layer will return an error which the node passes through. Confirm theDocEntryvalue is correct.Malformed Select string:
If theSelectproperty contains invalid field names or syntax, the API may reject the request. Ensure field names are valid SAP entity properties and comma-separated without extra spaces.Network or SSL issues:
The node disables SSL certificate verification (rejectUnauthorized: false). If connection issues persist, verify network connectivity and SAP Service Layer availability.General API errors:
Any other errors returned by the SAP Service Layer will be included in the output'serrorfield. Review the error message for details.
Links and References
- SAP Business One Service Layer Documentation
- OData Query Options
- n8n HTTP Request Node Documentation (for understanding underlying request mechanics)