Results for “xtr_price_models”

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

Overview

XTR_PRICE_MODELS is a Treasury (XTR) module configuration table in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the set of valid pricing models available for revaluing the fair value of specific Treasury deal types. The table contains both models seeded by Oracle and models defined by the user, making it a blend of delivered reference data and customer-maintained configuration. Pricing models recorded here are consumed during fair-value revaluation processing and supplement the models Oracle seeds by default. The object is owned by the XTR schema and holds VALID status in the data dictionary.

From a dimensional modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification. Under a Data Vault interpretation, the row-level attributes that describe and authorize each pricing model behave like satellite payload attached to a business key rather than an independent hub or a pure link. This classification is a heuristic suggestion derived from the FK topology, not a documented Oracle construct.

Key Information Stored

The table is physically documented with eleven columns. The most significant are described below.

• PRICE_MODEL_ID — the surrogate primary key, enforced by the XTR_PRICE_MODELS_PK constraint. It uniquely identifies each pricing model row and is the column downstream tables reference.
• DEAL_TYPE — identifies the Treasury deal type to which the pricing model applies. This is a foreign key to XTR_DEAL_TYPES and anchors the model to a specific instrument category.
• CODE — the short business identifier or code for the pricing model, used by users when selecting a model for revaluation.
• COMPONENT_MODEL_FLAG — indicates whether the pricing model is treated as a component model, influencing how the model is assembled during valuation.
• AUTHORIZED — controls whether the pricing model is enabled and available for use in revaluation. Only authorized models are eligible for processing.
• ZD_EDITION_NAME — the editioning column introduced with EBS 12.2 online patching, used to scope rows to the correct edition of the application.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS audit columns recording who created and last modified each row and when.

The unique index XTR_PRICE_MODELS_U1 covers (DEAL_TYPE, CODE, ZD_EDITION_NAME). This combination is the business-key candidate: within a given edition, a deal type and model code pair must be unique even though the surrogate PRICE_MODEL_ID remains the enforced primary key.

Common Use Cases and Queries

Typical usage centers on configuration review, authorization auditing, and lookup resolution during revaluation.

• Listing all authorized models for a deal type, joining the business key to the deal type table:

  SELECT p.price_model_id, p.code, p.deal_type
  FROM   xtr.xtr_price_models p
  WHERE  p.authorized = 'Y'
  AND    p.zd_edition_name = 'V_2019_...';

• Resolving a model code back to its surrogate key for downstream joins, using the unique index columns as the search predicate.
• Auditing user-defined versus Oracle-seeded models by comparing creation metadata and authorization status.
• Reporting on deal types that have no authorized pricing model, to identify configuration gaps before revaluation runs.
• Reviewing change history through the LAST_UPDATED_BY and LAST_UPDATE_DATE audit columns for SOX or internal control purposes.

Because 12.2 uses editioning, queries should consistently filter on ZD_EDITION_NAME to avoid returning rows from obsolete editions.

Related Objects

The most significant relationships for this table are:

• XTR_DEAL_TYPES — referenced by XTR_PRICE_MODELS.DEAL_TYPE. This parent table defines the Treasury deal types each pricing model is associated with; it is the primary join partner.
• XTR_PRICE_MODELS_PK — the primary key constraint on PRICE_MODEL_ID, used by any child table referencing a pricing model.
• XTR_PRICE_MODELS_U1 — the unique index on (DEAL_TYPE, CODE, ZD_EDITION_NAME), enforcing the business key.
• Downstream Treasury revaluation and fair-value processing objects that reference PRICE_MODEL_ID to select the valuation model applied to a deal.
• Treasury setup and concurrent program definitions that consume authorized pricing models during revaluation.

These objects should be treated as the core dependency set when tracing how a pricing model flows from configuration into Treasury fair-value calculation.