My Oracle Support Banner

ESTIMATED SCRAP ABSORPTION Transactions And WIP ESTIMATED SCRAP Transactions Are Created With Sysdate Instead Of Cost Cutoff Date (Doc ID 2387872.1)

Last updated on APRIL 18, 2018

Applies to:

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

Symptoms

On : 12.2.4 version, WIP Costing

ACTUAL BEHAVIOR
---------------
Estimated Scrap Absorption is created by 'Operation Yield Processor' automatically and it will use current date to create this transaction.
Cost Manager doesn't consider cost_cut_off date on Estimated Scrap Absorption and Estimated Scrap Reallocation transaction types.

EXPECTED BEHAVIOR
-----------------------
New functionality for Cost Manager to consider transaction_date as sysdate on Estimated Scrap Absorption and Estimated Scrap Reallocation transaction types.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Testcase performed for transaction types Estimated Scrap Absorption and Estimated Scrap Reallocation transaction.
2. Observed that cut off date does not consider the two transaction types and these are created despite cut off date setup.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, cut off date will not work as expected for Estimated Scrap Absorption and Estimated Scrap Reallocation transaction types.

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!


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