SAP Service Layer (Purchases) icon

SAP Service Layer (Purchases)

Todas las entidades de Purchases de SAP Service Layer

Overview

This node integrates with the SAP Service Layer to manage purchase-related entities, specifically here focusing on Purchase Orders. The "Update" operation allows users to modify an existing Purchase Order by specifying its unique identifier (DocEntry) and providing the updated data in JSON format.

Typical use cases include:

  • Automating updates to purchase orders based on external triggers or workflows.
  • Synchronizing purchase order data between SAP and other systems.
  • Adjusting purchase order details such as quantities, prices, or delivery dates programmatically.

For example, a user might update the delivery date of a purchase order after receiving new information from a supplier, or adjust item quantities before final approval.

Properties

Name Meaning
DocEntry The unique numeric identifier of the Purchase Order to update.
JSON Body A JSON object containing the fields and values to update in the Purchase Order record.

Output

The node outputs an array of JSON objects corresponding to each input item processed. Each output JSON contains the response from the SAP Service Layer API for the update request. This typically includes the updated Purchase Order data or confirmation of the update.

If an error occurs during the update, the output JSON will contain an error field with the error message.

No binary data is produced by this node.

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

  • Authentication errors: If login fails, verify that the base URL, username, password, and company database are correct and that the SAP Service Layer is reachable.

  • Invalid DocEntry: Ensure the DocEntry number corresponds to an existing Purchase Order; otherwise, the update will fail.

  • Malformed JSON Body: The JSON provided must conform to the expected schema for Purchase Orders in SAP. Invalid fields or types may cause errors.

  • Network issues: Connection timeouts or SSL errors can occur if the SAP Service Layer endpoint is unreachable or has invalid certificates. The node disables strict SSL verification (rejectUnauthorized: false), but network connectivity must still be ensured.

  • Error messages: The node returns error messages from the SAP API directly in the output under the error key. Review these messages to identify issues such as permission problems or invalid data.

Links and References

Discussion