SAP Service Layer (Purchases) icon

SAP Service Layer (Purchases)

Todas las entidades de Purchases de SAP Service Layer
Join our community

Actions88

Overview

This node integrates with the SAP Service Layer to interact with various purchase-related entities, specifically here focusing on the Purchase Return resource. The "Get All (OData)" operation allows users to retrieve multiple purchase return records using OData query options such as $select and $filter. This enables precise querying and filtering of purchase return data from an SAP Business One system.

Typical use cases include:

  • Fetching all purchase returns with specific fields for reporting or analysis.
  • Filtering purchase returns based on criteria like total amount or vendor code.
  • Integrating SAP purchase return data into workflows for auditing, reconciliation, or further processing.

For example, a user might retrieve all purchase returns where the document total exceeds 1000 and the vendor code equals 'V1000', selecting only key fields like DocEntry, CardCode, and DocTotal.

Properties

Name Meaning
Select Comma-separated list of fields to return in the response (used as OData $select).
Filter OData filter expression to restrict which purchase returns are returned (used as $filter).

Example values for Select: DocEntry,CardCode,DocTotal

Example value for Filter: DocTotal gt 1000 and CardCode eq 'V1000'

Output

The node outputs an array of JSON objects representing purchase return records retrieved from SAP. Each object contains the fields requested via the $select parameter or all fields if none specified.

Output structure example (simplified):

[
  {
    "DocEntry": 123,
    "CardCode": "V1000",
    "DocTotal": 1500.00,
    ...
  },
  ...
]

If an error occurs during the request, the output will contain an object with an error field describing the issue.

The node does not output binary data.

Dependencies

  • Requires connection to an SAP Service Layer instance.
  • Needs credentials including base URL, username, password, and company database name.
  • The node authenticates by sending a login POST request to /Login endpoint and uses session cookies for subsequent requests.
  • No additional external dependencies beyond the SAP Service Layer API.

Troubleshooting

  • Authentication errors: If login fails, verify the SAP Service Layer URL, username, password, and company database are correct.
  • Invalid OData queries: Malformed $select or $filter expressions may cause errors. Ensure proper syntax according to OData standards.
  • Network issues: Connection failures can occur if the SAP Service Layer is unreachable or SSL certificates are invalid. The node disables strict SSL verification (rejectUnauthorized: false), but network connectivity must be ensured.
  • Permission issues: The SAP user must have sufficient permissions to read Purchase Returns.
  • Error messages: Returned errors from SAP are included in the output under the error key. Review these messages for clues on misconfiguration or invalid parameters.

Links and References

Discussion