Professional Documents
Culture Documents
EDI Processing
After all setup is complete, the outbound EDI processing performs automatically as shown in the
flowchart below for the 855 Sales Acknowledgement transaction. All outbound EDI transactions follow a
similar flow depending on the entered document. Purchase Order entry will trigger the 850, Shipment
entry will trigger the 856, Sales Invoice entry will trigger the 810.
Is EDI active
EDI 855 flag set to
and 855
No No Request
enabled for
this BP?
Yes
The current EDI status for any Sales Order, Purchase Order, Shipment, or Sales Invoice can be
viewed on the corresponding document. A Misc. tab displays the EDI status. See examples below.
Sales Order
Shipment
Sales Invoice
Purchase Order
EDI BP Setup
The EDI BP Setup (GESXBG) function is used to enable specific business partners for particular EDI
transactions. An overarching EDI Active flag can be set for the selected BP. In addition, each of the
four supported EDI transactions can be activated separately for a given BP.
The second tab of the EDI BP Setup function can be used to hold specific identification parameters for
use with EDI.
The EDI Status Monitor displays the active inbound EDI transactions and their statuses.
o Shutting Down
o Restart in Progress
Query The request number as shown in the Task Management function
Status Indicates the current status of inbound EDI processing:
o Standby
o In Progress
o Finished
o Held
o Kill
o Aborted
o Error
o Immediate
o Warning
Processes The process number for the EDI monitoring process
When the EDI Status Monitor is started, a new process for each active EDI template is launched in
batch mode called XBEDI. In the example above, an XBEDI task is created for XBIMP810 and
XBIMP850.
The XBEDI process will periodically search the EDI directories defined in Inbound EDI Parameters
for any EDI files that match the format 810_# or 850_#.
When a file is found, that file is copied from the EDI directory to the import directory located on the
corresponding template (see below). NOTE: the EDI directory and template directory must be
different.
The files are copied in batches of 10 for efficiency. Once the files have been copied, a new batch
task is submitted to import the corresponding EDI files.
If the import is successful, a Purchasing Invoice (810) or Sales Order (850) is created.
If the import is not successful, the Status of the EDI task will be Error on the EDI Status Monitor.
The import file containing the error will be moved to the ERROR directory. It will maintain its same
name with .err added as the extension.
An error in one EDI file does NOT block the processing of other files.
To view the errors, go to the Request Management (AREQUETE) function and select the
corresponding EDI IMPORT process. Right click the line and select the Log button to display the
import log file.
Once an error has been fixed, the file may be renamed (the .err extension removed) and copied back
to the EDI directory for the EDI Status Monitor to reprocess. Or, the Import function may be run
manually by selecting the error file to be reprocessed.
Removing the error file(s) from the error directory resets the EDI Status Monitor status for that task
back from Error to In Progress.