The Z tables are files used to interface external interfaces into
JDEdwards , A Z table will usually correspond with the file you are
interfacing. For example to interface data into the G/L you would populate
the file F0911Z1. For each Z file there is also corresponding on-line
programs to view and update the files on-line as well as Batch programs
which will convert the Z file to their corresponding production files.
The advantage to this approach is that you populate as much
information as you can to the Z files. The JDEdwards batch program will
verify the integrity of the data and populate any missing data into the
corresponding fields using the defaults from the data dictionary.
Hope this helps.
University of Windsor
Sent by: email@example.com
23/01/2004 12:16 PM
Please respond to
JDELIST One World Developers Discussions <firstname.lastname@example.org>
To add a bit more info to Michael's reply.... Z-Tables can be processed BOTH Inbound and Outbound. So you can import data from a 3rd Party Software System into OneWorld/EnterpriseOne or you can export Data from OneWorld/EnterpriseOne into a 3rd Party Software System.
Many of the programs associated with Interoperability use the MBF on the Inbound side. This can be done day-to-day, minute-to-minute or just once for Data Conversion upon cutover from a legacy system.
On the Outbound side you will find many Applications, for example R31410 or P48013, with Processing Options that you can set to automatically populate the Z-File outbound whenever the Application adds, changes or deletes the Master Record in the Table. You should also find that you can create a "before" and "after" image of the File so you can see what has changed.
The spin-off to this is that they can be used for Audit Trails!