Search Results multiple_value




Overview
Explore in AI Chat

Overview

APPS.POR_VIEW_REQS_BY_GROUP_V is a reporting view in the Oracle E-Business Suite Purchasing module that consolidates purchase requisition header and line information into a single denormalized result set, aggregated at the requisition header level. It is designed to support the "Requisitions by Group" style of inquiry, in which a user views requisitions grouped by header while line-level detail is summarized through aggregation. The view is owned by the APPS schema and is available in both EBS 12.1.1 and 12.2.2, with the documented metadata confirmed for 12.2.2.

A distinguishing characteristic of this view is its explicit handling of the multiple-value condition. When the lines belonging to a requisition reference more than one distinct supplier, the view does not attempt to select a single vendor name. Instead, it returns the literal string 'MULTIPLE_VALUE' in the supplier column. This behavior is central to the view's purpose: it allows a report to present a meaningful supplier indicator for a grouped requisition without presenting an arbitrary or misleading single value.

Underlying Base Objects

The view is defined over a substantial set of EBS base objects. The documented references include PO_REQUISITION_HEADERS and PO_REQUISITION_LINES, the primary transactional tables holding requisition header and line data. Supplier information derives from PO_VENDORS, now modeled as a view in the current data model, and employee data from HR_EMPLOYEES_CURRENT_V with the HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY packages.

The view text combines an outer header query with an inline aggregated subquery over requisition lines, unioned to support differing security paths, so that totals and supplier flags reflect only lines visible to the querying user.

Key Columns

  • requisition_header_id and segment1 — the internal key and the user-visible requisition number.
  • preparer_id and full_name — the preparer's identifier and display name, with an uppercase last name for sorting.
  • description — the requisition header description.
  • authorization_status and displayed_field — the raw status code and its decoded display value.
  • cancel_flag and closed_code — cancellation indicator and the normalized closed code, defaulted to 'OPEN', each accompanied by a decoded displayed field.
  • card_number — corporate card number associated with the requisition where applicable.
  • creation_date conversions — the creation date formatted using the ICX_DATE_FORMAT_MASK profile, plus a canonical 'YYYY-MM-DD' form.
  • total — the sum of unit price multiplied by quantity less quantity cancelled across qualifying lines, formatted by the set of books currency.
  • supplier — the single vendor name when only one distinct vendor exists, otherwise the literal 'MULTIPLE_VALUE'.
  • placed_on_po — 'Y' when at least one line has been placed on a purchase order, otherwise 'N'.
  • emergency_po_num — the emergency purchase order number where present.

Common Use Cases and Queries

The view is typically consumed by requisition inquiry and reporting pages that group lines under their header and require a summarized supplier and total. A basic query retrieves open requisitions and flags those spanning multiple suppliers:

  • SELECT segment1, full_name, total, supplier FROM apps.por_view_reqs_by_group_v WHERE closed_code = 'OPEN';
  • SELECT segment1, supplier FROM apps.por_view_reqs_by_group_v WHERE supplier = 'MULTIPLE_VALUE'; — identifies grouped requisitions covering more than one vendor, useful for supplier consolidation review.
  • SELECT segment1, authorization_status, placed_on_po FROM apps.por_view_reqs_by_group_v WHERE placed_on_po = 'N' AND cancel_flag = 'N'; — surfaces requisitions not yet placed on a purchase order.

Because the supplier column resolves to 'MULTIPLE_VALUE' rather than a specific vendor, consumers should treat it as an indicator, not a foreign key, and drill into PO_REQUISITION_LINES when line-level vendor attribution is required.