Results for “parameter_value_code”

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

Overview

XTR_COMPANY_PARAMETERS is a Treasury (XTR) module table that stores transactional parameters specific to each company (legal entity) within Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as a company-level configuration store, allowing Treasury to apply different behavioral rules — such as defaulting conventions, processing options, or value mappings — on a per-company basis rather than globally. Because it holds descriptive attributes about companies referenced in XTR_PARTY_INFO, rather than the companies themselves, it behaves as a satellite-like structure in Data Vault modeling terms. This classification is a heuristic suggestion only; it reflects the table's role as an attribute-bearing, child table rather than a hub or link.

Key Information Stored

The table contains ten documented columns. The surrogate primary key is COMPANY_PARAMETER_ID, defined by the constraint XTR_COMPANY_PARAMETERS__PK. A unique index, XTR_COMPANY_PARAMETERS_U1, covers COMPANY_CODE and PARAMETER_CODE, making that pairing the natural business-key candidate that prevents duplicate parameter definitions for a given company.

• COMPANY_PARAMETER_ID — surrogate primary key identifying each parameter row.
• COMPANY_CODE — foreign key to XTR_PARTY_INFO; identifies the legal entity or company owning the parameter.
• PARAMETER_CODE — the code naming a specific transactional parameter being configured.
• PARAMETER_VALUE_CODE — a coded/validated value for the parameter, typically drawn from a lookup.
• PARAMETER_VALUE — a free-form or extended value for parameters not constrained to a code.
• CREATED_BY, CREATION_DATE — audit fields recording row creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — audit fields capturing the most recent change and session.

Common Use Cases and Queries

Treasury administrators and developers query this table to retrieve the effective parameters for a company, to audit configuration changes, or to join parameter values into settlement, deal, and counterparty reporting. A typical retrieval by business key uses the unique index:

• Fetch a parameter for a company: SELECT parameter_value_code, parameter_value FROM xtr_company_parameters WHERE company_code = :p_company AND parameter_code = :p_param;
• List all parameters configured for a company: SELECT parameter_code, parameter_value_code, parameter_value FROM xtr_company_parameters WHERE company_code = :p_company ORDER BY parameter_code;
• Audit recent changes: SELECT company_code, parameter_code, last_updated_by, last_update_date FROM xtr_company_parameters WHERE last_update_date >= :p_since ORDER BY last_update_date DESC;
• Detect orphaned references: SELECT c.company_code FROM xtr_company_parameters c LEFT JOIN xtr_party_info p ON p.company_code = c.company_code WHERE p.company_code IS NULL;

Because the business key is COMPANY_CODE + PARAMETER_CODE, reporting logic should always filter on both to guarantee singleton results.

Related Objects

• XTR_PARTY_INFO — referenced by XTR_COMPANY_PARAMETERS.COMPANY_CODE; the parent company/party record supplying company identity.
• XTR_A_COMPANY_PARAMETERS — audit table referencing XTR_COMPANY_PARAMETERS.COMPANY_PARAMETER_ID, capturing historical versions of each parameter row.
• XTR_COMPANY_PARAMETERS__PK — the primary key constraint on COMPANY_PARAMETER_ID.
• XTR_COMPANY_PARAMETERS_U1 — the unique index on COMPANY_CODE, PARAMETER_CODE.

These relationships make XTR_COMPANY_PARAMETERS a dependent configuration satellite of the company/party entity, with audit history maintained in parallel.