Search Results payment_reference_number




Overview
Explore in AI Chat

Overview

APPS.IBY_EXT_FD_PMT_1_0_V is an Oracle E-Business Suite view belonging to the Payments (IBY) module. It exposes the payload of the Oracle Payments Funds Disbursement extract format "PMT_1_0", representing a single payment instruction or payment record in the flattened, denormalized structure required by external payment formatting engines and delivery channels. In releases 12.1.1 and 12.2.2 the object serves as the primary read interface for downstream payment processing programs — Payment Instruction formatting, payment file generation, and bank transmission — that consume extraction data staged by the Payment Process Request (PPR).

Because the view is a thin projection over a version table, it is not a transactional entity. It is a reporting and integration surface: queries against it return the same payment attributes that the extract generator persists, allowing callers, custom concurrent programs, and business intelligence tools to inspect or re-use formatted payment data without re-executing the extraction logic. The user search term payment_reference_number maps directly to a column in this view and is frequently the join and search key for locating a specific disbursement.

Underlying Base Objects

Per the ETRM metadata, the view is defined over the version table IBY_EXT_FD_PMT_1_0_VT and draws on the APPS packages FND_GLOBAL and IBY_FD_EXTRACT_GEN_PVT:

  • IBY_EXT_FD_PMT_1_0_VT — the physical extraction/version table holding the payment extract rows. The view selects from this table and orders results by payment_reference_number.
  • IBY_FD_EXTRACT_GEN_PVT — the extraction generation package that populates the version table for a given payment service request. It defines the canonical PMT_1_0 payload semantics projected by this view.
  • FND_GLOBAL — the standard EBS package providing session context (user, responsibility, org) used in the view's definition for multi-org and security filtering.

The relationship is therefore one of projection: IBY_EXT_FD_PMT_1_0_V presents the version table's rows, and the version table itself is the persisted output of the extraction generation package. No direct joins to PAYMENTS, IBY_PAYMENTS_ALL, or IBY_PAY_INSTRUCTIONS_ALL occur inside the view; the payment_id and payment_instruction_id columns are carried through from the extract rather than resolved at query time.

Key Columns

  • payment_reference_number — the payment's unique reference as used in the extract; also the view's ORDER BY key, making it the principal lookup column.
  • payment_id / payment_instruction_id / payment_service_request_id — identifiers linking the row back to the payment, its instruction grouping, and the originating PPR.
  • payment_function / payment_function_meaning — whether the row is a payment or a remittance advice (e.g., PAYMENT, REMITTANCE).
  • payment_status / payment_status_meaning — the disbursement or instruction status at extraction time.
  • payment_amount, payment_currency_code, payment_amount_text — numeric amount, ISO currency, and the formatted amount string used in the output file.
  • payment_method_code, payment_method_name, payment_method_attr_cat — the disbursement method (check, wire, EFT, etc.) and its attribute category.
  • payee_party_id, payee_party_site_use_id, beneficiary_name — the payee and its site.
  • internal_bank_account_id, external_bank_account_id, legal_entity_id — the disbursing and receiving bank accounts and the owning legal entity.
  • payment_date, payment_due_date, maturity_date, anticipated_value_date, void_date — the full date set carried in the extract.
  • delivery_channel_code, delivery_channel_format_value — the transmission channel and format.
  • remittance_message1–3, payment_text_message1–3, payment_details — free-form and structured remittance data.
  • payment_doc_category, payment_doc_sequence_name, payment_doc_sequence_value, paper_document_number — document sequencing and printed document data.
  • positive_pay_file_created_flag — a customer-specific extension added in this view's text.

Common Use Cases and Queries

Typical uses include reconciliation of formatted payments, investigation of a specific payment by reference, feeding custom bank files, and reports on payment methods or amounts within a payment service request. The ORDER BY on payment_reference_number means range predicates perform predictably.

  • Locate a single disbursement by its reference number.
  • List all payments produced for a given payment process request.
  • Extract payee, amount, and remittance data for bank file reconciliation.
SELECT payment_reference_number, payment_id,
       payment_amount, payment_currency_code,
       payment_status_meaning, payment_date
FROM   apps.iby_ext_fd_pmt_1_0_v
WHERE  payment_reference_number = :p_ref_num;

SELECT payment_reference_number, payment_amount,
       payment_method_code, payee_party_id
FROM   apps.iby_ext_fd_pmt_1_0_v
WHERE  payment_service_request_id = :p_psr_id;

Because the view filters through FND_GLOBAL and depends on IBY_FD_EXTRACT_GEN_PVT having run, results are limited to payments for which the PMT_1_0 extract has been generated.