Search Results action_notes
Overview
IGCBV_CC_ACTION_HISTORIES is a read-only view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the IGC (Contract Commitment) product family. The view presents the full action history recorded against contract commitments, exposing each workflow or approval action taken on a contract together with the contract header context it belongs to. Its designation as a "BV" (business view) object indicates that it is intended primarily for reporting, inquiry, and integration consumption rather than for transactional data entry.
The view is important because it flattens and humanizes data that would otherwise require joining transactional action records to lookup tables. Literal action type, state, control status, and approval status values are surfaced through embedded lookup translation annotations that resolve coded values to their display meanings. The view is defined with the WITH READ ONLY clause, so it cannot be used as the target of DML against the underlying tables.
Underlying Base Objects
The view is defined over two base objects:
- IGC_CC_ACTIONS (referenced through a synonym, aliased IGC_CCA) — the transactional action table that stores each action performed against a contract commitment, including its action type, state, control status, approval status, and free-text notes.
- IGC_CC_HEADERS (aliased IGC_CCH; documented in ETRM 12.2.2 metadata as IGC_CC_HEADERS_ALL, referenced through a synonym) — the contract commitment header table supplying the contract number, version number, and header identifier.
The two objects are joined on IGC_CCA.CC_HEADER_ID = IGC_CCH.CC_HEADER_ID, producing one row per action with the parent contract header information attached. Because the join is an equality-only inner join on a single column, an action row is returned only where a matching header exists, and no version-specific filtering is applied.
Key Columns
- ACTION_NUMBER — maps to
IGC_CCA.CC_ACTION_NUM, the identifier of the action record. This is the column most commonly sought when searching for "action_number." - "_LA:ACTION_TYPE" — translated meaning of the action type, resolved against the FND_LOOKUPS lookup type
IGC_CC_ACTION_TYPE. - "_LA:ACTION_STATE" — translated meaning of the action state, resolved against lookup type
IGC_CC_STATE. - "_LA:ACTION_CONTROL_STATUS" — translated meaning of the control status, resolved against lookup type
IGC_CC_CONTROL_STATUS. - "_LA:ACTION_APPROVAL_STATUS" — translated meaning of the approval status, resolved against lookup type
IGC_CC_APPROVAL_STATUS. - ACTION_NOTES — free-text notes recorded with the action.
- CONTRACT_COMMITMENT_NUMBER and CONTRACT_VERSION_NUMBER — the contract number and version from the header.
- CONTRACT_COMMITMENT_ID — the header identifier that links the action to its contract commitment.
- LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard audit columns, useful for tracking when an action was created or last modified and by which user.
Common Use Cases and Queries
Typical uses include auditing approval progression on a contract commitment, reporting on pending or rejected actions, and extracting action history for downstream integration. The following query lists all actions for a given contract commitment number:
SELECT action_number, "_LA:ACTION_TYPE", "_LA:ACTION_STATE", "_LA:ACTION_APPROVAL_STATUS", action_notes, last_update_date FROM apps.igcbv_cc_action_histories WHERE contract_commitment_number = :p_cc_num ORDER BY action_number;
To review all actions in a particular approval status across contracts:
SELECT contract_commitment_number, contract_version_number, action_number, "_LA:ACTION_APPROVAL_STATUS", "_LA:ACTION_STATE" FROM apps.igcbv_cc_action_histories WHERE "_LA:ACTION_APPROVAL_STATUS" = 'Rejected';
Because the view is read-only and directly joins the action and header tables, it is suitable for ad hoc inquiry and custom reports without risk of modifying transactional data. Note that the translated "_LA:" columns carry quoted mixed-case identifiers and must be referenced exactly as named.
-
View: IGCBV_CC_ACTION_HISTORIES
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:IGC.IGCBV_CC_ACTION_HISTORIES, object_name:IGCBV_CC_ACTION_HISTORIES, status:VALID, product: IGC - Contract Commitment , implementation_dba_data: APPS.IGCBV_CC_ACTION_HISTORIES ,
-
View: IGCFV_CC_ACTION_HISTORIES
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:IGC.IGCFV_CC_ACTION_HISTORIES, object_name:IGCFV_CC_ACTION_HISTORIES, status:VALID, product: IGC - Contract Commitment , implementation_dba_data: APPS.IGCFV_CC_ACTION_HISTORIES ,
-
View: IGCFV_CC_ACTION_HISTORIES
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:IGC.IGCFV_CC_ACTION_HISTORIES, object_name:IGCFV_CC_ACTION_HISTORIES, status:VALID, product: IGC - Contract Commitment , implementation_dba_data: APPS.IGCFV_CC_ACTION_HISTORIES ,
-
View: IGCBV_CC_ACTION_HISTORIES
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:IGC.IGCBV_CC_ACTION_HISTORIES, object_name:IGCBV_CC_ACTION_HISTORIES, status:VALID, product: IGC - Contract Commitment , implementation_dba_data: APPS.IGCBV_CC_ACTION_HISTORIES ,