Search Results person_fk_key

Overview

The view EDW_HR_PERM_ASSIGN_LTC_IV is an Oracle E-Business Suite database object registered under the BIS – Applications BIS product family. Its name follows the Enterprise Data Warehouse (EDW) naming convention, indicating that it forms part of the Oracle HR analytics and data extraction layer used to expose permanent assignment data to reporting and integration consumers. The "IV" suffix denotes an interface view built on top of a "LTC" (load-to-cache/change) staging object; the view itself, EDW_HR_PERM_ASSIGN_LTC_IV, defines a stable column contract over the EDW_HR_PERM_ASSIGN_LTC source object.

Per the documented ETRM metadata, this view is not implemented in this database. It therefore does not exist as a queryable object in every 12.1.1 or 12.2.2 instance; its presence depends on whether the corresponding EDW HR extraction components have been deployed. Where it does exist, its role is to project permanent assignment attributes — including the ASSIGNMENT_DP data point referenced by user searches — into a flattened, denormalized form suitable for warehouse loading and downstream HR reporting.

Underlying Base Objects

The ETRM metadata documents no referenced base objects for this view, and no owner is recorded. The view text itself, however, shows that it is defined entirely over a single source object: EDW_HR_PERM_ASSIGN_LTC. The view is a direct projection, selecting every column of that table and appending a literal column, OPERATION_CODE, populated with a single space (' '). No joins, unions, or filter predicates appear in the definition.

Because OPERATION_CODE is a constant space character, the view is clearly a foundational feed layer: the placeholder column exists so that downstream change-detection or incremental-load processes can overwrite it with a meaningful DML indicator (INSERT, UPDATE, DELETE) when the view is used as an integration source. The base object EDW_HR_PERM_ASSIGN_LTC is not documented in the metadata, so its underlying physical tables (typically derived from PER_ALL_ASSIGNMENTS_F and related HR tables) cannot be confirmed from ETRM alone.

Key Columns

The view exposes twenty-three columns, listed as follows with their functional meaning:

• ROW_ID — The ROWID of the source row, exposed as a stable row identifier for the extraction process.
• ASSIGNMENT_DP — The assignment data point that the user searched for; the core assignment descriptor carried through the feed.
• ASSIGNMENT_PK / ASSIGNMENT_PK_KEY — Primary key of the assignment and its key representation, used for joins to assignment facts and dimensions.
• ASSIGN_NUMBER — The assignment number as held against the employee assignment.
• CREATION_DATE / LAST_UPDATE_DATE — Standard audit timestamps used for incremental extraction windows.
• GRADE — Grade of the assignment, used in compensation and workforce analytics.
• START_DATE / END_DATE — Effective dating of the assignment record, essential for date-tracked HR reporting.
• PRIMARY_FLAG — Indicates whether the assignment is the primary assignment for the person.
• PERSON_FK / PERSON_FK_KEY — Foreign key to the person and its key representation.
• NAME — Name of the person or assignment holder.
• LOCATION / BUSINESS_GROUP — Assignment location and business group context for organizational reporting.
• INSTANCE — Identifies the source EBS instance that produced the row.
• USER_ATTRIBUTE1 through USER_ATTRIBUTE5 — Descriptive flexfield segments carried through for customer-specific data.
• OPERATION_CODE — A literal space placeholder for change-tracking operations.

Common Use Cases and Queries

The primary use case is extraction of permanent assignment data into the EDW or an external data mart. Consumers typically select the full column set and apply a date-window filter on the audit columns to support incremental loads.

To extract assignments changed since a given point:

• SELECT ASSIGNMENT_DP, ASSIGNMENT_PK, ASSIGN_NUMBER, PERSON_FK, PRIMARY_FLAG, START_DATE, END_DATE, BUSINESS_GROUP FROM EDW_HR_PERM_ASSIGN_LTC_IV WHERE LAST_UPDATE_DATE >= :last_run_date;

To list current primary assignments by business group:

• SELECT NAME, ASSIGN_NUMBER, GRADE, LOCATION FROM EDW_HR_PERM_ASSIGN_LTC_IV WHERE PRIMARY_FLAG = 'Y' AND BUSINESS_GROUP = :bg AND SYSDATE BETWEEN START_DATE AND NVL(END_DATE, SYSDATE);

Because the view is a flat projection with no joins, it performs well for bulk extraction. Integrators should confirm implementation status first, as the metadata records the object as not implemented in the reference database, and should rely on OPERATION_CODE being replaced by the surrounding ETL framework rather than being read directly.