PlantScanner - SAP Service Layer icon

PlantScanner - SAP Service Layer

Interact with SAP Service Layer API
Join our community

Actions26

Overview

This node integrates with the SAP Service Layer API to perform various operations on SAP resources. Specifically, for the Inventory Gen Exit resource with the Get All operation, it retrieves multiple inventory generation exit records from SAP, supporting filtering, pagination (skip), field selection, and expansion of related entities.

This node is beneficial in scenarios where you need to automate or synchronize inventory exit data from SAP into other systems or workflows. For example, a warehouse management system could use this node to fetch all recent inventory exits filtered by warehouse code or date, enabling real-time stock updates or audit reporting.

Properties

Name Meaning
Filters OData filter string to narrow down results, e.g., WarehouseCode eq 'WH001' or CreationDate ge '2024-03-20'. Optional.
Skip Number of records to skip for pagination purposes. Optional; defaults to 0.
Select Comma-separated list of fields to include in the response. Leave empty to get all fields. Example: ItemCode, ItemName, PurchaseItem, SalesItem. Optional.
Expand Comma-separated list of related entities to expand in the response. Example: DocumentLines, Attachments2. Optional.

Output

The output is an array of JSON objects representing the inventory generation exit records retrieved from SAP. Each object contains the fields returned by the SAP Service Layer according to the selected properties (Select and Expand). If no fields are specified, all available fields are included.

No binary data output is produced by this operation.

Example output structure (simplified):

[
  {
    "DocEntry": 123,
    "DocDate": "2024-06-15",
    "WarehouseCode": "WH001",
    "JournalMemo": "Exit for production",
    "DocumentLines": [
      {
        "ItemCode": "ITEM001",
        "Quantity": 10
      }
    ]
  },
  ...
]

Dependencies

  • Requires connection credentials to the SAP Service Layer API, including:
    • Base URL of the SAP Service Layer.
    • Company database name.
    • Username and password for authentication.
    • Optional language setting.
  • The node uses HTTPS requests with disabled SSL certificate verification (rejectUnauthorized: false).
  • No additional external dependencies beyond standard HTTP client libraries.

Troubleshooting

  • Failed to get session cookie: Indicates login to SAP Service Layer failed. Check credentials and network connectivity.
  • Operation not supported: Occurs if an unsupported operation or resource is selected. Verify correct Resource and Operation parameters.
  • OData filter syntax errors: Invalid filter strings may cause API errors. Ensure filters follow OData syntax rules.
  • Empty or incomplete results: May be due to incorrect filters, skip values, or insufficient permissions.
  • SSL issues: Since SSL verification is disabled, ensure your environment trusts the SAP server or adjust settings accordingly.
  • To handle errors gracefully, enable "Continue On Fail" in the node settings to receive error details in output instead of stopping execution.

Links and References

Discussion