How To Avoid The Trigger Of Document Set If The Pick Slip Conc. Program Runs Into Error
(Doc ID 2729260.1)
Last updated on NOVEMBER 29, 2020
Applies to:Oracle Shipping Execution - Version 12.2.4 and later
Information in this document applies to any platform.
On : 12.2.4 version, Pick Release
User defined Document set is attached to this particular pick slip. The document set has "pick Slip Report", "XX report", Packaging Slip".
For example 7000 Pick Selection List Generation - SRS are scheduled out of these 7000 Pick release programs, almost 4000+ runs into warning because no order got qualified. Upon warning, the system submits the Document set attached to this particular pick slip.. Now the 4000 Warning "Pick Selection List Generation - SRS" , submits additional 3 programs from the document set 4000 *3 =12000 concurrent requests. This is clogging the Concurrent manager and adversely impacting system performance.
Is there a configuration or patch or way to avoid the submission of the document set if the ""Pick Selection List Generation - SRS" ends into warning?
Remember that the Document set is attached on the respective pick release program for each warehouse.
How to avoid the trigger of Document Set if the pick slip conc. program runs into error ?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document