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 entities, specifically here focusing on Purchase Invoices. The "Get by Key (Select)" operation retrieves a single Purchase Invoice identified by its unique DocEntry key and allows selecting specific fields to return via an OData $select query option.
Typical use cases include:
- Fetching detailed information about a specific purchase invoice for review or processing.
- Retrieving only certain fields of a purchase invoice to optimize data transfer and processing.
- Integrating SAP purchase invoice data into workflows for reporting, auditing, or triggering downstream actions.
For example, you might use this node to get the total amount and vendor code of a particular purchase invoice by specifying those fields in the "Select" property.
Properties
| Name | Meaning |
|---|---|
| DocEntry | The unique identifier (number) of the Purchase Invoice to retrieve. Required. |
| Select | Comma-separated list of fields to return from the Purchase Invoice (used as OData $select). Examples: DocEntry,CardCode,DocTotal. Optional. |
Output
The node outputs JSON data representing the requested Purchase Invoice record. The structure corresponds to the SAP Service Layer's Purchase Invoice entity, containing all or selected fields depending on the "Select" input.
Output example snippet (fields depend on selection):
{
"DocEntry": 123,
"CardCode": "V1000",
"DocTotal": 1500.00,
...
}
If the node encounters an error during the request, it outputs a JSON object with an error field describing the issue.
No binary data output is produced by this operation.
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, verify that the base URL, username, password, and company database are correct and that the SAP Service Layer is accessible.
- Invalid DocEntry: If the specified
DocEntrydoes not exist, the API will return an error; ensure the key is valid. - Malformed Select string: The "Select" property must be a comma-separated list of valid field names; invalid fields may cause errors or empty results.
- Network issues: Connection timeouts or SSL errors can occur if the SAP Service Layer endpoint is unreachable or has certificate issues. The node disables strict SSL verification (
rejectUnauthorized: false) but network connectivity must be ensured. - Error messages: Returned errors are included in the output JSON under the
errorkey. Review these messages to identify issues such as permission problems or malformed requests.
Links and References
- SAP Business One Service Layer Documentation
- OData Query Options
- n8n HTTP Request Node Documentation (for understanding underlying request mechanics)