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 entities, specifically here focusing on Purchase Orders. The "Get All (OData)" operation retrieves multiple purchase orders using OData query parameters, allowing users to filter and select specific fields from the dataset.

Common scenarios where this node is beneficial include:

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

Practical example:

  • A user wants to get all purchase orders where the total amount exceeds 1000 and only needs the document entry number, vendor code, and total amount. They can use the $filter and $select properties to achieve this efficiently.

Properties

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

Output

The output is an array of JSON objects representing purchase orders retrieved from the SAP Service Layer. 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 output is produced by this operation.

Dependencies

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

Troubleshooting

  • Authentication errors: If login fails, verify the base URL, username, password, and company database values are correct and that the SAP Service Layer is accessible.
  • Invalid OData queries: Malformed $filter or $select expressions may cause errors. Ensure proper syntax according to OData standards.
  • Empty results: If no purchase orders are returned, check the filter criteria or try removing filters to confirm data availability.
  • Network issues: Connection timeouts or SSL errors may occur if the SAP Service Layer endpoint is unreachable or has invalid certificates. The node disables strict SSL verification (rejectUnauthorized: false) but network connectivity must be ensured.
  • Error messages: Errors are returned in the output JSON under an error field with the message string. Review these messages for clues on misconfiguration or API issues.

Links and References

Discussion