Search Results job_change_flag

Overview

The EDW_HR_ASCH_ASG_CHNG_LCV view is a reporting and extraction object owned by the APPS schema within Oracle E-Business Suite. It belongs to the HRI — Human Resources Intelligence product family, which supplies the data foundation for HR analytics and the Oracle HRMS Intelligence warehouse. The object type is a VIEW with a documented status of VALID. The LCV suffix (Loadable Column View) is characteristic of the HR Intelligence architecture, where LCV views expose a flattened, denormalized projection of a base business view for use by ETL processes and downstream analytics. This view specifically represents assignment change records — discrete events that describe how an employee assignment was modified, such as organization, job, position, grade, or geography changes. It provides a stable column contract so that HR Intelligence extracts, dashboards, and integration interfaces can query assignment-change history without depending on transactional Human Resources tables directly. The presence of columns such as ORG_CHANGE_FLAG, JOB_CHANGE_FLAG, and GRD_CHANGE_FLAG indicates the view is oriented toward change-type analysis, which is central to workforce movement and turnover reporting.

Underlying Base Objects

Per the documented view text, EDW_HR_ASCH_ASG_CHNG_LCV is defined exclusively over a single base object: EDWBV_HR_ASCH_ASG_CHNG_LCV, a business view (EDWBV prefix) in the HR Intelligence layer. The definition issued is a projection: it selects the substantive columns from the base view and appends five trailing NULL placeholders that map to USER_ATTRIBUTE1 through USER_ATTRIBUTE5 in the documented column list. This pattern reserves descriptive-flexfield slots at the top of the view contract while leaving them unpopulated in the current release. Because the mapping is a thin layer over the EDWBV object, all derivation, joins, and business logic reside in the underlying business view rather than in this LCV. The ETRM metadata documents no additional referenced base tables; the underlying transactional HR tables (assignment, organization, job, grade, position, and location history) are reached through EDWBV_HR_ASCH_ASG_CHNG_LCV and are not enumerated here.

Key Columns

• ASG_CHANGE_PK — Surrogate primary key uniquely identifying an assignment-change record.
• ALL_FK — Foreign key linking the change event to the parent assignment or person context in the HR Intelligence model.
• ASG_CHANGE_DP — Date-part (effective date) of the assignment change, used for time-series and period-over-period analysis.
• CHANGE_STATUS — Status of the change record, supporting filtering of active versus completed changes.
• ASG_CHANGE_CODE — The classification code of the assignment change; this is the column most directly relevant to the searched term asg_change_code and is the principal dimension for grouping changes by type.
• ORG_CHANGE_FLAG, JOB_CHANGE_FLAG, POS_CHANGE_FLAG, GRD_CHANGE_FLAG, GEOG_CHANGE_FLAG, OTHER_CHANGE_FLAG — Boolean-style indicators marking which attribute of the assignment was altered by the event.
• INSTANCE — Identifies the source instance or organization context of the record.
• NAME — Descriptive name associated with the change record.
• CREATION_DATE, LAST_UPDATE_DATE — Standard audit columns recording insert and modification timestamps.
• USER_ATTRIBUTE1–5 — Reserved descriptive-flexfield columns, currently projected as NULL.

Common Use Cases and Queries

Typical usage centers on assignment-change frequency, workforce movement analysis, and extraction into the HR Intelligence warehouse. The following example filters change events by code and effective date:

• SELECT asg_change_pk, all_fk, asg_change_dp, asg_change_code, change_status FROM apps.edw_hr_asch_asg_chng_lcv WHERE asg_change_code = :p_code AND asg_change_dp BETWEEN :p_from AND :p_to;
• SELECT asg_change_code, COUNT(*) FROM apps.edw_hr_asch_asg_chng_lcv GROUP BY asg_change_code ORDER BY 2 DESC;
• SELECT asg_change_dp, org_change_flag, job_change_flag, grd_change_flag FROM apps.edw_hr_asch_asg_chng_lcv WHERE all_fk = :p_assignment_fk ORDER BY asg_change_dp;

These patterns support change-code distribution reports, per-assignment change histories, and targeted ETL extracts. Because the USER_ATTRIBUTE columns are NULL, queries should treat them as unavailable descriptors in this release.