Results for “program_login_id”

31 results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKC_REP_CONTRACT_PARTIES is a core table within the Oracle Contracts (OKC) module, owned by the OKC schema. It stores the parties associated with a contract — the individuals or organizations that fulfill a defined role on that contract. The table's purpose is to resolve the polymorphic relationship between a contract header and the external entity acting as a counterparty, whether that is a supplier, a customer, or an internal organization.

Because the PARTY_ID column can reference multiple source entities depending on the role, the table acts as a generalized bridge between contracts and master data. A PARTY_ID with a PARTY_ROLE_CODE of SUPPLIER-ORG originates from PO_VENDORS; a PARTY_ID with a role of CUSTOMER originates from HZ_PARTIES; and other roles may reference HR_ALL_ORGANIZATION_UNITS. This design allows a single contract to carry multiple parties in distinct roles without duplicating contract header records.

Under a heuristic Data Vault classification mined from its foreign key structure, this object leans toward a satellite. It carries descriptive, role-bearing attributes that depend on the primary contract hub (OKC_REP_CONTRACTS_ALL), rather than acting as an independent business key hub. This classification is a modeling suggestion, not a documented implementation constraint.

Key Information Stored

The physical schema documented for 12.2.2 contains 14 columns. The most significant of these are:

  • CONTRACT_ID — The contract header identifier. Part of the composite primary key and a foreign key to OKC_REP_CONTRACTS_ALL.
  • PARTY_ID — The identifier of the party. Its source table is role-dependent (PO_VENDORS, HZ_PARTIES, or HR_ALL_ORGANIZATION_UNITS).
  • PARTY_ROLE_CODE — The classification of the party's role on the contract (for example, SUPPLIER-ORG or CUSTOMER), which determines how PARTY_ID is interpreted.
  • PARTY_LOCATION_ID — The location associated with the party for this contract.
  • OBJECT_VERSION_NUMBER — Optimistic locking column supporting concurrent update control.
  • LAST_UPDATE_DATE / LAST_UPDATED_BY — Audit columns capturing the most recent change.
  • CREATION_DATE / CREATED_BY — Audit columns capturing initial insertion.
  • LAST_UPDATE_LOGIN, PROGRAM_ID, PROGRAM_LOGIN_ID, PROGRAM_APPLICATION_ID, REQUEST_ID — Standard EBS WHO columns identifying the login, concurrent program, and request that created or modified the row.

The primary key is OKC_REP_CONTRACT_PARTIES_PK, composed of CONTRACT_ID, PARTY_ID, and PARTY_ROLE_CODE. A unique index, OKC_REP_CONTRACT_PARTIES_U1, covers the same three columns in the order CONTRACT_ID, PARTY_ROLE_CODE, PARTY_ID, serving as the documented business-key candidate.

Common Use Cases and Queries

The table is typically queried to resolve counterparties for contract reporting, to drive supplier or customer-facing views, and to feed integration extracts. A common pattern joins the contract header to the party row and then outer-joins to the appropriate master table based on role.

A representative query retrieving supplier parties for a contract:

  • SELECT c.CONTRACT_ID, c.CONTRACT_NUMBER, p.PARTY_ID, p.PARTY_ROLE_CODE FROM OKC_REP_CONTRACTS_ALL c JOIN OKC_REP_CONTRACT_PARTIES p ON p.CONTRACT_ID = c.CONTRACT_ID WHERE p.PARTY_ROLE_CODE = 'SUPPLIER-ORG';

Because PARTY_ID is polymorphic, resolving the party name requires conditional logic: join to PO_VENDORS for SUPPLIER-ORG roles and to HZ_PARTIES for CUSTOMER roles. Reporting tools such as Oracle BI Publisher and custom concurrent programs frequently consume this table to produce contract party listings and audit reports.

Related Objects

  • OKC_REP_CONTRACTS_ALL — Parent contract header. Joined on OKC_REP_CONTRACT_PARTIES.CONTRACT_ID = OKC_REP_CONTRACTS_ALL.CONTRACT_ID.
  • OKC_REP_PARTY_CONTACTS — Child table holding contacts for a contract party. Joined on OKC_REP_PARTY_CONTACTS.CONTRACT_PARTY_ID = OKC_REP_CONTRACT_PARTIES.PARTY_ID (as documented via the CONTRACT_PARTY_ID foreign key).
  • PO_VENDORS — Source of supplier organization parties (role SUPPLIER-ORG).
  • HZ_PARTIES — Source of customer parties (role CUSTOMER).
  • HR_ALL_ORGANIZATION_UNITS — Source of internal organization parties where applicable.