Results for “auto_user_set”

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

Overview

XTR_DEAL_STATUSES is a Treasury (XTR) module configuration table that defines the valid status codes applicable to deals within Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is a reference or lookup table: rather than storing transactional deal data, it holds the set of permissible statuses for each deal type, thereby constraining and classifying the lifecycle state of records held in the XTR_DEALS transaction table. In this role the object functions as a controlled vocabulary that drives workflow progression, validation, and reporting across the Treasury dealing process.

Mined from its foreign key structure, the heuristic Data Vault classification for this object is satellite-leaning. It carries descriptive attributes (description, updateable flag, user-facing status code) that qualify a parent business key rather than representing an independent hub of business entities. Under a Data Vault modeling suggestion, DEAL_TYPE and STATUS_CODE would serve as the composite business key, with the remaining descriptive columns treated as satellite attributes. This classification is a modeling heuristic only and does not imply any physical Data Vault implementation in EBS.

Key Information Stored

The table is owned by the XTR schema and, in the 12.2.2 documented physical schema, contains nine columns. The most significant are:

• DEAL_TYPE — Identifies the category of deal (for example, a specific Treasury instrument type). Part of the primary key and the foreign key to XTR_DEAL_TYPES.
• STATUS_CODE — The seeded system status code. Part of the primary key and the value referenced by XTR_DEALS.STATUS_CODE.
• USER_STATUS_CODE — A user-defined or display-oriented status code, distinct from the seeded code. Part of unique index XTR_DEAL_STATUSES_U2.
• DESCRIPTION — The user-facing description of the status.
• SEEDED_DESCRIPTION — The delivered description for seeded (Oracle-provided) statuses.
• UPDATEABLE — Indicates whether the status record may be modified by users.
• AUTO_USER_SET — Indicates whether the user status is set automatically by the application.
• UPDATED_BY — Audit column recording the last user to modify the row.
• ZD_EDITION_NAME — Editioning column supporting EBS online patching (introduced in 12.2).

The surrogate primary key is XTR_DEAL_STATUSES_PK, defined on (DEAL_TYPE, STATUS_CODE). Business-key candidates are captured by two unique indexes: XTR_DEAL_STATUSES_U1 on (DEAL_TYPE, STATUS_CODE, ZD_EDITION_NAME) and XTR_DEAL_STATUSES_U2 on (DEAL_TYPE, USER_STATUS_CODE, ZD_EDITION_NAME).

Common Use Cases and Queries

Typical scenarios include validating that only permitted statuses are assigned to deals, driving status-based workflow and approval rules, and producing status distribution reports across deal types. A common query joins the status table to the deal transaction table to resolve human-readable status descriptions:

• Status lookup by deal type: SELECT status_code, user_status_code, description FROM xtr_deal_statuses WHERE deal_type = :p_deal_type;
• Deal reporting with status text: SELECT d.deal_number, s.description FROM xtr_deals d, xtr_deal_statuses s WHERE d.deal_type = s.deal_type AND d.status_code = s.status_code;
• Identifying user-maintainable statuses: SELECT * FROM xtr_deal_statuses WHERE updateable = 'Y' AND auto_user_set = 'N';
• Confirming seeded versus custom statuses via SEEDED_DESCRIPTION comparison.

Related Objects

The principal related objects, derived from the documented foreign key relationships, are:

• XTR_DEAL_TYPES — Parent reference table; XTR_DEAL_STATUSES.DEAL_TYPE references it.
• XTR_DEALS — The main transaction table; XTR_DEALS.DEAL_TYPE and XTR_DEALS.STATUS_CODE reference this table, making XTR_DEAL_STATUSES the validating parent for deal status assignment.
• XTR_DEAL_STATUSES_PK, XTR_DEAL_STATUSES_U1, and XTR_DEAL_STATUSES_U2 — The primary key and unique indexes enforcing key integrity and business-key uniqueness, the last two including ZD_EDITION_NAME for editioning support.

These relationships establish XTR_DEAL_STATUSES as a dependent reference object beneath XTR_DEAL_TYPES and above XTR_DEALS in the Treasury data model.