Search Results dummy_id




Overview
Explore in AI Chat

Overview

The APPS.SO_PO_REQUISITION_LINES_V view is a denormalized reporting and integration object within the Oracle E-Business Suite Order Entry (OE) product family. It is catalogued in the ETRM (E-Business Suite Technical Reference Manual) as a VALID VIEW owned by the APPS schema. Its principal role is to expose purchasing requisition line data in a form enriched with human-readable organization context, so that downstream Order Entry processes, forms, and interfaces can consume requisition information without issuing multiple joins to the underlying inventory and purchasing tables.

The view combines requisition line detail with location codes derived from inventory parameters and with the distribution account identifier. It is read-only and carries no DML of its own; it inherits the security, grants, and synonyms applied to its base objects. Because it is defined over APPS synonyms, it is intended to be queried through the standard APPS database connection rather than a product-specific schema.

Underlying Base Objects

The documented base objects referenced by this view are:

  • PO_REQUISITION_LINES (synonym) — the driving table, providing requisition line identity, line number, destination type, source and destination organizations, and audit columns.
  • MTL_PARAMETERS (synonym) — joined twice, once for the source organization and once for the destination organization, to resolve organization identifiers into organization codes.
  • PO_REQ_DISTRIBUTIONS (synonym) — joined to obtain the charge account distribution for the requisition line.

All joins are defined in the view text. The MTL_PARAMETERS joins are outer joins (indicated by the (+) operator in the WHERE clause), meaning requisition lines are retained even when the corresponding source or destination organization is not represented in MTL_PARAMETERS. The PO_REQ_DISTRIBUTIONS join on REQUISITION_LINE_ID is an inner join, so only requisition lines with a matching distribution row appear in the result set.

Key Columns

  • REQUISITION_LINE_ID — primary identifier of the requisition line; the join key to PO_REQ_DISTRIBUTIONS.
  • LINE_NUM — the displayed line sequence within the requisition header.
  • DESTINATION_TYPE_CODE — indicates the nature of the destination (for example, inventory or expense).
  • FROM_LOC — organization code of the source organization, resolved from MTL_PARAMETERS.
  • TO_LOC — organization code of the destination organization, resolved from MTL_PARAMETERS.
  • CODE_COMBINATION_ID — distribution account identifier, exposed as a character string via TO_CHAR on PO_REQ_DISTRIBUTIONS.CODE_COMBINATION_ID.
  • REQUISITION_HEADER_ID — foreign key linking the line to its requisition header.
  • DUMMY_ID — a literal constant 0 cast into the select list. The name is significant: it is not a stored or derived business attribute but a placeholder required by the consuming Order Entry form or block, which expects a column position named DUMMY_ID. It always evaluates to zero.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns carried from the requisition line.
  • ROW_ID — the ROWID of the base PO_REQUISITION_LINES row, used for row-level addressing.

Common Use Cases and Queries

The view is typically queried when Order Entry needs requisition line context, such as validating source and destination organizations or retrieving the charge account associated with a line. Because CODE_COMBINATION_ID is returned as text, consumers can display it directly without a numeric conversion.

A representative query is:

SELECT requisition_line_id,
       line_num,
       from_loc,
       to_loc,
       code_combination_id,
       requisition_header_id,
       dummy_id
FROM   apps.so_po_requisition_lines_v
WHERE  requisition_header_id = :p_header_id
ORDER  BY line_num;

To filter by destination organization code, a predicate on TO_LOC can be added. When troubleshooting the "dummy_id" reference, note that selecting or filtering on DUMMY_ID will always return the constant 0; it exists solely for positional compatibility with the consuming Order Entry construct and carries no business meaning.