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 various purchase-related documents, specifically here focusing on Purchase Credit Notes. The "Get by Key" operation retrieves a single Purchase Credit Note identified by its unique DocEntry key.

Typical use cases include:

  • Fetching detailed information about a specific Purchase Credit Note for review or processing.
  • Automating workflows that require validation or extraction of data from a particular credit note.
  • Integrating SAP purchase credit note data into other systems or reports.

For example, you might use this node to get the details of a Purchase Credit Note with DocEntry 12345 to verify its status before proceeding with payment or reconciliation.

Properties

Name Meaning
DocEntry The unique numeric identifier (DocEntry) of the Purchase Credit Note to retrieve.

Output

The node outputs a JSON object representing the Purchase Credit Note retrieved from the SAP Service Layer API. This JSON contains all the fields and nested data as provided by SAP for that document, such as vendor info, amounts, dates, line items, and status.

If an error occurs (e.g., invalid DocEntry or connectivity issues), the output JSON will contain an error field with the error message.

The node does not output binary data.

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 name.
  • 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

  • Common Issues:

    • Invalid or missing DocEntry: The node requires a valid numeric DocEntry to fetch the correct Purchase Credit Note.
    • Authentication failures: Incorrect username, password, or company DB will prevent login and cause errors.
    • Network or SSL issues: The node disables strict SSL verification (rejectUnauthorized: false), but network problems can still cause failures.
    • API endpoint changes or SAP Service Layer unavailability.

  • Error Messages:

    • Errors returned from the SAP API are captured and returned in the output JSON under the error key.
    • Typical messages include "Not Found" if the DocEntry does not exist, or authentication errors if login fails.

  • Resolution Tips:

    • Verify credentials and company DB settings.
    • Confirm the DocEntry exists in SAP.
    • Check network connectivity to the SAP Service Layer endpoint.
    • Review SAP Service Layer logs for more details if accessible.

Links and References

Discussion