Search Results ozf_fund_requests_v




Overview
Explore in AI Chat

Overview

OZF_FUND_REQUESTS_V is a Trade Management (OZF) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a denormalized, presentation-ready representation of the fund request tracking data stored in OZF_FUND_REQUESTS, enriched with descriptive fund attributes resolved from OZF_FUND_DETAILS_V. In the Trade Management fund lifecycle, a fund request captures a requester's demand for budget to be moved between funds — either transferred to a receiving fund or requested from a source fund. The view exposes both sides of that relationship in a single row, making it the primary read interface for fund transfer reporting, approval workflow inquiries, and integration extracts.

Because the view performs the fund lookups internally, consumers do not need to join to the fund details view themselves. This is particularly relevant for the TRANSFER_FM_ID column, which is the identifier of the originating ("from") fund in a transfer request and is a frequently searched attribute in transfer reconciliation and audit scenarios.

Underlying Base Objects

The view is defined over three documented objects. The driving object is the OZF_FUND_REQUESTS synonym, which supplies all transactional and workflow-related columns such as FUND_REQUEST_ID, FUND_REQUEST_STATUS, the requested and approved amounts, dates, exchange rate attributes, and the WHO columns. Two instances of OZF_FUND_DETAILS_V are joined to it under the aliases OZFFUN1 and OZFFUN2.

The join is an inner join in both cases, so a fund request row is only returned when both the transfer-to fund and the transfer-from fund resolve to valid fund records.

Key Columns

The columns can be grouped functionally. Request identity and workflow columns include FUND_REQUEST_ID, FUND_REQUEST_STATUS, REQUESTER, APPROVER, FUND_REQUEST_DATE, DATE_REQUIRED_BY, FUND_TRANSFER_DATE, REQUESTED_AMOUNT, APPROVED_AMOUNT, and RECEIVED_AMOUNT. Transfer routing columns include TRANSFER_TO_TYPE and TRANSFER_TO_ID for the destination, and TRANSFER_FM_TYPE and TRANSFER_FM_ID for the source.

Currency and conversion attributes include TO_CURRENCY_CODE, FM_CURRENTY_CODE (the source fund currency, retaining the historical spelling used in the base table), EXCHANGE_RATE_TYPE, EXCHANGE_RATE_DATE, and EXCHANGE_RATE. Fund context columns sourced from OZF_FUND_DETAILS_V include AVAILABLE_BUDGET, TOTAL_BUDGET, HOLDBACK_AMT, DISTRIBUTED_AMOUNT, TRANSFERED_IN_AMT, and TRANSFERED_OUT_AMT for the destination fund. Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and the concurrency column OBJECT_VERSION_NUMBER are also projected. TRANSFER_FM_ID is the key attribute for identifying the fund from which budget is being moved.

Common Use Cases and Queries

Typical uses include fund transfer reconciliation, approval aging reports, budget movement analysis across the OZF fund hierarchy, and integration extracts feeding external trade promotion systems. A common query locates all requests originating from a specific fund via TRANSFER_FM_ID:

  • SELECT fund_request_id, fund_request_status, transfer_fm_id, transfer_to_id, requested_amount, approved_amount FROM ozf_fund_requests_v WHERE transfer_fm_id = :p_fund_id;
  • SELECT fund_request_id, fund_request_status, requester, date_required_by FROM ozf_fund_requests_v WHERE fund_request_status = 'NEW' ORDER BY date_required_by;
  • SELECT fund_request_id, transfer_fm_id, transfer_to_id, requested_amount, exchange_rate FROM ozf_fund_requests_v WHERE fund_request_date BETWEEN :p_start AND :p_end;

Note that unaliased OZFFUN2 columns such as FUND_NUMBER and OWNER_FULL_NAME appear twice in the projection list, so queries should reference them by position or use explicit aliases when materializing results.