Results for “orig_enc_txn_reference1”

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

Overview

GMS_ENCUMBRANCES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the GMS – Grants Accounting product. It presents encumbrance records held in GMS_ENCUMBRANCES together with descriptive attributes resolved from human resources and organization tables, so that the numeric identifiers stored on the transaction are displayed as recognizable names and numbers. The view exposes one row per encumbrance record in GMS_ENCUMBRANCES (identified by ENCUMBRANCE_ID), denormalizing the incurred-by person and organization context onto each row.

The view is primarily consumed by Grants Accounting inquiry, reporting, and integration components that need to display or extract encumbrance header information without writing their own joins to PER_PEOPLE_F and HR_ORGANIZATION_UNITS. Because it resolves the current effective person record, it is suited to operational reporting rather than to historical point-in-time reconstruction.

Underlying Base Objects

The view is defined over the following documented base objects:

• GMS_ENCUMBRANCES (SYNONYM) — the driving table, supplying the encumbrance columns (aliased E).
• PER_PEOPLE_F (VIEW) — the effective-dated person view, aliased P, joined on E.INCURRED_BY_PERSON_ID = P.PERSON_ID (+) and restricted by TRUNC(SYSDATE) BETWEEN P.EFFECTIVE_START_DATE (+) AND P.EFFECTIVE_END_DATE (+), so only the currently effective person row is joined.
• HR_ORGANIZATION_UNITS (VIEW) — aliased O, joined on E.INCURRED_BY_ORGANIZATION_ID = O.ORGANIZATION_ID to supply ORGANIZATION_NAME.
• HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY (PACKAGEs) — referenced as supporting packaged logic/security used by the HR views underlying this definition.

Note the outer join (+) on the person side, which permits encumbrances to be returned where the incurred-by person is null or has no effective record; the organization join is an inner join. The commented-out predicate /* 3362016 AND P.EMPLOYEE_NUMBER (+) IS NOT NULL */ indicates that a former filter requiring an employee number was deliberately disabled, which is directly relevant to the incurred_by_employee_number attribute.

Key Columns

• ROW_ID, ENCUMBRANCE_ID — row identifier and the primary key of the encumbrance.
• INCURRED_BY_PERSON_ID — the person identifier stored on the encumbrance.
• INCURRED_BY_EMPLOYEE_NAME — derived from P.FULL_NAME.
• INCURRED_BY_EMPLOYEE_NUMBER — derived as NVL(P.EMPLOYEE_NUMBER, P.NPW_NUMBER), so non-employee (contingent worker) records return the NPW number instead of a null employee number.
• INCURRED_BY_ORGANIZATION_ID, ORGANIZATION_NAME — the incurring organization and its description.
• ENCUMBRANCE_STATUS_CODE, ENCUMBRANCE_CLASS_CODE, ENCUMBRANCE_ENDING_DATE, ENCUMBRANCE_GROUP — status, class, expiry, and grouping attributes.
• CONTROL_TOTAL_AMOUNT — the controlled total amount for the encumbrance.
• DENOM_CURRENCY_CODE, ACCT_CURRENCY_CODE, ACCT_RATE_DATE, ACCT_RATE_TYPE, ACCT_EXCHANGE_RATE — currency conversion and accounting currency context.
• ENTERED_BY_PERSON_ID, DESCRIPTION, INITIAL_SUBMISSION_DATE, WF_STATUS_CODE, TRANSFER_STATUS_CODE, OVERRIDING_APPROVER_PERSON_ID, USER_BATCH_NAME, ORG_ID — workflow, transfer, and audit attributes.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE10 — descriptive flexfield columns.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical usage includes encumbrance inquiry by employee, reconciliation of encumbrances to funding, and extracts that require the employee number as a display or matching key.

• Retrieve encumbrances incurred by a given employee number:

SELECT encumbrance_id, incurred_by_employee_number, incurred_by_employee_name, control_total_amount, encumbrance_status_code FROM apps.gms_encumbrances_v WHERE incurred_by_employee_number = :employee_number;

• List open encumbrances with their incurring organization:

SELECT encumbrance_id, organization_name, encumbrance_ending_date, control_total_amount FROM apps.gms_encumbrances_v WHERE encumbrance_status_code = 'OPEN' ORDER BY encumbrance_ending_date;

• Since INCURRED_BY_EMPLOYEE_NUMBER is computed as NVL(EMPLOYEE_NUMBER, NPW_NUMBER) and the old employee-number filter is commented out, rows may return an NPW value or a null; queries matching on this column should account for both cases.
• The effective-dated person join uses SYSDATE, so results reflect current person data rather than the person attributes in effect when the encumbrance was created.