Search Results person_pk

Overview

The view EDW_HR_PERM_PERSON_LTC_IV is a BIS (Business Intelligence System) applications object delivered within Oracle E-Business Suite 12.1.1 and 12.2.2 as part of the Enterprise Data Warehouse (EDW) extract layer for Human Resources. It is an interface view (the "_IV" suffix denotes "interface view") intended to expose permitted person information from the HR source system to the EDW or to downstream integration consumers. The view is documented in ETRM 12.2.2 as "Not implemented in this database," meaning that while its definition is shipped and documented, the compiled object may not physically exist in every environment. This is characteristic of seeded EDW views, which are frequently instantiated only when the associated collection, warehouse load, or extract program is configured and run.

The view presents a flattened projection of permanent (assignment) person records combined with role-related indicator flags — including the PLANNER_FLAG, BUYER_FLAG, and SALES_REP_FLAG columns — that identify a person's functional responsibilities within Oracle purchasing, order management, and receivables respectively. Because the user's search term was "planner_flag," the view is particularly relevant to reporting on which employees are designated as planners.

Underlying Base Objects

The ETRM metadata documents no referenced base objects; the definition is a single-source SELECT with no joins. The view is defined entirely over the base table EDW_HR_PERM_PERSON_LTC. All columns exposed by the view are drawn directly from that table, plus two derived or literal columns: ROWID is aliased to ROW_ID, and a literal space character ' ' is projected as OPERATION_CODE. The absence of joins indicates that the base table already carries the denormalized person, business group, and role-flag attributes required by the extract. In practice, this base table is itself populated from HR person and assignment entities, including role assignments sourced from purchasing (planners and buyers), order management (sales representatives), and the person/party model.

Key Columns

• ROW_ID — the physical row identifier of the source record, exposed via ROWID.
• PLANNER_FLAG — indicates whether the person is designated as a planner (for example, an inventory or purchasing planner). This is the column of primary interest for the user's search.
• BUYER_FLAG — indicates whether the person acts as a buyer.
• SALES_REP_FLAG — indicates whether the person is a sales representative.
• PERSON_PK / PERSON_PK_KEY — the person primary key and its surrogate/warehouse key used for EDW dimension linkage.
• PERSON_NUM — the employee or person number.
• NAME / FULL_NAME / LAST_NAME — person naming attributes maintained for reporting and matching.
• BUSINESS_GROUP — the HR business group (legal employer context) to which the person belongs.
• START_DATE / END_DATE — the effective date range for the person record or role association.
• SYS_GEN_FLAG — indicates whether the record was system-generated.
• USER_ATTRIBUTE1..5 — descriptive flexfield segments carried through for extensibility.
• INSTANCE, ALL_FK, ALL_FK_KEY — warehouse/source instance and foreign key context columns supporting multi-instance extraction.
• CREATION_DATE / LAST_UPDATE_DATE — audit columns used for incremental or high-water-mark extraction.
• OPERATION_CODE — a literal blank placeholder, typically used by the EDW load process to denote insert/update/delete intent; here it is hard-coded to a space.

Common Use Cases and Queries

The view is typically queried to identify personnel by their functional role flags for EDW loads, data validation, or ad hoc HR reporting. A representative query to list all planners is:

• SELECT PERSON_NUM, FULL_NAME, PLANNER_FLAG, BUSINESS_GROUP FROM EDW_HR_PERM_PERSON_LTC_IV WHERE PLANNER_FLAG = 'Y';
• SELECT PERSON_PK, FULL_NAME, BUYER_FLAG, PLANNER_FLAG, SALES_REP_FLAG FROM EDW_HR_PERM_PERSON_LTC_IV WHERE PLANNER_FLAG = 'Y' OR BUYER_FLAG = 'Y';
• SELECT BUSINESS_GROUP, COUNT(*) FROM EDW_HR_PERM_PERSON_LTC_IV WHERE PLANNER_FLAG = 'Y' GROUP BY BUSINESS_GROUP;

Because the underlying table is not documented as joined to any other object, these queries execute against a single source and are well suited to bulk extract and reconciliation routines. Analysts should confirm the object's existence in their environment, given the documented "not implemented" status, and verify that the flag columns use the expected 'Y'/'N' domain before relying on them in production reports.