Search Results cc_action_ctrl_status_desc

Overview

IGC_CC_ACTIONS_V is an APPS-owned database view in Oracle E-Business Suite Release 12.1.1 and 12.2.2, belonging to the IGC (Contract Commitment) product family. Contract Commitment functionality in EBS supports the creation, tracking, approval, and control of commitments against contracts, and is closely associated with the Oracle Procurement Contracts and Public Sector Financials contracting flows. The view exposes one row per recorded contract commitment action — that is, per discrete workflow or lifecycle event applied to a contract commitment header, such as submission, approval, rejection, or cancellation — and it enriches the raw transactional record with decoded lookup meanings and the identity of the creating user.

Its principal role is read-only reporting and integration. Because it joins the transactional action table to FND_LOOKUPS and FND_USER, consumers do not need to re-implement lookup decoding or user resolution, which makes the view a convenient source for concurrent programs, custom reports, OAF or Forms-based inquiry screens, and outbound interfaces that need human-readable action status information. The view is documented as VALID in the ETRM object registry, confirming it is compiled and available in the APPS schema.

Underlying Base Objects

The view is defined over a single factual base object, IGC_CC_ACTIONS (referenced in the APPS schema via synonym), aliased CCA. This table stores the contract commitment action records themselves, including the surrogate key columns, action type and state codes, control and approval status codes, free-text notes, and standard WHO audit columns.

Four additional objects are joined to supply descriptive context:

• FND_LOOKUPS (view), joined four times (LKP1–LKP4) using outer joins, to translate the codes held in IGC_CC_ACTIONS into their display meanings for the lookup types IGC_CC_ACTION_TYPE, IGC_CC_STATE, IGC_CC_CONTROL_STATUS, and IGC_CC_APPROVAL_STATUS.
• FND_USER (synonym), joined on FNDU.USER_ID = CCA.CREATED_BY, to resolve the creating user's application login name.
• FND_GLOBAL (package), referenced as the standard EBS context mechanism available to the underlying objects rather than as a direct join target.

Because the lookup joins are outer joins, action rows whose codes are not yet defined in FND_LOOKUPS still appear, with null description columns. The join to FND_USER, however, is an inner join, so rows are only returned where a matching user record exists.

Key Columns

The view exposes the identity, classification, status, and audit attributes of each commitment action:

• ROW_ID — the rowid of the underlying IGC_CC_ACTIONS row, useful as a unique handle for updates or drill-down.
• CC_HEADER_ID — foreign key to the contract commitment header to which the action belongs; the primary grouping column for per-commitment history.
• CC_ACTION_NUM and CC_ACTION_VERSION_NUM — the action sequence number and its version, supporting versioned action history.
• CC_ACTION_TYPE / CC_ACTION_TYPE_DESC — the coded action type and its decoded meaning.
• CC_ACTION_STATE / CC_ACTION_STATE_DESC — the workflow or lifecycle state of the action and its decoded meaning.
• CC_ACTION_CTRL_STATUS / CC_ACTION_CTRL_STATUS_DESC — the control status (for example, whether the action passed commitment control validation) and its decoded meaning.
• CC_ACTION_APPRVL_STATUS / CC_ACTION_APPRVL_STATUS_DESC — the approval status and its decoded meaning.
• CC_ACTION_NOTES — free-text notes attached to the action.
• WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and CREATED_BY_NAME (the resolved FND_USER.USER_NAME).

Common Use Cases and Queries

Typical uses include auditing the approval and control history of a commitment, building inquiry pages that show decoded statuses, and feeding external systems that require readable action descriptions rather than codes.

Retrieve the full action history for a specific commitment header:

• SELECT cc_action_num, cc_action_type_desc, cc_action_state_desc, cc_action_ctrl_status_desc, cc_action_apprvl_status_desc, created_by_name, creation_date FROM igc_cc_actions_v WHERE cc_header_id = :p_header_id ORDER BY cc_action_num, cc_action_version_num;

List all pending or rejected approvals within a date range:

• SELECT cc_header_id, cc_action_num, cc_action_apprvl_status_desc, cc_action_notes, created_by_name FROM igc_cc_actions_v WHERE creation_date BETWEEN :p_from AND :p_to AND cc_action_apprvl_status_desc IN ('PENDING','REJECTED') ORDER BY creation_date DESC;

Identify actions lacking a valid lookup definition, which surfaces configuration gaps in the IGC lookup set:

• SELECT cc_header_id, cc_action_num, cc_action_type, cc_action_state FROM igc_cc_actions_v WHERE cc_action_type_desc IS NULL OR cc_action_state_desc IS NULL;

Because the view performs no aggregation and applies no row-level security beyond that inherited from its base objects, report authors should apply their own operating unit or business group predicates where the underlying commitment data is partitioned.