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 interacts with the SAP Service Layer to manage purchase-related documents in the "Purchases" domain. Specifically, for the Purchase Down Payment resource with the Get All (OData) operation, it retrieves multiple purchase down payment records from SAP using OData query options.

The node supports advanced querying capabilities via OData parameters such as $select and $filter, allowing users to specify which fields to return and filter the results based on conditions.

Common scenarios:

  • Fetching a list of purchase down payments with specific fields to reduce payload size.
  • Filtering purchase down payments by criteria like total amount or vendor code.
  • Integrating SAP purchase down payment data into workflows for reporting, auditing, or further processing.

Example use case:

  • Retrieve all purchase down payments where the document total is greater than 1000 and the vendor code equals 'V1000', returning only the document entry number, card code, and total amount.

Properties

Name Meaning
Select Comma-separated list of fields to return for each purchase down payment (used as $select). Example: DocEntry,CardCode,DocTotal
Filter OData filter expression to restrict returned purchase down payments. Example: DocTotal gt 1000 and CardCode eq 'V1000'

Output

The output is an array of JSON objects representing purchase down payment records retrieved from SAP Service Layer.

  • Each item in the output corresponds to one purchase down payment record.
  • The fields included depend on the $select parameter; if omitted, all fields are returned.
  • The structure matches the SAP Service Layer's PurchaseDownPayments entity schema.
  • No binary data is output by this operation.

Example output snippet (simplified):

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

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 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.
  • Empty results: If no records match the filter, the output will be empty. Check filter criteria correctness.
  • Error responses: Errors from SAP Service Layer are returned in the output JSON under an error field with the message.

Links and References

Discussion