Search Results get_inst_open_commitments

Overview

GMS_WF_PKG is the Oracle Grants Management workflow integration package within the APPS schema. It acts as the PL/SQL bridge between the Grants Management (GMS) budget and award data model and the Oracle Workflow engine. The package encapsulates the server-side logic invoked by workflow function activities during budget approval, budget baselining, budget rejection and installment processing, and it also exposes utility entry points used by forms, concurrent programs and other PL/SQL units to initiate or query those workflows. As classified in ETRM (API classification: OTHER), it is a supporting, non-public-API component rather than a declaratively supported interface; it is nonetheless a critical dependency for Grants budget approval processing.

The specific entry point associated with the search term get_burden_amount is a performance-oriented function. The package header notes that it was introduced under Bug 3465169 to return the burden amount calculated for a given burdenable raw cost, expenditure type, organization and indirect cost compiled set, thereby avoiding a join against the GMS_COMMITMENT_ENCUMBERED_V view.

Key Procedures and Functions

• GET_BURDEN_AMOUNT — Function returning the burden amount for a supplied expenditure type, organization, indirect cost compiled set and burdenable raw cost. Used to avoid an expensive join to GMS_COMMITMENT_ENCUMBERED_V.
• SELECT_BUDGET_APPROVER — Workflow function activity that determines the budget approver for the workflow item.
• VERIFY_BUDGET_RULES — Workflow function activity validating budget rules before approval proceeds.
• BASELINE_BUDGET — Workflow function activity that performs baselining of the budget.
• REJECT_BUDGET — Workflow function activity that rejects a budget.
• IS_BUDGET_WF_USED — Determines whether budget workflow is enabled for a project, award, budget type and product code; returns result plus error code, stage and stack.
• START_BUDGET_WF — Initiates the budget approval workflow for a draft version, project and award, optionally marking the budget as original.
• START_BUDGET_WF_NTFY_ONLY — Starts a notification-only variant of the budget workflow.
• SELECT_WF_PROCESS — Selects the applicable workflow process definition.
• FUNDS_CHECK — Performs funds availability checking within the workflow context.
• CHK_BASELINED_BUDGET_EXISTS — Verifies existence of a baselined budget.
• START_REPORT_WF_PROCESS — Launches the workflow used for report generation.
• SCHEDULE_NOTIFICATION — Schedules workflow notifications.
• INIT_INSTALLMENT_WF, START_INSTALLMENT_WF, NOTIFY_INSTALLMENT_CLOSEOUT — Initialize, start and notify on installment-related workflows.
• GET_INST_OPEN_COMMITMENTS — Retrieves open commitments for an installment.
• EXCL_PERSON_FROM_NOTIFICATION — Excludes a person from workflow notification distribution.

Tables Accessed

The package reads and writes GMS budget and workflow tables including GMS_BUDGET_VERSIONS, GMS_BC_PACKETS, GMS_ENCUMBRANCE_ITEMS, GMS_SUMMARY_PROJECT_FUNDINGS, GMS_WF_PROCESSES and GMS_WORKFLOW_ITEMKEY_S. Award and installment data is drawn from GMS_AWARDS, GMS_INSTALLMENTS and GMS_PERSONNEL. Notification and reporting behavior relies on GMS_NOTIFICATIONS, GMS_REPORTS and GMS_REPORT_TEMPLATES. Workflow participant and profile resolution uses FND_USER, FND_PROFILE_OPTIONS and FND_PROFILE_OPTION_VALUES via APPS synonyms.

Usage Notes

GMS_WF_PKG is invoked principally by the Oracle Workflow engine when Grants budget approval and installment processes execute their function activities, and by Grants Management forms and concurrent programs that call IS_BUDGET_WF_USED, START_BUDGET_WF, START_BUDGET_WF_NTFY_ONLY and the installment entry points. GET_BURDEN_AMOUNT is called from custom or standard PL/SQL where a burden amount is required without incurring the cost of querying GMS_COMMITMENT_ENCUMBERED_V. Because the package is not classified as a public API and is referenced by three other packages, customizations should call it with caution and validate behavior across 12.1.1 and 12.2.2, where the 120.0 header version applies.