Search Results header_cancelled




Overview

OTFV_FINANCE_HEADERS is a Business Intelligence System (BIS) view owned by the APPS schema within Oracle E-Business Suite, registered in FND Design Data under the application short name OTA (Oracle Trade Management / Treasury). It presents generic financial information about dealings an enterprise has with particular customers or suppliers, consolidating header-level finance data such as invoice amounts, transfer status between sets of books, payment indicators, addresses, and party names into a single denormalized query surface. Because its View Type is explicitly documented as a Business Intelligence System view, its primary role is reporting, analytics, and downstream integration rather than transactional data entry; the row data itself originates in the OTA_FINANCE_HEADERS base table and is enriched with descriptive attributes resolved through joins to Oracle Receivables, Oracle Payables, Human Resources, and General Ledger objects.

Underlying Base Objects

The view is defined over a broad set of documented referenced objects. The principal transactional source is OTA_FINANCE_HEADERS (accessed via SYNONYM). Descriptive enrichment is drawn from HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, HZ_CUST_ACCT_SITES, HZ_PARTY_SITES, HZ_LOCATIONS, and HZ_ORG_CONTACTS for customer, contact, and address information; PO_VENDORS and PO_VENDOR_SITES_ALL supply supplier attributes. Organizational data comes from HR_ALL_ORGANIZATION_UNITS_TL and the HR_BIS package. Accounting context is provided through GL_SETS_OF_BOOKS and GL_CODE_COMBINATIONS, supporting the transfer-from and transfer-to accounting flexfield references. Security and session context are resolved via FND_GLOBAL and FND_USER, while business logic for status derivation is delegated to the packages OTA_GENERAL and OTA_TFH_API_BUSINESS_RULES2. This dependency profile confirms that the view is a reporting aggregation, not a stored entity.

Key Columns

The view exposes the transaction key HEADER_ID and the self-referencing HEADER_SUPERSEDES. Because the searched term was set_of_books_from, the most relevant columns are SET_OF_BOOKS_FROM and SET_OF_BOOKS_TO (VARCHAR2(30)), which carry the source and destination ledger names for inter-company or inter-ledger transfers, supported by the numeric TRANSFER_FROM_SET_OF_BOOKS_ID and TRANSFER_TO_SET_OF_BOOKS_ID. Related transfer columns include TRANSFER_STATUS, TRANSFER_DATE, TRANSFER_MESSAGE, TRANSFER_FROM_CC_ID, and TRANSFER_TO_CC_ID. Financial indicators such as HEADER_PAID, HEADER_CANCELLED, CANCELLED_FLAG, CURRENCY, and INVOICE_FULL_AMOUNT (stored as VARCHAR2(4000)) quantify the dealing. Descriptive columns include CUSTOMER_NAME, SUPPLIER_NAME, ORGANIZATION_NAME, CONTACT_NAME, INVOICE_CONTACT, AUTHORIZED_BY, and the ADDRESS_LINE1–4, CITY, PROVINCE, POSTAL_CODE, and COUNTY fields, along with the surrogate keys ADDRESS_ID, CONTACT_ID, CUSTOMER_ID, SUPPLIER_ID, and ORGANIZATION_ID. The flexfield descriptors _KF:CODE_COMBINATIONS:FROM and _KF:CODE_COMBINATIONS:TO expose the code combinations.

Common Use Cases and Queries

Typical usage includes reconciling finance headers transferred between ledgers, auditing cancelled or unpaid dealings, and building supplier/customer exposure reports. A representative query retrieving header details with source ledger context is:

  • SELECT header_id, customer_name, supplier_name, currency, invoice_full_amount, set_of_books_from, set_of_books_to, transfer_status, transfer_date FROM apps.otfv_finance_headers WHERE set_of_books_from = '&ledger_name';
  • Filtering outstanding balances: SELECT header_id, header_paid, header_cancelled, transfer_status FROM apps.otfv_finance_headers WHERE header_paid = 'N' AND cancelled_flag = 'N';
  • Joining headers to GL_SETS_OF_BOOKS via TRANSFER_FROM_SET_OF_BOOKS_ID for ledger-name resolution, or to HZ_CUST_ACCOUNTS via CUSTOMER_ID for receivables-side reporting.

Because the view is security-aware through FND_GLOBAL, queries respect the responsibility's operating unit and ledger context, making it suitable for embedded BI dashboards and extract routines.