With the openTrans order import, the ingenious software makes it possible to import customer order data electronically via the open standard.

In addition to general import settings, such as data source, etc., the product variants of the software systems to be exchanged must be mapped.

 

User rights

101820 – Contacts – View OpenTrans import settings

101830 – Contacts – Modify OpenTrans import settings

353000 – Projects – View openTRANS order export

353100 – Projects – Start openTRANS order export

353200 – Projects – Start openTRANS delivery note export

 

Basic settings

OpenTrans import basic settings

 

File storage

Active	Checkbox	Only contacts with activated checkbox are included in the import.
Import from	Simple input field	Directory containing the files to be imported
Save successfully imported files to	Simple input field	Directory where successfully imported files are stored after the import.
Save incorrect files to	Simple input field	Directory where files are stored that could not be imported.
Save order confirmation	Simple input field	Directory where the order confirmation is stored
Store delivery note	Simple input field	Directory where the dispatch notification is stored
Send error message to	Simple input field	E-Mail address to which error messages should be sent
Send error message to	Drop-down	Restricting the sending of error messages to only part list warnings or only part list errors
Character coding	Drop-down	Selection of the coding of the xml files
Decimal places at numeric conversion	Drop-down	Selection of the decimal places in numerical conversion

 

For each of the text boxes in which a directory can be entered, there is the option of choosing between a local/network directory or a directory on an FTP server.

The local/network directory can be selected with the button .

The FTP directory must be entered manually.

The format is unimportant here: for example, “\openTRANS_Import\XML”, “//openTRANS_Import//XML” and “openTRANS_Import//XML” would be possible.

 

FTP-Server

SSL	Checkbox	Activation of data transfer encryption
Host	Simple input field	Adress of the server on which the FTP server is running
Login	Simple input field	FTP user login
Password	Simple input field	FTP user password
Test connection	Button	Function for testing the connection with the stored FTP access data

 

Article list

All part list configurations are displayed in this list.

The following functions are available for the item list via the corresponding buttons.

	Adding an item to create a new configuration / a new part list mapping
	Delete marked article configuration from the list
	Duplicate article: the existing configuration for the marked article is opened and after editing, a new entry is created in the list with the new duplicated article
	Edit selected item configuration for the order import
	Edit selected article configuration for the order response export

 

Configuration of a new part list mapping

Clicking on the button opens a window in which a new configuration can be created.

 

Import mapping for a part list

 

The article is described in the upper part, the mapping is created or edited in the lower part.

 

Assignment

In the first text box the item matchcode is entered or searched for using the familiar search functions.

The SUPPLIER_PID is used to identify which item in the XML file is described by the configuration (path of the node in the XML file: ORDER/ORDER_ITEM_LIST/ORDER_ITEM/PRODUCT_ID/SUPPLIER_PID).

A feature from the XML file can be entered under “Additional conditions” (path of the node: ORDER/ORDER_ITEM_LIST/ORDER_ITEM/PRODUCT_FEATURES/FEATURE).

The identifier column corresponds to the FNAME node and the Value column to the fVALUE node.

If a value is entered in the additional conditions, this is used as further identification of the article.

In this way, items that have the same SUPPLIER_PID can be uniquely identified by specifying a different feature.

Example: Two articles have the SUPPLIER_PID “RollShutterA”.

The first article has the FEATURE node with FNAME = OT1, FVALUE = X, the second article has a FEATURE node with FNAME = OT1, FVALUE = Y.

If there is a line with the designation OT1 and the value Y in the further conditions, this configuration can be clearly assigned to the second article.

 

Mapping

ESNAME	Value of node FNAME from XML file
ESWERT	Value of node FVALUE from XML file
Conversion	Conversion of the EVALUATION into an ingenious part list value (only with activated value transfer) Options: string: Value is taken as it is in the XML file numerical – without conversion: only numbers are taken from the value (e.g.: 100cm becomes 100) mm -> cm: Value is multiplied by 10 cm -> mm: Value is divided by 10
Ingenious part list description	Identifier from the ingenious part list (e.g. plaster base, profile, type of construction, etc.) The value from the colum “ingenious part list value” is assigned to this identifier, or the value from the XML file, if it is accepted. Tab statements are possible.
Ingenious part list value	This value is assigned to the identifier from the “ingenious part list description” column (only with inactive value transfer). Tab statements are possible.
Transfer of value	Checkbox active: the value from the XML file is assigned to the identifier from the “ingenious part list description” column. Checkbox inactive: the value from the “ingenious part list value” column is assigned to the identifier from the “ingenious part list description” column.
Last column	Clicking on it opens the part list configuration windows (see figure) A mapping for the feature can be selected in the window: One line is created in the table for each option selected in the window. ESNAME and ESWERT are the same as the line in which the button was clicked. The ingenious part list description and values are taken from the window.

 

Part list cnfiguration

 

A new entry is  added using the icon , existing marked entries are removed using the button .

Entries in the table can be copied (Ctrl C) and added collectively (Ctrl V) to build up the list more quickly.

Multiple rows are selected with click + shift + click.

The rows can also be copied to Excel or pasted from Excel.

Note: In order to set the “Value transfer” checkbox correctly in Excel, “not selected” for an inactive checkbox and “selected” for an active checkbox must be entered in Excel in the 6th column.

 

openTRANS settings

 

Finer settings for configuring the import can be made in the openTRANS settings. For each openTRANS element you can choose whether and where it should be saved during the import.

A tree is shown on the left in the figure, which contains all elements of the ORDER, ORDERRESPONSE or DISPATCHNOTIFICATION subarea of the openTRANS standard. If an element is selected, information and setting options for it are displayed on the right.

With the “Active” checkbox, the user can choose whether this node should be imported if it is present in an XML file. The Link Type drop-down box determines where the value of this item should be stored. You can choose between a table field and a user field.

The “Select database field” button opens a window in which the desired table field can be selected.

Different setting options are available for the PARTY_ROLE element than for the other nodes, in order to differentiate between the different address types and to take them into account during the import according to the corresponding PARTY_ROLEs from the openTRANS standard:

 

openTRANS settings

 

The openTRANS element PARTY contains information about a business partner. One of the child nodes, PARTY_ROLE, describes the business partner’s role in the transaction.

For each address type it is possible to select up to two roles from the openTRANS specification in the drop-down fields below the checkboxes.

If a checkbox is active and at least one value is selected in the associated checkboxes, an address with the corresponding address type is created during import and filled with the values ​​from the PARTY element of the file to be imported, provided that a PARTY_ROLE with the value from one of the checkboxes exists.

The tree can be edited with the following buttons in the ribbon bar:

 

	Adds a copy of the currently selected element as a new node
	Removes the selected node
	Adds a new PRODUCT_COMPONENTS node to a selected PRODUCT_COMPONENT node
	Removes the selected PRODUCT_COMPONENTS node

 

Adding nodes can be useful if the selected node occurs several times in the order to be imported.

This ensures that the settings of each node are taken into account during the import.

For example, if there are two PARTYs with different PARTY_ROLEs in the order, then this should be reflected in the settings in the tree.

 

Scripts

The openTRANS import can be executed or influenced with the following scripts:

Function	Script	Module assignment
Start import manually	public override string OpenTransOrderImport() { return ingenious.net.Moduls.OpenTrans.OpenTransImport.OpenTransOrderImport.StartImport(); }	Projects
Script that is executed before the project is saved in the DB in order to edit or add information to the order confirmation	public override void OpenTransOrderImportBeforeSave(ingenious.net.DataSets.DataSet_Projects dataset) { }	Projects
Script that is executed in the DB before the order confirmation is exported in order to edit or supplement information in the order confirmation	public override string OpenTransOrderResponseBeforeExport(DataSet dataset, ingenious.net.Moduls.OpenTrans.OpenTransImport.OpenTransNode node) { }	Projects
Script that is executed in the DB before the dispatch notification is exported in order to edit or add information to the dispatch notification	public override string OpenTransDispatchNotificationBeforeExport(DataSet dataset, ingenious.net.Moduls.OpenTrans.OpenTransImport.OpenTransNode node) { }	Projects
Execute the import time-controlled via the ingenious scheduler	public void openTRANS_Import(out bool bError, out string sResult, out string sDescription) { bError = false; sResult = “”; sDescription = “”; ingenious.net.Moduls.OpenTrans.OpenTransImport.OpenTransOrderImport.StartImport(out bError, out sResult, out sDescription); }	Scheduler