Search Results name_prefix

Overview

EDW_HR_PERM_ASSIGN_LCV is a read-only view owned by the APPS schema in Oracle E-Business Suite, classified under product HRI (Human Resources Intelligence). The suffix "LCV" denotes a "lite current view" construct used within the Oracle HRMS Intelligence / Data Warehouse layer. Its role is to expose person and assignment information in a flattened, denormalized form suitable for reporting, extracts, and downstream integration with the Enterprise Data Warehouse (EDW). The view presents a single row per permanent assignment record, combining assignment-level identifiers with person-level demographic and descriptive attributes. Because it is a view rather than a base table, it holds no data of its own and inherits all data from its underlying source view, EDWBV_HR_PERM_ASSIGN_LCV, which is part of the seeded HRMS business view layer.

The view is registered as VALID in the ETRM metadata for both release 12.1.1 and 12.2.2, and the documented column set is identical across both releases, which supports consistent reporting code across upgrade projects.

Underlying Base Objects

The documented view text shows a direct one-to-one projection from EDWBV_HR_PERM_ASSIGN_LCV. No physical base tables are documented for EDW_HR_PERM_ASSIGN_LCV itself in the ETRM record. In practice, EDWBV_HR_PERM_ASSIGN_LCV is a seeded business view that in turn resolves to the core PER_ALL_ASSIGNMENTS_F and PER_ALL_PEOPLE_F tables plus the associated date-tracked person and assignment structures. The "LCV" wrapper therefore sits three levels deep: the physical HR tables, the seeded EDW business view, and this public APPS synonym-like view. This layering allows Oracle to change the internal projections without altering the interface consumed by customers and third-party tools.

Notably, the view text appends five NULL placeholders after LAST_UPDATE_DATE, which correspond to the USER_ATTRIBUTE1 through USER_ATTRIBUTE5 columns listed in the column definitions. These placeholder columns preserve column-count parity with related views in the HRI family.

Key Columns

• ASSIGNMENT_PK / PERSON_ID / GLOBAL_PERSON_ID: Primary and person-level identifiers used to join to other EDW views and to HRMS tables.
• ALL_FK / SPRVSR_LVL1_FK: Foreign-key style references used in the EDW star schema for the assignment and first-level supervisor dimensions.
• NAME, FULL_NAME, LAST_NAME, FIRST_NAME, MIDDLE_NAMES: Components of the person's name, with FULL_NAME providing a concatenated display value.
• NAME_SUFFIX: The suffix element of the person's name, such as Jr., Sr., II, or III. It is stored separately from the name components and is used where formal name rendering is required.
• NAME_PREFIX: The prefix element of the name, such as Mr., Ms., or Dr.
• PREVIOUS_LAST_NAME and KNOWN_AS: Alternate name values for matching and reporting on name changes.
• START_DATE / END_DATE / EFFECTIVE_START_DATE / EFFECTIVE_END_DATE: Assignment and date-tracked effective dating columns.
• EMPLOYEE_FLAG / APPLICANT_FLAG / OTHER ROLE FLAGS: Boolean indicators distinguishing person types.
• BUSINESS_GROUP and ORGANIZATION_ID: The HR business group and organization context, critical for multi-organization security.
• EMAIL_ADDRESS, TITLE, GENDER, DATE_OF_BIRTH, NATIONALITY, NATIONAL_IDENTIFIER: Demographic attributes exposed for analysis.

Common Use Cases and Queries

This view is typically queried by BI Publisher, Discoverer, OBIEE, or custom PL/SQL extract programs that require person and assignment data without navigating HRMS date-tracked logic manually. A common requirement, and the one that motivated the search for NAME_SUFFIX, is producing a formatted person name or filtering on individuals with a specific suffix.

Selecting suffix and name components:

SELECT person_id,
       full_name,
       last_name,
       name_suffix,
       name_prefix
FROM   apps.edw_hr_perm_assign_lcv
WHERE  name_suffix IS NOT NULL;

Filtering current employees within a business group:

SELECT assignment_pk,
       person_num,
       full_name,
       name_suffix,
       organization_id
FROM   apps.edw_hr_perm_assign_lcv
WHERE  employee_flag = 'Y'
AND    business_group IS NOT NULL
AND    SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE);

Because no indexes exist on a view, performance depends entirely on the underlying HRMS tables and the effective date predicates supplied. Queries should always constrain on business_group, effective dates, or person identifiers to avoid full scans of the date-tracked person and assignment data. Output is often fed into EDW staging tables or customer-facing headcount, directory, and compliance reports.