IBY Tables (181)
IBY - Payments — documented tables from Oracle EBS ETRM 12.2.2. Click any name for its documentation, columns and AI summary.
| Table | Columns | Description |
|---|---|---|
IBY_ACCOUNT_OWNERS |
11 | This table contains records of the account owners of the external bank accounts entered manually. This table corresponds to the Banking det |
IBY_ACCPPMTMTHD |
12 | IBY_ACCPPMTMTHD contains a list of all the payment instrument methods that are accepted by a iPayment. |
IBY_ACCTTYPE |
11 | IBY_ACCTTYPE contains a list of various account types supported. For example for bank account, the account types could be Checking, Savi |
IBY_ACCT_PMT_PROFILES_B |
24 | IBY_ACCT_PMT_PROFILES stores account-related information that completes the specification of the handling of payment instructions. Entries i |
IBY_ACCT_PMT_PROFILES_TL |
11 | IBY_ACCT_PMT_PROFILES stores account-related information that completes the specification of the handling of payment instructions. Entries i |
IBY_ACK_PMT_ALL |
33 | Provided to store acknowledgement information at payment level. |
IBY_ACK_PMT_ERRORS |
10 | Provided to store acknowledgement error(s) information at payment level. |
IBY_ACK_READERS |
11 | |
IBY_ACTIVITY |
52 | IBY_ACTIVITY stores scheduler related activities. |
IBY_APPLICABLE_PMT_MTHDS |
16 | IBY_APPLICABLE_PMT_MTHDS stores the payment method applicability information for company policy-based factors. The factors include First Par |
IBY_APPLICABLE_PMT_PROFS |
13 | IBY_APPLICABLE_PMT_PROFS maps payment methods to payment process profiles. Since administrators can define both payment methods and payment |
IBY_AR_DOC_HEADER_GT1 |
36 | |
IBY_AR_DOC_LINES_GT |
15 | |
IBY_BANKACCT |
22 | IBY_BANKACCOUNTstores bank account related information of the customer(payer) or payee. |
IBY_BANK_ACK_STATUSES |
10 | Provided to store Mapping of acknowledgement codes to ISO codes. |
IBY_BANK_INSTRUCTIONS_B |
12 | IBY_BANK_INSTRUCTIONS stores bank instructions that are used as lookup values for payment process profiles and external payee setup. This ta |
IBY_BANK_INSTRUCTIONS_TL |
12 | IBY_BANK_INSTRUCTIONS stores bank instructions that are used as lookup values for payment process profiles and external payee setup. This ta |
IBY_BATCHES_ALL |
48 | "This table contains records of the settlement batch information which is updated by system while processing 'Create settlement Batches' pro |
IBY_BEPINFO |
54 | IBY_BEPKEYS stores information about the payment systems. |
IBY_BEPKEYS |
30 | IBY_BEPKEYS stores information about the payment systems accounts. |
IBY_BEPLANGS |
11 | IBY_BEPLANGS contains list of all the languages supported by the Back End Payment System |
IBY_BEP_ACCT_OPT_NAME_B |
13 | |
IBY_BEP_ACCT_OPT_NAME_TL |
12 | |
IBY_BEP_ACCT_OPT_VALS |
11 | |
IBY_CC_ISSUER_RANGES |
11 | Table contains card ranges for various credit card issuers. Used to remove structure from a credit card number before it is encrypted. |
IBY_CREDITCARD |
83 | IBY_CREDITACRD stores Credit Card related information of the customer(payer) or payee. |
IBY_CREDITCARD_H |
65 | Holds historical data for credit cards |
IBY_CREDITCARD_ISSUERS_B |
13 | Holds the list of accepted card brands |
IBY_CREDITCARD_ISSUERS_TL |
12 | Holds the list of accepted card brands |
IBY_DEBIT_AUTHORIZATIONS |
28 | This table holds the mandate information for the bank accounts |
IBY_DEFAULT_BEP |
14 | IBY_DEFAULT_BEP stores information that will allow a payment system account and funds capture process profile to be derived for a transactio |
IBY_DELIVERY_CHANNELS_B |
12 | IBY_DELIVERY_CHANNELS stores delivery channel information that is used as lookup values for external payee setup or documents payable. The t |
IBY_DELIVERY_CHANNELS_TL |
12 | IBY_DELIVERY_CHANNELS stores delivery channel information that is used as lookup values for external payee setup or documents payable. The t |
IBY_DOCS_PAYABLE_ALL |
120 | "This table contains records of the documents payable which are updated by system while processing 'Build payments' program. IBY_DOCS_PAYA |
IBY_DOCS_PAYABLE_GT |
81 | |
IBY_DOCS_PAYABLE_VAL_GT1 |
82 | |
IBY_DOCUMENTS_PAYABLE_H |
105 | IBY_DOCUMENTS_PAYABLE_H stores historical snapshots of documents payable. This table contains denormalized versions of documents payable fro |
IBY_DOCUMENT_LINES |
18 | IBY_DOCUMENT_LINES stores Oracle Payments' representation of individual line items for documents payable, such as invoice lines for an Oracl |
IBY_DOCUMENT_LINES_H |
21 | IBY_DOCUMENT_LINES_H stores historical snapshots of document line items. This table contains denormalized versions of document lines from sp |
IBY_ECAPP |
11 | IBY_ECAPP stores information about Electronic Commerce Applications registered with iPayment. Oracle Applications which integrate with iPaym |
IBY_EXTERNAL_PAYEES_ALL |
32 | "This table contains payment details of an external payee automatically created by the source product. For example when supplier or supplie |
IBY_EXTERNAL_PAYERS_ALL |
18 | "This table contains payment details of an external payer automatically created by the source product. For example when customer or custome |
IBY_EXTRACTS_B |
14 | Defines data extracts for payment file creation |
IBY_EXTRACTS_TL |
11 | |
IBY_EXTRACT_ACTIVATIONS |
10 | IBY_EXTRACT_ACTIVATIONS defines which computed fields within an extract are unnecessary for a particular format, with each row corresponding |
IBY_EXT_BANK_ACCOUNTS |
69 | "This table contains records of the external bank accounts entered manually. This table corresponds to the Banking details page of supplier |
IBY_EXT_PARTY_PMT_MTHDS |
13 | IBY_EXT_PARTY_PMT_MTHDS stores payment method applicability driven by the preferences of the external party. A payment method is applicable |
IBY_EXT_PAYEE_RELATIONSHIPS |
32 | "This table stores information about third party payment related relationships and related attributes. IBY_EXT_PAYEE_RELATIONSHIPS contain |
IBY_FNDCPT_PAYEE_APPL |
9 | IBY_FNDCPT_PAYEE_APPL is a mapping table between internal payees and operating units. One payee may be associated with many operating units. |
IBY_FNDCPT_PMT_CHNNLS_B |
28 | IBY_FNDCPT_PMT_CHNNLS defines all payment methods for the funds capture flow. Payment methods are categorized by instrument types. The inst |
IBY_FNDCPT_PMT_CHNNLS_TL |
12 | IBY_FNDCPT_PMT_CHNNLS defines all payment methods for the funds capture flow. Payment methods are categorized by instrument types. The inst |
IBY_FNDCPT_SYS_CC_PF_B |
52 | |
IBY_FNDCPT_SYS_CC_PF_TL |
12 | |
IBY_FNDCPT_SYS_DC_PF_B |
53 | |
IBY_FNDCPT_SYS_DC_PF_TL |
12 | |
IBY_FNDCPT_SYS_EFT_PF_B |
54 | |
IBY_FNDCPT_SYS_EFT_PF_TL |
12 | |
IBY_FNDCPT_TX_EXTENSIONS |
27 | "The data in this table will be created by the source products through the public API IBY_FNDCPT_TRXN_PUB, Create_Transaction_Extension and |
IBY_FNDCPT_TX_OPERATIONS |
8 | IBY_FNDCPT_TX_OPERATIONS stores associations between transaction extension entities and authorization or settlement transactions. |
IBY_FNDCPT_TX_XE_COPIES |
8 | IBY_FNDCPT_TX_XE_COPIES stores the copy relationship between transaction extension entities. This relationship is many-to-many, since during |
IBY_FNDCPT_USER_CC_PF_B |
13 | |
IBY_FNDCPT_USER_CC_PF_TL |
10 | |
IBY_FNDCPT_USER_DC_PF_B |
13 | |
IBY_FNDCPT_USER_DC_PF_TL |
10 | |
IBY_FNDCPT_USER_EFT_PF_B |
13 | |
IBY_FNDCPT_USER_EFT_PF_TL |
10 | |
IBY_FORMATS_B |
29 | Stores payment processing format types |
IBY_FORMATS_TL |
11 | |
IBY_F_CRDT_APP_STATUS_B |
31 | |
IBY_F_CRDT_APP_STATUS_TL |
12 | |
IBY_F_PC_RATES_ALL |
20 | |
IBY_F_T_CA_GRNTRS_B |
15 | |
IBY_F_T_CA_GRNTRS_TL |
11 | |
IBY_F_T_CA_GRNTR_H |
11 | |
IBY_F_T_CRDT_APPS_ALL_B |
49 | |
IBY_F_T_CRDT_APPS_ALL_TL |
11 | |
IBY_F_T_CRDT_APP_REVS |
14 | |
IBY_F_T_CRDT_APP_ST_H |
20 | |
IBY_F_T_EMAIL_NOTIF_LOG |
21 | |
IBY_GEN_DOCS_PAYABLE |
84 | IBY_GEN_DOCS_PAYABLE serves as a template for source product tables or views from which Oracle Payables can import documents payable. |
IBY_GEN_DOCUMENT_LINES |
22 | IBY_GEN_DOCUMENT_LINES serves as a template for source product tables or views from which Oracle Payables can import documents payable. |
IBY_G_MSG_TEMPLATES_B |
32 | |
IBY_G_MSG_TEMPLATES_TL |
11 | |
IBY_G_ST_TRANSITIONS |
28 | |
IBY_G_T_MESSAGES |
18 | |
IBY_G_T_MSG_REQ_LOG |
16 | |
IBY_HOOK_DOCS_IN_PMT_T |
30 | |
IBY_HOOK_PAYMENTS_T |
26 | |
IBY_INSTRHOLDER |
13 | IBY_INSTRHOLDER stores the information about the holder of the instrment. A payment instrument can be held by different users or payees or p |
IBY_INSTRUCT_SOURCE_APPS |
8 | IBY_INSTRUCT_SOURCE_APPS stores a list of source products that submitted documents to be paid in each payment instruction. |
IBY_INSTR_CREATION_RULES |
31 | IBY_INSTR_CREATION_RULES specifies how payments are grouped into payment instructions. Payment instructions are always grouped by internal b |
IBY_INTERMEDIARY_ACCTS |
19 | IBY_INTERMEDIARY_ACCTS defines intermediary bank account information. |
IBY_INTERNAL_PAYERS_ALL |
20 | IBY_INTERNAL_PAYERS_ALL stores payment-related attributes for the funds disbursement payment process for all first party payers. These attri |
IBY_IRF_PMT_AMOUNT |
13 | This table stores information pertaining to the payment amount risk factor involved in the payment request. A payment request that has huge |
IBY_IRF_PMT_FREQUENCY |
12 | This table stores information pertaining to the payment frequency risk factor. It basically has information about the frequency of purchase |
IBY_IRF_PMT_HISTORY |
12 | This table stores information pertaining to the payment history risk factor. The merchant can set up different time ranges which he consider |
IBY_IRF_PMT_HIST_RANGE |
13 | This table stores the frequency ranges information pertaining to the payment history risk factor. The customer can setup multiple frequency |
IBY_IRF_RISKY_INSTR |
16 | IBY_IRF_RISKY_INSTR stores information pertaining to the risk instrument risk factor. It has information about the merchant who sends the fi |
IBY_IRF_TIMEOF_PURCHASE |
13 | This table stores information pertaining to the time of purchase risk factor. The merchant can setup different time ranges - and associate a |
IBY_IRF_TRXN_AMT_LIMIT |
12 | IBY_IRF_TRXN_AMT_LIMITstores information pertaining to the transaction amount limit risk factor. It is a limit on the total amount of payme |
IBY_MAPPINGS |
14 | IBY_MAPPINGS stores mapping of codes with risk scores. Each row includes a code and a value for that code. |
IBY_PAYEE |
27 | IBY_PAYEE stores a row for each payee, such as a biller, merchant, or store at this site. |
IBY_PAYEE_SUBKEYS |
11 | |
IBY_PAYMENTCARD |
48 | "This table stores information about card number for the card programs associated with card type 'Payment Card'.IBY_PAYMENTCARD contain paym |
IBY_PAYMENTS_ALL |
235 | "This table contains records of the payments which are created by system while processing 'Build payments' program. A payment can be a sin |
IBY_PAYMENTS_H |
122 | IBY_PAYMENTS_H table stores historical snapshots of payments. This table contains denormalized versions of payments from specific points in |
IBY_PAYMENT_METHODS_B |
44 | IBY_PAYMENT_METHODS stores the payment methods that Oracle Payments supports. A payment method is a payment attribute on a document payable |
IBY_PAYMENT_METHODS_TL |
12 | IBY_PAYMENT_METHODS stores the payment methods that Oracle Payments supports. A payment method is a payment attribute on a document payable |
IBY_PAYMENT_REASONS_B |
12 | IBY_PAYMENT_REASONS stores payment reasons that are used as lookup values for payee records or documents payable, that is, invoices. This ta |
IBY_PAYMENT_REASONS_TL |
12 | IBY_PAYMENT_REASONS stores payment reasons that are used as lookup values for payee records or documents payable, that is, invoices. This ta |
IBY_PAYMENT_REFERENCES |
8 | IBY_PAYMENT_REFERENCES stores the current payment reference number. Payment reference numbers are outward facing identifiers assigned to pay |
IBY_PAYMENT_RULES |
11 | IBY_PAYMENT_RULES stores the header-level information for a payment method defaulting rule. A defaulting rule enables the user to define the |
IBY_PAY_BATCHES_ALL |
55 | Stores batch level payment information as submitted by payable programs |
IBY_PAY_DASHBOARD_GT |
4 | |
IBY_PAY_INSTRUCTIONS_ALL |
57 | "This table contains records of the payment instructions. Instructions are created based on the Payment Process Request options. Data is i |
IBY_PAY_INSTRUCTIONS_H |
52 | IBY_PAY_INSTRUCTIONS_H stores historical snapshots of payment instructions. This table contains denormalized versions of payment instruction |
IBY_PAY_INVOICEPMTS |
17 | Stores a reference to the invoice in the calling payable programs |
IBY_PAY_PAYMENTS_ALL |
77 | Stores transaction level payment information as submitted by payable programs |
IBY_PAY_SERVICE_REQUESTS |
39 | "This table contains records of the payment process requests which are created by system while processing 'Build payments' program.IBY_PAY_ |
IBY_PCARD_BIN_RANGE |
11 | Stores the BIN ranges for all valid purchase cards. |
IBY_PMTMTHD_CONDITIONS |
14 | IBY_PMTMTHD_CONDITIONS stores the conditions for payment methods. Each condition is comprised of a parameter, operation, and value. The cond |
IBY_PMTSCHEMES |
11 | IBY_PMTSCHEMES stores a list of payment schemes that are supported by a payment system. |
IBY_PMT_CREATION_RULES |
20 | IBY_PMT_CREATION_RULES specifies how documents payable are grouped into payments. Creation rules are determined by payment process profiles. |
IBY_PMT_INSTR_USES_ALL |
36 | "This table contains records of the relationship between payment instruments and Payer/Payee. Data can be entered manually. IBY_PMT_INSTR_ |
IBY_PMT_LOGICAL_GRP_RULES |
18 | IBY_PMT_LOGICAL_GRP_RULES specifies the attributes for grouping the payments in a payment instruction. |
IBY_PMT_MTHD_ATTRIB_APPL |
11 | IBY_PMT_MTHD_ATTRIB_APPL stores payment channel or method attribute applicability settings. |
IBY_PMT_SYS_FORMATS |
10 | |
IBY_PMT_SYS_TRANSMISSIONS |
9 | |
IBY_PROCESS_CONC_REQUESTS |
10 | Concurrent requests |
IBY_PROCESS_FUNCTIONS |
3 | Populated by build program - list of all functions within any given PPR |
IBY_PROCESS_ORGS |
4 | Populated by build program - list of all orgs within any given PPR |
IBY_PYO_INVOICE_GT |
81 | |
IBY_PYO_PAYMENT_GT |
264 | |
IBY_REMIT_ADVICE_SETUP |
16 | IBY_REMIT_ADVICE_SETUP stores information on creating and delivering remittance information, or remittance advice, for a payee separately fr |
IBY_RESULT_CODES |
11 | Result codes |
IBY_RISK_FACTORS |
12 | IBY_RISK_FACTORS stores information about the Risk Factors. These are factors which a merchant deems fit to use to evaluate the risk of the |
IBY_RISK_FORMULAS |
12 | IBY_RISK_FORMULAS stores risk formula retaled information . Risk Formula is used by merchants to evaluate the risk of the customer. This for |
IBY_RISK_FORMULA_ITEM |
10 | IBY_RISK_FORMULA_ITEM table is an intersection table between the IBY_RISK_FORMULA and IBY_RISK_FACTORS. It stores weight for different Risk |
IBY_ROUTINGINFO |
22 | IBY_ROUTINGINFO stores information that maps payment method to the payment system and funds capture process profile via conditions. |
IBY_RULE_CONDITIONS |
13 | IBY_RULE_CONDITIONS stores the detail-level information for a payment method defaulting rule. Each row in the IBY_PAYMENT_RULES table has on |
IBY_SECURITY_SEGMENTS |
16 | |
IBY_SETUP_TASKS_B |
14 | IBY_SETUP_TASKS stores the status of all Oracle Payments' setup tasks. |
IBY_SETUP_TASKS_TL |
12 | IBY_SETUP_TASKS stores the status of all Oracle Payments' setup tasks. |
IBY_SYS_PMT_PROFILES_B |
69 | "This table stores Payment Process Profile setup for Funds Disbursement transactions. This table also stores information of the seeded Paym |
IBY_SYS_PMT_PROFILES_TL |
12 | IBY_SYS_PMT_PROFILES stores seeded information that specifies the bulk of payment processing behavior. The rest of the behavior is specified |
IBY_SYS_SECURITY_OPTIONS |
21 | |
IBY_SYS_SECURITY_SUBKEYS |
9 | |
IBY_TANGIBLE |
19 | IBY_TANGIBLE stores information about the bills or orders. |
IBY_TEMP_EXT_BANK_ACCTS |
73 | |
IBY_TEMP_EXT_PAYEES |
28 | |
IBY_TEMP_PMT_INSTR_USES |
15 | |
IBY_TRANSACTION_ERRORS |
27 | IBY_TRANSACTION_ERRORS stores any errors encountered during payment processing validations. |
IBY_TRANSMIT_CONFIGS_B |
10 | |
IBY_TRANSMIT_CONFIGS_TL |
10 | |
IBY_TRANSMIT_PARAMETERS_B |
17 | |
IBY_TRANSMIT_PARAMETERS_TL |
12 | |
IBY_TRANSMIT_PROTOCOLS_B |
11 | |
IBY_TRANSMIT_PROTOCOLS_TL |
11 | |
IBY_TRANSMIT_VALUES |
13 | |
IBY_TRXN_CORE |
50 | IBY_BEPKEYS stores information about the payment systems. |
IBY_TRXN_DOCUMENTS |
20 | Table used to store XML documents associated with a particular transaction. |
IBY_TRXN_ERROR_TOKENS |
10 | IBY_TRXN_ERROR_TOKENS stores the values that are used to fill out the tokens in transaction error messages. For each error in IBY_TRANSACTIO |
IBY_TRXN_EXTENDED |
31 | IBY_TRXN_EXTENDED stores the details of a payment request that are specific for extended set functionality for credit cards. |
IBY_TRXN_EXTENSIBILITY |
10 | |
IBY_TRXN_FI |
14 | IBY_TRXN_FI contains the details of a payment request that are specific for systems that support both bank account transfers and credit card |
IBY_TRXN_SUMMARIES_ALL |
91 | IBY_TRXN_SUMMARIES_ALL contains information about each payment request. This table is used for both online and offline payment transactio |
IBY_TRXN_TYPES_B |
11 | IBY_TRXN_TYPES stores the payment processing transaction types required by the dependent products for submitting payment transactions to Ora |
IBY_TRXN_TYPES_TL |
13 | IBY_TRXN_TYPES stores the payment processing transaction types required by the dependent products for submitting payment transactions to Ora |
IBY_UPG_GDFS |
21 | |
IBY_UPG_INSTRUMENTS |
19 | |
IBY_UPG_PPP_B |
89 | |
IBY_UPG_PPP_TL |
11 | |
IBY_USED_PAYMENT_DOCS |
10 | IBY_USED_PAYMENT_DOCS tracks information about which payment documents have been used when printing payments. |
IBY_VALIDATION_PARAMS_B |
11 | IBY_VALIDATION_PARAMS stores parameters for each validation. For example, one validation controls the maximum amount that can be paid in a s |
IBY_VALIDATION_PARAMS_TL |
12 | IBY_VALIDATION_PARAMS stores parameters for each validation. For example, one validation controls the maximum amount that can be paid in a s |
IBY_VALIDATION_SETS_B |
13 | |
IBY_VALIDATION_SETS_TL |
11 | |
IBY_VALIDATION_VALUES |
13 | IBY_VALIDATION_VALUES stores the values for each validation parameter. For example, one validation controls the maximum amount that can be p |
IBY_VAL_ASSIGNMENTS |
14 | |
IBY_VISBLTY_CLASS_DTLS |
16 | Stores the combinations of EC app, payee and org id for a visibility class |
IBY_VISIBILITY_CLASSES |
15 | Stores the user privilege settings for viewing sensitive data in iPayment operations UI |