Describe in a few words the content of application + link with functional or technical specifications (google links) done with during the project or linked with PPMO
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
Provide some history of the application : When was it created ? What was the initial project ? Who was the original requestor ? If possible provide link to the project information
List of application role + menu role and explanation if we have several applications role with specials rules.
| Role Code | Role Description | Explanation |
|---|---|---|
| ZBI_RCS_SCRE_A01 | SCRE - Transport/Packaging Analysis | Access role |
| ZR_RCS_CA_M76 | Transport & Packaging Analysis | Menu role |
List of autorisation objects mandatory for the application.
| Authorization object | Explanation |
|---|---|
| C_COMPCDE__C_AUTHMA | |
CPFCTR1_2 | |
Reporting documentation drive folder:
Exemple of dataflow overview :
Screen packaging uses many providers as source of data (used in calculations view):
ABMMIM02R
ABMMIM02S
DBMMIC01
DBMMIC02
DBFIGL03
DBFIGL06
DBFIGL13
DBFIGL14
DB_PUSL1
DB_PUSL2
DB_PUHD1
DB_PUHD2
ODSFIGL3
DPFIGL02
ABCOPP02
ABCOPP01
Only one provider is loaded, the ADSO ABSCPK01 "Controlling - Screen Packaging" with data from composite provider CPSCPK01 "Controlling - Screen Packaging".
The composites providers CPSCPK02 and CPSCPK03 use calculations views.
Composite provider CPSCPK01 use calculation view and also ADSO ABSCPK01 (to improve the performance of queries)..
ADSO ABSCPK01 is loaded during the working day with process chain PC_CT_TR_02 - "COSTA - Transactionnal Data 02 (Screen Pckg)".
The process chains starts at 6:30 am and waits the end of process chain PC_FREQUENTLY_LOAD_MAIN ' "01 Frequently Load PC Main" to load adso ABSCPPK01.
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 | 1300000 |
| ~ Total nb of rows loaded (if full) | 1300000 |
| ~ Average Runtime for 50k lines | 15s |
Give details if any historisation is done, example: keep only data greater than beginning of Y-3
Core queries:
BW_QRY_CPSCPK01_0001 - SCREEN - Pack. Inventory analysis - Detailed (Core Query)
BW_QRY_CPSCPK01_0002 - SCREEN - Pack. Inventory analysis - Aggregated (Core Query)
BW_QRY_CPSCPK02_0001 - SCRE - Pack. Purchasing analysis (Core Query)
BW_QRY_CPSCPK03_0001 - SCRE - Pack. Manuf. Consumption analysis (Core Query)
Qlikview queries:
QV_BW_QRY_CPSCPK01_0001 - SCRE - Pack. Inventory for QV / Stock (Core Query)
QV_BW_QRY_CPSCPK01_0002 - SCRE - Pack. Inventory for QV / Var. (Core Query)
QV_BW_QRY_CPSCPK02_0001 - SCRE - Purch. Pack. data for QV (Core Query)
QV_BW_QRY_CPSCPK03_0001 - SCRE - Pack. Consu. interface to QV (Core Query)
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