# Customer Table in Oracle EBS: TCA (HZ) and Supplier (AP_SUPPLIERS) Table Reference > Source: https://netray.co/tools/oracle-ebs-customer-and-supplier-tables-reference > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Searchable list of the Trading Community Architecture customer tables and the supplier tables in Oracle EBS, with keys, join columns and where to confirm in the eTRM. ## Category oracle ## Erp Oracle E-Business Suite ## Audience - EBS developer - Data migration analyst - Report writer ## Tool **Kind:** worksheet **Mode:** reference **Columns:** #### Table **Key:** table **Type:** text #### Module **Key:** module **Type:** text #### What it stores **Key:** stores **Type:** text #### Key column **Key:** key **Type:** text #### Joins to **Key:** joins **Type:** text #### Note **Key:** note **Type:** text **Rows:** **Table:** HZ_PARTIES **Module:** TCA **Stores:** Every party: organization, person or group **Key:** PARTY_ID **Joins:** HZ_CUST_ACCOUNTS.PARTY_ID, AP_SUPPLIERS.PARTY_ID **Note:** Shared by customers, suppliers and contacts **Table:** HZ_CUST_ACCOUNTS **Module:** TCA **Stores:** Customer account (the commercial relationship) **Key:** CUST_ACCOUNT_ID **Joins:** HZ_PARTIES via PARTY_ID **Note:** ACCOUNT_NUMBER is the customer number users see **Table:** HZ_CUST_ACCT_SITES_ALL **Module:** TCA **Stores:** Account site, one per address per operating unit **Key:** CUST_ACCT_SITE_ID **Joins:** HZ_CUST_ACCOUNTS via CUST_ACCOUNT_ID; HZ_PARTY_SITES via PARTY_SITE_ID **Note:** Filter ORG_ID **Table:** HZ_CUST_SITE_USES_ALL **Module:** TCA **Stores:** Business purpose of a site, such as BILL_TO or SHIP_TO **Key:** SITE_USE_ID **Joins:** HZ_CUST_ACCT_SITES_ALL via CUST_ACCT_SITE_ID **Note:** SITE_USE_CODE holds the purpose; order and invoice headers store SITE_USE_ID **Table:** HZ_PARTY_SITES **Module:** TCA **Stores:** Party's address linkage **Key:** PARTY_SITE_ID **Joins:** HZ_PARTIES via PARTY_ID; HZ_LOCATIONS via LOCATION_ID **Note:** Used for both customers and suppliers **Table:** HZ_LOCATIONS **Module:** TCA **Stores:** Physical address **Key:** LOCATION_ID **Joins:** HZ_PARTY_SITES via LOCATION_ID **Note:** ADDRESS1 to ADDRESS4, CITY, STATE, COUNTRY, POSTAL_CODE **Table:** HZ_CONTACT_POINTS **Module:** TCA **Stores:** Phone, email, web and other contact methods **Key:** CONTACT_POINT_ID **Joins:** OWNER_TABLE_ID with OWNER_TABLE_NAME **Note:** Owner may be a party or a party site **Table:** HZ_CUST_ACCOUNT_ROLES **Module:** TCA **Stores:** Contact roles at account or site level **Key:** CUST_ACCOUNT_ROLE_ID **Joins:** HZ_CUST_ACCOUNTS, HZ_RELATIONSHIPS via PARTY_ID **Note:** Customer contact assignments **Table:** HZ_RELATIONSHIPS **Module:** TCA **Stores:** Relationships between parties **Key:** RELATIONSHIP_ID **Joins:** SUBJECT_ID and OBJECT_ID to HZ_PARTIES **Note:** Person contact of an organization **Table:** HZ_ORGANIZATION_PROFILES **Module:** TCA **Stores:** Organization details, dated versions **Key:** ORGANIZATION_PROFILE_ID **Joins:** HZ_PARTIES via PARTY_ID **Note:** Filter on effective dates for current row **Table:** HZ_PERSON_PROFILES **Module:** TCA **Stores:** Person details, dated versions **Key:** PERSON_PROFILE_ID **Joins:** HZ_PARTIES via PARTY_ID **Note:** Filter on effective dates for current row **Table:** HZ_CUSTOMER_PROFILES **Module:** AR **Stores:** Credit and collection profile per account or site **Key:** CUST_ACCOUNT_PROFILE_ID **Joins:** HZ_CUST_ACCOUNTS via CUST_ACCOUNT_ID **Note:** SITE_USE_ID null means account-level profile **Table:** HZ_CUST_PROFILE_AMTS **Module:** AR **Stores:** Credit limits by currency **Key:** CUST_ACCT_PROFILE_AMT_ID **Joins:** HZ_CUSTOMER_PROFILES via CUST_ACCOUNT_PROFILE_ID **Note:** OVERALL_CREDIT_LIMIT, TRX_CREDIT_LIMIT **Table:** AR_CUSTOMERS **Module:** AR **Stores:** Compatibility view combining party and account **Key:** CUSTOMER_ID **Joins:** Equivalent to CUST_ACCOUNT_ID **Note:** Obsolete view; prefer HZ tables for new work **Table:** AP_SUPPLIERS **Module:** AP **Stores:** Supplier header **Key:** VENDOR_ID **Joins:** HZ_PARTIES via PARTY_ID **Note:** SEGMENT1 is the supplier number, VENDOR_NAME the name; replaced PO_VENDORS **Table:** AP_SUPPLIER_SITES_ALL **Module:** AP **Stores:** Supplier site by operating unit **Key:** VENDOR_SITE_ID **Joins:** AP_SUPPLIERS via VENDOR_ID; HZ_PARTY_SITES via PARTY_SITE_ID **Note:** VENDOR_SITE_CODE; purchasing, pay and RFQ flags **Table:** AP_SUPPLIER_CONTACTS **Module:** AP **Stores:** Supplier contacts **Key:** VENDOR_CONTACT_ID **Joins:** AP_SUPPLIER_SITES_ALL via ORG_PARTY_SITE_ID; HZ_PARTIES via PER_PARTY_ID **Note:** Names come from the TCA party record **Table:** IBY_EXTERNAL_PAYEES_ALL **Module:** Payments **Stores:** Payee setup for suppliers **Key:** EXT_PAYEE_ID **Joins:** PAYEE_PARTY_ID, SUPPLIER_SITE_ID **Note:** Payment method and delivery channel defaults **Table:** IBY_EXT_BANK_ACCOUNTS **Module:** Payments **Stores:** External bank accounts **Key:** EXT_BANK_ACCOUNT_ID **Joins:** IBY_PMT_INSTR_USES_ALL via INSTRUMENT_ID **Note:** Account numbers may be masked or encrypted **Table:** IBY_PMT_INSTR_USES_ALL **Module:** Payments **Stores:** Assignment of bank account to payee **Key:** INSTRUMENT_PAYMENT_USE_ID **Joins:** IBY_EXTERNAL_PAYEES_ALL via EXT_PMT_PARTY_ID **Note:** Primary account flag **Table:** HZ_CUST_ACCOUNTS **Module:** Order Management **Stores:** Sold-to customer on OE_ORDER_HEADERS_ALL **Key:** CUST_ACCOUNT_ID **Joins:** OE_ORDER_HEADERS_ALL.SOLD_TO_ORG_ID **Note:** SOLD_TO_ORG_ID is a CUST_ACCOUNT_ID, not a site use **Table:** HZ_CUST_SITE_USES_ALL **Module:** Order Management **Stores:** Ship-to and invoice-to on the order **Key:** SITE_USE_ID **Joins:** OE_ORDER_HEADERS_ALL.SHIP_TO_ORG_ID and INVOICE_TO_ORG_ID **Note:** Despite the name, ORG_ID columns hold site use IDs **Notes:** Confirm every table and column in the Oracle eTRM (Electronic Technical Reference Manual) for your release. Column names here reflect 12.1 and 12.2 and the Trading Community model. ## Content **Intro:** In Oracle EBS there is no single customer table. Customers are stored in the Trading Community Architecture (TCA) HZ tables, and suppliers in AP_SUPPLIERS and AP_SUPPLIER_SITES_ALL. This reference shows each table, its key and how they connect. **Sections:** #### How to use this reference **Body:** Search by table name or by what you need to find, such as bill-to, credit limit or bank account. Each row lists the key column and the tables it joins to, so you can build the join chain for a customer address or a supplier site without opening the eTRM for every step. Export to Excel to keep a data-mapping sheet for a migration or interface project. #### The customer model in one chain **Body:** A customer is a party (HZ_PARTIES) with an account (HZ_CUST_ACCOUNTS). The account has sites (HZ_CUST_ACCT_SITES_ALL) that point to a party site (HZ_PARTY_SITES) and a physical address (HZ_LOCATIONS). Each site has uses (HZ_CUST_SITE_USES_ALL) such as BILL_TO and SHIP_TO. Orders and invoices store the site use ID. Following PARTY_ID, CUST_ACCOUNT_ID, CUST_ACCT_SITE_ID, SITE_USE_ID and LOCATION_ID gets you from name to address. **Bullets:** - Customer name: HZ_PARTIES.PARTY_NAME - Customer number: HZ_CUST_ACCOUNTS.ACCOUNT_NUMBER - Address: HZ_LOCATIONS through HZ_PARTY_SITES - Bill-to and ship-to: HZ_CUST_SITE_USES_ALL.SITE_USE_CODE #### The supplier model and the link to TCA **Body:** Suppliers are stored in AP_SUPPLIERS (formerly PO_VENDORS in 11i) and sites in AP_SUPPLIER_SITES_ALL. Since release 12 the supplier is also a TCA party, so AP_SUPPLIERS.PARTY_ID points to HZ_PARTIES and supplier site addresses come from HZ_PARTY_SITES and HZ_LOCATIONS through PARTY_SITE_ID. The same party can be both a customer and a supplier, which is how you identify trading partners in both directions. #### Finding table documentation and common mistakes **Body:** Oracle documents every standard table in the eTRM, available from My Oracle Support for your release. You can also query ALL_TAB_COLUMNS and the FND_TABLES and FND_COLUMNS dictionary tables. Common errors: using old view names like AR_CUSTOMERS in new code, forgetting ORG_ID on _ALL tables, joining orders to HZ_CUST_ACCOUNTS through the wrong column (ship-to is a site use, not an account), and not filtering the dated profile tables to the current row. **Cta:** If you want customer and supplier questions answered without writing joins, we can add a private natural-language layer over your EBS database that runs on your own infrastructure. **Faq:** #### What is the customer table in Oracle EBS? **Answer:** There is no single one. The main table is HZ_CUST_ACCOUNTS for the account, linked to HZ_PARTIES for the name, and to HZ_CUST_ACCT_SITES_ALL and HZ_LOCATIONS for addresses. These are part of the Trading Community Architecture. #### What is the supplier table in Oracle EBS? **Answer:** AP_SUPPLIERS holds supplier headers and AP_SUPPLIER_SITES_ALL holds sites. In 11i the header table was PO_VENDORS. In release 12 the supplier is also a TCA party linked through PARTY_ID. #### Where is Oracle EBS table documentation? **Answer:** The Electronic Technical Reference Manual (eTRM) on My Oracle Support documents tables, columns, indexes and foreign keys per release. The Oracle Applications dictionary tables FND_TABLES and FND_COLUMNS list registered objects in your own instance. #### How do I get a customer's bill-to address? **Answer:** Join HZ_CUST_ACCOUNTS to HZ_CUST_ACCT_SITES_ALL, then to HZ_CUST_SITE_USES_ALL with SITE_USE_CODE = 'BILL_TO', then through HZ_PARTY_SITES to HZ_LOCATIONS. Filter on ORG_ID and status flags to keep only active records. ## Search terms customer table in oracle ebs, oracle ebs supplier table, oracle ebs standard tables, oracle ebs table documentation, hz_cust_accounts, ap_suppliers, oracle ebs tca tables, oracle apps customer query, oracle etrm --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json