Results for “gms_encumbrance_groups_v”
30 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The GMS_ENCUMBRANCE_GROUPS_V view is a reporting and integration object in the Oracle E-Business Suite Grants Accounting (GMS) module. It exposes encumbrance group records maintained in GMS_ENCUMBRANCE_GROUPS together with their descriptive, status, and cross-module linkage attributes, resolving foreign key values into user-facing meanings. Because the base table stores codes and IDs, this view performs the joins required to present readable status descriptions, transaction source details, and the identity of the creating user, making it suitable for both ad hoc reporting and programmatic consumption.
The view is owned by the APPS schema and is valid in 12.1.1 and 12.2.2. A defining characteristic, and the element most relevant to the "system_linkage" search, is the SYSTEM_LINKAGE_FUNCTION and SYSTEM_LINKAGE columns. The former is the stored code on the encumbrance group; the latter is its decoded meaning resolved from PA_SYSTEM_LINKAGES (matched on SL.FUNCTION = E.SYSTEM_LINKAGE_FUNCTION). This pairing lets users see not only which linkage function is assigned but what that function actually represents in the Projects/Grants integration context.
Underlying Base Objects
The view is defined over the following documented base objects: GMS_ENCUMBRANCE_GROUPS, FND_USER, PER_PEOPLE_F, PA_TRANSACTION_SOURCES, PA_SYSTEM_LINKAGES, and PA_LOOKUPS. All joins to the peripheral descriptive objects are outer joins (denoted by the (+) operator), so an encumbrance group is returned even when the matched user, person, or transaction source is absent. The join to PA_SYSTEM_LINKAGES is an inner join, since both SYSTEM_LINKAGE_FUNCTION and its meaning come from that pairing.
The metadata further lists referenced packaged objects: HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY, which support person name resolution and security. Where the view columns are involved, CREATED_BY links through FND_USER to PER_PEOPLE_F so that the creating user's employee name and employee (or NPW) number can be surfaced. The PA_LOOKUPS join resolves ENCUMBRANCE_GROUP_STATUS_CODE against lookup type 'EXPENDITURE GROUP STATUS'.
Key Columns
- ENCUMBRANCE_GROUP — the encumbrance group identifier and primary business key.
- ENCUMBRANCE_ENDING_DATE, ENCUMBRANCE_GROUP_STATUS_CODE, ENCUMBRANCE_GROUP_STATUS_M — ending date, stored status code, and decoded status meaning.
- SYSTEM_LINKAGE_FUNCTION / SYSTEM_LINKAGE — the stored linkage function code and its decoded meaning from PA_SYSTEM_LINKAGES.
- DESCRIPTION, CONTROL_COUNT, CONTROL_TOTAL_AMOUNT — group description and control totals used for validation.
- TRANSACTION_SOURCE, USER_TRANSACTION_SOURCE, ALLOW_ADJUSTMENTS_FLAG, ALLOW_REVERSAL_FLAG — source identifiers and the decoded source name with its adjustment and reversal permissions.
- CREATED_BY, CREATED_BY_EMPLOYEE_NAME, CREATED_BY_EMPLOYEE_NUMBER — audit creator and resolved person details.
- ORG_ID — the operating unit, supporting multi-org filtering.
- ROW_ID — the base table ROWID, exposed for row-level identification.
Common Use Cases and Queries
Typical uses include encumbrance group status reporting, reconciliation of group control totals, and integration extracts that must publish the decoded system linkage rather than raw codes. The following query lists groups with their status and decoded linkage:
SELECT encumbrance_group, encumbrance_ending_date,
encumbrance_group_status_m, system_linkage,
user_transaction_source, control_total_amount
FROM apps.gms_encumbrance_groups_v
WHERE org_id = :p_org_id
AND encumbrance_group_status_code = 'OPEN';
To trace creation and linkage for a specific function:
SELECT e.encumbrance_group, e.system_linkage,
e.created_by_employee_name, e.created_by_employee_number
FROM apps.gms_encumbrance_groups_v e
WHERE e.system_linkage_function = :p_function;
Because the view relies on outer joins, consumers should still guard against null descriptive values and always constrain by ORG_ID or a specific group when querying in multi-org environments.
-
APPS.GMS_ENCUMBRANCE_GROUPS_V·↳ FND_USER·↳ GMS_ENCUMBRANCE_GROUPS·↳ HR_GENERAL·Explore GMS module →
-
APPS.GMS_ENCUMBRANCE_GROUPS_V·↳ FND_USER·↳ GMS_ENCUMBRANCE_GROUPS·↳ HR_GENERAL·Explore GMS module →
-
12.2.2 DBA Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
VIEW: APPS.PA_LOOKUPS 12.2.2
-
VIEW: APPS.PA_LOOKUPS 12.1.1
-
VIEW: APPS.PER_PEOPLE_F 12.1.1
-
VIEW: APPS.PER_PEOPLE_F 12.2.2
-
SYNONYM: APPS.FND_USER 12.2.2
-
SYNONYM: APPS.FND_USER 12.1.1
-
eTRM - GMS Tables and Views 12.1.1
Versions of award and budget workflows. There can be many workflows for an award or budget.
-
eTRM - GMS Tables and Views 12.2.2
Versions of award and budget workflows. There can be many workflows for an award or budget.
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - GMS Tables and Views 12.1.1
Versions of award and budget workflows. There can be many workflows for an award or budget.
-
eTRM - GMS Tables and Views 12.2.2
Versions of award and budget workflows. There can be many workflows for an award or budget.
-
eTRM - PA Tables and Views 12.1.1
-
eTRM - PER Tables and Views 12.1.1
Table to store NQF Training info for a person
-
eTRM - PER Tables and Views 12.1.1
Table to store NQF Training info for a person
-
eTRM - PA Tables and Views 12.1.1