Search Results cc_type_name




Overview
Explore in AI Chat

Overview

The IGC_CC_CONTROL_FUNCTIONS_V view is a reporting and inquiry object in the Oracle E-Business Suite (EBS) Contract Commitment (IGC) module. It is owned by the APPS schema and holds a VALID status in both 12.1.1 and 12.2.2. The view presents a denormalized, human-readable representation of the control functions defined for contract commitments. Whereas the underlying base table stores control function records using coded lookup values, this view resolves those codes into descriptive meanings by joining to the FND_LOOKUPS view. This design makes the view well suited for concurrent program extracts, Oracle Reports, OAF/Forms inquiry pages, and integration interfaces where descriptive text is preferred over internal codes.

The object exposes a derived CC_TYPE_NAME column—the field most frequently referenced when users search for cc_type_name. This column supplies the translated display name for the CC_TYPE code, allowing downstream consumers to present control function type without performing their own lookup translation.

Underlying Base Objects

According to the documented view text, IGC_CC_CONTROL_FUNCTIONS_V is defined over the base table IGC_CC_WF_CONTROL_FUNCTIONS (exposed in the metadata as the synonym IGC_CC_CONTROL_FUNCTIONS_ALL) joined to IGC_CC_WF_CONTROL_GROUPS (synonym IGC_CC_CONTROL_GROUPS), and twice to FND_LOOKUPS. The documented referenced base objects are FND_GLOBAL (package), FND_LOOKUPS (view), IGC_CC_CONTROL_FUNCTIONS_ALL (synonym), and IGC_CC_CONTROL_GROUPS (synonym).

The join conditions are: control function to control group on CONTROL_GROUP_ID; the first FND_LOOKUPS instance on LOOKUP_TYPE = 'IGC_CC_TYPE' matched to CC_TYPE; and the second FND_LOOKUPS instance on LOOKUP_TYPE = 'IGC_CC_STATE' matched to CC_STATE. ROWID from the control functions table is aliased as ROW_ID. The view is multilanguage-enabled, since FND_LOOKUPS returns meanings in the session language.

Key Columns

Common Use Cases and Queries

Typical usage includes control function inquiries, security/approval matrix reporting, and integration extracts that require descriptive type and state values.

SELECT control_function_id,
       cc_type,
       cc_type_name,
       cc_state,
       cc_state_name,
       control_group_name
  FROM apps.igc_cc_control_functions_v
 WHERE org_id = :p_org_id
   AND SYSDATE BETWEEN NVL(start_date, SYSDATE)
                   AND NVL(end_date, SYSDATE);

To filter by a specific commitment type name:

SELECT control_function_id, cc_type_name, cc_state_name
  FROM apps.igc_cc_control_functions_v
 WHERE cc_type_name = :p_type_name;

Because the view resolves lookups at query time, report and integration authors should treat CC_TYPE_NAME and CC_STATE_NAME as the display-ready fields and always filter or join on the coded columns where deterministic behavior is required.