Overview
This node integrates with an ERP system to check the material availability for a specified work order. It retrieves detailed information about the work order, including the item name, required materials, warehouse details, and related sales order. The node then verifies if the necessary materials are available to proceed with the work order.
Common scenarios where this node is beneficial include:
- Manufacturing workflows where you need to confirm that all required materials are in stock before starting production.
- Inventory management processes to prevent delays caused by missing components.
- Automated alerts or decision-making based on material availability status.
For example, a manufacturing automation workflow could use this node to automatically verify material readiness before triggering downstream tasks like scheduling or procurement.
Properties
| Name | Meaning |
|---|---|
| Work Order Name | The name of the work order to check. This is a required string input where you specify which work order's material availability should be verified. |
Output
The node outputs an array of JSON objects, each corresponding to an input item processed. Each output object contains:
status: Overall status of the material check (e.g., whether materials are sufficient).work_order: The name of the work order checked.item_name: The main item associated with the work order.sales_order: Related sales order identifier, if any.triggered_by: The owner or user who created the work order.triggered_on: Timestamp when the work order was created.wip_warehouse: Warehouse location related to the work order.material_check_result: Detailed results of the material availability check, likely including which items are available or missing.
If the node encounters an error and is configured to continue on failure, it outputs an object with:
success: falseerror: Error message describing what went wrong.
The node does not output binary data.
Dependencies
- Requires connection credentials to the ERP system, including:
- ERP domain URL
- API key
- API secret
- These credentials must be configured in n8n prior to using the node.
- Relies on utility functions (
getWorkOrderDataandcheckMaterialAvailability) to fetch and process data from the ERP system.
Troubleshooting
- Missing Work Order Name: If the "Work Order Name" property is empty, the node will throw an error stating that the work order name is required. Ensure this field is filled.
- Authentication Errors: Incorrect or missing API credentials will cause failures connecting to the ERP system. Verify that the API key, secret, and domain are correctly set.
- Network Issues: Connectivity problems to the ERP endpoint can cause timeouts or errors. Check network access and ERP server status.
- Data Not Found: If the specified work order does not exist or has no required items, the node may return null or empty fields. Confirm the work order name is valid.
- When errors occur, enabling "Continue On Fail" allows the workflow to proceed while capturing error details in the output for troubleshooting.