Search Results get_budget_justification
Overview
IGW_GR_REPORT_PROCESSING is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM (E-Business Suite Technical Reference Manual) as an OTHER API object. Its name associates it with the IGW product family, which supports Grants and Research Administration functionality — specifically proposal and award processing. Within that context, the package serves as a reporting support utility: it supplies formatted person, organization, and budget attributes that are consumed by grant and proposal report layouts. The body carries a version marker from 2005 (igwgrrpprb.pls 120.1), indicating it originated in a pre-12.x release and was carried forward into 12.1.1 and 12.2.2 without substantive change.
A notable characteristic of this package is that a significant portion of its accessor functions return NULL placeholders. This pattern is often encountered in EBS report-support packages where the original implementation was intended to delegate to an external party, address, or HR data source that either became optional or was superseded. The package therefore functions primarily as a stable interface shell, shielding report templates from source data changes.
Key Procedures and Functions
The documented API surface comprises 25 functions and procedures, grouped by purpose:
- Person and Organization Accessors: GET_LAST_FIRST_MIDDLE_NAME, GET_JOB_TITLE, GET_PERSON_ORGANIZATION, GET_PHONE_NUMBER, GET_FAX_NUMBER, GET_EMAIL_ADDRESS, and GET_PERSON_ADDRESS retrieve formatted party attributes for report presentation. In the documented source, several of these simply return NULL, acting as placeholder stubs.
- Address Formatting: FORMAT_ADDRESS and FORMAT_ADDRESS_MULTILINE construct display-ready address strings, supporting both single-line and block address rendering on report output.
- Research and Approval: DOES_SPECIAL_RESEARCH evaluates whether a proposal is subject to a special review code; ANIMAL_APPROVAL_DATE returns the animal protocol approval date associated with a proposal.
- Budget and Distribution Reporting: GET_CATEGORY_PERIOD_AMOUNT, GET_CATEGORY_PERIOD_DESC, GET_PERIOD_DISTR_DC, GET_PERIOD_DISTR_IC, GET_TOTAL_DISTR_DC, and GET_TOTAL_DISTR_IC return budget category amounts and distribution figures, distinguishing direct cost (DC) from indirect cost (IC) components across periods.
- Salary and Effort: GET_SALARY_REQUESTED, GET_EMPLOYEE_BENEFITS, and GET_BUDGET_PERCENT_EFFORT expose proposed salary, benefit, and percent-effort values used in budget justification narratives.
Tables Accessed
The ETRM metadata excerpt does not enumerate any tables referenced through APPS synonyms. The documented source excerpt likewise shows only parameter-driven function bodies with no embedded SQL. Where data is retrieved in the full implementation, it would be expected to read proposal, budget, and party tables within the IGW schema via APPS synonyms, consistent with the function names. Because no table list is documented, integrators should treat the package as a thin presentation layer and confirm actual dependencies through the compiled source in their environment.
Usage Notes
Referenced by zero other packages per the ETRM, IGW_GR_REPORT_PROCESSING is an entry-point package rather than a shared library. It is most plausibly invoked from Oracle Reports or BI Publisher report definitions that produce grant proposal and budget justification documents, with function calls embedded in the report query or formula columns. A user searching for "get_budget_justification" will not find a function of that exact name in this object; the budget justification content is derived from the individual budget, salary, benefit, and percent-effort functions listed above, which a report template would combine to assemble the justification text. Custom code should call these functions rather than querying underlying tables directly, since the package isolates report logic from schema changes. Given the NULL-returning placeholders, any customization relying on those specific functions should validate output in the target 12.1.1 or 12.2.2 instance before deployment.