Results for “debit_auth_method”
37 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
IBY_PMT_INSTR_USES_ALL is a Payments (IBY) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that records the assignment, or "use," of a payment instrument by a specific party, payment flow, and payment function. Each row represents one instrument usage record — for example, a bank account or credit card assigned to a supplier or customer for a particular disbursement or receipt function. The table acts as the source of instrument selection rules in the Oracle Payments funds capture and disbursement engines, driving which account or card is used when a payment is processed.
From a heuristic Data Vault modeling perspective, this object is classified as hub-leaning. It carries a surrogate primary key (INSTRUMENT_PAYMENT_USE_ID) that uniquely identifies each instrument-usage assignment, and the composite unique key formed by PAYMENT_FLOW, PAYMENT_FUNCTION, INSTRUMENT_TYPE, INSTRUMENT_ID, and EXT_PMT_PARTY_ID provides a natural business key across the assignment dimensions. The presence of descriptive and lifecycle columns (start/end dates, debit authorization attributes, DFF attributes) suggests a hybrid role, combining core assignment identity with satellite-style context.
Key Information Stored
The most operationally significant columns include:
INSTRUMENT_PAYMENT_USE_ID— surrogate primary key (IBY_PMT_INSTR_USES_ALL_PK) and the join key to dependent objects.PAYMENT_FLOW— identifies whether the instrument is used for disbursements, funds capture, or both.PAYMENT_FUNCTION— specifies the functional role (e.g., payment, refund) the instrument serves.INSTRUMENT_TYPE— the category of instrument, such as bank account or credit card.INSTRUMENT_ID— the specific instrument (bank account ID or card ID) assigned.EXT_PMT_PARTY_ID— the external party (supplier, customer, or employee) to whom the instrument is assigned.ORDER_OF_PREFERENCE— ranking used when multiple instruments qualify for the same party and function.START_DATE/END_DATE— effective dating that governs when the assignment is valid.DEBIT_AUTH_FLAG,DEBIT_AUTH_METHOD,DEBIT_AUTH_REFERENCE,DEBIT_AUTH_BEGIN,DEBIT_AUTH_END— debit authorization details, chiefly relevant for funds-capture scenarios.- Standard WHO columns (
CREATED_BY,CREATION_DATE,LAST_UPDATED_BY,LAST_UPDATE_DATE,LAST_UPDATE_LOGIN) andOBJECT_VERSION_NUMBERfor audit and optimistic locking. - DFF columns
ATTRIBUTE_CATEGORYthroughATTRIBUTE15for extensibility.
Common Use Cases and Queries
The table is queried to determine which instrument a party will use for a given flow and function, to validate effective-dated assignments, and to report on instrument usage for reconciliation and audit purposes.
Typical SQL pattern — find the active instrument assignment for a party and flow:
SELECT instrument_payment_use_id,
instrument_type,
instrument_id,
order_of_preference,
start_date,
end_date
FROM iby.iby_pmt_instr_uses_all
WHERE ext_pmt_party_id = :party_id
AND payment_flow = :flow
AND payment_function = :function
AND TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, SYSDATE)
ORDER BY order_of_preference;
Common reporting uses include listing all instruments by supplier for disbursement configuration, auditing expired assignments, and identifying parties with multiple preference-ranked instruments.
Related Objects
The documented foreign-key relationship links this table to IBY_FNDCPT_TX_EXTENSIONS via INSTR_ASSIGNMENT_ID referencing INSTRUMENT_PAYMENT_USE_ID, connecting instrument assignments to funds-capture transaction extension records. Other significant dependents and references include the instrument definition tables (IBY_EXT_BANK_ACCOUNTS_ALL and IBY_CREDITCARD_ALL) reached through INSTRUMENT_ID and INSTRUMENT_TYPE, the external party reference table (IBY_EXTERNAL_PAYEES_ALL) reached through EXT_PMT_PARTY_ID, and the Oracle Payments setup views and APIs that read instrument usage when building payment instructions. Together these objects form the instrument assignment and funds-capture data model used throughout the IBY module.
-
This table holds the mandate information for the bank accounts
-
"This table contains records of the relationship between payment instruments and Payer/Payee. Data can be entered manually. IBY_PMT_INSTR_USES_ALL table assigns payment instruments to external party payers and payees. This table is shared
-
IBY_TRXN_SUMMARIES_ALL contains information about each payment request. This table is used for both online and offline payment transactions. The information contained in this table is generic in nature to cover the various payment inst
-
IBY_TRXN_SUMMARIES_ALL contains information about each payment request. This table is used for both online and offline payment transactions. The information contained in this table is generic in nature to cover the various payment inst
-
eTRM - IBY Tables and Views 12.2.2
Stores the user privilege settings for viewing sensitive data in iPayment operations UI
-
eTRM - IBY Tables and Views 12.1.1
Stores the user privilege settings for viewing sensitive data in iPayment operations UI