Search Results source_award_id

Overview

APPS.GMS_PA_XFACE is a PL/SQL package body belonging to the Oracle EBS Grants Management (GMS) module, operating in the intersection between Grants Management and Oracle Projects (PA). Its primary business function is to validate and prepare awards-related expenditure data before that data is interfaced or adjusted within Oracle Projects. The package is classified as OTHER in the ETRM metadata, indicating it is not a formally published public API but a supporting internal routine set used by GMS/PA integration logic.

The package is closely associated with the "source_award_id" concept that users search for, because its validation routines resolve a destination award, confirm that award is a sponsored project, and then verify that the expenditure item in question is allowable against that award. The header comments state explicitly that the VERIFY wrapper is called from PAXTADJB.pll, confirming that this package supports the Projects Adjustments form and related reconciliation processing.

Key Procedures and Functions

• VERIFY — The principal wrapper function. It is invoked from the PAXTADJB.pll form to determine whether a given expenditure item passes the award-related validation rules. It delegates to the specialized check functions below and returns a boolean result indicating whether the record may proceed.
• GMS_IS_SPON_PROJECT — Determines whether a supplied project is a sponsored project by joining PA_PROJECTS to GMS_PROJECT_TYPES and testing the sponsored flag. This establishes whether award-based validation even applies.
• GMS_CHECK_EXP_TYPE — Confirms that an expenditure type is allowed for the allowability schedule associated with the destination award. Returns TRUE when the expenditure type is permissible.
• GMS_CHECK_AWARD_DATES — Verifies that the expenditure item date does not exceed the end date of the destination award. Returns TRUE when the date falls within the award period.
• GMS_CHECK_BURDENCOST — Checks whether the AP invoice distribution line has been reversed out. Returns FALSE when no matching reversed record is found in the AP tables, causing the record to fail validation.
• GMS_COMP_AWARDS — Supports comparison or matching of awards, typically used to reconcile source and destination award relationships.
• GMS_SPLIT — Handles the splitting of expenditure or award amounts, generally for distribution across multiple awards or allowability schedules.
• GMS_ADJUST_ITEMS — Applies adjustment logic to expenditure items identified during validation.
• GMS_SET_AWARD — Establishes or assigns the destination award for the transaction being processed.
• GMS_SET_PROJECT_ID — Sets or resolves the project identifier used by subsequent validation steps.

Tables Accessed

• PA_PROJECTS — Used to resolve project attributes and, through GMS_PROJECT_TYPES, confirm sponsored status.
• GMS_AWARDS_ALL — Provides award header data, including award dates and identifiers.
• GMS_AWARD_DISTRIBUTIONS — Supplies award distribution and allowability schedule context.
• GMS_ALLOWABLE_EXPENDITURES — Validates whether expenditure types are allowed for a given award schedule.
• PA_EXPENDITURE_ITEMS_ALL — The core expenditure item records being validated.
• PA_COST_DISTRIBUTION_LINES — Provides cost distribution detail for expenditure items.
• AP_INVOICE_DISTRIBUTIONS — Used by GMS_CHECK_BURDENCOST to detect reversed invoice distribution lines.

Usage Notes

GMS_PA_XFACE is invoked primarily from the Oracle Projects expenditure adjustments form (PAXTADJB.pll) through the VERIFY wrapper, and it is referenced by one other package per the ETRM metadata. It is not intended for direct external calls. The typical invocation flow is: a user adjusts a project expenditure item, the form calls VERIFY with the expenditure item identifier, and the package resolves the associated award, confirms sponsored status, and applies expenditure type, award date, and burden cost checks. Failures cause the record to be rejected or flagged. Because the package operates on AP and PA base tables, custom code should treat it as an internal validation layer rather than a supported integration point.