Selected Cost Management Bug Fixes in This Update

This update includes some bug fixes that can change the way Oracle Cost Management works. This isn't a full list of all the bug fixes in this update. This list includes the bug fixes that can cause a noticeable change in application behavior.

Period End Validations Return Correct Count Based on Profit Center Business Unit
Before update 25B, the period end validations return the exception count for the shipping organization instead of the selling organization in the case of internal drop ship order flow. After you update to 25B, the period end validations provide the correct exception count for all cost organizations belonging to a profit center business unit for these flows:

  • Internal drop ship
  • Customer drop ship with internal drop ship
  • Customer drop ship with internal drop ship and global procurement

In the case of the flows listed here, the exception count is for a cost organization and cost book combination:

  • Simple sales order
  • Simple customer drop ship
  • Customer drop ship with global procurement
  • Direct sales order issue

By default, this exception data is for current period and the two immediate past periods. You can control this duration by setting the profile option Validate Pending Receivable Transactions (CST_PENDING_AR_TXNS_LATEST_PERIODS). If you set the value to 5, then the current period and the immediate past four periods will be considered.

Setting the Profile Option

  1. In the Setup and Maintenance work area, click the Manage Profile Options task.
  2. Click Add to create the profile option with these values:
    • Profile Option Code: CST_PENDING_AR_TXNS_LATEST_PERIODS
    • Profile Display Name: Validate Pending Receivable Transactions
    • Application: Cost Management
    • Module: Cost Management
  3. Click Save.
  4. In the Setup and Maintenance work area, click the Manage Cost Accounting Profile Options task.
  5. Search for the newly created profile option (CST_PENDING_AR_TXNS_LATEST_PERIODS) and enter a number for the profile value at the Site level.

Oracle reference: 37226462

Selective Cost Rollup for Configured Items Uses Latest Purchase Order or Work Order

Before update 25B, selective cost rollup for configured items wasn’t rolling up the costs for purchased items. After you update to 25B, selective cost rollup for configured items uses the latest purchase order or work order. You must set the rollup scope to Unprocessed Purchase Orders and Work Orders before rolling up the costs.

Oracle reference: 37349139

Steps to Enable

You don't need to do anything to enable this feature.