This application is used to follow:
Tool Leader + IT leader of the application: Name of project or main leader for the application + reporting coodinator
How many users? Which user category ? Is there critical period ? Which geographical perimeter? Describe in one sentence: around 50 users, worldwide or 200 users / European Site
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
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. |
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. |
Reporting documentation drive folder:
https://drive.google.com/drive/folders/0B0qn89R0RGdqYkZZOFZyYXlXVkE
Exemple of dataflow overview :
BW I&P - Quality Management (QM) Dataflow
Transformation done but not used. Only the update rules are used
Daily loading but few cases. Mostly irrelevant
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)
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)
Determining of the shift work and shift work day
Cleaning of data
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.
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.
Look up on DSO ODS_QM09 - Inspection Results: Quantitative/Qualitative Data using batch number and material number from the deliveries to retrieve QM data.
Obsolete
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)
None
Both DSO DSO_DLV1 and DPSD001 (deliveries) need to be loaded before the upwards dataflow is loaded. This is done through the PC:
Detail of process chain, list + link between or special event done for the loading
| 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. |
| 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. |
| 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. |
Detail of frequency : monthly; weekly or else
if possible, give some information on average process chain duration, amount of data loaded and total data volume example: daily process chain loaded in 30 min, weekly chain loaded in 1h15, with around 2k to 10k lines in DELTA mode for a total of 10M lines in cube. The purpose is to give a general overview of the volume of data managed y the application
| 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 |
Give details if any historisation is done, example: keep only data greater than beginning of Y-3
Query end user documentation should be created in the public "Customer Support Wiki" space under the corresponding BW application page : BW - Application. Technical query query documentation, if necessary should be added as a sub-page of this documentation using the BW Technical Query Documentation template.
List the most important and complex queries only with a link to the documentation
Give detail on all complex functionalities: list most important and/or complex KPI, query jump, alerts
Indicate if there are broadcasts and give some details on the broadcast settings.
Give the list and explanation on the known, not-solved, bugs.
List recurring procedures
Detail planned major evolution if already known. Example: complete decommissioning of application is planned in 2017 / Extension to solvay perimeter planned in 2nd semester of 2016
Transformation done but not used. Only the update rules are used