Search Results create_usr

Overview

APPS.PAYFV_ELEMENT_ENTRIES is a reporting view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 Payroll (PAY) module. It presents a denormalized, human-readable projection of payroll element entries assigned to employee assignments, resolving internal numeric identifiers into descriptive names through joins to the underlying element, input value, person, and organization tables. The view exposes business group, person, element, input value, and assignment context alongside audit columns, allowing report developers and integration specialists to query payroll element entries without manually decoding foreign keys.

The suffix "FV" denotes a business-intelligence-friendly view used primarily by Oracle Payroll reporting and the Payroll Archive and Reporting (PAR) toolset. It is not intended for transactional data entry; it provides a read-only presentation layer that surfaces the effective-dated element entry rows and their associated input values.

Underlying Base Objects

The view is defined over the following documented base objects, most resolved through APPS synonyms:

• PAY_ELEMENT_ENTRIES_F — the driving table, providing the element entry header rows, entry type, and effective start/end dates.
• PAY_ELEMENT_ENTRY_VALUES_F — the input value rows (screen entry values) associated with each element entry.
• PAY_INPUT_VALUES_F and PAY_INPUT_VALUES_F_TL — the input value definitions and their translated names.
• PAY_ELEMENT_LINKS_F and PAY_ELEMENT_TYPES_F with PAY_ELEMENT_TYPES_F_TL — element link and element type information with translated element names.
• PER_ASSIGNMENTS_F and PER_PEOPLE_F — assignment and person records, supplying job, position, grade, location, pay basis, payroll, and organization context.
• HR_ALL_ORGANIZATION_UNITS_TL — used twice, for business group name and organization name translations.
• FND_USER — joined twice to resolve creation and last-update user identifiers into user names.
• HR_GENERAL, HR_PERSON_NAME, HR_SECURITY — packages used for lookups and secure data retrieval.
• PAY_PAYFV_ELEMENT_ENTRIES_PKG — provides the DECODE-driven helper functions that resolve assignment attributes such as job, position, grade, location, pay basis, and payroll.

Each of these objects is referenced by synonym from the APPS schema, consistent with the standard EBS view architecture.

Key Columns

The view exposes a broad set of identifiers, descriptive names, and audit fields:

• business_group_name, person_name, organization_name — organizational and employee context.
• element, entry_type, input_value, unit_of_measure, entry_value — payroll element detail and the specific input value entered.
• job_name, position_name, grade_name, location_name, pay_basis, payroll_name — derived assignment attributes resolved via the PAYFV_ELEMENT_ENTRIES_PKG helper functions.
• effective_start_date, effective_end_date — date-effective validity of the element entry.
• assignment_id, business_group_id, person_id, element_entry_id, element_entry_value_id, element_link_id, element_type_id, organization_id — primary and foreign key identifiers for joining to other entities.
• creation_date, create_usr.user_name, last_update_date, update_usr.user_name — audit trail columns. The alias create_usr is the join to FND_USER that resolves the creation user name; this is the column referenced when searching for create_usr.

Common Use Cases and Queries

This view is typically used for payroll auditing, element entry reconciliation, and integration extracts. The join to FND_USER via the create_usr alias allows analysts to trace which user created a given element entry, which is a common audit requirement.

Representative query:

• SELECT person_name, element, input_value, entry_value, effective_start_date, create_usr.user_name FROM apps.payfv_element_entries WHERE person_id = :p_person_id ORDER BY effective_start_date;
• SELECT business_group_name, person_name, element, entry_type, create_usr.user_name FROM apps.payfv_element_entries WHERE create_usr.user_name = :p_user;
• SELECT person_name, element, entry_value, creation_date FROM apps.payfv_element_entries WHERE TRUNC(creation_date) BETWEEN :p_from AND :p_to;

Because the view resolves translated names using USERENV('LANG'), results respect the session language. Queries should account for the effective-dated nature of the underlying datetracked tables by filtering on effective_start_date and effective_end_date.