a. Data fields and Calculations in Dynasys
The Final forecast is elaborated though several successive calculations
Example of TS :
b. Forecast export to SAP
Files for SAP are generated at different frequencies and time slots, depending on the GBU.
MFT is in charge of catching files from Dynasys server.
| Instance | GBU | Frequency | Job | Approximative Running time (CET) | Data exported | How |
| DIP1 | TS | Every 1st and 6th of the month | Dscp DIP1 Daily BW export (at the end of the dynamic) | 8am CET | Final forecast ETD | through MFT |
| DIP1 | TS | Every Sunday | Dscp DIP1 Weekly | midday | Final forecast ETD | through MFT |
| DP2 | Composite | Manual flag in DSCP (mid month) + Every weekday Every Saturday Every Sunday | Dscp DP2 Daily Dynamic Dscp DP2 Daily Static Dscp DP2 Sunday | 6.30am 4.30am 4.30am | Final forecast | through MFT |
| DIP3 | Novecare | Every Saturday | Dscp DIP3 Saturday | 8am | Forecast after netting | through MFT |
| O&G | Every Saturday | Dscp DIP3 Saturday | 8am | Final forecast ETD | through MFT | |
| Novecare | Every Sunday | Dscp DiP3 Sunday | 1pm | Planned orders, target stock | through MFT |
c. Import in SAP
Transaction code ZWPP_PIR_UPLOAD( program: ZWPMR0001C) is using to upload the forecast from Dynasys to SAP, there are jobs scheduled in SAP by weekly or monthly to do this uploading automatically in WP2.
After MRP run, SAP will generate planned independent requirements for planning or Long term Planning.
Procedure to be used for WP2 :
DynaSys DP - Export Independent Requirement
Each GBU have a specific job, scheduled in SAP. Below the jobs available in WP2:
| System | GBU | Frequency | Job | Running time(CET) |
| WP2 | Composite | monthly-every 18th | PP_RCS_FC_UPLD_CM_WW (variantes CM_WW_00 + CM_WW_04) | 0:10 |
| WP2 | TS | monthly-every 1st and 6th | PP_RCS_FC_UPLD_TSMONTHLY_WW_1ST (variante TS_WW_00) Caution job PP_RCS_FC_UPLD_TSNVMNTH_WW (variante variant TS_NV_00) is still planned every 6 of the month, uploading a file not updated since 06.09.2023 at 8am =>DYN_FC_EXP_TS_NV_00.CSV => must be an error when NV + EW were replaced by WW | 9:00 PM CET |
| WP2 | TS | every Sunday | RCS_PP_FC_UPLD_TSWK_WW (variante TS_WW_00) | 4:00 PM CET |
| WP2 | Novecare | every Saturday | RCS_PP_FC_UPLD_NVWK_WW (variante CS_WW_00) | 6:00 PM CET |
| WP2 | OG | every Saturday | RCS_PP_FC_UPLD_OGWK_WW (variante OG_WW_00) | 6:00 PM CET |
d. Manual output the forecast from Dynasys to SAP
1> Login the backend server as an administrator, and manual trigger the Macro (ensure there is no background running), take Special chem as an example:
After the Macro done, go to the folder \DynaSys\ITF\Files\Out\FCST\WP2 on the backend server to check if the CSV file was generated correctly.
The CSV under folder WP2 will get transferred to SAP and meanwhile this file will be copied to folder BKUP after 5 minutes, If there is any problem for the MFT Jobs please contact the MFT team
2> check the CSV file in SAP
Use AL11 and go to Directory: /exploit/PP/data/DYN/FCST, you can see the file size and what time it got generated.
Be noted, the MFT will only work for the production environments, if we need to some tests in the background run from server, in WQ2 we can upload by program ZWFAU01000.
double click the file to see if it can be opened.
3> Launch transaction ZWPP_PIR_UPLOAD, select the correct variant:
4> Execute the program, there will be a loading log after complete the loading, and two log files also will send to the users if they have maintained the email address in ZDP_EMAIL_PIR( this function now only in WP2).
e. Verify the forecast in SAP
Check the import through SQ00 1/3
Check the import through SQ00 2/3
Check the import through SQ00 3/3
f. Forecast Individually checking
( Indépendant requirement is the result of the netting in dynasys)
Dynasys S&OP Planning and Interface.
Please don't use MD04 to check the forecast, the data shows in MD04 is deducted by the sales order allocation.
You can use MD63 to check the full loaded forecast from Dynasys.
| # | Description | Screenshot |
|---|---|---|
| 1 | Forecast from plant 0294 material 143509 (WP2) |
|
| 2 | same with the import file Use SAP transaction code AL11 go to Directory: /exploit/PP/data/DYN/FCST, you can see the file size and what time it got generated. | *Directory: /exploit/PP/data/DYN/FCST
|
| 3 | In Dynasys shipments requirements: | |
To check the Qty from DIP to DP was aligned. FCST export from DIP: | ||
| FCST export from DP: |
