List of application role + menu role and explanation if we have several applications role with specials rules.
|
List of authorization objects mandatory for the application.
Link to the BW Catalog of role https://drive.google.com/open?id=10GEfKYqrT1eeTO_uHYAheL1GX7L5y_pvH0KQU64qh5I |
Reporting documentation drive folder:
BW folder : https://drive.google.com/drive/folders/15FU8y_yH5SZGRnDAjyRWUeYrbsUrixET
Dataflow :
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.
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
This application was created in 2018, requested by Technology Solution.
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:
BW_QRY_MVFIWC05_0001: Inventory report at integrated costs (Core Query)
Conversion of currrency is using the conversion type CTK_ZRH2EM (Exchange rate ZRH2 with time ref = End of month )
Conversion of unit is done using the conversion type QCT_CMATNR (using T006 if available otherwise C_MATNR).
=> as the conversion is base don c_matnr and no c_matnr2, the conversion DSO is not the same: UOMC_MAT instead of UOMCMAT2 => VKG and VTN conversions are not generated as it is in DSO UOMCMAT2.
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.
We should have the information where the application is sending or receiving information (e.g. APD open hub)
Main Process Chain | Final Provider Loading | Frequency | Time start | Duration |
|---|---|---|---|---|
PC_COPA_PL_39 IM: TD Unit Costs | ODS_PCP9 & CRCOPA24 | Daily | 4 am | 2 mins |
FI_IC_DELTA_EXTR_HOURLY 03b IC Minimun Transactional | CUB_IC01 | Daily not weekend | 12:20 pm 6: 20 pm | 10 mins |
RCP_MMIC 03a IC Complete Transactional | CUB_IC01 | Daily | 6:25 am | 5 mins |
Data come from SAP system. To compare data between BW and sources systems, check propagation layers.
<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)>
<Describe the scheduling in place for the application (eg. existing jobs, trigger time/event based, dependencies)>
<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)>
<Describe how to handle errors (eg. error codes, description and respective resolution, alert users)>
<List the existing bugs, its criticity, workarounds and resolution plan.>
<List past & future evolutions for the application (including links to MED/FSD/TSD)>