Fact table of operation tracking
The fact table of operation tracking belongs to the WO-Operation tracking datamart. It contains elements coming from time tracking
Prerequisites
The MFGHEAD, MFGOPE et MFGOPETRK tables must be parameterized to be audited for the BI if data synchronization should be incremental (update of the elements modified since the last synchronization only).
Description
One of the objectives of the universe dedicated to operation tracking is to facilitate data handling by inexperienced users, it is in no way to duplicate data:
- Some information deemed secondary is not transmitted.
- Conversely, other information is calculated.
- Finally, information is restructured if needed.
Data detail
Field code | Normal title | Menu | Table | Object type |
MFGFCY | Production site | 0 | 0 | Dimension |
CPY | Company | 0 | 0 | Dimension |
FIYNUM | Financial year | 0 | 0 | Technical |
PERNUM | Period | 0 | 0 | Dimension |
MFGNUM | Work Order | 0 | 0 | Dimension |
ROUNUM | BOM | 0 | 0 | Dimension |
ROUALT | Route alternative | 0 | 0 | Dimension |
OPENUM | Operation | 0 | 0 | Information |
IPTDAT | Posting date: | 0 | 0 | Dimension |
EXTWST | Planned work center (main & second) | 0 | 0 | Information |
CPLWST | Achiev. work center (main & second) | 0 | 0 | Dimension |
TRKOPETIM | WO planned time/achieved qty | 0 | 0 | Information |
CPLOPETIM | Achieved op. time | 0 | 0 | Measurement |
CPLSETTIM | Achieved setup time | 0 | 0 | Measurement |
OPEUOM | Entry unit | 0 | 0 | Dimension |
OPEWORCOE | Conversion factor REL OPE | 0 | 0 | Information |
TRKQTY | WO planned qty/achieved qty | 0 | 0 | Information |
CPLQTY | Actual quantity | 0 | 0 | Measurement |
REJCPLQTY | Rejected quantity | 0 | 0 | Measurement |
QUACPLQTY | QC achieved quantity | 0 | 0 | Measurement |
MFGTRKNUM | Tracking button. | 0 | 0 | Information |
Technical additions
Synchronization rules
The fact table of work orders is populated on the basis of 2 synchronization rules:
- MFGOPETRK1: for the main work centers
- MFGOPETRK3: For secondary work centeres
A record in the database can thus yield two records in the datamart if there is a main work center and a secondary work center.
Only the closed work orders are fed to the datamart.
Specific loading formulas
- WO planned quantity/achieved quantity - [F:MFO]EXTQTY*[F:MFG]CPLQTY/[F:MFG]EXTQTY: This formula is used to express the quantity planned for the operation to produce the achieved quantity of finished products
- WO planned time/achieved time - [F:MFO]EXTOPETIM*[F:MFG]CPLQTY/[F:MFG]EXTQTY: This formula is used to express the time planned for the operation to produce the achieved quantity of finished products
Specific loading functions
- TRTX3BI.GETCPY([F:MFG]MFGFCY): This function returns the company of the production site
- TRTX3BI.GETEXE([F:MFG]MFGFCY,[F:MKO]DACDAT): this function is used to return the fiscal year of the operation tracking entry date.
TRTX3BI.GETPER([F:MFG]MFGFCY,[F:MKO]DACDAT): This function is used to return the period of the operation tracking entry date.