Actions19
- Bank Page Actions
- External Reconciliation Cancel Actions
- External Reconciliation Reconcile Actions
- Incoming Payment Actions
- Vendor Payment Actions
Overview
This node interacts with the SAP Business One Service Layer (version 6) specifically for managing banking-related entities, including Incoming Payments. The "Get by Key" operation under the Incoming Payment resource retrieves a specific incoming payment document from SAP B1 by its unique identifier (DocEntry). This is useful when you need to fetch detailed information about a particular payment, such as verifying payment status, auditing transactions, or integrating payment data into other workflows.
Practical examples:
- Automatically retrieving payment details after receiving a payment notification.
- Validating payment records before processing further accounting steps.
- Synchronizing payment data between SAP B1 and external systems.
Properties
| Name | Meaning |
|---|---|
| DocEntry | Identifier of the document (incoming payment) to retrieve. This is a required string. |
Output
The node outputs JSON data representing the full details of the requested incoming payment document as returned by the SAP B1 Service Layer API. The structure corresponds directly to the SAP B1 entity model for Incoming Payments, typically including fields like payment amount, customer info, payment date, and related documents.
No binary data output is produced by this operation.
Example output snippet (conceptual):
{
"DocEntry": 123,
"CardCode": "C0001",
"DocDate": "2024-01-01",
"DocTotal": 1000.00,
"PaymentMeans": [...],
...
}
Dependencies
- Requires an active SAP Business One Service Layer API endpoint (version 6).
- Needs credentials including base URL, username, password, and company database name.
- The node authenticates via a login POST request to obtain session cookies used in subsequent requests.
- No additional external dependencies beyond the SAP B1 Service Layer API.
Troubleshooting
- Authentication errors: If login fails, verify the SAP B1 credentials and that the Service Layer endpoint is reachable.
- Invalid DocEntry: If the specified
DocEntrydoes not exist, the API will return an error; ensure the ID is correct and exists in SAP B1. - Network issues: Connection timeouts or SSL errors may occur if the SAP B1 server is unreachable or has invalid certificates. The node disables strict SSL verification (
rejectUnauthorized: false) but network connectivity must be ensured. - Permission issues: The user account must have sufficient permissions to read incoming payment data.
Links and References
- SAP Business One Service Layer Documentation
- SAP B1 Incoming Payments Entity Reference (example link, check your version)
- n8n documentation on Creating Custom Nodes