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 Purchase Invoices. The "Get All (OData)" operation retrieves multiple purchase invoices using OData query options, allowing users to filter and select specific fields from the dataset.

Typical use cases include:

  • Fetching a list of purchase invoices that meet certain criteria (e.g., invoices above a certain total amount).
  • Retrieving only specific fields from purchase invoices to optimize data transfer and processing.
  • Integrating SAP purchase invoice data into workflows for reporting, auditing, or further automation.

For example, you could use this node to get all purchase invoices where the total is greater than 1000 and only retrieve the document entry number, card code, and total amount.

Properties

Name Meaning
Select Comma-separated list of fields to return from each purchase invoice (used as $select). Example: DocEntry,CardCode,DocTotal
Filter OData filter expression to limit which purchase invoices are returned. Example: DocTotal gt 1000 and CardCode eq 'V1000'

Output

The node outputs an array of JSON objects representing purchase invoices matching the query. Each object contains the fields requested via the Select property or all fields if none specified.

Example output structure (fields depend on Select):

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

No binary data is produced by this operation.

Dependencies

  • Requires connection credentials to the SAP Service Layer API, including:
    • Base URL of the SAP Service Layer instance.
    • Username and password for authentication.
    • Company database identifier.
  • The node performs a login request to obtain session cookies used in subsequent API calls.
  • No additional external dependencies beyond the SAP Service Layer API and valid credentials.

Troubleshooting

  • Authentication errors: If login fails, verify the base URL, username, password, and company database values. Ensure the SAP Service Layer is accessible and credentials are correct.
  • Invalid OData queries: Errors may occur if the Filter or Select expressions are malformed or reference invalid fields. Double-check syntax and field names against SAP documentation.
  • Network issues: Connection timeouts or SSL errors can happen if the SAP Service Layer endpoint is unreachable or uses self-signed certificates. The node disables strict SSL verification (rejectUnauthorized: false) but network connectivity must be ensured.
  • Empty results: If no purchase invoices match the filter, the output will be an empty array. Confirm filter criteria are correct and data exists.
  • API limits or permissions: Insufficient permissions or API rate limits on the SAP side may cause errors. Check user roles and API usage policies.

Links and References

Discussion