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

master: Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.

FilterShowing 62 of 62 tables

Module

A

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 striping
Schema: 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 id
Schema: APmasterpurchasing

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 meaning
Schema: 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 use
Schema: 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

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_ID
Schema: GLmasterfoundation
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 to
Schema: GLmasterfoundation

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_INFORMATION
Schema: 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 name
Schema: 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 columns
Schema: HRcontrolfoundation

M

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 structure
Schema: 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 inherit
Schema: 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-independent
Schema: 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 them
Schema: INVtransactioninventory
MTL_ITEM_CATEGORIESThe item-to-category assignment — one row per item, organization, category set, and category; the bridge every category rollup crosses
Schema: INVmasteritems
MTL_ITEM_LOCATIONSThe stock locator master — the physical bin/row/rack positions inside a subinventory, with the locator name held as SEGMENTn flexfield columns
Schema: 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 it
Schema: 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 number
Schema: 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 question
Schema: 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 issues
Schema: 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 against
Schema: 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 lot
Schema: 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 accounts
Schema: 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 org
Schema: 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 progresses
Schema: 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_ID
Schema: 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 language
Schema: INVmasteritems
MTL_TRANSACTION_ACCOUNTSAccounting distributions for material transactions — the debit and credit lines behind each material transaction, valued and pointed at a GL account combination
Schema: 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 quantity
Schema: 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 transactions
Schema: 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 organization
Schema: 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 language
Schema: 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 id
Schema: INVmasteritems

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 flows
Schema: 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 to
Schema: 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 date
Schema: 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 striped
Schema: 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" table
Schema: 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 invoicing
Schema: 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_ID
Schema: 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 price
Schema: 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_ID
Schema: 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 exists
Schema: 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 reporting
Schema: INVviewfoundation

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 fulfills
Schema: 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 striped
Schema: 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 table
Schema: 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 down
Schema: 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 here
Schema: 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 PO
Schema: 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 it
Schema: 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 path
Schema: APviewpurchasing

R

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 dates
Schema: 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 destination
Schema: 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 quantity
Schema: POtransactionreceiving

W

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 table
Schema: 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 confirm
Schema: 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 trips
Schema: 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 weights
Schema: 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 writes
Schema: WSHtransactionshipping
WSH_TRIPSThe trip header — a carrier/vehicle journey over an ordered set of stops, with ship method, carrier, and vehicle attributes
Schema: WSHtransactionshipping