EBS Reference
All Oracle EBS 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
- Schema: INV
- Schema: the Oracle product schema that owns the table (INV, ONT, WSH, PO, BOM, WIP, MRP, MSC, AR, AP, GL, HR, APPLSYS) — tells you which product family the object belongs to, not who can query it.
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
- OU-striped (ORG_ID)
- Rows are scoped to an operating unit. A landed extract carries every operating unit’s rows — filter or join on
ORG_ID, and don’t confuse it withORGANIZATION_ID(see the quirks guide). - Per inventory org
- Rows are scoped to an inventory organization (plant or warehouse) via
ORGANIZATION_ID— a different partition from OU-striped tables (see the quirks guide). - 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 (see the quirks guide). - View
- This is an APPS-schema convenience view, not a physical table. Extract the base tables it joins instead — views can be slow at scale and aren't guaranteed stable across patches.
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 primary-key field.
FilterShowing 104 of 104 tables
Module
Tables starting with A
- AP_INVOICE_DISTRIBUTIONS_ALLSupplier invoice distributions — one row per GL-account allocation of an invoice line; the spend-to-account grain payables accounting posts fromSchema: APtransactionfinancials
- AP_INVOICE_LINES_ALLSupplier invoice lines — the R12-new layer between header and distributions, carrying line type, amount, and the purchase-order and receipt matching referencesSchema: APtransactionfinancials
- AP_INVOICES_ALLSupplier invoice headers — standard invoices, credit/debit memos, prepayments, and expense reports share the table by type, with amounts, payment status, and the liability accountSchema: APtransactionfinancials
- AP_SUPPLIER_SITES_ALLSupplier sites — the purchasing/pay/RFQ site records per supplier, one row per site per operating unit, with the site code and control flags; where supplier data meets MOAC stripingSchema: APmasterpurchasing
- AP_SUPPLIERSThe R12 supplier master — one global row per supplier with the supplier number, type, and control flags, backed by the trading community architecture through its party idSchema: APmasterpurchasing
- AR_CASH_RECEIPTS_ALLCash receipts — one row per customer or miscellaneous receipt with amount, date, status, and reversal detail; application detail against invoices lives in companion tablesSchema: ARtransactionfinancials
- AR_PAYMENT_SCHEDULES_ALLThe open-receivables engine — one row per transaction installment AND one row per receipt, carrying original and remaining amounts, due date, and closure state; what aging, DSO, and collections analytics readSchema: ARtransactionfinancials
Tables starting with B
- BOM_BILL_OF_MATERIALSThe compatibility view legacy queries know BOM headers by — a window onto the structures table under the familiar 11i nameSchema: BOMviewbom-costing
- BOM_COMPONENTS_BSingle-level bill components — one row per component per operation per effectivity window, with usage quantity, yield, supply type, and the supply subinventory shop-floor issues pull fromSchema: BOMmasterbom-costing
- BOM_DEPARTMENTSThe department (work center) master per inventory organization — the places operations happen, with class, location, and the scrap accountSchema: BOMmasterbom-costing
- BOM_INVENTORY_COMPONENTSThe compatibility view legacy queries know BOM components by — an APPS-schema access layer over the physical components tableSchema: BOMviewbom-costing
- BOM_OPERATION_RESOURCESResources required per routing operation — usage rate, assigned units, and the basis and charge types that drive costing, capacity, and schedulingSchema: BOMmasterbom-costing
- BOM_OPERATION_SEQUENCESRouting operations — one row per operation per routing per effectivity window, department-assigned, with the count-point and backflush controls that decide where work is recordedSchema: BOMmasterbom-costing
- BOM_OPERATIONAL_ROUTINGSThe routing header — one routing per assembly item, organization, and alternate designator, with the common-routing pointer and the completion subinventory finished assemblies land inSchema: BOMmasterbom-costing
- BOM_RESOURCESThe resource master — machines, labor, and outside processing, plus overhead and material sub-elements sharing the table (the cost element discriminates), each with its UOM, charge behavior, and absorption accountSchema: BOMmasterbom-costing
- BOM_STRUCTURES_BThe bill-of-material header — one bill per assembly item, organization, and alternate designator (manufacturing or engineering), with the common-bill pointer that lets organizations share one structureSchema: BOMmasterbom-costing
Tables starting with C
- CST_COST_TYPESThe cost type master — the seeded Frozen, Average, and Pending types plus user-defined types for rollups and simulations, with the fallback pointer rollups use for missing costsSchema: BOMcontrolbom-costing
- CST_ITEM_COST_DETAILSThe cost-element breakdown under each item cost — one row per element, level, and department/operation/resource contribution; where a rolled-up cost's ingredients liveSchema: BOMmasterbom-costing
- CST_ITEM_COSTSThe item cost header — one row per item, organization, and cost type, carrying the total unit cost and its five cost-element buckets plus this-level/previous-level splitsSchema: BOMmasterbom-costing
Tables starting with F
- FND_FLEX_VALUE_SETSValue set definitions for key and descriptive flexfields — one row per value set with its validation type, format rules, and size limits; the configuration that gives SEGMENTn columns their meaningSchema: APPLSYScontrolfoundation
- FND_FLEX_VALUESThe valid values belonging to each flexfield value set — one row per segment value, with enabled/date-effectivity flags and the parent-value linkage dependent and rollup hierarchies useSchema: APPLSYScontrolfoundation
- FND_LOOKUP_VALUESThe generic lookup table — every seeded and user-defined code list (lookup type + code) with its meaning and description, one row per code per language; the decode target for coded columns across every module (EBS's analog of JDE's UDC table)Schema: APPLSYScontrolfoundation
Tables starting with G
- GL_CODE_COMBINATIONSEvery chart-of-accounts segment combination (CCID) stored once — the account string behind each SEGMENTn set; inventory accounting distributions and every journal line reference accounts through CODE_COMBINATION_IDSchema: GLmasterfoundation
- GL_JE_HEADERSJournal headers — one row per journal within a batch, carrying ledger, source, category, period, posting status, and control totals; where every subledger's accounting landsSchema: GLtransactionfinancials
- GL_JE_LINESJournal lines — the atomic debit/credit rows against account combinations; the source of trial-balance and account-activity analyticsSchema: GLtransactionfinancials
- GL_LEDGERSOne row per ledger, tying together the four Cs — currency, calendar, chart of accounts, and accounting convention; the R12 replacement for the 11i sets-of-books table, and the ledger context every operating unit resolves toSchema: GLmasterfoundation
Tables starting with H
- HR_ALL_ORGANIZATION_UNITSThe master list of every organization unit of every classification — business groups, legal entities, operating units, inventory organizations, HR organizations — across all business groups; classification detail lives in HR_ORGANIZATION_INFORMATIONSchema: HRmasterfoundation
- HR_OPERATING_UNITSThe delivered view that enumerates operating units — the ORG_ID domain — with their business group, ledger, and legal context; the standard way to turn the ORG_ID on an _ALL table into a nameSchema: HRviewfoundation
- HR_ORGANIZATION_INFORMATIONClassification rows for each organization unit — which orgs are operating units, inventory orgs, or legal entities, and the per-classification attributes, keyed by a context code with generic attribute columnsSchema: HRcontrolfoundation
- HZ_CUST_ACCOUNTSThe customer account — the commercial relationship layered over a party, and the id order headers actually carry as SOLD_TO_ORG_ID; one party, many accountsSchema: ARmastercustomers
- HZ_CUST_ACCT_SITES_ALLCustomer account sites — one row binding an account to a party site (address) within one operating unit, with the bill-to/ship-to capability flagsSchema: ARmastercustomers
- HZ_CUST_SITE_USES_ALLSite business purposes — one row per use (ship-to, bill-to, statements…) of an account site per operating unit; the SITE_USE_ID here is what order headers carry as SHIP_TO_ORG_ID and INVOICE_TO_ORG_IDSchema: ARmastercustomers
- HZ_LOCATIONSThe physical address master — pure address rows with no party context; one location can serve many parties, customer sites, and supplier sitesSchema: ARmastercustomers
- HZ_PARTIESThe trading-community party master — one row per person, organization, or group before any commercial context; customers AND suppliers resolve back to a party hereSchema: ARmastercustomers
- HZ_PARTY_SITESParty sites — the reusable link from a party to a location, carrying the site number and the identifying-address flag; both customer account sites and supplier sites resolve their address through hereSchema: ARmastercustomers
Tables starting with M
- MRP_FORECAST_DATESThe forecast fact — one row per forecast entry per item, org, forecast name, and date, carrying both the entered quantity and the post-consumption remainderSchema: MRPtransactionplanning
- MRP_FORECAST_DESIGNATORSThe forecast name and forecast set master per organization — consumption behavior (consume flag, forward/backward time fences, outlier cap) lives at this levelSchema: MRPcontrolplanning
- MRP_SCHEDULE_DATESMDS/MPS schedule entries — one row per entry per item, org, schedule name, and date, spanning discrete quantities and repetitive rates, demand rows and supply rowsSchema: MRPtransactionplanning
- MRP_SCHEDULE_DESIGNATORSThe MDS/MPS schedule name master per organization — schedule type, relief behavior, and whether the schedule supplies ATPSchema: MRPcontrolplanning
- MSC_DEMANDSEvery demand row a plan considered — sales orders, forecasts, and the dependent demand exploded from supplies, each with its due date, quantity, and originSchema: MSCtransactionplanning
- MSC_PLANSThe ASCP plan registry — one row per plan with its user-visible name, owning org, type, planning horizon, and run timestamps; every plan-output query starts by picking a row hereSchema: MSCcontrolplanning
- MSC_SUPPLIESEvery supply row in a plan — existing purchase orders, jobs, on-hand, and in-transit alongside the planner's recommended planned orders; the supply side of ASCP plan outputSchema: MSCtransactionplanning
- MSC_SYSTEM_ITEMSThe planning copy of the item master at plan + instance + org + item grain — collected item attributes frozen per plan run, and the bridge column back to the source EBS itemSchema: MSCmasterplanning
- MTL_CATEGORIES_BThe category master — one row per category code combination, with the SEGMENTn flexfield columns the category name concatenates from, keyed by the flexfield structureSchema: INVmasteritems
- MTL_CATEGORY_SETS_BCategory set definitions — validation rules, control level (master-org vs org-level), the multiple-assignments flag, and the default category new items inheritSchema: INVcontrolitems
- MTL_CROSS_REFERENCES_BItem cross-references — maps items to external identifiers (GTINs, superseded part numbers, customer and supplier part numbers) by cross-reference type, either per organization or org-independentSchema: INVmasteritems
- MTL_DEMANDThe legacy demand picture used by ATP and planning — summary demand, open demand, and pre-R12 reservation rows for an item in an org, keyed to the order document that generated themSchema: INVtransactioninventory
- MTL_ITEM_CATEGORIESThe item-to-category assignment — one row per item, organization, category set, and category; the bridge every category rollup crossesSchema: INVmasteritems
- MTL_ITEM_LOCATIONSThe stock locator master — the physical bin/row/rack positions inside a subinventory, with the locator name held as SEGMENTn flexfield columnsSchema: INVmasterinventory
- MTL_ITEM_REVISIONS_BItem revisions — one row per revision level of an item in an organization, with effectivity and implementation dates and the change notice that introduced itSchema: INVmasteritems
- MTL_LOT_NUMBERSThe lot master — definition, genealogy (parent lot), status, grade, and the origination/expiration/retest dates for every lot, keyed by item + organization + lot numberSchema: INVmasterinventory
- MTL_MATERIAL_TRANSACTIONSThe 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 questionSchema: INVtransactioninventory
- MTL_ONHAND_QUANTITIES_DETAILThe on-hand balance detail — receipt-level slices of stock per item, org, subinventory, locator, lot, and revision, consumed in FIFO order as material issuesSchema: INVtransactioninventory
- MTL_PARAMETERSInventory organization parameters — one row per inventory org, holding the short org code, the master org it points to, and the org's costing method and locator/lot/serial control defaults; the org list every ORGANIZATION_ID resolves againstSchema: INVcontrolinventory
- MTL_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 lotSchema: INVtransactioninventory
- MTL_SECONDARY_INVENTORIESThe subinventory master — each row a named section of stock within an organization (stores, staging, WIP, rejects) with its asset/expense nature, tracking and reservability controls, and default accountsSchema: INVmasterinventory
- MTL_SERIAL_NUMBERSThe serial number master — definition and current position (status, org, subinventory, locator, lot) of every serialized unit; a serial is unique per item, not per orgSchema: INVmasterinventory
- MTL_SUPPLYThe incoming-supply picture — one row per open requisition, purchase order, or in-transit shipment element expected into an org, with the supply type migrating as the document progressesSchema: INVtransactioninventory
- MTL_SYSTEM_ITEMS_BThe item master — one row per item per inventory organization, carrying identity (the SEGMENTn flexfield the user-visible item number concatenates from), status, 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_IDSchema: INVmasteritems
- MTL_SYSTEM_ITEMS_TLThe item master's translation companion — item description and long description in every installed language, one row per item per organization per languageSchema: INVmasteritems
- MTL_TRANSACTION_ACCOUNTSAccounting distributions for material transactions — the debit and credit lines behind each material transaction, valued and pointed at a GL account combinationSchema: INVtransactioninventory
- MTL_TRANSACTION_LOT_NUMBERSLot-level detail for material transactions — one row per lot consumed or received per material transaction, with the lot's share of the quantitySchema: INVtransactioninventory
- MTL_TRANSACTION_TYPESThe transaction type list — seeded and user-defined types, each mapping to the transaction action and source type that together classify material transactionsSchema: INVcontrolinventory
- MTL_TXN_REQUEST_HEADERSMove order headers — the user-visible move order number, type, status, and required date for requests to move material within an organizationSchema: INVtransactioninventory
- MTL_TXN_REQUEST_LINESMove order lines — each row requests moving a quantity of an item from a source to a destination subinventory, individually statused, allocated (quantity detailed), and transacted (quantity delivered)Schema: INVtransactioninventory
- MTL_UNITS_OF_MEASURE_TLThe unit-of-measure master — both the 3-char UOM code and the 25-char unit name, the UOM class, and the base-unit flag, one row per unit per languageSchema: INVmasteritems
- MTL_UOM_CONVERSIONSIntra-class UOM conversion rates to each class's base unit — both standard conversions and item-specific overrides, distinguished by the item idSchema: INVmasteritems
Tables starting with O
- OE_DROP_SHIP_SOURCESThe drop-ship bridge — one row linking a sales order line to the purchase requisition and purchase order raised to fulfill it from the supplier; the only physical tie between the order-to-cash and procure-to-pay flowsSchema: ONTtransactionorder-management
- OE_HOLD_DEFINITIONSHold definitions — the named hold types (credit check, administrative…) with their workflow scope and effectivity; global seed data every hold instance resolves toSchema: ONTcontrolorder-management
- OE_HOLD_SOURCES_ALLHold source criteria — the entity a hold was applied against (a customer, an order, an item, a warehouse), stored as a generic entity code plus a polymorphic id, with the hold-until dateSchema: ONTtransactionorder-management
- OE_ORDER_HEADERS_ALLThe sales order header — one row per order or quote, carrying the order number, type, customer references, currency, and the workflow status the whole order-to-cash cycle hangs off; operating-unit stripedSchema: ONTtransactionorder-management
- OE_ORDER_HOLDS_ALLHold instances on orders and lines — one row per applied hold, pointing at the hold source that applied it and the release record once lifted; the "why isn't this line shipping" tableSchema: ONTtransactionorder-management
- OE_ORDER_LINES_ALLSales order lines at their most granular workflow unit — shipment splits, model options, included items, and configuration items each get their own row, individually statused and quantity-tracked through booking, shipping, and invoicingSchema: ONTtransactionorder-management
- OE_ORDER_SOURCESThe order source master — the feeder systems order import brings sales documents in from (EDI, web, copies, internal orders), a small global decode for ORDER_SOURCE_IDSchema: ONTcontrolorder-management
- OE_PRICE_ADJUSTMENTSPricing modifier applications — discounts, surcharges, and freight/special charges applied to an order or a line, with the modifier list that produced them and the monetary effect; the gap between list and selling priceSchema: ONTtransactionorder-management
- OE_TRANSACTION_TYPES_ALLOrder and line transaction types in one pool — each row defines a document type (distinguished order vs line by the type code) with its workflow binding, defaults, and accounting hooks; the decode for both ORDER_TYPE_ID and LINE_TYPE_IDSchema: ONTcontrolorder-management
- OE_TRANSACTION_TYPES_TLTranslation companion for order/line transaction types — the display name and description per installed language; the only place the type name existsSchema: ONTcontrolorder-management
- ORG_ORGANIZATION_DEFINITIONSThe delivered view that presents inventory organizations with their operating unit, legal entity, ledger, and chart of accounts in one row — the org-mapping backbone of most inventory reportingSchema: INVviewfoundation
Tables starting with P
- PO_DISTRIBUTIONS_ALLPO accounting distributions — how each shipment schedule's quantity charges out: destination type, receiving inventory org and subinventory, charge account (CCID), and the requisition distribution it fulfillsSchema: POtransactionpurchasing
- PO_HEADERS_ALLPurchasing document headers — one row per purchase order, agreement, quotation, or RFQ (seven document types share the table), with supplier, buyer, currency, approval status, and closure state; operating-unit stripedSchema: POtransactionpurchasing
- PO_LINE_LOCATIONS_ALLPO shipment schedules — one row per delivery schedule per line with need-by/promised dates and the running received/billed/cancelled quantity counters; blanket price-break rows share the tableSchema: POtransactionpurchasing
- PO_LINES_ALLPurchasing document lines — the item, category, unit price, and ordered quantity per line across the same seven document types; shipment schedules and accounting live one and two levels downSchema: POtransactionpurchasing
- PO_RELEASES_ALLBlanket and planned PO releases — one row per release with its number, date, buyer, and approval status; the shipment schedules a release creates point back hereSchema: POtransactionpurchasing
- PO_REQUISITION_HEADERS_ALLRequisition headers — the requisition number, preparer, type (purchase vs internal), and approval status; where demand enters purchasing before it becomes a POSchema: POtransactionpurchasing
- PO_REQUISITION_LINES_ALLRequisition lines — item, quantity, price, need-by date, destination inventory org, and sourcing suggestion per line; carries the link to the PO shipment autocreate built from itSchema: POtransactionpurchasing
- PO_VENDORSThe compatibility view legacy purchasing queries know suppliers by — resolves to the supplier master joined to its trading-community party; kept for the name, not the extraction pathSchema: APviewpurchasing
Tables starting with R
- RA_CUSTOMER_TRX_ALLReceivables transaction headers — invoices, credit and debit memos, chargebacks, and deposits share the table, classified by transaction type; the revenue-document anchor of order-to-cashSchema: ARtransactionfinancials
- RA_CUSTOMER_TRX_LINES_ALLReceivables transaction lines — product lines, tax, and freight share the table by line type, with quantities, selling price, and the extended amount revenue analytics sumSchema: ARtransactionfinancials
- RCV_SHIPMENT_HEADERSReceipt and expected-receipt headers — one row per supplier ASN, receipt, or internal shipment, grouped by receipt source; carries the receipt number, supplier, and expected/shipped datesSchema: POtransactionreceiving
- RCV_SHIPMENT_LINESReceipt/shipment lines — one row per item per shipment header with cumulative shipped and received quantities, line status, the source-document pointers (PO, requisition, or RMA), and the default putaway destinationSchema: POtransactionreceiving
- 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 quantitySchema: POtransactionreceiving
Tables starting with W
- WIP_ACCOUNTING_CLASSESThe WIP accounting class master per organization — class code, type, and the elemental valuation and variance accounts jobs charge throughSchema: WIPcontrolwip
- WIP_DISCRETE_JOBSDiscrete job detail — status, start/completed/scrapped quantities, scheduled vs actual dates, accounting class, and the BOM/routing the job was built from; the workhorse of job-level manufacturing analyticsSchema: WIPtransactionwip
- WIP_ENTITIESThe WIP identity registry — every discrete job, repetitive assembly, and flow schedule claims its id and unique name here before type-specific detail lands in child tables; the anchor outside references point atSchema: WIPmasterwip
- WIP_MOVE_TRANSACTIONSThe shop-floor move ledger — one row per move event with from/to operation and intraoperation step, quantity, and date; the throughput, cycle-time, and WIP-aging fact behind the operation countersSchema: WIPtransactionwip
- WIP_OPERATIONSOperations on a job or repetitive schedule — the shop-floor step sequence with department, live quantity counters per intraoperation step (queue, run, to-move, reject, scrap), and first/last-unit schedule datesSchema: WIPtransactionwip
- WIP_REQUIREMENT_OPERATIONSMaterial requirements per job and operation — the job's exploded BOM with required vs issued quantities, supply type, and the supply subinventory issues pull fromSchema: WIPtransactionwip
- WIP_TRANSACTIONSThe WIP resource ledger — one row per resource charge (labor, machine, outside processing) with operation, resource, rates, and the purchasing/receiving references that drive outside-processing chargesSchema: WIPtransactionwip
- WSH_DELIVERY_ASSIGNMENTSThe assignment bridge between delivery details and deliveries — also encodes container nesting, where a detail's parent row is the LPN it is packed into; a detail reaches its delivery only through this tableSchema: WSHtransactionshipping
- WSH_DELIVERY_DETAILSThe atomic shipping line — one row per shippable unit of demand from order lines (or WIP/PO sources), plus container rows, tracking requested/picked/shipped quantities through pick release and ship confirmSchema: WSHtransactionshipping
- WSH_DELIVERY_LEGSDelivery legs — the mapping from a delivery to the trip stops where it is picked up and dropped off; the only path from deliveries to tripsSchema: WSHtransactionshipping
- WSH_NEW_DELIVERIESThe delivery header — a named grouping of delivery details shipped together from one location toward one final drop-off, carrying the ship-confirm date, carrier, waybill, and weightsSchema: WSHtransactionshipping
- WSH_TRIP_STOPSTrip stops — one row per pickup or drop-off point on a trip, with planned and actual arrival/departure timestamps; the actual departure at the pickup stop is the gate-out time ship confirm writesSchema: WSHtransactionshipping
- WSH_TRIPSThe trip header — a carrier/vehicle journey over an ordered set of stops, with ship method, carrier, and vehicle attributesSchema: WSHtransactionshipping