¶ Overview
Connect Prefile is one of the available backends of Connect. It's an integrated out-of-the-box solution that does not require direct integration into an ERP system, but instead uses standard CSV files as the interface between Connect and the ERP system.
¶ Configuration
For the configuration of the Connect Prefile backend, refer to Connect Configuration.
¶ Prefile Feature History
New Connect versions can add new Prefile features which may result in changes to the structure of the CSV files (and the underlying database).
We do recommend that you keep your Connect up-to-date. But before doing updating it, make sure to consult the feature history below and the detailed description of the CSV files, that updating your Connect does not accidentally break your integration.
| Connect Version | Feature  / Bugfix  |
Affected Files and Columns | Remarks |
|---|---|---|---|
| 5.0.1840 | All goods receivers in TXML 5 are now exported |
Bill_Ship.dat |  Read the description of Bill_Ship.dat or you may ship goods to the wrong receiver |
| 5.0.1813 | Delimiter configured in TecCom Portal was not used |
||
| 5.0.1810 | Sequence number for allowances and charges is returned in response |
||
| BuyerOrderNumber couldn't have maximum length of 35 characters |
|||
| Allowances and charges sequence number didn't default to 1 |
AllowCharge.dat | ||
| MatAllowCharge.dat | |||
| 5.0.1800.5 | Requests without currency errored |
||
| Same product number with different maker code gave wrong quantity |
|||
| Allowances and charges calculation flow refined |
MatAllowCharge.dat | See description of MatAllowCharge.dat |
|
Partner.dat: MinimumOrderValue, MinimumOrderCharge and MinimumOrderDesc removed |
|||
| 5.0.1770.4 | Material allowances and charges can now be customer-specific |
MatAllowCharge.dat: PriceGroupId, Sequence added |
New columns! May break integration! |
| Allowances and charges can be added on header level |
AllowCharge.dat |  New file |
|
| Columns removed! May break integration! |
|||
| 5.0.1760 | Materials can be distinguished by maker code / brand |
All import files (see description of individual files) | |
| 5.0.1701 | Maker code / brand is exported |
Order_Item.dat: MAKER_CODE added |
New Column! May break integration! |
| 5.0.1700 | Headers can be used for import files |
All import files (see description of individual files) | |
| 5.0.1608 | Buyer's item position number is stored and exported as sent |
Order_Item.dat: ITM_NR |
|
| 5.0.1600 | Extended support for TXML 5 |
See description of individual files | |
| 5.0.1501 | Requested delivery date was not exported |
Order_Item.dat: REQ_DATE |
|
| 5.0.1500 | Preliminary support for TXML 5 |
Order_Item.dat: OE_NR added (see description of individual files) |
New Column! May break integration! |
| Errored item column |
Order_Item.dat: ITEM_ERRORED added |
New Column! May break integration! |
|
| 5.0.1400 | Optional list price |
MatPrice.dat: Price, Currency, StandardPriceUnit can be empty |
|
| 5.0.1000 | Storage of verbatim material number |
Order_Item.dat: MATERIAL_VERBATIM added |
New Column! May break integration! |
| 5.0.8.7 | Customer-specific prices |
Partner.dat: PriceGroupId added |
|
MatPrice.dat: Price, Price2, PriceGroupId added |
¶ General
¶ TXML 5
TXML 5 is the new XML format underlying our TecCom Order products. It is fully operational and the Connect is prepared for it. Certain fields in the import and export files can only be used if your Connect is configured to use TXML 5. If that is not the case, any content you put into these fields in the import files will not be used by the Connect. Likewise, these fields will be empty in the export files.
¶ File Properties
All files described below have these properties:
| Property | Description |
|---|---|
| Encoding | UTF-8 |
| Field Separator | Semicolon (;) |
Colon (:) |
|
Comma (,) |
|
Equal sign (=) |
|
Pipe (|) |
|
Space ( ) |
|
Tabulator (\t) |
|
| Quoting | Any field's value may be enclosed by double quotation marks ("). |
If a field's value contains the field separator or double quotation marks ("), then quoting is mandatory. |
|
Within a quoted value the double quotation mark (") must be escaped by doubling it (""). |
|
| Decimal Separator | The decimal separator for numerical fields is the period (.) |
| Headers | Headers are optional. |
| Without headers all fields must be present; none can be skipped. |
No Headers are written for the export files
¶ File Examples
Here is an example using the file format described above:
¶ Without Headers
All five fields have to be provided:
1997,Ford,E350,"ac, abs, moon",3000.00
1999,Chevy,"Venture ""Extended Edition""","",4900.00
1999,Chevy,"Venture ""Extended Edition, Very Large""",,5000.00
The same example in tabular view, after the Connect import:
| Year | Maker | Model | Features | Price |
|---|---|---|---|---|
| 1997 | Ford | E350 | ac, abs, moon | 3000.00 |
| 1999 | Chevy | Venture "Extended Edition" | 4900.00 | |
| 1999 | Chevy | Venture "Extended Edition, Very Large" | 5000.00 |
¶ With Headers
Only the fields you want to use have to be provided:
Year,Maker,Model,Price
1997,Ford,E350,3000.00
1999,Chevy,"Venture ""Extended Edition""",4900.00
1999,Chevy,"Venture ""Extended Edition, Very Large""",5000.00
The same example in tabular view, after the Connect import:
| Year | Maker | Model | Features | Price |
|---|---|---|---|---|
| 1997 | Ford | E350 | 3000.00 | |
| 1999 | Chevy | Venture "Extended Edition" | 4900.00 | |
| 1999 | Chevy | Venture "Extended Edition, Very Large" | 5000.00 |
¶ File Description
The following template is used for the description of the files below:
| Column | Explanation |
|---|---|
| Fieldname | Name of the field |
| Type | string |
decimal |
|
integer |
|
| Length | 5 Exact length of 5 |
..5 Maximum length of 5 |
|
| Restricted | Only the given values are allowed, if any |
| Required | Field is mandatory if checked |
| Unique | Field value must be unique if checked (no duplicates allowed) |
Composite field value of all fields with this number must be unique if numbered ( ,  , ...) (no duplicates allowed) |
|
| Default | Field value is set to given default if value from file is empty |
| Description | Description of the field |
| TXML 5 | Field can only be used with TXML 5 if checked |
¶ Import Files
From the below import files you will need at least the files Partner.dat, Material.dat and Inventory.dat for every import. All other import files are optional.
Incremental updates are not supported; the import files always must contain the data for all materials.
¶ Relationship Diagram
The relationship diagram below is generated from the database of the Connect Prefile backend. Therefore the data types in it are more specific than the ones used in the file descriptions.
¶ Material.dat
The file Material.dat contains the materials you want to sell through TecCom Order.
| Fieldname | Type | Length | Restricted | Required | Unique | Default | Description | TXML 5 |
|---|---|---|---|---|---|---|---|---|
| MaterialNr | string | ..30 | - |  |
|
Supplier-specific material number |  |
|
| Ean | string | ..14 | - | |
|
International article number | |
|
| ShortText | string | ..75 | - | |
|
Material description | |
|
| Manufacturer | string | ..32 | - | |
|
Material manufacturer | |
|
| AlternMatNr | string | ..30 | - | |
|
Number of alternative material in Material.dat |
|
|
| OeNr | string | ..35 | - | |
|
Original equipment number | |
|
| MakerCode | string | ..35 | - | |
|
* |
TecCom maker code or TecDoc brand for MaterialNr |
|
| AlternMakerCode | string | ..35 | - | |
|
* |
TecCom maker code or TecDoc brand for AlternMatNr |
|
Remarks:
OeNr: any original equipment number must be unique; it can only appear in the file once. If a customer orders a material with this number and two or more materials have the same original equipment number, then the Connect is unable to uniquely identify the material, as the database will return multiple matches.
Example:
MaterialNr;Ean;ShortText;AlternMatNr;MakerCode
myFirstArticle;1234567890123;rear coil spring;;*
mySecondArticle;Null;rear coil spring;my-Second-Article;*
myThirdArticle;Null;front coil spring;;*
¶ Inventory.dat
The file Inventory.dat contains the inventory data for your materials.
| Fieldname | Type | Length | Restricted | Required | Unique | Default | Description | TXML 5 |
|---|---|---|---|---|---|---|---|---|
| MaterialNr | string | ..30 | - | |
|
Material number in Material.dat |
|
|
| SalesUnit | string | 3 | - | |
|
Sales unit | |
|
| Stock | decimal | - | |
|
Stock level | |
||
| StandardSalesUnit | integer | 0, 1 |
|
|
If set to 1, indicates standard sales unit for materials available in multiple units |
|
||
| MakerCode | string | ..35 | - | |
|
* |
TecCom maker code or TecDoc brand for MaterialNr |
|
Example:
MaterialNr;SalesUnit;Stock;StandardSalesUnit;MakerCode
myFirstArticle;PCE;300000;1;*
mySecondArticle;PCE;80000;0;*
¶ MatPrice.dat
The file MatPrice.dat is used to define the prices for your materials.
It is possible to return individual net prices for materials. This is done by sorting the customers into price groups (see
Partner.datdescription). Then you have to add as many lines for a material as you have price groups. For example:
MaterialNr ... Price2 Currency2 PriceGroupId 12345 ... 10.90 EUR 1 12345 ... 15.90 EUR 2 Here the material with the number 12345 has the price 10.90 EUR for price group 1 and 15.90 EUR for price group 2. Every customer assigned to price group 1 in
Partner.datwould therefore receive 10.90 EUR as the net price and every customer assigned to price group 2 inPartner.datwould receive 15.90 EUR as the net price.Lastly, the
PriceGroupIdfield is just an arbitrary string. So if you want to assign individual prices to each customer, you can just use the customer number as thePriceGroupId. But then you will have to add as many rows inMatPrice.datfor a material as you have customers.
Customers are only shown prices for those materials where an entry exists in
MatPrice.datwith the samePriceGroupIdthey belong to. If this is not the case, they are not shown any prices for those materials.
| Fieldname | Type | Length | Restricted | Required | Unique | Default | Description | TXML 5 |
|---|---|---|---|---|---|---|---|---|
| MaterialNr | string | ..30 | - | |
|
Material number in Material.dat |
|
|
| UnitForPrice | string | ..3 | - | |
|
Price unit | |
|
| ValidFrom | string | 8 | - | |
|
Date from which a price is valid | |
|
| Price | decimal | - | |
|
List price | |
||
| Currency | string | 3 | - | |
|
ISO 4217 currency code for list price | |
|
| StandardPriceUnit | integer | 0, 1 |
|
|
If set to 1, indicates standard price unit for materials available at multiple prices |
|
||
| PerQty | integer | - | |
|
Obsolete | |
||
| DiscountGroup | string | ..6 | - | |
|
Discount group | |
|
| Price2 | decimal | - | |
|
Net price | |
||
| Currency2 | string | 3 | - | |
|
ISO 4217 currency code for net price | |
|
| PriceGroupId | string | ..50 | - | |
|
* |
Price group ID to which this price belongs, if any | |
| MakerCode | string | ..35 | - | |
|
* |
TecCom maker code or TecDoc brand for MaterialNr |
|
Example:
MaterialNr;UnitForPrice;ValidFrom;Price;Currency;StandardPriceUnit;PriceGroupId;MakerCode
myFirstArticle;PCE;20240101;29.99;EUR;1;price-group-1;*
myFirstArticle;PCE;20240101;24.50;EUR;1;price-group-2;*
myFirstArticle;PCE;20240101;34.50;EUR;1;*;*
mySecondArticle;PCE;20240101;27.99;EUR;1;*;*
myThirdArticle;PCE;20240101;32.99;EUR;1;*;*
¶ Partner.dat
The file Partner.dat contains information about your customers and is used to control which customers are allowed to send inquiries and orders. If the customer number of the customer sending the request is not contained in this file the request will be rejected. Additionally, it is also used to define groups for the net price feature.
| Fieldname | Type | Length | Restricted | Required | Unique | Default | Description | TXML 5 |
|---|---|---|---|---|---|---|---|---|
| PartnerNr | string | ..13 | - | |
|
Customer number | |
|
| Name1 | string | ..35 | - | |
|
Name 1 | |
|
| Name2 | string | ..35 | - | |
|
Name 2 | |
|
| PostCode | string | ..10 | - | |
|
Postal code | |
|
| City | string | ..35 | - | |
|
City | |
|
| Street1 | string | ..35 | - | |
|
Street 1 | |
|
| Street2 | string | ..35 | - | |
|
Street 2 | |
|
| Tel | string | ..25 | - | |
|
Phone | |
|
| Fax | string | ..25 | - | |
|
Fax | |
|
| string | ..256 | - | |
|
Email address | |
||
| CntrCode | string | 2 | - | |
|
ISO 3166-1 Alpha-2 country code | |
|
| PriceGroupId | string | ..50 | - | |
|
* |
Price Group ID to which this customer belongs, if any | |
Example:
PartnerNr;Name1;Name2;PostCode;City;Street1;Street2;Tel;Fax;Email;CntrCode;PriceGroupId
222222;Buyer Company;;11111;Sample Town;23 Main Street;;+99 888 7777;;name@samplecompany.xyz;DE;*
268294;;;;;;;;;;DE;price-group-1
739104;;;;;;;;;;DE;*
¶ CustMaterial.dat
The file CustMaterial.dat can be used to define customer material numbers. This enables customers to order with their own material numbers which they might have assigned to supplier material numbers in their ERP system.
| Fieldname | Type | Length | Restricted | Required | Unique | Default | Description | TXML 5 |
|---|---|---|---|---|---|---|---|---|
| CustMaterialNr | string | ..30 | - | |
|
Customer material number | |
|
| PartnerNr | string | ..13 | - | |
|
Customer number in Partner.dat |
|
|
| MaterialNr | string | ..30 | - | |
|
Material number in Material.dat |
|
|
| MakerCode | string | ..35 | - | |
|
* |
TecCom maker code or TecDoc brand for MaterialNr |
|
¶ ReferenceMat.dat
The file ReferenceMat.dat can be used to have the Connect identify materials by different numbers than the supplier-specific material numbers.
| Fieldname | Type | Length | Restricted | Required | Unique | Default | Description | TXML 5 |
|---|---|---|---|---|---|---|---|---|
| MatNrManufact | string | ..30 | - | |
|
Material number of manufacturer | |
|
| NrSysManufact | string | ..6 | - | |
|
TecCom Maker code of manufacturer | |
|
| MaterialNr | string | ..30 | - | |
|
Material number in Material.dat |
|
|
| MakerCode | string | ..35 | - | |
|
* |
TecCom maker code or TecDoc brand for MaterialNr |
|
¶ AllowCharge.dat
The file AllowCharge.dat can be used to define allowances or charges for the whole order.
This file is only usable with TXML 5.
Customer-specific allowances and charges are possible via the
PriceGroupId(seeMatPrice.datfor details on how to use thePriceGroupId).
The Connect does perform a calculation of the summary net amount according to the matching allowances or charges in this file.
| Fieldname | Type | Length | Restricted | Required | Unique | Default | Description | TXML 5 |
|---|---|---|---|---|---|---|---|---|
| Type | string | ..10 | Allowance | |
|
|
||
| Charge | ||||||||
| Code | string | ..30 | see below | |
|
Type of allowance or charge | |
|
| Desc | string | ..35 | |
|
Description of allowance or charge | |
||
| Percent | decimal | |
|
Percent value of allowance or charge (not used for calculation) | |
|||
| Amount | decimal | |
|
Amount value of allowance or charge | |
|||
| PerValue | decimal | |
|
0 |
PerValue = 0: allowance or charge is always applied |
|
||
PerValue > 0 and Type = Allowance: allowance is applied if net amount of all lines greater or equal this value |
||||||||
PerValue > 0 and Type = Charge: charge is applied if net amount of all lines less than this value |
||||||||
| PriceGroupId | string | ..50 | - | |
|
* |
Price Group ID to which this allowance or charge belongs, if any | |
| Sequence | integer | - | |
|
1 |
Sequence number (calculation order) | |
¶ Code Values
¶ Allowances
Only certain codes of this list make sense, as the allowance is always applied to a material unconditionally.
FreeGoods, Discount, QuantityDiscount, PalletDiscount, TruckloadDiscount, TradeDiscount, WholesalingDiscount, AdvertisingAllowance, LogisticChainAllowance, CompetitiveAllowance, IntroductionAllowance, PromotionalAllowance, TemporaryAllowance, EarlyBuyAllowance, EarlyPaymentAllowance, OtherAllowances, ReSuppliersDiscount, Rebate
¶ Charge Codes
Only certain codes of this list make sense, as the charge is always applied to a material unconditionally.
ReturnableContainer, ReturnedProductCharge, ReturnHandling, MinimumOrderCharge, OtherCharges, NonReturnableContainer, MaterialSurcharge, CopperSurcharge, SilverSurcharge, EcoTax, Adjustments
¶ MatAllowCharge.dat
The file MatAllowCharge.dat can be used to define allowances or charges for materials.
This file is only usable with TXML 5.
Customer-specific allowances and charges are possible via the
PriceGroupId(seeMatPrice.datfor details on how to use thePriceGroupId).
The Connect does not perform any net amount calculation for allowances and charges of materials, with the exception that is listed in the description for the
PerQtyfield. You are responsible for providing the the correct net amounts inclusive all allowances and charges. The allowances or charges defined here are therefore mainly helpful for the buyer to understand the composition of the net price.
| Fieldname | Type | Length | Restricted | Required | Unique | Default | Description | TXML 5 |
|---|---|---|---|---|---|---|---|---|
| MaterialNr | string | ..30 | - | |
|
Material number in Material.dat |
|
|
| Type | string | ..10 | Allowance | |
|
|
||
| Charge | ||||||||
| Code | string | ..30 | see below | |
|
Type of allowance or charge | |
|
| Desc | string | ..35 | |
|
Description of allowance or charge | |
||
| Percent | decimal | |
|
Percent value of allowance or charge | |
|||
| Amount | decimal | |
|
Amount value of allowance or charge; has priority over Percent value. |
|
|||
If not specified, this value is calculated as: Line Net Amount * Percent / 100. |
||||||||
| PerQty | decimal | |
|
1 |
If Code = MinimumOrderCharge and Confirmed Quantity < PerQty: apply charge |
|
||
Else if PerQty = 0: apply Amount as given |
||||||||
Else if PerQty > 0: set Amount to result of Amount * Confirmed Quantity |
||||||||
| MakerCode | string | ..35 | - | |
|
* |
TecCom maker code or TecDoc brand for MaterialNr |
|
| PriceGroupId | string | ..50 | - | |
|
* |
Price Group ID to which this allowance or charge belongs, if any | |
| Sequence | integer | ..5 | - | |
|
1 |
Sequence number (calculation order) | |
¶ Code Values
¶ Allowances
Only certain codes of this list make sense, as the allowance is always applied to a material unconditionally.
FreeGoods, Discount, QuantityDiscount, PalletDiscount, TruckloadDiscount, TradeDiscount, WholesalingDiscount, AdvertisingAllowance, LogisticChainAllowance, CompetitiveAllowance, IntroductionAllowance, PromotionalAllowance, TemporaryAllowance, EarlyBuyAllowance, EarlyPaymentAllowance, OtherAllowances, ReSuppliersDiscount, Rebate
¶ Charge Codes
Only certain codes of this list make sense, as the charge is always applied to a material unconditionally.
ReturnableContainer, ReturnedProductCharge, ReturnHandling, MinimumOrderCharge, OtherCharges, NonReturnableContainer, MaterialSurcharge, CopperSurcharge, SilverSurcharge, EcoTax, Adjustments
¶ ExternalDocuments.dat
The file ExternalDocuments.dat can be used to return language-specific WWW links to additional documentation for a material.
This file is only usable with TXML 5.
| Fieldname | Type | Length | Restricted | Required | Unique | Default | Description | TXML 5 |
|---|---|---|---|---|---|---|---|---|
| MaterialNr | string | ..30 | - | |
|
Material number in Material.dat |
|
|
| Qualifier | string | ..70 | see below | |
|
Document qualifier | |
|
| Link | string | ..1500 | - | |
|
WWW link to document | |
|
| Language | string | ..2 | - | |
|
Language of document as ISO 639 Set 1 language code | |
|
| Title | string | ..512 | - | |
|
Title of document | |
|
| MakerCode | string | ..35 | - | |
|
* |
TecCom maker code or TecDoc brand for MaterialNr |
|
¶ Qualifier Values
DangerousGoods, Recycling, TechnicalData, ProductDescription, Payment, SenderGeneral, SenderProblem, SenderVehicle, ReceiverGeneral, ReceiverProblem, ReceiverVehicle
¶ Measurements.dat
The file Measurements.dat can be used to return various measurement information for a material.
This file is only usable with TXML 5.
| Fieldname | Type | Length | Restricted | Required | Unique | Description | TXML 5 | |
|---|---|---|---|---|---|---|---|---|
| MaterialNr | string | ..30 | - | |
|
Material number in Material.dat |
|
|
| Qualifier | string | ..20 | see below | |
|
Measurement type | |
|
| Unit | string | ..20 | see below | |
|
Measurement unit | |
|
| Value | decimal | - | |
|
Measurement value | |
||
| MakerCode | string | ..35 | - | |
|
* |
TecCom maker code or TecDoc brand for MaterialNr |
|
¶ Qualifier Values
UnitNetWeight, UnitGrossWeight, NetWeight, GrossVolume, StackingHeight, NetVolume, Height, Length, Width, TotalNetWeight, TotalGrossWeight, UnitsPerPallet, StackingWeight, Lines
¶ Unit Values
Centimetre, Inch, Kilogram, Litre, Millilitre, Millimetre, Squaremetre, CubicMetre, Metre, Piece, MetricTon, Grams, Barrel, GallonUS, Pound, Ounce, Number
¶ Export Files
¶ Order_Header.dat
The file Order_Header.dat is used to output the header information of received orders. Several orders can be contained in the same file.
| Fieldname | Type | Length | Restricted | Required | Unique | Description | TXML 5 |
|---|---|---|---|---|---|---|---|
| ORDER_NR | integer | ..10 | - | |
|
Order number | |
| PARTNER_NR | string | ..13 | - | |
|
Customer number | |
| PO_DATE | string | 8 | - | |
|
Purchase date | |
| PO_TIME | string | 6 | - | |
|
Purchase time | |
| PART_DLV | integer | 0, 1 |
|
|
If set to 1, partial delivery is allowed |
|
|
| BACKLOG_ALLOWED | integer | 0, 1 |
|
|
If set to 1, backlog is allowed |
|
|
| DISPATCH_MODE | integer | see below | |
|
Dispatch mode | |
|
| CUST_NAME | string | ..30 | - | |
|
Contact person name | |
| CUST_TELEPHONE | string | ..25 | - | |
|
Contact person phone number | |
| PO_NUMBER | string | ..20 | - | |
|
Purchase order number | |
| CURRENCY | string | 3 | - | |
|
ISO 4217 currency code | |
| FLAG | integer | - | |
|
Internal flag; ignore | |
|
| PROMOTION_CODE | string | ..20 | - | |
|
Promotion code | |
| ANO | string | ..20 | - | |
|
Arrival notice | |
| INCOTERMS1 | string | ..20 | - | |
|
Incoterms 1 | |
| INCOTERMS2 | string | ..20 | - | |
|
Incoterms 2 | |
| STORAGE_LOCATION | string | ..20 | - | |
|
Storage location | |
| CARRIER_ID_ILN | string | ..20 | - | |
|
Freight company code | |
| SPEDITION | string | ..20 | - | |
|
Freight company text | |
| FREE_TEXT | string | ..20 | - | |
|
Free text | |
| EXPRESS_DLV_COND | string | ..20 | - | |
|
Express delivery condition | |
¶ Bill_Ship.dat
The file Bill_Ship.dat is used to output the numbers and/or addresses of goods receivers for orders. The goods receivers of several orders can be contained in the same file.
| Fieldname | Type | Length | Restricted | Required | Unique | Description | TXML 5 |
|---|---|---|---|---|---|---|---|
| ORDER_NR | integer | - | |
|
Order number from Order_Header.dat |
|
|
| ROLE | string | ..25 | Unloading | |
|
Role | |
| ThirdParty | |||||||
| DeliveryParty | |||||||
| BILL_SHIP_NUMBER | string | ..13 | - | |
|
Goods recipient number | |
| NAME1 | string | ..35 | - | |
|
Name 1 | |
| NAME2 | string | ..35 | - | |
|
Name 2 | |
| POST_CODE | string | ..10 | - | |
|
Postal code | |
| CITY | string | ..35 | - | |
|
City | |
| STREET1 | string | ..35 | - | |
|
Street 1 | |
| STREET2 | string | ..35 | - | |
|
Street 2 | |
| TEL | string | ..25 | - | |
|
Phone number | |
| FAX | string | ..25 | - | |
|
Fax number | |
| string | ..256 | - | |
|
Email address | |
|
| CNTR_CODE | string | 2 | - | |
|
ISO 3166-1 Alpha-2 country code | |
TXML 5
TXML 5 can transport three different goods receivers for the same order. Therefore the
Bill_Ship.datfile can contain three lines for the same order:
UnloadingThirdPartyDeliveryPartyThese goods receivers have a priority according to the above list. You must ship the goods to the receiver with the highest priority.
TXML 4.1
With TXML 4.1 the
Bill_Ship.datfile will only contain one line for the same order.
¶ Dispatch Mode Values
¶ TXML 4.1
0 = Stock Order, 1 = Normal, 2 = Express, 3 = Overnight, 4 = Pickup, 5 = Cash-on-Delivery, 6 = Sea Freight, 7 = Air Freight, 9 = Till 9:00, 10 = Till 18:00, 12 = Till 12:00, 13 = Parcel Post, 14 = Private Parcel Service, 15 = Mail, 16 = Courier Express
¶ TXML 5
0 = Road, 1 = Road Express, 2 = Rail, 3 = Sea, 4 = Sea Express, 5 = Air, 6 = Air Express, 7 = Mail, 8 = Courier, 9 = Courier Express, 10 = Parcel Post, 11 = Private Parcel Service, 12 = Pickup, 13 = Overnight, 14 = Till 9:00, 15 = Till 12:00, 16 = Till 18:00
¶ Order_Item.dat
The file Order_Item.dat is used to output the items belonging to an order. The items of several orders are contained in the same file.
Customers can send prices via the fields
CUST_PRICE_CATEGORY,CUST_PER_QTY,CUST_UNIT_FOR_PRICE,CUST_DISCOUNT_GROUP,CUST_PRICEandCUST_CURRENCY. These prices are not part of the TecCom standard process. You can or cannot use them based on your own agreement you have with a customer.
| Fieldname | Type | Length | Restricted | Required | Unique | Description | TXML 5 |
|---|---|---|---|---|---|---|---|
| ORDER_NR | integer | ..10 | - | |
|
Order number from Order_Header.dat |
|
| ITM_NR | integer | ..6 | - | |
|
Position number of item | |
| MATERIAL | string | ..30 | - | |
|
Material number | |
| EAN | string | 14 | - | |
|
European article number | |
| CUST_MATERIAL_NR | string | ..30 | - | |
|
Customer material number | |
| QUANTITY | decimal | - | |
|
Quantity | |
|
| UNIT | string | 3 | - | |
|
Unit | |
| CUST_PRICE_CATEGORY | integer | - | |
|
Customer price category | |
|
| CUST_PER_QTY | integer | - | |
|
Customer quantity for price | |
|
| CUST_UNIT_FOR_PRICE | string | 3 | - | |
|
Customer unit for price | |
| CUST_DISCOUNT_GROUP | string | ..4 | - | |
|
Customer rebate group | |
| CUST_PRICE | decimal | - | |
|
Customer price | |
|
| CUST_CURRENCY | string | 3 | - | |
|
Customer currency | |
| PART_DLV | integer | 0, 1 |
|
|
If set to 1, partial delivery is allowed |
|
|
| BACKLOG_ALLOWED | integer | 1 | 0, 1 |
|
|
If set to 1, backlog allowed is allowed |
|
| REQ_DATE | string | 8 | Format: YYYYMMDD | |
|
Requested delivery date | |
| PROMOTION_CODE | string | ..20 | - | |
|
Promotion code | |
| ANO | string | ..20 | - | |
|
Arrival notice | |
| INCOTERMS1 | string | ..20 | - | |
|
Incoterms 1 | |
| INCOTERMS2 | string | ..20 | - | |
|
Incoterms 2 | |
| STORAGE_LOCATION | string | ..20 | - | |
|
Storage location | |
| CARRIER_ID_ILN | string | ..20 | - | |
|
Freight carrier code | |
| SPEDITION | string | ..20 | - | |
|
Freight carrier text | |
| FREE_TEXT | string | ..20 | - | |
|
Free text | |
| EXPRESS_DLV_COND | string | ..20 | - | |
|
Express delivery condition | |
| MATERIAL_VERBATIM | string | ..30 | - | |
|
Material number originally sent by customer | |
| ITEM_ERRORED | integer | 0, 1 |
|
|
If set to 1, there was an error during item processing |
|
|
| OE_NR | string | ..35 | - | |
|
Original equipment number | |
| MAKER_CODE | string | ..35 | - | |
|
TecCom maker code or TecDoc brand | |
¶ Prefile Database Access
It's possible to use a Prefile database directly, i.e. data is read from and written to the database through a direct connection, for example from the ERP system, without having to import and export the CSV files that the Connect uses by default.
If you want to use a Prefile database directly, note the following:
-
Do not modify the database schema! Connect does automatic database migrations and any modifications may result in it not working anymore or making it impossible to upgrade it to a newer version.
-
If you want to activate the Connect option
Remove special characters, then you have to be aware that in the database some tables contain special columns with_PROCESSEDattached to the name, for example,MATERIAL_NR_PROCESSEDin the tableMATERIAL. During import of the CSV files the Connect removes certain special characters from the value for theMATERIAL_NRcolumn and writes this value in theMATERIAL_NR_PROCESSEDcolumn.If these columns are not filled, but the Connect option
Remove special charactersis activated, the material search will fail.The columns into which material numbers with the special characters removed are written, are:
CUST_MATERIAL.CUST_MATERIAL_NR_PROCESSEDMATERIAL.MATERIAL_NR_PROCESSEDMATERIAL.OE_NR_PROCESSEDREFERENCE_MAT.MAT_NR_MANUFACT_PROCESSED
The special characters the Connect replaces during the import of the CSV files are:
!,§,$,_,|,<,>,%,&,/,=,#,;,@,,,(,),?,*,+,\,.,-.