| Table of Contents |
|---|
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
History
This application was created in 2018, requested by Technology Solution.
Roles & Access
Roles and access
|
Access Management
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
List of application role + menu role and explanation if we have several applications role with specials rules. |
...
|
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
List of authorization objects mandatory for the application.
Link to the BW Catalog of role https://drive.google.com/open?id=10GEfKYqrT1eeTO_uHYAheL1GX7L5y_pvH0KQU64qh5I |
...
Dataflow
Overview
| Embedded Google Drive File | ||||||
|---|---|---|---|---|---|---|
|
Same authorization as Working Capital application, except the WC account type, which is only "INVENTORY" for this application. Moreover, as we needed the cube Material Stock (CUB_IC001) for Logistic Inventory at Integrated Cost report, and this cube doesn't contain the PRS company code, then the perimeter role on 0company is also required.
...
Reporting documentation drive folder:
BW folder : https://drive.google.com/drive/folders/10E2KpooKYimueCVIYp15FU8y_T22FgekLM269-yH5SZGRnDAjyRWUeYrbsUrixET
Dataflow :
Functional and Technical rules on Workbench + Reporting
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
History
This application was created in 2018, requested by Technology Solution.
Technical Rules on Workbench
...
The solution is a multiprovider between Material stock WP1 cube and IM Cost unit cube.
Reporting
.
Material stock - CUB_IC001: not complex rules in DSO associated.
- Transformation: ODS_IC02 -> CUB_IC001: "stock" key figure are defined to 0.
IM - Unit Costs - CRCOPA24:
- ODS_PCP4 transformations explanations here: IM - Transformations rules
- ODS_PCP9
- TRSF: ODSO ODS_PCP4 -> ODSO ODS_PCP9
- Start routine: define logsys with module function Z_WBW_SOURCE_SYSTEM for RCS landscape. + load in internal table master data c_plant (fields logsys, plant, c_authma, c_compcde).
- Field routine: Define logsys.
- End routine: Read internal table plant to define C_AUTHMA, C_COMPCDE and COMP_CODE.
- TRSF: ODSO ODS_PCP4 -> ODSO ODS_PCP9
Reporting
...
Main queries
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.
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.
Broadcast
No Broadcast
Maintenance
Known bugs
Recurring procedure
...
Dependencies with other applications
We should have the information where the application is sending or receiving information (e.g. APD open hub)
Data loadings
Info providers and objects loaded
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 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)>