Search Results gms_allowable_expenditures_u1

Overview

GMS.GMS_ALLOWABLE_EXPENDITURES is a reference and configuration table in the Oracle EBS Grants Management (GMS) schema. It stores information about which expenditure types are allowable for a particular allowability schedule and, for each such expenditure type, the burden limits that govern how much burden cost can be charged. The table occupies a central position in the allowability rule framework used by Grants Management to determine whether costs charged to an award are permitted, and to what extent indirect or burden amounts may be applied.

The object resides in the APPS_TS_SEED tablespace, which is characteristic of seed and setup data rather than high-volume transactional data. The table is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2. Its physical schema in 12.2.2 consists of ten columns. The mined relationship data classifies GMS.GMS_ALLOWABLE_EXPENDITURES as standalone for Data Vault purposes. As a modeling suggestion, this would normally be modeled as a satellite attached to the allowability schedule hub, since each row qualifies an expenditure type within the context of a schedule rather than standing alone as an independent business entity.

Key Information Stored

The primary key is documented as GMS_ALLOWABLE_EXPENDITURES_PK, composed of ALLOWABILITY_SCHEDULE_ID and EXPENDITURE_TYPE. The unique index GMS_ALLOWABLE_EXPENDITURES_U1 carries the same two columns in the same order and therefore represents the business-key candidate: no schedule may define a given expenditure type more than once.

• ALLOWABILITY_SCHEDULE_ID — NUMBER(15), mandatory. Foreign key from GMS_ALLOWABILITY_SCHEDULES; identifies the schedule for which allowable expenditure types are being defined.
• EXPENDITURE_TYPE — VARCHAR2(30), mandatory. The allowable expenditure type for the schedule; a foreign key to PA_EXPENDITURE_TYPES.
• BURDEN_COST_LIMIT — NUMBER(22). The amount of raw cost for the expenditure type up to which burden cost may be charged.
• BURDEN_COST_LIMIT_PCT — NUMBER(22). The percentage of raw cost up to which burden can be calculated. Documented as not currently used.
• MTDC_EXEMPT_FLAG — VARCHAR2. Indicates whether the expenditure type is exempt from Modified Total Direct Cost; Y means exempted, N means not exempted.
• Standard Who columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN provide the standard Oracle Applications audit trail for each row.

Common Use Cases and Queries

The most common use is validating expenditure type allowability against a schedule when charges are processed or reviewed. Typical reporting includes identifying all allowable expenditure types for a schedule, and locating schedules that impose a burden cost ceiling on a given expenditure type. A basic retrieval follows the documented query text:

• SELECT ALLOWABILITY_SCHEDULE_ID, EXPENDITURE_TYPE, BURDEN_COST_LIMIT, BURDEN_COST_LIMIT_PCT, MTDC_EXEMPT_FLAG FROM GMS.GMS_ALLOWABLE_EXPENDITURES;
• Filter by schedule: WHERE ALLOWABILITY_SCHEDULE_ID = :p_schedule_id to review the allowable set for one schedule.
• Filter by expenditure type: WHERE EXPENDITURE_TYPE = :p_exp_type to see which schedules allow it.
• Burden ceiling analysis: WHERE BURDEN_COST_LIMIT IS NOT NULL to list expenditure types subject to a burden limit.
• MTDC review: WHERE MTDC_EXEMPT_FLAG = 'Y' to enumerate exempted expenditure types.

These patterns support award setup verification, burden policy audits, and reconciliations between schedule configuration and actual charges.

Related Objects

The FK and PK metadata identify the following significant relationships:

• GMS_ALLOWABILITY_SCHEDULES — parent of ALLOWABILITY_SCHEDULE_ID; join on ALLOWABILITY_SCHEDULE_ID to obtain schedule header details.
• PA_EXPENDITURE_TYPES — referenced by EXPENDITURE_TYPE; join on EXPENDITURE_TYPE to resolve expenditure type names and descriptions.
• GMS.GMS_ALLOWABLE_EXPENDITURES remains a child in both relationships; no further database objects are documented as referencing it directly.

Downstream processing in Grants Management, burden calculation, and MTDC determination consumes these allowability rules, while standard Who columns support audit and change tracking. The documented metadata states that the object does not itself reference any database object beyond the foreign keys described above.