Results for “bargaining_unit_code_meaning”

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

Overview

PER_ASSIGNMENTS_V is an APPS-owned database view within the Oracle E-Business Suite Human Resources (PER) product family. It holds the status VALID in ETRM for release 12.2.2 and carries the same identity in 12.1.1, where it is likewise supplied by the PER module. The documented description states that the view is "used to support user interface," meaning Oracle seeded it primarily to feed HRMS forms, self-service pages, and concurrent programs rather than as a formally published integration interface. In practice, however, the view is widely queried for reporting because it converts foreign-key identifiers into human-readable names in a single SELECT.

The view denormalizes the core assignment record against grades, jobs, positions, payrolls, locations, supervisors, organizations, comments, and status types. It also derives decode columns such as CHANGE_REASON_MEANING, FREQUENCY_MEANING, PROBATION_UNIT_MEANING, and BARGAINING_UNIT_CODE_MEANING, applying HR_GENERAL.DECODE_LOOKUP and HR_GENERAL.DECODE_POSITION_LATEST_NAME so that callers avoid extra lookup joins.

Underlying Base Objects

The principal driving object is PER_ALL_ASSIGNMENTS_F, the date-tracked assignment table, referenced in the view text as alias PA. Person attributes come from PER_ALL_PEOPLE_F. Name resolution relies on PER_GRADES / PER_GRADES_TL, PER_JOBS / PER_JOBS_TL, HR_ALL_ORGANIZATION_UNITS and its _TL table, HR_LOCATIONS_ALL_TL, and PAY_ALL_PAYROLLS_F.

Status presentation is built from PER_ASSIGNMENT_STATUS_TYPES, PER_ASSIGNMENT_STATUS_TYPES_TL, PER_ASS_STATUS_TYPE_AMENDS, and PER_ASS_STATUS_TYPE_AMENDS_TL, using NVL logic to prefer user-defined status amendments over the seeded status type. Supporting tables include HR_COMMENTS, PER_SPINAL_POINTS, PER_SPINAL_POINT_STEPS_F, PER_COLLECTIVE_AGREEMENTS, PER_CONTRACTS_F, and PER_PAY_BASES. The package HR_GENERAL supplies the decode functions, while FND_GLOBAL and FND_SESSIONS contribute session context. Purchasing views such as PO_VENDORS, PO_VENDOR_SITES_ALL, PO_HEADERS_ALL, and PO_LINES_ALL appear in the reference list, reflecting the sourcing and contingent-worker extensions that were folded into later releases.

Key Columns

• ASSIGNMENT_ID, ASSIGNMENT_NUMBER, ASSIGNMENT_SEQUENCE, PRIMARY_FLAG — assignment identity and whether it is the person's primary assignment.
• PERSON_ID, BUSINESS_GROUP_ID, ORGANIZATION_ID / ORGANIZATION_NAME — party, operating unit, and organization context.
• EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, D_EFFECTIVE_END_DATE — date-tracked validity; the D_ variant nulls the 4712/12/31 end date for presentation.
• GRADE_ID / GRADE_NAME, JOB_ID / JOB_NAME, POSITION_ID / POSITION_NAME — assignment attributes with decoded names.
• SUPERVISOR_ID, SUPERVISOR_NAME, SUPERVISOR_EMPLOYEE_NUMBER — supervisor chain, with NPW_NUMBER fallback for non-payroll workers.
• ASSIGNMENT_STATUS_TYPE_ID, USER_STATUS, PER_SYSTEM_STATUS — decoupled status display.
• PAYROLL_ID / PAYROLL_NAME, LOCATION_ID / LOCATION_CODE, NORMAL_HOURS, FREQUENCY / FREQUENCY_MEANING — compensation and scheduling attributes.

Common Use Cases and Queries

Typical scenarios include headcount and establishment reporting, supervisor hierarchy listings, and status audits. Because the view is not date-tracked itself in the usual sense, callers must constrain effective dates explicitly.

• Current primary assignments with manager and location detail.
• Assignment status reconciliation against PER_SYSTEM_STATUS.
• Grade and job distribution across organizations for HR analytics.

SELECT assignment_id, assignment_number, person_id,
       job_name, grade_name, organization_name,
       supervisor_name, user_status
  FROM apps.per_assignments_v
 WHERE TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date
   AND primary_flag = 'Y'
   AND business_group_id = :p_bg_id;