Search Results gms_billing




Overview
Explore in AI Chat

Overview

GMS_BILLING is an Oracle Application Object Library (APPS) schema package body that supports billing and invoicing operations for Oracle Grants Management. It provides the business logic required to transform award-related expenditures, burden costs, and event data into billable transactions that can be processed by Oracle Projects. The package occupies the boundary between the grants and projects billing engines, drawing on award structures such as GMS_AWARDS, award distributions, installments, and burden components, while invoking the Oracle Projects billing infrastructure through PA_BILLING_PUB, PA_BILLING_SEQ, and related compiled multiplier and cost base tables.

The package is documented in the ETRM as a non-API utility (API classification OTHER) with a VALID status and no inverse dependencies; no other database objects reference GMS_BILLING, indicating it is invoked only from external callers such as concurrent programs or Grants forms.

Key Procedures and Functions

The ETRM documents six procedures and functions within GMS_BILLING. Their purposes are summarized below; parameter lists are not published.

  • AWARD_BILLING — The central driver routine. It assembles award expenditure and event activity and triggers the generation of billing transactions against the associated Projects contracts.
  • INSERT_EVENT — Creates billing event records used to hold billable amounts, dates, and attributes prior to invoice generation.
  • UPDATE_EVENT — Modifies existing billing events, allowing amounts or descriptive attributes to be corrected after initial entry.
  • DELETE_EVENT — Removes billing events that should no longer participate in invoicing.
  • GET_TOTAL_ADL_RAW_COST — Returns the total raw cost from the Award Distribution Lines (ADL) for a given context, used as input to burden and billing calculations.
  • IS_INVOICE_FORMAT_VALID — Boolean-style validation that determines whether an invoice format is properly configured for the award billing process.

Tables Accessed

GMS_BILLING reads and writes a broad set of Oracle Grants, Oracle Projects, and Trading Community tables through APPS synonyms. The award family — GMS_AWARDS, GMS_AWARDS_ALL, GMS_AWARD_DISTRIBUTIONS, GMS_BURDEN_COMPONENTS, GMS_INSTALLMENTS, GMS_SUMMARY_PROJECT_FUNDINGS, and GMS_PERSONNEL — supplies the award terms, distribution rules, burden structures, payment schedules, and personnel assignments that drive billing. The event tables GMS_EVENTS_TEMP_FORMAT, GMS_EVENT_ATTRIBUTE, and GMS_EVENT_INTERSECT store temporary and persistent event data used by the INSERT, UPDATE, and DELETE event routines. GMS_CONCURRENCY_CONTROL and GMS_ERROR_PKG provide locking and error propagation for concurrent execution.

On the Projects side, the package references PA_PROJECTS_ALL, PA_PROJECT_TYPES, PA_PROJECT_CUSTOMERS, PA_PROJECT_PARTIES, PA_PROJECT_ROLE_TYPES, PA_TASKS, and PA_EXPENDITURES to resolve contract and task context. PA_EXPENDITURE_ITEMS_ALL, PA_EXPENDITURE_TYPES, PA_COST_DISTRIBUTION_LINES_ALL, PA_COST_BASE_COST_CODES, PA_COST_BASE_EXP_TYPES, PA_IND_COST_CODES, PA_COMPILED_MULTIPLIERS, and PA_CLASS_CATEGORIES feed cost and revenue computation. PA_EVENTS, PA_INVOICE_FORMAT_DETAILS, PA_INVOICE_GROUP_COLUMNS, PA_INVOICE_GROUP_TABLES, and the invoice group whitelist tables hold event and invoice formatting metadata. HZ_CUST_ACCOUNTS and HZ_CUST_SITE_USES resolve customer and site-use information, while HR_ORGANIZATION_UNITS and HR_ALL_ORGANIZATION_UNITS_TL resolve organization names. Foundation and currency utilities include FND_GLOBAL, FND_PROFILE, PA_CURRENCY, PA_OUTPUT_TAX, PA_BILLING_PUB, PA_BILLING_SEQ, and the PLITBLM and DBMS_SQL built-ins.

Usage Notes

GMS_BILLING is not a published public API and is not referenced by any other package. It is typically invoked indirectly: from the Grants Management billing concurrent programs, from the award billing forms that capture billing events, or from custom extensions that need the same award billing logic. Because the package writes to Projects event and billing tables, it should be run with the APPS schema privileges and within the standard concurrent manager or form session context that populates FND_GLOBAL and FND_PROFILE. Custom callers should honor GMS_CONCURRENCY_CONTROL to prevent overlapping billing runs and should route diagnostics through GMS_ERROR_PKG so failures surface consistently with native Grants processes. No wrapper package or public synonym beyond APPS.GMS_BILLING is documented in ETRM.