Search Results dummy_id




Overview
Explore in AI Chat

Overview

OE_PO_REQUISITION_LINES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, registered under the ONT (Order Management) product family. It is documented as a "Purchase order requisition lines view," meaning it presents a simplified, denormalized projection of purchasing requisition line data for consumption by Order Management functionality, external reporting, and integration interfaces. The view is marked VALID in the ETRM repository for both 12.1.1 and 12.2.2, and its metadata is stable across those releases.

The view exists to expose requisition line attributes without requiring callers to join the underlying transaction tables manually. Notably, the view text does not reference any Order Management tables such as OE_ORDER_HEADERS_ALL or OE_ORDER_LINES_ALL; it is a purchasing-centric view surfaced through the ONT module. The presence of the literal column 0 DUMMY_ID reflects a deliberate design pattern in EBS: a constant placeholder column included so that generic interface code, structure-compatibility checks, or dependent views expecting a column named DUMMY_ID can bind against this view without error. It carries no business meaning and always returns zero.

Underlying Base Objects

The view is defined over four documented base objects, all referenced as APPS synonyms in 12.2.2:

  • PO_REQUISITION_LINES_ALL — the primary driving table (alias PRL), supplying requisition line identifiers, line numbers, destination type, header reference, source/destination organizations, and audit columns.
  • PO_REQ_DISTRIBUTIONS_ALL — alias PRD, joined on REQUISITION_LINE_ID to supply the distribution accounting flexfield reference, exposed as CODE_COMBINATION_ID.
  • MTL_PARAMETERS — joined twice with outer joins (aliases MP1 and MP2) to derive organization codes for the source and destination inventory organizations.

The joins are: MP1.ORGANIZATION_ID(+) = PRL.SOURCE_ORGANIZATION_ID, MP2.ORGANIZATION_ID(+) = PRL.DESTINATION_ORGANIZATION_ID, and PRD.REQUISITION_LINE_ID = PRL.REQUISITION_LINE_ID. The (+) outer joins on MTL_PARAMETERS mean requisition lines with null or invalid source/destination organizations are still returned, with FROM_LOC and TO_LOC null. The distribution join is an inner join, so only lines with at least one matching distribution row appear; on multi-distribution lines this can produce row multiplication that callers must anticipate.

Key Columns

  • REQUISITION_LINE_ID — primary key of the requisition line, the principal join key back to PO_REQUISITION_LINES_ALL and to distribution records.
  • LINE_NUM — the displayed line number on the requisition.
  • DESTINATION_TYPE_CODE — indicates the destination context of the line, such as inventory, expense, or shop floor destination.
  • FROM_LOC / TO_LOC — organization codes resolved from MTL_PARAMETERS for the source and destination organizations respectively.
  • CODE_COMBINATION_ID — the accounting flexfield combination from the requisition distribution, exposed as a character string via TO_CHAR, which is significant for interfaces expecting text-formatted identifiers.
  • REQUISITION_HEADER_ID — foreign key to the parent requisition header.
  • DUMMY_ID — constant zero; a structural placeholder with no business semantics.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit and who columns sourced from the line record.
  • ROW_ID — the ROWID of the underlying PO_REQUISITION_LINES_ALL row, useful for direct row addressing and debugging.

Common Use Cases and Queries

Typical scenarios include reporting requisition demand destined for order fulfillment, resolving destination organization codes for inbound supply, and extracting distribution accounting references for reconciliation. A common diagnostic query, given the frequency of DUMMY_ID searches against this object, is:

  • SELECT requisition_line_id, line_num, destination_type_code, from_loc, to_loc, code_combination_id FROM oe_po_requisition_lines_v WHERE requisition_header_id = :p_header_id ORDER BY line_num;
  • SELECT requisition_line_id, dummy_id FROM oe_po_requisition_lines_v WHERE dummy_id = 0; — the query shape most often associated with the "dummy_id" search term, confirming the constant column is being used as a structural selector.
  • SELECT v.line_num, v.from_loc, v.to_loc FROM oe_po_requisition_lines_v v WHERE v.to_loc = :p_org_code; — locating requisition lines by destination organization.

Because CODE_COMBINATION_ID is returned as character data and the distribution join is inner, consumers should validate cardinality and data type conversions when integrating this view into downstream interfaces.