Actions45
- Inventory Gen Entrie Actions
- Inventory Gen Exit Actions
- Inventory Transfer Request Actions
- Product Tree Actions
- Production Order Actions
Overview
This node interacts with the SAP B1 Service Layer 8 specifically for production-related resources. The "Save Draft to Document" operation allows users to convert a draft production order into a finalized document within SAP Business One. This is useful in scenarios where production orders are initially saved as drafts for review or modification before being committed as official documents.
Practical examples include:
- Automating the transition of reviewed production drafts into active production orders.
- Integrating SAP B1 production workflows with other systems by programmatically saving drafts as documents.
- Streamlining production order management by reducing manual steps in SAP B1.
Properties
| Name | Meaning |
|---|---|
| DocEntry | The unique identifier (document entry number) of the production order draft to be saved as a document. This is required to specify which draft to convert. |
Output
The output is a JSON object representing the response from the SAP B1 Service Layer after attempting to save the draft to a document. It typically contains details about the newly created or updated production order document, including status and any relevant metadata returned by SAP.
If an error occurs, the output JSON will contain an error field with the error message describing what went wrong.
No binary data output is produced by this operation.
Dependencies
- Requires connection to an SAP B1 Service Layer 8 instance.
- Needs credentials including base URL, username, password, and company database name to authenticate via SAP's login endpoint.
- The node uses HTTP requests with session cookies obtained from the login response to perform operations.
- The environment must allow HTTPS requests with potentially self-signed certificates (
rejectUnauthorized: falseis set).
Troubleshooting
- Authentication failures: If login credentials are incorrect or the SAP B1 service is unreachable, the node will fail to obtain session cookies, resulting in errors. Verify credentials and network connectivity.
- Invalid DocEntry: Providing a non-existent or incorrect
DocEntrywill cause the API call to fail. Ensure the draft document ID exists in SAP B1. - Permission issues: The user account used must have sufficient permissions to save drafts as documents.
- SSL certificate errors: Since the node disables strict SSL verification, if the SAP server has invalid certificates, it may still connect but consider securing the connection properly.
- Error messages: Errors returned from SAP B1 are passed through in the
errorfield. Review these messages for specific SAP-side issues such as validation errors or business logic constraints.
Links and References
- SAP Business One Service Layer Documentation
- SAP B1 Production Orders API Reference (generic link, adjust based on actual SAP version)