Actions26
- Item Actions
- Production Order Actions
- Warehouse Actions
- Product Tree Actions
- Inventory Gen Entry Actions
- Inventory Gen Exit Actions
- SQL Query Actions
- Custom API Call Actions
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 Verify Exists operation, it checks whether an inventory exit record exists based on a given journal memo. This is useful in scenarios where you want to confirm if a particular inventory exit transaction has already been recorded in SAP before proceeding with further processing or avoiding duplicates.
Practical examples:
- Before creating a new inventory exit document, verify if one with the same journal memo already exists.
- Automate validation workflows that depend on the existence of specific inventory exit records.
Properties
| Name | Meaning |
|---|---|
| Journal Memo | The journal memo string used to check if an inventory gen exit record exists in SAP. |
Output
The output JSON contains two fields:
exists(boolean): Indicates whether any inventory gen exit records matching the journal memo were found (trueif at least one exists, otherwisefalse).count(number): The number of matching records found.
Example output JSON:
{
"exists": true,
"count": 1
}
No binary data is produced by this operation.
Dependencies
- Requires connection credentials to the SAP Service Layer API, including URL, company database name, username, password, and optionally language.
- Uses HTTPS requests with session cookie authentication obtained via a login call.
- The node depends on the SAP Service Layer being accessible and properly configured to accept API calls.
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 will throw an error.
- Empty or invalid journal memo: Ensure the journal memo parameter is provided and correctly formatted.
- Network or API errors: May occur due to SAP server issues or incorrect endpoint URLs; verify SAP Service Layer availability.
- To handle errors gracefully, enable "Continue On Fail" to receive error details in the output instead of stopping execution.
Links and References
- SAP Service Layer API Documentation
- OData Query Options (used for filtering)