Response 4: 

Dans la vue “Where-used list by component” qu’on trouve dans l’onglet “3-DRP result”, on trouve la BOM de notre SKU “Rhodiastab 92 Bulk ZFR3 Melle”. ( vue du bas)

Ce SKU rentre dans la fabrication de “Rhodiastab 92/200 KG POLYETHYLEN DRUM” avec un coefficient de 1, donc notre Dependant requirement pour le bulk sera notre besoin en production du DRUM (“Proposed production plan”).

Maintenant on va aller voir le détail du plan de production pour comprendre d'où viennent les 57 200. Pour ce faire , on va sous l’onglet “5-Constrained Prod plan” on trouvera la vue “Novecare - Detailed Production Plan”. On va prendre le “parent product” “Rhodiastab 92/200 KG POLYETHYLEN DRUM”

Partant du mois de mai, on a 5200 en Available inventory qui est le résultat de l’available inventory du mois d’avril 6600 moins l’independent requirement de 1400. Pour le mois de juin le besoin est de 20 000 donc notre available inventory sera égal à 5200-20000 donc on aura un besoin qui se génère de 20000-5200=14 800. Le stock de sécurité pour le mois de juin est de 17 732 donc le besoin s’élève à 14800+17732=32 532 Kg. Donc, l’outil va nous proposer un “Production plan”. La quantité proposée est de 57200 et non pas de 32532 parce qu’on a une contrainte de lot présentée par la ligne “Production batch size [Kg]”  qui est égal à 28600 donc on peut produire qu’un multiple de ce chiffre.



Response 5:

The forecast is sent to SAP after the S&OP validation at around 10 of the month. After that we’re not in the frozen period and the data is moving which explains the difference between what we have today in DIP Netting and SAP. 

If we check what was sent to SAP after the last validation, we find in U01-Novecare Z800- S&OP reference datas-> independent requirement :

The sum of the independent requirements in July is 57397, which is the same value that we find in SAP by clicking in “element details” of ind req at 29.07.2022

In the view below, we find the independent requirement equal to 25397 because we have received two customer orders with the total of 32000 so that was deduced from the 57395 that we had before.


Response 9:

Concerning the material 319496, the DFU’s main shipping site is Santo Andre.The DFU is Defined in DP . The Mereville site is sourced by Santo Andre, so that is why The forecast is at the level of this site and not at the level of the Mereville site. That explains why you don’t see the forecast in the DIP Netting.The forecast is only for the SKU shipto and not for the shipping site. 

So, if we see at the Santo Andre level we have forecast for those shipto:

The result of the DRP shows that we have an independent requirement, but we don’t have the receipt plan because we have enough stocks to cover the demand and that is why at the level of Mereville Site we don’t have the shipping plan at the “Outbound flows” view.


It’s the same thing about the material 319518. Let us take the example of “Toll Contract Arndell Site”. The DRP result is as follow

So in this example, we have a proposed receipt plan because we don’t have enough stocks to cover the demand so if we see at the Merville site level which is sourced by Toll Contract Arndell we can see that we have a shipping plan as you found it in “Outbound Flows” View. It’s in Month of May because we have a lead time of two months.


Response 11:

1/ Check in DP in CH - A0 Master Data workspace if the SKU is correctly assigned to ZGL.

It’s the case, so in DIP check that the SKU is not assigned to the appropriate MSS and go to the Workspace CH - A2 SOP Planning, in the 0-Flow to correct change, on this view

Click configure->Selection and then filter by Active Sku | Spechem

And then search the SKU and override with the appropriate MSS.

2/ Check in DP side if the combination is deactivated:

In DIP side, in the workspace SOP demand netting search SKU’s related to the two combinations mentioned

Go to the SKU Management workspace, in the Activation/Deactivation sheet-> the CH - All Active SKUs configure the grid view and change filter to  Active Sku | Spechem and Active Site | Sepechem. And then search the site in the view and deactivate the SKU concerned.


Response 12 :


  1. Simulate user Rights 
  2. Locate the correspondent data field 
  • Open the users workspace
  • Go to the related tab 
  • Locate the datafield (Right click in Correction, then click in Locate Object )

        3. Make the modification in the Data Field and Save 

           4. Verify 

  • Open the view (Not the user's workspace)

              In Tools / Dependency view, click on Display type : Utilization (Link Up could work as well)

              Open a Grid View for the View

  • Check if annotations are enabled 


Response 13 : 

  • Ticket response :

<<The order number 645829 is M3 type of order. It is a template order which does not generate an orderbook entry.

In July there are three open orders for 14.000 kg each : 5636669, 5636670 and 5636671.

These are the orders that appear today in DynaSys for July.

The order 5636669 has been delivered on 27/07/2022. So this order is not anymore displayed in BW reporting.

The data table "Order-book to be issued (confirmed - ETD)" takes into account the "Goods Issue date" from SAP.>>


  • Response Analysis :

The order 645829 has been changed for the order 5636669. This modification for an order can be displayed in SAP transaction VA03.

The procedure consists in search the order 5636669 in VA03 transaction and then click in "display document flow" button : 


DynaSys takes into account the "Goods Issue Date" from SAP for the data field "Orders to be issued". Which is the data field that the user marks in his screenshot. 

In order to find the "Goods Issue Date" for an order, there is a specific search that must be done because this order is related to PF1 database, which as we know is different from WP1. The search procedure can be consulted in this link at "PF1 Specific Searches " heading : SAP TRANSACTION

The delivery date is displayed in SAP transaction VA03, tab Shipping : 




  • No labels