Results for “get_line_item_cost”

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

Overview

IGW_BUDGET_INTEGRATION is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the OTHER API category. It belongs to the Oracle Grants Management (IGW) product family and serves as the budget integration layer between grant award and proposal data and the Oracle Projects budgeting engine. The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema rather than the definer, a design characteristic common to integration-layer packages that must respect the caller's data security context. Its principal business purpose is to compute, validate, and materialize award budgets, including burdened cost figures such as overhead and employee benefit amounts, and to resolve the budgeting configuration (entry method, resource list, and entry level) that governs how a project budget is built. The package also supports self-service application flows, as indicated by an internal comment noting that the create_award_budget procedure is invoked from the Self-Service application. This makes it a shared component used by both the professional forms-based Grant Management interface and the self-service grants pages.

Key Procedures and Functions

The package exposes ten documented program units, most of which are read-only helper functions used by budget calculation callers.

• GET_LINE_ITEM_COST — Returns the cost associated with a given line item identifier. Used to retrieve the raw cost for a budget or proposal line.
• GET_OH_COST — Returns the overhead (indirect) cost associated with a given line item identifier, applying the applicable overhead basis.
• GET_EB_COST — Returns the employee benefit cost associated with a given line item identifier.
• GET_EB_COST_PERSONNEL — Returns the employee benefit cost for a specific personnel detail record. This is the function referenced in the user's search and is the personnel-level counterpart to GET_EB_COST, allowing callers to obtain burden amounts at the individual personnel detail grain rather than at the line item grain.
• GET_OH_COST_SS — Overhead cost variant that returns unrounded figures, per the package comment noting that "_ss functions return unrounded figures."
• GET_EB_COST_SS — Employee benefit cost variant returning unrounded figures.
• GET_RESOURCE_LIST_ENTRY_METHOD — Returns the budgeting configuration for a project, including the budget entry method code, resource list identifier, time-phased type code, entry level code, and categorization code. It also returns a status and message for error handling.
• GET_RESOURCE_LIST_MEMBER_ID_SS — Resolves the resource list member identifier given a resource list, expenditure type, expenditure category flag, and categorization code, returning status and message outputs.
• CREATE_AWARD_BUDGET — Creates the award budget from a proposal installment identifier. This is the primary write operation and is called from the Self-Service application.
• VALID_EXPENDITURE_TYPE — Validates whether an expenditure type is permissible in the budgeting context.

Most cost functions and the two _ss functions carry the PRAGMA RESTRICT_REFERENCES(WNDS, WNPS) directive, confirming they are pure read functions that perform no writes to package or database state and are safe for SQL invocation.

Tables Accessed

The ETRM metadata for this package does not enumerate the underlying tables referenced through APPS synonyms. Functionally, the cost functions draw on budget line detail, personnel detail, and burden calculation data maintained by the Grants and Projects budgeting tables, while GET_RESOURCE_LIST_ENTRY_METHOD and GET_RESOURCE_LIST_MEMBER_ID_SS draw on resource list and project budgeting setup definitions. CREATE_AWARD_BUDGET writes into the award budget structures. Because the referenced tables are not documented here, exact table names cannot be asserted from the available metadata.

Usage Notes

IGW_BUDGET_INTEGRATION is typically invoked from Oracle Grants Management forms, from self-service grants pages (notably for award budget creation), and from custom client extensions that need to reuse award budgeting logic. The metadata records that the package is referenced by four other packages, confirming it functions as a reusable integration point rather than an isolated utility. The unrounded _ss variants should be used when precise, pre-rounding values are required for downstream aggregation, while the standard functions return rounded amounts suited to display. The presence of OUT NOCOPY status and message parameters on the procedures indicates a standard EBS error-handling contract in which callers must inspect x_return_status before consuming other OUT values. Because the package is AUTHID CURRENT_USER, callers must ensure their own schema has the necessary privileges on the underlying objects; grants to APPS or PUBLIC are not sufficient by themselves.