Search Results financials_system_parameters




Overview
Explore in AI Chat

Overview

APPS.POR_REQUESTER_LOV_V is a seeded Oracle E-Business Suite view owned by the APPS schema and shipped as part of the ICX (Oracle iProcurement) product. Its stated purpose in the ETRM repository is to serve as a "List of Values for Requesters." In practice, the view supplies the row source behind requester selection fields in the iProcurement and Purchasing requisition flows, returning the set of employees who may be designated as requesters together with the descriptive and organizational attributes those pages need to render the LOV and default downstream values.

Because it is a view rather than a table, POR_REQUESTER_LOV_V holds no data of its own. It projects live information from HR and FND at query time, and its result set is deliberately scoped to the currently connected user. The view is relevant to reporting and integration work chiefly as a convenience access point to requester attributes — particularly the deliver-to organization — without requiring custom joins across HR_EMPLOYEES_CURRENT_V, FND_USER, and the financials system parameters.

Underlying Base Objects

The documented base objects underlying the view are:

The view text is built as a UNION ALL across multiple branches; each branch shares the same projection list but applies a different predicate against ICX_REQ_OVERRIDE_REQUESTOR_CODE (NO, ORG, and ALL), governing whether the requester is restricted to the signed-on user or expanded to an organization or the entire population.

Key Columns

Common Use Cases and Queries

Typical uses include validating requester LOV contents, resolving the default deliver-to inventory organization for a requester, and joining requisition headers to requester names for reporting. Because the view is filtered by FND_GLOBAL.USER_ID, query results outside a session context may be restricted; testing in a specific user session or removing the security predicate in a custom query is often necessary.

Sample query to list requesters and their deliver-to organization:

  • SELECT user_id, full_name, employee_num, organization_id, deliver_to_org_id
  • FROM apps.por_requester_lov_v
  • ORDER BY full_name;

Join to requisition headers for requester reporting:

  • SELECT prh.segment1, prh.preparer_id, l.full_name, l.deliver_to_org_id
  • FROM po_requisition_headers_all prh, apps.por_requester_lov_v l
  • WHERE prh.preparer_id = l.user_id;

Always reference the view with the APPS schema prefix and confirm the effective profile setting, since ICX_REQ_OVERRIDE_REQUESTOR_CODE materially changes which requesters are returned.