Search Results line_types




Overview
Explore in AI Chat

Overview

APPS.PO_STYLE_ENABLED_LINE_TYPES is a lightweight Oracle EBS database view that exposes the set of purchasing line types currently enabled for a given document style. Within Oracle Purchasing, document styles (also called PO styles) control which features and value sets are available when a buyer creates or modifies a purchasing document. Styles are stored in PO_DOC_STYLE_VALUES, a key-value repository in which each style attribute is held as a name/value pair. The view filters that repository down to a single attribute — LINE_TYPES — and returns only the rows whose ENABLED_FLAG is set to 'Y'.

The result is a concise two-column projection, LINE_TYPE_ID and STYLE_ID, that answers the question: "For this purchasing style, which line types are currently allowed?" Because it abstracts the underlying generic attribute storage into a simple, purpose-specific shape, the view is convenient for reporting, validation, diagnostic queries, and integration logic that must confirm a style's permitted line types without reimplementing the filter logic. It is owned by APPS and follows the standard Oracle EBS convention of exposing a synonym-backed, read-only presentation layer over a base configuration table.

Underlying Base Objects

The view is defined over a single referenced base object, PO_DOC_STYLE_VALUES, accessed through a synonym. The view text is:

PO_DOC_STYLE_VALUES stores style configuration as generic attribute rows. Each row carries a STYLE_ID, a STYLE_ATTRIBUTE_NAME, a STYLE_ALLOWED_VALUE, and an ENABLED_FLAG. The view restricts STYLE_ATTRIBUTE_NAME to the literal 'LINE_TYPES' and retains only enabled ('Y') rows. The character STYLE_ALLOWED_VALUE is cast to a numeric type via TO_NUMBER to yield LINE_TYPE_ID, which corresponds to PO_LINE_TYPES_B.LINE_TYPE_ID. Because there is no join to PO_LINE_TYPES_B or PO_DOC_STYLES, the view returns identifiers only; descriptive attributes such as line type name or document style name must be obtained by joining to those tables separately. The view therefore functions as a denormalized bridge between style definitions and the line type master data.

Key Columns

  • LINE_TYPE_ID — Numeric identifier produced by TO_NUMBER(STYLE_ALLOWED_VALUE). Identifies an enabled line type for the associated style and maps to PO_LINE_TYPES_B.LINE_TYPE_ID.
  • STYLE_ID — Identifier of the purchasing document style to which the enabled line type belongs. Links to the style definition (for example PO_DOC_STYLES.STYLE_ID).

The ENABLED_FLAG and STYLE_ATTRIBUTE_NAME columns exist in the base table but are consumed by the view's WHERE clause and are not projected, so consumers always see only active 'LINE_TYPES' entries.

Common Use Cases and Queries

Typical scenarios include auditing which line types a style permits, validating that a desired line type is enabled before processing, and feeding style-driven logic in reports or interfaces.

  • List enabled line types for a specific style:
    SELECT LINE_TYPE_ID FROM APPS.PO_STYLE_ENABLED_LINE_TYPES WHERE STYLE_ID = :p_style_id;
  • Resolve identifiers to descriptive names:
    SELECT v.STYLE_ID, v.LINE_TYPE_ID, t.LINE_TYPE_NAME FROM APPS.PO_STYLE_ENABLED_LINE_TYPES v, APPS.PO_LINE_TYPES_B t, APPS.PO_LINE_TYPES_TL tl WHERE v.LINE_TYPE_ID = t.LINE_TYPE_ID AND t.LINE_TYPE_ID = tl.LINE_TYPE_ID AND tl.LANGUAGE = USERENV('LANG');
  • Count enabled line types per style:
    SELECT STYLE_ID, COUNT(*) FROM APPS.PO_STYLE_ENABLED_LINE_TYPES GROUP BY STYLE_ID;

Because the view is read-only and derived, it is safe for reporting and validation; modifications must be made against PO_DOC_STYLE_VALUES.