Search Results igc_cc_routing_ctrls_v




Overview
Explore in AI Chat

Overview

The IGC_CC_ROUTING_CTRLS_V view is a reporting and integration object owned by the APPS schema within the Oracle E-Business Suite IGC (Contract Commitment) product family. It exposes the routing control configuration that governs how Contract Commitment records are routed through Oracle Workflow for approval and encumbrance processing. The view presents the underlying routing control rows in a denormalized, user-readable form by resolving the coded values CC_TYPE and CC_STATE into their descriptive meanings through joins to the FND_LOOKUPS view. This makes it suitable for reports, concurrent programs, Oracle Discoverer worksheets, and custom integrations that must display routing rules with human-readable labels rather than raw lookup codes. In EBS 12.1.1 and 12.2.2, the view is documented as VALID and is commonly referenced when administrators need to inspect, audit, or troubleshoot the approval-path configuration assigned to each combination of commitment type and commitment state within an operating unit. The presence of the DEFAULT_APPROVAL_PATH_ID column makes the view particularly relevant to searches concerning default approval path assignment, since it reveals the Workflow approval path that is applied when no overriding routing rule exists.

Underlying Base Objects

The view is defined over three documented base objects. The primary object is IGC_CC_ROUTING_CTRLS, referenced as a SYNONYM that points to the underlying routing control table holding the transactional configuration rows. Two joins are made to FND_LOOKUPS, once for the IGC_CC_TYPE lookup type and once for the IGC_CC_STATE lookup type, to translate the stored codes into meanings. The documented referenced objects also include the FND_GLOBAL package, which supplies session context such as ORG_ID and user identity used to filter and attribute rows. The view text selects ICRC.ROWID together with the configuration columns and joins FND_LOOKUPS as F1 on LOOKUP_TYPE = 'IGC_CC_TYPE' and as F2 on LOOKUP_TYPE = 'IGC_CC_STATE'. Because FND_LOOKUPS is itself a view over the lookup tables, the routing control view remains read-only and inherits any organization or language security applied at those lower levels.

Key Columns

Common Use Cases and Queries

Typical scenarios include validating which approval path is defaulted for a commitment type and state, auditing routing rules per operating unit, and feeding integration extracts. A representative query is:

SELECT cc_type_name, cc_state_name, wf_approval_itemtype, wf_approval_process, default_approval_path_id FROM apps.igc_cc_routing_ctrls_v WHERE org_id = :p_org_id ORDER BY cc_type_name, cc_state_name;

To isolate records with a default approval path configured:
SELECT org_id, cc_type_name, cc_state_name, default_approval_path_id FROM apps.igc_cc_routing_ctrls_v WHERE default_approval_path_id IS NOT NULL;

Because the view is read-only, modifications must be performed against the base IGC_CC_ROUTING_CTRLS table through the supported IGC setup forms or APIs, not through this view.