Results for “tfh_information20”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.OTA_FINANCE_HEADERS_V is a reporting and integration view shipped with the Oracle Learning Management (OTA) module in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the denormalized content of the OTA_FINANCE_HEADERS transaction table together with the descriptive attributes required to interpret a finance header without additional lookups. The view resolves organization names, user names, vendor names, customer names, and decoded lookup meanings inline, and it invokes the OTA_TFH_API_BUSINESS_RULES2.INVOICE_FULL_AMOUNT function to compute the invoice amount for each header. It is the primary interface through which administrators and integrators inspect externally facing finance data generated from learning events, including invoices, credit memos, and receivable entries destined for Oracle Receivables or Oracle Payables.

Underlying Base Objects

The view is defined in the APPS schema and is layered over the following documented objects:

• OTA_FINANCE_HEADERS — the driving synonym and principal source of all header columns.
• HR_ALL_ORGANIZATION_UNITS and HR_ALL_ORGANIZATION_UNITS_TL — supply the operating unit NAME and BUSINESS_GROUP_ID.
• FND_USER — aliased twice to resolve AUTHORIZER_PERSON_ID and the ADMINISTRATOR column to user names.
• PO_VENDORS — provides VENDOR_NAME.
• HZ_CUST_ACCOUNTS and HZ_PARTIES — supply the customer name, truncated with SUBSTRB(...,1,50).
• HR_GENERAL (package) — provides DECODE_LOOKUP translations for TRANSFER_STATUS, FINANCE_HEADER_TYPE, and PAYMENT_METHOD.
• OTA_TFH_API_BUSINESS_RULES2 (package) — supplies the INVOICE_FULL_AMOUNT function.

Because the view joins these objects without filtering by business group or organization, callers must apply their own operating-unit and security predicates.

Key Columns

Among the most operationally significant columns are:

• FINANCE_HEADER_ID — unique primary key of the header record.
• SUPERCEDING_HEADER_ID — the header that replaces this record when an invoice or credit memo is superseded by a re-issued version. A null value indicates the header is current.
• TYPE and FINANCE_HEADER_TYPE — numeric type code and its decoded description.
• RECEIVABLE_TYPE, TRANSFER_STATUS, TRANSFER_DATE, and TRANSFER_MESSAGE — the accounting transfer lifecycle and any error text returned by the transfer process.
• PAYMENT_STATUS_FLAG, PAYMENT_METHOD, and PYM_ATTRIBUTE1..20 — payment configuration and the flexfield-style payment attributes.
• CURRENCY_CODE and the computed INVOICE_FULL_AMOUNT — monetary context of the header.
• CUSTOMER_ID/CUSTOMER_NAME and VENDOR_ID/VENDOR_NAME — the trading party.
• Audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE.

Common Use Cases and Queries

Typical uses include reconciling learning invoices before transfer, diagnosing stuck transfers, and reporting on superseded headers.

Locate current headers for an operating unit:

SELECT finance_header_id, type, currency_code, invoice_full_amount,
       transfer_status, transfer_date
FROM   ota_finance_headers_v
WHERE  organization_id = :org_id
AND    superceding_header_id IS NULL
AND    transfer_status <> 'Y';

Trace supersession chains:

SELECT finance_header_id, superceding_header_id, external_reference
FROM   ota_finance_headers_v
WHERE  superceding_header_id IS NOT NULL
ORDER BY creation_date DESC;

Review transfer failures with decoded status and message:

SELECT finance_header_id, transfer_status, transfer_message,
       invoice_full_amount, customer_name
FROM   ota_finance_headers_v
WHERE  transfer_message IS NOT NULL;

All queries should be restricted by org_id or business group to respect multi-org access, since the view itself includes no security predicate.