Results for “xtr_hedge_relationships”

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

Overview

XTR_HEDGE_RELATIONSHIPS is a Treasury module (XTR) table within the Oracle E-Business Suite 12.1.1 and 12.2.2 data model. Its documented purpose is to store hedge relationship information, meaning it records the association between hedging instruments and the exposures, attributes, or source documents they are designated to offset under the organization's hedge accounting and risk management framework. The table resides in the XTR schema and is flagged VALID in the ETRM data dictionary, confirming it is an active, supported repository object in both release levels referenced.

From a modeling perspective, the heuristic Data Vault classification mined from the foreign key structure is link. This is a suggested interpretation rather than a product-declared classification: the table's two outbound foreign keys connect it to XTR_HEDGE_ATTRIBUTES and XTR_SOURCE_TYPES, which is characteristic of a link entity resolving a many-to-many or associative relationship between two referenced hubs. Analysts building a Data Vault or dimensional layer over ETRM should treat XTR_HEDGE_RELATIONSHIPS as the associative bridge carrying the relationship-level descriptive and quantitative measures.

Key Information Stored

The documented physical schema contains 33 columns. The columns most significant for functional and reporting purposes are:

• HEDGE_RELATIONSHIP_ID — the surrogate primary key, enforced by the constraint XTR_HEDGE_RELATIONSHIPS_PK. Every relationship row is uniquely identified by this system-generated identifier.
• HEDGE_ATTRIBUTE_ID — foreign key to XTR_HEDGE_ATTRIBUTES, identifying the hedge attribute context to which the relationship belongs.
• SOURCE_TYPE_ID — foreign key to XTR_SOURCE_TYPES, identifying the source or instrument classification of the related exposure.
• PRIMARY_CODE and SECONDARY_CODE — business-facing code values identifying the parties or items joined by the relationship. These are the strongest business-key candidates in the documented metadata.
• INSTRUMENT_ITEM_FLAG — indicates whether the referenced item is treated as an instrument, supporting the hedge designation logic.
• PCT_ALLOCATION and CUR_PCT_ALLOCATION — the allocation percentage and its current-value counterpart, expressing how much of the exposure is hedged.
• REFERENCE_AMOUNT and CUR_REFERENCE_AMT — the notional or reference amount, plus the current-value equivalent.
• AMOUNT — the monetary amount associated with the relationship.
• COMMENTS — free-text annotation for the relationship.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle flexfield column set for descriptive, user-defined extension data.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns recording row provenance and change history.

No unique business index columns are separately documented beyond the primary key, so PRIMARY_CODE and SECONDARY_CODE should be treated as candidates that require verification against the actual index definitions before being relied upon as unique identifiers.

Common Use Cases and Queries

Typical reporting scenarios include listing all hedge relationships for a given hedge attribute, reconciling allocated notional amounts against exposure balances, and driving hedge accounting effectiveness documentation. A representative join pattern follows the documented foreign keys:

• Join XTR_HEDGE_RELATIONSHIPS.HEDGE_ATTRIBUTE_ID to XTR_HEDGE_ATTRIBUTES to retrieve descriptive hedge attribute context for each relationship.
• Join XTR_HEDGE_RELATIONSHIPS.SOURCE_TYPE_ID to XTR_SOURCE_TYPES to categorize relationships by source classification.
• Filter on PRIMARY_CODE or SECONDARY_CODE to isolate a specific counterparty pairing.
• Aggregate PCT_ALLOCATION across relationships for a given attribute to confirm total hedge coverage does not exceed 100 percent.
• Use CUR_PCT_ALLOCATION and CUR_REFERENCE_AMT where current-value reporting rather than original-value reporting is required.
• Sort or filter on LAST_UPDATE_DATE to identify recently amended relationships for audit review.

Because the table carries descriptive flexfield columns, any extract should decide explicitly whether ATTRIBUTE1 through ATTRIBUTE15 are required, as including them indiscriminately increases extract volume without analytical benefit.

Related Objects

The following objects are the most significant in the documented dependency chain:

• XTR_HEDGE_RELATIONSHIPS_PK — the primary key constraint on HEDGE_RELATIONSHIP_ID that guarantees uniqueness of each relationship record.
• XTR_HEDGE_ATTRIBUTES — referenced via HEDGE_RELATIONSHIP_ID's sibling column HEDGE_ATTRIBUTE_ID; provides the hedge attribute definition that the relationship serves.
• XTR_SOURCE_TYPES — referenced via SOURCE_TYPE_ID; supplies the source type classification used to interpret the relationship.
• Downstream extracts and Treasury reporting views that join across both foreign key parents to produce hedge designation and exposure coverage reporting.

No additional dependent tables, views, or public APIs are documented in the supplied metadata. Access to this table should be read-oriented for reporting; all insert, update, and delete activity is expected to occur through the Treasury application's own business logic rather than through direct SQL.