Trading Partner Code List

Here is the definition of Code List from the documentation:

"Sterling Integrator uses code pairs in code lists to identify items in transactions between two or more trading partners. A trading partner code list consists of one or many pairs of code values containing a sender code and a receiver code. Each code pair has one description and up to four additional codes relating to the pair. Code lists are dynamic and are stored in a database."

You can always export it and use in another system.

Map Code List

Code List that we use in a map is something completely different, it is not saved in a database, there is no interface to add or change it through GIS dashboard, and that kind of Code List is saved in a map only. It is used only to check if a specific value from a field is listed in a code list allocated to that field. If you apply 'Use Code' Standard Rule to one field, then value from that field will be validated against the values from that Code List, and if it does not match, error will be thrown.

Here is a part from the documentation:

"The Use Code standard rule enables you to use code lists to validate the contents of a field and use as a reference to look up an associated description for a field. A code list is a list of values and their corresponding descriptions. Code lists seldom change and are stored within the map itself. A field with a Use Code standard rule enables values to be either checked against or selected from the codes in a specified code list. Code lists are typically used to qualify another field.
You create code lists in the Map Editor as part of a map and manage them through the Map Editor. You can import and export code lists and copy and paste code lists between maps.

Code lists differ from the trading partner code lists used by the Select standard rule. Map Code Lists are generally static and stored within the map file."