Search Results xtr_pro_param




Overview
Explore in AI Chat

Overview

XTR_PRO_PARAM is the Treasury system parameter settings table within the Oracle E-Business Suite Treasury module (XTR). The table is owned by the XTR schema and resides in the ETRM (Enterprise Treasury Management) data model. It serves as the central repository for configuration values that govern the behavior of Treasury functions, including deal processing, cash management, risk analysis, and accounting integration. Each row represents a named parameter whose value controls a specific aspect of Treasury processing at the installation or (where applicable) edition level.

The documented metadata classifies XTR_PRO_PARAM as a standalone object under the heuristic Data Vault modeling suggestion, rather than a hub, link, or satellite. This classification reflects that the table has no documented foreign key dependencies and operates as an independent configuration entity. In Data Vault terms, a standalone object is best modeled as its own hub or reference table, with its attributes carried directly rather than split into satellite structures.

Key Information Stored

The table contains eleven documented columns in the ETRM 12.2.2 physical schema. The most significant columns are:

  • UNIQUE_REF_NUM — the surrogate primary key, enforced by the XTR_PRO_PARAM_PK constraint. It uniquely identifies each parameter row.
  • PARAM_NAME — the business identifier for the parameter. Together with ZD_EDITION_NAME it forms the unique business key constraint XTR_PRO_PARAM_U1, ensuring no duplicate parameter definitions exist within an edition.
  • ZD_EDITION_NAME — the edition identifier introduced by the E-Business Suite Edition-Based Redefinition (EBR) architecture in Release 12.2. It scopes parameter values to a specific edition, which is important for online patching and multi-edition environments.
  • PARAM_VALUE — the actual configuration value assigned to the parameter, typically stored as a character string and interpreted by Treasury application logic.
  • PARAM_TYPE — indicates the data type or category of the parameter, allowing applications to validate and interpret PARAM_VALUE correctly.
  • DESCRIPTION — the human-readable explanation of the parameter's purpose, used heavily in setup and administration screens.
  • AUDIT_INDICATOR — flags whether changes to the parameter are subject to auditing or tracking.

The remaining columns — UPDATED_BY, UPDATED_ON, CREATED_BY, and CREATED_ON — are standard Oracle EBS WHO (Who Columns) audit attributes recording the user and timestamp of the last insert and update. Note that no ORIGIN or LAST_UPDATE_DATE columns are documented in this schema.

Common Use Cases and Queries

The primary use case is retrieving Treasury configuration settings for validation logic, reporting, and troubleshooting. A typical query retrieves the current value of a specific parameter:

  • SELECT param_name, param_value, param_type, description FROM xtr.xtr_pro_param WHERE param_name = :p_name;
  • SELECT param_name, param_value, created_by, created_on, updated_by, updated_on FROM xtr.xtr_pro_param ORDER BY param_name;

Reporting scenarios include generating a full parameter audit report for SOX or internal control reviews, comparing configuration between instances, and verifying setup completeness after a Treasury implementation or patch. Because of the EBR architecture, any query should account for ZD_EDITION_NAME, either by filtering on a specific edition or by relying on the edition context of the connecting session. Administrators frequently join this table to application lookup views to translate parameter names into descriptive labels for end-user setup screens.

Related Objects

The metadata documents XTR_PRO_PARAM as standalone, with no foreign keys to related tables. Consequently the relationships below are the standard Treasury reference and transactional objects that depend on or are configured through these parameter settings:

  • XTR_PRO_PARAM_PK — the primary key constraint on UNIQUE_REF_NUM.
  • XTR_PRO_PARAM_U1 — the unique constraint on (PARAM_NAME, ZD_EDITION_NAME).
  • XTR_DEALS / XTR_DEAL_MASTER — Treasury deal records whose processing behavior is governed by parameters such as trade number generation and defaulting rules.
  • XTR_CASHFLOWS — cash flow schedules whose calculations may reference Treasury parameters.
  • XTR_RISK_* — risk analysis entities that consume limit and valuation parameters.
  • FND_* concurrent and profile options used in conjunction with these settings.
  • ZD_EDITION_NAME references — the edition metadata maintained by the EBS online patching infrastructure.

Because documentation confirms no inter-table foreign keys, any joining logic should be validated against specific application usage rather than assumed referential integrity.