AP_SUPPLIERS
Schema: APmasterThe 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
Suppliers are global; the operating-unit striping lives on supplier sites. PO_VENDORS survives as a compatibility view over this table — steer new queries here.
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
Fields
12 fields · 1 key
12 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | VENDOR_ID | Surrogate key of the supplier — what purchasing and receiving documents carry | NUMBER | Primary-key field |
| 2 | SEGMENT1 | The supplier number — same flexfield naming collision as document numbers | VARCHAR2 | |
| 3 | VENDOR_NAME | Supplier name | VARCHAR2 | |
| 4 | PARTY_ID | The trading-community party behind the supplier — the TCA backbone link | NUMBER | |
| 5 | VENDOR_TYPE_LOOKUP_CODE | Supplier type classification | VARCHAR2 | |
| 6 | ENABLED_FLAG | Whether the supplier is active | VARCHAR2 | |
| 7 | HOLD_FLAG | Whether new purchasing is held for the supplier | VARCHAR2 | |
| 8 | ONE_TIME_FLAG | One-time supplier marker | VARCHAR2 | |
| 9 | START_DATE_ACTIVE | Effectivity start date | DATE | |
| 10 | END_DATE_ACTIVE | Effectivity end date — NULL while active | DATE | |
| 11 | TERMS_ID | Default payment terms | NUMBER | |
| 12 | INVOICE_CURRENCY_CODE | Default invoice currency | VARCHAR2 |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading AP_SUPPLIERS on Databricks — real DATE columns need no conversion, and the org anchor is already in place. The optional LAST_UPDATE_DATE watermark is included. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.
4 parameters not filled: <catalog>, <schema>, <VENDOR_ID>, <watermark>
-- ============================================================
-- Table : AP_SUPPLIERS — The 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
-- Purpose: Column-selected read of AP_SUPPLIERS — auto-generated from field metadata
-- Grain : One row per VENDOR_ID
-- Notes : Auto-generated skeleton for Oracle EBS R12 data landed in your lakehouse. Dates are real DATE/TIMESTAMP columns — no conversion needed. WHO audit columns omitted (see the quirks guide); the optional LAST_UPDATE_DATE watermark filter supports incremental extracts.
-- ============================================================
SELECT
t.VENDOR_ID AS "Surrogate key of the supplier — what purchasing and receiving documents carry",
t.SEGMENT1 AS "The supplier number — same flexfield naming collision as document numbers",
t.VENDOR_NAME AS "Supplier name",
t.PARTY_ID AS "The trading-community party behind the supplier — the TCA backbone link",
t.VENDOR_TYPE_LOOKUP_CODE AS "Supplier type classification",
t.ENABLED_FLAG AS "Whether the supplier is active",
t.HOLD_FLAG AS "Whether new purchasing is held for the supplier",
t.ONE_TIME_FLAG AS "One-time supplier marker",
t.START_DATE_ACTIVE AS "Effectivity start date",
t.END_DATE_ACTIVE AS "Effectivity end date — NULL while active",
t.TERMS_ID AS "Default payment terms",
t.INVOICE_CURRENCY_CODE AS "Default invoice currency"
FROM <catalog>.<schema>.AP_SUPPLIERS t
WHERE
1 = 1 -- no partition column on this table; the filters below are optional
-- AND t.VENDOR_ID = <VENDOR_ID>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.VENDOR_ID;Verified September 2026
Relationships
Diagram of 1-hop neighbors — join details below. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.
Join details
ON PO_HEADERS_ALL.VENDOR_ID = AP_SUPPLIERS.VENDOR_IDON AP_SUPPLIER_SITES_ALL.VENDOR_ID = AP_SUPPLIERS.VENDOR_IDON PO_VENDORS.VENDOR_ID = AP_SUPPLIERS.VENDOR_IDON RCV_SHIPMENT_HEADERS.VENDOR_ID = AP_SUPPLIERS.VENDOR_IDON AP_SUPPLIERS.PARTY_ID = HZ_PARTIES.PARTY_IDON AP_INVOICES_ALL.VENDOR_ID = AP_SUPPLIERS.VENDOR_ID
More Purchasing tables
- 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
- 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
- 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
- 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
- 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
- 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