Skip to content
EBS Reference

AP_SUPPLIERS

Schema: APmaster

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

Module: PurchasingNot org-partitioned
Notes

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
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
In field listings, K marks a primary-key field.

Fields

12 fields · 1 key

Table fields: position, field name, description, data type, and flags. 12 fields.
#FieldDescriptionTypeFlags
1VENDOR_IDSurrogate key of the supplier — what purchasing and receiving documents carryNUMBER
Key
2SEGMENT1The supplier number — same flexfield naming collision as document numbersVARCHAR2
3VENDOR_NAMESupplier nameVARCHAR2
4PARTY_IDThe trading-community party behind the supplier — the TCA backbone linkNUMBER
5VENDOR_TYPE_LOOKUP_CODESupplier type classificationVARCHAR2
6ENABLED_FLAGWhether the supplier is activeVARCHAR2
7HOLD_FLAGWhether new purchasing is held for the supplierVARCHAR2
8ONE_TIME_FLAGOne-time supplier markerVARCHAR2
9START_DATE_ACTIVEEffectivity start dateDATE
10END_DATE_ACTIVEEffectivity end date — NULL while activeDATE
11TERMS_IDDefault payment termsNUMBER
12INVOICE_CURRENCY_CODEDefault invoice currencyVARCHAR2

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading AP_SUPPLIERSon Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark are already in place. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.

Query parameters
-- ============================================================
-- 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;

4 parameters not filled: <catalog>, <schema>, <VENDOR_ID>, <watermark>

Relationships

1-hop neighbors — click a table to navigate there. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.

Join details

  • PO_HEADERS_ALLAP_SUPPLIERSforeign key · N:1
    ON PO_HEADERS_ALL.VENDOR_ID = AP_SUPPLIERS.VENDOR_ID
  • AP_SUPPLIER_SITES_ALLAP_SUPPLIERSforeign key · N:1
    ON AP_SUPPLIER_SITES_ALL.VENDOR_ID = AP_SUPPLIERS.VENDOR_ID
  • PO_VENDORSAP_SUPPLIERSforeign key · 1:1
    ON PO_VENDORS.VENDOR_ID = AP_SUPPLIERS.VENDOR_ID
  • RCV_SHIPMENT_HEADERSAP_SUPPLIERSforeign key · N:1
    ON RCV_SHIPMENT_HEADERS.VENDOR_ID = AP_SUPPLIERS.VENDOR_ID

Browse more Purchasingtables →

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice →

Not affiliated with or endorsed by Oracle. Oracle and Oracle E-Business Suite are registered trademarks of Oracle and/or its affiliates.