Search Results fix_details_required_flag

Overview

CSS_DEF_STATUSES_VL is a translatable (VL, "view with language") database view historically shipped within the Oracle E-Business Suite Support module (CSS). It exposes the definition of defect status values — the lookup records that classify the lifecycle stage of a defect (bug), such as Open, Working, Resolved, Closed, or customer-specific variants. As a VL view, it joins a base table to a translation table and filters on the session language, returning the user-facing NAME and DESCRIPTION for each status.

In the context of Oracle EBS 12.1.1 and 12.2.2, the object is documented as belonging to the obsolete CSS – Support product. Per the ETRM documentation, it is not implemented in the reference database, meaning the object may not exist on every environment; it existed in legacy Support (pre-CRM-application) installations. Its practical role is referential: reporting and integration code that needs to resolve a numeric STATUS_ID to a meaningful, language-specific label would query this view rather than joining the base and translation tables manually.

Underlying Base Objects

The view text is defined over two tables:

• CSS_DEF_STATUSES_B — the base (non-translatable) table holding the STATUS_ID, who-columns, date-effectivity columns, functional flags, and the DFF attribute columns.
• CSS_DEF_STATUSES_TL — the translation table holding NAME and DESCRIPTION per language.

The join condition is B.STATUS_ID = T.STATUS_ID AND T.LANGUAGE = USERENV('LANG'), which restricts rows to the language of the current session. The ETRM metadata records no other referenced base objects, and no owner is documented for the 12.2.2 view. The ROW_ID column is sourced from B.ROWID.

Key Columns

• STATUS_ID — primary key of the status definition; the foreign key used by defect records.
• NAME / DESCRIPTION — translated display values from CSS_DEF_STATUSES_TL.
• START_DATE_ACTIVE / END_DATE_ACTIVE — date-effectivity range controlling when the status is usable.
• RESOLVED_FLAG — indicates whether the status represents a resolved state of the defect.
• CUSTOMER_VIEWABLE_FLAG — controls whether the status is visible to external customers.
• BASE_DEFECT_REQUIRED_FLAG / DEFECT_LINK_TYPE_CODE / FIX_DETAILS_REQUIRED_FLAG — workflow/validation controls governing transitions and required fix information.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit and optimistic-locking columns.
• ATTRIBUTE1–15, CONTEXT — descriptive flexfield (DFF) segments and the DFF context value.

Common Use Cases and Queries

Typical use is lookup resolution and reporting on defect status configuration:

• Joining defect headers to this view to display the status name in a report or OAF/Forms page.
• Listing only statuses currently active within their effectivity range.
• Driving validation logic based on RESOLVED_FLAG or CUSTOMER_VIEWABLE_FLAG.

SELECT status_id, name, resolved_flag, customer_viewable_flag
FROM   css_def_statuses_vl
WHERE  SYSDATE BETWEEN NVL(start_date_active, SYSDATE)
                   AND NVL(end_date_active, SYSDATE + 1);

Because the object is documented as not implemented, queries should be preceded by a data-dictionary check (e.g., querying ALL_VIEWS for CSS_DEF_STATUSES_VL) before being embedded in production code. Where the view is unavailable, equivalent information is generally obtained from the successor defect-status lookup in the CRM/Service application.