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 various purchase-related entities, including Purchase Requests. Specifically, the "Get by Key" operation for the Purchase Request resource retrieves a single purchase request document identified by its unique key (DocEntry). This is useful when you need to fetch detailed information about a specific purchase request from SAP Business One.

Common scenarios:

  • Fetching details of a particular purchase request to review or process it further.
  • Integrating SAP purchase requests data into other systems or workflows.
  • Automating reporting or validation tasks based on individual purchase requests.

Practical example:
You want to retrieve the purchase request with DocEntry 12345 to check its status and items before approving it in your workflow automation.


Properties

Name Meaning
DocEntry The unique identifier (number) of the purchase request document to retrieve. Required.

Output

The node outputs the JSON representation of the requested purchase request as returned by the SAP Service Layer API. The output structure corresponds directly to the SAP entity's fields, including all standard and custom properties of the purchase request.

  • The output is an object containing all details of the purchase request identified by the given DocEntry.
  • If an error occurs (e.g., invalid key or connectivity issues), the output will contain an error field with the error message.
  • No binary data output is produced by this operation.

Example output snippet (simplified):

{
  "DocEntry": 12345,
  "DocDate": "2024-06-01",
  "CardCode": "V1000",
  "DocTotal": 1500.00,
  "DocumentStatus": "Open",
  ...
}

Dependencies

  • Requires connection to an SAP Business One Service Layer endpoint.
  • Needs credentials including base URL, username, password, and company database name.
  • The node performs a login request to obtain session cookies used for subsequent API calls.
  • The SAP Service Layer API must be accessible from the n8n environment.

Troubleshooting

  • Authentication errors: If login fails, verify the SAP Service Layer URL, username, password, and company database are correct and that the SAP server is reachable.
  • Invalid DocEntry: If the specified DocEntry does not exist, the API will return an error; ensure the key is valid and exists in SAP.
  • Network issues: Connection timeouts or SSL errors may occur if the SAP server is down or network/firewall settings block access.
  • Permission issues: The user account must have sufficient permissions to read purchase requests.
  • Error messages: Errors are returned in the output JSON under the error property. Review these messages to identify issues such as invalid parameters or API limitations.

Links and References


If you need details on other operations or resources, feel free to ask!

Discussion