The impacts are in the Datahub, some files on the backend server and in DSCP application.
Let's take the example of a new BW file: DYS_BW_BOM.csv
Step by steps:
| Step # | Description | Screenshot |
|---|---|---|
| Step 1 | Copy/Paste file to 'IN' folder ,in this case DYS_BW_BOM.csv |
|
| Step 2 | Create DYS_BW_BOM.fmt file in each ‘Format’ folder on the backend server
|
|
| Step 3 | Edit each DYS_BW_BOM.fmt file Keep same column number in .fmt file compare to .csv file |
|
| Step 4 | Review the settings : | |
| Step 5 | Create _TEMP table in SQL server Duplicate one _TEMP to copy, right click to create a new query | |
| Step 6 | Create _TEMP table in SQL server, correct the values accordingly | |
| Step 7 | Adapt the related VIEW in SQL server, correct the values accordingly | |
| Step 8 | Go to Itf folder (wdcdyad21.eua.solvay.com\DynaSys\Test\Itf) right click on FilesToSql.cmd -> Run as administrator，to transfer file to SQL | |
| Step 9 | Check the _TEMP Table if it’s correctly filled | |
| Step 10 | Add treatment in Macros: GetUNC, to feed the _MAIN table from the _TEMP one. | |
| Step 11 | Add “DYS_BW_BOM” to Tech: Update Datahub, to trigger the automatic update | |
| Step 12 | Run Update Datahub + Check logs if no errors | |
| Step 13 | (optional): If need to interface to Dyn, adapt scenario/query/mapping |
