Results for “salary_basis”

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

Overview

The BEN_ASSIGNMENT_D view is a denormalized, read-only reporting object owned by the APPS schema within the Oracle E-Business Suite Advanced Benefits (BEN) product family. It exposes assignment-level information drawn primarily from Oracle Human Resources (PER) and Oracle Payroll (PAY) base objects, joined to benefits-relevant lookups and organizational attributes. The "_D" suffix conventionally denotes a view created for descriptive or display purposes, and this object functions as a convenience layer that assembles assignment, people, payroll, job, position, grade, location, organization, and lookup descriptions into a single flattened result set.

Given that the user searched for the term salary_basis, the pivotal column in this view is BASIS.NAME, sourced from PER_PAY_BASES via the PAY_BASIS_ID foreign key on the assignment. This column exposes the pay basis (salary basis) associated with the assignment, which is fundamental in benefits eligibility determination, compensation reporting, and payroll-benefits reconciliation. The view thereby supports benefits administrators and technical consultants who need to report on assignments together with their salary basis without traversing the underlying HR schema directly.

Underlying Base Objects

The view is defined as an outer-join-heavy SELECT across the following documented base objects, all referenced through APPS synonyms or views:

• PER_ASSIGNMENTS_F (VIEW) — the driving table, supplying assignment id, effective dates, hours, times, and foreign keys.
• PER_ALL_PEOPLE_F (SYNONYM) — joined on PERSON_ID to constrain assignment effective dating to the person record.
• PER_PAY_BASES (SYNONYM) — outer-joined on PAY_BASIS_ID, supplying the pay/salary basis name.
• PER_GRADES_VL, PER_JOBS_VL, PER_POSITIONS (VIEWS) — grade, job, and position descriptions.
• PAY_ALL_PAYROLLS_F and PAY_PEOPLE_GROUPS (SYNONYMS) — payroll and people group names.
• HR_LOCATIONS, HR_ALL_ORGANIZATION_UNITS_VL, HR_LOOKUPS (VIEWS) — location, organization, and four lookup meanings.
• FND_USER (SYNONYM) — the user name of the last updater.
• Supporting packages HR_API, HR_GENERAL, HR_SECURITY — referenced for security and utility functions underlying the view family.

Key Columns

• ASSIGNMENT_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE — assignment identity and date-tracked validity.
• BASIS.NAME — the salary basis name derived from PER_PAY_BASES.
• HR1.MEANING (FREQUENCY), HR2.MEANING (HOURLY_SALARIED_CODE) — lookup meanings for frequency and hourly/salaried classification.
• HR3.MEANING (EMP_CAT), HR4.MEANING (BARGAINING_UNIT_CODE) — employment category and bargaining unit descriptions.
• NORMAL_HOURS, TIME_NORMAL_START, TIME_NORMAL_FINISH — standard working attributes.
• LOCATION_CODE, ORGTL.NAME, GROUP_NAME, JOB.NAME, POS.NAME, GRADE.NAME, PAYROLL_NAME — descriptive organizational context.
• LABOUR_UNION_MEMBER_FLAG, LAST_UPDATE_DATE, FUSER.USER_NAME — union flag and audit information.

Common Use Cases and Queries

A primary scenario is validating which salary basis each employee assignment carries, especially when benefits plan eligibility depends on compensation structure.

SELECT assignment_id,
       basis_name,
       hourly_salaried_meaning,
       frequency_meaning
FROM   apps.ben_assignment_d
WHERE  basis_name = '&salary_basis';

Consultants also use this view to reconcile assignments to their personnel groups and payrolls, or to audit changes by last updater. Because the view applies HR security through the underlying HR packages, results remain subject to the standard security profile of the querying user.