General presentation

Objective of the application

This application allows 4 kinds of data reporting : 

• Reports on the inventory levels (quantity / value) at a given time
• Reports on the material movements (simple ones)
• Reports on the unit prices used for the material valuations
• Reports that mix several of those 3 first sources (Ex : Turnover calculations with needs both inventory level and material issue movements)

Tool Leader + IT leader of the application: Functionally this application is shared between Indus/RTR/OTC/PtP, but it's overall the owner is PtP. Current Reporting Coordinator is Duarte Costa.

Usage information

The tool is used by several types and areas of users :

• Financial controllers (values)
• Supply chain (Quantities, movements)
• Warehouse managers (Quantities)
• Maintenance (Industrial suppliers levels)

Used worldwide by hundreds of users.

Only has RCS data.

History

Created before 2006. No significant changes since on the dataflow.

Roles & Access

Roles and access

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

Authorization objects

List of autorisation objects mandatory for the application.

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/0BwM8zQWmqesDflp5VjlGME5WR2RGOWNfalpsOFRSSDZZRmUtUWJTdk5nUEYyR1BUdHhfNUU

Exemple of dataflow overview :

Template Application name DataFlow

Functional and Technical rules on Workbench + Reporting

Rules & Explanations

Detail of main topics with explanations of the rules and only the main + special rules about queries to run and use in the correct way

Dependencies with other applications

The stocks application is very linked to the PP Production planning --> The PP application also uses the MPR_IC001 cube.

For queries in that cube, the distinction between what goes to PP and what goes to IM is :

• If the query uses the CUB_PP01 or CUB_PP02 data --> PP Query
• If the query uses the material movements values/quantites and TRANSLATES them into categories like "production, consumption..." then it's PP. If it's only value/quantity then IM.

Data loadings

Info providers and objects loaded

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

Loading frequency

Follows the D4 frequently loaded data schedule. 

Average performance

if possible, give some information on average process chain duration, amount of data loaded and total data volume example: daily process chain loaded in 30 min, weekly chain loaded in 1h15, with around 2k to 10k lines in DELTA mode for a total of 10M lines in cube. The purpose is to give a general overview of the volume of data managed y the application

Record Keeping

All history MUST be kept : the stocks level queries are all using cumulative key figures so it's necessary to keep all documents.

Reporting

Queries End User Documentation

See documentation in the public wiki : IM - Stocks (WBP)

Main queries

See list of queries in the public wiki documentation :

IM - Stocks (WBP)

Main functionalities

Give detail on all complex functionalities: list most important and/or complex KPI, query jump, alerts

Broadcast

Indicate if there are broadcasts and give some details on the broadcast settings.

Maintenance

Known bugs

In the past we had sometimes issues on the 1st of January each year due to a few documents not being correctly loaded in the delta. 

Note that the stock level cube (CUB_IC001) is VERY sensitive to loading errors : if a document is missing on day D, it will affect ALL the results after day D since all the key figures are cumulative.

Recurring procedure

List recurring procedures

Planned Evolution

As of 25/07/2016 there is no consolidated stock application with all ERPs, but Anon, Kasemvilas is working on adding the PF1 data.