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 the Purchase Tax Invoice resource. The "Get All (OData)" operation allows users to retrieve multiple purchase tax invoices using OData query options such as $select and $filter. This enables fine-grained control over which fields are returned and which records are filtered based on conditions.

Typical use cases include:

  • Fetching a list of purchase tax invoices with only specific fields for reporting or further processing.
  • Filtering invoices by criteria like total amount or vendor code to analyze or automate workflows.
  • Integrating SAP purchase tax invoice data into other systems or dashboards via n8n workflows.

Example: Retrieve all purchase tax invoices where the document total is greater than 1000 and only return the DocEntry, CardCode, and DocTotal fields.

Properties

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

Output

The node outputs an array of JSON objects representing purchase tax invoices matching the query. 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,
    ...
  },
  {
    "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 endpoint.
    • 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 that the base URL, username, password, and company DB are correct and that the SAP Service Layer is accessible.
  • Invalid OData queries: Malformed $select or $filter expressions may cause API errors. Ensure proper syntax according to OData standards.
  • Empty results: If no invoices are returned, check the filter criteria or try removing filters to confirm data availability.
  • Network issues: Connection timeouts or SSL errors can 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.
  • API limits or permissions: Insufficient user permissions or API rate limits on the SAP side may cause errors.

Links and References

Discussion