Search Results create_reference_number

Overview

APPS.GMS_AWARD_PVT is a private PL/SQL package in Oracle Grants Accounting (part of Oracle E-Business Suite, applicable to releases 12.1.1 and 12.2.2). It encapsulates the low-level business logic used to create and manipulate award records within the GMS (Grants Management System) schema. The package is classified as "PVT," meaning it is not intended as a public integration surface; instead, it is called by the public award API layer (notably GMS_AWARD_PUB) and by other internal packages. Its responsibilities span award creation, copying, and the assembly of related child entities such as installments, personnel, terms and conditions, reference numbers, contacts, reports, and notifications. The package also provides a shared message-handling framework that tracks success, warning, and error states across the API call stack.

Key Procedures and Functions

The documented procedures fall into two functional groups: message-handling utilities and award data manipulation routines.

• reset_message_flag — Resets internal flags indicating that the global message table has not yet been initialized. Called from GMS_AWARD_PUB at the start of an API invocation.
• init_message_stack — Initializes the message stack used to accumulate messages during processing.
• add_message_to_stack — A common program unit that places a message into the stack, accepting a label plus optional token/value substitution pairs.
• set_return_status — Sets the standardized return status indicator (such as success or failure) propagated back to the caller.
• create_award — The core private API that inserts an award into Grants Accounting, primarily intended to transfer legacy system data into GMS. It returns the newly created award identifier along with message count and status indicators.
• copy_award — Duplicates an existing award and its associated structures.
• create_installment — Creates installment records associated with an award.
• create_personnel — Creates personnel assignments for the award.
• create_term_condition — Creates award term and condition entries.
• create_reference_number — Creates reference number entries for the award.
• create_contact — Creates contact records tied to the award.
• create_report — Creates default report assignments for the award.
• create_notification — Creates notification records for the award.
• add_funding — Adds funding information to an award. This procedure is the specific entry point returned for the "add_funding" search and is invoked as part of the award assembly logic.

Tables Accessed

The package reads and writes a consistent set of GMS and FND tables through APPS synonyms:

• GMS_AWARDS_ALL and GMS_AWARDS_S — the primary award entity and its sequence, written by create_award and copy_award.
• GMS_INSTALLMENTS and GMS_INSTALLMENTS_S — installment data and sequence used by create_installment.
• GMS_PERSONNEL — personnel assignments maintained by create_personnel.
• GMS_AWARDS_TERMS_CONDITIONS — term and condition records maintained by create_term_condition.
• GMS_REFERENCE_NUMBERS — reference number entries maintained by create_reference_number.
• GMS_AWARDS_CONTACTS — contact records maintained by create_contact.
• GMS_DEFAULT_REPORTS and GMS_DEFAULT_REPORTS_S — default report definitions used by create_report.
• GMS_NOTIFICATIONS — notification records maintained by create_notification.
• GMS_ALLOWABILITY_SCHEDULES — allowability schedule validation data consulted during award processing.
• GMS_IMPLEMENTATIONS_ALL — implementation configuration data read during setup validation.
• FND_USER — user identity reference used for audit and message attribution.
• GL_PERIOD_STATUSES — open/closed period information consulted to validate transaction timing.

Usage Notes

GMS_AWARD_PVT is invoked indirectly rather than by end users. The Grants Accounting award entry form and related concurrent programs call the public API layer, which in turn delegates to this private package. The reset_message_flag and init_message_stack procedures are expected to be called first from GMS_AWARD_PUB, establishing the message context that add_message_to_stack and set_return_status then populate. The create_* procedures support both interactive award definition and bulk legacy data conversion, while copy_award supports award duplication scenarios. The add_funding procedure participates in the same award-construction flow. Custom integrations should not call GMS_AWARD_PVT directly; the supported entry point remains GMS_AWARD_PUB, which is the only documented caller referenced in this metadata. Because the package is compiled with AUTHID CURRENT_USER, execution privileges and synonym resolution depend on the invoker's schema context, a consideration when debugging in multi-org or custom schema deployments.