My Oracle Support Banner

CTO COST TYPE DEFAULT LOT SIZE CANNOT BE UPDATED FROM A SUBASSEMBLY ITEM ATTRIBUTE UPDATE (Doc ID 2318430.1)

Last updated on FEBRUARY 18, 2019

Applies to:

Oracle Cost Management - Version 12.2.5 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.5 version, Cost Maintenance

ACTUAL BEHAVIOR
---------------
The CTO cost rollup for a configured item is not recognizing a change to a subassembly's standard lot size in the item master costing attributes. A supply chain cost rollup (pending cost) for the same top level will not recognize a change either. Per all of the Oracle documentation, it appears that the standard lot size is copied from the item master to the costing tables at the time of organization assignment. After that the only change can be made in the costing form, not in the item attributes. However, it was found that a changed value in the item master will be copied to the costing form when a supply chain cost rollup is run for the lower level subassembly item only and the parameter" Lot Size Option" is set to "Use Factor of Standard Lot Size". It does not copy a changed value when the top level supply chain cost rollup is run.

EXPECTED BEHAVIOR
-----------------------
 Customer could not found a way to utilize lot sizes greater than 1 with this cost type.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Responsibility: Cost Management
2. Navigation Path: Menu Tools >Requests
3. Submit Cost Rollup


Cause

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
Symptoms
Cause
Solution
References


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