Search Results xtr_confirmation_actions_pk




Overview

XTR_CONFIRMATION_ACTIONS is a Treasury (XTR) module configuration table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores deal confirmation action information required for a given deal type. In the Treasury confirmation workflow, a "confirmation action" defines the granular steps or activities that must be executed when a Treasury deal (for example, a foreign exchange contract, a money market instrument, or a debt instrument) is confirmed. The table effectively bridges the deal type and deal confirmation type definitions with the specific actions required, forming a master set of confirmation action templates reused across deal transactions.

From a Data Vault modeling perspective, the mined foreign key structure suggests a satellite-leaning classification. The overwhelmingly descriptive nature of the columns — confirmation requirement flags, group descriptions — and its dependency on a parent confirmation type indicate that this table functions primarily as an attribute-bearing construct rather than an independently keyed hub or a pure link. Analysts modeling the Treasury domain in a Data Vault should consider treating it as a satellite attached to a deal confirmation type hub, with the composite key forming a grouping descriptor.

Key Information Stored

The table contains five documented columns. The most significant are summarized below.

  • CONFO_ACTION_GROUP — The action group identifier. This is one of the two columns comprising the primary key (XTR_CONFIRMATION_ACTIONS_PK) and represents the business grouping of confirmation actions applied to a deal type.
  • ACTION_TYPE — The second primary key column and the sole documented foreign key. It identifies the specific confirmation action type and references XTR_DEAL_CONFO_TYPES.ACTION_TYPE, anchoring the action to a standardized confirmation type definition.
  • DEAL_TYPE — The deal type to which the confirmation action applies. This ties the action configuration to the Treasury deal taxonomy (e.g., FX, MM, or debt instruments) and is a key business-key candidate for scoping queries.
  • CONFO_REQD — A flag indicating whether the confirmation action is required for the associated deal type. This drives validation logic during deal entry and confirmation processing.
  • GROUP_DESC — Descriptive text for the action group, providing human-readable context for the CONFO_ACTION_GROUP value and supporting reporting and setup verification.

The composite primary key (CONFO_ACTION_GROUP, ACTION_TYPE) is the surrogate/structural key, while DEAL_TYPE combined with the group and action type forms the effective business-key candidate used in operational lookups.

Common Use Cases and Queries

Typical use cases include setup validation, confirmation requirement reporting, and integration checks before deal confirmation processing.

  • Identifying all confirmation actions defined for a specific deal type: SELECT confo_action_group, action_type, confo_reqd FROM xtr_confirmation_actions WHERE deal_type = :deal_type;
  • Joining to the confirmation type reference to resolve action descriptions: SELECT a.confo_action_group, t.action_type, a.confo_reqd FROM xtr_confirmation_actions a, xtr_deal_confo_types t WHERE a.action_type = t.action_type;
  • Reporting action groups and their descriptive labels for setup review: SELECT DISTINCT confo_action_group, group_desc FROM xtr_confirmation_actions ORDER BY confo_action_group;
  • Detecting configuration gaps where no required confirmation action exists for a deal type: filter on confo_reqd = 'Y' and compare against active deal types.

Related Objects

The table participates in a tightly scoped referential relationship within the Treasury module.

  • XTR_DEAL_CONFO_TYPES — Referenced via XTR_CONFIRMATION_ACTIONS.ACTION_TYPE; the parent definition of confirmation types that each action instantiates.
  • XTR_CONFIRMATION_ACTIONS_PK — The primary key constraint enforcing uniqueness of (CONFO_ACTION_GROUP, ACTION_TYPE).
  • XTR deal confirmation transaction tables — Deal confirmation processing in Treasury consumes these action definitions to determine which confirmations are required for a given deal.
  • Treasury deal setup tables — DEAL_TYPE values align with the Treasury deal type master, which supplies the taxonomy used in the DEAL_TYPE column.

Because the documented foreign key surface is limited to XTR_DEAL_CONFO_TYPES, this object should be treated as a configuration-level dependency of the broader Treasury confirmation process rather than a high-fan-out transactional table.