Results for “okc_price_att_values_h”

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

Overview

OKC_PRICE_ATT_VALUES_H is a Contracts Core (OKC) table that stores the values of price attributes for an object, used to derive the price for a contract header and contract line. In Oracle EBS 12.1.1 and 12.2.2, this table supports the pricing engine within the Contracts module by capturing the qualifier and pricing attribute combinations that determine how prices are calculated for a given contract or line. The table resides in the OKC schema and is classified as VALID.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure is a link table. It connects contract headers and contract lines to their associated pricing attribute values, and it references FND_SECURITY_GROUPS for security context. The presence of MAJOR_VERSION in the unique index suggests it also functions in a versioned capacity, consistent with the "_H" suffix convention used for history or version tracking in EBS.

Key Information Stored

The table contains 218 columns, the majority of which are repeating sets of pricing and qualifier attributes. The most significant columns include:

• ID — The surrogate primary key (constraint OCO_38752808), uniquely identifying each price attribute value record.
• MAJOR_VERSION — Part of the unique index OKC_PRICE_ATT_VALUES_H_U1 alongside ID, supporting version tracking of price attribute values.
• CHR_ID — Foreign key to OKC_K_HEADERS_B, linking the price attribute values to a contract header.
• CLE_ID — Foreign key to OKC_K_LINES_B, linking the price attribute values to a contract line.
• FLEX_TITLE — Identifies the descriptive flexfield context or title associated with the pricing attributes.
• PRICING_CONTEXT — The context under which pricing attributes are evaluated.
• PRICING_ATTRIBUTE1 through PRICING_ATTRIBUTE100 — Repeating columns holding the actual pricing attribute values used to derive the contract price.
• QUALIFIER_CONTEXT — The context for qualifier attributes.
• QUALIFIER_ATTRIBUTE1 through QUALIFIER_ATTRIBUTE100 — Repeating columns holding qualifier values that further refine pricing eligibility.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing multi-org/security group access.
• OBJECT_VERSION_NUMBER — Supports optimistic locking for concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard audit columns.

The unique index identifies (ID, MAJOR_VERSION) as the business-key candidate, distinguishing it from the surrogate ID primary key.

Common Use Cases and Queries

Typical scenarios involve tracing how a contract header or line price was derived, auditing pricing attribute combinations, and reporting on qualifier usage across contracts.

• Retrieving all price attribute values for a given contract header:

  SELECT * FROM OKC.OKC_PRICE_ATT_VALUES_H WHERE CHR_ID = :p_chr_id AND MAJOR_VERSION = :p_version;

• Joining to contract lines to see line-level pricing attributes:

  SELECT p.* FROM OKC.OKC_PRICE_ATT_VALUES_H p, OKC.OKC_K_LINES_B l WHERE p.CLE_ID = l.ID;

• Reporting on pricing context distribution:

  SELECT PRICING_CONTEXT, COUNT(*) FROM OKC.OKC_PRICE_ATT_VALUES_H GROUP BY PRICING_CONTEXT;

• Auditing changes using MAJOR_VERSION to compare versions of price attribute values for the same ID.

Related Objects

The following objects are most significant in relation to OKC_PRICE_ATT_VALUES_H, based on documented foreign key and primary key relationships:

• OKC_K_HEADERS_B — Referenced via CHR_ID; the contract header table. Joins allow header-level price attribute analysis.
• OKC_K_LINES_B — Referenced via CLE_ID; the contract line table. Joins enable line-level pricing derivation analysis.
• FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID; enforces security group access control.
• OKC_PRICE_ATT_VALUES_H_U1 — Unique index on (ID, MAJOR_VERSION), supporting version-aware queries and enforcing uniqueness.
• OCO_38752808 — Primary key constraint on ID, ensuring record-level uniqueness.

Additionally, the OKC schema includes related pricing and contract tables and APIs such as OKC_K_HEADERS_B and OKC_K_LINES_B that interact with pricing attribute values during contract creation, amendment, and pricing derivation processes. The table's security group association also links it to multi-org access control routines.