Access Management 

See Technical Documentation - CAPEX Analysis report

DataFlow

Overview

Use the google presentation below as a template. This google presentation must be saved in the Reporting GDrive folder under the corresponding application. Then post the link to the document here.

Reporting documentation drive folder:

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

Exemple of dataflow overview  :

Template Application name DataFlow

Technical Rules on Workbench

These flows contain all the FI-GL data used for the calculation of the CAPEX FI key figures (Key figures "FI Detailed posting" and "FI CX accounts"):

• FI CX accounts: WP1/PF1 entries in Loc. curr. on GL accounts linked to CAPEX BFC Accounts (Cf. SAP sets ZFC-A20600, ZFC-A20500…)
• FI Detailed posting : as some CAPEX accounts are only booked during month-end closing and with very few informations in postings, when possible, we can also use some corresponding postings but with more details.

Dataflow:

https://drive.google.com/file/d/1KbKFyErE_FyUktQ8c0rkQPgQNn_fBw_LGtzo6NTIj1w/view

CAPEX FI-GL CICC Factoring data flow

DTP: DPFIGL03 -> DBFIGL20 - Delta: Restricted to factoring companies (0231, 2232, 4044, 6440, WARP) + semantic groupe on LOGSYS, /BIC/C_COMPCDE, CHRT_ACCTS, GL_ACCOUNT, FISCVARNT, FISCPER, AC_DOC_NO and ITEM_NUM.

PRS Affiliate Company Code determination - Data Propagation Layer (DPFIGL03) updated from  DPFIWC03:

Update of existing entries in DPFIGL03 only (no creation of new lines) with the Affiliate PRS company code in DPFIWC03 (Data from ZZF_BSEG CICC table).

An error stack is updated if the line item in DPFIWC03 can't be found in DPFIGL03 => no update in DPFIGL03 but the record is put into the error stack to be reprocessed during the next process chain's run

Affiliate data determination - Business Transformation Layer CICC (DPFIWC03 → DBFIGL20):

 Affiliate source system and Affiliate company code are derived from the PRS Affiliate company code determined in the Data propagation layer by reading Master Data PRS company code (C_COMPPRS) and Company code (C_COMPCDE) (it is done by the method get_aff_compcde_from_compprs of the class ZZF_CL_FACTORING_TOOLS).

If the Affiliate PRS company was determined but the landscape or the ERP Company code can't be determined, it should be due to inconsistencies in C_COMPPRS or C_COMPCDE Master Data => the line item is updated in DBFIGL20 but the record is put into the error stack and the DTP is set to "Update valid records, no reporting (request red)" mode to be warned if it occurs.

Today, every GL entry in CAPEX reporting from CICC is linked to Affiliate (even if the first entries had not the detail of the Affiliate). The actual solution consists to update new objects Affiliate source system and Affiliate company in objects C_LGSYSAF and C_COMPCAF but keeping existing objects in the DSO. However, if for future needs, if we have to differentiate some CICC entries from the ones to be followed by Affiliate, we should create 2 different flows and use the notion of "Legal" and "Affiliate" objects as it is done in "Factoring" AR and AP or in "by Affiliate" FIGL-AP and AR flows.

IFRS16 Changes

As part of IFRS16, there are new fields added to 0FI_GL_4 in the source system. The corresponding info objects are created in BW as well. In addition to that, added new navigational attributes to the cube and mapped the same in FI Multi provider. Technical details of the changes and info objects, DSOs, Cubes and Multi providers and given in the below section.

ECC Related Changes:

Enhanced 0FI_Gl_4 extractor in PF1 and WP1 with new fields ZZVERTN (Contract Number) , ZZVBEWA (RE Flow type) and ZZVALOBJ_ID ( Identifier of the Financial Valuation Object)

BW Related Changes:

Added RE Flow Type (C_VBEWA), Contract Number (C_VERTNR), Identifier of the Financial Valuation Object (C_VALOBJI) to DSOs ODSFIGL1/3 and DPFIGL02.

Added RE Flow Type (C_VBEWA) to ODSFIGL3, DPFIGL02, and DBFIGL16/17.

Added WBS Element (with System ID) (C_WBS_EL2), Contract (C_RECONTR) to DSOs DBFIGL18/19.

Added Contract (C_RECONTR), RE Flow Type (C_VBEWA) to Cubes - CRFIGL18/19.

Added C_ASSET2__C_RECONTR/__C_CONTRTY /__C_REVEND/__C_WBSE_TP as navigational in CRFIGL16/17.

Mapped all the newly added navigational attributes to the Multi provider MVFICX01.

Multi Provider Mappings:

Please find the attachment for multi provider mappings to MVFICX01 from FI cubes CRFIGL16/17/18/19.

As part of cut-over activity, we have adopted “FULL LOAD reloading from Jan 2019 to May 2019 at propagation layer DSOs from both the source systems PF1 as well as WP1“ to get the historical data for the newly added fields.

Reporting

Dependencies with other applications

We should have the information where the application is sending or receiving information (e.g. APD open hub) 

Data Loading

Info Providers and objects loaded 

Meta chain: PC_FIWC_01 - FIWC: TD - D - WISE 03.00 - Global (CICC / Acetow / Solvay)

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