Each first of month, a close monitoring has to be done to validate completeness of stocks
Novecare (CS) is expecting an email confirming they can start their planning
Caution specific action if 1st of the month is a Saturday or a Sunday (see wiki)
To organize monitoring, this file is used and updated every month Planning Monitoring Monthly
...
- emails from DSCP_Solvay (sent ONLY when job issue)
- In case if a job running with error, open the log file joined to the mail and search for errors messages :
- Analyse the root cause of the error and communicate with DIP PP team and interface team to solve it
...
- Check all job status
...
Administrator / Macros / Shared macros
(normally must be executed by interface team)
...
Normally must be executed by interface team
...
In case there was an error during the automatic execute monthly task sequence only:
In DIP1
In DIP2
/!\ SILICA : For Silica, the update U00 → U02 is done every Sunday. When the first day of the month is on a Saturday or a Sunday, BW files are created and updated in DIP only the following Monday (because of issues in the file generation). So in this case, the update U00 → U02 needs to be manually launched, and then a full loop has to be run.
...
Open some views (example DRP views) and check the change of month
DSCP1 - workspace P3M || EU SAD SODA => current month has to be in blank color
...
Check data consistency of the most important data :
I500 - Imported stock datas (day) > I500 Initial Inventory (MD04 +MB5B for movements)
=>For SILICA => Homologated inventory
plant 7528 in SI DIP = plant 7525 in SAP
I402 End of month unrestricted Inventory (MB5B with last day of the previous month in date)
I402 - Actual Shipped at GI - site dim (MB51 from beginning to end of last month movement 601)
(Attention for Silica: in case of inconsistency, you might check the movements 633; because the movement is from shipped to consignment
...
For examples on 0278, 7525
I400 - Intransit inventory in receipt date (MB5T) : Attention, not to check the shipto for this datafield; only for intersites.
I400 Firm Shipment in shipping (MD04 customer order + Deliveries) : check the "MRP element"
I002 Final Forecast in ETD (DP side: User models/U99/Data tables/Export| BW/DIP-PP - Material:Shipto@DC/ Final Forecast ETD)
I500 Blocked stock (MMBE : Blocked Stock + Blocked Stock Returns)
You need to compare with SAP or DP data to be sure that everything is ok.
...
Select some key products (most produced, most sold, basic products) and check some indicators coherence like
Arithmetical inventory
Shipping plan vs Shipping requirements,
Global Balance reports
...
Check the Transit inventory SILICA => We must have data for the previous month
Compare results between the 2 parameters as well as the total quantity on M-1 of the parameter I402 - End of month transit inventory SILICA, must be equal to the Sum of all quantities in transit of the paramter I400 Intransit inventory in receipt date
If there is some gap:
-Check in SAP (mb5t) if it match with Intransit inventory in receipt date
-For Silica, we take In transit inventory in receipt date that we archive on the last day of the month to plug it into the actuals. We do not take the U00 Actuals to display it in the Silica screens.
...
Check between SAP and Dynasys the Forecast exported
=> Take 3 SKUs PW as examples by BU
> Novecare : in DIP, Final Demand after netting (last validated) in CS model
!!! Please take examples from Sites where forecast export is activated!!!
!!! Please take examples when forecast is different from 1 month to another !!!
You can use this specific Grid view to help the monitoring.
In MD63, please fill the Plant/Material and the month to check.
> Special Chem: (in progress)
> TS:
- For Mining & Phosphorus : compare DP, Final Forecast in U99 and SAP MD63
- For PA : the Final forecast after netting and supersession is sent to DP and then from DP to SAP
Compare DIP Final demand ETD after netting and SAP MD63
...
Compare U99
Perox : 
/ SODA 
with SAP :
We export to SAP the current month + 3 months
For DIP3:
...
Before starting the checks, be sure that the dynamic import is finished.
If not → wait until it end
...
#2
...
Check that the boxes are ticked for all the sites except those not selected in the filter of the "Novecare - Distribution additional data | Cancel Order Book activation"
...
Find a SKUs as example and check the following data:
- Initial inventory = between DIP and SAP (MB5B)
- Firm independent requirement= between DIP and SAP (MD04)
- Firm planned order = between DIP and SAP (MD04)
- Intransit = between DIP and SAP (MD04)
- Forecast = between DP and DIP (Final Forecast ETD) (ex of DFU: 98673R@55099R)
- External purchase from SAP = between DIP and SAP (MD04)
- Firm receipt ETA = between DIP and SAP (MD04)
Check the projected inventory calculated by the DRP is correct
Check that the final demand after netting seems ok.
Check that export to QV batch has run without error (SBS technical view)
...
Check between SAP and Dynasys the Forecast exported
=> Take 3 SKUs PW as examples by BU
> Novecare : in DIP, Final Demand after netting (last validated) in CS model
!!! Please take examples from Sites where forecast export is activated!!!
!!! Please take examples when forecast is different from 1 month to another !!!
You can use this specific Grid view to help the monitoring.
In MD63, please fill the Plant/Material and the month to check.
...
Send an email to the DIP3 users
to: "$DynaSysUsersDiP3 (Novecare)"
<DynasysUsersDiP3@solvay.com>
Dear All,
The monthly update is done. You can now connect into DIP.
SAP data will not be updated until the end of the netting process on the 6th of the current month. → Verify the date each month !
Next SAP data update takes place after S&OP validation on the 11th of the current month. → Verify the date each month !
The remaining SAP data updates will take place every Saturday until the end of the current month.
Regards.
...
Check if the archiving is done correctly
Z800 should be equal to S&OP Validation of Month M for M+1
...