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 step:

Step #       DescriptionScreenshot
Step 1Copy/Paste file to 'IN' folder ,in this case DYS_BW_BOM.csv 


Step 2Create DYS_BW_BOM.fmt file in each ‘Format’ folder on the backend server
  • D:\Dynasys\ITF\Files\In\Format
  • D:\Dynasys\DSCPx\ITF\Files\In\Format

Step 3

Edit each DYS_BW_BOM.fmt file

Keep same column number in .fmt file compare to .csv file

Step 4

Adapt the settings in D:\DynaSys\Batchs\Settings\settings.ini

  • Add the filename in UTF8_To_UnicodeList list  if a transcodification into Unicode Standard is necessary
  • Add the filename in WoInfinityList if Infinity values nedd to force to 0

See 4.5 - Import process of csv files for more detailed information


Step 5

Generate a SQL script from an existing table

Step 6Adapt the script above to create the _TEMP table

Step 7

Apply the steps 5 and 6 to generate the VIEW associated to the table.

Pay attention to keep (or not) the WHERE clause

Step 8

Open in edit mode the file D:\DynaSys\ITF\GlobalFilesToSql-OneFile-woCreateDt.cmd


Change the table name


Click on GlobalFilesToSql-OneFile-woCreateDt.cmd -> Run as administrator to transfer file to SQL

Step 9Check 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 11Add “DYS_BW_BOM” to Tech: Update Datahub, to trigger the automatic update

Step 12

Run Update Datahub + Check logs if no errors

Check the content of the _MAIN table for the current application (filter applied on App_Name field)

Step 13

(optional) If need to interface to Dyn, adapt scenario/query/mapping





  • No labels