You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

General presentation

Objective of the application

In context of the Credit Control Area migration done in SAP by using the standard program RFDKLI20, it was necessary to create a dedicated mechanism to migrate data in BW.

Indeed, the CCA migration ran in WP1/PF1/PI1 thanks to the standard SAP program RFDKLI20, does not generate any change logs / any timestamp update on the SAP side.

Therefore, these changes are not catched by the data sources in delta mode, especially 0FI_AR_4. 

The following solution has been designed to reprocess data directly in BW to update the FI documents with the new CCA value, based on data extractions from SAP.

Usage information

Technical flow. No user usage, only IT.


Dataflow overview

Reporting documentation drive folder:

https://drive.google.com/drive/folders/0B0qn89R0RGdqYkZZOFZyYXlXVkE

Exemple of dataflow overview :

Template Application name DataFlow

Functional and Technical rules on Workbench + Reporting

Rules & Explanations

The idea if the BW process for CCA migration is to force the new CCA value (exple: "SYEN" instead of "SOLV") in the FIAR propagation layers (DPFIAR01/02/03) only for the documents migrated in SAP.
To do so:

  • The new aDSO AAFIAR01 "FIAR: Control Credit Area migration - FF" has been created with key 0LOGSYS/C_COMPCDE/0FISCYEAR/0FISCVARNT/0AC_DOC_NO/0ITEM_NUM.
    AAFIAR01 is updated using new Datasource DTS_FIAR_CCA_01 with flat files including the list of WP1/PF1/PI1 migrated documents at item level.


  • Dedicated recursive transformations have been created in order to force the new CCA values in 0C_CTR_AREA in Propagation DSOs DPFIAR01/2/3 for the entries listed in the aDSO AAFIAR01.
    In the start routine, only the entries that matches with the entries in AAFIAR01 are kept in the Source Package. Then, the CCA value is retrieved in the field routine.


  • As this is a one shot reload, and in order to optimize as much as possible the update process by reducing the volume of processed entries: the FULL mode DTPs needs to be filtered C_COMPCDE & 0FISCYEAR.

Dependencies with other applications

Data loadings

Info providers and objects loaded

Loading frequency

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

Reporting

Queries End User Documentation


Main queries

Main functionalities

Broadcast

Maintenance

Known bugs

Recurring procedure

Planned Evolution


  • No labels