Results for “bank_instruction2_code”
50+ results
-
View: IBY_EXTERNAL_PAYEES_V 12.2.2
APPS.IBY_EXTERNAL_PAYEES_V·↳ IBY_EXTERNAL_PAYEES_ALL·Explore IBY module →
-
View: IBY_EXTERNAL_PAYEES_V 12.1.1
APPS.IBY_EXTERNAL_PAYEES_V·↳ IBY_EXTERNAL_PAYEES_ALL·Explore IBY module →
-
View: IBY_EXT_FD_PMT_1_0_V 12.2.2
APPS.IBY_EXT_FD_PMT_1_0_V·↳ FND_GLOBAL·↳ IBY_EXT_FD_PMT_1_0_VT·↳ IBY_FD_EXTRACT_GEN_PVT·Explore IBY module →
-
View: IBY_PAYMENTS_SEC_V 12.2.2
APPS.IBY_PAYMENTS_SEC_V·↳ CE_SECURITY_PROFILES_V·↳ FND_ACCESS_CONTROL_UTIL·↳ FND_GLOBAL·Explore IBY module →
-
View: IBY_FD_PAYMENTS_V 12.2.2
APPS.IBY_FD_PAYMENTS_V·↳ IBY_FD_EXTRACT_GEN_PVT·↳ IBY_PAYMENTS_ALL·↳ IBY_PAY_INSTRUCTIONS_ALL·Explore IBY module →
-
View: IBY_PAYMENT_PROFILES 12.2.2
APPS.IBY_PAYMENT_PROFILES·↳ IBY_ACCT_PMT_PROFILES_VL·↳ IBY_SYS_PMT_PROFILES_VL·Explore IBY module →
-
View: IBY_EXT_FD_PMT_1_0_V 12.1.1
APPS.IBY_EXT_FD_PMT_1_0_V·↳ FND_GLOBAL·↳ IBY_EXT_FD_PMT_1_0_VT·↳ IBY_FD_EXTRACT_GEN_PVT·Explore IBY module →
-
"This table contains payment details of an external payee automatically created by the source product. For example when supplier or supplier site is created manually system automatically inserts row in to the IBY_EXTERNAL_PAYEES_ALL table.
-
"This table stores Payment Process Profile setup for Funds Disbursement transactions. This table also stores information of the seeded Payment process profiles. IBY_SYS_PMT_PROFILES_B stores information that specifies the bulk of payment
-
View: IBY_PAYMENTS_SEC_V 12.1.1
APPS.IBY_PAYMENTS_SEC_V·↳ CE_SECURITY_PROFILES_V·↳ FND_ACCESS_CONTROL_UTIL·↳ FND_GLOBAL·Explore IBY module →
-
View: IBY_PAYMENT_PROFILES 12.1.1
APPS.IBY_PAYMENT_PROFILES·↳ IBY_ACCT_PMT_PROFILES_VL·↳ IBY_SYS_PMT_PROFILES_VL·Explore IBY module →
-
APPS.IBY_SYS_PMT_PROFILES_VL·↳ IBY_SYS_PMT_PROFILES_B·↳ IBY_SYS_PMT_PROFILES_TL·Explore IBY module →
-
AP_SUPPLIER_SITES_INT_ALL holds Supplier Site information which is loadedby the user for import. The columns in the table map to corresponding columnsin PO_VENDOR_SITES_ALL table. The Oracle Payables application uses this information to
-
AP_SUPPLIERS_INT holds Supplier information which is loaded by the user for import. The columns in the table map to corresponding columns in the PO_VENDORS table. The Oracle Payables application uses this information to create a new Supp
-
View: IBY_EXT_FD_INS_1_0_V 12.1.1
APPS.IBY_EXT_FD_INS_1_0_V·↳ CE_LOOKUPS·↳ CE_PAYMENT_DOCUMENTS·↳ CE_SECURITY_PROFILES_GT·Explore IBY module →
-
IBY_PAYMENTS_H table stores historical snapshots of payments. This table contains denormalized versions of payments from specific points in time, including when the payment was submitted to a payment system. Different snapshots of the same
-
APPS.IBY_SYS_PMT_PROFILES_VL·↳ IBY_SYS_PMT_PROFILES_B·↳ IBY_SYS_PMT_PROFILES_TL·Explore IBY module →
-
View: IBY_FD_PAYMENTS_V 12.1.1
APPS.IBY_FD_PAYMENTS_V·↳ IBY_FD_EXTRACT_GEN_PVT·↳ IBY_PAYMENTS_ALL·↳ IBY_PAY_INSTRUCTIONS_ALL·Explore IBY module →
-
View: IBY_EXT_FD_INS_1_0_V 12.2.2
APPS.IBY_EXT_FD_INS_1_0_V·↳ CE_LOOKUPS·↳ CE_PAYMENT_DOCUMENTS·↳ CE_SECURITY_PROFILES_GT·Explore IBY module →
-
AP_SUPPLIERS_INT holds Supplier information which is loaded by the user for import. The columns in the table map to corresponding columns in the PO_VENDORS table. The Oracle Payables application uses this information to create a new Supp
-
AP_SUPPLIER_SITES_INT_ALL holds Supplier Site information which is loadedby the user for import. The columns in the table map to corresponding columnsin PO_VENDOR_SITES_ALL table. The Oracle Payables application uses this information to
-
"This table contains records of the payments which are created by system while processing 'Build payments' program. A payment can be a single check or an electronic fund transfer between first party payer and third party payee. A row in
-
VIEW: IBY.IBY_UPG_GDFS# 12.2.2
-
TABLE: IBY.IBY_UPG_GDFS 12.1.1
-
TABLE: IBY.IBY_UPG_GDFS 12.2.2
-
VIEW: IBY.IBY_UPG_PPP_B# 12.2.2
-
VIEW: IBY.IBY_UPG_GDFS# 12.2.2
-
VIEW: IBY.IBY_PAYMENTS_H# 12.2.2
-
VIEW: AP.AP_SUPPLIERS_INT# 12.2.2