SAP B1 Service Layer 6 - Gestion Bancos icon

SAP B1 Service Layer 6 - Gestion Bancos

Interact with SAP B1 Service Layer 6 - Gestion Bancos

Actions19

Overview

This node integrates with the SAP Business One Service Layer (version 6) specifically for managing banking-related entities. The "Incoming Payment" resource's "Update" operation allows users to modify existing incoming payment records in SAP B1.

Typical use cases include:

  • Updating details of an incoming payment after it has been initially created, such as correcting amounts, dates, or linked documents.
  • Automating updates to incoming payments based on external triggers or workflows.
  • Synchronizing payment information from other systems into SAP B1.

For example, a finance team could use this node to update the status or details of a customer payment received, ensuring SAP B1 reflects the latest information without manual entry.

Properties

Name Meaning
DocEntry Identifier of the document (incoming payment) to update. This is required.
JSON Body JSON content to send as the request body containing the fields and values to update.

Output

The node outputs an array of JSON objects corresponding to each input item processed. Each output item contains:

  • json: The response from the SAP B1 Service Layer API after attempting the update operation. This typically includes the updated incoming payment data or error details if the update failed.
  • pairedItem: Metadata linking the output to the input item index.

No binary data is produced by this node.

Dependencies

  • Requires connection credentials to the SAP Business One Service Layer API, including:
    • Base URL of the SAP B1 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 node uses HTTP methods PATCH for update operations.
  • The environment must allow HTTPS requests to the SAP B1 Service Layer endpoint.

Troubleshooting

  • Authentication errors: If login fails, verify that the base URL, username, password, and company database are correct and that the SAP B1 Service Layer is accessible.
  • Invalid DocEntry: Providing a non-existent or incorrect DocEntry will cause the update to fail. Ensure the DocEntry corresponds to an existing incoming payment.
  • Malformed JSON Body: The JSON body must be valid and conform to SAP B1's expected schema for incoming payments. Invalid fields or types may cause errors.
  • Network issues: Connection timeouts or SSL errors can occur if the SAP B1 server is unreachable or has invalid certificates. The node disables strict SSL verification (rejectUnauthorized: false), but network connectivity must still be ensured.
  • API errors: The node returns error messages from the SAP B1 API in the output JSON under the error key. Review these messages to adjust the request accordingly.

Links and References

Discussion