Search Results transfer_to_number

Overview

APPS.OZF_FUND_REQUESTS_V is a reporting and integration view within the Oracle E-Business Suite (EBS) Trade Management (formerly Oracle Marketing) module, part of the OZF (Oracle Funds) schema family. It presents fund transfer requests together with denormalized attributes of both the originating and destination funds, allowing callers to resolve a complete transfer picture from a single query. In EBS 12.1.1 and 12.2.2 the view is owned by the APPS account and is typically consumed by concurrent programs, OBIEE/XML Publisher reports, and inbound integration interfaces that need fund request details without joining multiple fund views manually.

The view is defined over OZF_FUND_REQUESTS (exposed as a synonym) joined to OZF_FUND_DETAILS_V twice — once aliased OZFFUN1 for the destination fund (transfer_to_id) and once aliased OZFFUN2 for the source fund (transfer_fm_id). It therefore behaves as a two-sided fund transfer snapshot. The currency_code_tc column referenced by the user originates from OZF_FUND_DETAILS_V and appears twice in the projection, once per fund side.

Underlying Base Objects

• OZF_FUND_REQUESTS (synonym) — the driving entity holding the fund request header: identifiers, audit columns (WHO columns), request status, transfer-to/from type and id, amounts, dates, exchange rate attributes, and workflow/request metadata.
• OZF_FUND_DETAILS_V (view, referenced twice) — supplies fund-level descriptive and financial attributes for each side of the transfer, including short name, fund number, currency_code_tc, owner name, and budget amounts.

The join predicates are OZFREQ.transfer_to_id = OZFFUN1.fund_id and OZFREQ.transfer_fm_id = OZFFUN2.fund_id. Because both sides are mandatory equi-joins against a view, rows will only appear when both the destination and originating fund records resolve in OZF_FUND_DETAILS_V.

Key Columns

• fund_request_id — primary identifier of the fund request.
• fund_request_status, transfer_type, transfer_to_type, transfer_to_id, transfer_fm_type, transfer_fm_id — request lifecycle and direction attributes.
• currency_code_tc — the transaction currency of the associated fund, sourced from OZF_FUND_DETAILS_V. It is projected twice: OZFFUN1.currency_code_tc (destination fund) and OZFFUN2.currency_code_tc (source fund). The "_TC" suffix denotes the transaction (functional/ledger) currency code.
• short_name, fund_number, owner_full_name — descriptive fund attributes for each side.
• available_budget, total_budget, holdback_amt, distributed_amount, transfered_in_amt, transfered_out_amt — financial measures from the destination fund side (OZFFUN1).
• requested_amount, approved_amount, received_amount — amounts recorded on the request itself.
• to_currency_code, exchange_rate_type, exchange_rate_date, exchange_rate — currency conversion attributes for cross-currency transfers.
• date_required_by, fund_request_date, fund_transfer_date, description, requester, approver — scheduling, narrative, and approval context.
• WHO columns (creation_date, created_by, last_update_date, last_updated_by, last_update_login) and program/request columns (request_id, program_application_id, program_id, program_update_date) for audit and traceability.

Common Use Cases and Queries

Typical uses include fund transfer reconciliation, cross-currency transfer reporting, and dashboards showing pending or approved fund requests with both source and destination fund context. Because both currency_code_tc projections exist, analysts frequently need to alias them explicitly.

• List fund requests joining source and destination currency codes.
• Report approved transfers with exchange rate and to_currency_code for FX review.
• Reconcile budget consumption via available_budget and transfered_out_amt.

Sample query:

SELECT fund_request_id, fund_request_status,
  OZFFUN2.CURRENCY_CODE_TC source_ccy,
  OZFFUN1.CURRENCY_CODE_TC dest_ccy,
  to_currency_code, exchange_rate,
  requested_amount, approved_amount, received_amount
FROM APPS.OZF_FUND_REQUESTS_V
WHERE fund_request_status = 'APPROVED';

Note that the view is read-only and reflects current fund details at query time; historical currency snapshots are not preserved, so point-in-time reporting should rely on the request's own to_currency_code and exchange_rate columns.