General presentation

Objective of the application

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:

  1. Customer attributes – Only which exists in sales item data (Ship to party)
  2. Material group texts – Only which exists in sales item data

Tool Leader + IT leader of the application: 

  • BW OtC : Craig Wanamake
  • BI4: Laurence DE-ZEEUW
  • Reporting leader OtC: Diogo Paiva 
  • Project manager : Anon Kasemvilas
  • Developer:  Ajay Thalada-ext

Usage information

BO or BI/4 system extracts the files from AL11-SAP Directories on daily basis. There is no direct users

History

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

Roles & Access

Roles and access

There is no report involved in these developments. No access required for end users related to these developments.

Authorization objects

N/A

 Dataflow overview

Functional and Technical rules on Workbench + Reporting

Rules & Explanations

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’

  1. Customer
  2. Material Group
  3. Source System

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 are 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

Dependencies with other applications

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.

Data loadings

Info providers and objects loaded

Process chain: PC_SD_CRM_MD_01

Loading frequency

The process chain ‘PC_SD_CRM_MD_01’ is scheduled on daily basis at 5:00 AM with delta loading

Average performance

 

Key FigureEstimation
~ 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

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.

Reporting

Queries End User Documentation

N/A

Main queries

N/A

Main functionalities

Broadcast

Maintenance

Known bugs

  1. 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.
  2. Material group mapping issue in ECC : Refer #2320357 in fresh desk.  The issue, rootcause  and solution can be found in the following link  BW OTC - PQ1 vs BI4 interface - Issue - Root cause & Solution 2320357


Recurring procedure

Planned Evolution

These developments are temporary.  These objects will be deleted after decommissioning the PPE system.  It is planned to decommission by end of 2019.

 

  • No labels