Change 11iDescription
Type
Functional
Functional
Functional Multi-Org or multiple organization
access (MOAC) In Release 11i, when
one had to enter or process data for
multiple operating units, one had to
login to different responsibilities
because each responsibility could only
access one operating unit. If one was
managing Payables for Sweden,
Norway and Finland one needed to
define three different responsibilities.
Functional
R12 change
The new Oracle Sub-ledger
Accounting (SLA) architecture
allows users to customize the
standard Oracle accounting
entries .As a result of Cost
Management’s uptake of this new
architecture, users can customize
their accounting for Receiving,
Inventory and Manufacturing
transactions.
New page for viewing acquisition
cost to track freight &
miscellaneous delivery cost
components while receiving. Actual
delivery coats are tracked during
invoice matching.
Multi-Org or multiple organization
access (MOAC) In Release 12, one
would create a Security Profile and
assign as many operating units as you
required. One can tie that security
profile to a single responsibility using a
profile option called MO: Security
Profile. For example, you could assign
the security profile to the EMEA
Payables responsibility to allow that
responsibility to process invoices across
all three operating units.
Enhanced BOM setup screen and
WIP Material Requirement screen
that support materials having a
fixed usage irrespective of the job
size for WIP Jobs, OSFM lot-based
jobs, or Flow Manufacturing.
Functional New functionality that provides
flexibility to control the value of
component yield factors at WIP job
level. This feature allows the user to
include or exclude yield factor while
calculating back flush transactions.

Enhanced functionality for WIP Final

Completion, WIP Scrap Absorption,
PAC WIP Value Report, Material
Overhead Absorption Rule, EAM
work order, and PAC EAM Work
Order Cost Estimate Processor
Report.
Component yield functionality users
have the flexibility to control the
value of component yield factors
and use those factors for back flush
transactions. Of course if the yield
factor is not used, yield losses can
be accounted for using the manual
component issue transaction.
In this release, the job close
program and the job close variance
program are migrated from Pro*c to
PL/SQL. This enhancement provides
performance improvements but
does not change job close
functionality.
Oracle Cost Management processes
are enhanced to support the new
Ledger and Legal Entity
architecture. In this new
architecture, Ledgers replace Set of
Books. Each Operating Unit is
associated with a Primary Ledger.
 Multiple Ledger Entities can be tied
to a Ledger through the accounting
set up flow. The existing link
between Operating Unit and Legal
Entity is no longer be maintained.

Chang 11iDescription R12 change

e
Type
Techni 11i Reports R12 Reports
cal
Inventory Value Report Inventory Value Report – by Subinventory

Inventory Value Report – Warehouse Inventory Value Report – by Cost Group

Management

All Inventories Value Report All Inventories Value Report – by Subinventory

All Inventories Value Report – Average All Inventories Value Report – by Cost Group
Costing

All Inventories Value Report – Warehouse

Management

Elemental Inventory Value Report Elemental Inventory Value Report – by

Subinventory

Elemental Inventory Value Report – Elemental Inventory Value Report – by Cost

Average Costing Group
 Elemental Inventory Value Report –
Warehouse Management
Techni FORMS
cal Changed Windows or Pages
• Org Cost Group/Cost Type
Associations
• Accounting Period - Process
Status
• Average Cost Update
• Layer Cost Update
• Pending Transactions
• Periodic Cost Update
• Periodic Account Assignments
FORMS
Changed Windows or Pages
• Org Cost Group/Cost Type Associations
Use this window to select the Enable
Iterative Periodic Average Costing
check box for using IPAC. You can also
select the Perform Multiple Iterations
check box. This attribute determines
whether multiple iterations should be
performed until the tolerance is
achieved when inter-organization
transfers across cost groups are
processed. If this is not checked, then
only one iteration is performed.
• Accounting Period - Process Status
This window is the standard PAC
format. The Phase column displays the
status for Absorption Cost Processing
along with the status of Cost
Processing.
• Average Cost Update
The Average Cost update window is
used to update the average cost of an
item in a specific cost group in an
average costing organization. You can
run three types of Average Cost
Updates:
Specify the new cost
Specify the percentage change in the
cost
Specify the Value change
After the changes in this feature, you
can specify the Adjustment Quantity for
Value change.
This is a generic enhancement to
update inventory value change based
 on user-specified adjustment quantity.
• Layer Cost Update
The Layer Cost update window is used
to update the Layer cost of an item in a
specific inventory layer in a Fifo/Lifo
Costing organization. You can run three
types of Layer Cost Updates:
Specify the new cost
Specify the percentage change in the
cost
Specify the Value change
Use this window to specify the
adjustment quantity for value change.
This is a generic enhancement to
update inventory value change based
on user-specified adjustment quantity.
• Pending Transactions
The Pending Transactions window is
viewable from the Inventory
Accounting Periods window and must
display the Landed Cost Adjustment
interface records count.
• Periodic Cost Update
The Periodic Cost update window is
used to update the periodic cost of an
item in a specific legal entity, cost type,
and cost group in periodic costing
setup. You can run three types of
Periodic Cost Updates:
Specify the new cost
Specify the percentage change in the
cost
Specify the Value change
This window is modified to enter the
adjustment quantity for Periodic Cost
Update - Value Change.
• Periodic Account Assignments
The Periodic Account Assignments
window is used to set up the accounts

Techni REPORTS
cal • Purchase Price Variance Report
• Periodic Accrual Reconciliation
Report
• All Inventory Value Report
• Periodic Acquisition Cost Report
• Receiving Value Report
essential for the Periodic Average Cost
(PAC) distribution processor. The
Landed Cost Absorption account and
Landed Cost Variance account are
required to be set up for this feature if
any of the organization attached to the
cost group is LCM enabled.
This window is modified to add the
Landed Cost Absorption account and
Landed Cost Variance account.
New Window or Page Name
• Landed Cost Adjustments Interface
This window is used to:
Query Landed Cost Adjustment
interface records posted from the LCM
product
Find specific records based on LCM
shipment number, PO Receipt, PO
Receipt delivery, Inventory Item, and
other fields.
Edit and re-submit errored interface
records.
View pending landed cost adjustments
transactions and resubmit any
incorrect pending adjustment
transactions.
• Receiving Accounting Events
Query perpetual Receive Accounting
Events and corresponding accounting
distributions.
Find the accounting distributions for
specific Receive Accounting Events.
REPORTS
• Purchase Price Variance Report
The Purchase price variance report
(XML) displays the PPV value generated
by receiving transactions in inventory.
With delivery adjustment events being
created for landed cost management,
• Receiving Account Distribution further purchase price variance will be
Report generated against these events.
• Periodic Accrual Reconciliation Report
The Periodic Accrual Reconciliation
report is used to report the A/P accrual
balances.
• All Inventory Value Report
In the section for the receiving value,
the receiving cost is taken as of date
provided by the customer, and for LCM
enabled PO's, the cost also considers
the LCM adjustments done. The report
calls function RCV_AccrualUtilities_GRP.
Get_ReceivingUnitPrice to get the price
as of date.
• Periodic Acquisition Cost Report (XML)
The Periodic Acquisition Cost Report
(XML) displays the acquisition costs for
the receiving transactions. In an LCM
enabled organization, the acquisition
cost is calculated based on
unit_landed_cost of the receipt
transactions and recalculated every
time the landed cost for the receipt is
revised.
• Receiving Value Report
The receiving cost is taken as of the
date provided by the customer, and for
LCM enabled PO's, the cost also
considers the LCM adjustments done.
The report calls function
RCV_AccrualUtilities_GRP.
Get_ReceivingUnitPrice to get the price
as of date.
• Receiving Account Distribution Report
The Receiving Account Distribution
Report (XML) also displays the following
landed cost adjustment events:
Landed Cost Adjustment to Receipt

Changed Programs
• Periodic Acquisition Cost
Processor
• Periodic Acquisition Cost
Adjustment Processor
• Cost Manager
• Receiving Transaction Processor
• Periodic Cost Processor
Landed Cost Adjustment to Delivery
Asset
Landed Cost Adjustment to Delivery
Expense
New Concurrent Programs
• Compute Iterative Periodic Average
Cost Concurrent Program
• Landed Cost Adjustment Processor
• Periodic Distribution Processor
• Accrual Reconciliation Program –
Accrual Write-Offs
• IPV Transfer to Cost Update
• Period Close Validation
Changed Programs
• Periodic Acquisition Cost Processor
Computes acquisition costs based on
latest landed cost adjustments when
LCM is enabled. When LCM is not
enabled, acquisition cost adjustments
are based on AP invoice transactions as
in existing R12.1 functionality.
• Periodic Acquisition Cost Adjustment
Processor
Computes acquisition cost adjustment
based on the latest landed cost
adjustments when LCM is enabled.
When LCM is not enabled, acquisition
cost adjustments based on AP invoice
transactions as in existing R12.1
functionality.
• Cost Manager
The cost manager launches the Landed
Cost Adjustment processor every time
it runs. The processor is launched
conditionally, based on whether there
exist transactions in the interface table.
• Receiving Transaction Processor
 The receiving transactions table
(RCV_TRANSACTIONS) is populated
with the unit_landed_cost in addition to
the primary_unit_price (po price), for
LCM enabled shipments.
• Periodic Cost Processor
Periodic Cost Processor calculates and
creates the cost for each transaction in
a particular period ad cost group.
For LCM integration, the periodic cost
processor must:
Create mtl_pac_actual_cost_details with
the latest landed cost for PO Receipts
for LCM-enabled Purchase Orders.
For Periodic cost update transactions, if
the value change has been specified
and the primary quantity is also
specified, then if the current onhand is
less than the quantity specified, then
only apply the apportioned value to the
inventory. The remaining value should
go to onhand_variance_amount. The
Periodic Cost Updates with value
change and primary_quantity >0 would
now be processed before any cost
owned transaction in transaction
category of 2.5. That is, after the
periodic cost update for new cost or
percentage change(transaction
category=2) and before cost owned
transactions(transaction category=3)

Techni TABLES TABLES

cal • CST_PAC_INTORG_ITMS_TEMP
• RCV_ACCOUNTING_EVENTS
• CST_PAC_INTORG_ITMS_TEMP
(New Columns introduced in 12.0.6 version
are as follows:
PREV_ITR_ITEM_COST,
INTERORG_RECEIPT_FLAG,
INTERORG_SHIPMENT_FLAG,
 SEQUENCE_NUM,
DIFFERENCE,DIVERGING_FLAG)
• RCV_ACCOUNTING_EVENTS
(New Columns introduced in 12.0.6 version
are as follows:
QUANTITY_RECEIVED,
QUANTITY_INVOICED,
AMOUNT_RECEIVED,
AMOUNT_INVOICED)

VIEWS VIEWS
• RCV_RECEIVING_ACCT_DISTR_V • RCV_RECEIVING_ACCT_DISTR_V
(New Columns introduced in 12.0.6 version
are as follows:
TRANSACTION_DATE)
(For 12.1.1 version New column introduced
UNIT_LANDED_COST)

New Tables (12.1.1 version)

• CST_PAC_INTERORG_TXNS_TM
• CST_LCM_ADJ_INTERFACE
• CST_LCM_ADJ_TRANSACTIONS
• CST_LCM_RCV_TXN_GT
• CST_LCM_ACCOUNTS_GT
• CST_LCM_ADJ_ACCTG_INFO_GT
• CST_LCM_RAE_EVENTS_GT
• CST_LCM_MMT_GT
• CST_LC_INTERFACE_ERRORS
• CST_PAC_ITMS_ABSL_CODES

Tables Modified in 12.1.1 version

• MTL_CST_ACTUAL_COST_DETAILS
(This table is modified to store On hand
Variance Amount.)
• MTL_CST_LAYER_ACT_COST_DETAILS
(This table is modified to store On hand
Variance Amount.)
• RCV_ACCOUNTING_EVENTS
(This table is modified to store Landed Cost
absorption Account and Current Landed
Cost.)