General presentation

Objective of the application

This application extract the forecasts from the application APO. The data is loaded and aggregated in BW and made accessible through a multiprovider which regroups data from three application. APO, Dynasys and Logility. In time, application Logility will be terminated and the data coming from APO should be integrated in Dynasys.

Tool Leader + IT leader of the application: Celia Gonzales

Usage information

History

Golive In May 2017

Roles & Access

Roles and access

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

This should be the same as what's done for Dynasys.

Authorization objects

List of autorisation objects mandatory for the application.

This should be the same as what's done for Dynasys.

Dataflow overview

Reporting documentation drive folder:

https://drive.google.com/open?id=0BxkySrtHryoBeG05a0ljVWJpSmM

Functional and Technical rules on Workbench + Reporting

Rules & Explanations

1 : Cleaning of incoming data before propagation datastore objects

C_MATNR2: adjust the format of the material number to the right number of digit, adding/removing zeros in the process.

0LOGSYS : Determination of system source

2 : Determination of previous period for C_FCSTMTH when loading the snapshots

It's usually the previous month. It can however be fixed to a specific value through the use of filters in masterdata C_GLBFILT

3 : Loading of attributes from MD for all DSOs

• CPFCTR1_2 is retrieved from the corresponding attribute of C_MATPNT2.

C_MATPNT2 is determined through the coupling of material and plant and is used for business assignments (ERP or BFC). It contains multiple attributes mainly loaded through either the standard attributes from datasource 0mat_plant and the MD C_SUBACT2 (a mix of Profit center (WP1) and Business area (PF1, PI1 and RHO systems)).

• C_CUSTGRP is retrieved from the corresponding attribute of C_CUSTENT.
• C_COMPCODE is retrieved from the corresponding attribute of C_MPPLANT.
• C_SAL_OFF and C_DOCTYP2 have been initialised with value APO.

4 : Loading of attributes from MD for loading coming from RCS (Every DSO except the two for Special Chemicals)

• 0DIVISION is retrieved from the corresponding attribute of C_MATNR2.
• 0G_CWWE01 is retrieved from the corresponding attribute of C_CDSA

C_CDSA contains the distribution channel coupled with division. The IECRA can also be found in C_MATPNT2, but it's value is wrong.

5 : Loading of attributes from MD for loading coming from SOLVAY (Only the DSO for Special Chemicals)

• C_MAT_GRP is retrieved from the corresponding attribute of C_MATNR2.
• C_SHTCTRY is retrieved from the corresponding attribute of C_SHIPTID.
• 0G_CWWE01 is retrieved from the corresponding attribute of C_MATPNT2.

IECRA is specified in this dataflow as an information but is not reliable. IECRA is not an organizational structure used in Solvay.

• C_PROD is retrieved from the corresponding attribute of C_MATNR2.

6 : Keyfigures in summation when loading the business datastore objects

Data in APO can't really be aggregated in a DSO as every characteristic is key. This means that the semantic keys which were determined for the propagation level is not absolute. Since the DSO are in write optimized, there is no loss of data thanks to the techical keys. 

This is only true for the datastore with a RCS source, which is every datasource except for source Solvay Specialty Chemicals. This is because data in RCS is retrieved down to the week while in Solvay records are already in the targeted month detail.

7 : Determination of C_FLGMTH for dynamic dataflow

We are always loading data for current month M

8 : Determination of C_FLGMTH for snapshot dataflow

The month view is determined depending on the difference between the period 0CALMONTH of the forecast and the considered period C_FCSTMTH.

IF 0CALMONTH = C_FCSTMTH THEN C_FLGMTH = M

ELSE IF 0CALMONTH > C_FCSTMTH THEN C_FLGMTH = M-2, M-3,...

ELSE C_FLGMTH = N/A

9 : Determination of GH quantity and bias for snapshot dataflow

For each snapshot loaded in a business datastore object, we rework the entire datastore object. We update the Gross History quantity for past snapshots using the latest GH quantity depending on the keys of the DSO.

There is 3 bias which are calculated:

• The bias for the final forecast is calculated through the following:  ABS ( FF Quantity - GH quantity).
• The bias for the sales team forecast is calculated through the following:  ABS ( STF Quantity - GH quantity).
• The bias of the statistical forecast is calculated through the following:  ABS ( STATF Quantity - GH quantity).

Dependencies with other applications

This dataflow is using the same multiprovider than the dataflow for dynasys. Therefore when modifying multiprovider MVDYN11, beware of the impacts.

The loading of the snapshot part is done on the same day than dynasys.

Data loadings

Info providers and objects loaded

There is a high volume of data for the snapshot dataflow, which is why a clean-up was established during the loading in the PC. We keep only 36 months of history. The deletion process is done on every layer.

As the snapshot and dynamic dataflow use the same source, a decision tree was used to stop one loading if the other is already on-going.

Loading frequency

There is two master PC:

• The loading of the dynamic data is done twice a day
• The loading of the snapshot data is done on the 6th of each month

Average performance

Record Keeping

36 Months of history

Reporting

Queries End User Documentation

See Query definition under Dynasys.

Main queries

Main functionalities

Broadcast

Maintenance

Known bugs

Recurring procedure

Planned Evolution