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 manage purchase-related documents, specifically here focusing on "Purchase Credit Note" entities. The "Get All (OData)" operation allows users to retrieve multiple purchase credit notes using OData query options such as $select and $filter. This enables fetching only specific fields or filtering records based on conditions.

Typical use cases include:

  • Retrieving a list of purchase credit notes with selected fields for reporting or auditing.
  • Filtering purchase credit notes by criteria like total amount or vendor code.
  • Integrating SAP purchase credit note data into workflows for further processing or notifications.

For example, you could fetch all purchase credit notes where the total exceeds 1000 and only return the document entry number, card code, and total amount.

Properties

Name Meaning
Select Fields to return in the response, used as the OData $select parameter. Example: DocEntry,CardCode,DocTotal
Filter OData $filter expression to filter results. Example: DocTotal gt 1000 and CardCode eq 'V1000'

Output

The node outputs an array of JSON objects representing purchase credit notes matching the query. Each object contains the fields requested via the $select parameter or all fields if none specified.

The output structure is:

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

No binary data is produced by this operation.

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 DB are correct.
  • Invalid OData queries: Malformed $select or $filter strings can cause errors. Ensure proper syntax and encoding.
  • Network issues: Connection failures may occur if the SAP Service Layer is unreachable or SSL certificates are invalid (the node disables strict SSL verification).
  • Empty results: If no purchase credit notes match the filter, the output will be an empty array.
  • Error responses: The node returns error messages in the output JSON under an error field if the API call fails.

Links and References

Discussion