Key Reference Tables in Oracle Cost Management Cloud

 

Key Database Tables in Oracle SCM Cost Management

This blog provides a list of the key database tables from Oracle SCM Cost Management module. In Oracle Fusion SCM, the Cost Management module plays a critical role in ensuring accurate valuation of inventory, recording of manufacturing costs, and generation of accounting entries for all supply chain transactions. To support this, Oracle Fusion maintains a robust set of database tables that capture transaction details, costing data, accounting distributions, and configuration setups.

Below is a list of the key database tables and views used in Oracle Fusion Cost Management. These tables form the backbone of the costing engine — linking Inventory, Procurement, Manufacturing, and Accounting data to derive financial impact for every supply chain event.

Each table serves a specific role, whether it’s storing transaction-level cost entries, maintaining item cost profiles, managing cost books, or tracking accounting events and journal lines. Understanding these tables is crucial for functional consultants, developers, and support analysts.

 

Sr. No.	Module	Table Name	Description
1	Cost Management	CST_STD_COSTS	Stores the information pertaining to standard costs.
2	Cost Management	CST_COST_DISTRIBUTIONS	This table contains the distribution header information for the costing transactions. Distribution processor creates data in this table before it is accounted into SLA
3	Cost Management	CST_COST_DISTRIBUTION_LINES	This table contains the distribution details such as debits, credits and the distribution amounts.
4	Cost Management	CST_COST_BOOKS_B	This table contains the cost book codes. Cost book is an independent entity and does not require/depend on any other setup.
5	Cost Management	CST_COST_ELEMENTS_B	This is the base table of all cost elements defined in cost management. These cost elements help in providing break-up of item cost into various elements.
6	Cost Management	CST_COST_PROFILES_B	This table contains the cost profiles setup by the user.
7	Cost Management	CST_DEFAULT_COST_PROFILES	This table contains the default cost profiles which are identified by Cost Organization, Cost Book and Category. Default cost profiles are setup in context of cost organization and cost books.
8	Cost Management	CST_COST_ORG_BOOKS	This table contains the Cost organization and cost book association. It describes the Ledger, calendar, currency, accounting attributes of the defined cost-org book.
9	Cost Management	CST_VAL_UNITS_B	This table contains the valuation unit codes. Valuation units are created in context of cost organization, cost book and valuation structure.
10	Cost Management	CST_TRANSACTIONS	These are costing transactions. The imported inventory transactions are converted to costing transaction type, exploded for Cost Org - Book and stamped with suitable costing setup like item cost profile, valuation unit and costing method etc.
11	Cost Management	CST_TRANSACTION_COSTS	This table holds the actual cost of receipts and issues for transactions in parent table CST_TRANSACTIONS. It holds the entire history of what each actual cost was after every adjustment, and the cost is stored in its entirety on each adjustment instead of being stored in incremental costs.
12	Cost Management	CST_RESOURCE_TRANSACTIONS	This table will contain the manufacturing resource transactions that are staged for cost processor. The transactions are staged for each cost book within the cost organization associated to the plant where the resource was consumed. In addition to the resource transactions from manufacturing, this entity will also contain the logical transaction for the WIP revaluation corresponding to the resource rate changes.
13	Cost Management	CST_RESOURCE_COSTS	This entity contains the breakup of resource cost at cost element, expense pool level, which will be used to create accounting distributions for these resource transactions.
14	Cost Management	CST_EXPENSE_POOLS_B	This table contains the information about expense pools.
15	Cost Management	CST_INV_TRANSACTIONS	This is Costing's Inventory Transactions table and is the source of all inventory transactions within costing. It contains all transactions that are imported into Costing through the interface and also transactions that are created by costing's engines during processing.
16	Cost Management	CST_PERPAVG_COST	This table contains the current and Historical perpetual average Cost
17	Cost Management	CST_TRANSFERS	Transfer Layers tracks quantity flow of in transit transactions.
18	Cost Management	CST_VU_ONHAND_VALUATIONS	This table contains inventory valuation with quantities at the VU level and the costs at total level.
19	Cost Management	CST_TRADE_EVENTS	This table contains the trade event transactions from the FOS system.
20	Product Data Hub	EGP_SYSTEM_ITEMS_B	This table contains the item information.

 

Understanding Period-End Accruals in Oracle Fusion

 

Demystifying Period-End Accruals in Oracle Fusion

 

In any financial system, ensuring expenses are recognized in the correct accounting period is critical to maintaining accurate financial reporting. This is where period-end accruals come into play.

In Oracle Fusion, Period-End Accruals are used to account for goods or services that have been received but not yet invoiced by the supplier at the end of an accounting period. This ensures that expenses are recorded in the correct period, even if the supplier invoice is processed later.

 

How It Works?

When a purchase order (PO) is raised and goods are received, the system records the receipt transaction. However, if the supplier invoice has not yet been entered or matched, Oracle Fusion automatically creates an accrual entry during the period-end process.

This accrual temporarily recognizes the expense and liability for received items until the actual invoice arrives.

When the supplier invoice is eventually created and matched to the receipt, the accrual is reversed — ensuring there is no double counting of expenses.

 

Why It Matters?

• Ensures financial statements reflect true expenses of the period.
• Supports compliance with accrual-based accounting standards.
• Automates the matching and reconciliation process, reducing manual errors.

 

Process Overview:

The Create Un-invoiced Receipt Accruals process creates pairs of debit and credit accounting entries to accrue for purchase order receipts that are:

• Designated as not to accrue at receipt
• Receipt hasn’t been matched with an invoice in accounts payable

 

 

Here are the steps involved in the process-

 

1.      Create PO with Accrue on Receipt as N

This is applicable only for Expense Destination Type POs.

2.      Receive the PO.

3.      Invoice the PO for partial quantity OR do not create the invoice for any quantity - so that Qty Received > Qty Invoiced.

4.      Run following ESS jobs to transfer transaction data to Receipt Accounting application

a.      Transfer Transactions from Receiving to Costing

b.      Transfer Costs to Cost Management  -> This program transfers Invoice accounting data from Payables to Receipt Accounting application

5.      Run the ESS Job -  Create Uninvoiced Receipt Accruals with below parameter

·       Bill to Business Unit - Respective Bill to BU as per the PO

·       Accrual Run Mode - Select Report or Accounting

Report Mode is used to view the Period End Accrual Amount any time before the End of Period.

Accounting Mode to be used only for the Final Run at the End of Period but before to that ensure the Payables and Period is Closed.

·       Accounting Period - Respective Period

·       Period End Accrual Cutoff and Accounting Date - Last Date of the Period

·       Include Purchase Order Status - 'All'

 

 

6.      Run the Job - Uninvoiced Receipt Accrual Report -> To View the Un-Invoiced PO Details

 

 

7.      Run Create Accounting job for Subledger Application as Receipt Accounting

The accounting date for the distribution is same as the accrual cut-off date entered while creating un-invoiced receipt accruals.

8.      Close the Current GL Period.

9.      If the Accrual Reversal is not set to Automatic in the Subledger Options for Receipt Accounting, then Run the Job - Create Accrual Reversal Accounting to generate the Reversal Entries.

This completes the cycle for period end accrual process for one period. Repeat the same for the next period.

 

·      The receipt accounting distributions are staged in the Receipt Accounting subledger and posted to General Ledger only after you run the Create Accounting process.

·       Each time you run the Create Uninvoiced Receipt Accruals process, data is created for reporting and then you can review it by running the Uninvoiced Receipt Accrual Report.

 

Few Important Points:

• Ensure all receiving transactions for goods and services you received during the period are interfaced to Receipt Accounting.

• Enter and match all invoices you received during the period for your receipts and accrual entries.

• By default, the Create Uninvoiced Receipt Accruals process only considers purchase orders that are open or in closed status for receiving to compute period end accrual amounts.

• If you run the Create Uninvoiced Receipt Accruals process multiple times, ensure that each run of the process is with the same period end accrual cutoff and accounting date.

• The list of values for accounting period doesn't require the accounts payable period to be closed.
• However, it’s strongly recommended that the corresponding accounts payable period is closed before running the process in the Accounting mode.

• Optionally you can create a cost accounting profile option with the name CST_ENABLE_AP_PERIOD_STATUS_VALIDATION, to enforce the practice of allowing period end accrual to be booked only after the accounts payable period is closed.

• Run the Uninvoiced Receipt Accruals Report after running the Create Uninvoiced Receipt Accruals process to analyze your uninvoiced receipts.
• The report shows the  data based on the selection criteria with which the Create Uninvoiced Receipt Accruals process was run, thus ensures you know exactly what you accrue and for what amount.

• The Create Uninvoiced Receipt Accruals process can be run as many items as you need.
• After you run the process in the Accounting run mode, the subsequent runs of the job can only be in the Accounting mode, and the job can't be run in the Report mode for the respective period.
• Use appropriate Accrual cut-off date to avoid mismatch in the periods in which accrual is booked between the ledgers.
• In case of Multiple Ledger Scenario with different period types like Calendar months for Primary Ledger and 4-4-5 type for the Secondary Ledger, there is always a possibility that the period end date will be different for both the ledgers
• In such cases, use the last date of the period which is common between ledgers as cut-off date.
• Final Close PO to avoid generating the Period End Accrual Entries which would be no more Invoiced in future.
• Final Closing old POs on a regular basis helps to improve the process performance.
• You can control defaulting of accrue at receipt flag based on setup at the BU level in Manage Common Options for Payables and Procurement.
• If ”Expense Accruals” is set to “Period end”, All expense PO schedules will have the accrue on receipt flag un-checked. This option cannot be overridden
• If ”Expense Accruals” is set to “At Receipt”, All expense PO schedules will have the accrue on receipt flag checked by default. Buyers can override this flag at the PO schedule level.

 

 

Best Practice:

·     It’s recommended to run the Period-End Accrual Process in Procurement or Payables before closing the accounting period.

·     Regular reconciliation and cleanup of aged accruals help maintain accurate reporting and prevent overstated liabilities.

·        Create Job sets to ensure all transactions from source systems  (Receiving, PO, Invoices) are interfaced.

·       Review the un-invoiced receipt accruals report on a regular basis during the period to identify discrepancies in estimates and avoid any last-minute surprises.

·     Review Subledger period end validation exceptions to ensure there are no unposted or incomplete accrual or accrual reversal journals.

·       Use ledger options to restrict GL period close if there are any unposted accrual or accrual reversal journals in the system.

·       The period end accrual event created by receipt accounting is set to Auto reverse journals.

·       Do not use the GL reversal feature for reversing Uninvoiced receipt accruals journals to avoid double accounting.

Oracle Inventory Cloud – Essential Tables Reference

 

Key Database Tables in Oracle SCM Inventory Cloud

This blog provides a list of the key database tables from Oracle SCM Inventory Cloud module. These tables form the backbone of transactional and master data in Oracle Cloud Inventory and are essential for reporting, troubleshooting, integrations, and custom development.

 

Sr. No.	Module	Table Name	Description
1	Product Data Hub	EGP_SYSTEM_ITEMS_B	Stores the Item Number and other attributes of the item
2	Inventory	INV_MATERIAL_TXNS	Stores the record of every material transaction or cost update performed in Inventory
3	Inventory	INV_MATERIAL_TXNS_TEMP	Stores the open pick quantity
4	Inventory	INV_TRANSACTIONS_INTERFACE	Stores the interface transactions performed in Inventory
5	Inventory	INV_RESERVATIONS	Stores the Item Reservation details
6	Inventory	INV_ONHAND_QUANTITIES_DETAIL	Stores the quantity on hand information by control level and location
7	Inventory	INV_ORG_PARAMETERS	This table stores the inventory organization parameters defined in Oracle Inventory.
8	Inventory	INV_SECONDARY_INVENTORIES	This table stores the subinventory details in each inventory organization defined in Oracle Inventory.
9	Inventory	INV_SECONDARY_LOCATORS	This table  stores all locators within a subinventory for a specific item.
10	Inventory	INV_ITEM_LOCATIONS	This table stores the definition table for stock locators.
11	Inventory	INV_LOT_NUMBERS	This table stores the definition and expiration date of all lot numbers in inventory.
12	Inventory	INV_SERIAL_NUMBERS	This table stores the definition of all serial numbers in inventory.
13	Inventory	INV_SUPPLY	This table stores the incoming supply information for an organization.
14	Inventory	INV_TXN_REQUEST_HEADERS	This table stores the movement request (move order) headers.
15	Inventory	INV_TXN_REQUEST_LINES	This table stores the movement request (move order) lines.
16	Inventory	INV_TRANSFER_ORDER_HEADERS	This is the Transfer Order header table.
17	Inventory	INV_TRANSFER_ORDER_LINES	This is the Transfer Order lines table.
18	Inventory	INV_TRANSFER_ORDER_DISTRIBS	This is the Transfer Order line distributions table.
19	Inventory	INV_TRANSACTION_REASONS_B	This is the base table for inventory transaction reasons. It stores the list of all transaction reasons across organizations.
20	Inventory	INV_TRANSACTION_TYPES_B	This table contains the seeded and user defined transaction types.

 

·       Demand Quantity details are not captured in any of the Inventory Tables.

·       However, you can review the reservation quantity as well as the Demand Source in the INV_RESERVATIONS table.