AP_SUPPLIER_SITES_ALL
Schema: APmasterOU-striped (ORG_ID)Supplier 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
The same supplier repeats across operating units — a site row per OU. Address columns physically exist here but the address is maintained in the trading community model via LOCATION_ID.
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_SITE_ID | Surrogate key of the supplier site | NUMBER | Primary-key field |
| 2 | VENDOR_ID | The supplier the site belongs to | NUMBER | |
| 3 | ORG_ID | Operating unit — the same supplier gets one site row per OU (see quirks guide) | NUMBER | |
| 4 | VENDOR_SITE_CODE | The site code users see | VARCHAR2 | |
| 5 | LOCATION_ID | The TCA location that actually holds the address — the address columns here are legacy | NUMBER | |
| 6 | PARTY_SITE_ID | The trading-community party site behind this row | NUMBER | |
| 7 | PURCHASING_SITE_FLAG | Whether POs may be placed against the site | VARCHAR2 | |
| 8 | PAY_SITE_FLAG | Whether invoices may be paid to the site | VARCHAR2 | |
| 9 | RFQ_ONLY_SITE_FLAG | RFQ-only site marker | VARCHAR2 | |
| 10 | INACTIVE_DATE | When the site was inactivated — NULL while active | DATE | |
| 11 | TERMS_ID | Payment terms at the site level | NUMBER | |
| 12 | INVOICE_CURRENCY_CODE | Invoice currency at the site level | VARCHAR2 |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading AP_SUPPLIER_SITES_ALL 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.
5 parameters not filled: <catalog>, <schema>, <operating_unit_id>, <VENDOR_SITE_ID>, <watermark>
-- ============================================================
-- Table : AP_SUPPLIER_SITES_ALL — Supplier 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
-- Purpose: Column-selected read of AP_SUPPLIER_SITES_ALL — auto-generated from field metadata
-- Grain : One row per operating unit (ORG_ID) + VENDOR_SITE_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_SITE_ID AS "Surrogate key of the supplier site",
t.VENDOR_ID AS "The supplier the site belongs to",
t.ORG_ID AS "Operating unit — the same supplier gets one site row per OU (see quirks guide)",
t.VENDOR_SITE_CODE AS "The site code users see",
t.LOCATION_ID AS "The TCA location that actually holds the address — the address columns here are legacy",
t.PARTY_SITE_ID AS "The trading-community party site behind this row",
t.PURCHASING_SITE_FLAG AS "Whether POs may be placed against the site",
t.PAY_SITE_FLAG AS "Whether invoices may be paid to the site",
t.RFQ_ONLY_SITE_FLAG AS "RFQ-only site marker",
t.INACTIVE_DATE AS "When the site was inactivated — NULL while active",
t.TERMS_ID AS "Payment terms at the site level",
t.INVOICE_CURRENCY_CODE AS "Invoice currency at the site level"
FROM <catalog>.<schema>.AP_SUPPLIER_SITES_ALL t
WHERE
t.ORG_ID = <operating_unit_id> -- operating unit (MOAC does not filter extracts)
-- AND t.VENDOR_SITE_ID = <VENDOR_SITE_ID>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.VENDOR_SITE_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.
Loading relationship diagram…
Join details
ON PO_HEADERS_ALL.VENDOR_SITE_ID = AP_SUPPLIER_SITES_ALL.VENDOR_SITE_ID AND PO_HEADERS_ALL.ORG_ID = AP_SUPPLIER_SITES_ALL.ORG_IDON AP_SUPPLIER_SITES_ALL.VENDOR_ID = AP_SUPPLIERS.VENDOR_IDON AP_SUPPLIER_SITES_ALL.PARTY_SITE_ID = HZ_PARTY_SITES.PARTY_SITE_IDON AP_SUPPLIER_SITES_ALL.LOCATION_ID = HZ_LOCATIONS.LOCATION_IDON AP_INVOICES_ALL.VENDOR_SITE_ID = AP_SUPPLIER_SITES_ALL.VENDOR_SITE_ID AND AP_INVOICES_ALL.ORG_ID = AP_SUPPLIER_SITES_ALL.ORG_ID
More Purchasing tables
- 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
- 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