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).
Before starting P&I in DynaSys, it's important to define the scope of the user, the 12 months 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)":

Action:

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:

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
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.