Results for “old_pricing_context”

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

Overview

CSI_I_PRICING_ATTRIBS_H is a historical audit table within the Oracle E-Business Suite Install Base (CSI) module. It is documented with 250 columns and is owned by the CSI schema, carrying a VALID status in both Oracle EBS 12.1.1 and 12.2.2. The object's documented description identifies it as "Instance Pricing Attributes History," indicating that it preserves prior and current states of pricing attribute values associated with instances tracked in the Install Base.

The table functions as a temporal companion to CSI_I_PRICING_ATTRIBS. Where the base table retains the active pricing attribute record for a given instance, CSI_I_PRICING_ATTRIBS_H stores row-level change history, capturing both the old and new values whenever a pricing attribute is created, modified, or superseded. Each history row is anchored by a transaction identifier, allowing consumers to trace who or what changed a pricing attribute and when, in the context of a discrete business event.

From a modeling perspective, the ETRM metadata supplies a heuristic Data Vault classification of link for this object. That classification is a suggestion derived from the foreign-key structure rather than a documented design intent; it reflects the fact that the table principally associates a pricing attribute with a transaction, rather than holding a standalone descriptive entity or a purely descriptive satellite of one hub.

Key Information Stored

The physical schema is dominated by paired OLD_ and NEW_ column sets that record the before-and-after state of a pricing attribute. The most consequential columns are as follows.

• PRICE_ATTRIB_HISTORY_ID — Surrogate primary key, enforced by the CSI_I_PRICING_ATTRIBS_H_PK constraint and backed by the unique index CSI_I_PRICING_ATTRIBS_H_U01. This is the system-generated identity of each history row.
• PRICING_ATTRIBUTE_ID — Foreign key to CSI_I_PRICING_ATTRIBS, identifying the base pricing attribute record whose lifecycle this history row describes.
• TRANSACTION_ID — Foreign key to CSI_TRANSACTIONS, tying the change to a specific Install Base transaction event.
• OLD_PRICING_CONTEXT / NEW_PRICING_CONTEXT — The pricing context descriptor before and after the change.
• OLD_PRICING_ATTRIBUTE1 through OLD_PRICING_ATTRIBUTE100 and NEW_PRICING_ATTRIBUTE1 through NEW_PRICING_ATTRIBUTE100 — The core flexfield-style value carriers, presented in paired OLD/NEW form so that any individual attribute change can be reconstructed. This is the largest column block in the table.
• OLD_ACTIVE_START_DATE / NEW_ACTIVE_START_DATE and OLD_ACTIVE_END_DATE / NEW_ACTIVE_END_DATE — Effective-dating boundaries captured on either side of the change.
• OLD_CONTEXT / NEW_CONTEXT and OLD_ATTRIBUTE1 through OLD_ATTRIBUTE15 and NEW_ATTRIBUTE1 through NEW_ATTRIBUTE15 — The descriptive flexfield context and attribute values preserved across the change.
• OBJECT_VERSION_NUMBER — Optimistic locking version, used by the OA Framework and concurrent programs to detect stale updates.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing multi-org / data security partitioning.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO columns that identify the actor and timestamp of the history record itself.
• FULL_DUMP_FLAG and MIGRATED_FLAG — Operational flags indicating whether the row represents a complete snapshot versus a delta, and whether the row was introduced through migration.
• CSI_I_PRICING_ATTRIBS_H_U02 (TRANSACTION_ID, PRICING_ATTRIBUTE_ID) — A documented unique index acting as a business-key candidate, establishing that a given pricing attribute may appear at most once per transaction within the history.

Common Use Cases and Queries

The primary use case is retrospective analysis: determining what a pricing attribute looked like at a prior point in time, or identifying which transaction altered it. A representative query joins the history table to its parent attribute and to the transaction that produced the change.

Typical SQL patterns include:

• Retrieving the full change log for a single attribute: SELECT * FROM csi.csi_i_pricing_attribs_h WHERE pricing_attribute_id = :id ORDER BY creation_date;
• Reconstructing the state at a point in time by selecting the NEW_ column set from the latest history row whose creation date precedes the target timestamp.
• Joining to CSI_TRANSACTIONS to attribute each change to a transaction type and date: SELECT h.*, t.* FROM csi.csi_i_pricing_attribs_h h, csi.csi_transactions t WHERE h.transaction_id = t.transaction_id;
• Joining to CSI_I_PRICING_ATTRIBS to compare current versus historical values, which supports reconciliation reports and audit packs.
• Security-scoped reporting that filters on SECURITY_GROUP_ID to respect operating unit partitions.

Because of the 100-pair pricing attribute block and the 15-pair DFF attribute block, ETL and reporting layers should favor column projection over SELECT *, and should treat the table as append-oriented rather than update-in-place.

Related Objects

The following objects are the most significant dependencies, per the documented foreign-key relationships.

• CSI_I_PRICING_ATTRIBS — The base pricing attribute table; joined via CSI_I_PRICING_ATTRIBS_H.PRICING_ATTRIBUTE_ID = CSI_I_PRICING_ATTRIBS.PRICING_ATTRIBUTE_ID. This is the parent object whose history is being tracked.
• CSI_TRANSACTIONS — The Install Base transaction table; joined via CSI_I_PRICING_ATTRIBS_H.TRANSACTION_ID = CSI_TRANSACTIONS.TRANSACTION_ID. Supplies the business event context for each historical row.
• FND_SECURITY_GROUPS — Referenced through SECURITY_GROUP_ID, driving data security and multi-org visibility.
• CSI_I_PRICING_ATTRIBS_H_PK — The unique index on PRICE_ATTRIB_HISTORY_ID that enforces row identity.
• CSI_I_PRICING_ATTRIBS_H_U01 — Unique index on PRICE_ATTRIB_HISTORY_ID, a further business-key candidate.
• CSI_I_PRICING_ATTRIBS_H_U02 — Unique index on (TRANSACTION_ID, PRICING_ATTRIBUTE_ID), the composite business-key candidate.
• CSI_I_PRICING_ATTRIBS_H_U03 — Additional unique index documented on the same table, supporting alternate access paths.

Together these relationships position CSI_I_PRICING_ATTRIBS_H as the audit spine for Install Base pricing attribute changes, linking attribute identity to transaction provenance under a security-group partition.