Search Results autolaunch_workflow_flag
Overview
CS_SR_TYPES_SELECT_SEC is a Service (CS) module view in Oracle E-Business Suite 12.1.1 and 12.2.2 that exposes the definition of service request types and subtypes. The view is defined over the CS_INCIDENT_TYPES_B base table and presents a security-oriented projection of incident type configuration, including workflow routing attributes, web channel flags, and descriptive flexfield context columns. In the ETRM metadata for 12.2.2 the object is recorded with no documented dependent base objects, and its description notes that the view is "not implemented in this database" in the captured environment — meaning it is a seeded dictionary object whose presence and population depend on whether Service request types have been configured.
Because service request types drive incident classification, workflow selection, and self-service portal behaviour, the view functions as a reporting surface for administrators, implementers, and integration developers who need a read-only, queryable representation of request type configuration without joining directly to the transactional base table.
Underlying Base Objects
The view is defined over a single base object, CS_INCIDENT_TYPES_B. The SELECT list projects nearly every column from that table's business-layer record, including audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER), effective-dating columns (START_DATE_ACTIVE, END_DATE_ACTIVE), and the extensive set of workflow and channel attributes. Column aliases follow the base table names; for example B.WEB_WORKFLOW and B.WEB_ENTRY_FLAG pass through unchanged. The user's search term "web_workflow" resolves directly to the WEB_WORKFLOW column exposed here. The accompanying column list also references ROW_ID, NAME, and DESCRIPTION, which are characteristic of the table's primary key and descriptive translation structures.
Key Columns
- INCIDENT_TYPE_ID / INCIDENT_SUBTYPE — the primary business key identifying a request type or subtype.
- PARENT_INCIDENT_TYPE_ID — links a subtype to its parent incident type, enabling hierarchical classification.
- WORKFLOW — the workflow process launched when a service request of this type is created.
- WEB_ENTRY_FLAG / WEB_WORKFLOW — control whether the type is available through web/self-service entry and which workflow runs for web-originated requests; directly relevant to the "web_workflow" search.
- WEB_IMAGE_FILENAME / IMAGE_FILE_NAME — images associated with the type in the service portal.
- TASK_WORKFLOW — workflow used for tasks linked to the request type.
- BUSINESS_PROCESS_ID — associated business process definition.
- STATUS_GROUP_ID — status group governing transitions for requests of this type.
- ABORT_WORKFLOW_CLOSE_FLAG / AUTOLAUNCH_WORKFLOW_FLAG — workflow lifecycle control flags.
- SEEDED_FLAG — distinguishes Oracle-seeded rows from customer-defined rows.
- MAINTENANCE_FLAG / CMRO_FLAG / ACTIVE_ITEM_RELATIONSHIP / DETAILED_ERECORD_REQ_FLAG — functional behaviour indicators.
- CONTEXT and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield context and segment values.
Common Use Cases and Queries
Typical uses include auditing workflow configuration for web-enabled request types, validating flexfield usage, and feeding integration or migration routines. A representative query lists active web workflow types:
- SELECT INCIDENT_TYPE_ID, INCIDENT_SUBTYPE, WORKFLOW, WEB_WORKFLOW FROM CS_SR_TYPES_SELECT_SEC WHERE WEB_ENTRY_FLAG = 'Y' AND SYSDATE BETWEEN START_DATE_ACTIVE AND END_DATE_ACTIVE;
- Join to CS_INCIDENT_TYPES_TL on INCIDENT_TYPE_ID for the NAME/DESCRIPTION translation when reporting in a specific language.
Because the view is read-only and mirrors the base table structure, it is safe for ad-hoc reporting and secured query exposure without risk of mutating configuration.
-
View: CS_SR_TYPES_SELECT_SEC
12.2.2
product: CS - Service , implementation_dba_data: Not implemented in this database ,
-
View: CS_INCIDENT_TYPES_VL
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:CS.CS_INCIDENT_TYPES_VL, object_name:CS_INCIDENT_TYPES_VL, status:VALID, product: CS - Service , description: Multi-lingual view for CS_INCIDENT_TYPES_B and CS_INCIDENT_TYPES_TL tables. , implementation_dba_data: APPS.CS_INCIDENT_TYPES_VL ,
-
View: CS_INCIDENT_TYPES_VL
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:CS.CS_INCIDENT_TYPES_VL, object_name:CS_INCIDENT_TYPES_VL, status:VALID, product: CS - Service , description: Multi-lingual view for CS_INCIDENT_TYPES_B and CS_INCIDENT_TYPES_TL tables. , implementation_dba_data: APPS.CS_INCIDENT_TYPES_VL ,
-
View: CS_INCIDENT_TYPES_VL_SEC
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:CS.CS_INCIDENT_TYPES_VL_SEC FND.CS_INCIDENT_TYPES_VL_SEC, object_name:CS_INCIDENT_TYPES_VL_SEC, status:VALID, product: CS - Service , description: Multi-lingual Secured view based onr CS_INCIDENT_TYPES_B_SEC_V view and CS_INCIDENT_TYPES_TL table. , implementation_dba_data: APPS.CS_INCIDENT_TYPES_VL_SEC ,
-
View: CS_SR_TYPES_SELECT_SEC
12.1.1
product: CS - Service , implementation_dba_data: Not implemented in this database ,
-
View: CS_INCIDENT_TYPES_VL_SEC
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:CS.CS_INCIDENT_TYPES_VL_SEC FND.CS_INCIDENT_TYPES_VL_SEC, object_name:CS_INCIDENT_TYPES_VL_SEC, status:VALID, product: CS - Service , description: Multi-lingual Secured view based onr CS_INCIDENT_TYPES_B_SEC_V view and CS_INCIDENT_TYPES_TL table. , implementation_dba_data: APPS.CS_INCIDENT_TYPES_VL_SEC ,