1. User Management
Technical Documentation about User Management.
a. Exercises
- #1 - Please provide TS Pricing team new hire Ludmila Dupaka with DynaSys access.
- #2 - Can you provide access to DynaSys for Jeffrey Kolpa (jeffrey.kolpa@syensqo.com) to the DynaSys account of John Lampariello (Sales Rep code - 2RG). John has left Solvay and Jeff will be responsible to input the forecast numbers for his region until a replacement is found.
- #3 - Donwell Lawrence needs to have access to DynaSys placed on new laptop.
- #4 - Please give CN / LIU Zhiyun view/edit access to the following individuals in DynaSys.
CN / WANG Shan
CN / DING Paolo - #5 - Pourrais-tu donner accès à Arsène au module Dynasys Web ? Arsène va encoder ses prévisions de ventes dans l'outil.
Identifiant Solvay: DJAB7170
English Translation: Please give Arsene access to the DynaSys web module. Arsene will enter forecasts in the tool. Solvay ID: DJAB7170
- #9 - Please grant access to DynaSys DP in Edit mode to Mr Steven Shen for the same portfolio than Mr Qi Hongqiu.
- #10 - Could you please check the Web access for Dynasys DP as some of the Sales Rep cannot access to enter their forecasts (example Anna JAROSZEK) or Filiz DINIZ (CSR in Turkey).
- #11 - User Olga Pintor, need to have the same Dynasys access of Olga Duval.
- #12 - Please create DynaSys access for Caroline Trentin.
- #13 - Please create DynaSys access for Philipp Berg.
- #15 - I can't switch to S&OP Leader role for Europe. Could you please check? Thanks. - Felix Lessard
- #16 - I am the new S&OP planner replacing Fadila Benachich. Please provide identical access. - Julien Gena
b. Ticket References
| KT Users Management | GBU | Sub-Process |
| 1 | TS | User Creation |
| 2 | TS | User Creation |
| 3 | TS | Connection |
| 4 | TS | User Update |
| 10 | CS | Connection |
| 15 | CS | Switch User |
| 16 | CS | User Creation |
c. Steps to take
- #1 - Pricing Team is a specific role for GBU TS where users update the LC (local currency) and prices. Per default, all Pricing team users have access to the whole GBU (no scope condition).
- #2 - Here is a frequent case of turnover in the Commercial Team. We have different options to solve the situation depending on how it will be managed in SAP. The preferred option will be to assign the user group scope (of the person who left) to the user who will assures the transition. However, when the replacement is found, we should un-do our reassignment and create a new scope for the person hired (regular new user creation).
- #3 - First thing to check is the GBU and the role in order to know which type of access the user is using (remote or web). After that, you need to share with the user: the link of Prod. Portal (if remote) or the URL of Prod. data base (if web).
- #4 - The best practice would be to have no scope shared among several users. However, TS GBU is not following these rules due to their Commercial organization (and they are aware of blocking issues). In this case, we need to existing user group scope to an existing user. Beware on the way we do it: you need to identify the user and the different scopes.
- #5 - Here is a typic request of new user creation.
- #6 - Here is a typic request of new user creation. In addition, we need to make sure the new user has access to the workspaces listed above by using the security functionality.
- #7 - This request is referring to accessing workspaces which are handled through security by user role. We need to make sure the stated user has access to them and we have two ways of doing it. The first option is to check the security of workspace and assignment of user-user group. The second option is to simulate the user and verify the workspaces are accessible.
- #8 - The best practice would be to have no scope shared among several users. However, SD GBU is not following these rules due to their Commercial organization (and they are aware of blocking issues). In this case, we need to existing user group scope to an existing user. Beware on the way we do it: you need to identify the user and the different scopes.
- #9 - The best practice would be to have no scope shared among several users. CH GBU is following these rules. In this case, we need to existing user group scope to an existing user and alert the user of the blocking issue.
- #10 - We need to make sure user accounts are set-up correctly and simulate their user. If configuration is correct, we remind them about how to connect.
- #11 - Here is a typic request of new user creation. If the new user needs to have access to the same access to someone else already in the data base, we don't need to create a new condition and a new user group: we simply reuse the ones existing.
- #12 - Here is a typic request of new user creation.
- #13 - Here is a typic request of new user creation.
- #14 - This request is referring to accessing workspaces which are handled through security by user role. We need to make sure the stated user has access to them and we have two ways of doing it. The first option is to check the security of workspace and assignment of user-user group. The second option is to simulate the user and verify the workspaces are accessible.
- #15 - The switch functionality is frequently used by several GBUs and a specific set-up needs to be completed.
- #16 - Here is a typic request of new user creation.
2. DFU Management
a. Exercises
- #3 - Hello Roberto Baleki, Yes. I had to activate Item 147501 in Dynasys. You should have visibility on Monday. Kind regards, Stacey Walker-Robertson
- #4 - Hello, I need to create 3 new DFU's, but the ship to I need cannot be found. I am using the Phosphorus Demand Review Workspace. The DFU's I need to create are. Aleksis Parfens
- Customer - GRAIN STORAGE SUPPLIES PTY LTD (2090174)
- Materials - ECO2FUME 50L 31.0KG 68.3LB AL CYL AU (147648)
ECO2FUME 50L 31.0KG 68.3LB ST CYL AU (144143)
VAPORPH3OS 49L 22KG 48.5LB ST CY (144316) - Distribution Channel - 0G
- Manufacturing Plant - 8712
- Shipping Plant - 8512
- #5 - The material 203757 is existing in SAP but I can not select the material in Dynasys to create a new DFU. What is the reason? (DP3)
- #6 - Dear team, 3 days ago two new material numbers were created in SAP MM. Checking today in Dynasys for setting up new DFUs, they are not listed. Please have them added/listed in Dynasys, so that the new DFUs can be created and forecasted. Jörg Braunschweig
- 319887 OPTALYS 501 LR 400 KG
- 319888 OPTALYS 501 LR 100 KG
- #8 - Hello, These DFUs (from Solvay INC US) are wrongly under Isabel Silva's scope in DynaSys DP. Please check. Luciana Vaz De Sousa Gastaldello.
- FENTAMINE DMA1297 BULK(CN):SOLVAY USA PRINCETON US
- FENTAMINE DMA1495 BULK(CN):SOLVAY USA US_NJR_PRINCETON US
- #9 - Hello, Order# 3007793 has been created in SAP for a while but somehow I don't see it as a DFU under Mat# 114494 in Dynasys DP. Can you please check what went wrong? It was not deactivated or superseded. Thanks, Tao Chen
- #11 - Can't find any DFUs with material 14858R, why? - Ghyslaine Etienne
- #13 - Can't find my DFU 127230R:2501578R@16R, why? - Carlos Sierra
b. Ticket References
| KT DFU Management | GBU | Sub-Process |
| 3 | TS | Activation/Deactivation |
| 4 | TS | New DFU Creation |
| 8 | CS | Assignment |
| 9 | CS | Import Flow |
| 11 | CS | Activation/Deactivation |
| 13 | CS | Assignment |
c. Steps to take
- #1 - First, check if the ship-to is in the Master Table Ship-to. If it is, it might be an issue of visibility for the user: we need to check the view of DFU creation and filter by condition applied. If it is not, we need to check the BW Ship-to file: if it is there, it will be imported on the next Static batch - if it is not there, we can import manually a ship-to by contacting the ITF team.
- #2 - We need to check the Master Table Material. If it is there, it might be an issue of visibility. If it is not, we need to check the BW file Material. If it is there, we need to wait for the next import (for material, it is scheduled weekly in Saturday except for DP2). If it is not, we need to check in SAP Material Master Data if all conditions are met: Tcode MM03, Basic data, MRP data, Cost and Accounting views need to be set-up.
- #3 - In this case, there is no action to do on our side. Roberto asks visibility for a DFU and Stacey, the Demand Planner, has activated it. It takes one day, after a static batch.
- #4 - DFUs creation is a process under the responsibility of the Demand Planner/S&OP planner. First, check if the ship-to is in the Master Table Ship-to. If it is, it might be an issue of visibility for the user: we need to check the view of DFU creation and filter by condition applied. If it is not, we need to check the BW Ship-to file: if it is there, it will be imported on the next Static batch - if it is not there, we can import manually a ship-to by contacting the ITF team.
- #5 - We need to check the Master Table Material. If it is there, it might be an issue of visibility. If it is not, we need to check the BW file Material. If it is there, we need to wait for the next import (for material, it is scheduled weekly in Saturday except for DP2). If it is not, we need to check in SAP Material Master Data if all conditions are met: Tcode MM03, Basic data, MRP data, Cost and Accounting views need to be set-up.
- #6 - We need to check the Master Table Material. If it is there, it might be an issue of visibility. If it is not, we need to check the BW file Material. If it is there, we need to wait for the next import (for material, it is scheduled weekly in Saturday except for DP2). If it is not, we need to check in SAP Material Master Data if all conditions are met: Tcode MM03, Basic data, MRP data, Cost and Accounting views need to be set-up.
- #7 - We need to check if the DFU is existing, active and planned (not replaced and not planned). We can check either in the master table with the related conditions or by creation a view from scratch with the related data fields. If the DFU is deactivated, you can reactivate it. If the DFU is not planned, you can re-planned it. If the DFU is replaced, you can cancelled the related supersession). In the three situations, tick the related data field and it will be visible the next day after the static batch. Also, if the DFU meets the criteria, it might be an issue of visibility/assignment to the correct user. In this case, you need to follow the flow upstream to verify if there is an override or what is the information we receive from interface.
- #8 - In this case, we can take the assumption that DFUs are existing, active and planned. So it might be an issue of visibility/assignment to the correct user. In this case, you need to follow the flow upstream to verify if there is an override or what is the information we receive from interface.
- #9 - First, we need to find what if the DFU reference: go to SAP, Tcode VA05N and key in the Order number. We will have then the material, ship-to and DC. Then, we need to check if the DFU is existing, active and planned (not replaced and not planned). We can check either in the master table with the related conditions or by creation a view from scratch with the related data fields. If the DFU is deactivated, you can reactivate it. If the DFU is not planned, you can re-planned it. If the DFU is replaced, you can cancelled the related supersession). In the three situations, tick the related data field and it will be visible the next day after the static batch. Also, if the DFU meets the criteria, it might be an issue of visibility/assignment to the correct user. In this case, you need to follow the flow upstream to verify if there is an override or what is the information we receive from interface.
- #10 - We need to check if the DFU is existing, active and planned (not replaced and not planned). We can check either in the master table with the related conditions or by creation a view from scratch with the related data fields. If the DFU is deactivated, you can reactivate it. If the DFU is not planned, you can re-planned it. If the DFU is replaced, you can cancelled the related supersession). In the three situations, tick the related data field and it will be visible the next day after the static batch. Also, if the DFU meets the criteria, it might be an issue of visibility/assignment to the correct user. In this case, you need to follow the flow upstream to verify if there is an override or what is the information we receive from interface.
- #11 - We need to check if any DFU is existing with this material, active and planned (not replaced and not planned). We can check either in the master table with the related conditions or by creation a view from scratch with the related data fields. If the DFU is deactivated, you can reactivate it. If the DFU is not planned, you can re-planned it. If the DFU is replaced, you can cancelled the related supersession). In the three situations, tick the related data field and it will be visible the next day after the static batch. Also, if the DFU meets the criteria, it might be an issue of visibility/assignment to the correct user. In this case, you need to follow the flow upstream to verify if there is an override or what is the information we receive from interface.
- #12 - We need to check if the DFU is existing, active and planned (not replaced and not planned). We can check either in the master table with the related conditions or by creation a view from scratch with the related data fields. If the DFU is deactivated, you can reactivate it. If the DFU is not planned, you can re-planned it. If the DFU is replaced, you can cancelled the related supersession). In the three situations, tick the related data field and it will be visible the next day after the static batch. Also, if the DFU meets the criteria, it might be an issue of visibility/assignment to the correct user. In this case, you need to follow the flow upstream to verify if there is an override or what is the information we receive from interface.
- #13 - We need to check if the DFU is existing, active and planned (not replaced and not planned). We can check either in the master table with the related conditions or by creation a view from scratch with the related data fields. If the DFU is deactivated, you can reactivate it. If the DFU is not planned, you can re-planned it. If the DFU is replaced, you can cancelled the related supersession). In the three situations, tick the related data field and it will be visible the next day after the static batch. Also, if the DFU meets the criteria, it might be an issue of visibility/assignment to the correct user. In this case, you need to follow the flow upstream to verify if there is an override or what is the information we receive from interface.
3. Import/Export Flows
Technical Documentation and Functional Documentation about BW reports.
a. Exercises
b. Ticket References
| KT Import/Export | GBU | Sub-Process |
| 1 | CS | Import - Master Data |
| 2 | CS | Import - Dynamic Data |
| 3 | All | Scheduling |
| 5 | All | Export - Dynamic Data |
| 6 | All | Export - Dynamic Data |
| 7 | All | Import - Static Data |
| 8 | TS | Export - Dynamic Data (SAP) |
| 9 | CS | Import - Dynamic Data |
| 10 | CS | Link Master Data |
c. Steps to take
- #1 - We need to check the Master Table Material. If it is there, it might be an issue of visibility. If it is not, we need to check the BW file Material. If it is there, we need to wait for the next import (for material, it is scheduled weekly in Saturday except for DP2). If it is not, we need to check in SAP Material Master Data if all conditions are met: Tcode MM03, Basic data, MRP data, Cost and Accounting views need to be set-up.
- #2 - We need to find what actuals the user is referring to: we can simulate his user and see which data fields he is using. Once found, we need to follow the data flow upstream to the import data field (fed by BW data). Then, we need to check which BW file is used (link up, display query) and verify the file. If we see data, it will be ok after next dynamic batch. If we don't, we need to check directly in SAP (Tcode VA05N).
- #3 - If a Sales Order for a new DFU has been created on D-Day, we need to wait D+2 to have the same DFU created in DynaSys: one day to be retrieved by BW and one day to be integrated in DynaSys with the static import. Manual creation will take only one day and data will be merged once information are received from BW.
- #4 - Each DFU is assigned to one Main Shipping Site (MSS) and one Main Production Site (MPS) based on data received from SAP (with possibility of override directly in DynaSys). There is a specific forcing loop for sites. We should open all data fields used on this loop to understand where data comes from. In this case, it could be either an override or data received from BW.
- #5 - Data are exported four times a day to DIP and BW reports (7AM, 1PM, 5PM, 11PM). The changes will reflect on BW reports automatically on the next refresh (unless there is an issue raised by our BW expert/ITF Team).
- #6 - For any question related to BW reports, we can refer to BW documentation which is always updated and complete. We can also check the export user model/data table to list the data fields which are exported. If a new data field needs to be exported, we need to validate this evolution with our team lead.
- #7 - The rule is we should get new DFU created in DynaSys two days after Sales Order creation in SAP. We need to check the Master Table DFU. If it is there, it would be a visibility/scope issue. If it is not there, we need to check Material, Ship-to, DC Master Tables. If we have all elements, we need to check the BW DFU file. If we don't, we need to check the BW file of the missing data. If we find data in BW files, it will be ok after static batch (daily for all, weekly for material). If we don't, we need to check in the Sales Order in SAP and verify the Order Type, the assigned Plant... or ask our BW expert.
#8 - First, we need to compare Final Forecast on Export User Model/Data Table and Forecast on Export file. If data is not matching, it might be linked to validation after file generation or file not generated after validation: we should contact ITF Team. If data is matching, we should contact SAP expert to check further.
- #9 - We need to follow the data flow upstream to the import data field (fed by BW data) until to check which BW file is used (link up, display query) and verify the file. If we see data, it will be ok after next dynamic batch. If we don't, we need to check directly in SAP (Tcode VA05N).
- #10 - The Mini-Zone and Zone are assigned manually by Country-BU. It needs to be updated regularly for new combination.
4. Screen Design
a. Exercises
- #1 - Create a view with the "Gross History and Final Forecast" data field, filtered on GBU - TS, grouped by Mini-Zone, Zone collapsed, with a drop-down list with BU Name to check data. This view will be saved in your Starting Workspace.
- #3 - Inverse the order of views in NV00.
- #4 - Before moving to next year, all CS Web Workspaces need to be updated with Current Y expanded and Y-1/Y+1 collapsed.
- #5 - Last time "TS - Sales Team Forecast" workspace has been saved, PC resolution was incorrect - could you please resize all views in all tabs? Also, please display name of drop-down list available. Also, remove grouping by country and add a drop-down list with the country instead in TS2.
- #7 - Use the view in #1 and save it under TS user model.
- #9 - Use the view in #1 and remove the split of dimensions and the actual grouping. DFUs should be now grouped by Material, Ship-to, Sold-to.
- #10 - GBU TS needs a dedicated workspace for DFU Management: what is your proposition?
- #11 - Add a data field style for a data field of your choice: Red if negative vs Green if positive.
b. Ticket References
| KT Screen Design | GBU | Sub-Process |
| 1 | TS | Grid View Creation |
| 3 | CS | Screen Design |
| 4 | CS | Screen Design |
| 5 | TS | Screen Design |
| 7 | TS | Grid View Creation |
| 9 | TS | Screen Design |
| 10 | TS | Remote Workspace Creation |
| 11 | All | Data field Style |
c. Steps to take
- #1 - Click on "New", "Grid View" on your upper ribbon. A new window opens. In "Data fields" tab, Browse and select the correct data field. If we don't know where the data field is the structure, we can use dependency view first to locate it. In "Selection" tab, select DFU dimension and filter with condition, click Next and Finish. In the same tab, group the Mini-Zone and then Zone (for each level, we need to tick "Display collapsed at opening"), click Next and Finish. Drop down list with Master Data is usually done with a split of dimension: in "Dim. Mapping" tab, click on "Specific", select the dimension you would like to split, click on "Split Dimension", tick this dimension and the BU name (in this case), go back to "Selection" tab, change code for name. Click OK and save configuration and save to server.
- #3 - Go to Configuration tab in our Explorer, right click, modify on the NV00 workspace. On "Definition" tab, select one view and change row or column set-up with 1, 2... Click OK and save to server.
- #4 - Go to Configuration tab in our Explorer, right click, modify views under NVxx workspaces. On "Selection" tab, select Horizon dimension, review filter by condition to take the correct fences and review grouping by year, tick "Display collapsed at opening" except "Current Year". Click OK and save to server.
- #5 - Open the workspace and click on "Adapt to Workspace". Right click on each drop-down list, a new window will open on the correct tab and dimension, change code for name. On grouping, unselect the first one and click Finish. Drop down list with Master Data is usually done with a split of dimension: in "Dim. Mapping" tab, click on "Specific", select the dimension you would like to split, click on "Split Dimension", tick this dimension and the Country name (in this case). Beware, in "Order of Dimensions" tab, we need to tick Invalid coordinate. Click OK and save configuration and save to server.
- #7 - Select the view you should have in your starting workspace, save as a model under TS User Model, rename the view according to Best Practices and save to server.
- #9 - Open the view, on "Dim. Mapping" tab, click on Standard. On "Selection" tab, select the dimension, click on group button and on the first level, choose your new grouping. Beware cross-hierarchies dimensions need to be chosen.
- #10 - The easiest solution would be to duplicate an existing workspace for another GBU and reapply correct groupings/filters. Or we can move existing views related to DFU management on another workspace. Create a new workspace, copy/paste views and review security to give access to TS users.
- #11 - Choose a data field, right click and click on Style of Data fields, choose Create or Modify private style of data field. In "Grid Style" tab, choose Interval and add two rules: Is lower than 0 = OK 1 - Is greater than 0 = Problem 1.