You can transfer any third party information to PARTsolutions with ERP integration (into the link database).
There are three basic requirements regarding data transfer and links for PARTsolutions with an ERP link.
Cyclical data updating is realized by scripting via nightupdate.vbb
. Details can be found at Section 4.13.3.5, “
Configuration file nightupdate.cfg
”
The identification of the correct dataset can happen by the material master number and the ERP_PDM_NUMBER.
If a data record is uniquely assigned, information from any number of ERP columns can be transferred to the link database.
The following illustration shows an example of an update of the item price and stock columns.
The license "CSN2005*PSDEV*PIDENT" has to be available.
The ERP system cyclically exports changes in form of a CSV file (e.g. daily, possibly several times a day, usually by night. The CSV file only contains datasets changed during the last cycle.
A job is defined via "Planned tasks" (according to the export cycle of the ERP system).
The script
nightupdate.vbb
is called here; either with or without additional specification of the configuration file:Without explicit declaration of a configuration file:
"%cadenas%\bin\x86\32\cscripthost.exe" "%cadenas_setup%\scripts\erp\nightupdate.vbb"
With additional declaration of a configuration file. This can make sense, if differently configured CSV files are used.
"%cadenas%\bin\x86\32\wscripthost.exe" "%cadenas_setup%\scripts\erp
\nightupdate.vbb" "nightupdate.cfg"
The script is available at
$CADENAS_SETUP\scripts\erp\nightupdate.vbb
please also note the information in the script file itself.The configuration file is located under
$CADENAS_SETUP\nightupdate.cfg
.Specific adjustments are made in the configuration file
nightupdate.cfg
.The changed datasets of the third party system are written into the LinkDB according to these settings.
![]() | Note |
---|---|
Detailed information on the configuration file |
![]() | Note |
---|---|
That
Update via scripting by |