Access Management 

DataFlow

Overview

https://docs.google.com/presentation/d/1xV7_SS0oan6RmQgTHF7gsFtxLjLS5Fl4Ze7ITbSs4JY

Objective of the application

Integration in WBP COSTA model of the hierarchy created in Anaplan to identify budget owner and budget reviewer levels, and the dependencies between the levels.

This hierarchy is meant to be used in QlikSense Applications.

Two flat files are integrated in BW in order to load: Anaplan hierarchy levels, their related Responsible Cost Center, their description and their attributes.

This solution is temporary.

Tool Leader + IT leader of the application: Guillaume.THEVENET@solvay.com 

Functional and Technical rules on Workbench + Reporting

Flow Levels attributes and texts

Source file is generated from Anaplan and has to be stored in AL11 in BW :  /exploit/BW/Anaplan_inbound/Level 5 attributes and texts.csv

Program ZBW_FILE_TRANSFERT can be used to upload the file.

File template is available in folder https://drive.google.com/drive/folders/1Dv6RFIRwdyWY3eneZzFy2j-WSIHtAkbT

This flat file contains Levels descriptions and Level 5 attributes and is loaded in Inbound ADSO AACOCT02.

Data cleaning routines are implemented on file extraction :

• Characters ‘#’ are deleted for all fields
• Characters ‘!’ are deleted for level codes
• Level codes and Bridge fields are translated in upper case and spaces are deleted

For level texts loading (InfoObjects C_LEVEL1/2/3/4), duplicates data records are deleted in start routine.

For level 5 attributes loading (InfoObjects C_LEVEL5):

• ALPHA conversion is manually applied in PRS Company code routine.
• Bridge routine is converted to Boolean. Value ‘X’ is assigned:
  • If source value equals ‘X’ or ‘1’
  • Else if source value exists in RSBOOLT table where BOOL equals ‘X’ : field TXTSH, which correspond to ‘True’ value in various languages
  • Else if a record exists in Global Filter Master Data GLBFILT with STREAM = ‘F2G’ and RULE = ‘BRIDGE’

Flow Link Level 5 - Responsible Cost center

The source file has to be stored in AL11 :  /exploit/BW/Anaplan_inbound/Link Level 5 - Responsible Cost center.csv

Program ZBW_FILE_TRANSFERT can be used to upload the file.

File template is available in folder https://drive.google.com/drive/folders/1Dv6RFIRwdyWY3eneZzFy2j-WSIHtAkbT

This flat file contains mapping between Level 5 and Responsible Cost center and is loaded in Inbound ADSO AACOCT01.

Data cleaning routines are implemented on file extraction :

• Characters ‘#’ are deleted in Responsible Cost Center codes
• Characters ‘#’ and ‘!’ are deleted for level 5 codes
• Level codes are translated in upper case and spaces are deleted

Then data is loaded in ADSO APCOCT18 “Link Level 5 - Responsible Cost center”:

• In start routine, all records where couple Controlling Area / Cost Center does not exist in Master Data C_COSTCTR are deleted.
• Version, Date From and Date To fields have been created for further implementation. As for now, constant values are assigned.
• Controlling Area and Responsible Cost Center values are substrings of source field RESP_CC.

Reporting

Dependencies with other applications

Used by COSTA model.

Data loadings

Info providers and objects loaded

Both data flow are loaded in Process chain PC_CT_LEVEL5_HIER (“COSTA - Hierarchy Level 5 - Responsible Cost center”).

Both Inbound ADSO are cleaned up before the new loading.

Flat files are loaded in FULL mode.

Loading frequency

Loadings are not scheduled. Process chain execution is processed on demand.

Loading steps

1. Load new csv files in corresponding AL11 folders (see upward) using program ZBW_FILE_TRANSFERT
2. Run Process chain PC_CT_LEVEL5_HIER

Average performance

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

Record Keeping

N/A

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 criticity, workarounds and resolution plan.>

Roadmap