Search Results default_start_time




Overview

ICX_PER_ORGANIZATION_UNITS_V is a view owned by the APPS schema within Oracle E-Business Suite, catalogued under the ICX (Oracle iProcurement) product family. The ETRM documentation classifies this object with a status of VALID and an object description of Obsolete. This designation indicates that the view remains present and compilable in the database — it is not invalidated or dropped — but Oracle no longer positions it as a supported integration or customization surface for iProcurement functionality. In practice, organizations running EBS 12.1.1 or 12.2.2 may still encounter the view in legacy customizations, reports, or BI Publisher data models that predate its retirement.

The view is a thin projection over the organization units data used by Oracle HRMS. It passes through organization unit records rather than transforming them, which means it behaves as a convenience alias for consumers that need organization unit information without querying the HRMS base view directly. Because the object is marked obsolete, any new development should treat it as read-only legacy infrastructure.

Underlying Base Objects

The documented base objects for this view are PER_ORGANIZATION_UNITS, HR_GENERAL, and HR_SECURITY. The view text is a straightforward SELECT that lists all columns from PER_ORGANIZATION_UNITS without joins, filters, or expressions. PER_ORGANIZATION_UNITS is itself a view rather than a physical table, and it is that view — not a stored table — that supplies every column exposed here.

The inclusion of HR_GENERAL and HR_SECURITY in the metadata reflects the dependency chain: PER_ORGANIZATION_UNITS resolves organization unit rows and applies HR security predicates through the HR_SECURITY package, while HR_GENERAL provides general HR utility functions and business group context resolution. Row-level access is therefore governed by HR security profiles attached to the querying user, not by logic inside ICX_PER_ORGANIZATION_UNITS_V itself. There is no iProcurement-specific filtering, so results are bounded by the HRMS security model rather than by purchasing or procurement document scope.

Key Columns

Common Use Cases and Queries

The most frequent use is retrieving scheduling attributes such as DEFAULT_END_TIME for an organization unit, typically to drive iProcurement requisition defaults, approval routing, or downstream reporting. HR security applies, so the querying user's security profile determines visible rows.

A typical retrieval of scheduling data follows:

SELECT organization_id, name, default_start_time, default_end_time, working_hours, frequency FROM apps.icx_per_organization_units_v WHERE business_group_id = :p_business_group_id AND TRUNC(SYSDATE) BETWEEN date_from AND NVL(date_to, TRUNC(SYSDATE));

A second pattern resolves the organization name for a known ID, joining outward to other HR or purchasing entities as needed. Because the view is documented obsolete and is only a projection of PER_ORGANIZATION_UNITS, the recommended approach for new development is to query PER_ORGANIZATION_UNITS directly, reserving ICX_PER_ORGANIZATION_UNITS_V for maintaining existing legacy objects until they are migrated.