Access Management
List of application role + menu role and explanation if we have several applications role with specials rules.
| Role Code | Role Description | Explanation |
|---|---|---|
| ZBI_RCS_DP_A03 | Demand Planning - Dynasys Keyuser | Authorization object ZBI_DPS_K
|
List of authorization objects mandatory for the application.
| Authorization object | Explanation |
|---|---|
DataFlow
Overview
Technical Rules on Workbench
MVDYN11 - DYN - Reporting is composed by 16 cubes, but only fw of them are still loaded:
| Cube | Description | last loading (checked in 12.06.2023) |
|---|---|---|
| CRAPO002 | APO - Global (Dynamic) | No data |
| CRAPO006 | APO - Novecare (Snapshot History) | No data |
| CRAPO005 | APO - Novecare (Snapshot) | No data |
| CRAPO008 | APO - Polyamide Downstream (Snapshot History) | No data |
| CRAPO007 | APO - Polyamide Downstream (Snapshot) | 07.06.2020 |
| CRAPO010 | APO - Polyamide Upstream (Snapshot History) | No data |
| CRAPO009 | APO - Polyamide Upstream (Snapshot) | 07.06.2020 |
| CRAPO012 | APO - Special Chemicals (Snapshot History) | No data |
| CRAPO011 | APO - Special Chemicals (Snapshot) | 10.23.2020 |
| CRAPO004 | APO - Special Chemicals / Rare Earth (Snapshot History) | No data |
| CRAPO003 | APO - Special Chemicals / Rare Earth (Snapshot) | 10.23.2020 |
| CRDYN11 | DYN - Reporting (Dynamic) | 12.06.2023 |
| CRDYN14 | DYN - Reporting PAX Historic | No data |
| CRDYN15 | DYN - Reporting PV/PY/PV since 2019(OBS) | No data |
| CRDYN13 | DYN - Reporting SnapShot | 12.06.2023 |
| CRLOG01 | LOG - Reporting (Dynamic) | No data |
| CRLOG02 | LOG - Reporting (SnapShots) | No data |
CRDYN11
source data comes from hana calculation view CV_EXP_FORE_DR_BW based on table and view TB_EXP_FORE_DR_BW / VT_EXP_FORE_DR_BW.
TRSF : DTS_CV_EXP_FORE_DR_BW (Dynasys) -> DPDYN04
End routine: if in master data global filter C_GLBFILT for stream DPS and rule PROSPECTS the low value = X AND if the size of C_DYN_025 is > 11 then C_DYN_003 (Customer with System Extension) = C_DYN_025 (Ship-to (including Prospects) with extension). If low value is not equal to X, C_DYN_025 takes the 11 characters after the first seven and C_DYN_003 (Customer with System Extension) = C_DYN_025 (Ship-to (including Prospects) with extension).
ODSO DPDYN04 -> ODSO DBDYN20
Start routine defines the source system (logsys) with help of last character of C_DYN_005 (R = Rhodia, S = Solvay).
Fields routines:
- C_MATNR2 → determined with module function CONVERSION_EXIT_MATN1_INPUT with field C_DYN_005 in input.
- 0DISTR_CHAN = two first characters from field C_DYN_006 (Distribution Channel with System Extension).
- C_DYN_GBU (BFC GBU for Dynasis) = C_DYN_003 (Customer with System Extension) without the last characters.
- C_SHIPTID (Ship-to party (Core)) = C_DYN_003 (Customer with System Extension) without the last characters.
- C_FLGMTH (Concerned Period (Flag)) = M
- 0UNIT (Unit of measure) = KG
- C_SAL_OFF (Sales Office) = DYN
- C_DOCTYP2 (Order document type) = DYN
- C_COMPCDE (Company code) = DYN
End routine:
C_DYN_010 & CPFCTR1_2 come from master data C_DYN_005. If no corespodance found with C_DYN_005, fields come from master data G_CWWE01.
CPFCTR2_2 & C_MAGNITU come from master data C_DYN_018 (internal filled with selection on field C_DYN_005), we check if in internal table we have data in function of fields C_DYN_018 =<RESULT_FIELDS>-/BIC/C_DYN_003 and C_DYN_005 =<RESULT_FIELDS>-/BIC/C_DYN_005. If we have a correspondance, master data C_MATPNT2 is read to fill field CPFCTR3_2. Else, CPFCTR2_2 & C_MAGNITU & CPFCTR3_2 are empty.
C_SHTCTRY comes from master data C_DYN_024.
C_SOLDID & C_SOLDTO come from master data C_DYN_014 (in function of field C_DYN_003).
C_PROD comes from master data C_MATNR2.
IECRA (G_CWWE01) for RCS records is searched from master data G_CWWE01 with the logsys and the division found in master data C_MATNR2 we we searched the C_PROD.
If IECRA is found, we read again master data G_CWWE01 with the IEACRA (and with CPFCTR1_2 and C_PFCTR2 not empty).
If record found, we fill fields C_DYN_010 with C_PFCTR2 from G_CWWE01 , CPFCTR1_2 with CPFCTR1_2 from G_CWWE01, CPFCTR2_2 with CPFCTR2_2 from G_CWWE01 and CPFCTR3_2 with CPFCTR3_2 from G_CWWE01 (else fields are empty).
TRSF: DBDYN20 (DynaSys) -> CRDYN11
Start routine:
Internal table itb_c_dyn_017 is filled with data from master data itb_c_dyn_017 where C_DYN_017 = SOURCE_PACKAGE-/bic/C_DYN_003 and C_DYN_006 = SOURCE_PACKAGE-/bic/C_DYN_006.
Internal table itb_C_GBR14 is filled with data from master data C_GBR14 in function of fields logsys, C_PROD, CPFCTR1_2 and C_SHIPTID.
Field routines:
C_DYN_017 & C_DYN_021 → If in master data global filter C_GLBFILT for stream DPS and rule PROSPECTS the low value is empty, field equal C_DYN_025 else field = C_DYN_003.
C_SOTCTRY Sold-to Country comes from master data C_SOLDTO
End routine
Fields C_SALEMP & C_ZIPART come from internal table itb_c_dyn_017 (or fields are empty).
Field C_GBR4 comes from internal table itb_C_GBR14 or equal source field C_SHIPTID.
CRDYN13
TRSF: DTS_CV_EXP_FORE_BW (DynaSys) -> DPDYN01
source data comes from hana calculation view CV_EXP_FORE_BW based on table and view TB_EXP_FORE_BW / VT_EXP_FORE_BW.
In start routine the records with SHIPTO_CODE with size > 11 are deleted.
Field routine: C_FCSTMTH (End of Month View) comes from master data global filter (only if C_ACTIVE = Y):
ODSO DPDYN01 -> ODSO DBDYN13
For C_DYN_010, CPFCTR1_2, CPFCTR2_2, C_MAGNITU, C_SOLDID and C_SOLDTO and IECRA it's the same rules as transformation ODSO DPDYN04 -> ODSO DBDYN20 .
C_SHTCTRY comes from master data C_CUST_ID.
For IECRA, we search for Solvay source system, not Rhodia.
ODSO DBDYN13 -> ODSO DBDYN13 Compute GH/BIAS 1
End routine:
Data in source package are stored in internal table ITB_GH (sorted in descending mode in function of fields C_DYN_003, C_DYN_005, C_DYN_006, LOGSYS, CALMONTH and C_FCSTMTH) and records with same C_DYN_003, C_DYN_005, C_DYN_006, LOGSYS and CALMONTH are deleted to avoid duplcate entries.
Then we search for each reords of source package if there are a correspondance in ITB_GH (with keys C_DYN_003, C_DYN_005, C_DYN_006, LOGSYS and CALMONTH)
If correspondance found:
- K_BIASM1 = ( /BIC/K_FFM1QTY - <FS_GH>-/BIC/K_GHQTY ) in absolute value.
- K_BIASSTF = ABS(<RESULT_FIELDS>-/BIC/K_STFM1QT - <FS_GH>-/BIC/K_GHQTY)
- K_BIASSTA = ABS(<RESULT_FIELDS>-/BIC/K_RFM1QTY - <FS_GH>-/BIC/K_GHQTY)
- K_DYN_278 = ABS(<RESULT_FIELDS>-/BIC/K_DYN_277 - <FS_GH>-/BIC/K_GHQTY)
- K_DYN_279 = ABS(<RESULT_FIELDS>-/BIC/K_SHFM1QT - <FS_GH>-/BIC/K_GHQTY )
For C_DYN_010, CPFCTR1_2, CPFCTR2_2, C_MAGNITU, C_SOLDID and C_SOLDTO and IECRA it's the same rules as transformation ODSO DPDYN04 -> ODSO DBDYN20 .
C_SHTCTRY comes from master data C_CUST_ID.
TRSF: DBDYN13 (DynaSys) -> CRDYN13
Same rules as transformation TRSF: DBDYN20 (DynaSys) -> CRDYN11.
Reporting
Dependencies with other applications
We should have the information where the application is sending or receiving information (e.g. APD open hub)
Data Loading
Info Providers and objects loaded
Detail of process chain, list + link between or special event done for the loading
| Main Process Chain | Final Provider Loading | Frequency | Time start | Duration |
|---|---|---|---|---|
Data Quality Control
Operational Documentation
Procedures
<Describe the recurring procedures needed to operate the application (eg. start/pause/terminate/restart the app processes, data preparation, data ingestion, ETL, data visualization, data export, other manual activities)>
Scheduling
<Describe the scheduling in place for the application (eg. existing jobs, trigger time/event based, dependencies)>
Monitoring
<Describe the monitoring checks to confirm the application is performing well (eg. check the overall status, check performance metrics like runtime/data volume/memory/disk/CPU, maintain and react to alerts/notifications)>
Error Handling
<Describe how to handle errors (eg. error codes, description and respective resolution, alert users)>
Known Bugs
<List the existing bugs, its criticality, workarounds and resolution plan.>
Roadmap
<List past & future evolutions for the application (including links to MED/FSD/TSD>