Search Results customer_org

Overview

The OKC.OKC_REP_CONTRACT_PARTIES table is a core transactional table within the Oracle E-Business Suite Contracts (OKC) schema. It records the parties associated with a contract, capturing each party's role and the source system from which its identifier originates. The table functions as the authoritative register of whom a contract is with — customers, suppliers, partners, or internal organizations — and is a prerequisite for downstream contract functionality such as party contacts, deliverables, and clauses.

The party source varies by role. A PARTY_ID carrying a PARTY_ROLE_CODE of SUPPLIER-ORG is drawn from PO_VENDORS; CUSTOMER_ORG and PARTNER_ORG values are drawn from HZ_PARTIES; and an INTERNAL_ORG role resolves to HR_ALL_ORGANIZATION_UNITS. This design allows a single contract record to reference heterogeneous party models without duplicating master data. Users searching for "internal_org" typically need to identify the internal organization records attached to a contract, which are the rows where PARTY_ROLE_CODE equals INTERNAL_ORG.

The heuristic Data Vault classification mined from the foreign-key structure is satellite-leaning. This suggests that, in a dimensional or Data Vault model, OKC_REP_CONTRACT_PARTIES is best treated as a satellite hanging off the contract hub (OKC_REP_CONTRACTS_ALL), carrying descriptive party-role attributes keyed by the contract.

Key Information Stored

The table comprises 14 documented columns. The most significant are enumerated below.

• CONTRACT_ID — Identifier of the contract to which the party record belongs. Also a foreign key to OKC.OKC_REP_CONTRACTS_ALL.
• PARTY_ROLE_CODE — The role the party plays on the contract (for example SUPPLIER-ORG, CUSTOMER_ORG, PARTNER_ORG, or INTERNAL_ORG). This value also determines the originating source system of the PARTY_ID.
• PARTY_ID — Identifier of the party, resolved against PO_VENDORS, HZ_PARTIES, or HR_ALL_ORGANIZATION_UNITS according to the role code. Indexed non-uniquely by OKC_REP_CONTRACT_PARTIES_N1.
• PARTY_LOCATION_ID — Location identifier associated with the party on the contract.
• OBJECT_VERSION_NUMBER — Sequential version number, set to 1 on insert and incremented on update. Used by APIs to enforce optimistic concurrency control.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Who columns providing audit lineage for the row.
• PROGRAM_ID, PROGRAM_LOGIN_ID, PROGRAM_APPLICATION_ID, REQUEST_ID — Concurrent program context columns identifying which application and request created or last modified the record.

The primary key is OKC_REP_CONTRACT_PARTIES_PK, defined on (CONTRACT_ID, PARTY_ID, PARTY_ROLE_CODE). The unique index OKC_REP_CONTRACT_PARTIES_U1 mirrors this same column set and represents the documented business-key candidate, ensuring a given party may hold a role only once per contract.

Common Use Cases and Queries

The most common reporting requirement is to list the parties engaged on a contract along with their roles. A typical pattern joins back to OKC_REP_CONTRACTS_ALL for contract header attributes and resolves the party through the appropriate master table.

• List all parties on a contract: SELECT contract_id, party_role_code, party_id FROM okc_rep_contract_parties WHERE contract_id = :p_contract_id ORDER BY party_role_code;
• Isolate internal organizations: SELECT contract_id, party_id FROM okc_rep_contract_parties WHERE party_role_code = 'INTERNAL_ORG'; joined to HR_ALL_ORGANIZATION_UNITS on organization_id = party_id to obtain the organization name.
• Find all contracts for a given party: use index OKC_REP_CONTRACT_PARTIES_N1 with WHERE party_id = :p_party_id.
• Audit recent changes: filter on LAST_UPDATE_DATE and the PROGRAM_ID / REQUEST_ID columns to trace concurrent-program-driven modifications.

Related Objects

• OKC.OKC_REP_CONTRACTS_ALL — Parent header table; joined on CONTRACT_ID = CONTRACT_ID and referenced by the foreign key.
• OKC.OKC_REP_PARTY_CONTACTS — Child table referencing this table via CONTRACT_PARTY_ID, holding individual contact records for each contract party.
• PO_VENDORS — Source of PARTY_ID for rows whose role is SUPPLIER-ORG.
• HZ_PARTIES — Source of PARTY_ID for CUSTOMER_ORG and PARTNER_ORG roles.
• HR_ALL_ORGANIZATION_UNITS — Source of PARTY_ID where PARTY_ROLE_CODE is INTERNAL_ORG.
• OKC_REP_CONTRACT_PARTIES_PK / _U1 / _N1 — Primary, unique, and non-unique indexes supporting integrity and access paths.