EDI Batch Processing

7.6. EDI Batch Processing

Note! In release 23.1 and forward, the EDI component will no longer be a part of DXC SICS. #

EDI batches can be imported and processed on a regular basis using the Job Scheduler. This particularly useful when batches arrive overnight as the scheduler can import and process them before work starts next morning.

The EDI batch job has two modes:

  • Import and process new batches only
  • Import, process new and reprocess existing batches

In the first mode, only new batches are handled. If there are no new batches, nothing happens when the job is run.

In the second mode new batches can be imported and processed (though it is not a requirement), and all incomplete batches are reprocessed each time the job is run. Incomplete batches are those with the following statuses:

  • Unprocessed
  • Error
  • Partially processed

The same job is used for LIMNET and Joint Venture.

Create a New EDI Batch Job #

  • Follow the procedure for creating a scheduled job ( Job Scheduler)
  • Select EDI Batch in from the Job Step drop down list, and click Save
  • Highlight the EDI Batch step in Job Template Properties
  • Select parameters from the popup menu.

Parameters #

Parameters.png

There are three parameters for the EDI batch job

  • Inbox path
  • Archive path
  • Reprocess Existing Batches

The Inbox path is where you define the folder where batches to be imported can be found.

The Archive path is the folder to which batches are moved after import. To avoid importing the same batches repeatedly, it is important that Archive folder is not the same as the Inbox.

Reprocess Existing Batches - use this check box to select the mode required. If this option is selected, existing batches are reprocessed each time the job is run.

Additional Information #

The job can be scheduled to run weekly or daily at a fixed time, or to run more frequently. There is no facility to check the inbox and only run the job when a new batch is detected.

The job processes batches in the following primary order:

  • JV REBORD
  • JV RECLAM
  • JV RETACC
  • JV RESETT
  • LIMNET CLASS
  • LIMNET Signings
  • LIMENT Settlement

Number order: For LIMNET batches, the bureau order is ILU then LIRMA.

To avoid reprocessing batches that you know cannot be processed, you can select to ’exclude’ a batch from reprocessing by the scheduled job. This is done on the Find batch window, using the pop-up menu. Refer to P&C Find EDI Batches

Some LIMNET batches can be very large, and consequently take a long time to process. If a number of large batches are scheduled to be reprocessed, the job may take several hours to complete. Avoid scheduling the EDI batch job more frequently than daily if this is the case.

Example of an Automatic EDI Processing Setup #

Typically, you might want to import new batches whenever they appear in the inbox, but only reprocess the existing data once a day. To do this, create two EDI batch jobs.

The first job should use the correct inbox path, and be set to the first mode (import and process new batches only). This job can be scheduled with a frequency of, say, 30 minutes.

The second job should have the inbox folder set to a dummy folder that will NOT contain any batches. The processing mode should be to reprocess existing batches. This job should be scheduled to run at a fixed time once a day.