Results for “funds_capture”

50+ results




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

Overview

APPS.OKX_RCPT_METHOD_ACCOUNTS_V is a reporting and integration view in Oracle E-Business Suite that exposes the payment instrument accounts available for use as receipt methods within the Order-to-Cash and payments infrastructure. The view consolidates two distinct categories of stored payment instruments — external bank accounts and credit cards — into a single, uniform result set that downstream forms, lookups, and integrations can query without concerning themselves with the underlying entity model. Its design reflects the Oracle Payments (IBY) architecture introduced in release 12, where payment instrument usage is decoupled from receipt method configuration and stored centrally in IBY_PMT_INSTR_USES_ALL.

The defining characteristic of this view is its restriction to instruments whose PAYMENT_FLOW is 'FUNDS_CAPTURE'. This is directly relevant to the search term "funds_capture": the view intentionally filters to instruments designated for the funds capture process — that is, inbound receipt processing where funds are drawn from a customer's account or card. Instruments configured for funds disbursement (outbound payments) are excluded. The view therefore acts as the funds-capture-specific slice of the broader payment instrument repository, which is exactly why it is associated with receipt method account selection.

Underlying Base Objects

The view is defined over several core Oracle Payments, Receivables/Trading Community, and lookup objects. The principal IBY objects are IBY_PMT_INSTR_USES_ALL, which stores each instrument-payment-use assignment including the payment flow and instrument type; IBY_EXT_BANK_ACCOUNTS, which holds external (customer) bank account details such as account number, masked number, branch, start and end dates, and currency; and IBY_EXTERNAL_PAYERS_ALL, which links external payers to their customer accounts and site uses. Two supporting objects round out the bank-account branch of the UNION: HZ_PARTIES supplies the bank party name, and HZ_CUST_SITE_USES_ALL provides the customer site use and operating unit context.

The credit card branch of the UNION draws on IBY_CREDITCARD for card number, masked card number, issuer name, issuer identifier, and expiry date, together with IBY_CREDITCARD_ISSUERS_VL for issuer-level attributes. IBY_CREDITCARD_ISSUERS_VL being a value-set view of issuers reflects the standard Oracle pattern for exposing credit card issuer reference data. FND_GLOBAL is referenced for session context (such as ORG_ID resolution), and FND_LOOKUPS supplies lookup meaning for coded values. Note that the ETRM documentation lists HZ_CUST_SITE_USES_ALL, HZ_PARTIES, IBY_EXTERNAL_PAYERS_ALL, IBY_EXT_BANK_ACCOUNTS, and IBY_PMT_INSTR_USES_ALL as synonyms owned by APPS — the view resolves through these synonyms rather than schema-qualified base tables.

Key Columns

  • ID1 / ID2 — The instrument_payment_use_id serves as the primary identifier; a constant '#' is returned as ID2, a legacy construct retained for compatibility with lookup-driven forms.
  • NAME — A concatenation of the bank account name or credit card number with the customer site location name, providing a human-readable disambiguation label.
  • DESCRIPTION — The masked bank account number or masked credit card number, ensuring sensitive values are not fully exposed.
  • BANK_NAME / BANK_ACCOUNT_ID / BANK_ACCOUNT_NUM / BANK_BRANCH_ID — Bank and account identification attributes; for cards, these map to issuer name, issuer ID, card number, and a fixed branch value of 1.
  • ACCOUNT_TYPE — The instrument type from IBY_PMT_INSTR_USES_ALL, indicating the class of payment instrument.
  • CUSTOMER_ID / CUSTOMER_SITE_USE_ID / ORG_ID — Customer account, site use, and operating unit identifiers used for security and filtering.
  • START_DATE_ACTIVE / END_DATE_ACTIVE / STATUS — Validity window and derived status (A for active, I for inactive) computed by comparing SYSDATE to the account start and end dates.
  • SET_OF_BOOKS_ID, MULTI_CURRENCY_FLAG, RECEIPT_MULTI_CURRENCY_FLAG, CONTACT_* — Placeholder columns returned as NULL to satisfy the expected column contract of the consuming forms or APIs.

Common Use Cases and Queries

This view is typically queried when resolving which payment instruments a customer may use for a funds capture receipt, when populating a receipt method account list of values, or when auditing active versus expired instruments. A representative query filtering active instruments for a customer follows:

  • SELECT id1, name, description, account_type, status FROM apps.okx_rcpt_method_accounts_v WHERE customer_id = :p_customer_id AND status = 'A';
  • SELECT bank_name, bank_account_num, currency_code FROM apps.okx_rcpt_method_accounts_v WHERE org_id = :p_org_id;

Because the view already restricts to PAYMENT_FLOW = 'FUNDS_CAPTURE', no additional flow predicate is required. Its UNION structure guarantees consistent column shape across bank and card instruments, making it suitable for direct attachment as a Lov or report data source. For customers with multiple instruments, joining to IBY_PMT_INSTR_USES_ALL on id1 recovers additional usage attributes not exposed by the view.