Results for “user_status_code”

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

Overview

The XTR_DEAL_STATUSES_V view is a reporting and integration construct within the Oracle E-Business Suite Treasury (XTR) module, owned by the APPS schema. It presents the set of valid deal status codes used to classify the lifecycle state of a Treasury deal, together with the corresponding user-facing status label, descriptive text, and control attributes governing how each status may be applied. In Oracle EBS 12.1.1 and 12.2.2, this object is classified as a VALID view and is treated as a read-oriented interface to the deal status configuration data. Its principal role is to decouple external consumers—reports, concurrent programs, OBIEE extracts, and custom integrations—from the physical storage of status metadata, exposing a stable column list including STATUS_CODE, USER_STATUS_CODE, DESCRIPTION, UPDATEABLE, AUTO_USER_SET, DEAL_TYPE, SEEDED_DESCRIPTION, and UPDATED_BY.

Underlying Base Objects

The view is defined over a single documented base object: the synonym XTR_DEAL_STATUSES, which in turn resolves to the underlying APPS table holding the deal status definitions. The ETRM metadata records this relationship as the only referenced base object, and the view text confirms a straightforward projection with no joins:

SELECT STATUS_CODE, USER_STATUS_CODE, DESCRIPTION, UPDATEABLE, AUTO_USER_SET,
       DEAL_TYPE, SEEDED_DESCRIPTION, UPDATED_BY
FROM XTR_DEAL_STATUSES

Because the definition is a direct SELECT from the base synonym, the view inherits the row set of the underlying table without filtering, aggregation, or row-level security predicates. This means the view is effectively a named, stable column interface for the deal status domain, and any referential or validation data maintained in the base table is immediately visible through the view. No additional views, tables, or PL/SQL functions are documented as contributing to the definition.

Key Columns

• STATUS_CODE — The internal system identifier for a deal status. This is the value typically referenced by foreign-key columns on deal and transaction entities.
• USER_STATUS_CODE — The user-facing status code, which is the column most commonly targeted by searches such as "user_status_code." It provides the code displayed to or entered by users, distinct from the internal STATUS_CODE.
• DESCRIPTION — The descriptive text associated with the status, used for display and reporting.
• UPDATEABLE — A flag indicating whether the status can be manually set by a user; statuses that are system-driven are generally non-updateable.
• AUTO_USER_SET — Indicates whether the status is assigned automatically by the application as part of a user-initiated action or workflow transition.
• DEAL_TYPE — The Treasury deal type to which the status applies, enabling status sets to be scoped by deal category.
• SEEDED_DESCRIPTION — The original seeded description delivered by Oracle, preserved where users have customized the DESCRIPTION value.
• UPDATED_BY — The application user identifier of the last person to modify the status definition.

Common Use Cases and Queries

The view is most frequently used to resolve a status code into its user-facing equivalent, to enumerate the permissible statuses for a given deal type, and to determine which statuses may be set manually. A typical lookup resolving user_status_code is:

SELECT status_code, user_status_code, description
FROM   xtr_deal_statuses_v
WHERE  user_status_code = :p_user_status_code;

To list manually assignable statuses for a particular deal type:

SELECT status_code, user_status_code, description
FROM   xtr_deal_statuses_v
WHERE  deal_type = :p_deal_type
AND    updateable = 'Y'
ORDER BY user_status_code;

Because the view is a direct projection of the base synonym, standard APPS schema privileges and any custom grants apply. Queries should qualify the view with the APPS schema in custom code and avoid DML, as the object is intended strictly for read access.