Search Results ota_finance_lines_v




Overview
Explore in AI Chat

Overview

OTA_FINANCE_LINES_V is a read-only view owned by the APPS schema within the Oracle E-Business Suite Learning Management module (OTA). It presents the complete set of attributes for finance lines associated with the training and learning finance model, consolidating data from the OTA_FINANCE_LINES base entity together with descriptive decoded values, booking deal attributes, delegate booking details, training unit classifications, and customer or delegate identification logic. In Oracle EBS 12.1.1 and 12.2.2, the view serves as the primary reporting and integration surface for finance line records, exposing both raw coded values and their lookup-based translations so that external reports, concurrent programs, and interfaces do not need to re-implement decoding logic or join ancillary tables themselves.

Underlying Base Objects

The view is defined primarily over the OTA_FINANCE_LINES synonym, joined to OTA_BOOKING_DEALS (via BOOKING_DEAL_ID) and to delegate booking records in OTA_DELEGATE_BOOKINGS. Decoded values are produced through calls to HR_GENERAL.DECODE_LOOKUP against lookup types such as YES_NO, FINANCE_LINE_TYPE, GL_TRANSFER_STATUS, BOOKING_DEAL_TYPE, and TRAINING_UNIT. Party and organization identity resolution draws on HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, HZ_ORG_CONTACTS, HZ_PARTIES, HZ_RELATIONSHIPS, HR_ORGANIZATION_UNITS, PER_ALL_PEOPLE_F, and the OTA_TDB_BUS package function for full-name formatting. Additional context is supplied by OTA_OFFERINGS, OTA_PRICE_LISTS, OTA_ACTIVITY_VERSIONS_TL, OTA_EVENTS and OTA_EVENTS_TL, OTA_CATEGORY_USAGES, OTA_RESOURCE_BOOKINGS, OTA_SUPPLIABLE_RESOURCES_V, and the security and API packages HR_SECURITY, HR_API, OTA_GENERAL, and OTA_TBD_API. Because the view references Oracle HR security routines and HZ synonyms, query results are subject to the standard business group and security profile restrictions enforced by those packages.

Key Columns

Identifier and control columns include FINANCE_LINE_ID, FINANCE_HEADER_ID, SEQUENCE_NUMBER, OBJECT_VERSION_NUMBER, and ROWID. The CANCELLED_FLAG column exposes the raw value alongside a decoded YES_NO meaning, while LINE_TYPE carries a decoded FINANCE_LINE_TYPE description. Currency and amount information is available through CURRENCY_CODE, STANDARD_AMOUNT, MONEY_AMOUNT, and UNITARY_AMOUNT. General Ledger transfer tracking is supported by TRANSFER_STATUS (with GL_TRANSFER_STATUS decoding), a derived transfer indicator (Y when status is 'ST'), TRANSFER_DATE, and TRANSFER_MESSAGE. The TRANS_INFORMATION_CATEGORY with TRANS_INFORMATION1 through TRANS_INFORMATION20 provides the descriptive flexfield segments.

Booking-related columns include BOOKING_DEAL_ID, the deal NAME and TYPE (decoded via BOOKING_DEAL_TYPE), DISCOUNT_PERCENTAGE, BOOKING_ID, and TRAINING_UNIT_TYPE decoded through the TRAINING_UNIT lookup. Delegate and customer context is resolved through DECODE logic that distinguishes internal from external participants, returning either the delegate person or contact identifier and the corresponding formatted name, along with NUMBER_OF_PLACES and the organization or customer identifier.

Common Use Cases and Queries

Typical usage covers finance line reconciliation, GL transfer monitoring, delegate billing review, and feed extraction for downstream financial systems. A simple listing of active, untransferred lines might read:

  • SELECT finance_line_id, finance_header_id, line_type, currency_code, money_amount, transfer_status FROM ota_finance_lines_v WHERE cancelled_flag = 'N' AND transfer_status <> 'ST';
  • SELECT booking_id, booking_deal_id, name, discount_percentage, training_unit_type FROM ota_finance_lines_v WHERE finance_header_id = :header_id;
  • SELECT finance_line_id, transfer_date, transfer_message FROM ota_finance_lines_v WHERE transfer_status = 'ST' AND transfer_date >= :from_date;

Because the view joins several HR and HZ objects, queries should be filtered by business group and relevant identifiers to maintain performance and to respect security policies. All access is read-only, and no DML should be issued against the view.