Results for “hr_h2pi_assignments_v”

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

Overview

HR_H2PI_ASSIGNMENTS_V is an Oracle E-Business Suite view owned by the APPS schema and classified under the PER – Human Resources product family. Its name reflects its purpose: it supports the Human Resources to Payroll Interface (H2PI), the mechanism by which Oracle HR supplies assignment-level data to Oracle Payroll for processing. The view consolidates assignment records from the core HR assignment entity with soft coding key flexfield data, exposing a flattened, payroll-ready projection of assignment attributes.

The critical defining characteristic of the view is its restriction to employee assignments. A filter on the base assignment table requires the assignment type to equal 'E', meaning only employee-type assignments are surfaced. Contingent worker, applicant, and other non-employee assignment types are excluded. Because HR assignment data is date-effectively tracked, the view exposes EFFECTIVE_START_DATE and EFFECTIVE_END_DATE columns, allowing consumers to resolve the correct row for any point in time. The view is defined with an outer join to the soft coding key flexfield, so assignments lacking soft coding still appear, with null segment values. In version 12.1.1 and 12.2.2 the view remains a reporting and interface artifact rather than a transactional object; it carries no data of its own.

Underlying Base Objects

Per the ETRM metadata, the view is defined over the following documented base objects: PER_ALL_ASSIGNMENTS_F, HR_SOFT_CODING_KEYFLEX, PAY_PEOPLE_GROUPS, and PER_ASSIGNMENT_STATUS_TYPES, all accessed through synonyms in the APPS schema. The primary driver is PER_ALL_ASSIGNMENTS_F, aliased as ASG, which supplies every column except the soft coding segments. HR_SOFT_CODING_KEYFLEX, aliased as SCK, is joined via SOFT_CODING_KEYFLEX_ID using an outer join, and contributes SEGMENT1 through SEGMENT30.

PER_ALL_ASSIGNMENTS_F is the date-effective intersection table between a person and an organization, holding the assignment number, payroll, location, pay basis, and hours. HR_SOFT_CODING_KEYFLEX holds the flexfield combinations used for cost allocation and payroll distribution. PAY_PEOPLE_GROUPS and PER_ASSIGNMENT_STATUS_TYPES appear as referenced objects and are typically used within the HR-to-Payroll interface logic to resolve payroll grouping and assignment status, though they are not projected in the excerpted view text. The view text is explicitly documented as a join of PER_ALL_ASSIGNMENTS_F and HR_SOFT_CODING_KEYFLEX.

Key Columns

• ASSIGNMENT_ID, PERSON_ID, BUSINESS_GROUP_ID – Primary identifiers linking the assignment to its person and to the business group.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE – Date-effective boundaries enabling as-of-date reporting.
• ASSIGNMENT_NUMBER, PRIMARY_FLAG, TITLE – Descriptive assignment attributes.
• PAYROLL_ID, PAY_BASIS_ID, LOCATION_ID, ORGANIZATION_ID – Payroll, pay basis, and organizational context used by the payroll interface.
• FREQUENCY, NORMAL_HOURS, HOURLY_SALARIED_CODE – Working-time and compensation-basis attributes.
• TIME_NORMAL_START / TIME_NORMAL_FINISH – Standard working times.
• EMPLOYMENT_CATEGORY – Classification of the employment relationship.
• SEGMENT1 … SEGMENT30 – Soft coding key flexfield segments for cost allocation.
• ASS_ATTRIBUTE_CATEGORY and ASS_ATTRIBUTE1 … ASS_ATTRIBUTE30 – Descriptive flexfield context and values on the assignment.

Common Use Cases and Queries

The view is typically queried to extract employee assignments for payroll validation, soft coding verification, or data migration checks. A common pattern resolves the current active row:

• SELECT assignment_id, person_id, assignment_number, organization_id, payroll_id FROM hr_h2pi_assignments_v WHERE sysdate BETWEEN effective_start_date AND effective_end_date;
• SELECT assignment_id, segment1, segment2, segment3 FROM hr_h2pi_assignments_v WHERE segment1 IS NULL; — identifies assignments missing soft coding.

Because the view returns date-effective rows, consumers must always constrain on the effective dates unless the full history is required.