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 entities, specifically here focusing on the Purchase Request resource with the Get All (OData) operation. It retrieves multiple purchase request records from SAP using OData query options, allowing users to specify which fields to return and filter the results based on conditions.

Typical use cases include:

  • Fetching a list of purchase requests for reporting or analysis.
  • Retrieving only specific fields (e.g., document number, vendor code, total amount) to optimize data transfer.
  • Filtering purchase requests by criteria such as total amount greater than a threshold or specific vendor codes.

For example, a user might want to get all purchase requests where the total exceeds 1000 and the vendor code equals "V1000", returning only the document entry, card code, and total fields.

Properties

Name Meaning
Select Comma-separated list of fields to return in the response (used as OData $select query). Example: DocEntry,CardCode,DocTotal
Filter OData filter expression to restrict returned purchase requests. Example: DocTotal gt 1000 and CardCode eq 'V1000'

Output

The node outputs an array of JSON objects representing purchase requests retrieved from SAP Service Layer. Each object contains the fields requested via the Select property or all fields if none specified.

Output structure example (fields depend on Select):

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

No binary data is output by this node.

Dependencies

  • Requires connection credentials to SAP Service Layer API, including base URL, username, password, and company database name.
  • The node authenticates by sending a login POST request to SAP Service Layer /Login endpoint and manages session cookies.
  • Uses HTTP requests to interact with SAP Service Layer REST endpoints.
  • No additional external dependencies beyond the SAP Service Layer API and valid credentials.

Troubleshooting

  • Authentication errors: If login fails, verify the SAP Service Layer credentials (username, password, company DB) are correct and that the SAP server is reachable.
  • Invalid OData queries: Malformed $select or $filter expressions may cause errors. Ensure proper syntax according to OData standards.
  • Network issues: Connection timeouts or SSL errors can occur if the SAP server is down or network settings block access. Check connectivity and SSL configurations.
  • Empty results: If no purchase requests match the filter, the output will be an empty array. Confirm filter criteria are correct.
  • Error messages: The node returns error details in the output JSON under an error field if the request fails. Review these messages for clues.

Links and References

Discussion