General presentation

Objective of the application

The aim of this application is to give a P&L reporting adapted to Soda Ash GBU requirements.

It is based on the corporated P&L query and offered special axis and calculation for Soda Ash.

Specifications: https://drive.google.com/open?id=1Q-QjleNGzLF1tbhALtbjN0hdp9x9Y4zBrR2gURi3yw4

Owner : RtR reporting

IS RtR Reporting coordinator is Charlotte Rollier.

Usage information

History

The project was done in 2018.

Roles & Access

Roles and access

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

Authorization objects

Link to the BW Catalog of role

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

Dataflow overview

https://drive.google.com/open?id=1KvtTRYpRfKjRJNCx0sxGMGQVSe04ARE9V0OnVvd70uI

Reporting documentation drive folder:

https://drive.google.com/drive/folders/1D0RpGQ3rTMDh_7S0AvhWBRkcT-2buhfZ

Functional and Technical rules on Workbench + Reporting

Rules & Explanations

Why a dedicated flow for Soda Ash P&L?

To enhance the existing P&L flows with axis and calculations required by Soda Ash would have been more risky, more expensive and would have badly impacted corporate P&L flows complexity.

Extraction to Data propagation explanations:

Why a query as Infoprovider?

The flow could have been based directly on the multiprovider MVCOPA01, however, tests reveal it was a lot slower than to retrieve the data from a query. Moreover, it permits to retrieve some shared restricted key figures and to manage the quantity translation in the BeX query.

Query as Infoprovider - encountered issues

• The unit linked to the key figure "N8110 - Qty Sold - VKG" is always empty after the extraction => it seems that query as infprovider don't provide the unit for restricted key figures. The workaround was to use the unit of the key figure "Qty invoice - VKG" which is not restricted. Another possibility would have been to manage the VKG conversion in the flow and not in the query.
• It was necessary to add the detail material and unit in the infosource, else, the extraction dumped. It must be due to the fact that without this level of detail, different units are agregated. The dump occurs when the unit linked to the key figure "N8110 - Qty Sold - VKG" was not correctly filled, maybe the problem would not occur anymore at the moment the converted unit is in the key of the inforsource. 

Dependencies with other applications

Data loadings

Info providers and objects loaded

Loading frequency

Average performance

Record Keeping

Reporting

Queries End User Documentation

Main queries

Main functionalities

Broadcast

Maintenance

Known bugs

Recurring procedure

Planned Evolution