How to check why a Material is not in DynaSys ?
Material import in Dynasys

Check if the material is in the BW file: DYS_BW_Material
If yes: Ask to the interface team to run a static batch week end
N.B: Material is created only every week at the week end
If no: you'll have to raise a ticket to BW team
How to check why a Sales Employee is not consistent with the Sales Group in SAP WP1 ?
Sales rep import from SAP to Dynasys

Extract the sales employee and the sales employe ID of the DFU and compare the Sales group/account manager in SAP
1- If there are not the sames, we need to check if there is a sales employee override :
Create a view using all data fields from the Material@Shipto@DC level |Sales Employee data table in the Master Table Updates user model. Pay special attention to the Sales Employee data field and the Sales Employee Override data field.
2- If there are the sames, 2 options:
Material does not display the right name
example:
https://sbs-support.solvay.com/a/tickets/5816109
In Dynasys, for each Item, we have description (sap name) and short description
the short description of shipto is: first 2 words of the SAP name + city name + country code
You could choose between the description or the short description with the filter
![]()
Choose name or short name
![]()
Click on the data field
Open dependency view
Click on utilization
Find the "IN" data field and click on it
Click on the menu Link up
Right click on the line with 2.05. > DISPLAY text

CH process:
Ticket related:
https://sbs-support.solvay.com/a/tickets/5963823
Golden rules for supersession:
- set supersession from 1 DFU to 1 DFU
- set supersession from N DFUs to 1 DFU
- NO supersession from 1 DFU to N DFUs
First step:
You need to check the datas field Substituted reference and Substituted reference final from the user model Supersession
![]()
Substituted item= Old DFU
Material:Shipto@DC= New DFU

In this example, it means that The "Substituted Reference Final" data field is the final output which is taken into account to apply supersession in data fields.
Second step:
You need to check if there was an issue with the supersession by checking the data filed: Wrong supersession 1 old to multiple New
![]()
In this example, we can see the the data field it is ticked and also that there was a supersession from 1 DFU to N DFUs.
However, it is not the best pratice.
In that case, the user needs to cancel the supersessions with the workspace Life cycle and uniticked the data field Substituted reference:
After 1 day, the user can do another supersession
Novecare process
Use the workspace Life cycle
Go to the grid view List of supersession

