Results for “creator_user_name”

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

Overview

IC_ITEM_HIERARCHY_V is an APPS-owned database view within the Oracle E-Business Suite environment, belonging to the GMI (Process Manufacturing Inventory) product family. The view is documented as VALID in ETRM metadata for both EBS 12.1.1 and 12.2.2. Its stated function per Oracle documentation is to support the Item Activation Workflow, which manages the transition of process manufacturing items through their lifecycle states.

The view's practical purpose is to resolve the hierarchy of personnel responsible for item activation — specifically identifying which user created an item record and which user supervises that creator. Because the source data can reside in either Oracle HRMS (person/assignment records) or the Process Manufacturing item hierarchy table, the view normalizes both sources into a single two-column result set through a UNION. This abstraction allows the Item Activation Workflow to identify routing recipients without needing to know where the underlying hierarchy data originates.

Underlying Base Objects

The documented base objects referenced by IC_ITEM_HIERARCHY_V are FND_USER (synonym), GEM_LOOKUPS (view), HR_GENERAL (package), HR_SECURITY (package), IC_ITEM_HIERARCHY (synonym), and PER_ASSIGNMENTS_F (view).

The first branch of the UNION queries PER_ASSIGNMENTS_F joined twice to FND_USER — once via PERSON_ID to resolve the creator's username, and once via SUPERVISOR_ID to resolve the supervisor's username. The second branch reads IC_ITEM_HIERARCHY directly, which stores pre-resolved creator and supervisor usernames. Both branches are gated by a system mode discriminant stored in GEM_LOOKUPS: the value of MEANING for LOOKUP_TYPE='IC_ITEM_HIERARCHY' and LOOKUP_CODE='1' determines whether the HRMS branch or the OPM branch is active ('HRMS' or 'OPM' respectively). The HR_GENERAL and HR_SECURITY packages are documented dependencies, consistent with the HRMS security model used to secure person and assignment data.

Key Columns

• CREATOR_USER_NAME — The FND_USER username of the individual who created the item. In the HRMS branch this is derived from B.USER_NAME via the PER_ASSIGNMENTS_F/FND_USER join on PERSON_ID; in the OPM branch it is read directly from IC_ITEM_HIERARCHY.
• SUPERVISOR_USER_NAME — The FND_USER username of the creator's supervisor, derived from C.USER_NAME via the SUPERVISOR_ID join, or read directly from IC_ITEM_HIERARCHY in the OPM branch.

Both columns are of type VARCHAR2 and are the only projected columns. No primary key or unique constraint is documented on the view.

Common Use Cases and Queries

This view is typically consumed by workflow background processes rather than by end-user reports. A representative query returns the creator/supervisor pairs for item activation routing:

• Retrieve all hierarchy rows: SELECT creator_user_name, supervisor_user_name FROM apps.ic_item_hierarchy_v;
• Look up the supervisor for a specific creator: SELECT supervisor_user_name FROM apps.ic_item_hierarchy_v WHERE creator_user_name = :p_user;

Because the view returns data from either the HRMS or OPM source depending on the GEM_LOOKUPS discriminant, developers troubleshooting item activation issues should first verify the current value of MEANING for LOOKUP_TYPE='IC_ITEM_HIERARCHY' and LOOKUP_CODE='1'. A value of 'HRMS' indicates personnel data is sourced from PER_ASSIGNMENTS_F; 'OPM' indicates IC_ITEM_HIERARCHY is authoritative. Any custom reporting built on this view should account for both possibilities and should not assume the HRMS branch is always active.