Access Management 


List of application role + menu role  and explanation if we have several applications role with specials rules.

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)



List of authorization objects mandatory for the application.

Authorization objectExplanation
0COMP_CODE__C_AUTHMAZR_*_CA_P00
CPFCTR1_2ZR_*_CA_P05
0COMP_CODEZR_*_CA_P01

Link to the BW Catalog of role

https://drive.google.com/open?id=10GEfKYqrT1eeTO_uHYAheL1GX7L5y_pvH0KQU64qh5I


Dataflow overview



Reporting documentation drive folder:

BW folder : https://drive.google.com/drive/folders/10E2KpooKYimueCVIYp_T22FgekLM269-

Dataflow :


General presentation

Objective of the application

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

The general idea is to have a report similar to "Inventory aging report “ (BW_QRY_MPR_IC001_0001)  but has quantities valuated at IM unit cost.

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

Usage information

How many users? Which user category ? Is there critical period ? Which geographical perimeter? Describe in one sentence: around 50 users, worldwide or 200 users / European Site

History

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



Functional and Technical rules on Workbench + Reporting

Rules & Explanations


The solution is a multiprovider between Material stock WP1 cube and IM Cost unit cube.


Material stock - CUB_IC001: not complex rules in DSO associated.

IM - Unit Costs - CRCOPA24: 



Reporting

Queries End User Documentation

Query end user documentation should be created in the public "Customer Support Wiki" space under the corresponding BW application page : BW - Application. Technical query query documentation, if necessary should be added as a sub-page of this documentation using the BW Technical Query Documentation template.


Main queries

Main functionalities

No exception aggregation is used to valuate the quantities, so it is important to keep the characteristics Plant and Material in the queries in order to be able to valuate the stock 

Constant Selection on infoprovider "CRCOPA24" is set on IM cost unit key figures in order to ignore selections on characteristics that are not in the IM cost unit infoprovider.



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