Search Results gms_check_exp_type

Overview

The APPS.GMS_PA_XFACE package is a Grants Management System (GMS) integration utility within Oracle EBS that bridges sponsored award data and Oracle Projects expenditure accounting. It is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user and therefore relies on the caller's access to the APPS synonym layer. The package's central purpose is to evaluate expenditure items against award and project constraints and, where required, to split or adjust an expenditure item so that charges are correctly attributed across awards, projects, and burden structures.

In the Oracle EBS 12.1.1 and 12.2.2 environments, this package sits at the intersection of the Grants Accounting and Oracle Projects modules. It supports the business requirement that sponsored expenditure lines be validated for allowability, expenditure type, award dates, and burden cost before they are accepted, and that items spanning multiple awards or projects be partitioned correctly. The presence of the GMS_SPLIT procedure—the term commonly searched as "gms_split"—reflects this split-and-adjust capability as the package's defining function.

Key Procedures and Functions

• VERIFY — Function that validates an expenditure item, returning a boolean result indicating whether the item satisfies the package's verification logic.
• GMS_SPLIT — Procedure that performs the split processing for a given expenditure item, redistributing its cost across the appropriate award or project targets.
• GMS_IS_SPON_PROJECT — Function that determines whether a given project is a sponsored project, returning a boolean.
• GMS_CHECK_EXP_TYPE — Function that checks whether the expenditure type associated with an item is valid for the award context.
• GMS_CHECK_AWARD_DATES — Function that validates the expenditure item date against the award's effective start and end dates.
• GMS_COMP_AWARDS — Function that compares or computes award values based on an adjustment action, returning a string result.
• GMS_CHECK_BURDENCOST — Function that verifies the burden cost treatment for an expenditure item.
• GMS_ADJUST_ITEMS — Procedure that adjusts expenditure items in bulk, accepting a calling process identifier and a row count to control the scope of processing.
• GMS_SET_AWARD — Procedure that sets the source and destination award identifiers used during split or adjustment processing.
• GMS_SET_PROJECT_ID — Procedure that sets the source and destination project identifiers for the same purpose.

Tables Accessed

• PA_EXPENDITURE_ITEMS_ALL — The primary expenditure item records being verified, split, or adjusted.
• PA_PROJECTS — Project definitions used to identify sponsored projects.
• PA_COST_DISTRIBUTION_LINES — Cost distribution detail supporting adjustment and split logic.
• GMS_AWARDS_ALL — Award master data referenced for award dates and sponsored project determination.
• GMS_AWARD_DISTRIBUTIONS — Award distribution records used in award comparison and allocation.
• GMS_ALLOWABLE_EXPENDITURES — Allowable expenditure definitions used for allowability checks.
• AP_INVOICE_DISTRIBUTIONS — AP distribution data consulted during expenditure verification and interface processing.

Usage Notes

GMS_PA_XFACE is typically invoked programmatically rather than directly by end users. It is called from Grants Accounting and Oracle Projects forms, from concurrent programs that process expenditure adjustments, and from custom extensions that must enforce award validation rules. Because it is referenced by one other package, it functions as a lower-level utility within the GMS integration stack. The GMS_ADJUST_ITEMS procedure's calling-process and row-count parameters indicate it is designed to be driven by batch or mass-adjustment processes. Custom code should call these APIs within a controlled transaction and handle the boolean-returning validation functions carefully, since they signal pass/fail outcomes rather than raising exceptions. The fixed globals (SOURCE_AWARD_ID, DEST_AWARD_ID, and related variables) carry state between the setter procedures and the processing routines, so callers must set them in the correct sequence.