Shop Floor Management Orchestrations
JD Edwards EnterpriseOne Orchestrations enable you to automate business processes within JD Edwards EnterpriseOne, thereby simplifying tedious tasks and saving time. Pre-built orchestrations are available for select applications to address common use cases. You can use these orchestrations as models to design custom orchestrations.
For additional information about using and creating orchestrations, see the JD Edwards EnterpriseOne Tools Orchestrator Guide for Studio Version 8 and Prior.
The JDE_ORCH_CreatePartsListShortagesParent orchestration is a container that includes multiple other orchestrations in a specific hierarchy in order to create a parts list shortage.
This table describes the orchestrations that you can use with the Shop Floor Management system:
Orchestration |
Description |
|---|---|
These orchestrations are available for use with the shortage maintenance process: |
|
JDE_ORCH_DeterminePartsListItemShortage |
This orchestration determines shortage for an item on the parts list to be issued for the work order. |
JDE_ORCH_CreatePartsListItemShortage |
This orchestration runs the Shortage Revisions program (P3118) to create shortage for each record that has a material status of 86 in the Part List table (F3112). Then, it creates a cycle count for each shortage using R41411. It runs the Work Order Issues program (P31113) to update the material status from 86 to 87 to indicate that the shortage is processed. The orchestration also triggers shortage notifications to the planner and buyer associated with the Item Branch record (F4102). |
These orchestrations are available for use with the shortage maintenance process: |
|
JDE_ORCH_RemoveOrderItemShortage |
This orchestration removes shortage from the F3118 table when the part list at material status 87 has the quantity issued greater than or equal to the quantity ordered. |
JDE_ORCH_DetermineAndRemoveShortage |
This orchestration determines whether the shortage should be removed from F3118. If required, it removes the shortage. |
These orchestrations trigger shortage notifications: | |
JDE_ORCH_31_PlannerShortageNotify |
This orchestration selects the planner for the item and branch from F4102, and triggers notifications to inform the planner of any shortages. |
JDE_ORCH_31_BuyerShortageNotify |
This orchestration selects the buyer for the item and branch from F4102, and triggers the notifications to inform the buyer of any shortages. |
These orchestrations are available for use with the scrap handling process: | |
JDE_ORCH_31_LowYieldCheck |
This orchestration sends notifications when there are unexpected scrap quantities so that corrective action can be taken immediately. It checks whether there are any open work orders with operations at status 30. If it finds any, it processes those by triggering the JDE_ORCH_31_ScrapCheckProcess orchestration. |
JDE_ORCH_31_ScrapCheckProcess |
This orchestration verifies if the shipped quantity is less than the expected quantity from the record received from the JDE_ORCH_31_LowYieldCheck orchestration. If it is, then the orchestration sends an email to the manager associated with the work order header. When the record is processed, it sets the work order operation to status 31 so that it is not processed again. |
|
This orchestration is available for use with the work order operation rescheduling process: |
|
JDE_ORCH_UpdateWORequested |
This orchestration updates a work order with a newly calculated requested date. This orchestration uses the Work Order Processing (P48013) program to update the work order by calculating and entering the new Requested Date, clearing the values in the Start Date and Planned Effective Date fields, and then clicking OK. The system then updates the Work Order Routing table (F3112) and the Work Order Master File table (F4801), and updates all the three dates on the Scheduled Work Order Operations chart — Start Date, Requested Date, and Effective Date. The orchestration uses version ZJDE0002 of the P48013 program that is set up to update the parts list and routing too. The orchestration uses the following user-defined objects (UDOs):
|