PlantScanner - SAP Service Layer icon

PlantScanner - SAP Service Layer

Interact with SAP Service Layer API

Actions26

Overview

This node integrates with the SAP Service Layer API to manage and retrieve data related to various SAP resources. Specifically, for the Production Order - Get operation, it fetches a single production order record by its unique ID from the SAP system.

Typical use cases include:

  • Retrieving detailed information about a specific production order in manufacturing or supply chain workflows.
  • Integrating SAP production order data into automation workflows for reporting, monitoring, or triggering downstream processes.
  • Fetching selective fields or expanding related entities of a production order to optimize data usage.

Example: A user wants to get the details of a production order with ID "12345" including its document lines and attachments to verify order status before proceeding with shipment.

Properties

Name Meaning
ID The unique identifier of the production order record to retrieve. (Required)
Select Comma-separated list of specific fields to return in the response. Leave empty to get all fields. Example: DocNum, Status, PlannedQuantity
Expand Comma-separated list of related entities to expand in the response. For example: DocumentLines, Attachments2

Output

The output is a JSON object representing the requested production order record as returned by the SAP Service Layer API. It includes all fields by default or only the selected fields if specified. Expanded related entities are included as nested objects or arrays.

Example output structure (simplified):

{
  "DocEntry": 12345,
  "DocNum": "PO-2024-001",
  "Status": "Planned",
  "PlannedQuantity": 100,
  "DocumentLines": [
    {
      "LineNum": 1,
      "ItemCode": "ITEM001",
      "Quantity": 50
    }
  ],
  "Attachments2": [
    {
      "AbsEntry": 10,
      "FileName": "specs.pdf"
    }
  ]
}

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to an SAP Service Layer API endpoint.
  • Needs credentials including URL, company database name, username, password, and optionally language.
  • Uses HTTPS requests with session cookie authentication obtained via login.
  • The node disables SSL certificate verification (rejectUnauthorized: false) which may be relevant for self-signed certificates.

Troubleshooting

  • Failed to get session cookie: Indicates login to SAP Service Layer failed. Check credentials and network connectivity.
  • Operation not supported: If an unsupported operation or resource is selected, the node throws an error.
  • Invalid ID or record not found: If the provided ID does not exist, the API may return an error or empty result.
  • Malformed select or expand parameters: Incorrectly formatted field lists can cause API errors.
  • SSL issues: Since SSL verification is disabled, ensure your environment trusts the SAP server or adjust settings accordingly.
  • Continue on Fail: If enabled, errors per item will be captured in the output JSON under an error key instead of stopping execution.

Links and References

Discussion