Results for “payment_currency_code”

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

Overview

IBY_XML_FD_PMT_1_0_V is an APPS-owned database view in the Oracle E-Business Suite Payments (IBY) module. It materializes a single outbound payment record as a structured XML document conforming to the Payment (PMT) message format, version 1.0, used by Oracle Payments' funds disbursement and extract generation framework. The view wraps the XMLELEMENT constructor to produce an XMLType instance whose root element is OUTBOUNDPAYMENT, containing nested elements for payment source information, payment identification, dates, status, payee, payee bank account, amount, and payment method. Positioned within IBY's extract-generation architecture, the view functions as the XML-producing layer that feeds payment instruction formatting, bank communication, and print programs. It is a read-only, non-stored object; all data is derived at query time from the underlying payments tables and packaged PL/SQL functions, so no physical storage or index maintenance applies.

Underlying Base Objects

The documented referenced objects confirm the view's role as a thin XML projection over core Payments data. IBY_PAYMENTS_ALL (synonym to the payments base table) supplies most scalar columns, including calling application, payment service request, function, organization, document category, sequence, dates, status, currency, method, and amount. IBY_DOCS_PAYABLE_ALL provides document-level payment attributes. FND_CURRENCIES_VL contributes currency meaning via the currency code lookup. Helper views IBY_EXT_FD_PMT_1_0_V and packages IBY_EXT_WRAP_PUB, IBY_FD_EXTRACT_GEN_PVT, IBY_EXTRACTGEN_PVT, and IBY_UTILITY_PVT furnish transformations — notably IBY_FD_EXTRACT_GEN_PVT.GET_PMT_PMTERRAGG for payment attributes and the payee/payee-bank-account XML fragments. FND_GLOBAL resolves runtime session context such as the current application and organization, while XMLTYPE is the SQL/XML datatype constructor target. The view therefore joins relational payment rows to lookup meanings and XML serialization logic in one pass.

Key Columns

• PAYMENT_ID — Primary key driving extraction; passed into the payment-attributes function.
• CALLING_APP_ID / APPLICATION_NAME — Originating application (e.g., Payables) and its name.
• PAYMENT_SERVICE_REQUEST_ID — Correlates the payment to its payment service request.
• PAYMENT_FUNCTION / PAYMENT_FUNCTION_MEANING — Functional category code and decoded meaning.
• PAYMENT_ORG_ID / PAYMENT_ORG_TYPE / PAYMENT_ORG_NAME — Payer organization internal ID, type code/meaning, and name.
• PAYMENT_DOC_CATEGORY, PAYMENT_DOC_SEQUENCE_NAME, PAYMENT_DOC_SEQUENCE_VALUE — Document category and sequence identification.
• PAYMENT_REFERENCE_NUMBER, PAPER_DOCUMENT_NUMBER — Payment reference and check number.
• PAYMENT_DATE, PAYMENT_DUE_DATE, MATURITY_DATE — Key payment dates.
• PAYMENT_STATUS, PAYMENT_STATUS_MEANING — Status code and decoded meaning.
• PAYMENT_AMOUNT, PAYMENT_CURRENCY_CODE, PAYMENT_AMOUNT_TEXT — Numeric amount, currency, and amount-in-words text.
• PAYMENT_METHOD_CODE, PAYMENT_METHOD_NAME, PAYMENT_METHOD_ATTR_CAT — Payment method identifiers and conditional attributes.
• EXTERNAL_BANK_ACCOUNT_ID — Controls whether the payee bank account XML fragment is emitted.

Common Use Cases and Queries

Typical scenarios include troubleshooting extract output for a specific payment, verifying the XML payload emitted to a bank, and validating payee and bank-account eligibility before funds disbursement. Because the view already returns XMLType, callers usually fetch the complete document or extract individual nodes with SQL/XML functions:

• Retrieve a full XML document: SELECT * FROM apps.iby_xml_fd_pmt_1_0_v WHERE payment_id = :p_id;
• Extract scalar nodes: SELECT x.payment_number, x.status_code FROM apps.iby_xml_fd_pmt_1_0_v x WHERE x.payment_id = :p_id; using the aliased XML columns exposed by the view.
• Confirm bank-account inclusion: check whether the PAYEEBANKACCOUNT element is populated by filtering on external_bank_account_id IS NOT NULL.
• Audit method attributes: group by payment_method_code to identify records where conditional method attributes are null.

Because each call re-executes the XML constructors and packaged functions, restrict queries to specific payment IDs rather than full-table scans.