Data Import

Dynasys is daily refreshed from BW and SalesForce.

A global and unique process (common to all instances of one company) allows to manage files provided by those two applications. The goal is to :


Results of import flows are centralized into DYS_GLOBAL_IO_FLOWS table,  filtered on Flow_type = 'DYN_IN' and Flow_Sub_Type = 'Import_Files' and Activated = '1'


> Flow_Table = name of the inbound file without its extension

> Original_Date = date of the last file imported in U00

> Last_Exec = date of the last file proceed


Here's the algorithm dedicated to inbound csv files for DPx/DiPx instances only :



Read files

If current day = Monday, the file must have been generated on Day-1 at the latest

Otherwise, the creation date of the file must be Day 0.

The setting file D:\DynaSys\Batchs\Settings\dscp_settings.ini on the backend server contains a list of files to exclude.

If the file is part of this list, it won't be processed.


Force "infinity"

The list of files in which infinity values are replaced by zero are defined in the setting file :


Switch to unicode 

Files to convert to Unicode Standard are listed in the setting file :


UTF8 files

Files including special characters and with UTF-8 encoding are listed in the setting file :

Note : the option Collation must be removed from the fmt file

Status = ?

Once the file is uploaded into its TEMP table, then the related line of DYS_GLOBAL_IO_FLOWS table is updated :

If the file is defined in the list of excluded files, then the related line of DYS_GLOBAL_IO_FLOWS table is updated :


Rework data

This process allows to force some values in TEMP tables or remove lines that are not consistent.

For example :


Apply integrity controls

Once in the Datahub, data sourced from BW/SalesForce may be controlled in order to guarantee consistency : we talk about integrity controls (IC) which are performed on TEMP tables.

Different types of IC are predefined in Dynasys application.

An IC is always assigned to one table (actually one file), several IC can be set up to monitor one table.

Four types of IC :

If all IC assigned to one table are verified, then this TEMP table is copied into its "twin" BCKUP table.

Otherwise, the TEMP table is refreshed from BCKUP table.


Integrity controls are defined into DYS_GLOBAL_IO_FLOWS table,  filtered on Flow_type = 'DYN_IN_IC' and Activated = '1'



Manual import of csv files

All DYS_BW / DYS_SF files

This manual process allows to refresh all TEMP tables, whatever the creation date of inbound files.

Files part of the exclusion list are ignored.


One or several files

This manual process allows to refresh one (or several) TEMP table(s), whatever the creation date of inbound files.

Files part of the exclusion list are ignored.