Search Results otfv_finance_headers

Overview

The APPS.OTFV_FINANCE_HEADERS view is a business view template delivered with the OTA (Learning Management) module in Oracle E-Business Suite 12.1.1 and 12.2.2. It is generated from the flexfield view framework and serves as the primary reporting and integration surface for finance headers associated with training and learning financial transactions. Rather than exposing the raw OTA_FINANCE_HEADERS table directly, the view resolves foreign keys, decodes lookup codes, and aggregates related party, vendor, customer, and organization data into a single denormalized row per finance header. This makes it suitable for operational reporting, BI Publisher data sources, and interface programs that need human-readable descriptions alongside internal identifiers.

Underlying Base Objects

The view is defined over OTA_FINANCE_HEADERS (accessed via a synonym) as its driving table, aliased TFH. Lookup decoding and currency descriptions are resolved through the HR_BIS and OTA_GENERAL packages. Invoice amounts are computed dynamically through OTA_TFH_API_BUSINESS_RULES2.INVOICE_FULL_AMOUNT. Set of books names are joined from GL_SETS_OF_BOOKS (a view), and chart of accounts context is supplied through GL_CODE_COMBINATIONS. Party-level attributes are drawn from the HZ schema through HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, HZ_CUST_ACCT_SITES, HZ_LOCATIONS, HZ_PARTY_SITES, HZ_ORG_CONTACTS, and HZ_RELATIONSHIPS. Supplier information comes from the PO_VENDORS and PO_VENDOR_SITES_ALL views, while organization and user context come from HR_ALL_ORGANIZATION_UNITS_TL and FND_USER. FND_GLOBAL supplies session context. The embedded descriptor tokens (_KF and _DF) indicate that the view participates in the flexfield view-generation template, which is why the underlying object is documented as a "business view template."

Key Columns

• HEADER_ID — Surrogate from TFH.FINANCE_HEADER_ID; uniquely identifies the finance header.
• HEADER_SUPERSEDES — References SUPERCEDING_HEADER_ID, indicating header replacement chains.
• HEADER_TYPE / HEADER_SUB_TYPE — Decoded FINANCE_HEADER_TYPE lookup plus RECEIVABLE_TYPE.
• CANCELLED_FLAG / HEADER_CANCELLED / HEADER_PAID — Yes/No lookup decodes for cancellation and payment status.
• CURRENCY — Descriptive currency name resolved via OTA_GENERAL.FND_CURRENCY_NAME.
• TRANSFER_STATUS / TRANSFER_DATE / TRANSFER_MESSAGE — GL transfer state machine attributes.
• TRANSFER_FROM_SET_OF_BOOKS_ID / TRANSFER_TO_SET_OF_BOOKS_ID — The source and destination ledger identifiers; these are the columns most relevant to the search term transfer_to_set_of_books_id. They are complemented by SET_OF_BOOKS_FROM and SET_OF_BOOKS_TO, the descriptive names joined from GL_SETS_OF_BOOKS.
• TRANSFER_FROM_CC_ID / PAYING_COST_CENTER / RECEIVING_COST_CENTER — Cost center and chart of accounts context.
• INVOICE_FULL_AMOUNT — Computed through the business rules package.
• SUPPLIER_NAME / CUSTOMER_NAME / CONTACT_NAME / AUTHORIZED_BY / ORGANIZATION_NAME — Descriptive party and approver fields.
• ADDRESS_LINE1–4, CITY, POSTAL_CODE, PROVINCE, COUNTY — Address elements from HZ_LOCATIONS/HZ_PARTY_SITES.

Common Use Cases and Queries

Typical scenarios include reconciling training-related financial transactions before and after GL transfer, auditing inter-ledger transfers, and driving BI Publisher layouts without re-implementing lookup decoding. A representative query isolating the transfer destination ledger is:

SELECT header_id, set_of_books_from, set_of_books_to, transfer_to_set_of_books_id, transfer_status, transfer_date, invoice_full_amount FROM apps.otfv_finance_headers WHERE transfer_to_set_of_books_id IS NOT NULL AND transfer_status <> 'TRANSFERRED';

For cross-ledger analysis, joining header_id back to OTA_FINANCE_HEADERS or OTA_FINANCE_LINES provides drill-down to distribution detail. Because the view already resolves currency, supplier, customer, and address attributes, it is preferable to a raw table query for reporting purposes. In 12.2.2 the join to GL_SETS_OF_BOOKS reflects the transition toward ledger-based accounting, though the column naming retains the historical "SET_OF_BOOKS" convention for backward compatibility with 12.1.1.