This application is separated from Working Capital application (required to be in a separate role menu)
|
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.
|
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
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.
This application was created in 2018, requested by Technology Solution.
cf. BW RTR - IM from FIGL at Integrated Costs (WBP)
cf. BW RTR - Logistic Inventory at Integrated Cost
We should have the information where the application is sending or receiving information (e.g. APD open hub)
Detail of process chain, list + link between or special event done for the loading
| Main Process Chain | Final Provider Loading | Frequency | Time start | Duration |
|---|---|---|---|---|
<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.>