Results for “employee_vendor_name”

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

Overview

GMS_EXPEND_ITEMS_ADJUST_V is a Grants Accounting (GMS) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents expenditure item and cost distribution detail in a denormalized form, joining award distribution lines, project and task attributes, expenditure classifications, employee and vendor identifiers, and organization hierarchies. The view is typically used by grants administrators, project accountants, and interfaces that must reconcile or adjust expenditure items at the distribution level without traversing the full PA and GMS base table set.

The view is particularly relevant to the EMPLOYEE_VENDOR_NUMBER column, which resolves the payee of an expenditure item to a single identifier regardless of whether the cost originated as labor (employee) or non-labor (vendor). This is a common search term because reconciliation, subledger transfer, and third-party reporting frequently require a unified payee reference.

Underlying Base Objects

The view is defined over the PA and GMS transactional and reference tables. The principal base objects documented in ETRM 12.2.2 are:

• GMS_AWARD_DISTRIBUTIONS — award distribution lines supplying ADL_LINE_NUM and distribution percentage.
• PA_EXPENDITURE_ITEMS_ALL and PA_EXPENDITURES_ALL — expenditure item and expenditure header detail (EI and X aliases).
• PA_COST_DIST_LINES_ALL_BAS — raw cost and burdened cost distribution amounts (ADL alias).
• PA_PROJECTS, PA_TASKS, PA_PROJECT_TYPES_ALL, PA_EXPENDITURE_TYPES, PA_SYSTEM_LINKAGES, PA_TRANSACTION_SOURCES, PA_EXPENDITURE_COMMENTS — project, task, type, and comment attributes.
• PER_PEOPLE_F, PER_JOBS, PO_VENDORS — payee identity via HR_PERSON_NAME, employee number, job name, and vendor number/name.
• HR_ALL_ORGANIZATION_UNITS_TL and FND_LOOKUP_VALUES — organization names and lookup meanings (project class, unit of measure, expenditure status, system linkage).
• PL/SQL packages HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY, which enforce person-name resolution and row-level security.

The view is anchored by a hint (INDEX(ADL GMS_ADL_UK)) to drive the award distribution join efficiently, and only exposes rows where distribution values and expenditure items align.

Key Columns

• EXPENDITURE_ITEM_ID / EXPENDITURE_ID — the primary link to the underlying expenditure records.
• PROJECT_ID, PROJECT_NUMBER, PROJECT_NAME — project context, with PROJECT_CLASS and PROJECT_TYPE derived from lookups and project types.
• TASK_ID, TASK_NUMBER, TASK_NAME — the task on which the expenditure was incurred.
• EMPLOYEE_NAME, EMPLOYEE_NUMBER — from PER_PEOPLE_F where an employee incurred the cost.
• VENDOR_NUMBER, VENDOR_NAME — from PO_VENDORS for non-labor or third-party costs.
• EMPLOYEE_VENDOR_NAME, EMPLOYEE_VENDOR_NUMBER — the NVL-combined payee columns: employee name/number if present, otherwise vendor name/number.
• EXPENDITURE_ORGANIZATION_ID / NAME — resolved as NVL(OVERRIDE_TO_ORGANIZATION_ID, INCURRED_BY_ORGANIZATION_ID).
• RAW_COST, BURDENED_COST, BURDENED_COST_RATE — costs prorated by distribution percentage.
• EXPENDITURE_STATUS_M, UNIT_OF_MEASURE_M, SYSTEM_LINKAGE_M — lookup meanings for status, UOM, and system linkage.

Common Use Cases and Queries

The view supports reconciliation of award distributions to expenditure items, payee-level analysis, and extracts for third-party reporting. A typical query filtering on the searched column would be:

• SELECT PROJECT_NUMBER, EXPENDITURE_ITEM_ID, EMPLOYEE_VENDOR_NUMBER, EMPLOYEE_VENDOR_NAME, RAW_COST, BURDENED_COST FROM GMS_EXPEND_ITEMS_ADJUST_V WHERE EMPLOYEE_VENDOR_NUMBER = :payee AND EXPENDITURE_ITEM_DATE BETWEEN :start AND :end;

Other practical scenarios include aggregating burdened cost by expenditure organization, validating that award distribution percentages total 100, and identifying unmatched payees where both employee and vendor columns are null. Because the view references HR_SECURITY, results are subject to the operating unit and security profile of the executing user, which must be considered when scheduling concurrent extracts.