Results for “pat_id”

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

Overview

The OKC_PRICE_ADJ_ASSOCS table resides in the OKC schema, which belongs to the Contracts Core product within Oracle E-Business Suite. Its documented purpose is to associate price adjustments with the specific object for which a price has been adjusted. In practical terms, this table operates as the connective layer between a price adjustment definition and the contractual or billing entity that the adjustment applies to, allowing a single adjustment to be tied to the correct billing context without duplicating the adjustment definition itself.

From a Data Vault modeling perspective, the mined foreign-key structure classifies this object heuristically as a link table. The classification is a suggestion rather than a directive, but it reflects the object's structure: the table primarily holds foreign keys pointing to independent entities, with the surrogate ID column acting as the primary key rather than serving as a composite business key. The presence of multiple foreign keys to distinct destination tables (billing lines, contract lines, and adjustment records) reinforces the link interpretation.

Key Information Stored

The table contains seventeen documented columns, of which the following are most significant for understanding and querying the data:

• ID — The surrogate primary key, enforced by OKC_PRICE_ADJ_ASSOCS_PK and mirrored in the unique index OKC_PRICE_ADJ_ASSOCS_U1. This is a system-generated identifier and is not a business key.
• PAT_ID — Foreign key to OKC_PRICE_ADJUSTMENTS, identifying the price adjustment being associated.
• PAT_ID_FROM — A second foreign key to OKC_PRICE_ADJUSTMENTS, indicating the source or originating adjustment in a transfer or derivation relationship.
• CLE_ID — Foreign key to OKC_K_LINES_B, linking the association to a specific contract line.
• BSL_ID — Foreign key to OKS_BILL_SUB_LINES, linking to a billing sub-line.
• BCL_ID — Foreign key to OKS_BILL_CONT_LINES, linking to a billing contract line.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting multi-tenant data segregation and access control.
• OBJECT_VERSION_NUMBER — Supports optimistic locking for concurrent update control.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard EBS audit columns recording who created and last modified each row and when.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID, LAST_UPDATE_LOGIN — Concurrent program and session context columns captured automatically during DML.

The most important business-relevant attributes are therefore the four entity pointers (PAT_ID, PAT_ID_FROM, CLE_ID, plus the billing line references), since these determine which adjustment applies to which object.

Common Use Cases and Queries

Typical usage involves reconciling price adjustments against the contract lines and billing lines they affect. A common pattern joins the association table to OKC_PRICE_ADJUSTMENTS to retrieve adjustment detail alongside the contract line context:

SELECT a.ID, a.PAT_ID, a.CLE_ID, p.NAME
FROM   OKC.OKC_PRICE_ADJ_ASSOCS a,
       OKC.OKC_PRICE_ADJUSTMENTS p
WHERE  a.PAT_ID = p.ID
AND    a.CLE_ID = :contract_line_id;

Reporting use cases include identifying all billing sub-lines affected by a given adjustment, tracing adjustment propagation across contract structures via PAT_ID_FROM, and auditing historical changes through the standard audit columns. Developers authoring extensions or interfaces should treat this table as insert-mostly linkage data and avoid unsafe manual updates that could break referential integrity.

Related Objects

• OKC_PRICE_ADJUSTMENTS — The definition of each adjustment; joined on PAT_ID and PAT_ID_FROM.
• OKC_K_LINES_B — Contract lines; joined on CLE_ID.
• OKS_BILL_SUB_LINES — Billing sub-lines; joined on BSL_ID.
• OKS_BILL_CONT_LINES — Billing contract lines; joined on BCL_ID.
• FND_SECURITY_GROUPS — Security group definitions; joined on SECURITY_GROUP_ID.
• OKC_PRICE_ADJ_ASSOCS_PK / _U1 — Primary key constraint and supporting unique index on ID.