Menu Access
Character: EDI 4 7
GUI: EDI; System
Use this function to load incoming transaction sets into the transaction set holder
file for the range of file locations specified. This will allow you to review the
transaction sets, and to print out the details of the transaction sets that are loaded in
before they are processed by the Receive EDI Data
function.
Before loading transaction sets into the transaction set holder file, the system checks to
see if the EDI system information record
has been created. If it hasn't, you will receive an error message and will be returned to
the menu.
For each file location that is processed, the system checks to see if the input directory
is not locked (i.e., in use). The system also checks to see if the backup directory to use
for the file location has been created.
If your communications script has created multiple files to be input then you can set up
the file location to receive them from the same input directory. You may do this by
putting wildcards in the input file name when setting up the file location. Please
see the EDI File Location Maintenance function
for more information.
Error messages will be displayed if the system is unable to load transaction sets into the
transaction set holder file due to the conditions described above, and will proceed to the
next file location to process.
If everything is all right, then the system proceeds to load in transaction sets from the
input file specified for the file location being processed into the transaction set holder
file. The system assumes that each transaction set line in the input file is on a separate
line (i.e., is unwrapped). If you are using a UNIX-based system, use the unwrap.sh shell
script, located in the edi directory, and supplied with the EDI system, to unwrap the
input file. If you are using an MS-DOS (i.e. MS-DOS, Windows 95, Windows NT) based
system, use the unwrap.bat batch file, located in the edi directory and supplied with the
EDI system, to unwrap the input file. Otherwise, check to see if the Value Added Network
(VAN) you are dealing with can unwrap the data. If they are unable to do this for you,
then please contact GTR support.
For each transaction set that is loaded in, the system attempts to determine the version
and transaction set used by the transaction set from the GS (functional group header), and
ST (transaction set header) segments respectively. If the system is unable to determine
the version and/or the transaction set used, then the system will not save the transaction
set in the transaction set holder file.
If you are dealing with trading partners that use TDCC version numbers in the GS segment
(e.g., X1/1), set up a translation table called EDIVERS using the EDI Translation Table Maintenance function, to
translate the TDCC version to the appropriate ANSI X.12 version. For example, if TDCC
version X1/1 corresponds to ANSI X.12 version 002001, you would set up a record using the
EDI Translation Table Maintenance for table code "EDIVERS" with a
"From" value of X1/1, and a "To" value of 002001.
In addition to storing the information from the transaction set itself, the system also
stores the ISA (interchange control header), GS (functional group header) and ST
(transaction set header) segments along with the transaction set being processed. Please
note that the system does not save any SE (transaction set trailer), GE (functional group
trailer) or IEA (interchange control trailer) segments contained in the input file.
If the element delimiter used for a given transaction set line has a character (i.e.,
ASCII) value lower than 32 or higher than 126, then the system will use Control-A (ASCII
value 1) as the element delimiter, if possible. Otherwise, the delimiter is left
unchanged. This is done so that transaction set lines do not cause problems when they are
displayed or printed.
Each transaction set that is loaded will be assigned a unique transaction set
identification number. This identification number is used by the Edit EDI Data On Hold and other functions to refer to
a given transaction set in the transaction set holder file. The transaction set
identification number assigned to a particular transaction set is displayed on the report.
When the system has completed processing the input file, it makes a backup in the backup
directory specified for each file processed within each file location. The system uses a
file name in the following format:
i-<date>.<num> (e.g., i-960220.002)
The <date> is the system date in "YYMMDD" format, and <num> is a
three-digit sequential number. If the system is unable to make a backup copy, an error
message displays. Otherwise, the name of the backup file used is printed on the report.
In the event where the transaction sets needed to be reloaded into the transaction set
holder file due to a system crash, or hardware failure, the EDI Data File Manager function should be used to
append the backup file to the input file.
There is an option to put loaded transaction sets "on hold". Placing a
transaction set "on hold", will ensure that the transaction set is not processed
by the Receive EDI Data function. Transaction sets
should be put on hold if you need to enter information manually for that transaction set
before it is processed, or if you want to control when the transaction set is processed by
the Receive EDI Data function.
If needed, functional acknowledgements can be generated immediately after the transaction
sets have been loaded into the transaction set holder file for the range of file locations
specified. This is useful when trading partners require that documents must be
acknowledged within a specific time frame after they have been retrieved from the Value
Added Network (VAN) or trading partner's host computer.
Please note that you do not have to load the input file into the transaction set holder
file before using the Receive EDI Data function, as
this function allows you to process transaction sets from the input file directly.
Last updated October 20, 2006