Search Results no_process_defined

Overview

IGC_CC_WF_ACCOUNTS_PKG is an Oracle EBS workflow support package owned by APPS and classified as OTHER under the ETRM metadata model. Its principal business purpose is to supply the decision logic used by Oracle Grants/Contracts (IGC) workflow processes that determine how charge accounts are generated for encumbrance accounting transactions. The package name reflects its role as the workflow (WF) accounts handling layer for the IGC costing and contracts modules, designated by the IGC_CC prefix (Contracts/Costing) plus WF for workflow integration.

The package body supplied in the source excerpt carries the header identifier IGCCWFCB.pls version 120.2.12000000.1, dated 20-Aug-2007, indicating that the logic has been stable across the 12.1.1 and 12.2.2 releases. Its functions are invoked as workflow function activities — that is, as callbacks within an Oracle Workflow process definition that evaluate a business condition and return a value stored in the workflow engine's result attribute. Because the package only performs read operations and attribute lookups, it does not itself post journals or update account balances; it merely directs the workflow to the correct downstream activity.

Key Procedures and Functions

The documented metadata lists four procedures/functions: IS_CC_PROJECT_RELATED, IS_ENCUMBRANCE_ON, GET_CHARGE_ACCOUNT, and NO_PROCESS_DEFINED.

• IS_ENCUMBRANCE_ON — Public procedure that evaluates whether encumbrance accounting is enabled for the workflow transaction. It reads the workflow item attribute CC_ENCUMBRANCE_FLAG via wf_engine.GetItemAttrText and returns COMPLETE:TRUE when the flag is Y, otherwise COMPLETE:FALSE. The procedure explicitly performs no action in CANCEL or TIMEOUT function modes and returns immediately, which is standard Oracle Workflow callback behavior.
• IS_CC_PROJECT_RELATED — Public procedure documented in the source as a dummy function intended to be replaced by a customized workflow function activity. It determines whether the default CC charge account generation rules apply or whether the transaction should instead follow CUSTOMIZED project accounting rules, returning a boolean-style workflow result. The body opens by retrieving a CC_PROJECT_ID numeric value and, like its sibling procedure, bypasses processing in CANCEL and TIMEOUT modes.
• GET_CHARGE_ACCOUNT — Public procedure referenced in the package metadata whose purpose is to derive the appropriate charge account to be used during the workflow's accounting step. The ETRM excerpt does not expose the implementation body, so parameter structure should be confirmed directly from the deployed source.
• NO_PROCESS_DEFINED — Public procedure listed in the package metadata. It corresponds directly to the search term "no_process_defined" and serves as the workflow branch or error handler invoked when no valid workflow process definition can be resolved for the transaction.

Tables Accessed

The documented metadata for this package records no tables referenced through APPS synonyms. Consistent with that fact, the visible source uses only the Oracle Workflow engine API (wf_engine.GetItemAttrText) and the wf_core.context error-logging API. Business data is therefore sourced from workflow item attributes such as CC_ENCUMBRANCE_FLAG rather than from direct SQL against application tables. Any account or encumbrance lookups performed by GET_CHARGE_ACCOUNT or NO_PROCESS_DEFINED are not enumerated in the metadata and should be verified against the deployed package.

Usage Notes

These procedures are designed to be registered as function activities within an IGC workflow process definition. The workflow engine passes itemtype, itemkey, actid, and funcmode on each invocation; the procedure sets the result OUT parameter to a string such as COMPLETE:TRUE or COMPLETE:FALSE, which the engine then uses to select the next transition. Because CANCEL and TIMEOUT modes are no-ops, the package is safe to leave attached to long-running or timed-out workflow items.

The ETRM metadata records zero packages referencing IGC_CC_WF_ACCOUNTS_PKG, so it is not called from other PL/SQL units in the APPS schema; invocation is exclusively through the Workflow runtime. Customizations should avoid editing the seeded body and instead follow the documented pattern for IS_CC_PROJECT_RELATED, substituting a custom function activity to override default charge account generation rules. The header comment fixes the baseline at version 120.2.12000000.1, which customers should compare against their instance before applying any patch-level changes.