Search Results igcfv_cc_contract_commitments

Overview

IGCFV_CC_CONTRACT_COMMITMENTS is an APPS-owned reporting view in the Oracle E-Business Suite IGC (Contract Commitment) module. It presents a denormalized, human-readable projection of contract commitment header data, joining the core commitment records in IGC_CC_HEADERS with the descriptive attributes that users expect to see on a commitment summary screen or report: vendor details, payment terms, ledger, currency, conversion type, operating unit, and owning/preparer users. Rather than forcing report authors and integrators to join a dozen base objects manually, the view assembles them into a single flat structure keyed on the contract commitment header.

The view is significant because it is the primary public surface for contract commitment reporting in IGC. It exposes translated lookups (approval status, control status, encumbrance status, state, and type) indirectly, and it carries a dual maintenance of surrogate keys and descriptive columns, allowing consumers to filter by ID (TERM_ID, VENDOR_ID, ORG_ID) while displaying labels such as TERMS_NAME, VENDOR_NAME, and ORGANIZATION_NAME. The user search term "terms_name" maps directly to the AP_TERMS_TL.NAME column surfaced by this view, reflecting the common need to report commitments alongside their negotiated payment terms.

Underlying Base Objects

The view text is anchored on IGC_CC_HEADERS (aliased IGC_CCH, referenced in the documented metadata as IGC_CC_HEADERS_ALL). The documented referenced base objects are:

• AP_TERMS_TL (SYNONYM) — payment terms translated name, surfaced as TERMS_NAME.
• FND_CURRENCIES (SYNONYM) — currency validation, related to the CURRENCY_CODE column.
• FND_GLOBAL (PACKAGE) — session/context resolution, including org context.
• FND_USER (SYNONYM) — resolved user names for owner and preparer.
• GL_DAILY_CONVERSION_TYPES (SYNONYM) — currency conversion type, surfaced as CONVERSION_USER_TYPES.
• GL_SETS_OF_BOOKS_11I (SYNONYM) — ledger name and short name (SETS_OF_BOOKS_NAME, SETS_OF_BOOKS_SHORT_NAME).
• HR_ALL_ORGANIZATION_UNITS (SYNONYM) — operating unit/org name, surfaced as ORGANIZATION_NAME.
• HR_LOCATIONS_ALL (SYNONYM) — location code, surfaced as LOCATION_CODE.
• PO_VENDORS (VIEW) — supplier name and number.
• PO_VENDOR_CONTACTS (VIEW) — vendor contact first and last name.
• PO_VENDOR_SITES_ALL (VIEW) — supplier site code.

In effect, the view consolidates supplier master data (PO_VENDORS family), financial setup (ledger, currency, conversion type), HR organization and location data, and the IGC commitment header into one row per commitment version.

Key Columns

The view exposes both descriptive labels and their backing identifiers. Important columns include:

• CONTRACT_COMMITMENT_NUMBER, CONTRACT_VERSION_NUMBER — the human-readable commitment identifier and version (from IGC_CCH.CC_NUM, CC_VERSION_NUM).
• CONTRACT_COMMITMENT_ID — the surrogate key (IGC_CCH.CC_HEADER_ID), used for joins back to base tables.
• TERMS_NAME — the translated payment terms name from AP_TERMS_TL, driven by TERM_ID. This is the column targeted by the "terms_name" search.
• DESCRIPTION, START_EFFECTIVE_DATE, END_EFFECTIVE_DATE — commitment description and effective date range.
• VENDOR_NAME, VENDORS_NUMBER, VENDOR_SITES_CODE, VENDOR_CONTACTS_LAST_NAME, VENDOR_CONTACTS_FIRST_NAME — supplier identity and contact details.
• ORGANIZATION_NAME, ORGANIZATION_ID, LOCATION_CODE, LOCATION_ID — operating unit and location context.
• SETS_OF_BOOKS_NAME, SETS_OF_BOOKS_SHORT_NAME, SET_OF_BOOKS_ID — ledger identification.
• CURRENCY_CODE, CONVERSION_TYPE, CONVERSION_USER_TYPES — currency and conversion setup.
• USER_NAME, OWNER_USER_ID, PREPARER_USER_ID — owning and preparer responsibility.
• Approval, control, encumbrance, state, and type lookup labels (exposed through the embedded _LA token columns) along with their underlying status codes.
• Standard audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE.

Common Use Cases and Queries

Typical uses include commitment reporting by supplier, listing commitments for a ledger and currency, and resolving commitments to their payment terms. A representative query searching on the terms name is:

• SELECT contract_commitment_number, terms_name, vendor_name, currency_code FROM igcfv_cc_contract_commitments WHERE terms_name = :p_terms_name;
• SELECT contract_commitment_number, terms_name, vendor_name, sets_of_books_short_name FROM igcfv_cc_contract_commitments WHERE organization_id = :p_org_id AND vendor_id = :p_vendor_id;
• SELECT contract_commitment_number, terms_name, start_effective_date, end_effective_date FROM igcfv_cc_contract_commitments WHERE start_effective_date >= :p_from_date;

Because the view already resolves translated names, it is well suited to BI Publisher reports, ad hoc discoverer queries, and integration extracts where commitment data must be presented without further lookup joins.