Results for “igc_cc_encumbrance_status”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.IGC_CC_HEADERS_V is the descriptive (denormalized) view over the Commitment Control header entity in Oracle E-Business Suite. The underlying transactional table is IGC_CC_HEADERS (exposed through the IGC_CC_HEADERS_ALL synonym), and the view is created by joining that table to a series of lookup views, supplier master views, HR person and location views, and FND user tables. Its purpose is to present a human-readable, fully resolved image of a commitment control document — including decoded lookup meanings, supplier names, preparer and owner identities, access levels, and workflow attributes — without requiring the caller to perform dozens of manual joins.

The view is central to the ETRM (Enterprise Transaction & Records Management) commitment control feature set. It supports both reporting and integration: Oracle Forms and OAF pages built for the Commitment Control module query this view directly, and external systems integrating via PL/SQL or published interfaces frequently select from it to obtain the current state of a commitment header in a single pass. Because it resolves FND_LOOKUPS codes into their MEANING values, it is particularly valuable for outbound extracts destined for data warehouses or downstream reconciliation engines.

Underlying Base Objects

The view is defined over IGC_CC_HEADERS with outer joins to five aliases of FND_LOOKUPS (l, sl, asl, csl, el), which supply decoded meanings for cc_type, cc_state, cc_apprvl_status, cc_ctrl_status, and cc_encmbrnc_status respectively. Supplier data is sourced from PO_VENDORS, PO_VENDOR_SITES_ALL, and PO_VENDOR_CONTACTS (through po_vendor_contacts so that the last name and first name can be concatenated).

Identity resolution is performed by joining FND_USER and PER_PEOPLE_F for the preparer, owner, and current user, including employee_id derived from fndu, ofndu, and cfndu. Additional contextual objects include AP_TERMS for payment term names, HR_LOCATIONS for location codes, and GL_SETS_OF_BOOKS for the accounting book. A self-join against IGC_CC_HEADERS_ALL (pcchd) retrieves the parent commitment number. The view also invokes three packages: IGC_CC_ACCESS_PKG (to compute access level via get_access_level), FND_GLOBAL (for USER_ID), and HR_SECURITY/HR_GENERAL/HR_PERSON_NAME as supporting dependencies for HR-based security and name formatting. This dependency on FND_GLOBAL.USER_ID means query results are inherently user-context sensitive.

Key Columns

• cc_header_id — primary key and the join key used by downstream detail views.
• cc_num, cc_ref_num, cc_version_num — document number, external reference, and version.
• cc_type, cc_state, cc_apprvl_status, cc_ctrl_status — raw codes, each accompanied by a decoded MEANING column from FND_LOOKUPS.
• cc_encmbrnc_status — the encumbrance status code; the decoded meaning appears via the el lookup alias. Users searching for igc_cc_encumbrance_status are typically locating this column or its lookup type.
• vendor_id, vendor_name, segment1, vendor_site_id, vendor_site_code, vendor_contact_id — supplier identity and site, with contact name concatenated from last and first name.
• cc_preparer_user_id, cc_owner_user_id, cc_current_user_id — user identifiers, each paired with user_name, full_name, and employee_id.
• cc_acct_date, cc_start_date, cc_end_date — accounting and effective date range.
• conversion_type, conversion_date, conversion_rate — currency conversion metadata; currency_code and set_of_books_id define the ledger context.
• term_id, location_id, cc_desc, parent_header_id — descriptive and hierarchical attributes.
• wf_item_type, wf_item_key — workflow linkage for the approval process.
• attribute1 … attribute15 — the standard DFF columns plus context.
• cc_guarantee_flag — guarantee indicator; hold_flag from the vendor record.

Common Use Cases and Queries

Typical usage includes commitment control status reporting, approval workflow monitoring, and encumbrance reconciliation. A basic listing retrieves the current state and decoded status for a set of headers:

SELECT cc_num, cc_type, meaning AS cc_type_meaning, cc_state, cc_encmbrnc_status FROM apps.igc_cc_headers_v WHERE org_id = :p_org_id AND cc_state = 'ACTIVE';

To isolate documents by encumbrance condition, filter on the decoded meaning rather than the raw code:

SELECT cc_num, vendor_name, cc_encmbrnc_status FROM apps.igc_cc_headers_v WHERE UPPER(cc_encmbrnc_status) LIKE '%ENCUMB%';

For approver workload analysis, the preparer/owner columns are combined with workflow identifiers:

SELECT cc_num, full_name, wf_item_type, wf_item_key, cc_apprvl_status FROM apps.igc_cc_headers_v WHERE cc_apprvl_status = 'PENDING';

Because access level is computed for the invoking user via FND_GLOBAL.USER_ID, queries execute with the session’s security context. Consequently, results may differ between interactive sessions and concurrent-program runs, and integrations should set the user context explicitly before querying. All lookups and supplier joins are outer joins, so headers with incomplete supplier or lookup data are still returned.