CMCLCW Layer Cost Worker Performance, Processing Small Number Of Transactions (Doc ID 2883124.1)

Last updated on JULY 28, 2022

Applies to:

Symptoms

On : 12.2.9 version, Performance

ACTUAL BEHAVIOR
---------------
Layer Cost Worker poor performance, only processing a small number of transactions per execution

We have a very large backlog of uncosted material transactions in the queue. When the Cost Manager runs only one Layer Cost Worker is launched.
It only runs for several seconds and then completes successfully. However, it is only processing a small number of uncosted transactions.

Last week several users submitted about 70,000 Inter-organization Transfer (Direct) which are still being processed by the Layer Cost Worker.
These transactions are what is causing the slowdown. However, it is not the transactions fault, the Cost Manager and Layer Cost Worker should be able to handle the load.
The settings for the Cost Manager are the default, Run every 5 minutes and 200 rows per worker.
Also, why is only 1 Layer Cost Worker being spawned by the Cost Manager when there are so many transactions needing processing?

We it was due to the large number of Inter-organization Transfers (Direct) which were performed last week.
We have never done so many of them at one time before to notice this issue

The items involved in the Inter-organization Transfer (Direct) were all serial controlled. Last week was the first time we ever had to process any large volume of transactions for serial controlled items. I this has something to do with the slow performance. Last Wednesday there were probably 70,000 of these executed on that day.

EXPECTED BEHAVIOR
-----------------------
 Expected Layer Cost Worker better performance

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1. Responsibility: Inventory Super User
2. Wait for Cost Manager to run. Cost Manager completes normal
3. Navigation:   Inventory ,Material Transactions:
4. Check Material Transactions:
5. Transactions -> Material Transactions
   Default date from and to:  Today’s date, Find
6. Lines complete with status Error
7. Check Material Transactions "Reason, Reference" Tab
8. There are very large backlog of uncosted material transactions in the queue
9. When the Cost Manager runs only one Layer Cost Worker is launched.

Changes

Cause

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