Search Results igc_cc_routing_ctrls




Overview
Explore in AI Chat

Overview

IGC_CC_ROUTING_CONTROLS — documented under the object name IGC_CC_ROUTING_CTRLS — is a configuration table within the Oracle E-Business Suite IGC – Contract Commitment product family. Its documented purpose is to hold routing controls for contract types. In practical terms, the table defines, per operating unit and per contract type, which workflow routing state or processing state a contract commitment must occupy for a given routing control to apply. It therefore acts as a control-and-configuration reference that governs how contract commitments of a particular CC_TYPE are routed through their approval and processing lifecycle, as identified by CC_STATE.

The metadata records that the object is Not implemented in this database. This indicates that the table is defined in the Oracle EBS data model and shipped with the product, but is not physically instantiated in the environment from which the documentation was extracted. Analysts should confirm existence via ALL_TABLES before depending on it in custom code or reports.

Under the heuristic Data Vault classification mined from the foreign-key structure, the object is identified as standalone. In Data Vault modeling terms, this suggests treating IGC_CC_ROUTING_CTRLS as a self-contained reference or lookup structure rather than as a hub or link. Its three-part primary key supports this interpretation: it is a composite key table whose rows are configuration records rather than transaction facts. A modeling suggestion would be to represent it as a reference satellite keyed on its natural composite business key, with no inferred parent hub relationships.

Key Information Stored

The documented columns of IGC_CC_ROUTING_CTRLS are limited and precisely specified in the metadata. The principal columns are:

  • ORG_ID — The operating unit identifier. This is the multi-organization discriminator that scopes every routing control row to a specific operating unit. It is a business-key component.
  • CC_TYPE — The contract commitment type. This is the business classification of the commitment to which the routing control applies. It is a business-key component.
  • CC_STATE — The contract commitment state. This identifies the workflow or processing state being controlled. It is a business-key component.
  • IGC_CCRC_PK — The documented primary key constraint, defined over the column combination (ORG_ID, CC_TYPE, CC_STATE).

Notably, the primary key is a composite business key rather than a system-generated surrogate. No separate single-column surrogate identifier is documented for this table. The uniqueness of a routing control is therefore guaranteed by the natural combination of operating unit, contract type, and contract state: at most one routing control configuration may exist for a given ORG_ID / CC_TYPE / CC_STATE triple. No additional unique indexes beyond the primary key are documented in the available metadata. Because the object is marked as not implemented, no row-level data contents are available for inspection.

Common Use Cases and Queries

The primary use case for IGC_CC_ROUTING_CTRLS is to determine the routing or processing control applicable to a contract commitment based on its type and current state. Typical access patterns filter on all three business-key columns, since the primary key is composite.

A representative query pattern, restricted to the documented columns, is:

  • SELECT org_id, cc_type, cc_state FROM igc_cc_routing_ctrls WHERE org_id = :p_org_id AND cc_type = :p_cc_type;
  • SELECT org_id, cc_type, cc_state FROM igc_cc_routing_ctrls WHERE org_id = :p_org_id AND cc_type = :p_cc_type AND cc_state = :p_cc_state;

Reporting scenarios include enumerating all contract types and states configured for routing controls within an operating unit, and validating configuration completeness by comparing the distinct combinations of type and state present in routing controls against those defined in contract type and contract state reference tables. In contract commitment processing, such a lookup determines whether a commitment in a given state is subject to a configured routing control before it advances.

Related Objects

The available metadata describes FKs at a high level and classifies the object as standalone; it does not enumerate specific referenced or referencing tables with named join columns. Consequently, related objects are identified by the business-key columns rather than by explicit foreign-key relationships.

  • ORG_ID joins the operating unit organization definition, commonly accessed through the organization classification views associated with the IGC product's MOAC (multi-organization access control) filtering.
  • CC_TYPE relates to the contract type reference used elsewhere in the IGC – Contract Commitment module, where a given CC_TYPE categorizes commitments.
  • CC_STATE corresponds to the contract commitment state or workflow status referenced by the core contract commitment tables in IGC.
  • Core contract commitment tables in IGC (for example, the contract commitment header and line entities) are the principal consumers of the routing controls, resolving configuration by ORG_ID, CC_TYPE, and CC_STATE.
  • Workflow and routing definitions used by the commitment approval process operate in conjunction with these controls.

Because concrete FK join columns are not documented beyond the primary key, integrators should derive actual relationships from the IGC data model dictionary in the target environment. The single most reliable join key set is the composite (ORG_ID, CC_TYPE, CC_STATE).