Search Results igc_cc_wf_accounts_pkg

Overview

The IGC_CC_WF_ACCOUNTS_PKG package is an Oracle Application Object Library PL/SQL package owned by the APPS schema. It resides within the Oracle E-Business Suite (EBS) Grants and Contracts (IGC) product family, where the "CC" designation conventionally refers to Costing and Charging logic. The package is classified under the ETRM documentation as an "OTHER" API classification, meaning it is a supporting internal package rather than a publicly released application programming interface. Its status is recorded as VALID in both Oracle EBS 12.1.1 and 12.2.2.

Functionally, the package serves as a workflow-oriented helper for determining how accounts and accounting attributes behave in the context of contract and project costing. It provides decision logic used by Oracle Workflow processes to determine whether a given transaction relates to a contract project, whether encumbrance accounting is enabled for the relevant context, and what charge account should be assigned to a workflow-driven accounting event. The package therefore bridges the IGC contracting domain and the Workflow engine, supplying the accounting routing and validation rules that Workflow needs in order to progress a transaction correctly.

Key Procedures and Functions

The ETRM metadata documents four procedures/functions within this package:

• IS_CC_PROJECT_RELATED — Evaluates whether the project associated with the current workflow context is a cost-collection, contract-related project. This boolean-style check allows downstream workflow branches to determine if contract costing and charging rules apply, or whether the transaction should be treated as standard project billing.
• IS_ENCUMBRANCE_ON — Determines whether encumbrance accounting is enabled for the applicable ledger or operating unit. This drives Workflow decision branches that govern whether funds reservation, encumbrance entries, or budget checking are required before the accounting entry can be created.
• GET_CHARGE_ACCOUNT — Returns the charge account (or accounting flexfield combination) that should be applied to the workflow transaction. This is central to accounting derivation in IGC costing workflows, ensuring that the correct General Ledger account is passed forward for subledger accounting and journal creation.
• NO_PROCESS_DEFINED — A fallback or exception handler invoked when no matching process definition is found for a given workflow scenario. It signals an error or unhandled state so that the calling process can fail gracefully rather than creating an incorrect accounting entry.

Tables Accessed

The ETRM dependency excerpt for this object does not enumerate direct base-table references via APPS synonyms. The dependency information lists only SYS.STANDARD as a referenced program unit, indicating that the package relies primarily on PL/SQL built-in constructs, internal package logic, and Workflow context values rather than on direct SELECT/INSERT statements against IGC or GL tables. Where table access does occur, it would typically be through public synonyms in the APPS schema that resolve to IGC costing, project, and accounting setup tables. Because no tables are documented, implementers should treat this as a logic/decision package rather than a data-manipulation package.

Usage Notes

This package is referenced by no other documented packages and has no downstream dependents recorded, confirming its role as a leaf-level utility invoked from Oracle Workflow process definitions rather than from other PL/SQL APIs. It is most commonly executed through Workflow function activities configured in IGC costing and contract processes, where the returned charge account and boolean checks feed gateway and assignment nodes. Custom code should avoid calling this package directly unless replicating Workflow behaviour, since its procedures are tuned to the internal Workflow context. Any extension should be regression-tested in both 12.1.1 and 12.2.2, as the package remains VALID in each release.