Access Management 

DataFlow

Overview

The DSOS (AACOCT01 and AACOCT02) and InfoObjects (C_LEVEL1, C_LEVEL2, C_LEVEL3, C_LEVEL4 and C_LEVEL5) from previous solution were reused.

General presentation

Objective of the application

New BW L5 hierarchy definition and integration to Anaplan.

Tool Leader: Charlotte Rollier

IT leader of the application: Guillaume Thevenet

History

The L5 hierarchy was before defined with the steps below, coming from Anaplan to BW via flat files.

AS-IS : The management of the L5 Budget hierarchy is the following one : 

1. The data are managed in many google spreadsheets  (maintain by SU MAC Data team)
2. Anaplan admin team generated 2 files from the google spreadsheet one for L5 budget hierarchy detail with all the nodes L1 to L5 + attributes like BSA, GBU etc and second files with the link between L5 code and Cost center
3. Anaplan admin load these 2 files on F2G model
4. Automatic process generate 2 files from F2G model to AWS S3 bucket
5. Webmethods process in recurrent mode (several times per day) transfer the 2 files from AWS S3 Bucket to BW folder
6. A BW process chain uploads the data on BW objects (master data and ADSO)

In this new solution we define the Levels applying rules to the existing BW Cost Center data, then generate outbound files to Anaplan.

Technical Rules on Workbench

Level Rules definition

Extraction rules

Only ECO and SCO scope data. (C_COMPCODE-C_SCOPE - 02 for ECO and 03 for SCO)

Remove records where Level 5 is empty or only "_".

Remove records where Level 1 is empty.

Reporting

Dependencies with other applications

Global Filter variables for the Level Exceptions, Controlling Areas, GBU Functions and Scopes.

Open Hubs for Anaplan

BW folder for the files: /exploit/BW/Anaplan_outbound

Format: in TXT, Unicode format and comma as separator.

Add “ “ for the descriptions fields as some of them could contain comma and raise issues in the Anaplan upload process.

Custom Program ZBW_ANAPLAN_OUTBOUND_HEADER created to add the files header lines, this is the last step from Process Chain PC_CT_LEVEL5_HIER2.

OH_COCT14 - F2G Anaplan - L5 Budget Hierarchy ECO

File name: L5_budget_hierarchy_ECO.txt

Structure definition:

L1 Code (mandatory) (extraction only L1 not empty)

L1 Description (mandatory)

L2 Code (mandatory)

L2 Description (mandatory)

L3 Code (mandatory)

L3 Description (mandatory)

L4 Code (mandatory)

L4 Description (mandatory)

L5 Code (mandatory)

L5 Description (mandatory)

Scope (mandatory)

Filter: Only Scope (C_COMPCODE-C_SCOPE = 02 - ECO)

OH_COCT15 - F2G Anaplan - L5 Link Cost Center ECO

File name: L5_link_cc_ECO.txt

Structure definition:

CC Code (mandatory)

CC Description (mandatory)

LVL5 Code (mandatory) 

BSA (not mandatory)

Scope (mandatory)

Filter: Only Scope (C_COMPCODE-C_SCOPE = 02 - ECO)

OH_COCT16 - F2G Anaplan - L5 Budget Hierarchy SCO

File name: L5_budget_hierarchy_SCO.txt

Structure definition:

L1 Code (mandatory) (extraction only L1 not empty)

L1 Description (mandatory)

L2 Code (mandatory)

L2 Description (mandatory)

L3 Code (mandatory)

L3 Description (mandatory)

L4 Code (mandatory)

L4 Description (mandatory)

L5 Code (mandatory)

L5 Description (mandatory)

Scope (mandatory)

Filter: Only Scope (C_COMPCODE-C_SCOPE = 03 - SCO)

OH_COCT17 - F2G Anaplan - L5 Link Cost Center SCO

File name: L5_link_cc_SCO.txt

Structure definition:

CC Code (mandatory)

CC Description (mandatory)

LVL5 Code (mandatory) 

BSA (not mandatory)

Scope (mandatory)

Filter: Only Scope (C_COMPCODE-C_SCOPE = 03 - SCO)

Data loadings

Process Chain: PC_CT_LEVEL5_HIER2 - COSTA - Hierarchy Level 5 from ECC

Loading frequency

Daily at 10pm (Belgium calendar - not loaded on sunday & belgium bank holidays)

Note: the ZCBS hierarchy is loaded at 7pm. A cost center must be assigned to the correct ZCBS group in the ERP before 7pm in order to be included in the correct L5 group at 10pm

To allow the filling of the cost center master data BW attributes linked to L5 NASA Hierarchy, some pre-requisites are mandatory :

A) loads of the attributes of the cost center from ERP's (WP1, PF1 and PI1) and transaction code ZBW_CBS

B) Load of the ZCBS hierarchies 

C) Load of L5 fields

A-1) The load of the cost center master data from PF1 :

Process chain : RPC_COOM_MD_PF1

Daily schedule at around 02:00am (CET Time)

Frozen period : period from end of December until around 20th of January which is not allow to reflect the update done in master data to not impact the end yearly closing period which should be done with th scope of the current year and not the future year)

• L oad during the frozen period :

• Load after frozen period :

A-2) The load of the cost center master data from PI1 :

Process chain : RPC_COOM_MD_PI1

Daily schedule at around 02:00am (CET Time)

• During the frozen period :

• Out of frozen period :

A-3) The load of the cost center master data from WP1

Process chain : ZPC_MD_ATTR_RCS

Daily schedule at around 00:00am (CET Time)

• During the frozen period :

• Out of frozen period :

A-4) The load of the cost center master data from WP1 with process chain : FREQUENTLY_LOAD_MD

Process chain : FREQUENTLY_LOAD_MD

Daily schedule (3 times a day and 6 times a day during closing) 

• During the frozen period :

• Out of frozen period :

A-5) The load of the cost center master data from Non ERP flow

Process chain : PC_FC_CYTEC_001

Daily schedule: 5 times a day

• During the frozen period :

• Out of frozen period :

B-1) Load of the hierarchy every days at 07:00pm (CET time) CO_DAILY_MASTER_DATA (Daily Hierarchies CO 1/2)

For WP1 data :

Master process chain : DAILY_PC_HIER_TXT

B-2) Load of the hierarchy every days at 07:00pm (CET time) CO_DAILY_MASTER_DATA_HY (Daily Hierarchies CO 2/2)

For PF1 and PI1 data

Master process chain : DAILY_PC_HIER_TXT

C-1) Load of L5 fields on Cost center (C_COSTCTR) BW master data : 

L5 update with PC_CT_LEVEL5_HIER_02 every days at 10:00pm cet time BUT following the BE Factory calendar, so the process chain is not running during Belgium public holidays.

For example for 2024 :

Data Quality Control

Data come from SAP system. To compare data between BW and sources systems, check propagation layers.

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