Search Results abort_workflow_close_flag

Overview

CSS_DEF_PROB_CATEGORIES_VL is a bilingual (VL-suffixed) view within the Oracle E-Business Suite CSS – Support module. It presents problem category definitions maintained by the Support application, exposing both the descriptive, translated attributes (name and description) and the operational control attributes that govern how service requests assigned to a category are processed. The view follows the standard Oracle EBS MLS (Multi-Language Support) pattern, where a "_TL" translation table supplies language-dependent text and a "_B" base table supplies language-independent data.

In the context of Oracle EBS 12.1.1 and 12.2.2, this view is documented as belonging to CSS – Support (Obsolete). The ETRM metadata records that it is not implemented in the current database, and no referenced base objects are formally documented for the 12.2.2 release. This is consistent with the obsolescence designation: later releases of Oracle Service (the successor to CSS Support) moved category and workflow configuration into the Service Request management framework, and the legacy CSS_DEF_PROB_CATEGORIES tables were retired. Consequently, the view should be treated as a historical or legacy object rather than an active integration point in modern 12.2.2 environments.

Where the view does exist, its role is to provide a single, EBS-standard read interface over problem category definitions for reporting, lookups, and integration. The inclusion of the AUTOLAUNCH_WORKFLOW_FLAG column is directly relevant to the user's search, as that flag determines whether a workflow process is launched automatically when an incident is created in the associated category.

Underlying Base Objects

The view text is a join across two tables:

• CSS_DEF_PROB_CATEGORIES_B – the base table holding the language-independent definition of each problem category, including its workflow configuration and descriptive flexfield attributes.
• CSS_DEF_PROB_CATEGORIES_TL – the translation table holding the language-dependent NAME and DESCRIPTION for each category, keyed and filtered by language.

The join condition is B.PROBLEM_CATEGORY_ID = T.PROBLEM_CATEGORY_ID AND T.LANGUAGE = USERENV('LANG'), which restricts the result set to the rows in the session's current language. The _VL suffix therefore reflects the standard Oracle convention that the view supplies the "language" view of the entity. The B.ROWID is exposed as the ROW_ID column, providing a unique row identifier for the underlying base record.

Key Columns

• PROBLEM_CATEGORY_ID – Primary key linking the base and translation tables; uniquely identifies the category.
• ROW_ID – The ROWID of the base table row, exposed for uniqueness and locking purposes.
• NAME and DESCRIPTION – Language-specific text from the translation table, suitable for display and reporting.
• CATEGORY_TYPE – Classifies the category within the Support model.
• START_DATE_ACTIVE / END_DATE_ACTIVE – Effective dating range that determines when the category is valid.
• WORKFLOW – Identifies the workflow process associated with the category.
• AUTOLAUNCH_WORKFLOW_FLAG – When set, indicates the associated workflow should launch automatically on creation of an item in this category.
• ABORT_WORKFLOW_CLOSE_FLAG – Controls whether the workflow is aborted when the item is closed.
• OBJECT_VERSION_NUMBER – Optimistic locking version column, characteristic of the OA Framework-based 12.x data model.
• Audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) – Standard EBS WHO columns.
• ATTRIBUTE1–ATTRIBUTE15 and CONTEXT – Descriptive flexfield segments and context, allowing site-specific extensions.

Common Use Cases and Queries

A typical reporting query retrieves active categories and their workflow automation settings for the current language:

• SELECT PROBLEM_CATEGORY_ID, NAME, WORKFLOW, AUTOLAUNCH_WORKFLOW_FLAG FROM CSS_DEF_PROB_CATEGORIES_VL WHERE SYSDATE BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE + 1);
• Identifying categories that will trigger workflow automatically: SELECT NAME, WORKFLOW FROM CSS_DEF_PROB_CATEGORIES_VL WHERE AUTOLAUNCH_WORKFLOW_FLAG = 'Y';
• Looking up a specific category's workflow configuration by ID, joining to the ID for cross-reference in integration scripts.

Because the object is documented as obsolete and unimplemented, these queries apply only to environments where the underlying CSS_DEF_PROB_CATEGORIES_B/_TL tables remain present. New development should target the current Service Request framework APIs and views instead of relying on this legacy view.