Difference between revisions of "OEE Oracle Work Order Process Flow"
Jump to navigation
Jump to search
Helena wang (talk | contribs) |
|||
| Line 27: | Line 27: | ||
#OEE sends parameters to 42Q's MES-API. | #OEE sends parameters to 42Q's MES-API. | ||
#42Q returns the results to OEE: Plant Code, Location, Start Time, End Time, Shop Order, MFG Line, Part Number, Process, Finished QTY, Good QTY, Target QTY. | #42Q returns the results to OEE: Plant Code, Location, Start Time, End Time, Shop Order, MFG Line, Part Number, Process, Finished QTY, Good QTY, Target QTY. | ||
| + | |||
== Revision Log == | == Revision Log == | ||
| Line 32: | Line 33: | ||
| | ||
| − | {| | + | {| border="1" class="wikitable" |
|- | |- | ||
| '''Revision #''' | | '''Revision #''' | ||
Revision as of 00:56, 12 March 2019
Work Order Process Flow: OEE → Oracle → 42Q
Steps
The following steps outline how to set an ERP Route. This process can be used by EMS plants using ShopVue or Oracle as an ERP system.
- Set the Target UPH value in Target Maintenance.
- Set the Complete Quantity in Target Maintenance.
- Set the Good Quantity in Target Maintenance.
- Set the following parameters in Oracle: Plant Code, Client ID, Locations, Start Time, End Time.
- OEE sends parameters to 42Q's MES-API.
- 42Q returns the results to OEE: Plant Code, Location, Start Time, End Time, Shop Order, MFG Line, Part Number, Process, Finished QTY, Good QTY, Target QTY.
Revision Log
| Revision # | Revision Date | Description | Updated by | Approved by |
| 1 | 10/4/18 | This is the first draft of the OEE/Oracle How To | Martha Jordan |
