¶ TecAlliance Message Formats
¶ The differences in detail
The following matrix visualizes which processes and data fields are supported by data formats in the TecCom Portal. Use it for exploring your possibilities to support your business processes. Moreover, you can easily understand which information you could expect as an orderer or respectively which information you could provide as a supplier depending on which message format you or your suppliers uses.
| Edifact | TecForm | TXML 4.1 | TXML 5.0 | ||
|---|---|---|---|---|---|
| Messages | Support for asynchronous messages (stock order / order response) |  |
|
|
|
| Synchronous messages (express order/ Inquiries) |  |
|
(with backorder option) |
(with backorder option) |
|
| Availability of business rules on inquiry/order | Format can be partly supported by TA business rules | Format can be partly supported by TA business rules | Format supports all TecAlliance Standards | Format support newest Txml5 TecAlliance Standards | |
| Handling of delivery related fields | Delivery date handling in requests | Per default date is being handled as arrival date | Per default date is being handled as arrival date Enables time range definition by dispatch modes |
Enables time range definition by dispatch mode Date omittable |
No need for delivery dates anymore because dispatchmodes have delivery date ranges, but buyer can define exact delivery dates and Txml5 business rules clearly define outcome. |
| Request for delivey options | |
|
|
|
|
| Delivery date handling in responses | Responses can include multiple delivery dates Supports delivery increments |
Date gets not returned | Responses can include multiple delivery dates Supports delivery increments |
TXML4 equivalent but additionally exact business rules define expected outcome. Clear separation of delivery and dispatch dates | |
| Delivery date agreement | Not supported | Depends on supplier interpretation (traffic lights) |
Possibility for mutual agreement | clear standard rules | |
| Requested delivery date is displayed in the response | Not supported | Not supported | can be returned (not yet supported by OMP) |
can be returned | |
| Available number of dispatch modes | 1 for asynchronous messages (stock orders) / NA for synchronous messages | 1 for asynchronous messages (stock orders) / 7 for synchronous messages | 1 for asynchronous messages / 7 + tillNine/tilTwelve/tillEighteen (not yet supported by OMP) | 4 for asynchronous messages / 14 synchronours dispatchmodes. New standard! | |
| Possibility for backorders permission by buyer | Supported for asynchronous messages (stock orders) / NA for synchronous messages | Supported for asynchronous messages (stock orders) / NA for synchronous messages | Buyer can potentially choose for each dispatch mode separately (if supplier support that option) | Buyer can potentially choose for each dispatch mode separately (if supplier support that option) | |
| Returning divergent delivery addresses in response | final delivery address returned for asynchronous messages / NA for synchronous messages | Not supported | Final delivery address returned (not yet supported by OMP) | Final delivery address returned | |
| Information availability | Error messages/warnings/information | Not supported | 1 header & 1 line level | Multiple on header and line level | Multiple on header and line level |
| Additional free text information from the supplier | Possible on header level | Possible on header level | Possible on line and header level | Possible on line and header level | |
| Technical information, measurments weights and volume | submittable in freetext | submittable in freetext | submittable in freetext | detailed transmission possible |
¶ Overview of the message evolution
