Actions32
- Resource Actions
- Work Order Actions
- Work Order Routing Actions
- Work Order Pos Actions
- Work Order BOM Actions
- Reservation Actions
- Time Receipt Actions
- Item Actions
Work Order Routing → Get
AI-generatedOverview
This node interacts with the BEAS Service Layer API to retrieve a single Work Order Routing record by its ID. It is useful in scenarios where you need to fetch detailed information about a specific work order routing entry, such as in manufacturing or production workflows where routing details are critical for process management. For example, you can use this node to get routing steps, operations, or related data for a particular work order routing ID.
Use Case Examples
- Retrieve a work order routing record by specifying its unique ID to get details like operation sequences and timings.
- Fetch specific fields of a work order routing record by using the 'Select' parameter to limit the response to relevant data.
- Expand related entities such as linked work order lines or components using the 'Expand' parameter to get comprehensive routing information.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the Work Order Routing record to retrieve. This is a required field for the 'Get' operation. |
| Select | Comma-separated list of fields to include in the response. If left empty, all fields are returned. This allows for optimized data retrieval by selecting only necessary fields. |
| Expand | Comma-separated list of related entities to expand in the response. This enables fetching related data along with the main record, such as linked work order lines or components. |
Output
JSON
json- The JSON object containing the retrieved Work Order Routing record data from the BEAS Service Layer API.
Dependencies
- BEAS Service Layer API with valid credentials including service URL and service password for authentication.
Troubleshooting
- Ensure the provided ID is valid and exists in the BEAS system; an invalid ID will cause the request to fail.
- Check that the BEAS Service Layer API credentials are correctly configured and the service URL is reachable.
- If the node fails to get a session cookie during login, verify the service password and network connectivity.
- Invalid JSON in 'Select' or 'Expand' parameters (if used) may cause errors; ensure proper formatting and valid field names.