SKU Shipto (Material@Shipto) Creation & Activation

DimensionHow to See
Source

SAP →  Dynasys DP → DynaSys DiP (for SAP shipto)

SFDC → Dynasys DP → DynaSys DiP (for Opportunities)

Conditions
  • DFUs must be existing & active in Dynasys DP (Active DFUs = TRUE). If it's active in DP, the SKU Shipto will be active in DiP (DP is the Master system for SKU Shipto's related information).

    Note 1 on "Active DFUs" in DP : the Demand Planner has the capability of defining which DFU are Active or not in DynaSys DP (pre-requisite: the DFU must exist in DynaSys DP, see below).

    Note 2 on existing DFU in DP: for a DFU to exist in DP, there must be an at least one Sales Orders created in SAP. The DFU can also be created 'manually' in the tool by the Demand Planner in case of need (prerequisite for manual creation): Material and Ship-to need to exist in the tool to create new DFU.
FrequencyFrom Dynasys DP to DynaSys DiP, it takes 1 day to be available in DynaSys DiP
Trouble-shooting
  1. If user don't see SKU Shipto in DynaSys DiP => check if it exists & is active in Dynasys DP.
  2. If it doesn't exist in Dynasys DP, reason could be that there is no Sales Order in SAP => user can create it manually in Dynasys DP.
  3. If Material & Shipto is missing when creating it manually, please raise ticket to SBS team to add the new material/shipto into Dynasys DP. Then, manually create the DFU in Dynasys DP, wait 1 day to see it in DynaSys DiP.


When a new ship-to is created in SAP, it will be available at Day+2 in Dynasys, as soon as there is an associated sales order.

When a new material is created in SAP with Basic View/MRP View/Costing Accounting View, the new materials are updated once a week in Dynasys (on Saturday).

*By default, we do not create a new ship-to/client or material, except if there is a sales order associated to it.



The Activation/deactivation of SKU Shipto in DiP-PP is managed from DP


MSS of SKU Shipto

The Main shipping site defined in DP for each DFU is sent and available in DiP-PP to help construct the network


Supersessed SKU shipto (Material@Shipto)

The “Supersessed” status of the DFUs in DP (i.e., indicative if the DFUs is part or not of a Supersession) is also sent to DiP-PP to define the supersessed SKU Ship-to’s => important to keep the consistency between the two systems as to which references (which “Material@Shipto”)  are active in terms of planning or not.


No print screen is available for now, Interface/Evolution on going...


BFC BU / Market from DP


BFC BU/Market are notions that makes sense only at DFU (Material:Shipto@DC) level, so in DP application.

DiP expected granularity is Material:Shipto (SKU Shipto).

As normally, for 1 Material:Shipto we have only 1 BFC BU or BFC Market, aggregation those notions from Material:Shipto@DC to Material:Shipto is OK. However, there might be some cases (few cases) where for one Material:Shipto we have can have multiple BFC Market or BFC BU. For thoses cases, we take the BFC Market or BFC BU with highest Gross History and Final Forecast.


In DP:

These are the 2 datafield exported:



In DiP:


They are imported into these 2 datafields:



Note: since this data is coming from DP, it's only available at Material:Shipto (SKU Shipto). Any attemp to have it at SKU P/W will need a kind of (complex) calculation to aggregate it.

During P&I project, in order to facilitate navigation in P&I tool, we had implemented a calculation that is able to calculate the "BFC Market" also for level 1 of network (SKU @ Solvay Site that ship directly to end customers), by doing a transposition of original data (at Material x Shipto). Note: This "BFC Market for P&I" will not be considered in DiP module or other tools like BW or QV. More information here: 12. BFC Market