Results for “ben_assignment_extra_in_v”

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

Overview

BEN_ASSIGNMENT_EXTRA_IN_V is a seeded Oracle E-Business Suite database view owned by the APPS schema and shipped as part of the BEN (Advanced Benefits) product. It is a denormalized reporting construct that joins assignment-level records from Oracle Human Resources to the assignment extra information records consumed by Advanced Benefits processing. In the ETRM catalog for release 12.2.2 the object is registered with a status of VALID and is classified as a VIEW, indicating that it carries no independent storage and derives all of its content at runtime from its underlying base objects.

The view serves a specific integration purpose: Advanced Benefits frequently requires attributes that are not native to the PER_ALL_ASSIGNMENTS_F row itself, such as user-defined extra information captured against an assignment. Rather than requiring callers to re-implement the join, BEN_ASSIGNMENT_EXTRA_IN_V exposes the combined result set so that concurrent programs, Fast Formulas, OAF pages, and customer-written reports can retrieve assignment context and its associated extra information in a single query. The naming convention reflects this intent, with the "EXTRA_IN" segment denoting extra information and the "_V" suffix confirming the object type.

The search term "aei_information12" corresponds to the assignment extra information area of the data model, and this view is the canonical access point for that data when it must be evaluated alongside core assignment attributes.

Underlying Base Objects

The documented base objects referenced by this view are:

• PER_ALL_ASSIGNMENTS_F (SYNONYM) — the effective-dated assignment entity in Oracle HRMS, aliased as ASG in the view text.
• PER_ASSIGNMENT_EXTRA_INFO (SYNONYM) — the extra information table holding assignment-level descriptive flexfield style attributes, aliased as AEI.
• FND_SESSIONS (SYNONYM) — the Applications session table, typically used to enforce session-scoped or security-related filtering.

Because the view is defined over synonymous references rather than directly over the physical tables, it resolves through the APPS synonyms to the underlying HR and FND objects. The join is anchored on ASSIGNMENT_ID, with the assignment row supplying the driving key and PER_ASSIGNMENT_EXTRA_INFO supplying the supplemental attribute rows.

Key Columns

The projection is broad and mirrors the PER_ALL_ASSIGNMENTS_F column set, prefixed by the ASG alias. Notable columns include:

• ROW_ID — the ROWID of the assignment row, useful for direct row addressing and for optimistic locking patterns.
• ASSIGNMENT_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE — the primary key and date-track columns that define the effective-dated assignment record.
• PERSON_ID, PRIMARY_FLAG, ASSIGNMENT_NUMBER, ASSIGNMENT_SEQUENCE, ASSIGNMENT_TYPE — identify the worker and the role of the assignment.
• BUSINESS_GROUP_ID, ORGANIZATION_ID, LOCATION_ID, GRADE_ID, JOB_ID, POSITION_ID, PAYROLL_ID, SUPERVISOR_ID — the organizational and compensation context of the assignment.
• ASS_ATTRIBUTE_CATEGORY and ASS_ATTRIBUTE1 through ASS_ATTRIBUTE30 — the assignment descriptive flexfield segments, which are frequently the target of downstream reporting.
• ASSIGNMENT_EXTRA_INFO_ID — sourced from the AEI alias and carries the extra information record identifier.

Additional columns in the listing include HR-specific attributes such as NORMAL_HOURS, FREQUENCY, PROBATION_PERIOD, SAL_REVIEW_PERIOD, BARGAINING_UNIT_CODE, and HOURLY_SALARIED_CODE.

Common Use Cases and Queries

Typical scenarios include benefits eligibility reporting, extra information audits, and integration extracts that must combine assignment context with benefit-relevant extra attributes.

• Listing active assignments with their extra information identifier for a business group.
• Extracting effective-dated assignment attributes for a specific person across a date range.
• Reconciling extra information records against populated descriptive flexfield attributes.

A representative query is:

SELECT assignment_id, assignment_number, person_id, effective_start_date, effective_end_date, assignment_extra_info_id FROM ben_assignment_extra_in_v WHERE business_group_id = :p_bg_id AND TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date AND primary_flag = 'Y';

Because the view is join-based, it should be filtered on effective dates and business group to avoid returning broad result sets, and it should be treated as read-only in all customer extensions.