Results for “system_linkage_function”

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

Overview

GMS_ENCUMBRANCE_GROUPS_ALL is the Grants Accounting (GMS) master table that stores groups of pre-approved encumbrances. In Oracle EBS 12.1.1 and 12.2.2, it defines the top-level grouping construct used to organize encumbrances that have been pre-approved within the grants and project accounting flow, so that related commitment transactions can be handled, tracked, and validated as a single logical unit. The table resides in the GMS schema and is documented as VALID within the ETRM repository.

From a Data Vault modeling perspective, the mined metadata classifies this object as satellite-leaning. In practical terms, it functions as a core grouping header that carries descriptive and status attributes around the primary grouping key, while dependent transaction-level encumbrance detail would be modeled in separate linked structures. This classification is a heuristic derived from the foreign key topology and should be treated as a modeling suggestion rather than a prescriptive design.

Key Information Stored

The table defines 18 columns. The most significant are:

• ENCUMBRANCE_GROUP — the surrogate primary key of the table, enforced by GMS_ENCUBMBRACE_GROUPS_PK. It also appears as the business-key candidate in the unique index GMS_ENCUBMBRACE_GROUPS_U1.
• ENCUMBRANCE_GROUP_STATUS_CODE — the lifecycle status of the encumbrance group.
• ENCUMBRANCE_ENDING_DATE — the effective end date associated with the group.
• SYSTEM_LINKAGE_FUNCTION — a reference to the system linkage function defined in PA_SYSTEM_LINKAGES, linking the group to the owning application context.
• CONTROL_COUNT and CONTROL_TOTAL_AMOUNT — control totals that reconcile the number and monetary value of encumbrances assigned to the group.
• DESCRIPTION — free-text description of the group.
• TRANSACTION_SOURCE — identifies the originating source of the group record.
• ORG_ID — the operating unit identifier supporting multi-org access, consistent with the _ALL naming convention.

Standard WHO columns are also present: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, plus the concurrent program context columns REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, and PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical usage includes reconciling pre-approved encumbrances, reporting control totals per group, and validating status before downstream processing. A representative query:

• SELECT eg.encumbrance_group, eg.encumbrance_group_status_code, eg.encumbrance_ending_date, eg.control_count, eg.control_total_amount FROM gms.gms_encumbrance_groups_all eg WHERE eg.org_id = :p_org_id AND eg.encumbrance_group_status_code = :p_status;
• Joining to PA_SYSTEM_LINKAGES on SYSTEM_LINKAGE_FUNCTION to enrich reports with the linkage function meaning.
• Aggregating CONTROL_TOTAL_AMOUNT by organization or status for commitment reporting.

Related Objects

The documented foreign key links GMS_ENCUMBRANCE_GROUPS_ALL.SYSTEM_LINKAGE_FUNCTION to PA_SYSTEM_LINKAGES, the most direct dependency. Additional significant relationships in this functional area include project and award encumbrance structures in PA and GMS, the Grants Accounting encumbrance detail and approval tables that reference the group, and the multi-org operating unit definitions keyed by ORG_ID. Reports and concurrent programs consume the control totals and status columns for reconciliation and approval workflows.