E1: XMLP: Report Definition (RD) Job Submission and Printing Sequence
Last updated on MAY 30, 2017
Applies to:JD Edwards EnterpriseOne Tools - Version 9.1 and later
Information in this document applies to any platform.
In some instances, it is required to print the RD job output in the same sequence in which they are submitted. For example, consider the below scenario:
The warehouse confirms order A, B and C. The interface launch invoice print three times for the orders A, B and C. The desired outcome is that invoice of order A, B and C are printed in the right order in which they are submitted.
The print invoice batch is launched on a single-threaded, so the jobs are processed serially by the UBE engine. Even if the batch queue processes the batch sequentially, the XMLP kernel processes that produce the RD output appears to be asynch. If the order A has 100 rows and order B has only 1 row, it happens that invoice of order B is printed before order A because the corresponding RD job for order B is processed faster.
Is it possible to make sure that the RD outputs are sent to the printer in the same sequence in which they are submitted?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms