Search Results user_maintainable_flag

Overview

ASO_STATUS_TRANSITIONS_V is a seeded APPS-owned database view in the Oracle E-Business Suite Order Capture (ASO) module. It exposes the transition rules that govern movement between quote statuses in Oracle Quoting and related order capture flows. In EBS 12.1.1 and 12.2.2, the view serves as the reporting and integration face of the underlying transition-rule table, joining each transition record to the descriptive data of its target status so that consumers receive readable status codes, meanings, and descriptions alongside the raw identifiers.

Because the view is defined in the APPS schema and remains VALID across both releases, it can be queried directly by custom reports, concurrent programs, discovery-based integrations, and SOA/Bpel composites without requiring knowledge of the physical table layout. It is not an interface table; it is read-oriented and inherits the WHO columns of its base object, making it suitable for audit queries as well.

Underlying Base Objects

The documented ETRM metadata for 12.2.2 lists two referenced base objects: ASO_QUOTE_STATUSES_VL (a view) and ASO_QUOTE_STATUS_TRANSITIONS (a synonym). The view text confirms this relationship. It selects all columns from ASO_QUOTE_STATUS_TRANSITIONS (aliased T) and joins ASO_QUOTE_STATUSES_VL (aliased VL) on VL.QUOTE_STATUS_ID = T.TO_STATUS_ID.

Two characteristics follow from this definition. First, the join is to the target status only; the source status (FROM_STATUS_ID) is returned as an ID without descriptive columns. Second, because ASO_QUOTE_STATUSES_VL is a _VL view, it is language-enabled, so TO_STATUS_CODE, TO_STATUS_MEANING, and TO_STATUS_DESCRIPTION are returned in the session's language. The view therefore inherits NLS behavior from the status lookup layer while remaining a flat, denormalized projection for the transition records themselves.

Key Columns

• TRANSITION_ID — Primary identifier for the transition rule.
• USER_MAINTAINABLE_FLAG — Indicates whether the transition can be maintained by end users through the application UI; this is the column most frequently used to filter user-editable versus system-controlled transitions.
• LOV_DRIVEN_FLAG — Identifies transitions that are exposed through a list of values (LOV) in the quoting UI.
• ENABLED_FLAG — Active/inactive indicator for the transition rule.
• FROM_STATUS_ID / TO_STATUS_ID — Source and destination quote status identifiers defining the directed edge between statuses.
• TO_STATUS_CODE, TO_STATUS_MEANING, TO_STATUS_DESCRIPTION — NLS-sensitive descriptive attributes of the target status, sourced from ASO_QUOTE_STATUSES_VL.
• ATTRIBUTE_CATEGORY through ATTRIBUTE15 — DFF (descriptive flexfield) columns carried on the transition record.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Standard WHO and concurrent-program audit columns.
• ROW_ID — Row identifier selected as T.ROWID.

Common Use Cases and Queries

Typical scenarios include documenting the allowed status flow for quote lifecycles, validating configuration after patching, and driving custom workflow or approval logic that must respect user-maintainable transitions. A frequent query filters on the flag the user searched for:

• SELECT transition_id, from_status_id, to_status_id, to_status_code, to_status_meaning, lov_driven_flag FROM apps.aso_status_transitions_v WHERE user_maintainable_flag = 'Y' AND enabled_flag = 'Y' ORDER BY from_status_id, to_status_id;
• Enumerating the full set of target statuses reachable from a given source: SELECT to_status_code, to_status_meaning FROM apps.aso_status_transitions_v WHERE from_status_id = :p_from_status_id AND enabled_flag = 'Y';
• Auditing recently changed rules: SELECT transition_id, last_updated_by, last_update_date FROM apps.aso_status_transitions_v WHERE last_update_date >= :p_since;

Because the view omits source-status descriptions, queries requiring both endpoints should join back to ASO_QUOTE_STATUSES_VL on FROM_STATUS_ID. All access requires APPS-level read privileges, consistent with standard EBS view grants.