You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Next »


General Knowledge : Interface management

Administration tab / macros


Administration tab / scenarios


Interface Management

Structure tab

Hierarchy (Master data or Static Data) →


Dynamic Data →



Troubleshooting → Alert emails

Alert mails:

Google group for problems in DP1 / DP3 : $Batch DynaSys alert DP pour les alertes DP : (email :batch.dynasys.alert@solvay.com)

Google group for problems in DiP1 or DiP2: $batch.dynasys.alert.DiP  (email : batch.dynasys.alert.DiP@solvay.com)


Interface management

How to add manually one Material in DynaSys?

https://docs.google.com/presentation/d/1S8hDXr3SH9MGzHQuVfJidPb-bp3zgVZRgml03ntpvtI/edit 

How to add manually one Ship-to in DynaSys?

https://docs.google.com/presentation/d/1XoNDT0IfqtG2UlwRRL6r_Cn0U7wm63nMnW4emOxcpMY/edit 

How to import a CSV file for mass upload?


Learning > Level 1 DP vs Level 1 DiP


To transfer data from DP to DiP, since we have different levels of granularity, we need see first if we are talking about Master data or volumes:

In DP,  DFU = Material : Shipto @ DC

In DiP, SKU Shipto = Material @ Shipto

1>To transfer volumes (FF, Budget,...): we need to aggregate the volumes from DFU to SKU but it’s not complex, no need to define a rule on how to aggregate volumes (i.e., it’s straightforward)

2> To transfer the Master Data

  • In WP1, Need to define a rule of aggregation from level 1 to level 2

In case of several DCs, the rule is to take the most recurrent. For ex, for ABC Classification, we could take the most recurrent classification 

  • In PF1, ok. Since for Perox the DC = BU, no need to define a rule






  • No labels