The TRADACOMS Component in MapForce

www.altova.com Print this Topic Previous Page Up One Level Next page

Home >  Data Sources and Targets > EDI > TRADACOMS >

The TRADACOMS Component in MapForce

In MapForce, the TRADACOMS component replicates the structure of a generic TRADACOMS transmission (with optional batching feature), while retaining all features common to other MapForce EDI-related components.

tradacoms_component

A sample TRADACOMS component in MapForce

The topmost item of the component, File, displays the name of the TRADACOMS interchange file being processed or generated by the component.  "Default" indicates that no file has been assigned yet. The File/String ( btn_file_string ) button displays advanced features common to all file-based MapForce components. It provides, among other options, the ability to read or process multiple files dynamically (for more information, see Processing Multiple Input or Output Files Dynamically ).

 

The "Envelope" and "Interchange" structures are generic for all MapForce EDI-related components. Where applicable, they provide the ability to process multiple interchanges within the same MapForce component.

 

The STX and END structures are specific to the TRADACOMS format. They denote the "Start of Transmission" and "End of Transmission" segments, respectively.

 

The BAT and EOB structures are specific to the TRADACOMS format. They denote the "Start of Batch" and "End of Batch" segments, respectively. Such segments are applicable if you are reading data from a TRADACOMS interchange file with batches, or if you want to generate a file with batches. Since there may exist multiple batches in the same transmission, a Batch sequence is available as parent of the BAT sequence.

 

The Message_Code structure (Message_INVFIL, in the sample above) corresponds to the TRADACOMS "file". The Select EDI Message Types button ( excel1-compicon ) opens a dialog box where you can change the type of the file (for example, "Invoice File", "Orders File", and so on). By virtue of the existing MapForce EDI functionality, you can also include multiple file types in the same component. Note, however, that the TRADACOMS specification recommends one file and one type of file in each interchange transmission.

 

Any TRADACOMS file ("Invoice File", in this example) contains a Header Message, one or more Details Messages, and a Trailer Message. In the component above, these are the INVFIL (Invoice File Header), INVTLR (Invoice File Trailer), the VATTLR (File VAT Trailer) and multiple INVOIC (Invoice Details) messages.

 

As with any other MapForce component, the input and output connectors (small triangles) displayed on each side of the component provide the ability to map each individual data element or segment to or from other data types or formats supported by MapForce. Likewise, when you move the mouse over any item on the component, you can view additional information about it (such as the minimum and maximum allowed occurrences), provided that tips are enabled from the View | Show Tips menu.

 

Finally, you can change these and other settings by double-clicking the component head and opening the Component Settings dialog box (see EDI Component Settings ). Note that this dialog box is generic for all EDI-related component types and, thus, some of the options might not be applicable to TRADACOMS.


© 2019 Altova GmbH