My Oracle Support Banner

Purge Messages Program Does Not Work Correctly When Using The Sales Order As A Parameter (Doc ID 3010066.1)

Last updated on MARCH 14, 2024

Applies to:

Oracle Order Management - Version 12.2 and later
Information in this document applies to any platform.


There are issues with the Purge Messages program when using the Sales Order as a parameter.
Let us go by example. If there are 100 records in the table for 10 orders and 1 order that we are interested in truncating has only 8 messages.
The code can be written 2 ways:
1. Query all the 100 records and then in the loop truncate the 8 records for the order (by comparison), we wanted to truncate the messages for.
2. Query only the 8 records (with a where condition in the cursor) and then truncate them all (8 records) in the loop.

Right now the code is written as described in the point number 1.
That will cause all the records in the table to be pulled first as part of the cursor, and that will never complete, because our tables are too huge with millions of records and hence the program will hang.

The issue can be reproduced at will with the following steps:
1. Order Management Super User, Vision Operations (USA)
2. Navigate to: Reports, Requests > Run Requests
    Select name = Message Purge
      Enter parameter for Order Number Low
      Enter parameter for Order Number High
    Submit request




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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.