Search Results iby_ext_fd_pmt_1_0_v




Overview
Explore in AI Chat

Overview

IBY_EXT_FD_PMT_1_0_V is an Oracle E-Business Suite view in the APPS schema belonging to the IBY (Payments) product. It is a key component of the Oracle Payments funds disbursement and external extract framework, exposing payment instruction data in a flattened, lookup-enriched form suitable for reporting, integration, and payment file generation. The view presents one row per payment instruction, combining transactional payment attributes with translated meanings drawn from Oracle Payments lookup tables and package functions. Its role is primarily as a data source for extract programs, custom reports, and interface feeds that must reconcile internal payment data with externally received or transmitted payment files.

Underlying Base Objects

The view is documented over three referenced base objects: IBY_EXT_FD_PMT_1_0_VT, IBY_FD_EXTRACT_GEN_PVT, and FND_GLOBAL. The principal base object is IBY_EXT_FD_PMT_1_0_VT, the "VT" (view table) holding the raw payment instruction columns such as PAYMENT_INSTRUCTION_ID, PAYMENT_ID, PAYMENT_FUNCTION, PAYMENT_STATUS, and ORG_ID. The view aliases this object as PMT and joins it to lookup sources and codes. IBY_FD_EXTRACT_GEN_PVT is the Payments extract generator package whose PL/SQL functions enrich the result, including GET_PAYMENT_AMOUNT_TEXT, GET_PAYMENT_AMOUNT_WITHHELD, and GET_ALLOTMENT_CODE, each invoked against PMT.PAYMENT_ID. FND_GLOBAL supplies session context, most notably the CALLING_APP_ID resolved through FNDAPP.APPLICATION_SHORT_NAME, identifying the application that initiated the payment service request (REQ.CALLING_APP_ID). The "1_0" suffix denotes the version 1.0 format definition of the extract view.

Key Columns

The view exposes identifiers and descriptive columns that together describe a payment instruction end-to-end. Central identifiers include PAYMENT_INSTRUCTION_ID, PAYMENT_ID, PAYMENT_SERVICE_REQUEST_ID, INTERNAL_BANK_ACCOUNT_ID, EXTERNAL_BANK_ACCOUNT_ID, LEGAL_ENTITY_ID, PAYEE_PARTY_ID, and PARTY_SITE_ID. Payment characteristics include PAYMENT_FUNCTION with its decoded PAYMENT_FUNCTION_LOOKUP.MEANING (the value users search for as "payment_function_meaning"), PAYMENT_METHOD_CODE with PAYMENT_METHODS.PAYMENT_METHOD_NAME, PAYMENT_STATUS with its lookup meaning, SETTLEMENT_PRIORITY, DELIVERY_CHANNEL_CODE, and BANK_CHARGE_BEARER. Financial amounts include PAYMENT_AMOUNT, PAYMENT_CURRENCY_CODE, DISCOUNT_AMOUNT_TAKEN, BANK_CHARGE_AMOUNT, DECLARATION_AMOUNT, and the derived amount text functions. Extended descriptive fields include DOCUMENT_CATEGORY_CODE, DOCUMENT_SEQUENCE_VALUE, PAYMENT_REFERENCE_NUMBER, PAYMENT_DATE, PAYMENT_DUE_DATE, MATURITY_DATE, UNIQUE_REMITTANCE_IDENTIFIER, URI_CHECK_DIGIT, PAYMENT_TEXT_MESSAGE1–3, REMITTANCE_MESSAGE1–3, and the bank instruction code/meaning pairs.

Common Use Cases and Queries

Typical applications include verifying that payment files generated by the extract match the internal instruction set, auditing payment function and status distributions, and building remittance advice data. A frequent requirement is decoding the stored payment function code, which the view performs through PAYMENT_FUNCTION_LOOKUP.MEANING. A representative query is:

  • SELECT payment_instruction_id, payment_reference_number, payment_function, payment_function_meaning, payment_status, payment_status_meaning, payment_amount, payment_currency_code FROM iby_ext_fd_pmt_1_0_v WHERE org_id = :p_org_id AND payment_date BETWEEN :p_from AND :p_to;
  • Aggregate by function: SELECT payment_function, payment_function_meaning, COUNT(*), SUM(payment_amount) FROM iby_ext_fd_pmt_1_0_v GROUP BY payment_function, payment_function_meaning;
  • Reconcile a specific instruction: SELECT * FROM iby_ext_fd_pmt_1_0_v WHERE payment_instruction_id = :p_instruction_id;

Because the view calls package functions per row, large unbound queries can be expensive; constrain results by ORG_ID, PAYMENT_DATE, or PAYMENT_INSTRUCTION_ID wherever possible.