The purpose of these developments is to generate files and store them in AL11 - SAP Directories on daily basis. These files will be extracted by BO or BI/4 system on daily basis for PPE application.
Details of the data files:
Tool Leader + IT leader of the application:
BO or BI/4 system extracts the files from AL11-SAP Directories on daily basis. There is no direct users
These developments exist in PQ1 system. As the system got decommissioned these developments are again developed and transported to WBP system.
Object details in PQ1:
Refer the data flow of DSO ‘ZZVCRM2’ in PQ1 & the program ‘ZSD_BO_INTERFACE’ in PQ1
There is no report involved in these developments. No access required for end users related to these developments.
N/A
The delta data from the DSO ‘DPSDSO02’ (Sales document item data) is transferred in to the DSO ‘DBSDSOT1’ (Temporary master data for BI4 - PPE) on a daily basis.
The following fields are transferred from DSO ‘DPSDSO02’ -> DSO ‘DBSDSOT1’
The program ‘ZSD_BO_INTERFACE’ extracts the data from the DSO ‘DBSDSOT1’; With reference to the data of DSO ‘DBSDSOT1’ the attributes of customer master and texts of material group and extracted and then placed in the AL11 in the following locations
Customer attributes data path ---- /exploit/BW/SD/PPS_customer_PQ1.txt
Material group data path ----------- /exploit/BW/SD/PPS_mat_grp_PQ1.txt
List of objects developed as part of these developments.
Object Type | Technical Name |
DSO | DBSDSOT1 |
Transformation | 0EUBSUC9X30G1ZJCHODQW8LBZDO2TNZZ |
DTP | DTP_B1FNYSNDTRTODIO213ZENYY57 |
Program | ZSD_BO_INTERFACE |
Process chain | PC_SD_CRM_MD_01 |
Mapping Information
DPSDSO02-0LOGSYS -> DBSDSOT1-0LOGSYS
DPSDSO02-C_MAT_GRP -> DBSDSOT1-C_MAT_GRP
DPSDSO02- C_SHIPTID -> DBSDSOT1-C_CUSTID
The master data objects like ‘C_MAT_GRP’(Text data), C_CUSTID(Attributes) and transaction data ‘DSO DPSDSO02’ should be loaded first then only the process chain ‘PC_SD_CRM_MD_01’ should be triggered. Otherwise the generated file won’t contain the latest data.
The files have to generated to the folder before BI4 get the data.
Process chain: PC_SD_CRM_MD_01
The process chain ‘PC_SD_CRM_MD_01’ is scheduled on daily basis at 5:00 AM with delta loading
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 |
The key fields in the DSO ‘DBSDSOT1’ are Customer, Material Group & Source system. There is no date field in the DSO ‘DBSDSOT1’ and it only stores the combination of key fields in the active table of DSO.
So it is not feasible and not even required to archive or delete the historical data based on date.
The change log data in the DSO ‘DBSDSOT1’ is cleared on daily basis and this activity is part of the process chain ‘PC_SD_CRM_MD_01’. The data older than 0 days will be cleared from the changelog of DSO.
N/A
N/A
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.
If the dependent objects are not loaded successfully then the generated files wont contain the latest data; In this case, need to trigger the process chain ‘PC_SD_CRM_MD_01’ again after the dependent objects are successfully loaded so that the updated files will be generated else the updated files will be generated on the next day.
List recurring procedures
These developments are temporary. These objects will be deleted after decommissioning the PPE system. It is planned to decommission by end of 2019.