Search Results purchase_basis




Overview
Explore in AI Chat

Overview

PO.PO_LINE_TYPES_B is the Purchasing (PO) module's base configuration table defining line types. A line type classifies each purchasing document line — purchase order, requisition, RFQ, blanket, or auction line — and controls downstream behavior such as receiving, purchase basis, matching basis, and default category and unit of measure. In Oracle EBS 12.1.1 and 12.2.2 the table resides in the PO schema and is the authoritative source of the LINE_TYPE_ID surrogate key consumed by transactional and interface tables across Purchasing, Order Management, Services, and Advanced Supply Chain Planning. In 12.2.2, the multi-tenant column architecture is exposed through the ZD_EDITION_NAME column, and the unique index PO_LINE_TYPES_B_U1 spans LINE_TYPE_ID and ZD_EDITION_NAME.

Under the heuristic Data Vault classification derived from the FK structure, this table is hub-leaning: it holds a stable, uniquely identified business entity (the line type) referenced by many dependent tables, while the descriptive attribute columns function as satellite-style context. Treating PO_LINE_TYPES_B as a hub is a reasonable modeling suggestion when reverse-engineering or mapping EBS to a warehouse.

Key Information Stored

The object comprises 38 documented columns. The most significant are:

The unique index PO_LINE_TYPES_B_U1 on LINE_TYPE_ID plus ZD_EDITION_NAME is the documented business-key candidate; LINE_TYPE_ID alone is the surrogate PK.

Common Use Cases and Queries

Typical usage centers on resolving line type descriptions for purchasing reports, validating that a PO or requisition line was created with a receiving-enabled type, and driving matching-basis analysis for invoice hold investigations.

  • Join PO_LINES_ALL.LINE_TYPE_ID to PO_LINE_TYPES_B.LINE_TYPE_ID to report line type per PO line.
  • Filter RECEIVING_FLAG = 'Y' to identify receipt-controlled lines for receiving reconciliation.
  • Report MATCHING_BASIS and PURCHASE_BASIS distributions across active line types where INACTIVE_DATE IS NULL.
  • Resolve CATEGORY_ID against MTL_CATEGORIES_B for category spend analysis.
  • Audit CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, and PROGRAM_ID for setup change tracking.

Because the table is small and largely static, queries typically treat it as a reference dimension joined to high-volume fact tables such as PO_LINES_ALL and PO_REQUISITION_LINES_ALL.

Related Objects

The documented relationships identify the primary dependents and the single outbound reference:

Collectively these relationships confirm PO_LINE_TYPES_B as a foundational hub within the Purchasing data model, with wide but shallow fan-out into transactional, interface, and archival tables.