Fusion Reference
All Oracle Fusion Cloud SCM Tables
Every table in the reference, sorted alphabetically. Use the jump-bar to skip to a letter, or filter by module, data class, and org column.
What the badges mean
- Product: EGP
- Product: the Oracle product family that owns the object — the short code Oracle's Tables and Views documentation lists as the object owner. Fusion is SaaS, so this isn't a database schema; there's no SQL path to the tables at all (see the quirks guide).
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
- BU-striped (ORG_ID)
- Rows are scoped to a business unit. The column is still named
ORG_ID, but in Fusion it means business unit, not the EBS operating unit — treat any migrated “operating unit” filter as suspect (see the quirks guide). - Per inventory org
- Rows are scoped to an inventory organization via
ORGANIZATION_ID— always pair it withINVENTORY_ITEM_IDon item-level joins (see the quirks guide). - Set / ledger / named-BU striped
- Some tables stripe by a named column instead of
ORG_ID: reference data set (SET_ID— see the quirks guide), ledger (LEDGER_IDon the GL journal tables), or a named business-unit column (PRC_BU_ID/REQ_BU_IDin procurement). The table page’s partition line names the column, and the generated SQL anchors on it — never treat these tables as unpartitioned. - Language-striped
- The table carries a
LANGUAGEcolumn (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to oneLANGUAGEor a join multiplies rows. - Date-effective
- This is an
_Ftable — one row per entity per effectivity window, withEFFECTIVE_START_DATEandEFFECTIVE_END_DATEpart of the key. Join without a window filter and every fact multiplies by history (see the quirks guide). - View
- This is a documented convenience view, not a physical table. Extract through the BICC data store that fronts its base objects instead of assuming the view lands as-is.
Structural facts — how the table is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
In field listings, the Key chip marks a key field — a member of the documented primary key or of a documented unique index.
FilterShowing 85 of 85 tables
Module
Tables starting with A
- AP_INVOICE_DISTRIBUTIONS_ALLPayables invoice distributions — the accounting grain under each line: one row per charged GL account with the amount, accounting date, period, and posted state; where AP spend meets the ledgerProduct: APtransactionfinancials
- AP_INVOICE_LINES_ALLPayables invoice lines — the goods/services, freight, tax, and prepayment rows under each invoice, carrying the amount, quantity, and the PO/receipt match pointersProduct: APtransactionfinancials
- AP_INVOICES_ALLPayables invoice headers — one row per supplier invoice, prepayment, or credit/debit memo, with the supplier, invoice number, amounts, payment status, and approval state; business-unit stripedProduct: APtransactionfinancials
- AR_CASH_RECEIPTS_ALLCash receipts — one row per receipt entered, with receipt number, date, amount, status, and the paying customer account; the cash side that payment schedules apply againstProduct: ARtransactionfinancials
- AR_PAYMENT_SCHEDULES_ALLThe open-receivables ledger — one row per installment of every transaction and receipt, restated as amounts due, applied, and remaining; the table AR aging actually readsProduct: ARtransactionfinancials
Tables starting with C
- CST_COST_BOOKS_BThe cost book master — book codes that attach to cost organizations to give multiple parallel cost representations of the same operationsProduct: CSTcontrolcost-management
- CST_COST_DISTRIBUTION_LINESThe debit and credit lines under each cost distribution — per cost element, with entered and ledger amounts and both the user-entered and final SLA-derived GL accountsProduct: CSTtransactioncost-management
- CST_COST_DISTRIBUTIONSCost distribution headers — one per costed transaction event, carrying the cost org/book, item, event class, GL date, and accounting state ahead of subledger accountingProduct: CSTtransactioncost-management
- CST_COST_ELEMENTS_BThe cost element master — the buckets (material, overhead, and so on) item cost decomposes into, striped by reference data setProduct: CSTcontrolcost-management
- CST_COST_ELEMENTS_TLThe cost element master's translation companion — per-language element descriptionsProduct: CSTcontrolcost-management
- CST_COST_INV_ORGSThe cost-org to inventory-org bridge — which cost organization costs each inventory org, with dated validity; an inventory org belongs to exactly one cost orgProduct: CSTcontrolcost-management
- CST_COST_ORG_BOOKSThe cost org + book association — the working grain of Fusion costing, carrying the ledger, currency, calendar, and whether accounting is created for the combinationProduct: CSTcontrolcost-management
- CST_COST_ORGS_VThe delivered view that enumerates cost organizations — the costing scope every CST table's COST_ORG_ID resolves to, with code, effectivity, and owning legal entityProduct: CSTviewcost-management
- CST_PERPAVG_COSTThe perpetual average cost history — recomputed transaction by transaction per cost org, book, item, valuation unit, and cost element; the latest row is the current averageProduct: CSTtransactioncost-management
- CST_STD_COSTSStandard cost records — the date-effective standard unit cost per cost org, cost book, and item (optionally per valuation unit), with publish statusProduct: CSTtransactioncost-management
- CST_TRANSACTION_COSTSThe actual cost attached to each costing transaction — one row per transaction, cost element, and expense pool per effective date; a complete cost history including every adjustmentProduct: CSTtransactioncost-management
- CST_TRANSACTIONSThe costed-transaction spine — inventory transactions after import into costing, exploded per cost org-book and stamped with cost status; what distributions and cost rows hang offProduct: CSTtransactioncost-management
Tables starting with D
- DOO_FULFILL_LINES_ALLFulfillment lines — the executable, shippable unit of an order line and the correct analytics grain for order-to-ship reporting, with the quantity lifecycle, schedule/actual dates, fulfillment org, and amountsProduct: DOOtransactionorder-management
- DOO_HEADERS_ALLThe sales order header — one row per orchestration order, carrying the order number, source-system references, sold-to customer, currency, and the status the whole order-to-cash cycle hangs off; business-unit stripedProduct: DOOtransactionorder-management
- DOO_HOLD_INSTANCESHold instances — one row per hold applied to an orchestration order, order line, or fulfillment line, with who applied and released it and when; the "why isn't this line shipping" tableProduct: DOOtransactionorder-management
- DOO_LINES_ALLSales order lines — the middle tier between the header and the fulfillment lines, carrying the item, ordered/shipped/fulfilled quantities, selling price, and line statusProduct: DOOtransactionorder-management
- DOO_ORDER_CHARGE_COMPONENTSThe price-waterfall detail — one row per price element (list price, discounts, net price, margin) under each charge, carrying the actual amounts in both charge and header currencyProduct: DOOtransactionorder-management
- DOO_ORDER_CHARGESThe price-waterfall charge header — one row per charge (product price, freight, fees) applied to a fulfillment line, classified by charge type, subtype, and price typeProduct: DOOtransactionorder-management
Tables starting with E
- EGP_CATEGORIES_BThe category master — one row per category with its user-facing category code and active window; categories are global and keyed by CATEGORY_IDProduct: EGPmasterproduct-master
- EGP_CATEGORY_SETS_BCatalog (category set) definitions — control level, the multiple-assignments flag, hierarchy option, and the default category new items inheritProduct: EGPcontrolproduct-master
- EGP_COMPONENTS_BItem structure component lines — one row per component per operation per effectivity window, child of the structure header, with quantity, yield, and WIP supply behaviorProduct: EGPmasterproduct-master
- EGP_ITEM_CAT_ASSIGNMENTSThe item-to-category assignment — one row per item, organization, catalog (category set), and category; the bridge every category rollup crossesProduct: EGPmasterproduct-master
- EGP_ITEM_REVISIONS_BItem revisions — one row per revision level of an item in an organization, with effectivity and implementation dates and the change-order line that introduced itProduct: EGPmasterproduct-master
- EGP_STRUCTURES_BItem structure (BOM) headers — one row per manufacturing or engineering bill per named variant, identified by BILL_SEQUENCE_ID, with common-structure sharing and change-order linkageProduct: EGPmasterproduct-master
- EGP_SYSTEM_ITEMS_BThe item master — one row per item per inventory organization, carrying the item number as a real column plus status, type, unit of measure, and the control flags for every functional area; every balance, transaction, and order line joins back to it on INVENTORY_ITEM_ID + ORGANIZATION_IDProduct: EGPmasterproduct-master
- EGP_SYSTEM_ITEMS_TLThe item master's translation companion — item description and long description in every installed language, one row per item per organization per language; the only place the item description existsProduct: EGPmasterproduct-master
Tables starting with F
- FND_LOOKUP_VALUESThe generic lookup view — every seeded and user-defined code list (lookup type + code) with its meaning and description, one row per code per installed language; the decode target for coded columns across every moduleProduct: FNDviewfoundation
- FUN_ALL_BUSINESS_UNITS_VThe delivered view that enumerates business units — the BU domain later waves' documents stripe on — with the legal entity, primary ledger, and default set each BU resolves toProduct: FUNviewfoundation
Tables starting with G
- GL_CODE_COMBINATIONSEvery chart-of-accounts segment combination (CCID) stored once — the account string behind each SEGMENTn set; accounting distributions and journal lines reference accounts through CODE_COMBINATION_IDProduct: GLmasterfoundation
- GL_JE_HEADERSGeneral ledger journal headers — one row per journal within a batch, with the ledger, category, source, period, currency, posting status, and running debit/credit totalsProduct: GLtransactionfinancials
- GL_JE_LINESGeneral ledger journal lines — the debit/credit grain: one row per line with the account combination, entered and accounted amounts, effective date, and the drill-back link to subledger accountingProduct: GLtransactionfinancials
- GL_LEDGERSOne row per ledger — currency, calendar, chart of accounts, and accounting convention; the ledger context business units and subledgers resolve toProduct: GLmasterfoundation
Tables starting with H
- HR_ALL_ORGANIZATION_UNITS_FThe date-effective master list of every organization unit — business units, inventory orgs, departments, and legal-entity org rows all resolve their ids here, one row per org per effectivity windowProduct: PERmasterfoundation
- HZ_CUST_ACCOUNTSThe customer account — the commercial (selling) relationship layered on a party; one party can carry several accounts, each with its own account number, status, and typeProduct: HZmastercustomers
- HZ_CUST_ACCT_SITES_ALLCustomer account sites — an account's use of a party site (address); the layer order and invoice addresses hang off, with bill-to/ship-to/market purpose flagsProduct: HZmastercustomers
- HZ_CUST_SITE_USES_ALLSite uses — the business purposes (bill-to, ship-to, statements) assigned to each customer account site; the bottom TCA layer, and the id AR transactions actually point atProduct: HZmastercustomers
- HZ_LOCATIONSThe location master — the physical postal address itself (street, city, postal code, country, coordinates), shared by every party and account site that points at itProduct: HZmastercustomers
- HZ_PARTIESThe party master — one row per person, organization, or group in the trading community, with the party number, type, status, and a denormalized identifying address and primary contact point; the top of the four-layer customer modelProduct: HZmastercustomers
- HZ_PARTY_SITESParty sites — the link between a party and a location, carrying the site number, name, addressee, and mailstop; one party can have many sites and one location can serve many partiesProduct: HZmastercustomers
Tables starting with I
- INV_ITEM_LOCATIONSThe stock locator master — the physical bin/row/rack positions inside a subinventory, with the human-readable locator name, capacity limits, and pick sequencingProduct: INVmasterinventory
- INV_LOT_NUMBERSThe lot master — definition, genealogy (parent lot), grade, and the origination/expiration/retest dates for every lot, keyed by item + organization + lot numberProduct: INVmasterinventory
- INV_MATERIAL_TXNSThe material transaction ledger — one row per inventory movement or cost update, classified by transaction type, action, and source type, with quantity, date, and the document reference that caused it; the reconciliation backbone for every stock questionProduct: INVtransactioninventory
- INV_ONHAND_QUANTITIES_DETAILThe on-hand balance detail — receipt-level slices of stock per item, org, subinventory, locator, and lot, consumed in FIFO order as material issuesProduct: INVtransactioninventory
- INV_ONHAND_QUANTITIES_SUMMARYPre-aggregated on-hand at the item + location grain, maintained automatically in step with the detail table — the ready-made balance EBS never hadProduct: INVtransactioninventory
- INV_ORG_PARAMETERSInventory organization parameters — one row per inventory org, holding the short org code, the item-master org it points to, its business unit and legal entity, and the org's locator/lot/serial control defaults; the org list every ORGANIZATION_ID resolves againstProduct: INVcontrolfoundation
- INV_RESERVATIONSFirm reservations tying a demand source (a sales order line, most commonly) to a supply source (on-hand or expected supply) for an item in an org, optionally pinned down to subinventory, locator, and lotProduct: INVtransactioninventory
- INV_SECONDARY_INVENTORIESThe subinventory master — each row a named section of stock within an organization (stores, staging, receiving, rejects) with its asset/expense nature, tracking and reservability controls, and replenishment sourceProduct: INVmasterinventory
- INV_SERIAL_NUMBERSThe serial number master — definition and current position (status, org, subinventory, locator, lot) of every serialized unit, with manufacturing and shipping lifecycle datesProduct: INVmasterinventory
- INV_TRANSACTION_TYPES_BThe transaction type list — seeded and user-defined types, each mapping to the transaction action and source type that together classify material transactionsProduct: INVcontrolinventory
- INV_TRANSFER_ORDER_HEADERSTransfer order headers — the orchestration document for internal material moves within or between organizations, carrying the order number, originating process, and requisitioning business unitProduct: INVtransactioninventory
- INV_TRANSFER_ORDER_LINESTransfer order lines — the actionable grain carrying item, source and destination organizations, the requested/shipped/received/delivered quantity lifecycle, dates, and the transfer priceProduct: INVtransactioninventory
- INV_TXN_REQUEST_HEADERSMovement request (move order) headers — the user-visible request number, type, status, and required date for requests to move material within an organizationProduct: INVtransactioninventory
- INV_TXN_REQUEST_LINESMovement request lines — each row requests moving a quantity of an item from a source to a destination subinventory (or account), individually statused, allocated (quantity detailed), and deliveredProduct: INVtransactioninventory
Tables starting with P
- PO_DISTRIBUTIONS_ALLPO accounting distributions — how each schedule's quantity charges out: destination type and org, deliver-to, the GL charge account, project costing columns, and the requisition distribution it fulfillsProduct: POtransactionprocurement
- PO_HEADERS_ALLPurchasing document headers — one row per purchase order or agreement (standard, blanket, contract), with supplier, buyer, currency, and the document status; striped by the procurement business unitProduct: POtransactionprocurement
- PO_LINE_LOCATIONS_ALLPO schedules — one row per shipment schedule (or blanket price break) with need-by/promised dates and the system-maintained received/accepted/rejected/billed quantity buckets; the workhorse grain for open-PO analyticsProduct: POtransactionprocurement
- PO_LINES_ALLPurchasing document lines — the item, category, unit price, and ordered quantity per line; the line quantity is the rollup of its schedules one level downProduct: POtransactionprocurement
- POR_REQUISITION_HEADERS_ALLRequisition headers — the requisition number, preparer, status, and justification; where demand enters procurement before it becomes a purchase orderProduct: PORtransactionprocurement
- POR_REQUISITION_LINES_ALLRequisition lines — item, quantity, price, need-by date, destination org, and suggested supplier per line; carries the keys of the resulting PO header, line, and schedule once sourcedProduct: PORtransactionprocurement
- POZ_SUPPLIER_SITES_ALL_MSupplier sites — the transactable endpoints purchase orders and payments point at, one row per supplier address per procurement business unit, with purchasing/pay/RFQ purpose flags and payment defaultsProduct: POZmasterprocurement
- POZ_SUPPLIERSThe supplier master — one row per supplier with the supplier number, type, business relationship level, and tax attributes, backed by the trading community architecture through its party idProduct: POZmasterprocurement
Tables starting with R
- RA_CUSTOMER_TRX_ALLReceivables transaction headers — one row per invoice, credit memo, debit memo, or bill receivable, with the transaction number, type, dates, customer account and site-use pointers, and currency; business-unit stripedProduct: RAtransactionfinancials
- RA_CUSTOMER_TRX_LINES_ALLReceivables transaction lines — mixed row kinds under each transaction: LINE rows carry the goods/services amounts, TAX and FREIGHT rows attach to their parent line, CB rows carry chargebacksProduct: RAtransactionfinancials
- RCV_SHIPMENT_HEADERSReceipt and expected-receipt headers — one row per supplier ASN, receipt, in-transit shipment, or RMA return, grouped by receipt source; carries the receipt number, supplier, and expected/shipped datesProduct: RCVtransactionreceiving
- RCV_SHIPMENT_LINESReceipt/shipment lines — one row per item per shipment header with cumulative shipped and received quantities, line status, the source-document pointers, and the default putaway destinationProduct: RCVtransactionreceiving
- RCV_TRANSACTIONSThe receiving event ledger — one immutable row per receiving action (receive, inspect, transfer, deliver, correct, return), chained to its prior step by parent transaction id; the event-grain truth behind every receipt quantityProduct: RCVtransactionreceiving
Tables starting with W
- WIE_OPERATION_TRANSACTIONSThe shop-floor product ledger — one row per movement of primary-product quantity through operation dispatch states: completions, moves, scrap, reject, and their reversalsProduct: WIEtransactionmanufacturing
- WIE_RESOURCE_TRANSACTIONSThe resource charge ledger — labor and equipment usage charged (or reversed) against work order operation resources, with full lineage down to the resource assignmentProduct: WIEtransactionmanufacturing
- WIE_WO_OPERATION_MATERIALSComponent requirements of each work order operation — one row per material line with per-assembly usage, total requirement, supply method, and running issued/allocated/picked countersProduct: WIEtransactionmanufacturing
- WIE_WO_OPERATION_RESOURCESLabor and equipment requirements for each work order operation — usage rate, required and actual usage, assigned units, and charge behaviorProduct: WIEtransactionmanufacturing
- WIE_WO_OPERATIONS_BWork order operations — one row per execution step with its sequence, work center, count-point behavior, and the quantity balances sitting at each dispatch stateProduct: WIEtransactionmanufacturing
- WIE_WORK_ORDERS_BThe work order header — the primary product being built, the work definition version it was created from, the build quantity, status, and planned/actual execution datesProduct: WIEtransactionmanufacturing
- WIS_RESOURCES_BThe production resource master — each row an equipment or labor resource that performs operations at work centers, unique per plant by resource codeProduct: WISmastermanufacturing
- WIS_WD_OPERATIONS_BWork definition operations — the ordered, date-effective steps of a work definition, each pointing at the work center where it runs and optionally at a reusable standard operationProduct: WISmastermanufacturing
- WIS_WD_VERSIONSWork definition versions — dated snapshots of the version-controlled header attributes, with the approval status gating which version execution usesProduct: WISmastermanufacturing
- WIS_WORK_CENTERS_BThe work center master — a physical station inside a work area where a type of operation happens; deliberately thin, with names in the translation companion and capacity on the resource assignmentsProduct: WISmastermanufacturing
- WIS_WORK_DEFINITIONSThe work definition header — one row per item + definition-name combination in a plant, binding the produced item, the item structure supplying material requirements, and the work method; the Fusion successor to the routingProduct: WISmastermanufacturing
- WSH_DELIVERY_ASSIGNMENTSThe assignment bridge between shipment lines and deliveries — also the carrier of the packing hierarchy through its parent-detail pointer; a line reaches its delivery only through this tableProduct: WSHtransactionshipping
- WSH_DELIVERY_DETAILSThe atomic shipment line — one row per shippable unit of demand, tracking the source order line, item, warehouse, and the requested/picked/shipped quantity lifecycle through pick, stage, and ship confirmProduct: WSHtransactionshipping
- WSH_NEW_DELIVERIESThe delivery (shipment) header — a named grouping of shipment lines shipped together, carrying the ship-confirm and actual ship/delivery dates, carrier, ship method, waybill, and weight/volume rollupsProduct: WSHtransactionshipping