Many of the configuration tables contain columns that are of the same function. Rather than explain them for each table repetitively we will discuss the column function in this section as its function applies to all tables in the same way.
Standard Check Box Column
This column is used to identify a mapping line as being from the standard mappings that are provided by Thomson Reuters as pre-delivered content. As a customer you will not be able to check this field in the configuration tables. The field can be ignored for your purpose. Notice in the standard version of the table all the lines in this view have the box checked. This is a tool that will make it easier for debugging your system and also to allow for updates in the future. Rows marked as standard will be updated with software updates. Rows that are not marked as standard will not be changed with a software update thereby leaving your custom configuration intact.
Many of the configuration screens have a Sort Order field. The system processes the line with the lowest Sort Order first and then the line with the next highest Sort Order and so on. The Sort Order field for customer updated tables must be greater than or equal to sequence 1000001 through 999999. Sort Order fields that are part of the standard tables use Sort Order sequence from 0 to 100000. This way customer configuration is of a higher sort number and will be used to override or augment the standard mappings that we provide as part of the standard setup.
For the Proxy only: The line with the lowest Sort Order is checked first to see if it is valid for the current situation. If it is valid then it is selected. If it is not valid then the line with the next highest Sort Order is checked and so on.
This check box column is used to turn on or off the line in the configuration table. If checked then the configuration is active. If the box is unchecked, then the configuration line will remain in the table for future use but it will not be used. This can be very helpful when debugging an error in the configuration or testing different options to solve a business need.
In this column you would first establish which journey you want to use for the new configuration. To choose the correct journey name, you would ask yourself if this field is part of what you want to send to the request data going to Determination or is it part of the data that will be coming back on the response. Is it data at the header level of a document or is it data stored at the line level? Is this an SD order, billing, PO, LIV invoice, or FI generated document, etc.?
With this column a system user can direct a specific configuration to only be applicable to a single route by entering the route name in this column. The mapping will then only be applicable if the listed route is used in the transaction.
With this column a system user can reduce the number of repetitive mapping lines if the same configuration is required for several routes within the same journey. In this case the user would first populate the route group table, then assign a list of routes to the route group, and then use this route group in the configuration table to assign the same value to the desired group of routes.
You would not use both the route name column on the same line as the route group column to designate the path of the transaction.
Configurations can also be limited by company code using this column to designate the applicable company code.
In this column you have the option to specify your configuration line to further limitation based on group of countries based on the creation and assignment of a country group name. To do this you would first create a country group name as noted in the Country Group table, and then assign a country or list of countries to the newly named country group in the country group assignment table.
This column is used to describe the mapping for ease of tracking and reference notes.
An asterisk (*) can be used as a wildcard for most of the columns indicating that any value is an allowed match.
The product column has been added (directly to the right of the Standard checkbox on some standard view tables) because of the release of the new Goods Movement Product that was re-designed to work with our new Integration approach. With many of our tables being shared by the two product offerings we need a way to segregate the table entries by product so that future updates to the product will not conflict and overwrite lines through the transport process. At this point you will see either “GM” for lines associated with the Goods Movement product and “GN” for lines that were added as needed for the Global Next Integration. As other products may be added to this new structure and table logic in the future, new product designators will be added to keep them straight and avoid any conflicts to future product release updates. You will not need to be concerned with this column as it is only used on standard setup (display only) views of the tables and is used internally in the upgrade transport creation process.