SAP Service Layer (Purchases)Install

Overview

This node integrates with the SAP Service Layer to manage various purchase-related entities, including Purchase Orders. Specifically, for the Purchase Order - Delete operation, it allows users to delete a purchase order identified by its unique document entry number (DocEntry). This is useful in scenarios where a purchase order needs to be removed from the SAP system due to cancellation, error correction, or cleanup.

Practical examples include:

• Automatically deleting obsolete or erroneous purchase orders as part of an automated workflow.
• Integrating with other systems to synchronize and clean up purchase orders in SAP.
• Managing purchase order lifecycle by programmatically removing unwanted entries.

Properties

Output

The node outputs a JSON object representing the response from the SAP Service Layer API after attempting to delete the specified purchase order. Typically, this will confirm successful deletion or provide error details if the operation failed.

If an error occurs during the request, the output JSON will contain an error field with the error message.

No binary data output is produced by this operation.

Example output on success (simplified):

{
  "json": {
    // Response confirming deletion, often empty or status info
  },
  "pairedItem": {
    "item": 0
  }
}

Example output on error:

{
  "json": {
    "error": "Error message describing what went wrong"
  },
  "pairedItem": {
    "item": 0
  }
}

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 name.
• The node performs a login request to obtain session cookies used for 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 database are correct and that the SAP Service Layer is accessible.
• Invalid DocEntry: Ensure the DocEntry number corresponds to an existing purchase order; otherwise, the API may return a not found or similar error.
• Permission issues: The user account must have sufficient permissions to delete purchase orders.
• Network or SSL issues: The node disables strict SSL verification (rejectUnauthorized: false), but network connectivity and firewall settings should allow access to the SAP Service Layer endpoint.
• Error messages: Errors returned from the SAP API are passed through in the output's error field. Review these messages for specific causes.

Links and References

• SAP Business One Service Layer Documentation
• SAP Service Layer API Reference (search for PurchaseOrders entity)
• OData Protocol Overview

This summary focuses solely on the Purchase Order resource and the Delete operation as requested.