General presentation
Objective of the application
This application is used to follow:
- the Quality Results for Shipment
- As source of MiniCus or MniTab application
- To follow the Limites, Quantitative and qualitative results of the Quality inspections.
- Statistical ratios and calculations on the quality inspections results
Tool Leader + IT leader of the application:
Usage information
History
This application has been created in 2006 for Rhodia data (WP1). It was upgraded for Solvay data (PF1) in 2017. At the same time data from both Rhodia and Solvay was consolidated and optimized in a unique multiprovider, and the number of used queries was reduced to keep only those necessary
Roles & Access
Roles and access
List of application role + menu role and explanation if we have several applications role with specials rules.
| Role Code | Role Description | Explanation |
|---|---|---|
| ZR_RCS_CA_M14 | QM - Quality Management | This role gives access to the Query and Workbooks through role menus. |
| ZBI_RCS_QM_A02 | Quality Results Application - End User role | This role controls access to the application. |
| ZR_*_CA_P01 | Analysis company - XXX | Role to control access to data based on the company code, with XXX being the name of the company code. There is a many role as there is company code. In the new multiproviders created, this role is not relevant. |
| ZR_*_CA_P02 | Analysis - Plant XXX - YYY | Role to control access to data based on the plant, with XXX being the name of the plant, and YYY its description. There is a many role as there is plants. In the new multiproviders created, the infoobject used for authorization is C_PLANT. |
Authorization objects
List of autorisation objects mandatory for the application.
| Authorization object | Explanation |
|---|---|
| ZBI_QM | This object gives global access to objects relevant for authorization yet not relevant for the related multiprovider. This is especially true for the controlling area (CO_AREA) |
| ZXXXXCAP01 | This object gives access to the various infoobjects company code related and relevant for authorization, with XXXX being the company code considered. |
| ZXXXXCAP02 | This object gives access to the various infoobjects plant related and relevant for authorization, with XXXX being the plant considered. |
Dataflow overview
Reporting documentation drive folder:
https://drive.google.com/drive/folders/0B0qn89R0RGdqYkZZOFZyYXlXVkE
Exemple of dataflow overview :
BW I&P - Quality Management (QM) Dataflow
Functional and Technical rules on Workbench + Reporting
Rules & Explanations
Inspection Results
4: ODS_QM09 8ODS_QM07 and ODS_QM08 8ODS_QM07
Transformation done but not used. Only the update rules are used
5: ODSO ODS_QM01 -> ODSO ODS_QM01 and ODSO ODS_QM07 -> ODSO ODS_QM07
Daily loading but few cases. Mostly irrelevant
7: TRSF: DBQM03 -> CRQM06 (Solvay) and TRDF: DBQM04 -> CRQM05 (Rhodia) and TRSF DBQM04 -> CRQM03 and TRSF DBQM03 -> CRQM04 (Solvay)
Difference between historical and current data.
7-a: TRSF: DBQM03 -> CRQM06 (Solvay) and TRDF: DBQM04 -> CRQM05 (Rhodia)
Loading of the inspection lots with a creation date /BIC/C_ENSTEHD greater than current date minus 3 years (ex. current date 16/02/2017 ==> Loading of data from 01/01/2015 and upwards)
7-b: TRSF DBQM04 -> CRQM03 and TRSF DBQM03 -> CRQM04 (Solvay)
Loading of the inspection lots with a creation date /BIC/C_ENSTEHD smaller than current date minus 3 years (ex. current date 16/02/2017 ==> Loading of data older than 01/01/2015)
8: TRSF: DPQM09 -> DBQM04 (Rhodia) and TRSF: DPQM08 -> DBQM03 (Solvay)
- Deletion od data if results exist (field C_MRMITNI).
- CO_AREA determination
9: TRSF: DPQM07 -> DBQM03 (Solvay) and TRSF: DPQM08 -> DBQM03 (Solvay) and TRSF: DPQM07 -> DBQM03 (Rhodia) and TRSF: DPQM09 -> DBQM04 (Rhodia)
Mapping of a few fields with the values of QASE, QAMR or QASR, depending on the values of c_semesni (if value is set for QASE), c_secode1 (code QASE), c_srcode1 (Code QASR), C_SRMITNI (if value is set for QAMR)
10: TRSF: IH_QM_2LIS_05_QE1_RCS -> DPQM09 and TRSF: IH_QM_2LIS_05_QE1_SOLVAY -> DPQM08
Determining of the shift work and shift work day
11: TRSF: 2LIS_05_QE1 / Rhodia -> IH_QM_2LIS_05_QE1_RCS and TRSF: 2LIS_05_QE1 Solvay -> IH_QM_2LIS_05_QE1 and TRSF: 2LIS_05_QE1 Solvay -> IH_QM_2LIS_05_QE1 and TRSF: 2LIS_05_QE2 - Solvay -> IH_QM_2LIS_05_QE2
Cleaning of data
Inspection Results for deliveries
1: TRSF: DPSD001 -> DBQM06 (Solvay)
Look up on DSO DBQM03 - DSO QM - Business Layer : Inspection Results (Solvay) using batch number and material number from the deliveries to retrieve QM data. There is also a filter on the "generic inspection lot". Solvay is using some batch to do multiple deliveries. However this generates countless lines which would then be multiplied depending on the lines in DBQM03 (generating at worst more than 5 millions lines). Those generic lot are therefore filtered if the number of lines for a given couple batch / material is more than 30.
2: TRSF: DSO_DLV1 -> DBQM05 (Rhodia)
Look up on DSO DBQM04 - DSO QM - Business Layer : Inspection Results (Rhodia) using batch number and material number from the deliveries to retrieve QM data.
3: ODSO DSO_DLV1 -> ODSO DSO_QMTL
Look up on DSO ODS_QM09 - Inspection Results: Quantitative/Qualitative Data using batch number and material number from the deliveries to retrieve QM data.
6: ODSO DSO_QMTL -> CUBE CUB_QM03
Obsolete
7: TRSF: DBQM05 -> CRQM08 (Rhodia) and TRSF: DBQM05 -> CRQM09 (Rhodia) and TRSF: DBQM06 -> CRQM07 (Solvay) and TRSF: DBQM06 -> CRQM10 (Solvay)
Difference between historical and current data
7-a: TRSF: DBQM06 -> CRQM10 (Solvay) and TRSF: DBQM05 -> CRQM09 (Rhodia)
Loading of the inspection lots with a creation date /BIC/C_ENSTEHD greater than current date minus 2 years (ex. current date 16/02/2017 ==> Loading of data from 01/01/2015 and upwards)
7-b: TRSF: DBQM05 -> CRQM08 (Rhodia) and TRSF: DBQM06 -> CRQM07 (Solvay)
Loading of the inspection lots with a creation date /BIC/C_ENSTEHD smaller than current date minus 2 years (ex. current date 16/02/2017 ==> Loading of data older than 01/01/2015)
Dependencies with other applications
Inspection Results
None
Inspection Results for deliveries
Both DSO DSO_DLV1 and DPSD001 (deliveries) need to be loaded before the upwards dataflow is loaded. This is done through the PC:
- DPSD001: PC_SD_01
- DSO_DLV1: PC_SD
Data loadings
Info providers and objects loaded
Loading frequency
Main Process Chains
| Process Chain | Code | Comments |
|---|---|---|
| META - D - QM - Master Chain | PC_QM_00 | Loading of data in delta mode |
| META - ADH - QM - Inspection Results Init | PC_QM_19 | Used to reload data for dataflow QM. Caution: The loading of the two DSO ODS_QM07 and ODS_QM01 for Rhodia is not included. |
| TD - ADH - QM - Deletion of Inspection Results data | PC_QM_18 | Used to delete data in infoproviders |
| TD - Y - QM - Inspection Results - Historic Data | PC_QM_07 | Updates the infocubes containing historical data for both Solvay and Rhodia Data with the previous year. The infocubes containing the last 5 years of data is emptied and reloaded accordingly. Caution: Delta won't retrieve all data when loading historic data for 2017 as a delta without transfer was done from DSO to infocube in March 2017. Therefore to retrieve year 2017, it's best to use a full and not the delta |
| TD - Y - QM - Qual. Insp. Res. for deliv. - Historic Data | PC_QM_17 | Updates the infocubes containing historical data for both Solvay and Rhodia Data with the previous year. The infocubes containing the last 5 years of data is emptied and reloaded accordingly. Caution: Delta won't retrieve all data when loading historic data for 2017 as a delta without transfer was done from DSO to infocube in March 2017. Therefore to retrieve year 2017, it's best to use a full and not the delta |
Sub Process Chains
| Process Chain | Code | Comments |
|---|---|---|
| MD - D - QM - Textes QM | PC_QM_24 | Loading of the texts for specific QM MD |
| TD - D - QM - Propagation Layer - Solvay | PC_QM_01 | Used to load Solvay data for the propagation layer for every QM projects |
| TD - D - QM - PL - Inspection Results (Solvay) | PC_QM_12 | Used to load Solvay data for the propagation layer for Inspection Results |
| TD - D - QM - Propagation Layer - Rhodia | PC_QM_02 | Used to load Rhodia data for the propagation layer for every QM projects (Currently not used) |
| TD - D - QM - Business Layer - Rhodia | PC_QM_03 | Used to load Rhodia data for the business layer for every QM projects |
| TD - D - QM - BL - Inspect. Results for Deliveries - Rhodia | PC_QM_09 | Used to load Rhodia data for the business layer for Inspection Results for deliveries |
| TD - D - QM - BL - Inspection Results - Rhodia | PC_QM_08 | Used to load Rhodia data for the business layer for Inspection Results |
| TD - D - QM - Business Layer - Solvay | PC_QM_04 | Used to load Solvay data for the business layer for every QM projects |
| TD - D - QM - BL - Inspect. Results for Deliveries - Solvay | PC_QM_10 | Used to load Solvay data for the business layer for Inspection Results for deliveries |
| TD - D - QM - BL - Inspection Results - Solvay | PC_QM_11 | Used to load Solvay data for the business layer for Inspection Results |
| TD - ADH - QM - BL - Insp Res for Del - Rhodia - Init < 2013 | PC_QM_25 | Used when loading Rhodia data for project inspection results for deliveries. Given the volumetry generated, it's easier to load the data year by year. This PC loads data depending on the creation date up to 31.12.2012 |
| TD - ADH - QM - BL - Insp Res for Del - Rhodia - Init >=2013 | PC_QM_26 | Used when loading Rhodia data for project inspection results for deliveries. Given the volumetry generated, it's easier to load the data year by year. This PC loads data depending on the creation date from 01.01.2013 |
| TD - ADH - QM - BL - Insp Res for Del - Solvay - Init < 2013 | PC_QM_27 | Used when loading Solvay data for project inspection results for deliveries. Given the volumetry generated, it's easier to load the data year by year. This PC loads data depending on the creation date up to 31.12.2012 |
| TD - ADH - QM - BL - Insp Res for Del - Solvay - Init >=2013 | PC_QM_28 | Used when loading Solvay data for project inspection results for deliveries. Given the volumetry generated, it's easier to load the data year by year. This PC loads data depending on the creation date from 01.01.2013 |
| TD - D - QM - Reporting Layer - Rhodia | PC_QM_05 | Used to load Rhodia data for the reporting layer. |
| TD - D - QM - RL - Inspect. Results for Deliveries - Rhodia | PC_QM_15 | Used to load Rhodia data for the reporting layer for inspection results for deliveries. |
| TD - D - QM - RL - Inspection Results - Rhodia | PC_QM_13 | Used to load Rhodia data for the reporting layer for inspection results. |
| TD - D - QM - Reporting Layer - Solvay | PC_QM_06 | Used to load Solvay data for the reporting layer. |
| TD - D - QM - RL - Inspect. Results for Deliveries - Solvay | PC_QM_14 | Used to load Solvay data for the reporting layer for inspection results for deliveries. |
| TD - D - QM - RL - Inspection Results - Solvay | PC_QM_16 | Used to load Solvay data for the reporting layer for inspection results. |
Average performance
| Key Figure | Estimation |
|---|---|
| ~ Average Process Chain Runtime | |
| ~ Average nb of rows loaded per load | |
| ~ Total nb of rows loaded (if full) | |
| ~ Average Runtime for 10k lines |
Record Keeping
Reporting
Queries End User Documentation
Main queries
Main functionalities
Broadcast
Maintenance
Known bugs
Recurring procedure
Planned Evolution
Transformation done but not used. Only the update rules are used