By default, the MapForce configuration files and the underlying MapForce processing logic reflects the base version of the TRADACOMS standard (931). Therefore, if you use this TRADACOMS version, customization of the TRADACOMS configuration files is not necessary. However, if you want to make changes to the existing configuration for any reason, it is possible to do so. Note that any changes made to the standard TRADACOMS configuration files will take immediate effect and will affect the way MapForce parses or writes TRADACOMS structures.
The MapForce configuration files applicable to TRADACOMS are stored in the following directory: C:\Program Files\Altova\MapForce2022\MapForceEDI\TRADACOMS. Should you need to make changes to the TRADACOMS configuration files, you can start by creating a sibling copy of the TRADACOMS directory, for example "TRADACOMS1", edit the directory permissions not to be "read-only", and then edit the files in it according to your custom requirements. All configuration files adhere to the XML syntax. Therefore, it is recommended that you use an XML editor to modify the files.
The EDI.Collection file contains a list of all messages in the current TRADACOMS configuration directory (for example, C:\Program Files\Altova\MapForce2022\MapForceEDI\TRADACOMS).
Any messages listed in the collection file become available for selection in the "Browse EDI Collections" dialog box when you add a TRADACOMS component to the mapping (Insert | EDI). Therefore, if you want to suppress any message type on this dialog box, comment out or remove their respective XML element from the EDI.Collection file.
For example, commenting out the following line makes the LPRHDR message type unavailable:
Defines the structure of the TRADACOMS component in MapForce (that is, elements that are surrounded by the Envelope sequence). This file is validated against a schema handled by MapForce internally, and it should not be edited.
This file defines the TRADACOMS codes and the values that they may contain, and is used for validation of input/output TRADACOMS files. You can add custom code lists to this file, if required.
This file defines the Segment, Composite and Field names of the TRADACOMS files, and is used when parsing a TRADACOMS file. Changes made to this file are global customizations, and apply to all segments and messages.
Defines the structure of a single TRADACOMS message. Changes made to this file are treated as local (inline) customizations.