Menu Access
Character: EDI 7
GUI: System
This menu contains functions that are used intermittently, such as purges and batch processes. Click on the menu item to learn more about each item. Some of the items have already been explained in relation to their corresponding functions within some of the other menus.
Purges document triggers.
Purges functional acknowledgements from the system.
When the Electronic Data Interchange (EDI) system is being used to generate data,
restore data, etc., the system locks the directories being used to ensure that the files
being manipulated are not corrupted. When a function is finished using a directory, it
unlocks it so that other users can work.
In addition to locking directories, the EDI system locks the transaction set holder file
when the Receive EDI Data function is run in order to ensure that only one user is
processing data from the transaction set holder at a time. As with the directories, the
system unlocks the transaction set holder file when it is finished using it.
In the event of a system crash, or other hardware failure, the system may not be able to
remove these "lock" files, and as a result, users may not be able to use the EDI
system, even though no one is using it. The Remove EDI Lock Files function removes the
lock from either a directory or the transaction set holder file, so that the EDI system
can be used.
NOTE: This function can cause very serious problems if used incorrectly, or at the wrong
time. Therefore, it is recommended that this function be password protected, and only
experienced personnel be allowed access.
The user is prompted for the type of lock file to remove. Use the |LEFT/RIGHT ARROW| keys
to select the type of lock to remove, or enter "T" to unlock the transaction set
holder file, or "F" to unlock the directories associated with a file location.
If the user chooses to unlock a directory associated with a file location, the user is
prompted for the file location to use, after which, the user is prompted for the directory
to unlock. Use the |LEFT/RIGHT ARROW| keys to select the desired directory to unlock, or
enter "I" for the input directory, "O" for the output directory or
"B" for the backup directory.
If the transaction set holder file or directory chosen is not locked, then an error
message is displayed; otherwise, the system proceeds to unlock the transaction set holder
file or specified directory as appropriate.
When the Receive EDI Data function is run, the
system temporarily creates quotes, orders, A/P vouchers, etc. in the system to hold the
incoming transaction set. If the transaction set is valid, then the system assigns a
quote, order or voucher number etc., to the document that is creating. Otherwise, the
system removes the document created from the transaction set from the database.
In the event of a system crash, or other hardware failure, the Receive EDI Data function may not be able to remove the
documents created by an incoming transaction set if the transaction set has errors in it,
or is not processed in its entirety. As a result, there may be a loss of integrity in the
database due to the fact that invalid documents may exist in your database. The Remove
Orphan EDI Documents function removes all documents created by the Receive EDI Data function that were either in error or
incomplete, and as a result, restores integrity to the database.
Please note that this function is EXTREMELY dangerous if used incorrectly, or at the wrong
time. Therefore, it is recommended that this function be password protected, and that only
experienced personnel be allowed to access this function.
There are no parameters for this function. Once the function is executed, the function
will remove all offending documents from the system.
Will do the same as the Mass EDI Doc Status Code Change, but for Acknowledgement triggers.
Use this function to remove unwanted EDI message records (864 transaction set) from the
system, such as those that have already been read. The partner and control numbers to be
removed can be specified, as well as whether the user wants the details to be printed.
If details are to be printed, the system will only print the trading partner, GS control
and transaction set control numbers, as well as the date and time received of the EDI
message being purged. The total number of message lines purged is displayed at the end of
the report.
Use this function to remove unwanted EDI purchase order acknowledgement records from the system, such as those that have already been sent by EDI. The acknowledging partners, GS (functional group) control numbers, and ST (transaction set) control numbers to be removed can be specified, as well as whether the user wants the details to be printed.
Use this function to removed transaction sets that are no longer needed from the transaction set holder file. You can specify the range of transaction set identification numbers to purge, and whether or not you want details to be printed.
Use this function to generate the programs required to edit transaction set lines in
the Edit EDI Data On Hold function. You can
specify the range of versions, transaction sets, and segments to use when generating
"edit" programs. You can also indicate whether or not you wish to overwrite any
"edit" programs that already exist.
Before attempting to generate "edit" programs, the system checks to see if the
edit program directory, as defined by the EDI
System Information Maintenance function, has been created. If it hasn't, then the
system will attempt to create the edit program directory. If the edit program directory
cannot be created, you will receive an error message, and you will be returned to the
menu.
The system then proceeds to create all the "edit" programs required within the
range of versions, transaction sets and segments requested. If an "edit" program
directory already exists for the version and segment being processed, the system will not
regenerate the "edit" program unless you choose to overwrite existing programs.
The system automatically compiles the "edit" programs that it generates, and
saves the compiled programs in the edit program directory.
You will receive a status message to indicate whether or not a particular "edit"
program was generated successfully, and whether or not the "edit" program
compiled without errors. If there are problems, then please contact your System
Administrator if you having directory and/or permissions problems. If your System
Administrator is unable to resolve the problem, then please contact GTR support.
It should be noted that if you do not generate "edit" programs using this
function, then the Edit EDI Data On Hold function will attempt to generate the
"edit" programs required to edit a particular transaction set line.
Use this function to remove suspended payments that are no longer needed, or that will not be converted into cash receipts (i.e. system payments) from the system. You can specify the range of payment receipt numbers, customer numbers and transaction dates, as well as whether or not to print details of the suspended payments being purged.
Obsolete program.
Last update October 20, 2006