Results for “po_line_types_all_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The PO_LINE_TYPES_ALL_V view resides in the APPS schema and belongs to the Oracle Purchasing (PO) product module. It is documented in ETRM metadata with the description "10SC ONLY - Retrofitted," indicating that the object was retrofitted into the E-Business Suite environment from an earlier 10SC (Oracle 10 Smart Client / character-mode) code line and remains a valid, compiled object in both Oracle EBS 12.1.1 and 12.2.2. The view exposes the master definition of purchasing line types — the category of document line that governs downstream behavior such as receiving, purchase basis, and default unit of measure and price — joined to human-readable lookup meanings for the order type classification and the purchase basis.

Functionally, the view serves as a reporting and integration convenience layer. It allows banner, forms, reports, concurrent programs, and external interfaces to resolve the lookup codes on a line type into their displayed descriptions without re-joining the lookup structures each time. Because it selects across PO_LINE_TYPES and PO_LOOKUP_CODES, it presents a "denormalized" picture of line type configuration that is directly consumable by downstream logic and by customizations that reference the ORDER_TYPE_LOOKUP_CODE attribute.

Underlying Base Objects

The ETRM documented metadata for the 12.2.2 environment lists three referenced base objects: FND_GLOBAL (PACKAGE), PO_LINE_TYPES (SYNONYM), and PO_LOOKUP_CODES (VIEW). The view text confirms that the principal data comes from PO_LINE_TYPES (aliased LT), which supplies the line type definition itself. PO_LOOKUP_CODES is joined twice: once as LC to resolve the ORDER_TYPE_LOOKUP_CODE against the lookup type 'ORDER TYPE', and once as LC1 to resolve PURCHASE_BASIS against the lookup type 'PURCHASE BASIS'. This double-join pattern is the defining structural characteristic of the view. The inclusion of FND_GLOBAL in the referenced-object metadata reflects the standard EBS practice of capturing session context (user, responsibility, application) via the FND_GLOBAL package, even though it does not appear explicitly in the published join clause.

Key Columns

• LINE_TYPE — The code value identifying the line type.
• DESCRIPTION — The descriptive name of the line type.
• LINE_TYPE_ID — The unique primary key identifier for the line type; the column most commonly used in foreign-key joins from line-level tables.
• DISPLAYED_FIELD — Derived from PO_LOOKUP_CODES for the 'ORDER TYPE' lookup, providing the displayed value associated with the order type classification.
• ORDER_TYPE_LOOKUP_CODE — The lookup code that classifies the line type's order type; this is the column that users most frequently search for and that links the view to the 'ORDER TYPE' lookup definition.
• CATEGORY_ID — Reference to the purchasing category associated with the line type.
• UNIT_OF_MEASURE, UNIT_PRICE — Default unit of measure and default unit price propagated to lines created with this line type.
• OUTSIDE_OPERATION_FLAG — Indicates whether the line type supports outside processing operations.
• RECEIVING_FLAG — Indicates whether goods for this line type are received, driving the receiving workflow.
• PURCHASE_BASIS — The code indicating whether purchasing is based on quantity or amount.
• PURCHASE_BASIS_DSP — The displayed description of the purchase basis, sourced from PO_LOOKUP_CODES via the 'PURCHASE BASIS' lookup type.

Common Use Cases and Queries

The view is typically queried when building lookups for line-entry forms, validating line type configuration, or reporting on how order types map to line types. A representative query filters on the searched attribute:

• SELECT line_type_id, line_type, description, order_type_lookup_code, displayed_field, purchase_basis, purchase_basis_dsp FROM apps.po_line_types_all_v WHERE order_type_lookup_code = :p_order_type;
• SELECT line_type_id, line_type, description, receiving_flag, outside_operation_flag FROM apps.po_line_types_all_v ORDER BY line_type;
• SELECT l.line_type, l.description, l.purchase_basis_dsp FROM apps.po_line_types_all_v l WHERE l.purchase_basis = 'QUANTITY';

These patterns are commonly embedded in value-set validation, custom concurrent reporting, and inbound interface processing where a requester supplies an order type and the corresponding valid line types must be enumerated.