Search Results base_defect_required_flag

Overview

CSS_DEF_PROB_TYPES_VL is a reporting and integration view within the Oracle E-Business Suite CSS (Support) module, a component historically associated with the CRM/TeleService problem-management and defect-tracking facilities. The view exposes the definition of problem types — the classification values used to categorize customer-reported issues, service requests, and defects during support operations. In EBS 12.1.1 and 12.2.2 the object is documented as belonging to the CSS – Support module and classified as obsolete, meaning it is retained for backward compatibility and reference but should not be relied upon for new development or customization. Its primary role is to present the translatable, user-facing attributes (problem type name and description) joined with the non-translatable, language-independent attributes of each problem type in a single rowset, which makes it convenient for concurrent programs, reports, and integration extracts that require a denormalized, locale-aware view of the problem type list.

Underlying Base Objects

The view text shows that it is defined over two base tables:

• CSS_DEF_PROB_TYPES_B — the primary (base) table storing the language-independent columns of each problem type record.
• CSS_DEF_PROB_TYPES_TL — the translation table storing the language-dependent NAME and DESCRIPTION columns.

The join is performed on PROBLEM_TYPE_ID, with the translation side additionally constrained by T.LANGUAGE = USERENV('LANG'), so that only the rows matching the session's current language are returned. This is the standard Oracle EBS "_B / _TL" pattern used throughout the applications to support multi-language deployments. View metadata records no separate referenced base objects beyond the two tables implied by the query text, and the object is documented as not implemented in the reference database, confirming its obsolete status.

Key Columns

• ROW_ID — the row identifier of the base table record, exposed from B.ROWID.
• PROBLEM_TYPE_ID — the unique identifier and primary key of the problem type; the join key between the base and translation tables.
• PROBLEM_CATEGORY_ID — foreign reference to the parent problem category to which the type is assigned.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the framework to detect concurrent updates.
• START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date range controlling whether the problem type is currently active.
• BASE_DEFECT_REQUIRED_FLAG — indicates whether a base defect reference is mandatory when the type is used.
• SORT_ORDER — display sequence used when listing problem types.
• NAME / DESCRIPTION — the translated, user-facing label and long description sourced from the _TL table.
• ATTRIBUTE1–ATTRIBUTE15, CONTEXT — the standard EBS descriptive flexfield columns.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns.

Common Use Cases and Queries

Because the view already resolves the language join, it is typically queried directly to retrieve the list of problem types in the session's language for reporting, validation, or data migration. A representative query retrieving all active types is:

SELECT problem_type_id, name, description, problem_category_id, sort_order
FROM   css_def_prob_types_vl
WHERE  TRUNC(SYSDATE) BETWEEN NVL(start_date_active, TRUNC(SYSDATE))
                          AND NVL(end_date_active, TRUNC(SYSDATE))
ORDER BY sort_order, name;

Typical uses include populating LOV-style reference lists, extracting problem type definitions for integration with external helpdesk or defect-tracking systems, joining to problem or service request transaction tables for reporting by type, and validating category-to-type hierarchies. Given the object's obsolete classification, any new development in EBS 12.1.1 or 12.2.2 should confirm the current supported replacement object before depending on this view, and existing usages should be reviewed during upgrades.