Professional Documents
Culture Documents
This articles provides insight into the functionality behind the table
ASO_ORDER_FEEDBACK_T and information on how we regained 100GB space
by performing certain tasks.
Functional Analysis
This queue is built as soon the order is booked which happens in the private api that is
used to create orders: oe_order_pvt.process_order. This in turn calls the package
oe_service_util.notify_oc which builts the queue. This simple article addresses the
following questions:
Subscribers
The following programs and packages consume the queue when you run the
programs. If you do not run these programs obviously the queue grows as soon an
order is booked and never gets dequeued.
• Between Oracle Marketing and Fund & Budgets, the OZF queue is consumed,
depending on which program and version of applicatons is used. This basically
eats into the budgeted funds of the marketing campaign allocated in these
applications. These accruals come as price adjustments or promotions from
order management. Please make sure you take an expert’s opinion in these
applications for more informaton.
• CN queue is consumed when you collect orders to pay commission for the
orders that are booked. This obviously suggests of a business process where
booked orders are used as a source to pay commisssion to the sales force.
• When OKS queue is consumed, it creates a service contract (Service
Agreement or Extended Warranty or Warranty depending on the profile option
OKS: OM interface Contract Category setup) from order management when a
service item is associated to a line that creates/updates the install base. The
association of Service Item to the Inventory Items that is trackable in Install
Base is done using Service tab in the order lines.
How to contain the growth of this table if we do not have any consuming
application and what is the impact?
Obviously the simplest way to contain this is by disabling the subscribers in the
lookup type.But before doing so we should make sure we have no need to run the
programs that are mentioned above, otherwise it can cause issues with a number of
applications. If we have no business need to run the program, we can safely disable
them. This will stop further growth though you are entering new orders and booking
them.
What do we do with my existing data in the queue table if we do not have any
need to run the programs?
Please refer to the metalink note 181410.1 for more information on this.
What we did?
Following the instructions in the above note, first we dropped the queue. Then after
careful analysis we disabled the subscribers to this queue as we do not use them. Then
we recreated the queue.