Search Results is_invoice_format_valid

Overview

The APPS.GMS_BILLING package is a PL/SQL API within the Oracle E-Business Suite Grants Management module. Its principal business function is to support the billing and revenue generation lifecycle for sponsored awards and grant-funded projects. The package encapsulates the logic required to identify billable award activity, generate billing events, populate billing extension attributes, and calculate burdened costs associated with award expenditures. By exposing this logic through a packaged API rather than embedded form code, Oracle enables both the standard Grants Management billing flows and customer-specific extensions to invoke award billing routines programmatically and consistently.

The package is declared AUTHID CURRENT_USER, meaning its unqualified database object references are resolved using the privileges of the invoking session rather than the package owner. This design is significant because much of its logic references APPS-owned synonyms, and it reinforces the expectation that the package is called within the APPS execution context, such as a concurrent manager session or a form running under the APPS schema.

Key Procedures and Functions

The ETRM metadata documents six procedures and functions within the package.

• AWARD_BILLING — The primary entry point for processing billing against an award. It accepts identifying information such as the award project, top task, calling process, amounts, percentages, billing and revenue dates, and billing extension identifiers. It orchestrates the creation of billing events and related revenue records for a given award project.
• INSERT_EVENT — Inserts records into the GMS_EVENT_ATTRIBUTE table. It takes award project, event number, installment, actual project/task, burden cost code, expenditure organization, bill amount, revenue amount, expenditure type, and an error code output parameter.
• UPDATE_EVENT — Modifies existing award billing event records, allowing corrections or adjustments to previously generated events.
• DELETE_EVENT — Removes billing event records, typically used when an event is reversed, cancelled, or superseded by a re-validated billing run.
• GET_TOTAL_ADL_RAW_COST — Returns the total raw cost at the award distribution level (ADL), a supporting calculation used to derive billable or burdened amounts.
• IS_INVOICE_FORMAT_VALID — A validation function that determines whether a given invoice format is valid for award billing purposes. This function is the object most often sought by developers validating invoice configuration before allowing billing processing to proceed.

Tables Accessed

The package reads and writes a broad set of Grants Management and shared reference tables through APPS synonyms. GMS_AWARDS and GMS_AWARDS_ALL provide the award header and organization-specific award context. GMS_AWARD_DISTRIBUTIONS and GMS_BURDEN_COMPONENTS drive distribution-level and burden calculation logic. GMS_CONCURRENCY_CONTROL supports locking and concurrent process coordination. Billing event data is managed in GMS_EVENT_ATTRIBUTE, GMS_EVENT_INTERSECT, and GMS_EVENTS_TEMP_FORMAT, while GMS_INSTALLMENTS and GMS_SUMMARY_PROJECT_FUNDINGS supply installment and funding information. Party and site references come from HZ_CUST_ACCOUNTS and HZ_CUST_SITE_USES. Organizational and classification data is drawn from HR_ALL_ORGANIZATION_UNITS_TL, PA_CLASS_CATEGORIES, and GMS_PERSONNEL.

Usage Notes

GMS_BILLING is typically invoked from the Grants Management billing concurrent programs, from the award billing forms, and from custom PL/SQL extensions that need to generate or validate award billing events. Because the package is referenced by zero other documented packages, its public procedures are generally called directly by application flows or bespoke code rather than through an intermediate wrapper. Developers should invoke it within the APPS schema context and respect the concurrency control tables it uses when running billing in parallel. The IS_INVOICE_FORMAT_VALID function is normally called as a pre-processing check to confirm that an invoice format is acceptable before committing billing data.