Search Results tax_calculation_event_code




Overview
Explore in AI Chat

Overview

OE_LINE_TYPES_V is an APPS-owned database view in the Oracle E-Business Suite Order Management (ONT) module. As its description states, it exposes line transaction types for a specific organization and language. In Oracle Order Management, transaction types govern the behavior, defaults, and validation applied to order headers and lines. Two principal categories exist: order transaction types and line transaction types. OE_LINE_TYPES_V is dedicated to the latter, filtering the underlying transaction type definition to only those records whose TRANSACTION_TYPE_CODE equals 'LINE'.

Because the view carries an ORG_ID column sourced from the multi-org enabled base object, it is an organization-specific (operating unit) view. This makes it suitable for reporting and integration scenarios where the correct line type set must be resolved for a given business unit and session language. The view is marked VALID in the ETRM repository, confirming its compiled status in both 12.1.1 and 12.2.2 environments.

Underlying Base Objects

The view text shows a single documented base object: OE_TRANSACTION_TYPES_VL. This is the translated (VL) view over the transaction types entity and supplies both the language-dependent descriptive columns (NAME, DESCRIPTION) and the language-independent attributes. OE_LINE_TYPES_V selects the full column list from OE_TRANSACTION_TYPES_VL and applies the predicate WHERE TRANSACTION_TYPE_CODE = 'LINE'. It therefore acts as a filtered projection: no joins or aggregations are introduced, and no additional filtering beyond the line-type restriction is applied at the view level. Note that two columns in the view text both reference TRANSACTION_TYPE_ID; the column listing distinguishes them as TRANSACTION_TYPE_ID and LINE_TYPE_ID, the latter being the legacy name for the line type identifier.

Key Columns

Common Use Cases and Queries

OE_LINE_TYPES_V is commonly used to populate LOVs and validation lists in custom forms, reports, and interfaces that accept a line transaction type, and to drive defaulting logic in inbound order interfaces. A typical generic query is:

SELECT TRANSACTION_TYPE_ID, NAME, ORDER_CATEGORY_CODE, WAREHOUSE_ID
FROM OE_LINE_TYPES_V
ORDER BY NAME;

For an organization-restricted listing, constrain on ORG_ID or rely on the multi-org view's automatic operating unit filtering:

SELECT TRANSACTION_TYPE_ID, NAME, ORDER_CATEGORY_CODE
FROM OE_LINE_TYPES_V
WHERE ORG_ID = :p_org_id
AND SYSDATE BETWEEN NVL(START_DATE_ACTIVE, SYSDATE)
AND NVL(END_DATE_ACTIVE, SYSDATE);

Because the view already restricts to line transaction types, no additional filtering on TRANSACTION_TYPE_CODE is required. When joining to order lines, use TRANSACTION_TYPE_ID as the link to OE_ORDER_LINES_ALL.TRANSACTION_TYPE_ID, and combine with OE_ORDER_HEADERS_ALL to report line behavior by type, category, and invoice defaults.