Page tree


Access Management 


Roles & Access

This application is separated from Working Capital application (required to be in a separate role menu)

Role CodeRole DescriptionExplanation
ZR_RCS_CA_M64IMWC - Inventory at Integrated CostRole menu
ZBI_RCS_FI_A36IMWC – Inventory at Integrated Cost - End User role

Application Role:

  • End User rights
  • gives access to infoproviders of Infoarea "IA_FMCO_FIWC_IM*"
  • BI Analysis Authorization "ZBI_IMWC" ("*" for authorization objects not relevant for the application)
Authorization Objects

Authorization objectExplanation
IM from FIGL at Integrated CostsC_SUBACT2__CPFCTR1_2ZR_*_CA_P05
IM from FIGL at Integrated CostsC_COMPCDE__C_COMPPRSZR_*_CA_P07
IM from FIGL at Integrated CostsC_COMPCDE__C_MNGAREAZR_*_CA_P08
IM from FIGL at Integrated CostsC_COMPCDE__C_AUTHMAZR_*_CA_P00

Logistic Inventory at Integrated Cost

0COMP_CODE__C_AUTHMAZR_*_CA_P00

Logistic Inventory at Integrated Cost

CPFCTR1_2ZR_*_CA_P05

Logistic Inventory at Integrated Cost

0COMP_CODEZR_*_CA_P01

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


General presentation

Objective of the application

The aim of this application is to provide inventories valuated with Integrated Margin cost unit (IMc)

The application owner is Rosario Sevilla
The reporting coordinator is Charlotte Rollier.

Usage information

History

This application was created in 2018, requested by Technology Solution.



Technical Rules on Workbench

IM from FIGL at Integrated Costs (WBP):

cf. IM from FIGL at Integrated Costs (WBP)

Logistic Inventory at Integrated Cost:

cf. Logistic Inventory at Integrated Cost

Reporting

Queries

QueryDescription
BW_QRY_MVFIWC04_0001 Inventory report at integrated costs (Core Query)
BW_QRY_MVFIWC04_0002Inventory report at integrated costs Monthly FX (Core Query)
BW_QRY_MVFIWC05_0001 Inventory Aging Report at Integrated Cost (Core Query)

Workbooks:


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 

Detail of process chain, list + link between or special event done for the loading



Main Process ChainFinal Provider LoadingFrequencyTime startDuration

IM from FIGL at Integrated Costs

PC_FIWC_09

Init Process Chain

DPFIGL08

Meta chain for PC_FIWC_07

On demand

IM from FIGL at Integrated Costs

PC_FIWC_10

Global Process Chain

Meta chain for PC_FIWC_07 & PC_FIWC_08

Event Z_EVT_IMWC triggered at the end of D4 Process Chain (complete PC only).


Daily, not weekend

Arround 7:15 am10 mins

IM from FIGL at Integrated Costs

PC_FIWC_07

FIWC: TD - D - Stock IM - Business To Reporting layer

DBFIGL23 / 24

CRFILG23 / 24

see PC_FIWC_10see PC_FIWC_10see PC_FIWC_10

IM from FIGL at Integrated Costs

PC_FIWC_08

FIWC: TD - D - Stock IM - Data Propagation layer

DPFIGL08

see PC_FIWC_10see PC_FIWC_10see PC_FIWC_10

Logistic Inventory at Integrated Cost

PC_COPA_PL_39

IM: TD Unit Costs

ODS_PCP9 & CRCOPA24

Daily4 am2 mins

Logistic Inventory at Integrated Cost

FI_IC_DELTA_EXTR_HOURLY

03b IC Minimun Transactional

CUB_IC01

Daily not weekend

12:20 pm

6: 20 pm

10 mins
Logistic Inventory at Integrated Cost

RCP_MMIC

03a IC Complete Transactional

CUB_IC01

Daily

6:25 am

5 mins

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

<List past & future evolutions for the application (including links to MED/FSD/TSD)>