0.0 - Process


The P&I in DynaSys will be structured as follows :




Note: because of functional & technical constraints, we recommend DynaSys to provide a report of the approved outputs (SHS, SHS RLT, Catalog LT, batch size). This report can be used later by the responsible GBU team (Data Admin, Site Planner,...) to double check and perform the update manually on SAP.

This will avoid any unwanted surprise in SAP operational part and other projects (like CEM).


0.1 - Set-up


Before starting P&I in DynaSys, it's important to define the scope of the user, the 12 months in the past used as reference for Decision tree & Val Class calculation and the Baseline month (used as reference, against which we will calculate the WC savings).


This is done in the following Workspace: "PI - 0. Set-up (scope / baseline / ref months)":



  1. Definition of scope / Baseline month / Past 12 referent months:


Action: 

  1. Define the site for each user (need to wait 1 day to be effective)
  2. Define the Baseline month for that site. In the example below, we defined December 2020 as the Baseline (M12-2020).
  3. Define the Past 12 months used as reference for P&I calculations. This will help 'freeze' the time horizon used for Decision tree & Valuation Class for P&I calculation.
    Example: If we are doing the P&I exercice in April 2021, we might define April 2020 through Mars 2021 as the 12 referent months.






Note:  by default, we don't display all the Sites. In order to see them, User has to untick the option "Hide rows with default values"


WARNING: Here you will define a scope by plant and then you will be able to see all the Active SKUs in DIP assigned to this site. The Active SKUs are defined by the S&OP Planner on the Data Management Workspaces so if some SKUs are not viewable please check with him if it is not deactivated (nb: to reactivate a SKU, the S&OP Planner need to do a modification in DIP and then it will be active in D+1). 





Note: the scope definition can also be accesible at any time from the shortcut below:


More details on Baseline


How?

> This will part of the global settings, user needs to tick the ‘Baseline month’.

> Defined by site. In the example, Dec 2020 is the Baseline site por P&I calculations


Impact?

>This Baseline will be used as referent when calculating the Working Capital Impact and the DIOH


More details on Past months choice


How?

> This will part of the global settings, the user needs to tick 12 months accurately in the ‘Past months choice’.

If you tick 11 or 13 the calculation afterwards will then be wrong as it meant to be 12 months. 

Impact?

>These 12 "Past months choice" will be used as reference for the P&I calculations with the following data:


0.2 - Launch Manual Import of Dynamic (transactional) data


In the previous step, when we defined the 12 referent months, we help 'freeze' the past months taken into account for P&I calculation. However, P&I calculations also take into consideration future months (for example: when calculation the Valuation Class for P&I for new FG or new RM, we need to consider Future Demand as well).

In order to ensure that any change in Future volumes (or also past volumes) does not change any P&I calculation, we need to manually run an 'Dynamic data update'.


Impact: it will update in one shot Past volumes (considering the 12 referent months) + Future volumes on the user's scope (ex: if user's scope is Mexico Natie, it will only refresh Mexico Natie's past & future volumes).

How to: using the Shortcut below '2. Dynamic data update'



This will copy & freeze all the transactional data/volumes input (Past Demand, Future Demand, Past Consumption, etc...), so that P&I outputs like "Proposed SHS", "Proposed Valuation Class P&I" etc do not change during P&I Exercice


Other data from SAP are updated every day in Dynasys.


The other 2 shortcuts: "3- Validation & Archiving" or "4 - Information" will be used later in the process. However, "4- Information" can provide a report with the most important inputs for P&I exercice.