Results for “cur_apl_flag”

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

Overview

PER_ASSIGNMENTS_V3 is a valid APPS-owned view within the Oracle E-Business Suite Human Resources (PER) product module. It is documented in ETRM for both 12.1.1 and 12.2.2 with the concise description "Used to support user interface." Its purpose is therefore not to serve as an integration or open-interface object in its own right, but to present a flattened, user-facing projection of assignment, person, and period-of-service data that the HR forms and OAF-based pages consume. The view name carries the "V3" suffix, indicating it is the third iteration in the PER_ASSIGNMENTS_Vn family, each successive version adding joins or derived columns required by evolving UI screens.

Because the view is a UI support construct, it is not part of the documented public API surface of Oracle HRMS. The columns are exposed for display, and the view is not registered as a multitenant-aware or row-level-secured replacement for the underlying PER_ALL_ASSIGNMENTS_F table. Consultants using it for reporting must account for this and prefer the base tables where a supported, upgrade-stable interface is required.

The view is significant in the context of the search term last_flag because it does not itself expose a LAST_FLAG column. The view text exposes LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN, but the effective-dating "current record" indicator resides in the underlying date-tracked tables, not in this projection. Users looking for LAST_FLAG must query PER_ALL_ASSIGNMENTS_F or PER_PEOPLE_F directly.

Underlying Base Objects

The documented referenced objects reveal a fan-out join pattern. The primary driver is PER_ALL_ASSIGNMENTS_F (SYNONYM), with PER_ASSIGNMENTS_F2 (VIEW) also participating, joining to PER_PEOPLE_F (VIEW) and PER_PERIODS_OF_SERVICE via PERSON_ID and PERIOD_OF_SERVICE_ID. Descriptive lookups are resolved through PER_JOBS, PER_JOBS_TL, PER_PERSON_TYPES, PER_PERSON_TYPES_TL, PER_ASSIGNMENT_STATUS_TYPES, PER_ASSIGNMENT_STATUS_TYPES_TL, PER_ANALYSIS_CRITERIA, and PER_PERSON_ANALYSES. Organization context comes from HR_ALL_ORGANIZATION_UNITS and its _TL table. Flexfield structure metadata is retrieved from FND_ID_FLEX_STRUCTURES, and session context from FND_SESSIONS. A vendor reference is present through PO_VENDORS (VIEW). Business logic and name formatting are delegated to PL/SQL packages: HR_GENERAL, HR_PERSON_NAME, HR_PERSON_TYPE_USAGE_INFO, and HR_SECURITY. HR_SECURITY is notable, as it implies the view may apply security predicates rather than returning raw rows.

Key Columns

• ROW_ID, ASSIGNMENT_ID, PERSON_ID, PERIOD_OF_SERVICE_ID — identifiers linking the assignment to the person and period of service.
• BUSINESS_GROUP_ID, ORGANIZATION_ID, JOB_ID, POSITION_ID, GRADE_ID, LOCATION_ID, PAYROLL_ID — organizational and compensation context.
• ASSIGNMENT_NUMBER, ASSIGNMENT_SEQUENCE, ASSIGNMENT_TYPE, ASSIGNMENT_STATUS_TYPE_ID — assignment identification and status classification.
• EFFECTIVE_START_DATE, EFFECTIVE_END_DATE — date-tracked validity range inherited from the _F table.
• ASS_ATTRIBUTE1 through ASS_ATTRIBUTE30, ASS_ATTRIBUTE_CATEGORY — the assignment descriptive flexfield, exposed in full.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard audit columns.
• PAY_BASIS, MARITAL_STATUS, NATIONALITY, SEX — decoded via HR_GENERAL.DECODE_PAY_BASIS and DECODE_LOOKUP.
• FIRST_NAME, LAST_NAME, FULL_NAME, KNOWN_AS, EMAIL_ADDRESS, APPLICANT_NUMBER, WORK_TELEPHONE — person identity attributes.
• CUR_EMP_FLAG / CUR_APL_FLAG — current employee and applicant indicators.

Common Use Cases and Queries

The view is most useful for reproducing UI-style assignment listings. A typical query retrieves current assignments for a person:

SELECT assignment_id, assignment_number, effective_start_date, effective_end_date, job_id, organization_id, assignment_status_type_id FROM apps.per_assignments_v3 WHERE person_id = :p_person_id ORDER BY effective_start_date;

Because the view does not expose LAST_FLAG, users seeking the effective-dated current row must join or query the base table: SELECT assignment_id, primary_flag, effective_start_date FROM apps.per_all_assignments_f WHERE person_id = :p_person_id AND effective_end_date = hr_general.get_max_end_date AND trunc(sysdate) BETWEEN effective_start_date AND effective_end_date;

Security-sensitive queries should account for HR_SECURITY predicates embedded in the view, and any production code should be validated against the base PER_ALL_ASSIGNMENTS_F interface, since the "user interface support" designation does not guarantee backward compatibility.