Results for “purchase_basis”

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

Overview

PO_LINE_TYPES_VAL_V is an Oracle E-Business Suite (EBS) view owned by the APPS schema within the Purchasing (PO) module. Its ETRM description carries the notation "10SC ONLY - Retrofitted," indicating that the object originated in an earlier 10SC code line and was subsequently retrofitted into the 12.1.1 and 12.2.2 environments. In practice, the view serves as a validation and reporting layer over purchasing line type definitions, joining line type records to lookup code descriptions so that order type and purchase basis values are presented in a business-friendly, decoded form. It is typically consumed by forms validation logic, concurrent reporting, and downstream integrations that need a filtered list of currently active line types. The view is registered as VALID in the APPS schema and is referenced through the standard APPS synonym conventions, meaning it must be accessed with the APPS schema context (or an appropriate synonym or grant) rather than queried directly against the base tables.

Underlying Base Objects

The documented ETRM metadata for the 12.2.2 file identifies the referenced base objects as FND_GLOBAL (PACKAGE), PO_LINE_TYPES (SYNONYM), and PO_LOOKUP_CODES (VIEW). In the view's SQL text, PO_LINE_TYPES supplies the core line type attributes, while PO_LOOKUP_CODES is joined twice under the aliases LC and LC1. The first join resolves ORDER_TYPE_LOOKUP_CODE against LOOKUP_TYPE = 'ORDER TYPE', and the second resolves PURCHASE_BASIS against LOOKUP_TYPE = 'PURCHASE BASIS'. This dual self-join pattern is what exposes the decoded DISPLAYED_FIELD values, including PURCHASE_BASIS_DSP. The reference to FND_GLOBAL reflects the standard EBS session dependency, where the view is evaluated in the context of the authenticated application session. Although PO_LINE_TYPES and PO_LOOKUP_CODES are listed as synonyms and a view respectively in the ETRM reference, they ultimately resolve to the underlying purchasing base tables and lookup views maintained by the PO module.

Key Columns

The view projects thirteen columns. The most significant include:

• LINE_TYPE and LINE_TYPE_ID — the internal identifier and primary key for each purchasing line type; LINE_TYPE_ID is the value typically stored on transactional lines.
• DESCRIPTION — the user-facing name of the line type.
• ORDER_TYPE_LOOKUP_CODE and DISPLAYED_FIELD — the raw lookup code and its decoded description for the associated order type.
• PURCHASE_BASIS and PURCHASE_BASIS_DSP — the purchase basis lookup code and its decoded display field, determining whether the line is priced by quantity, amount, or another basis.
• MATCHING_BASIS — controls how the line is matched against receipts and invoices.
• UNIT_OF_MEASURE, UNIT_PRICE, CATEGORY_ID — default sourcing parameters applied when the line type is used.
• OUTSIDE_OPERATION_FLAG and RECEIVING_FLAG — flags governing outside processing and receipt-driven behavior.

Common Use Cases and Queries

The most common use is populating a validated list of active line types for forms or interfaces. The view's WHERE clause excludes inactive records by comparing SYSDATE against INACTIVE_DATE, so consumers automatically receive only current definitions. A representative query is:

• SELECT line_type_id, line_type, description, purchase_basis_dsp FROM apps.po_line_types_val_v ORDER BY line_type;
• SELECT line_type_id, description FROM apps.po_line_types_val_v WHERE order_type_lookup_code = 'STANDARD';
• SELECT line_type, matching_basis, receiving_flag FROM apps.po_line_types_val_v WHERE purchase_basis = 'QUANTITY';

These queries support reporting on line type configuration, data validation during purchasing document import, and integration extraction of default unit of measure and matching rules. Because the view is retrofitted and marked for 10SC lineage, implementations should verify grants and any client extensions before relying on it in custom code.