Making the alias data available to application maps
About this task
Every time the Message Manager export map runs, any changes to trade link information are updated and made available to the Message Manager system. It produces four files when it is run; each file contains information about each application partner, including:
- Alias Name
- User Defined 1
- User Defined 2
Each file contains the same data but the columns are ordered differently within the row and the rows are sorted differently within the file:
| Description | File Name | Row Sort Order |
|---|---|---|
| Alias Information by Partner ID | AliasByP.tsv | By ISA Address (X12) |
| Alias Information by Alias Name | AliasByA.tsv | By Alias Name |
| Alias Information by User Defined 1 | AliasBy1.tsv | By User Defined 1 |
| Alias Information by User Defined 2 | AliasBy2.tsv | By User Defined 2 |
The alias files are written to the Message Manager . tmgr_vn.n \mmgr\share directory.
The Message Manager does not use these files. They are provided to cross-reference information between your application's identification methods and the corresponding EDI addresses. For instance, you might use Alias Name to store your internal customer ID, account number, or client code. Using the appropriate alias files in your application maps, you could move easily between your internal coding systems and your EDI partner addresses.