Results for “funding_type_code”

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

Overview

OKL_FUND_REQ_HEADERS_UV is an APPS-owned database view in Oracle E-Business Suite Release 12.1.1 and 12.2.2, delivered as part of the OKL – Lease and Finance Management (formerly Oracle Lease Management) product. It is the user interface view for the funding request header and consolidates funding request data drawn from the lease transaction tables with descriptive, language-sensitive attributes sourced from vendor, currency, lookup, and terms objects. The view is intended for direct presentation in the funding request pages and related inquiry screens rather than for transactional write-back; all data manipulation occurs against the underlying base tables.

The view exposes translated and derived columns, including meanings decoded from FND_LOOKUPS, currency names from FND_CURRENCIES_TL, and a concatenated vendor site address. Because all descriptive join columns are joined to USERENV('LANG'), the view returns data in the session's current language, making it suitable for multi-language deployments. The column FUND_DESCRIPTION, which corresponds to the user search term "fund_description," is mapped from OKL_TRX_AP_INVOICES_TL.DESCRIPTION and carries the funding request description in the session language.

As a data dictionary object the view is reported VALID in APPS and is referenced in the ETRM (Electronic Technical Reference Manual) for 12.2.2. Organizations typically treat it as an interface for custom reporting, diagnostics, and read-only integration into external systems.

Underlying Base Objects

The view is defined over the following documented objects:

• OKL_TRX_AP_INVOICES_B (synonym) – base funding request header, aliased H; supplies fund id, fund number, currency, payment method, funding type, vendor site, contract id, dates, status, and transaction type.
• OKL_TRX_AP_INVOICES_TL (synonym) – translated table supplying the funding request description HL.DESCRIPTION.
• PO_VENDORS (view) - vendor master for vendor id, number, and name.
• PO_VENDOR_SITES_ALL (view) – vendor sites for site code, pay flag, and address components.
• FND_CURRENCIES_TL (synonym) – translated currency name.
• FND_LOOKUPS (view) – four lookup instances for payment method, funding type, transaction status, and invoice type meanings.
• AP_TERMS_V (view) – payment terms name.
• PO_LOOKUP_CODES (view) – displayed field for the pay group lookup code.
• OKL_FUNDING_PVT (package) – called to compute GET_CONTRACT_LINE_FUNDED_AMT, producing FUND_TOTAL.
• FND_GLOBAL (package) – indirectly referenced for environment context such as USERENV('LANG') and ORG_ID resolution.

Key Columns

• FUND_ID – primary identifier from OKL_TRX_AP_INVOICES_B.ID.
• FUND_NUMBER – vendor invoice number identifying the funding request.
• FUND_DESCRIPTION – translated description of the funding request; the column sought by the "fund_description" search.
• CURRENCY_CODE / CURRENCY_NAME – funding currency and its translated name.
• PAYMENT_METHOD_CODE / PAYMENT_METHOD_NAME and FUNDING_TYPE_CODE / FUNDING_TYPE_NAME – coded values and decoded lookup meanings.
• FUND_DUE_DATE, FUND_APPROVED_DATE, DATE_ENTERED – key funding timeline dates.
• FUND_TOTAL – computed contract line funded amount returned by OKL_FUNDING_PVT.
• TRX_STATUS_CODE / TRX_STATUS_NAME – funding request status.
• VENDOR_ID, VENDOR_NUMBER, VENDOR_NAME, VENDOR_SITE_CODE, VENDOR_SITE_ADDRESS, PAY_SITE_FLAG – vendor and site details.
• ORG_ID – multi-org operating unit identifier, used for security filtering.

Common Use Cases and Queries

The view supports funding request inquiries, approval monitoring, vendor payment reconciliation, and custom extracts. A return to a specific funding request, including its description, may be issued as:

• SELECT fund_id, fund_number, fund_description, trx_status_name, fund_total FROM okl_fund_req_headers_uv WHERE fund_description IS NOT NULL;
• SELECT fund_number, vendor_name, currency_name, fund_approved_date FROM okl_fund_req_headers_uv WHERE org_id = :p_org_id ORDER BY fund_approved_date DESC;
• SELECT fund_id, fund_description, fund_total FROM okl_fund_req_headers_uv WHERE funding_type_code = 'SUPPLIER' AND trx_status_name = 'APPROVED';
• SELECT fund_number, vendor_site_address FROM okl_fund_req_headers_uv WHERE pay_group_lookup_code = :p_pay_group;

Because translation columns filter on USERENV('LANG'), queries executed under different language sessions return localized descriptions and lookup meanings. Reports should always constrain by ORG_ID for multi-organization security, and heavy extraction queries should account for the function call to OKL_FUNDING_PVT.GET_CONTRACT_LINE_FUNDED_AMT, which is evaluated per row.