Results for “template_yn”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

In Oracle E-Business Suite 12.1.1 and 12.2.2, CSC_CONDITION_HEADERS_V is an APPS-owned, VALID database view within the CSC (Customer Care) product family. It exposes the conditions that drive the Service Fulfillment Workflow (SFW) engine, specifically the condition headers evaluated when an Action fires. Each row defines a Condition to be evaluated upon the occurrence of an Action, and is restricted to the Customer Care Service Plan Header object context.

The view is a key integration and reporting surface for the Condition/Action engine. Rather than querying the underlying OKC objects directly, implementers, form personalizations, and downstream integrations query this view to retrieve a condition's name, validity state, timing relative to the action, and its parent action metadata. The column CONDITION_NAME (aliased from OCH.NAME) is the descriptive label users typically search for.

Underlying Base Objects

The view is defined over two documented base objects:

• OKC_CONDITION_HEADERS_V (VIEW) — supplies the condition header itself. Its columns are projected into the outer view with renames or direct aliases.
• OKC_ACTIONS_V (VIEW) — supplies the associated Action metadata, joined on OCH.ACN_ID = OA.ID.

Critically, the WHERE clause applies the constant filter OCH.JTOT_OBJECT_CODE = 'CSC_PLAN_HEADER'. This scopes the view exclusively to Customer Care Service Plan Header conditions, binding the generic OKC condition framework to the CSC application. Because both sources are views, no physical table can be traced directly through this object; performance depends on the underlying OKC base tables beneath those views.

Key Columns

• CONDITION_HEADER_ID — Primary identifier, aliased from OCH.ID.
• CONDITION_NAME — Business-facing name of the condition (from OCH.NAME); the primary search attribute.
• CONDITION_VALID_YN and ACTION_ENABLED — Validity and enabled flags indicating whether the condition and its action will be evaluated at runtime.
• BEFORE_AFTER — Indicates whether the condition is evaluated before or after the action executes.
• ACTION_ID, ACTION_NAME, ACTION_DESCRIPTION, ACTION_TYPE — Parent Action context joined from OKC_ACTIONS_V.
• COUNTER_ACTION_YN — Flag identifying the action as a counter-action.
• ONE_TIME_YN, TEMPLATE_YN, SFWT_FLAG — Behavioral qualifiers for the condition.
• DATE_ACTIVE, DATE_INACTIVE — Effective dating window for the condition.
• OBJECT_ID and CONDITION_HEADER_TYPE — Object linkage and classification.

Common Use Cases and Queries

Typical scenarios include auditing which conditions attach to a given action, verifying which conditions are currently active and valid, and embedding the view in SFW diagnostics. A representative query listing active conditions with their action names is:

• SELECT condition_name, action_name, action_type, before_after, condition_valid_yn, action_enabled, date_active, date_inactive FROM csc_condition_headers_v WHERE condition_valid_yn = 'Y' AND action_enabled = 'Y' ORDER BY action_name, condition_name;
• SELECT condition_header_id, condition_name, one_time_yn FROM csc_condition_headers_v WHERE action_id = :action_id;
• SELECT condition_name FROM csc_condition_headers_v WHERE UPPER(condition_name) LIKE UPPER('%' || :condition_name || '%');

Because the view is restricted to the CSC_PLAN_HEADER object code, results are limited to Customer Care Service Plan conditions; conditions defined against other JTOT object codes are excluded. All queries should be executed against the APPS schema or a synonym with appropriate privileges.