Search Results gms_default_reports_s

Overview

GMS_AWARD_PVT is a private PL/SQL package body in the APPS schema that encapsulates the core award-creation and award-maintenance logic for the Oracle Grants Management (GMS) module in Oracle E-Business Suite 12.1.1 and 12.2.2. The suffix _PVT marks it as an internal, private API layer: it is not registered as a public API and is not intended to be called directly by customer extensions. Rather, it provides the reusable business logic that the public Grants APIs and the Grants forms invoke when an award and its associated child entities are created, copied, or extended. It centralises award header processing, child record creation (installments, personnel, terms and conditions, reference numbers, contacts, reports and notifications), funding distribution, and the API message/return-status plumbing inherited from FND_API. Because the package body has STATUS VALID and is referenced by one other package, it forms part of the live, compiled Grants runtime rather than a dormant or customised object.

Key Procedures and Functions

The documented metadata lists fourteen procedures and functions:

• RESET_MESSAGE_FLAG, INIT_MESSAGE_STACK, ADD_MESSAGE_TO_STACK, SET_RETURN_STATUS — the standard FND_API error-handling scaffolding. These initialise the message stack, accumulate messages, reset the message flag between calls, and set the API return status (usually SUCCESS, EXPECTED_ERROR, or UNEXPECTED_ERROR).
• CREATE_AWARD — the principal entry point that inserts or processes the award header in GMS_AWARDS_ALL, applying defaults, validating the award attributes, and returning the generated award identifier.
• COPY_AWARD — duplicates an existing award and its dependent structures, supporting the "copy award" business flow.
• CREATE_INSTALLMENT — creates billing/schedule installment records associated with the award.
• CREATE_PERSONNEL — creates award personnel assignments (e.g., principal investigators, award managers).
• CREATE_TERM_CONDITION — creates award-level terms and conditions.
• CREATE_REFERENCE_NUMBER — creates award reference number records.
• CREATE_CONTACT — creates award contact records.
• CREATE_REPORT — creates default report definitions for the award.
• CREATE_NOTIFICATION — creates award notification records.
• ADD_FUNDING — appends funding distribution lines for the award, interacting with the project funding and multi-funding structures.

These are private, helper-style procedures rather than a single public API surface; the caller (typically a public Grants package) drives them in sequence inside one transaction. Parameter lists are not documented in the supplied metadata and are intentionally not reproduced here.

Tables Accessed

Through APPS synonyms the package reads and writes the Grants base and interface tables, including GMS_AWARDS_ALL (award header), GMS_AWARDS_S (award sequence/key), GMS_AWARDS_CONTACTS, GMS_AWARDS_TERMS_CONDITIONS, GMS_INSTALLMENTS and GMS_INSTALLMENTS_S, GMS_PERSONNEL and GMS_PERSONNEL_S, GMS_REFERENCE_NUMBERS, GMS_DEFAULT_REPORTS and GMS_DEFAULT_REPORTS_S, GMS_NOTIFICATIONS, GMS_ALLOWABILITY_SCHEDULES, GMS_IMPLEMENTATIONS_ALL, and GMS_SUMMARY_PROJECT_FUNDINGS. It also selects from control and setup sources such as FND_USER, FND_PROFILE and GL_PERIOD_STATUSES, and depends on the Oracle Projects (PA) and Trading Community (HZ) schemas — for example PA_PROJECTS_ALL, PA_AGREEMENTS_PKG, PA_BILLING_CYCLES and HZ_CUST_ACCOUNTS — reflecting the close coupling between awards, projects and customers.

Usage Notes

Because GMS_AWARD_PVT is a private package, it is normally invoked indirectly: from the Grants Award entry forms, from public Grants APIs, or from concurrent programs that create or copy awards in bulk. It must be called within the caller's transaction — it does not commit on its own and relies on the FND_MSG_PUB message stack for error reporting, so callers should check the return status and message stack after each call. Custom code should call the supported public Grants API rather than GMS_AWARD_PVT directly, since the private layer's signature can change between releases. The documented presence of COPY_AWARD and the child-creation routines indicates the package is the engine behind award copy, award creation, and award funding operations across Release 12.1.1 and 12.2.2.