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 Down Payments. Specifically, the "Get by Key" operation for the "Purchase Down Payment" resource retrieves a single purchase down payment document from SAP by its unique identifier (DocEntry). This is useful when you need to fetch detailed information about a specific purchase down payment for further processing, reporting, or validation within an automated workflow.
Common scenarios:
- Retrieving details of a particular purchase down payment to verify its status or amounts.
- Using the retrieved data to update other systems or trigger conditional logic based on the down payment's attributes.
- Auditing or logging specific purchase down payments in external databases or files.
Practical example:
You have an automation that processes vendor payments and needs to confirm the existence and details of a purchase down payment before proceeding. Using this node operation, you can fetch the down payment by its DocEntry and then decide whether to continue with payment processing.
Properties
| Name | Meaning |
|---|---|
| DocEntry | The unique numeric identifier of the Purchase Down Payment document to retrieve. |
Output
The output is a JSON object representing the full details of the requested Purchase Down Payment as returned by the SAP Service Layer API. It includes all standard fields and nested objects related to the down payment, such as amounts, dates, vendor information, and status.
If the operation encounters an error (e.g., invalid DocEntry), the output JSON will contain an error field with the error message.
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 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
Common issues:
- Invalid or missing
DocEntry: The node will return an error if the specified document key does not exist. - Authentication failures: Incorrect credentials or company DB name will cause login failure.
- Network connectivity problems to the SAP Service Layer endpoint.
- Insufficient permissions for the user account to access purchase down payment data.
- Invalid or missing
Error messages and resolutions:
"Unauthorized"or login errors: Verify credentials and company DB parameters."Not Found"or similar when fetching by key: Confirm theDocEntryvalue exists in SAP.- SSL or certificate errors: The node disables strict SSL verification (
rejectUnauthorized: false), but network policies might still block requests; check connectivity and firewall settings.
Links and References
- SAP Business One Service Layer Documentation
- OData Query Options (for
$select,$filterusage in other operations)
Note: This summary focuses exclusively on the "Purchase Down Payment" resource and the "Get by Key" operation as requested.