Results for “last_batch_id”

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

Overview

XTR_HEDGE_ATTRIBUTES is a Treasury (XTR) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the descriptive and control attributes of a hedge relationship within Oracle Treasury's hedge accounting functionality. It records the start and end dates of the hedge, the hedge status, and supporting information such as the responsible company, the hedging strategy, and the hedge type or approach. In practice, this is the central header-like record that ties a hedge designation to its subsequent effectiveness testing, relationship mapping, and reclassification activity.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure is satellite-leaning. This is a modeling suggestion rather than a delivered design: the table carries a surrogate key (HEDGE_ATTRIBUTE_ID) together with a cluster of descriptive and status attributes that would naturally be modeled as satellite columns attached to a hedge business key, while several of its columns (STRATEGY_CODE, COMPANY_CODE, RETRO_DEALER_CODE, PROS_DEALER_CODE, REQUEST_ID) behave as foreign-key references to reference or link structures.

Key Information Stored

XTR_HEDGE_ATTRIBUTES is documented with 52 physical columns. The most significant are as follows.

• HEDGE_ATTRIBUTE_ID — the surrogate primary key of the table; the column to which all dependent testing and relationship tables point.
• HEDGE_STATUS — the current lifecycle state of the hedge designation (for example, active, discontinued, or de-designated).
• HEDGE_DESCRIPTION — the free-text description of the hedge.
• HEDGE_APPROACH — the hedge type or accounting approach applied.
• START_DATE and END_DATE — the effective period of the hedge designation.
• DISCONTINUE_DATE — the date on which the hedge ceased to qualify.
• HEDGE_CURRENCY and HEDGE_AMOUNT — the currency and notional amount being hedged.
• STRATEGY_CODE — foreign key to XTR_HEDGE_STRATEGIES, identifying the hedging strategy.
• COMPANY_CODE — foreign key to XTR_PARTY_INFO, identifying the legal entity or company owning the hedge.
• RETRO_METHOD, RETRO_TOLERANCE_MIN, RETRO_TOLERANCE_MAX — parameters governing retrospective effectiveness testing.
• PROS_METHOD, PROS_FREQUENCY_NUM, PROS_FREQUENCY_UNIT, PROS_TOLERANCE_MIN, PROS_TOLERANCE_MAX — parameters governing prospective effectiveness testing and its test frequency.
• RETRO_DEALER_CODE and PROS_DEALER_CODE — foreign keys to XTR_DEALER_CODES identifying the dealers associated with each test type.
• FULFILLED_AMOUNT, INIT_FAIR_VALUE_RATE, EXCLUSION_ITEM_CODE — amount and valuation attributes supporting measurement and exclusion-item handling.
• REQUEST_ID — foreign key to FND_CONCURRENT_REQUESTS, recording the concurrent request that last processed the record.

The descriptive ATTRIBUTE1–15 columns and the standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) provide the usual DFF and auditability support. The primary key is documented as HEDGE_ATTRIBUTE_ID; no separate unique index on a business key is documented in the supplied metadata.

Common Use Cases and Queries

The table is most often queried to report active hedge designations and their testing parameters, and to drive or audit the Treasury effectiveness testing programs.

• Listing currently active hedges with strategy and company context:

  SELECT h.hedge_attribute_id, h.hedge_description, h.hedge_status,
         h.start_date, h.end_date, h.hedge_currency, h.hedge_amount,
         s.strategy_code, p.party_name
  FROM   xtr.xtr_hedge_attributes h,
         xtr.xtr_hedge_strategies s,
         xtr.xtr_party_info p
  WHERE  h.strategy_code = s.strategy_code
  AND    h.company_code  = p.company_code
  AND    h.hedge_status  = 'ACTIVE';

• Identifying hedges requiring retrospective testing, based on the recorded tolerance and method parameters (RETRO_METHOD, RETRO_TOLERANCE_MIN/MAX).
• Joining to XTR_HEDGE_RETRO_TESTS and XTR_HEDGE_PRO_TESTS on HEDGE_ATTRIBUTE_ID to produce an effectiveness testing history per hedge.
• Tracing hedges back to the concurrent program run that processed them via REQUEST_ID against FND_CONCURRENT_REQUESTS.
• Auditing discontinued hedges by filtering on DISCONTINUE_DATE and DEDESIGNATED_DATE.

Related Objects

The following dependencies are the most significant for navigation and join design.

• XTR_HEDGE_STRATEGIES — referenced by STRATEGY_CODE.
• XTR_PARTY_INFO — referenced by COMPANY_CODE.
• XTR_DEALER_CODES — referenced twice, by RETRO_DEALER_CODE and PROS_DEALER_CODE.
• FND_CONCURRENT_REQUESTS — referenced by REQUEST_ID.
• XTR_HEDGE_RELATIONSHIPS — references HEDGE_ATTRIBUTE_ID, linking hedges to hedged items.
• XTR_HEDGE_RETRO_TESTS and XTR_HEDGE_PRO_TESTS — reference HEDGE_ATTRIBUTE_ID and store retrospective and prospective effectiveness test results.
• XTR_DEAL_RETRO_TESTS — references HEDGE_ATTRIBUTE_ID for deal-level retrospective results.
• XTR_RECLASS_DETAILS — references HEDGE_ATTRIBUTE_ID for reclassification accounting entries.
• XTR_HEDGE_CRITERIA — references HEDGE_ATTRIBUTE_ID, capturing qualification criteria.