Structuring Interface Tables
Each JD Edwards EnterpriseOne transaction uses a set of interface tables. Some files share a common set of interface tables. The interface table name is based on the JD Edwards EnterpriseOne application table name and has Z1 as a suffix. For example, if the application table is the F4211 table, the interface table is the F4211Z1 table.
Use the these guidelines to determine the based-on table:
Inbound is based on the application table that is updated with data from the interface table.
Outbound is based on the application table that has data extracted from it and placed in the interface table.
Both the inbound and outbound directions of an internal transaction within a system use a single set of interface tables. For example, for a sales order in the Sales Order system, the inbound customer order (850) and the outbound order acknowledgment (855) share a set of interface tables.
If the interface table is used for both inbound and outbound transactions, the based-on table should be the same application table. In the Sales Order example with an inbound customer order and an outbound order acknowledgment, the detail interface table is based on the F4211 table.
If the interface table exceeds 250 columns or has a record length greater than 1968, an additional interface table is needed for the remaining columns. Columns in the additional interface table should contain infrequently used data. The additional interface table is named after the primary interface table with a letter, starting with A, after the Z1 suffix. For example, if the primary interface table is F4211Z1, the additional table is F4211Z1A.
The beginning of the table has these columns, which act as control fields:
User ID (EDUS) (key field)
Batch Number (EDBT) (key field)
Transaction Number (EDTN) (key field)
Line Number (EDLN) (key field)
Document Type (EDCT)
Transaction Type (TYTN)
Translation Format (EDFT)
Transmission Date (EDDT)
Direction Indicator (DRIN)
Number of Detail Lines (EDDL)
Processed (EDSP)
Trading Partner ID (PNID)
Action Code (TNAC)
You must use the key structure previously discussed.
The end of the table has the these columns, which are reserved for user and audit fields:
User Reserved Code (URCD)
User Reserved Date (URDT)
User Reserved Amount (URAT)
User Reserved Number (URAB)
User Reserved Reference (URRF)
Transaction Originator (TORG)
User ID (USER)
Program ID (PID)
Work Station ID (JOBN)
Date Updated (UPMJ)
Time of Day (TDAY)
The middle of the table has all of the columns from the based-on application table, excluding user reserved and audit field columns. An exception to this is when the interface table is near the 250-column limit or the 1968-record length limit. In this case, columns from the application table that most likely will not be needed should be excluded.
Prefixes for the table columns are SY for the header and SZ for the detail.
Change or match interface tables, such as a cash receipt or purchase receipt, might require additional columns that correspond to user input capable controls on an interactive form.
A header table is not required for every transaction.