Results for “actual_task_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GMS_EVENT_ATTRIBUTE is a table owned by the GMS schema (Grants Accounting) in Oracle EBS 12.1.1 and 12.2.2. It stores supplementary billing event information that maps to the core billing event records maintained in the PA_EVENTS table. While PA_EVENTS holds the master billing event definition used by Project Billing, GMS_EVENT_ATTRIBUTE carries the grant-specific and revenue-recognition attributes that Grants Accounting needs to correctly value, burden, and recognize revenue on those events. In practice, the table acts as an extension of PA_EVENTS: a row exists only where additional grant-related detail is required, keyed back to the originating project and event number.

From a dimensional modeling perspective, the foreign-key structure — which references PA_EVENTS and IGS_FI_PP_INSTLMNTS rather than containing its own downstream dependents — suggests a satellite-leaning classification. That is, GMS_EVENT_ATTRIBUTE behaves as an attribute-bearing satellite attached to the PA_EVENTS hub/link, carrying descriptive and monetary measures about a billing event rather than defining new business entities.

Key Information Stored

The table contains 20 documented columns. The most significant are:

• PROJECT_ID and EVENT_NUM — the composite business key that links each attribute row to its parent billing event in PA_EVENTS. Together these form the foreign key to PA_EVENTS.
• INSTALLMENT_ID — foreign key to IGS_FI_PP_INSTLMNTS, tying the event to a specific receivable installment.
• ACTUAL_PROJECT_ID and ACTUAL_TASK_ID — the project and task against which the event is actually costed or recognized, which may differ from the owning project.
• BILL_AMOUNT, REVENUE_AMOUNT, and WRITE_OFF_AMOUNT — the monetary measures associated with the event.
• REVENUE_ACCUMULATED — the cumulative revenue recognized to date for the event.
• BURDEN_COST_CODE and EXPENDITURE_TYPE — costing classification used to derive burden and expenditure treatment.
• EXPENDITURE_ORG_ID — the organization owning the expenditure.
• RESOURCE_LIST_MEMBER_ID — links the event to a resource list member for rate and billing determination.
• REQUEST_ID, EVENT_CALLING_PROCESS — audit and process-origination fields identifying the concurrent request and calling process that created the row.
• CREATED_BY, CREATED_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS WHO columns.

No standalone surrogate primary key column is documented; the identifying key is the composite of PROJECT_ID and EVENT_NUM inherited from the PA_EVENTS relationship.

Common Use Cases and Queries

The table is typically queried when reconciling grant billing events, validating revenue recognition, or auditing how a PA_EVENTS record was valued. A common pattern joins the attribute row to its parent event:

• Reconcile billed versus recognized amounts: SELECT EVENT_NUM, BILL_AMOUNT, REVENUE_AMOUNT, REVENUE_ACCUMULATED FROM GMS_EVENT_ATTRIBUTE WHERE PROJECT_ID = :project_id;
• Identify events tied to receivables installments: SELECT INSTALLMENT_ID, BILL_AMOUNT FROM GMS_EVENT_ATTRIBUTE WHERE INSTALLMENT_ID IS NOT NULL;
• Trace event origination for audit: SELECT EVENT_CALLING_PROCESS, REQUEST_ID FROM GMS_EVENT_ATTRIBUTE WHERE EVENT_NUM = :num;
• Reporting by burden and expenditure classification for grant costing analysis.

Related Objects

• PA_EVENTS — parent billing event table; joined on PROJECT_ID and EVENT_NUM.
• IGS_FI_PP_INSTLMNTS — installment table referenced via INSTALLMENT_ID.
• PA_PROJECTS_ALL / PA_TASKS — descriptive source for ACTUAL_PROJECT_ID and ACTUAL_TASK_ID.
• PA_EXPENDITURE_TYPES — validates EXPENDITURE_TYPE.
• HR_ALL_ORGANIZATION_UNITS — resolves EXPENDITURE_ORG_ID.
• GMS_AWARD_* and GMS billing program objects — consume these attributes during grant billing and revenue recognition concurrent processes.