Search Results header_sub_type




Overview
Explore in AI Chat

Overview

OTFV_FINANCE_LINES is a business view template owned by the APPS schema within the OTA (Learning Management) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It is not an operational table but a presentation-layer construct designed to expose finance line records for use by descriptive flexfield (DFF) view generation, reporting, and integration. Specifically, the view serves as the business view template from which the flexfield view is generated, meaning it defines the selectable, joinable, and displayable shape of finance line data that downstream flexfield-enabled views inherit.

In ETRM-enabled reporting, this view functions as a flattened, decoded, user-readable projection of the OTA finance line and finance header data. Rather than requiring report authors and integrators to resolve raw codes, foreign keys, and multi-table joins against booking deals, events, activity versions, customers, and contacts, the view exposes pre-joined, lookup-decoded columns. This makes it suitable for ad hoc queries, OBIEE-style repositories, and outbound integration extracts.

Underlying Base Objects

The view is defined over a set of documented base objects. The primary fact sources are the synonyms OTA_FINANCE_LINES (aliased TFL) and OTA_FINANCE_HEADERS (aliased TFH). Contextual enrichment comes from a wide set of joins across the Learning Management and shared Oracle schemas, including:

The view text shows that decoding is delegated to HR_BIS.BIS_DECODE_LOOKUP for lookup categories such as FINANCE_LINE_TYPE, YES_NO, GL_TRANSFER_STATUS, FINANCE_HEADER_TYPE, BOOKING_DEAL_TYPE, and TRAINING_UNIT, and that currency names are resolved through OTA_GENERAL.FND_CURRENCY_NAME. Several columns are placeholders cast with TO_CHAR(NULL) or TO_DATE(NULL), leaving resource attributes (RESOURCE_NAME, RESOURCE_TYPE, RESOURCE_BOOKING_FROM, RESOURCE_BOOKING_TO) to be populated by the flexfield-generated view rather than by the base template query.

Key Columns

Common Use Cases and Queries

Typical uses include finance reconciliation, revenue or receivable analysis for enrollments, and GL transfer monitoring. A basic query follows:

SELECT line_id, line_type, sequence, currency,
       money_amount, date_raised, transfer_status,
       student_name, customer_name, event_title
FROM   apps.otfv_finance_lines
WHERE  transfer_status = 'Pending'
ORDER BY date_raised DESC;

For aggregation by header type and currency:

SELECT header_type, currency,
       COUNT(*) line_count, SUM(money_amount) total_amount
FROM   apps.otfv_finance_lines
WHERE  line_cancelled = 'No'
GROUP BY header_type, currency;

Integrators frequently join LINE_ID back to OTA_FINANCE_LINES or OTA_FINANCE_HEADERS for keys not exposed through lookup decoding, and filter on ENROLLMENT_TYPE to separate internal (PER) from external (HZ) delegates.