The filename should contain the following elements in the order listed below. Each element is separated by an underscore character. Underscore characters cannot be used with an element of the filename.
XML document must be company specific i.e. only one company per document
Example valid file names:
ZAV_GJCTIMESHEET_TSHEETS_100_999999.xml
|
Element |
Description |
Type |
Example |
|
PREFIX |
As per the Integration module default settings. For example this will be “ZAV’. This is a mandatory part of the filename. |
Alpha numeric (Len 10) |
“ZAV” |
|
PROCESSNAME |
This is the name of the Integration processes. For example this will be “GJCTIMESHEETS”. This is a mandatory part of the filename. |
Alpha Numeric |
“GJCTIMESHEETS” |
|
PARTNER/ SYSTEM Identifier |
Incoming – Set to a unique id allocated to a partner/system sending incoming XML files. For example this ID will be unique for each of the systems that integrate to it. This is a mandatory part of the filename. |
Alpha Numeric |
“TSHEETS” |
|
COMPANY CODE |
The Zavanti company the file relates to. This needs to be a valid company number. This is a mandatory part of the filename. |
Alpha Numeric (Len 3) |
“100” |
|
XML DOCUMENT NUMBER |
Incoming – Unique within Process Name, Company. Each partner/system will maintain uniqueness at this level. Files from different partners/systems are then unique by virtue of the Partner/System Identifier included in the file name. This is a mandatory part of the filename. |
Numeric |
“999999” |