Search Results location_organization_id

Overview

The ICX_PO_REQUESTOR_VAL_V view is a requester list-of-values (LOV) view owned by the APPS schema in Oracle E-Business Suite, validated in releases 12.1.1 and 12.2.2. It is delivered by the ICX (Oracle iProcurement) product and serves as the data source for the Requester LOV presented to users during requisition entry and similar purchasing flows. Rather than exposing raw HR tables, the view flattens employee, user, location, and financials system parameter data into a single denormalized record per eligible requester, making it suitable for LOV lookups, reporting, and integration queries.

Because the view joins against profile-driven logic and HR security, the set of requesters returned is filtered according to the ICX_REQ_OVERRIDE_REQUESTOR_CODE profile option, controlling whether a user may act as a requester only for themselves, within their organization, or across all organizations. This behavior is central to its role as a controlled validation source rather than a simple employee listing.

Underlying Base Objects

The view text defines joins over the following documented base objects:

• HR_EMPLOYEES_CURRENT_V — aliased twice (HRE and HRE2) to supply current employee attributes and to enforce the organization-level matching driven by the override profile.
• HR_LOCATIONS — joined on LOCATION_ID (outer join) to supply location code and, where present, the inventory organization tied to the location.
• FND_USER — supplies the web user identity linked to the employee.
• ICX_USER_PROFILES — ties the web user to iProcurement profile data.
• FINANCIALS_SYSTEM_PARAMETERS — provides the default inventory organization used when the location is not associated with one.
• FND_PROFILE (package) — invoked through FND_PROFILE.VALUE_WNPS to evaluate ICX_REQ_OVERRIDE_REQUESTOR_CODE and branch the join logic.

Additional documented references include HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY packages, which supply name resolution and security enforcement within the underlying HR view.

Key Columns

• WEB_USER_ID — the FND_USER identifier of the requestor; the LOV return value.
• FULL_NAME and EMAIL_ADDRESS — display and notification attributes for the requester.
• EMPLOYEE_ID, EMPLOYEE_NUM — HR employee identifiers used for linkage back to HR records.
• DEFAULT_CODE_COMBINATION_ID — the default accounting flexfield for the employee, used in charge account derivation.
• LOCATION_ID and LOCATION_CODE — the HR location assigned to the employee.
• ORGANIZATION_ID and BUSINESS_GROUP_ID — the employee's organization and business group context.
• EXPENSE_CHECK_ADDRESS_FLAG — indicates whether the expense check address applies.
• LOCATION_ORGANIZATION_ID — the column matched by the search term "location_organization_id." It resolves to NVL(HRL.INVENTORY_ORGANIZATION_ID, FSP.INVENTORY_ORGANIZATION_ID), returning the inventory organization associated with the employee's location, or the financials system parameter default when no location-level organization exists.

Common Use Cases and Queries

Typical uses include validating requester selections in custom requisition forms, reporting on requesters and their default organizations, and troubleshooting why a given user appears or does not appear in the iProcurement Requester LOV.

• Listing eligible requesters: SELECT web_user_id, full_name, location_organization_id FROM apps.icx_po_requestor_val_v;
• Resolving the inventory organization for a specific requester: SELECT full_name, location_code, location_organization_id FROM apps.icx_po_requestor_val_v WHERE web_user_id = :p_user_id;
• Auditing requesters by organization: SELECT organization_id, COUNT(*) FROM apps.icx_po_requestor_val_v GROUP BY organization_id;

Because visibility depends on the ICX_REQ_OVERRIDE_REQUESTOR_CODE profile and HR security, query results vary by the effective profile values of the session, a behavior worth confirming when validating integration output.