Search Results copy_award

Overview

GMS_AWARD_PUB is the public PL/SQL API package for the Oracle Grants Management (GMS) module in Oracle E-Business Suite. It exposes the server-side business logic that governs the creation and maintenance of award records stored in the GMS_AWARDS_ALL table, which is the central repository for sponsored-project award data in EBS. The package is classified as a published (PUB) API, meaning Oracle supports its procedures for direct invocation by external callers, including forms, concurrent programs, and customer-written extensions. Its procedures encapsulate the validation and defaulting rules required to create awards, copy awards, and establish the dependent child records — installments, personnel, terms and conditions, reference numbers, contacts, reports, and funding distributions — that together constitute a complete award setup.

Key Procedures and Functions

The package exposes nine documented public procedures:

• CREATE_AWARD — Creates a new award header record in GMS_AWARDS_ALL. Its signature accepts the full set of award attributes, including award number, short and full names, start, end, close, and pre-award dates, award purpose and status codes, award manager and organization identifiers, funding source details, and the billing and revenue distribution rules, schedules, and formats that drive downstream invoicing and revenue recognition. Callers supply decode values rather than internal code values, and the procedure returns a status indicator alongside the generated award identifier.
• COPY_AWARD — Duplicates an existing award to create a new award record. This is the procedure referenced by the search term "copy_award" and supports establishing a new award that inherits the configuration of a predecessor award, which is common when awards are renewed, amended, or repeated across periods.
• CREATE_INSTALLMENT — Creates installment records associated with an award, used to define scheduled billing or funding amounts over the life of the award.
• CREATE_PERSONNEL — Creates award personnel assignments, linking individuals to an award with their associated roles.
• CREATE_TERM_CONDITION — Creates term and condition records attached to an award, capturing the contractual clauses that govern the award.
• CREATE_REFERENCE_NUMBER — Creates reference number entries, allowing sponsor, agency, or internal reference identifiers to be associated with the award.
• CREATE_CONTACT — Creates award contact records, associating contacts and their roles with the award.
• CREATE_REPORT — Creates award report definitions, specifying reporting requirements tied to the award.
• ADD_FUNDING — Adds funding distributions or funding source allocations to an award.

Tables Accessed

The package operates against several documented tables, accessed through APPS synonyms. GMS_AWARDS_ALL is the primary table, holding the award header and its descriptive, financial, and scheduling attributes, and is the target of CREATE_AWARD and COPY_AWARD. GMS_ALLOWABILITY_SCHEDULES stores allowable cost schedules referenced during award creation and copied as part of award duplication. GMS_INSTALLMENTS holds the installment records produced by CREATE_INSTALLMENT, defining the schedule of amounts billed or funded against an award. PA_BILLING_CYCLES supplies billing cycle information used to determine the billing cadence applied to an award. Collectively these tables support both award definition and the billing and funding configuration that drives subsequent project accounting activity.

Usage Notes

GMS_AWARD_PUB is typically invoked from the Grants Management forms when users create or copy awards through the standard user interface, where the form calls the public API rather than performing direct DML. It is also called from concurrent programs and from custom PL/SQL integrations that load award data from external systems or legacy sources. Because the API performs business-rule validation and returns a status of S (success), E (business rule error), or U (unexpected error), calling code must check the return status and inspect the message count and message data outputs before proceeding. The API version constant is 1.0. The package is not referenced by any other documented package, so callers integrate with it directly. When invoking COPY_AWARD or CREATE_AWARD, source systems must supply decode values, not internal code values, to ensure correct validation.