The trading partner database consists of three tables that contain information about the company, its trading partners, and the trade agreements that have been set up between them.
In the non-ODBC version, the company information is stored in an ASCII flat file, and the trading partner and trade agreement information are stored in Access tables and dBaseIII tables. (For map development, the program uses the data in Access tables, but at runtime the program uses the data in dBaseIII tables.)
In the ODBC version, the three tables can be stored in any ODBC-compliant database. The user must assign a data source name (DSN) that points to the trading partner database and use the appropriate ODBC driver for that specific database.
File |
Description |
|---|---|
wixset.dat |
Contains company information for non-ODBC databases. See details in Table 3-1. |
wixset |
Contains company information for ODBC databases. See details in Table 3-2. |
customer.dbf customer.mdb |
Contains trading partner information for non-ODBC databases. See details in Table 3-3. |
Contains trading partner information for ODBC databases. See details in Table 3-4. |
|
tradstat.dbf tradstat.mdb |
Contains trade agreement information for non-ODBC databases. See details in Table 3-5. |
tradstat |
Contains trade agreement information for ODBC databases. See details in Table 3-6. |
The log database contains information logged during the map execution. For non-ODBC users, transaction logging is written to one of two ASCII flat files—translog.in for inbound processing and translog.out for outbound processing. For ODBC users, transaction logging is written to one trlog table. The user must assign a data source name (DSN) that points to the log database and use the appropriate ODBC driver for that specific database.
File |
Description |
|---|---|
translog.in translog.out |
Contains transaction logging for non-ODBC databases. See details in Table 3-7. |
trlog |
Contains transaction logging for ODBC databases. See details in Table 3-8. |
The transaction log has one user-defined field (USERID_ENT) with a corresponding system variable (SYS_USER_FIELD), which can be used in any way the user wants.
For related information, see Chapter 4, “EDI Envelopes,” the System Variables chapter in the ECMap User Guide, and the ECRTP Reference Guide.
This chapter contains the formats for each of the files and tables in the two databases. The following information is included in the description of each format: Field Number, Field Name, Type, Width/Precision, and Description. The Description contains a textual explanation of the field contents and where applicable, an explanation of the relationship between the field itself, other fields in the database, EDI envelope fields, and related system variables.
The program actions involving database fields differ for inbound and outbound processing. Some important processing actions are highlighted in the following sections. See “In outbound processing” and “In inbound processing”.
