Search Results get_event_info

Overview

The APPS.GMS_EVT_BILLING package body supports billing and revenue recognition processing for Grants Management System (GMS) awards within Oracle E-Business Suite. Grants accounting requires that award-funded projects be invoiced and that revenue be recognized against the correct funding source, event, and installment. This package provides the internal logic used to resolve event-level billing information for a given project and event number, then derive the amounts that must be billed or recognized.

The package is classified as OTHER in the ETRM metadata rather than as a public API, which indicates that it is primarily an internal worker package rather than a supported integration point. Its documented scope centers on a single entry point, MANUAL_BILLING, which orchestrates the billing process and, in turn, invokes helper procedures such as GET_EVENT_INFO and GET_CURR_BILLED_AMOUNT. The header comment (gmsinmab.pls 120.1) confirms the package belongs to the GMS inbound manual billing family and originated in the 11.5 code line, with the event lookup logic explicitly noted as reading from the GMS_EVENTS_V view for backward compatibility.

Key Procedures and Functions

• MANUAL_BILLING — The single documented procedure and the main driver of the package. It performs manual billing for GMS award events, coordinating the retrieval of event information, the calculation of currently billed amounts, and the generation of the corresponding billing transactions. It is also the procedure in which the package-level exception NO_PROCESSING_OF_AWARD is handled, although that exception may be raised from subordinate procedures invoked within it.
• GET_EVENT_INFO — A helper procedure (not listed among the documented ETRM procedures but present in the source) that resolves the event type, event type classification, installment identifier, and actual project and task identifiers for a supplied project and event number. It selects from GMS_EVENTS_V joined to PA_EVENT_TYPES. It raises NO_PROCESSING_OF_AWARD when no rows or too many rows are found, after logging the condition through GMS_ERROR_PKG.GMS_MESSAGE.
• GET_CURR_BILLED_AMOUNT — A second helper that determines the amount already billed for a given project, task, and installment, supplying the baseline against which new billing is computed.

The NO_PROCESSING_OF_AWARD exception is the package's principal error-signalling mechanism, ensuring that unresolved event data halts billing rather than producing incorrect invoices.

Tables Accessed

• GMS_AWARDS and GMS_SUMMARY_PROJECT_FUNDINGS — Award and funding data used to validate that the project is award-funded and to determine the funding context for billing.
• PA_EVENT_TYPES — Supplies the event type classification used to interpret the billing event.
• PA_PROJECTS_ALL and PA_TASKS — Project and task attributes needed to resolve the actual project and task for the event.
• PA_CUST_EVENT_RDL_ALL — Customer event revenue distribution lines that carry the billable event detail.
• PA_DRAFT_INVOICES, PA_DRAFT_INVOICE_ITEMS, PA_DRAFT_REVENUES, and PA_DRAFT_REVENUE_ITEMS — Draft invoice and revenue tables that receive or are queried for the billing and revenue recognition results.

These tables are referenced through APPS synonyms, consistent with standard EBS schema access. Together they span the award, project, event, and receivables subledger domains.

Usage Notes

GMS_EVT_BILLING is an internal GMS package rather than a general-purpose API. It is referenced by zero other packages in the ETRM metadata, indicating that its callers are UI or concurrent program layers rather than other PL/SQL packages. It is typically invoked from Grants Management billing forms or concurrent programs that perform manual billing of award events, and from any custom code that must reproduce GMS manual billing behavior.

Because the package manipulates draft invoice and revenue records, it should be invoked within the standard billing workflow to preserve Transaction Manager integrity and accounting consistency. The use of NOCOPY OUT parameters in its helper procedures reflects performance optimization for the relatively large number of returned values. Developers extending this logic should note the hard-coded dependency on GMS_EVENTS_V, which restricts event retrieval to the view's supported columns in both 12.1.1 and 12.2.2.