Search Results action_enabled

Overview

APPS.CSC_CONDITION_HEADERS_V is a reporting and integration view in Oracle E-Business Suite (12.1.1 / 12.2.2) that exposes condition header definitions scoped to the Service Fulfillment / Service Contract (CSC) plan header context. It is an APPS-owned, read-only database object built entirely over other views rather than base tables, so it carries no independent storage and inherits its data directly from its parents at query time. Its defining characteristic is the filter och.jtot_object_code = 'CSC_PLAN_HEADER', which restricts output to condition headers associated with the CSC plan header object, joining each row to its corresponding action definition. The view therefore acts as a purpose-built projection layer for consumers that need condition metadata already joined to action attributes (name, description, type, counter-action flag, enabled flag) without having to perform the underlying multi-object join themselves. For ETRM (E-Business Tax / Trade Management adjacent) and service contract reporting, this simplifies queries against rule and condition setups, and makes the object suitable for concurrent program extracts, BI Publisher data models, and inbound/outbound integration interfaces that require condition-to-action resolution.

Underlying Base Objects

The view is defined exclusively over two documented view objects:

• OKC_CONDITION_HEADERS_V (alias OCH) — supplies the condition header attributes, including the primary key ID, action reference (ACN_ID), the object identifier, descriptive fields, validity and type flags, and the JTOT_OBJECT_CODE that drives the CSC filter.
• OKC_ACTIONS_V (alias OA) — supplies action metadata joined in on OCH.ACN_ID = OA.ID.

Because both parents are views, CSC_CONDITION_HEADERS_V is a nested view with no direct dependency on base tables; the dependency chain is resolved by the respective OKC view definitions. This has two consequences: query performance depends on the underlying OKC view SQL and any function-based logic within them, and any change to the OKC views propagates transparently to this object. The join is an inner join on ACN_ID, so a condition header without a matching action row is excluded from the result set.

Key Columns

• CONDITION_HEADER_ID — renaming of OCH.ID; the surrogate primary key for the condition header, and the column most frequently searched by users.
• ACTION_ID — the action reference (ACN_ID), linking the condition header to its action record.
• OBJECT_ID — identity of the owning object (the CSC plan header instance).
• CONDITION_NAME, DESCRIPTION, SHORT_DESCRIPTION, COMMENTS — descriptive attributes of the condition.
• CONDITION_VALID_YN, ONE_TIME_YN, TEMPLATE_YN — validity, single-use, and template flags.
• BEFORE_AFTER — indicates whether the condition is evaluated before or after the associated action.
• DATE_ACTIVE, DATE_INACTIVE — effective dating window for the condition.
• CONDITION_HEADER_TYPE — the condition header classification (CNH_TYPE).
• SFWT_FLAG — a source/setup flag carried from the condition header view.
• ACTION_NAME, ACTION_DESCRIPTION, ACTION_TYPE, COUNTER_ACTION_YN, ACTION_ENABLED — denormalized action attributes joined from OKC_ACTIONS_V.

Common Use Cases and Queries

Typical scenarios include listing all active conditions for CSC plan headers, identifying which actions are referenced by conditions, auditing before/after sequencing, and feeding integration extracts. A parameterized lookup by the searched key is common:

• SELECT condition_header_id, condition_name, action_id, action_name, action_type, before_after, date_active, date_inactive FROM apps.csc_condition_headers_v WHERE condition_header_id = :p_id;

• SELECT condition_header_id, condition_name, action_name, action_enabled, action_type FROM apps.csc_condition_headers_v WHERE condition_valid_yn = 'Y' AND action_enabled = 'Y' ORDER BY condition_name;

• SELECT object_id, COUNT(*) FROM apps.csc_condition_headers_v WHERE template_yn = 'N' GROUP BY object_id;

Because the view is already restricted to JTOT_OBJECT_CODE = 'CSC_PLAN_HEADER', consumers do not need to repeat that predicate, and should avoid adding redundant filters on the underlying OKC columns.