This Technical Reference Manual (TRM) in any form, software or printed matter, contains proprietary information of Oracle ; it is provided under an Oracle agreement containing restrictions on use and disclosure and is also protected by copyright, patent, and other intellectual property law. Restrictions applicable to this TRM include, but are not limited to: (a) exercising either the same degree of care to safeguard the confidentiality of this TRM as you exercise to safeguard the confidentiality of your own most important Confidential Information or a reasonable degree of care, whichever is greater; (b) maintaining agreements with your employees and agents that protect the Confidential Information of third parties such as Oracle and instructing such employees and agents of these requirements for this TRM; (c) restricting disclosure of this TRM to those of your employees who have a 'need to know' consistent with the purposes for which this TRM was disclosed to you; (d) maintaining this TRM at all times on your premises; (e) not removing or destroying any proprietary or confidential legends or markings placed upon this TRM in whatever form, software or printed matter; and (f) not reproducing or transmitting this TRM in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Oracle. You should not use this TRM in any form, software or printed matter, to create software that performs the same or similar functions as any Oracle products.
The information in this TRM is subject to change without notice. If you find any problems in the TRM in any form, software or printed matter, please report them to us in writing. Oracle does not warrant that this TRM is error free. This TRM is provided to customer 'as is' with no warranty of any kind. This TRM does not constitute Documentation as that term is defined in Oracle's agreements. Reverse engineering of the Programs (software and documentation) associated with this TRM are prohibited. The Programs associated with this TRM are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be licensee's responsibility to take all appropriate fail safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and Oracle disclaims liability for any damages caused by such use of the Programs. Program Documentation is licensed for use solely to support the deployment of the Programs and not for any other any other purpose. Restricted Rights Legend
This TRM and the Programs associated with this TRM delivered subject to the DOD FAR Supplement are 'commercial computer software' and use, duplication and disclosure of the TRM and the Programs associated with this TRM shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement. Otherwise, this TRM and the Programs associated with this TRM delivered subject to the Federal Acquisition Regulations are 'restricted computer software' and use, duplication and disclosure of the TRM and the Programs associated with this TRM shall be subject to the restrictions in FAR 52.227-14, Rights in Data General, including Alternate III (June 1987). Oracle, 500 Oracle Parkway, Redwood City, CA 94065.
Oracle is a registered trademark. AIM Advantage™, Big Business. Small Business. All Business.™, CDM Advantage™, .comference™, ConText®, Des40®, Easy*Query™, Easy*SQL®, Education Objects™, EMM Advantage™, Enabling the Information Age®, ExpertDetectSM, Express®, FastForwardSM, GEMMS®, Gist™, Hyper*SQL™, instantOracle™, "Internet Business Intelligence - Insight for Everyone"™, iSQL*Plus™, JInitiator™, NLS*Workbench®, Object Marketplace™, ODP Pulse™, ODP Techwire™, OLA™, On Oracle™, Oracle®, Oracle Book®, Oracle Bookbatch®, Oracle BookBuilder®, OracleBRONZE®, Oracle Business OnLine®, OracleDevConnectSM, Oracle® Discoverer™, Oracle® Expert™, Oracle Financials®, OracleGOLDSM, OracleIncidentSM, OracleJSP™, OracleLifeCycleSM, Oracle Media Objects®, OracleMERCURYSM, OracleMetaLinkSM, OraclemetalsSM, OracleMobile™, Oracle Names®, Oracle NetSolutions®, Oracle® One™, Oracle Open Gateways®, Oracle OpenWorld®, OraclePLATINUMSM, Oracle Power Objects®, Oracle Press®, Oracle Procedural Gateway®, Oracle Quality®, Oracle Secure Network Services®, OracleSILVERSM, Oracle® SQL/Services™, Oracle® SQL*TutorSM, OracleSTERLINGSM, Oracle Store®, Oracle Transparent Gateway®, OracleWare®, Oracle8i™, Oracle9i™, PC Express®, Personal Express®, PJM Advantage™, PL/SQL™, Pro*Ada®, Pro*C™, Pro*C/C++™, Pro*COBOL®, Pro*FORTRAN®, Pro*Pascal®, Pro*PL/1®, Pro*REXX®, Profit™, ProREXX™, Report Card™, Secure Access 2.0™, Secure Network Services®, Security Without Compromise™, SellingPoint®, SQL*Plus®, Tutor™ are trademarks or registered trademarks of Oracle. Other names may be trademarks of their respective owners. The absence of a product or service name, slogan, or logo from this list does not constitute a waiver of Oracle's trademark or other intellectual property rights concerning that name, slogan, or logo.
| Description: | This table contains records of the account owners of the external bank accounts entered manually. This table corresponds to the Banking details page of supplier or customer. When an external bank account is created a row will be stored in |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_ACCOUNT_OWNERS.EXT_BANK_ACCOUNT_ID | IBY_EXT_BANK_ACCOUNTS |
| IBY_ACCOUNT_OWNERS.ACCOUNT_OWNER_PARTY_ID | HZ_PARTIES |
IBY_ACCOUNT_OWNERS stores the joint account owners of a bank account.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_ACCOUNT_OWNERS_U1 | UNIQUE | APPS_TS_TX_IDX | ACCOUNT_OWNER_ID |
| IBY_ACCOUNT_OWNERS_U2 | UNIQUE | APPS_TS_TX_IDX |
EXT_BANK_ACCOUNT_ID
ACCOUNT_OWNER_PARTY_ID PRIMARY_FLAG |
| IBY_ACCOUNT_OWNERS_N1 | NONUNIQUE | APPS_TS_TX_IDX | ACCOUNT_OWNER_PARTY_ID |
| IBY_ACCOUNT_OWNERS_N2 | NONUNIQUE | APPS_TS_TX_IDX |
PRIMARY_FLAG
EXT_BANK_ACCOUNT_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ACCOUNT_OWNER_ID | NUMBER | (15) | Y | PK of this table |
| EXT_BANK_ACCOUNT_ID | NUMBER | (15) | Y | Bank account identifier |
| ACCOUNT_OWNER_PARTY_ID | NUMBER | (15) | Y | Joint account holder's party identifier |
| END_DATE | DATE | End date | ||
| PRIMARY_FLAG | VARCHAR2 | (1) | Y or N flag indicating that this is the primary bank account owner | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. |
IBY.IBY_ACCOUNT_OWNERS does not reference any database object
IBY.IBY_ACCOUNT_OWNERS is referenced by following:
| Description: | IBY_ACCPPMTMTHD contains a list of all the payment instrument methods that are accepted by a iPayment. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_ACCPPMTMTHD.MPAYEEID | IBY_PAYEE |
| IBY_ACCPPMTMTHD.ACCTTYPEID | IBY_ACCTTYPE |
IBY_ACCPPMTMTHD contains a list of all the payment instrument methods that are accepted by a payeet.
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYEEID | VARCHAR2 | (80) | Y | ID of the payee passed by Ellectronic Commerce Application |
| ECAPPID | NUMBER | Y | Electronic Commerce Application identifier | |
| ACCTTYPEID | NUMBER | (15) | Y | Account type identifier |
| MPAYEEID | NUMBER | (15) | Y | Payee Identifier |
| STATUS | NUMBER | (2) | Status in 0-active, 1-inactive. | |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column - date when a user last updated this row. | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | This column is used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard who column - user who last updated this row (foreign key to FND_USER.USER_ID). |
| CREATED_BY | NUMBER | (15) | Y | Standard who column - user who created this row (foreign key to FND_USER.USER_ID). |
| CREATION_DATE | DATE | Y | Standard who column - date when this row was created. | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard who column - operating system login of user who last updated this row (foreign key to FND_LOGINS.LOGIN_ID). | |
| SECURITY_GROUP_ID | NUMBER | Used in hosted environments |
IBY.IBY_ACCPPMTMTHD does not reference any database object
IBY.IBY_ACCPPMTMTHD is referenced by following:
| Description: | IBY_ACCTTYPE contains a list of various account types supported. For example for bank account, the account types could be Checking, Savings etc, for Credit Card, the account types could be Visa, MasterCard, Discover etc... |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_ACCPPMTMTHD.ACCTTYPEID | IBY_ACCTTYPE |
| IBY_BANKACCT.ACCTTYPEID | IBY_ACCTTYPE |
| IBY_CREDITCARD.ACCTTYPEID | IBY_ACCTTYPE |
IBY_ACCTTYPE contains a list of various account types supported.
For example for bank account, the account types could be Checking, Savings etc...
For Credit Card, the account types could be Visa, MasterCard, Discover etc...
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_ACCTTYPE_ACCTTYPEID_U1 | UNIQUE | APPS_TS_TX_IDX |
ACCTTYPEID
ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ACCTTYPEID | NUMBER | (15) | Y | AccountType identifier |
| ACCTTYPE | VARCHAR2 | (30) | Indicates the type of Accounts e.g CHECKING, SAVING, VISA, AMEX etc. It is a lookup code for LOOKUP TYPE IBY_ACCT_TYPE. | |
| INSTRTYPE | VARCHAR2 | (30) | Indicates different instrument types e.g bank account, credit card etc. It is a lookup code for lookup type IBY_INSTRUMENT_TYPES. | |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column - date when a user last updated this row. | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | This column is used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard who column - user who last updated this row (foreign key to FND_USER.USER_ID). |
| CREATION_DATE | DATE | Y | Standard who column - date when this row was created. | |
| CREATED_BY | NUMBER | (15) | Y | Standard who column - user who created this row (foreign key to FND_USER.USER_ID). |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard who column - operating system login of user who last updated this row (foreign key to FND_LOGINS.LOGIN_ID). | |
| SECURITY_GROUP_ID | NUMBER | Used in hosted environments | ||
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_ACCTTYPE does not reference any database object
IBY.IBY_ACCTTYPE is referenced by following:
| Description: | IBY_ACCT_PMT_PROFILES stores account-related information that completes the specification of the handling of payment instructions. Entries in this table are based on entries in the IBY_SYS_PMT_PROFILES table. A combination of the two tables |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_ACCT_PMT_PROFILES_B.SYSTEM_PROFILE_CODE | IBY_SYS_PMT_PROFILES_B |
| IBY_ACCT_PMT_PROFILES_B.BEP_ACCOUNT_ID | IBY_BEPKEYS |
| IBY_ACCT_PMT_PROFILES_B.TRANSMIT_CONFIGURATION_ID | IBY_TRANSMIT_CONFIGS_B |
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_ACCT_PMT_PROFILES_TL.PAYMENT_PROFILE_ID | IBY_ACCT_PMT_PROFILES_B |
| IBY_DOCS_PAYABLE_ALL.PAYMENT_PROFILE_ID | IBY_ACCT_PMT_PROFILES_B |
| IBY_DOCUMENTS_PAYABLE_H.PAYMENT_PROFILE_ID | IBY_ACCT_PMT_PROFILES_B |
| IBY_PAYMENTS_ALL.PAYMENT_PROFILE_ID | IBY_ACCT_PMT_PROFILES_B |
| IBY_PAY_INSTRUCTIONS_ALL.PAYMENT_PROFILE_ID | IBY_ACCT_PMT_PROFILES_B |
| IBY_PAY_SERVICE_REQUESTS.PAYMENT_PROFILE_ID | IBY_ACCT_PMT_PROFILES_B |
IBY_ACCT_PMT_PROFILES stores account-related information that completes the specification of the handling of payment instructions. Entries in this table are based on entries in the IBY_SYS_PMT_PROFILES table. A combination of the two tables is defined in the view IBY_PAYMENT_PROFILES. The selection of a payment process profile is driven by the payment method assigned to a document and other factors. This table corresponds to the Payment Process Profiles pages.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_ACCT_PMT_PROFILES_B_U1 | UNIQUE | APPS_TS_TX_IDX |
PAYMENT_PROFILE_ID
ZD_EDITION_NAME |
| IBY_ACCT_PMT_PROFILES_B_N1 | NONUNIQUE | APPS_TS_TX_IDX | SYSTEM_PROFILE_CODE |
| IBY_ACCT_PMT_PROFILES_B_N2 | NONUNIQUE | APPS_TS_TX_IDX | BEP_ACCOUNT_ID |
| IBY_ACCT_PMT_PROFILES_B_N3 | NONUNIQUE | APPS_TS_TX_IDX | TRANSMIT_CONFIGURATION_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYMENT_PROFILE_ID | NUMBER | (15) | Y | System generated primary key |
| SYSTEM_PROFILE_CODE | VARCHAR2 | (100) | Y | System payment process profile Identifier |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number | |
| BEP_ACCOUNT_ID | NUMBER | (15) | Payment system account Identifier | |
| SECURITY_CONFIGURATION_ID | NUMBER | (15) | Security configuration Identifier | |
| TRANSMIT_CONFIGURATION_ID | NUMBER | (15) | Transmission configuration Identifier | |
| RESET_VALUE_1 | NUMBER | (15) | Value to which the first sequence is reset | |
| LAST_USED_NUMBER_1 | NUMBER | (15) | Last number that was used by the first sequence | |
| RESET_REQUEST_1 | NUMBER | (15) | Identifier of the concurrent request used to reset the first sequence | |
| RESET_VALUE_2 | NUMBER | (15) | Value to which the second sequence is reset | |
| LAST_USED_NUMBER_2 | NUMBER | (15) | Last number that was used by the second sequence | |
| RESET_REQUEST_2 | NUMBER | (15) | Identifier of the concurrent request used to reset the second sequence | |
| RESET_VALUE_3 | NUMBER | (15) | Value to which the third sequence is reset | |
| LAST_USED_NUMBER_3 | NUMBER | (15) | Last number that was used by the third sequence | |
| RESET_REQUEST_3 | NUMBER | (15) | Identifier of the concurrent request used to reset the third sequence | |
| INACTIVE_DATE | DATE | Inactive date | ||
| ACK_SEC_CONFIG_ID | NUMBER | (15) | Security configuration Identifier for acknowledgement file | |
| ACK_TRANSMIT_CONFIG_ID | NUMBER | (15) | Transmission configuration Identifier for acknowledgement file | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_ACCT_PMT_PROFILES_B does not reference any database object
IBY.IBY_ACCT_PMT_PROFILES_B is referenced by following:
| Description: | IBY_ACCT_PMT_PROFILES stores account-related information that completes the specification of the handling of payment instructions. Entries in this table are based on entries in the IBY_SYS_PMT_PROFILES table. A combination of the two tables |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_ACCT_PMT_PROFILES_TL.PAYMENT_PROFILE_ID | IBY_ACCT_PMT_PROFILES_B |
IBY_ACCT_PMT_PROFILES stores account-related information that completes the specification of the handling of payment instructions. Entries in this table are based on entries in the IBY_SYS_PMT_PROFILES table. A combination of the two tables is defined in the view IBY_PAYMENT_PROFILES. The selection of a payment process profile is driven by the payment method assigned to a document and other factors. This table corresponds to the Payment Process Profiles pages.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_ACCT_PMT_PROFILES_TL_U1 | UNIQUE | APPS_TS_TX_IDX |
PAYMENT_PROFILE_ID
LANGUAGE ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYMENT_PROFILE_ID | NUMBER | (15) | Y | System generated primary key |
| PAYMENT_PROFILE_NAME | VARCHAR2 | (100) | Y | Payment process profile name |
| LANGUAGE | VARCHAR2 | (4) | Y | Language code |
| SOURCE_LANG | VARCHAR2 | (4) | Y | Language code of the record's current language |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_ACCT_PMT_PROFILES_TL does not reference any database object
IBY.IBY_ACCT_PMT_PROFILES_TL is referenced by following:
| Description: | Provided to store acknowledgement information at payment level. |
|---|
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ACK_PMT_ID | NUMBER | (15) | Y | System generated primary key. Should be unique. |
| PAYMENT_REF_NUMBER | NUMBER | (15) | Y | Payment reference number. This is the matching key. |
| PAYMENT_INSTRUCTION_REF_NUMBER | NUMBER | (15) | Payment instruction reference number. | |
| BANK_STATUS_CODE | VARCHAR2 | (30) | Y | Bank provided status code in payment acknowledgement file. |
| PAYMENT_ACK_STATUS | VARCHAR2 | (30) | Y | Payment status as per lookup 'IBY_ACKNOWLEDGEMENT_STATUSES' which can be:ACCP, ACSP, ACWC, PNDG and RJCT |
| ACKNOWLEDGEMENT_DATE | DATE | Y | Date of the acknowledgement, provided by the bank in the acknowledgement file | |
| BANK_ASSIGNED_REF_CODE1 | VARCHAR2 | (80) | Bank provided reference code 1 | |
| BANK_ASSIGNED_REF_CODE2 | VARCHAR2 | (80) | Bank provided reference code 2 | |
| PAYER_NAME | VARCHAR2 | (360) | Payer name | |
| PAYER_BANK_NAME | VARCHAR2 | (360) | Payer bank name | |
| PAYER_BANK_BRANCH_NAME | VARCHAR2 | (360) | Payer bank branch name. | |
| PAYER_BANK_SWIFT_CODE | VARCHAR2 | (12) | Payer bank swift code (BIC). | |
| PAYER_BANK_ACCOUNT_NUMBER | VARCHAR2 | (30) | Payer bank account number. | |
| PAYER_BANK_IBAN_NUMBER | VARCHAR2 | (40) | Payer bank account IBAN. | |
| PAYEE_NAME | VARCHAR2 | (360) | Payee name. | |
| PAYEE_BANK_NAME | VARCHAR2 | (360) | Payee bank name | |
| PAYEE_BANK_BRANCH_NAME | VARCHAR2 | (360) | Payee bank branch name. | |
| PAYEE_BANK_SWIFT_CODE | VARCHAR2 | (12) | Payee bank swift code (BIC). | |
| PAYEE_BANK_ACCOUNT_NUMBER | VARCHAR2 | (30) | Payee bank account number. | |
| PAYEE_BANK_IBAN_NUMBER | VARCHAR2 | (40) | Payee bank account IBAN. | |
| PAYMENT_AMOUNT | NUMBER | Payment amount | ||
| BANK_CHARGE_AMOUNT | NUMBER | Bank charge amount | ||
| PAYMENT_CURRENCY_CODE | VARCHAR2 | (15) | The currency for the payment. | |
| EXCHANGE_RATE | NUMBER | The exchange rate. | ||
| CALCULATED_PAYMENT_AMOUNT | NUMBER | This will be payment amount multiplied with exchange rate. | ||
| CALCULATED_BANK_CHARGE_AMOUNT | NUMBER | This will be bank charge amount multiplied with exchange rate | ||
| VALUE_DATE | DATE | The date bank withdrew funds from the payer bank account | ||
| REQUESTED_EXECUTION_DATE | DATE | Date on which bank to debit payer bank account for making payment | ||
| CREATED_BY | NUMBER | (15) | Y | Standard Who columns |
| CREATION_DATE | DATE | Y | Standard Who columns | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who columns |
| LAST_UPDATE_DATE | DATE | Y | Standard Who columns | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who columns |
IBY.IBY_ACK_PMT_ALL does not reference any database object
IBY.IBY_ACK_PMT_ALL is referenced by following:
| Description: | Provided to store acknowledgement error(s) information at payment level. |
|---|
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ACK_PMT_ERROR_ID | NUMBER | (15) | Y | System generated primary key |
| ACK_PMT_ID | NUMBER | (15) | Y | PK of payment acknowledgement table. |
| BANK_ERROR_CODE | VARCHAR2 | (80) | Bank assigned error code | |
| BANK_ERROR_MESSAGE | VARCHAR2 | (1024) | Error message describing the error | |
| BANK_ERROR_LOCATION | VARCHAR2 | (1024) | Location of the error in the original payment file. | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who columns |
| CREATION_DATE | DATE | Y | Standard Who columns | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who columns |
| LAST_UPDATE_DATE | DATE | Y | Standard Who columns | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who columns |
IBY.IBY_ACK_PMT_ERRORS does not reference any database object
IBY.IBY_ACK_PMT_ERRORS is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_FNDCPT_SYS_CC_PF_B.SETTLEMENT_ACK_RDR_CODE | IBY_ACK_READERS |
| IBY_FNDCPT_SYS_CC_PF_B.QUERY_ACK_RDR_CODE | IBY_ACK_READERS |
IBY_ ACK_READERS defines code points for parsing payment instruction acknowledgments.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_ACK_READERS_ARC_U1 | UNIQUE | APPS_TS_TX_IDX |
ACK_READER_CODE
ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ACK_READER_CODE | VARCHAR2 | (30) | Y | Acknowledgment reader primary key |
| READER_CODE_LANGUAGE | VARCHAR2 | (30) | Y | Language in which the reader is implemented; possible values include: JAVA , PLSQL |
| READER_CODE_PACKAGE | VARCHAR2 | (255) | Y | Package where the reader is defined; in PL/SQL this corresponds to a package name, in Java a class name |
| READER_CODE_ENTRY_POINT | VARCHAR2 | (255) | Y | Entry point for the reader; typically a function or method name |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_ACK_READERS does not reference any database object
IBY.IBY_ACK_READERS is referenced by following:
| Description: | IBY_ACTIVITY stores scheduler related activities. |
|---|
IBY_ACTIVITY stores scheduler related activities.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_ACT_JTF_ACT_ACT_LOGS_ID_U1 | UNIQUE | APPS_TS_TX_IDX | JTF_ACT_ACTIVITY_LOGS_ID |
| IBY_ACT_ACTIVITY_NAME_ID_N1 | NONUNIQUE | APPS_TS_TX_IDX | ACTIVITY_NAME_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| JTF_ACT_ACTIVITY_LOGS_ID | NUMBER | Y | JTF Activity Log Identifier | |
| APPLICATION_ID | NUMBER | Y | Application Identifier | |
| ACTIVITY_NAME_ID | NUMBER | Y | Activity Name Identifier which logs this activity | |
| JTF_ACT_ACTIVITY_LOGS_USER_ID | NUMBER | JTF Activity Log User Identifier | ||
| COMPONENT | VARCHAR2 | (255) | Subcomponent of the Loging activity | |
| COLUMN1 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN2 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN3 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN4 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN5 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN6 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN7 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN8 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN9 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN10 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN11 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN12 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN13 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN14 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN15 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN16 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN17 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN18 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN19 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN20 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN21 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN22 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN23 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN24 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN25 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN26 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN27 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN28 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN29 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN30 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN31 | VARCHAR2 | (255) | vthe columns which stores the values of activities. | |
| COLUMN32 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN33 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN34 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN35 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN36 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN37 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN38 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN39 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| COLUMN40 | VARCHAR2 | (255) | the columns which stores the values of activities. | |
| CREATED_BY | NUMBER | Y | Standard who column - user who created this row (foreign key to FND_USER.USER_ID). | |
| CREATION_DATE | DATE | Y | Standard who column - date when this row was created. | |
| LAST_UPDATED_BY | NUMBER | Y | Standard who column - user who last updated this row (foreign key to FND_USER.USER_ID). | |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column - date when a user last updated this row. | |
| LAST_UPDATE_LOGIN | NUMBER | Standard who column - operating system login of user who last updated this row (foreign key to FND_LOGINS.LOGIN_ID). | ||
| OBJECT_VERSION_NUMBER | NUMBER | This column is used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. | ||
| SECURITY_GROUP_ID | NUMBER | Used in hosted environments |
IBY.IBY_ACTIVITY does not reference any database object
IBY.IBY_ACTIVITY is referenced by following:
| Description: | IBY_APPLICABLE_PMT_MTHDS stores the payment method applicability information for company policy-based factors. The factors include First Party Legal Entity, First Party Organization, Payment Processing Transaction Type, Transaction is Forei |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_APPLICABLE_PMT_MTHDS.PAYMENT_METHOD_CODE | IBY_PAYMENT_METHODS_B |
| IBY_APPLICABLE_PMT_MTHDS.APPLICATION_ID | FND_APPLICATION |
IBY_APPLICABLE_PMT_MTHDS stores the payment method applicability information for company policy-based factors. The factors include First Party Legal Entity, First Party Organization, Payment Processing Transaction Type, Transaction is Foreign Currency or Not, Cross-Border Transaction or Not, and Payment Amount. Payment method applicability determines which payment method applies under given conditions. It is used to narrow the list of possible payment methods when a user or application is assigning a payment method to a document payable. This table is shared by funds capture and fund disbursement flows.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_APPLICABLE_PMT_MTHDS_U1 | UNIQUE | APPS_TS_TX_IDX |
APPLICABLE_PMT_MTHD_ID
ZD_EDITION_NAME |
| IBY_APPLICABLE_PMT_MTHDS_N1 | NONUNIQUE | APPS_TS_TX_IDX | PAYMENT_METHOD_CODE |
| IBY_APPLICABLE_PMT_MTHDS_N2 | NONUNIQUE | APPS_TS_TX_IDX | APPLICATION_ID |
| IBY_APPLICABLE_PMT_MTHDS_N3 | NONUNIQUE | APPS_TS_TX_IDX | APPLICABLE_TYPE_CODE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| APPLICABLE_PMT_MTHD_ID | NUMBER | (15) | Y | System generated primary key |
| PAYMENT_METHOD_CODE | VARCHAR2 | (30) | Y | Payment method identifier |
| PAYMENT_FLOW | VARCHAR2 | (30) | Determines the source table for the PAYMENT_METHOD_CODE foreign key. Lookup values of IBY_PAYMENT_FLOW lookup type. Values are DISBURSEMENTS and FUND_CAPTURE. | |
| APPLICABLE_TYPE_CODE | VARCHAR2 | (30) | Y | Applicable type. Each type corresponds to one factor in determining the applicability of a payment method. Lookup values of IBY_PMT_MTHD_USAGE_RULE_TYPES lookup type |
| APPLICABLE_VALUE_FROM | VARCHAR2 | (240) | From value of the applicability type. Used for the payment amount applicability only | |
| APPLICABLE_VALUE_TO | VARCHAR2 | (240) | To value of the applicability type | |
| APPLICATION_ID | NUMBER | (15) | Y | Application Identifier of the calling product |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number | |
| EXCLUDE_FROM_APPLIC_FLAG | VARCHAR2 | (1) | Y or N flag | |
| INACTIVE_DATE | DATE | Inactive date | ||
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_APPLICABLE_PMT_MTHDS does not reference any database object
IBY.IBY_APPLICABLE_PMT_MTHDS is referenced by following:
| Description: | IBY_APPLICABLE_PMT_PROFS maps payment methods to payment process profiles. Since administrators can define both payment methods and payment process profiles, they must also choose which payment process profiles are associated with each paym |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_APPLICABLE_PMT_PROFS.SYSTEM_PROFILE_CODE | IBY_SYS_PMT_PROFILES_B |
IBY_APPLICABLE_PMT_PROFS maps payment methods to payment process profiles. Since administrators can define both payment methods and payment process profiles, they must also choose which payment process profiles are associated with each payment method. Those choices are stored in this table. The relationship is many-to-many, which means that the same payment process profile may fulfill the requirements of more than one payment method. This table corresponds to the Usage Rules tab of the Update Payment Process Profile page.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_APPLICABLE_PMT_PROFS_U1 | UNIQUE | APPS_TS_TX_IDX |
APPLICABLE_PMT_PROF_ID
ZD_EDITION_NAME |
| IBY_APPLICABLE_PMT_PROFS_N1 | NONUNIQUE | APPS_TS_TX_IDX | SYSTEM_PROFILE_CODE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| APPLICABLE_PMT_PROF_ID | NUMBER | (15) | Y | System generated primary key |
| SYSTEM_PROFILE_CODE | VARCHAR2 | (100) | Y | Unique primary key |
| APPLICABLE_TYPE_CODE | VARCHAR2 | (30) | Y | Applicable type. Each type corresponds to one factor in determining the applicability of a payment process profile. Lookup values of IBY_PMT_PROF_USAGE_RULE_TYPES lookup type |
| SEEDED_FLAG | VARCHAR2 | (1) | Y or N flag controlling updatability of records. Y indicates record was seeded by Oracle and may have user updates limited. | |
| APPLICABLE_VALUE_FROM | VARCHAR2 | (240) | From value of the applicability type. Used for the payment amount applicability only | |
| APPLICABLE_VALUE_TO | VARCHAR2 | (240) | To value of the applicability type | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_APPLICABLE_PMT_PROFS does not reference any database object
IBY.IBY_APPLICABLE_PMT_PROFS is referenced by following:
| Description: |
|---|
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IDX_INITIATOR_EXTENSION_ID | NONUNIQUE | INITIATOR_EXTENSION_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| CALLING_APP_DOC_REF_NUMBER | VARCHAR2 | (30) | ||
| DOCUMENT_DATE | DATE | |||
| CREATION_DATE | DATE | |||
| DOCUMENT_TYPE | CHAR | (7) | ||
| DOCUMENT_DESCRIPTION | VARCHAR2 | (240) | ||
| DOCUMENT_AMOUNT | NUMBER | |||
| DOCUMENT_CURRENCY_CODE | VARCHAR2 | (15) | ||
| SETTLEMENT_AMOUNT | NUMBER | |||
| DISCOUNT_AMOUNT | NUMBER | |||
| FREIGHT_AMOUNT | NUMBER | |||
| DOCUMENT_DISCOUNT_EARNED | NUMBER | |||
| LOCAL_TAX_AMOUNT | NUMBER | |||
| NATIONAL_TAX_AMOUNT | NUMBER | |||
| VAT_TAX_AMOUNT | NUMBER | |||
| ADDRESS1 | VARCHAR2 | (240) | ||
| ADDRESS2 | VARCHAR2 | (240) | ||
| ADDRESS3 | VARCHAR2 | (240) | ||
| CITY | VARCHAR2 | (60) | ||
| COUNTY | VARCHAR2 | (60) | ||
| STATE | VARCHAR2 | (60) | ||
| COUNTRY | VARCHAR2 | (60) | ||
| POSTAL_CODE | VARCHAR2 | (60) | ||
| TO_ADDRESS1 | VARCHAR2 | (240) | ||
| TO_ADDRESS2 | VARCHAR2 | (240) | ||
| TO_ADDRESS3 | VARCHAR2 | (240) | ||
| TO_CITY | VARCHAR2 | (60) | ||
| TO_COUNTY | VARCHAR2 | (60) | ||
| TO_STATE | VARCHAR2 | (60) | ||
| TO_COUNTRY | VARCHAR2 | (60) | ||
| TO_POSTAL_CODE | VARCHAR2 | (60) | ||
| ORDER_TANGIBLE_ID | VARCHAR2 | (80) | ||
| TRANSACTIONID | NUMBER | |||
| INITIATOR_EXTENSION_ID | NUMBER | (15) | ||
| DOC_UNIQUE_REF | NUMBER | (15) | ||
| BR_DRAWEE_ISSUED_FLAG | VARCHAR2 | (1) | ||
| BR_SIGNED_FLAG | VARCHAR2 | (1) |
IBY.IBY_AR_DOC_HEADER_GT1 does not reference any database object
IBY.IBY_AR_DOC_HEADER_GT1 is referenced by following:
| Description: |
|---|
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IDX_DOC_UNIQUE_REF | NONUNIQUE | DOC_UNIQUE_REF |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| LINE_NUMBER | NUMBER | |||
| PO_NUMBER | VARCHAR2 | (50) | ||
| LINE_TYPE | VARCHAR2 | (20) | ||
| DESCRIPTION | VARCHAR2 | (240) | ||
| EXTENDED_AMOUNT | NUMBER | |||
| INVOICE_CURRENCY_CODE | VARCHAR2 | (15) | ||
| UNIT_PRICE | NUMBER | |||
| QUANTITY | NUMBER | |||
| UNIT_OF_MEASURE | VARCHAR2 | (3) | ||
| INVENTORY_ITEM_ID | NUMBER | (15) | ||
| DISCOUNT_AMOUNT | NUMBER | |||
| SALES_TAX_AMOUNT | NUMBER | |||
| TAX_RATE | NUMBER | |||
| VAT_TAX_AMOUNT | NUMBER | |||
| DOC_UNIQUE_REF | NUMBER | (15) |
APPS.IBY_AR_DOC_LINES_GT does not reference any database object
APPS.IBY_AR_DOC_LINES_GT is referenced by following:
| Description: | IBY_BANKACCOUNTstores bank account related information of the customer(payer) or payee. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_BANKACCT.ADDRESSID | HZ_LOCATIONS |
| IBY_BANKACCT.ACCTTYPEID | IBY_ACCTTYPE |
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_INSTRHOLDER.INSTRID | IBY_BANKACCT |
IBY_BANKACCOUNT keeps bank account related information of the customer(payer) or payee.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_BANKACCT_INSTRID_U1 | UNIQUE | APPS_TS_TX_IDX | INSTRID |
| IBY_BANKACCT_BANKACCOUNTID_N2 | NONUNIQUE | APPS_TS_TX_IDX | BANKACCOUNTID |
| IBY_BANKACCT_ENCRYPTED_N3 | NONUNIQUE | APPS_TS_TX_IDX | ENCRYPTED |
| IBY_BANKACCT_ROUTINGNO_N1 | NONUNIQUE | APPS_TS_TX_IDX | ROUTINGNO |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| INSTRID | NUMBER | (15) | Y | System generated id. Primary key |
| BANKACCOUNTID | VARCHAR2 | (80) | Y | Bank Account number |
| ADDRESSID | NUMBER | Address identifier, FK to HZ_LOCATIONS table. Address for the bank branch. | ||
| FINAME | VARCHAR2 | (80) | Financial Institution Name - bank name | |
| ACCTTYPEID | NUMBER | Y | Accttype identifier, FK to iby_accttype. CHECKING, SAVING, etc. | |
| BRANCHNAME | VARCHAR2 | (60) | Bank Branch Name. Used to store bank branch number | |
| ROUTINGNO | VARCHAR2 | (25) | ABA Routing Number for US bank accounts; bank number for non-US banks issued by some Code Agency | |
| DESCRIPTION | VARCHAR2 | (240) | Description of the instruments | |
| INSTRNAME | VARCHAR2 | (80) | Name of the instrument | |
| ACCOUNT_HOLDER_NAME | VARCHAR2 | (240) | Account Holder Name | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard who column - user who last updated this row (foreign key to FND_USER.USER_ID). |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column - date when a user last updated this row. | |
| CREATION_DATE | DATE | Y | Standard who column - date when this row was created. | |
| CREATED_BY | NUMBER | (15) | Y | Standard who column - user who created this row (foreign key to FND_USER.USER_ID). |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard who column - operating system login of user who last updated this row (foreign key to FND_LOGINS.LOGIN_ID). | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | This column is used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. | |
| SECURITY_GROUP_ID | NUMBER | Used in hosted environments | ||
| BRANCHID | VARCHAR2 | (30) | Bank branch number. Added for AR-BR integration | |
| BANKSWIFTCODE | VARCHAR2 | (30) | Bank SWIFT code. Added for AR-BR integration | |
| CHECK_DIGITS | VARCHAR2 | (30) | Check digits for bank accounts that identify them separately from the bank account numbers | |
| ENCRYPTED | VARCHAR2 | (1) | Indicates whether strong encryption was used on sensitive data | |
| CURRENCY_CODE | VARCHAR2 | (15) | ISO three digits currency code |
IBY.IBY_BANKACCT does not reference any database object
IBY.IBY_BANKACCT is referenced by following:
| Description: | Provided to store Mapping of acknowledgement codes to ISO codes. |
|---|
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_BANK_ACK_STATUSES_U1 | UNIQUE | APPS_TS_TX_IDX | BANK_ACK_STATUS_CODE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| BANK_ACK_STATUS_CODE | VARCHAR2 | (10) | Y | Bank Acknowledgement Status Code |
| BANK_ACK_STATUS_NAME | VARCHAR2 | (30) | Bank Acknowledgement Status Code Name. | |
| PAYMENT_ACK_STATUS | VARCHAR2 | (30) | Y | ISO Acknowledgement Status Code |
| DESCRIPTION | VARCHAR2 | (3000) | Description | |
| INACTIVE_DATE | DATE | Inactive Date | ||
| CREATED_BY | NUMBER | (15) | Y | Standard Who columns |
| CREATION_DATE | DATE | Y | Standard Who columns | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who columns |
| LAST_UPDATE_DATE | DATE | Y | Standard Who columns | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who columns |
IBY.IBY_BANK_ACK_STATUSES does not reference any database object
IBY.IBY_BANK_ACK_STATUSES is referenced by following:
| Description: | IBY_BANK_INSTRUCTIONS stores bank instructions that are used as lookup values for payment process profiles and external payee setup. This table corresponds to the Bank Instruction Codes page. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_BANK_INSTRUCTIONS_B.TERRITORY_CODE | FND_TERRITORIES |
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_BANK_INSTRUCTIONS_TL.BANK_INSTRUCTION_CODE | IBY_BANK_INSTRUCTIONS_B |
| IBY_EXTERNAL_PAYEES_ALL.BANK_INSTRUCTION1_CODE | IBY_BANK_INSTRUCTIONS_B |
| IBY_EXTERNAL_PAYEES_ALL.BANK_INSTRUCTION2_CODE | IBY_BANK_INSTRUCTIONS_B |
| IBY_PAYMENTS_H.BANK_INSTRUCTION1_CODE | IBY_BANK_INSTRUCTIONS_B |
| IBY_PAYMENTS_H.BANK_INSTRUCTION2_CODE | IBY_BANK_INSTRUCTIONS_B |
| IBY_SYS_PMT_PROFILES_B.BANK_INSTRUCTION1_CODE | IBY_BANK_INSTRUCTIONS_B |
| IBY_SYS_PMT_PROFILES_B.BANK_INSTRUCTION2_CODE | IBY_BANK_INSTRUCTIONS_B |
| IBY_TEMP_EXT_PAYEES.BANK_INSTRUCTION1_CODE | IBY_BANK_INSTRUCTIONS_B |
| IBY_TEMP_EXT_PAYEES.BANK_INSTRUCTION2_CODE | IBY_BANK_INSTRUCTIONS_B |
IBY_BANK_INSTRUCTIONS stores bank instructions that are used as lookup values for payment process profiles and external payee setup. This table corresponds to the Bank Instruction Codes page.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_BANK_INSTRUCTIONS_B_U1 | UNIQUE | APPS_TS_TX_IDX |
BANK_INSTRUCTION_CODE
ZD_EDITION_NAME |
| IBY_BANK_INSTRUCTIONS_B_N1 | NONUNIQUE | APPS_TS_TX_IDX | TERRITORY_CODE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| BANK_INSTRUCTION_CODE | VARCHAR2 | (30) | Y | User entered primary key |
| FORMAT_VALUE | VARCHAR2 | (80) | Value required by the payment format that uses this bank instruction | |
| SEEDED_FLAG | VARCHAR2 | (1) | Y or N flag controlling updatability of records. Y indicates record was seeded by Oracle and may have user updates limited. | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number | |
| INACTIVE_DATE | DATE | Inactive date | ||
| TERRITORY_CODE | VARCHAR2 | (2) | Code of the country where the bank instruction code is assigned or used | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_BANK_INSTRUCTIONS_B does not reference any database object
IBY.IBY_BANK_INSTRUCTIONS_B is referenced by following:
| Description: | IBY_BANK_INSTRUCTIONS stores bank instructions that are used as lookup values for payment process profiles and external payee setup. This table corresponds to the Bank Instruction Codes page. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_BANK_INSTRUCTIONS_TL.BANK_INSTRUCTION_CODE | IBY_BANK_INSTRUCTIONS_B |
IBY_BANK_INSTRUCTIONS stores bank instructions that are used as lookup values for payment process profiles and external payee setup. This table corresponds to the Bank Instruction Codes page.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_BANK_INSTRUCTIONS_TL_U1 | UNIQUE | APPS_TS_TX_IDX |
BANK_INSTRUCTION_CODE
LANGUAGE ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| BANK_INSTRUCTION_CODE | VARCHAR2 | (30) | Y | User entered primary key |
| LANGUAGE | VARCHAR2 | (4) | Y | Language code |
| SOURCE_LANG | VARCHAR2 | (4) | Y | Language code of the record's current language |
| MEANING | VARCHAR2 | (80) | Lookup meaning of bank instruction | |
| DESCRIPTION | VARCHAR2 | (240) | Lookup description of bank instruction | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_BANK_INSTRUCTIONS_TL does not reference any database object
IBY.IBY_BANK_INSTRUCTIONS_TL is referenced by following:
| Description: | "This table contains records of the settlement batch information which is updated by system while processing 'Create settlement Batches' program.IBY_BATCHES_ALL stores information about batch operations for credit cards and bank account tra |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_BATCHES_ALL.BEPID | IBY_BEPINFO |
| IBY_BATCHES_ALL.MPAYEEID | IBY_PAYEE |
| Foreign Key Column | Foreign Table |
|---|---|
|
IBY_PAY_BATCHES_ALL.IBY_BATCH_ID
IBY_PAY_BATCHES_ALL.PAYER_ID |
IBY_BATCHES_ALL |
| IBY_TRXN_SUMMARIES_ALL.MBATCHID | IBY_BATCHES_ALL |
IBY_BATCHES_ALL stores information about batch operations for credit card transactions. A terminal-based merchant needs to have batch operations. The status of the payee's batch is contained in this table.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_BATCHES_BATCHID_PAYEEID_U1 | UNIQUE | APPS_TS_TX_IDX |
BATCHID
PAYEEID |
| IBY_BATCHES_MBATCHID_U2 | UNIQUE | APPS_TS_TX_IDX | MBATCHID |
| IBY_BATCHES_ALL_N3 | NONUNIQUE | APPS_TS_TX_IDX | REQDATE |
| IBY_BATCHES_BATCHSTATUS_N1 | NONUNIQUE | APPS_TS_TX_IDX | BATCHSTATUS |
| IBY_BATCHES_LASTUPDATEDATE_N2 | NONUNIQUE | APPS_TS_TX_IDX | LAST_UPDATE_DATE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| MBATCHID | NUMBER | (15) | Y | System generated batch Identifier |
| BATCHID | VARCHAR2 | (80) | Y | Batch Identifier provided by electronic commerce application |
| PAYEEID | VARCHAR2 | (80) | Identifier of the payee passed by electronic commerce application | |
| BEPID | NUMBER | Payment system Identifier | ||
| MPAYEEID | NUMBER | Payee Identifier | ||
| ECAPPID | NUMBER | Electronic commerce application Identifier | ||
| PAYMENTMETHODNAME | VARCHAR2 | (80) | Name of the payment method | |
| BATCHSTATUS | NUMBER | Status of the batch | ||
| BATCHCLOSEDATE | DATE | Close date of this batch | ||
| NUMTRXNS | NUMBER | Number of transactions in this batch | ||
| BATCHSTATEID | NUMBER | (15) | State of the batch. Batch states are 0 for batch accepted, 1 for batch sent, 2 for batch queued, 3 for batch rejected, 4 for batch processed, 5 for batch error, 6 for batch not found, and 7 for batch unknown. | |
| BATCHTOTAL | NUMBER | Total net amount for this batch | ||
| BATCHSALES | NUMBER | Total inflow | ||
| BATCHCREDIT | NUMBER | Total outflow including return and credit transaction amounts | ||
| CURRENCYNAMECODE | VARCHAR2 | (15) | ISO currency code for this batch | |
| VPSBATCHID | VARCHAR2 | (80) | Batch Identifier from payment system | |
| GWBATCHID | VARCHAR2 | (80) | Batch Identifier from Gateway | |
| ERRORLOCATION | NUMBER | Indicates the location of error | ||
| BEPCODE | VARCHAR2 | (80) | Error code from payment system | |
| BEPMESSAGE | VARCHAR2 | (1024) | Error messages from payment system | |
| BATCHOPENDATE | DATE | Date batch was opened | ||
| REQTYPE | VARCHAR2 | (20) | Type of request such as closebatch, purgebatch, or openbatch | |
| REQDATE | DATE | Date when the batch operation request is received | ||
| DESTURL | VARCHAR2 | (1024) | Payment system URL constructed during schedule of payments | |
| TERMINALID | VARCHAR2 | (80) | Terminal Identifier used for credit card processing. A merchant can get multiple terminal identifiers with a batch open for each one. The merchant can perform operations on those batches independently. | |
| ACQUIRER | VARCHAR2 | (80) | Merchant bank which may be optionally returned | |
| NLSLANG | VARCHAR2 | (80) | NLS Language | |
| NEEDSUPDT | VARCHAR2 | (3) | Y or N flag indicating that the rows that have changed status | |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Used for locking purposes that subsequently allows for checking if there is old data on the screen compared to what is in the database. The situation occurs when the HTML application is a stateless application. | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| ORG_ID | NUMBER | (15) | First party organization identifier for all transactions in the batch | |
| SECURITY_GROUP_ID | NUMBER | Used in hosted environments | ||
| BEPKEY | VARCHAR2 | (80) | Merchant account Identifier used with this transaction | |
| SENTCOUNTER | NUMBER | Count of the number of times the batch has been sent to the payment system | ||
| SENTCOUNTERDAILY | NUMBER | Count of the number of times that the batch has been sent to the payment system on the current day | ||
| LEGAL_ENTITY_ID | NUMBER | (15) | Legal entity identifier | |
| PROCESS_PROFILE_CODE | VARCHAR2 | (30) | Funds capture process profile for the batch | |
| PAYEEINSTRID | NUMBER | (15) | Internal bank account for all transactions in the batch | |
| SETTLEDATE | DATE | Settlement date for all transactions in the batch | ||
| ORG_TYPE | VARCHAR2 | (30) | Organization type from lookup type IBY_ORGANIZATION_TYPES | |
| INSTRUMENT_TYPE | VARCHAR2 | (30) | Instrument type for the batch from lookup type IBY_PAYMENT_INSTR_TYPES | |
| BR_DISPUTED_FLAG | VARCHAR2 | (1) | Bills receivable disputed flag | |
| PAYER_NOTIFICATION_REQUIRED | VARCHAR2 | (1) | Y or N flag indicating whether payer notification is created for settlements in this batch | |
| PAYER_NOTIFICATION_CREATED | VARCHAR2 | (1) | Y or N flag indicating whether payer notification has been created for settlements in this batch |
IBY.IBY_BATCHES_ALL does not reference any database object
IBY.IBY_BATCHES_ALL is referenced by following:
| Description: | IBY_BEPKEYS stores information about the payment systems. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_BEPINFO.PARTY_ID | HZ_PARTIES |
| IBY_BEPINFO.BANK_ID | HZ_PARTIES |
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_BATCHES_ALL.BEPID | IBY_BEPINFO |
| IBY_BEPKEYS.BEPID | IBY_BEPINFO |
| IBY_BEPLANGS.BEPID | IBY_BEPINFO |
| IBY_BEP_ACCT_OPT_NAME_B.BEPID | IBY_BEPINFO |
| IBY_DEFAULT_BEP.BEPID | IBY_BEPINFO |
| IBY_FNDCPT_SYS_DC_PF_B.PAYMENT_SYSTEM_ID | IBY_BEPINFO |
| IBY_FNDCPT_SYS_EFT_PF_B.PAYMENT_SYSTEM_ID | IBY_BEPINFO |
| IBY_PAY_INSTRUCTIONS_H.BEPID | IBY_BEPINFO |
| IBY_PMTSCHEMES.BEPID | IBY_BEPINFO |
| IBY_PMT_SYS_FORMATS.PAYMENT_SYSTEM_ID | IBY_BEPINFO |
| IBY_PMT_SYS_TRANSMISSIONS.BEPID | IBY_BEPINFO |
| IBY_ROUTINGINFO.BEPID | IBY_BEPINFO |
| IBY_SYS_PMT_PROFILES_B.BEPID | IBY_BEPINFO |
| IBY_TRXN_SUMMARIES_ALL.BEPID | IBY_BEPINFO |
| IBY_TRXN_SUMMARIES_ALL.BEPID | IBY_BEPINFO |
IBY_BEPKEYS stores information about the payment systems.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_BEPINFO_BEPID_U1 | UNIQUE | APPS_TS_TX_IDX |
BEPID
ZD_EDITION_NAME |
| IBY_BEPINFO_NAME_U2 | UNIQUE | APPS_TS_TX_IDX |
NAME
ZD_EDITION_NAME |
| IBY_BEPINFO_SUFFIX_U3 | UNIQUE | APPS_TS_TX_IDX |
SUFFIX
ZD_EDITION_NAME |
| IBY_BEPINFO_N1 | NONUNIQUE | APPS_TS_TX_IDX | PARTY_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| BEPID | NUMBER | (15) | Y | Payment system identifier |
| NAME | VARCHAR2 | (80) | Y | Name of the payment system |
| BASEURL | VARCHAR2 | (1024) | URL to the payment system | |
| SUFFIX | VARCHAR2 | (10) | Y | Three-letter payment system suffix. This is unique per payment system |
| BEPUSERNAME | VARCHAR2 | (80) | Username for authenticating from iPayment to Back End Payment System. | |
| BEPPASSWORD | VARCHAR2 | (80) | password for BEPUSERNAME. | |
| SUPPORTEDOP | NUMBER | Bitmap to denote operations supported by bank end payment system | ||
| PSUSERNAME | VARCHAR2 | (80) | username for authenticating from Back End Payment System to iPayment | |
| PSPASSWORD | VARCHAR2 | (80) | Password for PSUSERNAME | |
| ADMINURL | VARCHAR2 | (1024) | URL to the native Back End Payment System admin pages | |
| LOGINURL | VARCHAR2 | (1024) | loginurl to the payment system | |
| LOGOUTURL | VARCHAR2 | (1024) | logouturl to the payment system | |
| SRVRIDIMMED | VARCHAR2 | (1) | Y or N flag indicating that Server ID is immediately sent | |
| ACTIVESTATUS | VARCHAR2 | (1) | Indicates whether payment system is active or not | |
| LEADTIME | NUMBER | Lead time that is needed to schedule the payment | ||
| HOLIDAYFILE | VARCHAR2 | (1) | Denotes support for holiday file | |
| FILESUPPORT | VARCHAR2 | (1) | Y or N flag | |
| SECURITYSCHEME | NUMBER | Denotes whether HTML Page or Wallet for invoice or pay operation | ||
| INSTRTYPE | VARCHAR2 | (30) | Instrument type | |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| SECURITY_GROUP_ID | NUMBER | Used in hosted environment | ||
| PARTY_ID | NUMBER | (15) | Oracle Internal use only - reserved for future use | |
| BEP_TYPE | VARCHAR2 | (10) | Indicates whether the BEP is a processor or gateway model payment system. Values for this column include: PROCESSOR and GATEWAY | |
| MAX_BATCH_SIZE | NUMBER | No longer used | ||
| OUTBOUND_INVALID_CHARS | VARCHAR2 | (3000) | Invalid characters to be replaced by the corresponding replacement characters. Generally should have positional correspondence with the replacement ones. For Citi-Payables only. | |
| OUTBOUND_REPLACE_CHARS | VARCHAR2 | (3000) | Replacement characters corresponding to the invalid characters. Generally should have positional correspondence with the invalid ones. For Citi-Payables only. | |
| BANK_ID | NUMBER | (15) | System generated primary key | |
| NLS_LANGUAGE | VARCHAR2 | (50) | NLS language character set for the payment system network communication. | |
| INACTIVE_DATE | DATE | Inactive date | ||
| SEEDED_FLAG | VARCHAR2 | (1) | Y or N flag indicating that the data is seeded record | |
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | Descriptive Flexfield structure defining column | |
| ATTRIBUTE1 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE2 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE3 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE4 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE5 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE6 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE7 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE8 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE9 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE10 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE11 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE12 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE13 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE14 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE15 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| AUTH_REVERSAL_FLAG | VARCHAR2 | (1) | Indicates if authorization reversal is supported by the Payment System. U-UNSUPPORTED, F-FULL_ONLY, M-FULL_AND_PARTIAL | |
| ALLOW_CAPTURE_EX_AUTH_FLAG | VARCHAR2 | (1) | Y/N flag indicating if the payment system allows capture amount greater than authorization amount | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_BEPINFO does not reference any database object
IBY.IBY_BEPINFO is referenced by following:
| Description: | IBY_BEPKEYS stores information about the payment systems accounts. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_BEPKEYS.BEPID | IBY_BEPINFO |
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_ACCT_PMT_PROFILES_B.BEP_ACCOUNT_ID | IBY_BEPKEYS |
| IBY_BEP_ACCT_OPT_VALS.BEP_ACCOUNT_ID | IBY_BEPKEYS |
| IBY_DEFAULT_BEP.BEP_ACCOUNT_ID | IBY_BEPKEYS |
| IBY_FNDCPT_USER_CC_PF_B.BEP_ACCOUNT_ID | IBY_BEPKEYS |
| IBY_FNDCPT_USER_DC_PF_B.BEP_ACCOUNT_ID | IBY_BEPKEYS |
| IBY_FNDCPT_USER_EFT_PF_B.BEP_ACCOUNT_ID | IBY_BEPKEYS |
IBY_BEPKEYS links internal payers to their payment system account values. Oracle Payments can only submit transactions to a payment system if it has the correct values for the selected payment system's parameters, as defined in IBY_BEP_ACCT_OPT_NAME. These values are stored in IBY_BEP_ACCT_OPT_VALS. This table corresponds to the Payment System Accounts page.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_BEPKEYS_U1 | UNIQUE | APPS_TS_TX_IDX |
BEP_ACCOUNT_ID
ZD_EDITION_NAME |
| IBY_BEPKEYS_N1 | NONUNIQUE | APPS_TS_TX_IDX | BEPID |
| IBY_BEPKEYS_N2 | NONUNIQUE | APPS_TS_TX_IDX | OWNERID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| OWNERID | VARCHAR2 | (80) | Identifier of the payer or payee | |
| BEPID | NUMBER | (15) | Y | Payment system identifier |
| KEY | VARCHAR2 | (80) | Y | Payment system account name |
| OWNERTYPE | VARCHAR2 | (30) | Payer or payee | |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| SECURITY_GROUP_ID | NUMBER | Unsed in hosted environment | ||
| DEFAULTS | VARCHAR2 | (1) | Y or N flag to denote whether this key is the payee's default for the given payment system | |
| BEP_ACCOUNT_ID | NUMBER | (15) | Y | Identifier of the payment system account |
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | Descriptive Flexfield structure defining column | |
| ATTRIBUTE1 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE2 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE3 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE4 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE5 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE6 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE7 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE8 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE9 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE10 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE11 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE12 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE13 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE14 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE15 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_BEPKEYS does not reference any database object
IBY.IBY_BEPKEYS is referenced by following:
| Description: | IBY_BEPLANGS contains list of all the languages supported by the Back End Payment System |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_BEPLANGS.BEPID | IBY_BEPINFO |
IBY_BEPLANGS contains list of all the languages supported by the Back End Payment System
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_BEPLANGS_ID_LANG_PRE_U1 | UNIQUE | APPS_TS_TX_IDX |
PREFERRED
BEPLANG BEPID ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| BEPID | NUMBER | Y | Back End Payment System identifier | |
| BEPLANG | VARCHAR2 | (80) | language supported by the Back End Payment System | |
| PREFERRED | NUMBER | Y | denotes whether this is the preferred language of the Back End Payment System | |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column - date when a user last updated this row. | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | This column is used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard who column - user who last updated this row (foreign key to FND_USER.USER_ID). |
| CREATION_DATE | DATE | Y | Standard who column - date when this row was created. | |
| CREATED_BY | NUMBER | (15) | Y | Standard who column - user who created this row (foreign key to FND_USER.USER_ID). |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard who column - operating system login of user who last updated this row (foreign key to FND_LOGINS.LOGIN_ID). | |
| SECURITY_GROUP_ID | NUMBER | Used in hosted environments | ||
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_BEPLANGS does not reference any database object
IBY.IBY_BEPLANGS is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_BEP_ACCT_OPT_NAME_B.BEPID | IBY_BEPINFO |
| Foreign Key Column | Foreign Table |
|---|---|
|
IBY_BEP_ACCT_OPT_NAME_TL.ACCOUNT_OPTION_CODE
IBY_BEP_ACCT_OPT_NAME_TL.BEPID |
IBY_BEP_ACCT_OPT_NAME_B |
IBY_BEP_ACCT_OPT_NAME stores payment system account configuration names.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_BEP_ACCT_OPT_NAME_B_BA_U1 | UNIQUE | APPS_TS_TX_IDX |
BEPID
ACCOUNT_OPTION_CODE ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| BEPID | NUMBER | (15) | Y | Payment system defining the account option |
| ACCOUNT_OPTION_CODE | VARCHAR2 | (30) | Y | Code of the account option |
| ACCOUNT_OPTION_DATATYPE | VARCHAR2 | (30) | Y | Data type of the option. Values from the lookup IBY_PARAMETER_TYPES include VARCHAR2, NUMBER, and DATE. |
| DISPLAY_ORDER | NUMBER | (15) | Y | Display order within the set of all options for that payment system |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Used for locking purposes that subsequently allows for checking if there is old data on the screen compared to what is in the database. The situation occurs when the HTML application is a stateless application. | |
| SECURED_FLAG | VARCHAR2 | (1) | Indicates if the option should be secured- i.e., is sensitive | |
| UNIQUE_PER_BATCH_FLAG | VARCHAR2 | (1) | Indicates if the option should unique per settlement batch file. | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_BEP_ACCT_OPT_NAME_B does not reference any database object
IBY.IBY_BEP_ACCT_OPT_NAME_B is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
|
IBY_BEP_ACCT_OPT_NAME_TL.ACCOUNT_OPTION_CODE
IBY_BEP_ACCT_OPT_NAME_TL.BEPID |
IBY_BEP_ACCT_OPT_NAME_B |
IBY_BEP_ACCT_OPT_NAME stores payment system account configuration names.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_BEP_ACCT_OPT_NAME_TL_U1 | UNIQUE | APPS_TS_TX_IDX |
LANGUAGE
ACCOUNT_OPTION_CODE BEPID ZD_EDITION_NAME |
| IBY_BEP_ACCT_OPT_NAME_TL_BA_N1 | NONUNIQUE | APPS_TS_TX_IDX |
BEPID
ACCOUNT_OPTION_CODE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| BEPID | NUMBER | (15) | Y | Payment system defining the account option |
| ACCOUNT_OPTION_CODE | VARCHAR2 | (30) | Y | Code of the account option |
| LANGUAGE | VARCHAR2 | (4) | Y | Language code |
| SOURCE_LANG | VARCHAR2 | (4) | Y | Language code of the record's current language |
| ACCOUNT_OPTION_NAME | VARCHAR2 | (100) | Y | Descriptive name of the account option |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Used for locking purposes that subsequently allows for checking if there is old data on the screen compared to what is in the database. The situation occurs when the HTML application is a stateless application. |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_BEP_ACCT_OPT_NAME_TL does not reference any database object
IBY.IBY_BEP_ACCT_OPT_NAME_TL is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_BEP_ACCT_OPT_VALS.BEP_ACCOUNT_ID | IBY_BEPKEYS |
| IBY_BEP_ACCT_OPT_VALS.VAL_SEC_SEGMENT_ID | IBY_SECURITY_SEGMENTS |
IBY_BEP_ACCT_OPT_VALS stores values for the parameters defined in IBY_BEP_ACCT_OPT_NAME for a given payee's payment system account. For example, this table is used to provide a payee's Doing Business As, or DBA, name. This table is shared by both the disbursements and funds capture modules of Payments.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_BEP_ACCT_OPT_VALS_AIAC_U1 | UNIQUE | APPS_TS_TX_IDX |
BEP_ACCOUNT_ID
ACCOUNT_OPTION_CODE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| BEP_ACCOUNT_ID | NUMBER | (15) | Y | Associated payment system account |
| BEPID | NUMBER | (15) | Y | Payment system to which the account option belongs |
| ACCOUNT_OPTION_CODE | VARCHAR2 | (30) | Y | Code of the account option |
| ACCOUNT_OPTION_VALUE | VARCHAR2 | (255) | Y | Value of the account option |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. |
| VAL_SEC_SEGMENT_ID | NUMBER | (15) | Reference to the security segment storing the encrypted option value. |
IBY.IBY_BEP_ACCT_OPT_VALS does not reference any database object
IBY.IBY_BEP_ACCT_OPT_VALS is referenced by following:
| Description: | Table contains card ranges for various credit card issuers. Used to remove structure from a credit card number before it is encrypted. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_CC_ISSUER_RANGES.CARD_ISSUER_CODE | IBY_CREDITCARD_ISSUERS_B |
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_CREDITCARD.CC_ISSUER_RANGE_ID | IBY_CC_ISSUER_RANGES |
| IBY_TRXN_SUMMARIES_ALL.CC_ISSUER_RANGE_ID | IBY_CC_ISSUER_RANGES |
Table contains card ranges for various credit card issuers. Used to remove structure from a credit card number before it is encrypted.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_CC_ISSUER_RANGES_U1 | UNIQUE | APPS_TS_TX_IDX |
CC_ISSUER_RANGE_ID
ZD_EDITION_NAME |
| IBY_CC_ISSUER_RANGES_ISS_N1 | NONUNIQUE | APPS_TS_TX_IDX | CARD_ISSUER_CODE |
| IBY_CC_ISSUER_RANGES_LEN_N2 | NONUNIQUE | APPS_TS_TX_IDX | CARD_NUMBER_LENGTH |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| CC_ISSUER_RANGE_ID | NUMBER | (15) | Y | Primary key for the |
| CARD_ISSUER_CODE | VARCHAR2 | (30) | Y | The card issuer owning this card range |
| CARD_NUMBER_PREFIX | VARCHAR2 | (30) | Common prefix for all card numbers under this issuer | |
| CARD_NUMBER_LENGTH | NUMBER | (15) | Number of digits in the card number | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who Column |
| CREATION_DATE | DATE | Y | Standard Who Column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who Column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who Column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who Column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Object Version Number |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_CC_ISSUER_RANGES does not reference any database object
IBY.IBY_CC_ISSUER_RANGES is referenced by following:
| Description: | IBY_CREDITACRD stores Credit Card related information of the customer(payer) or payee. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_CREDITCARD.ACCTTYPEID | IBY_ACCTTYPE |
| IBY_CREDITCARD.CHNAME_SEC_SEGMENT_ID | IBY_SECURITY_SEGMENTS |
| IBY_CREDITCARD.ADDRESSID | HZ_PARTY_SITE_USES |
| IBY_CREDITCARD.CARD_OWNER_ID | HZ_PARTIES |
| IBY_CREDITCARD.CARD_ISSUER_CODE | IBY_CREDITCARD_ISSUERS_B |
| IBY_CREDITCARD.CC_ISSUER_RANGE_ID | IBY_CC_ISSUER_RANGES |
| IBY_CREDITCARD.CC_NUM_SEC_SEGMENT_ID | % |
| IBY_CREDITCARD.BILL_ADDR_TERRITORY_CODE | FND_TERRITORIES |
| IBY_CREDITCARD.UPGRADE_ADDRESSID | HZ_LOCATIONS |
| IBY_CREDITCARD.EXPIRY_SEC_SEGMENT_ID | IBY_SECURITY_SEGMENTS |
| Foreign Key Column | Foreign Table |
|---|---|
| AP_CARDS_ALL.CARD_REFERENCE_ID | IBY_CREDITCARD |
| IBY_CREDITCARD_H.INSTRID | IBY_CREDITCARD |
| IBY_INSTRHOLDER.INSTRID | IBY_CREDITCARD |
Holds credit card details
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_CREDITCARD_INSTRID_U1 | UNIQUE | APPS_TS_TX_IDX | INSTRID |
| IBY_CREDITCARD_CCNUMBER_N1 | NONUNIQUE | APPS_TS_TX_IDX |
CC_NUMBER_HASH1
CC_NUMBER_HASH2 |
| IBY_CREDITCARD_ENCRYPTED_N2 | NONUNIQUE | APPS_TS_TX_IDX | ENCRYPTED |
| IBY_CREDITCARD_MASK_N4 | NONUNIQUE | APPS_TS_TX_IDX |
CARD_UNMASK_LENGTH
CARD_MASK_SETTING |
| IBY_CREDITCARD_OWNER | NONUNIQUE | APPS_TS_TX_IDX |
CARD_OWNER_ID
CCNUMBER |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| INSTRID | NUMBER | (15) | Y | Unique internal Identifier for this record. Generated using a database sequence. Sequence used is IBY_INSTR_S.nextval |
| CCNUMBER | VARCHAR2 | (30) | Y | The number of the credit card |
| EXPIRYDATE | DATE | Expiration date of the credit card | ||
| ACCTTYPEID | NUMBER | No longer used | ||
| ADDRESSID | NUMBER | Will become a foreign key to HZ_PARTY_SITE_USES.PARTY_SITE_USE_ID instead of HZ_LOCATIONS.LOCATION_ID ; changes to existing customer data will be implemented in an upgrade script | ||
| INSTRNAME | VARCHAR2 | (80) | No longer used | |
| DESCRIPTION | VARCHAR2 | (240) | The free text entered in the Description field of the credit card setup screen | |
| CHNAME | VARCHAR2 | (80) | Name of the card holder as mentioned on the card | |
| FINAME | VARCHAR2 | (80) | The free text entered in the financial institution field of the credit card setup screen | |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column - date when a user last updated this row. | |
| LAST_UPDATED_BY | NUMBER | Y | Standard who column - unique internal identifier user who last updated this row. Foreign key to the USER_ID column of the FND_USER table. | |
| CREATION_DATE | DATE | Y | Standard who column - date when this row was created. | |
| CREATED_BY | NUMBER | Y | Standard who column - unique internal identifier of user who created this row. Foreign key to the USER_ID column of the FND_USER table. | |
| LAST_UPDATE_LOGIN | NUMBER | Standard who column - operating system login of user who last updated this row. Foreign key to the LOGIN_ID column of the FND_LOGINS table. | ||
| OBJECT_VERSION_NUMBER | NUMBER | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. This number is incremented for every update to the row through the application. | |
| SUBTYPE | VARCHAR2 | (80) | No longer used | |
| SECURITY_GROUP_ID | NUMBER | Used in hosted environments | ||
| ENCRYPTED | VARCHAR2 | (1) | Flag indicating whether the credit card number is encrypted and stored in the database | |
| CARD_OWNER_ID | NUMBER | (15) | Owner TCA Party ID | |
| BILLING_ADDR_POSTAL_CODE | VARCHAR2 | (50) | Billing address postal code | |
| BILL_ADDR_TERRITORY_CODE | VARCHAR2 | (2) | Billing address territory code | |
| MASKED_CC_NUMBER | VARCHAR2 | (30) | Masked credit card number; to be used for display purposes | |
| CARD_MASK_SETTING | VARCHAR2 | (30) | Setup value for the masking of the card holder name. The lookup used is IBY_PMT_INSTR_MASKING. The possible values are - Display Last Digits, Display First Digits, etc. | |
| CARD_UNMASK_LENGTH | NUMBER | (2) | The number of digits that can be exposed while displaying the bank account number on the UI or reports. This can be numeric values like 4, 6, etc. | |
| CC_NUMBER_HASH1 | VARCHAR2 | (64) | Hash value 1 of the credit card number. Used for the encryption of the credit card number. | |
| CC_NUMBER_HASH2 | VARCHAR2 | (64) | Hash value 1 of the credit card number. Used for the encryption of the credit card number | |
| INSTRUMENT_TYPE | VARCHAR2 | (30) | Y | CREDITCARD |
| PURCHASECARD_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether the credit card is Purchase card (company card) |
| PURCHASECARD_SUBTYPE | VARCHAR2 | (30) | IBY_PURCHASECARD_SUBTYPE include B (Business Card), C (Corporate Card), P (Purchase Card) and U (Unknown). | |
| CARD_ISSUER_CODE | VARCHAR2 | (30) | The issuer of the card. The possible value are Visa, Amex, Mastercard, etc. The customers can also add the new credit card brands which are flown in to the credit card setup screen. | |
| CC_ISSUER_RANGE_ID | NUMBER | (15) | The reference for this column is IBY_CC_ISSUER_RANGES.CC_ISSUER_RANGE_ID and this is a system generated sequence number generated while inserting new BIN ranges into IBY_CC_ISSUER_RANGES | |
| CC_NUMBER_LENGTH | NUMBER | (3) | The length of the credit card number may be 13, 15, 16, etc. depending on the card issuer. | |
| ACTIVE_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether the credit card is active or inactive. |
| SINGLE_USE_FLAG | VARCHAR2 | (1) | Y or N flag indicating whether the credit card can be used only once. | |
| INFORMATION_ONLY_FLAG | VARCHAR2 | (1) | Y or N flag indicating whether the credit card is registered for information use only | |
| CARD_PURPOSE | VARCHAR2 | (30) | Purpose of the credit card whether Supplies or Education | |
| INACTIVE_DATE | DATE | Inactive date | ||
| CC_NUM_SEC_SEGMENT_ID | NUMBER | (15) | For security features | |
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | Descriptive Flexfield structure defining column | |
| ATTRIBUTE1 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE2 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE3 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE4 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE5 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE6 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE7 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE8 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE9 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE10 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE11 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE12 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE13 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE14 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE15 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE16 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE17 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE18 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE19 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE20 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE21 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE22 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE23 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE24 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE25 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE26 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE27 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE28 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE29 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE30 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| REQUEST_ID | NUMBER | (15) | Enhanced Who column Concurrent Program who column - concurrent request id of the program that last updated this row. Foreign key to the REQUEST_ID column of the FND_CONCURRENT_REQUESTS table. | |
| PROGRAM_APPLICATION_ID | NUMBER | (15) | Enhanced Who column Concurrent Program who column - application id of the program that last updated this row. Foreign key to the APPLICATION_ID column of the FND_APPLICATION table. | |
| PROGRAM_ID | NUMBER | (15) | Enhanced Who column Concurrent Program who column - program id of the program that last updated this row. Foreign key to the CONCURRENT_PROGRAM_ID column of the FND_CONCURRENT_PROGRAM table. | |
| PROGRAM_UPDATE_DATE | DATE | Enhanced Who column Concurrent Program who column - date when a program last updated this row). | ||
| UPGRADE_ADDRESSID | NUMBER | (15) | Upgrade column | |
| SEC_SUBKEY_ID | NUMBER | Identifies the security sub-key used to encrypt this instrument | ||
| SALT_VERSION | NUMBER | (2) | Denotes the versions of the encryption algorithm used for the credit card encryption. | |
| EXPIRY_SEC_SEGMENT_ID | NUMBER | (15) | For security purposes. | |
| CHNAME_SEC_SEGMENT_ID | NUMBER | (15) | For security purposes. | |
| EXPIRED_FLAG | VARCHAR2 | (1) | Marks if a card has already expired. This flag value is updated by the IBY_MARK_EXPIRED_CREDITCARDS Concurrent Program | |
| CHNAME_MASK_SETTING | VARCHAR2 | (30) | Setup value for the masking of the card holder name. The lookup used is IBY_PMT_INSTR_MASKING. The possible values are - Display Last Digits, Display First Digits, etc. | |
| CHNAME_UNMASK_LENGTH | NUMBER | (2) | Setup value for the masking of the card holder name. | |
| INVALID_FLAG | VARCHAR2 | (1) | Flag value to indicate if the creditcard is an invalid one | |
| INVALIDATION_REASON | VARCHAR2 | (100) | This column holds the invalidation reason for an invalid credit card |
IBY.IBY_CREDITCARD does not reference any database object
IBY.IBY_CREDITCARD is referenced by following:
| Description: | Holds historical data for credit cards |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_CREDITCARD_H.INSTRID | IBY_CREDITCARD |
| IBY_CREDITCARD_H.ADDRESSID | HZ_PARTY_SITE_USES |
| IBY_CREDITCARD_H.CARD_ISSUER_CODE | IBY_CREDITCARD_ISSUERS_B |
| IBY_CREDITCARD_H.CARD_OWNER_ID | HZ_PARTIES |
| IBY_CREDITCARD_H.CHNAME_SEC_SEGMENT_ID | IBY_SECURITY_SEGMENTS |
Holds historical data for credit cards
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_CREDITCARD_H_CHID_U1 | UNIQUE | APPS_TS_TX_IDX | CARD_HISTORY_CHANGE_ID |
| IBY_CREDITCARD_H_INSTRID_N1 | NONUNIQUE | APPS_TS_TX_IDX | INSTRID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| CARD_HISTORY_CHANGE_ID | NUMBER | (15) | Y | Credit card history change identifier |
| INSTRID | NUMBER | (15) | Y | Sequence: IBY_INSTR_S.nextval |
| EXPIRYDATE | DATE | Expiration date of the card | ||
| ADDRESSID | NUMBER | (15) | Will become a foreign key to HZ_PARTY_SITE_USES.PARTY_SITE_USE_ID instead of HZ_LOCATIONS.LOCATION_ID ; changes to existing customer data will be implemented in an upgrade script | |
| DESCRIPTION | VARCHAR2 | (240) | Description of payment instrument | |
| CHNAME | VARCHAR2 | (80) | Card holder name | |
| FINAME | VARCHAR2 | (80) | Financial institution name | |
| SECURITY_GROUP_ID | NUMBER | (15) | Used in hosted environments | |
| ENCRYPTED | VARCHAR2 | (1) | Flag indicating if the instrument is encrypted | |
| MASKED_CC_NUMBER | VARCHAR2 | (30) | Masked credit card number; to be used for display purposes | |
| CARD_OWNER_ID | NUMBER | (15) | Owner TCA Party ID | |
| INSTRUMENT_TYPE | VARCHAR2 | (30) | Y | CREDITCARD |
| PURCHASECARD_FLAG | VARCHAR2 | (1) | Y | N |
| PURCHASECARD_SUBTYPE | VARCHAR2 | (30) | IBY_PURCHASECARD_SUBTYPE include B (Business Card), C (Corporate Card), P (Purchase Card) and U (Unknown). | |
| CARD_ISSUER_CODE | VARCHAR2 | (30) | Y | Card Issuer Code if know. Otherwise UNKNOWN. |
| SINGLE_USE_FLAG | VARCHAR2 | (1) | Y | |
| INFORMATION_ONLY_FLAG | VARCHAR2 | (1) | Y or N flag indicating whether the credit card is registered for information use only | |
| CARD_PURPOSE | VARCHAR2 | (30) | Purpose of the credit card from lookup type IBY_CARD_PURPOSE | |
| ACTIVE_FLAG | VARCHAR2 | (1) | Y | Y |
| INACTIVE_DATE | DATE | Inactive date | ||
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | Descriptive Flexfield structure defining column | |
| ATTRIBUTE1 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE2 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE3 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE4 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE5 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE6 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE7 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE8 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE9 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE10 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE11 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE12 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE13 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE14 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE15 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE16 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE17 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE18 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE19 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE20 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE21 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE22 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE23 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE24 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE25 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE26 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE27 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE28 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE29 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE30 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| REQUEST_ID | NUMBER | (15) | Concurrent Who column | |
| PROGRAM_APPLICATION_ID | NUMBER | (15) | Concurrent Who column | |
| PROGRAM_ID | NUMBER | (15) | Concurrent Who column | |
| PROGRAM_UPDATE_DATE | DATE | Concurrent Who column | ||
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number | |
| EFFECTIVE_START_DATE | DATE | Active date | ||
| EFFECTIVE_END_DATE | DATE | Inactive date | ||
| EXPIRY_SEC_SEGMENT_ID | NUMBER | (15) | For Securrity purposes | |
| CHNAME_SEC_SEGMENT_ID | NUMBER | (15) | For Security purposes |
IBY.IBY_CREDITCARD_H does not reference any database object
IBY.IBY_CREDITCARD_H is referenced by following:
| Description: | Holds the list of accepted card brands |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_CC_ISSUER_RANGES.CARD_ISSUER_CODE | IBY_CREDITCARD_ISSUERS_B |
| IBY_CREDITCARD.CARD_ISSUER_CODE | IBY_CREDITCARD_ISSUERS_B |
| IBY_CREDITCARD_H.CARD_ISSUER_CODE | IBY_CREDITCARD_ISSUERS_B |
| IBY_CREDITCARD_ISSUERS_TL.CARD_ISSUER_CODE | IBY_CREDITCARD_ISSUERS_B |
Holds the list of accepted card brands
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_CREDITCARD_ISSUERS_B_U1 | UNIQUE | APPS_TS_TX_IDX |
CARD_ISSUER_CODE
ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| CARD_ISSUER_CODE | VARCHAR2 | (30) | Y | Card Issuer Code if know. Otherwise UNKNOWN. |
| CARD_ISSUER_ACCEPTED_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether the credit card brand is accepted for fund capture. |
| AUTHORIZATION_VALIDITY_PERIOD | NUMBER | (15) | Authorization validity period | |
| DIGIT_CHECK_FLAG | VARCHAR2 | (1) | Y | Whether a MOD-10 digit check applies to this issuer's card numbers |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. | |
| AUTH_REVERSAL_FLAG | VARCHAR2 | (1) | Indicates if authorization reversal is supported by the Payment System. U-UNSUPPORTED, F-FULL_ONLY, M-FULL_AND_PARTIAL | |
| ALLOW_CAPTURE_EX_AUTH_FLAG | VARCHAR2 | (1) | Y/N flag indicating if the payment system allows capture amount greater than authorization amount | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_CREDITCARD_ISSUERS_B does not reference any database object
IBY.IBY_CREDITCARD_ISSUERS_B is referenced by following:
| Description: | Holds the list of accepted card brands |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_CREDITCARD_ISSUERS_TL.CARD_ISSUER_CODE | IBY_CREDITCARD_ISSUERS_B |
Holds the list of accepted card brands
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_CREDITCARD_ISSUERS_TL_U1 | UNIQUE | APPS_TS_TX_IDX |
CARD_ISSUER_CODE
LANGUAGE ZD_EDITION_NAME |
| IBY_CREDITCARD_ISSUERS_TL_N1 | NONUNIQUE | APPS_TS_TX_IDX | CARD_ISSUER_CODE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| CARD_ISSUER_CODE | VARCHAR2 | (30) | Y | Card Issuer Code if know. Otherwise UNKNOWN. |
| CARD_ISSUER_NAME | VARCHAR2 | (100) | Y | Credit card brand name |
| DESCRIPTION | VARCHAR2 | (240) | Description of the credit card brand | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. | |
| LANGUAGE | VARCHAR2 | (4) | Y | Language code |
| SOURCE_LANG | VARCHAR2 | (4) | Y | Language code of the record's current language |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_CREDITCARD_ISSUERS_TL does not reference any database object
IBY.IBY_CREDITCARD_ISSUERS_TL is referenced by following:
| Description: | This table holds the mandate information for the bank accounts |
|---|
This table holds the mandate information for the bank accounts
| Index | Type | Tablespace | Column |
|---|---|---|---|
| SYS_IL0000510751C00028$$ | UNIQUE | APPS_TS_TX_DATA |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| DEBIT_AUTHORIZATION_ID | NUMBER | (15) | Y | Mandate Id/Debit Authorization id |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Standard Column |
| EXTERNAL_BANK_ACCOUNT_USE_ID | NUMBER | (15) | Y | Site use id of the bank account |
| AUTHORIZATION_REFERENCE_NUMBER | VARCHAR2 | (35) | Mnadate Reference Number | |
| INITIAL_DEBIT_AUTHORIZATION_ID | NUMBER | (15) | Y | Original mandate id |
| AUTHORIZATION_REVISION_NUMBER | NUMBER | (15) | Authorization Revision Number | |
| PAYMENT_TYPE_CODE | VARCHAR2 | (35) | Mandate type | |
| AMENDMENT_REASON_CODE | VARCHAR2 | (50) | Reason for the amendment | |
| AUTH_SIGN_DATE | DATE | Debit Auth Sign date | ||
| AUTH_CANCEL_DATE | DATE | Debit Auth Cancel Date | ||
| DEBIT_AUTH_METHOD | VARCHAR2 | (30) | DEBIT_AUTH_METHOD | |
| PRE_NOTIFICATION_REQUIRED_FLAG | VARCHAR2 | (1) | Flag to denote if pre-notification is required. | |
| CREDITOR_LEGAL_ENTITY_ID | NUMBER | (15) | Payee LE | |
| CREDITOR_LE_NAME | VARCHAR2 | (150) | Payee LE Name | |
| CREDITOR_IDENTIFIER | VARCHAR2 | (150) | Payee Identifier | |
| CREATED_BY | NUMBER | (15) | Y | Standard who |
| CREATION_DATE | DATE | Y | Standard when | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | last updated by |
| LAST_UPDATE_DATE | DATE | Y | Last updated date | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Y | Last updated login |
| DEBIT_AUTH_BEGIN | DATE | Y | Debit authorization begin date | |
| DEBIT_AUTH_END | DATE | Debit authorization end date | ||
| CURR_REC_INDI | VARCHAR2 | (1) | Currency record Indicator | |
| DEBIT_AUTH_FLAG | VARCHAR2 | (1) | Debit authorization flag | |
| DEBIT_AUTH_REFERENCE | VARCHAR2 | (100) | Debit auth reference details | |
| CUST_ADDR_ID | NUMBER | (15) | Cutomer Aaddress Identifier | |
| CUST_IDENTIFICATION_CODE | VARCHAR2 | (100) | Customer Identification code | |
| MANDATE_FILE | BLOB | (4000) | Mandate file |
IBY.IBY_DEBIT_AUTHORIZATIONS does not reference any database object
IBY.IBY_DEBIT_AUTHORIZATIONS is referenced by following:
| Description: | IBY_DEFAULT_BEP stores information that will allow a payment system account and funds capture process profile to be derived for a transaction should the routing rules fail to yield them. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_DEFAULT_BEP.BEPID | IBY_BEPINFO |
| IBY_DEFAULT_BEP.MPAYEEID | IBY_PAYEE |
| IBY_DEFAULT_BEP.BEP_ACCOUNT_ID | IBY_BEPKEYS |
IBY_DEFAULT_BEP stores information that will allow a payment system account and funds capture process profile to be derived for a transaction should the routing rules fail to yield them.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_DEFAULT_BEP_U1 | UNIQUE | APPS_TS_TX_IDX |
BEPID
INSTRTYPE MPAYEEID PAYMENT_CHANNEL_CODE ZD_EDITION_NAME |
| IBY_DEFAULT_BEP_BAM_N1 | NONUNIQUE | APPS_TS_TX_IDX |
BEPID
BEP_ACCOUNT_ID MPAYEEID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| INSTRTYPE | VARCHAR2 | (30) | Y | Type of Instrument supported by Back End Payment System |
| BEPID | NUMBER | (15) | Y | Back End Payment System identifier |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column - date when a user last updated this row. | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | This column is used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard who column - user who last updated this row (foreign key to FND_USER.USER_ID). |
| CREATION_DATE | DATE | Y | Standard who column - date when this row was created. | |
| CREATED_BY | NUMBER | (15) | Y | Standard who column - user who created this row (foreign key to FND_USER.USER_ID). |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard who column - operating system login of user who last updated this row (foreign key to FND_LOGINS.LOGIN_ID). | |
| SECURITY_GROUP_ID | NUMBER | Used in hosted environments | ||
| MPAYEEID | NUMBER | (15) | Payee identifier | |
| PAYMENT_CHANNEL_CODE | VARCHAR2 | (30) | Payment method of the transaction | |
| FNDCPT_USER_PROFILE_CODE | VARCHAR2 | (30) | Default funds capture process profile to be used for the payment method if routing rules fail to yield one | |
| BEP_ACCOUNT_ID | NUMBER | (15) | Default payment system account that | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_DEFAULT_BEP does not reference any database object
IBY.IBY_DEFAULT_BEP is referenced by following:
| Description: | IBY_DELIVERY_CHANNELS stores delivery channel information that is used as lookup values for external payee setup or documents payable. The table is similar to FND_LOOKUPS, but with a new column for territory identification. Products that us |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_DELIVERY_CHANNELS_B.TERRITORY_CODE | FND_TERRITORIES |
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_DELIVERY_CHANNELS_TL.DELIVERY_CHANNEL_CODE | IBY_DELIVERY_CHANNELS_B |
| IBY_DOCS_PAYABLE_ALL.DELIVERY_CHANNEL_CODE | IBY_DELIVERY_CHANNELS_B |
| IBY_EXTERNAL_PAYEES_ALL.DELIVERY_CHANNEL_CODE | IBY_DELIVERY_CHANNELS_B |
| IBY_PAYMENTS_ALL.DELIVERY_CHANNEL_CODE | IBY_DELIVERY_CHANNELS_B |
| IBY_TEMP_EXT_PAYEES.DELIVERY_CHANNEL_CODE | IBY_DELIVERY_CHANNELS_B |
IBY_DELIVERY_CHANNELS stores delivery channel information that is used as lookup values for external payee setup or documents payable. The table is similar to FND_LOOKUPS, but with a new column for territory identification. Products that use data in this table can code their LOVs to be sensitive to the country context, so that only values relevant for the country will appear. This table corresponds to the Delivery Channel Codes page.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_DELIVERY_CHANNELS_B_U1 | UNIQUE | APPS_TS_TX_IDX |
DELIVERY_CHANNEL_CODE
ZD_EDITION_NAME |
| IBY_DELIVERY_CHANNELS_B_N1 | NONUNIQUE | APPS_TS_TX_IDX | TERRITORY_CODE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| DELIVERY_CHANNEL_CODE | VARCHAR2 | (30) | Y | User entered primary key |
| FORMAT_VALUE | VARCHAR2 | (80) | Value required by the payment format that uses this delivery channel | |
| SEEDED_FLAG | VARCHAR2 | (1) | Y or N flag controlling updatability of records. Y indicates record was seeded by Oracle and may have user updates limited. | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number | |
| INACTIVE_DATE | DATE | Inactive date | ||
| TERRITORY_CODE | VARCHAR2 | (2) | Code of the country where the delivery channel code is assigned or used | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_DELIVERY_CHANNELS_B does not reference any database object
IBY.IBY_DELIVERY_CHANNELS_B is referenced by following:
| Description: | IBY_DELIVERY_CHANNELS stores delivery channel information that is used as lookup values for external payee setup or documents payable. The table is similar to FND_LOOKUPS, but with a new column for territory identification. Products that us |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_DELIVERY_CHANNELS_TL.DELIVERY_CHANNEL_CODE | IBY_DELIVERY_CHANNELS_B |
IBY_DELIVERY_CHANNELS stores delivery channel information that is used as lookup values for external payee setup or documents payable. The table is similar to FND_LOOKUPS, but with a new column for territory identification. Products that use data in this table can code their LOVs to be sensitive to the country context, so that only values relevant for the country will appear. This table corresponds to the Delivery Channel Codes page.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_DELIVERY_CHANNELS_TL_U1 | UNIQUE | APPS_TS_TX_IDX |
DELIVERY_CHANNEL_CODE
LANGUAGE ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| DELIVERY_CHANNEL_CODE | VARCHAR2 | (30) | Y | User entered primary key |
| LANGUAGE | VARCHAR2 | (4) | Y | Language code |
| SOURCE_LANG | VARCHAR2 | (4) | Y | Language code of the record's current language |
| MEANING | VARCHAR2 | (80) | Lookup meaning of delivery channel | |
| DESCRIPTION | VARCHAR2 | (240) | Lookup description of delivery channel | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_DELIVERY_CHANNELS_TL does not reference any database object
IBY.IBY_DELIVERY_CHANNELS_TL is referenced by following:
| Description: | "This table contains records of the documents payable which are updated by system while processing 'Build payments' program. IBY_DOCS_PAYABLE_ALL stores Oracle Payments' representation of source products' documents payable. A document pay |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
|
IBY_DOCS_PAYABLE_ALL.CALLING_APP_ID
IBY_DOCS_PAYABLE_ALL.PAY_PROC_TRXN_TYPE_CODE |
IBY_TRXN_TYPES_B |
| IBY_DOCS_PAYABLE_ALL.PAYMENT_SERVICE_REQUEST_ID | IBY_PAY_SERVICE_REQUESTS |
| IBY_DOCS_PAYABLE_ALL.EXTERNAL_BANK_ACCOUNT_ID | CE_BANK_ACCOUNTS |
| IBY_DOCS_PAYABLE_ALL.FORMATTING_PAYMENT_ID | IBY_PAYMENTS_ALL |
| IBY_DOCS_PAYABLE_ALL.PAYMENT_METHOD_CODE | IBY_PAYMENT_METHODS_B |
| IBY_DOCS_PAYABLE_ALL.PAYMENT_PROFILE_ID | IBY_ACCT_PMT_PROFILES_B |
| IBY_DOCS_PAYABLE_ALL.PAYMENT_ID | IBY_PAYMENTS_ALL |
| IBY_DOCS_PAYABLE_ALL.EXT_PAYEE_ID | IBY_EXTERNAL_PAYEES_ALL |
| IBY_DOCS_PAYABLE_ALL.PAYMENT_REASON_CODE | IBY_PAYMENT_REASONS_B |
| IBY_DOCS_PAYABLE_ALL.DELIVERY_CHANNEL_CODE | IBY_DELIVERY_CHANNELS_B |
| IBY_DOCS_PAYABLE_ALL.PAYMENT_FORMAT_CODE | IBY_FORMATS_B |
| IBY_DOCS_PAYABLE_ALL.INTERNAL_BANK_ACCOUNT_ID | CE_BANK_ACCOUNTS |
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_DOCUMENT_LINES.DOCUMENT_PAYABLE_ID | IBY_DOCS_PAYABLE_ALL |
| IBY_DOCUMENT_LINES_H.DOCUMENT_PAYABLE_ID | IBY_DOCS_PAYABLE_ALL |
IBY_DOCS_PAYABLE_ALL stores Oracle Payments' representation of source products' documents payable. A document payable is a supplier invoice or similar document that needs to be paid. This table contains the identifier for the source product's document payable. In addition, this table contains whatever document information is necessary for payment processing.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_DOCS_PAYABLE_ALL_U1 | UNIQUE | APPS_TS_TX_IDX | DOCUMENT_PAYABLE_ID |
| IBY_DOCS_PAYABLE_ALL_N1 | NONUNIQUE | APPS_TS_TX_IDX | PAYMENT_DATE |
| IBY_DOCS_PAYABLE_ALL_N10 | NONUNIQUE | APPS_TS_TX_IDX | PAYMENT_FORMAT_CODE |
| IBY_DOCS_PAYABLE_ALL_N11 | NONUNIQUE | APPS_TS_TX_IDX | INTERNAL_BANK_ACCOUNT_ID |
| IBY_DOCS_PAYABLE_ALL_N12 | NONUNIQUE | APPS_TS_TX_IDX | DOCUMENT_STATUS |
| IBY_DOCS_PAYABLE_ALL_N13 | NONUNIQUE | APPS_TS_TX_IDX |
CALLING_APP_ID
CALLING_APP_DOC_UNIQUE_REF1 CALLING_APP_DOC_UNIQUE_REF2 CALLING_APP_DOC_UNIQUE_REF3 CALLING_APP_DOC_UNIQUE_REF4 CALLING_APP_DOC_UNIQUE_REF5 |
| IBY_DOCS_PAYABLE_ALL_N14 | NONUNIQUE | APPS_TS_TX_IDX | FORMATTING_PAYMENT_ID |
| IBY_DOCS_PAYABLE_ALL_N15 | NONUNIQUE | APPS_TS_TX_IDX | REJECTED_DOCS_GROUP_ID |
| IBY_DOCS_PAYABLE_ALL_N16 | NONUNIQUE | APPS_TS_TX_IDX | COMPLETED_PMTS_GROUP_ID |
| IBY_DOCS_PAYABLE_ALL_N2 | NONUNIQUE | APPS_TS_TX_IDX | PAYMENT_SERVICE_REQUEST_ID |
| IBY_DOCS_PAYABLE_ALL_N3 | NONUNIQUE | APPS_TS_TX_IDX | EXTERNAL_BANK_ACCOUNT_ID |
| IBY_DOCS_PAYABLE_ALL_N4 | NONUNIQUE | APPS_TS_TX_IDX | PAYMENT_METHOD_CODE |
| IBY_DOCS_PAYABLE_ALL_N5 | NONUNIQUE | APPS_TS_TX_IDX | PAYMENT_PROFILE_ID |
| IBY_DOCS_PAYABLE_ALL_N6 | NONUNIQUE | APPS_TS_TX_IDX | PAYMENT_ID |
| IBY_DOCS_PAYABLE_ALL_N7 | NONUNIQUE | APPS_TS_TX_IDX | EXT_PAYEE_ID |
| IBY_DOCS_PAYABLE_ALL_N8 | NONUNIQUE | APPS_TS_TX_IDX | PAYMENT_REASON_CODE |
| IBY_DOCS_PAYABLE_ALL_N9 | NONUNIQUE | APPS_TS_TX_IDX | DELIVERY_CHANNEL_CODE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAY_PROC_TRXN_TYPE_CODE | VARCHAR2 | (100) | Y | Type of payment processing transaction or document |
| CALLING_APP_ID | NUMBER | (15) | Y | Calling product Identifier |
| CALLING_APP_DOC_REF_NUMBER | VARCHAR2 | (100) | Y | Reference number entered by user of the source product. Need not be unique |
| DOCUMENT_PAYABLE_ID | NUMBER | (15) | Y | Oracle Payments' unique internal document payable Identifier |
| PAYMENT_FUNCTION | VARCHAR2 | (30) | Y | Function or purpose of the payment. Values from the lookup IBY_PAYMENT_FUNCTIONS include SUPPLIER_PAYMENT, CUSTOMER_REFUNDS, and others. |
| PAYMENT_DATE | DATE | Y | Payment date | |
| DOCUMENT_DATE | DATE | Y | Date of document | |
| DOCUMENT_TYPE | VARCHAR2 | (30) | Y | Type of document payable. Values from the IBY_DOCUMENT_TYPES lookup include INVOICE. |
| DOCUMENT_STATUS | VARCHAR2 | (30) | Y | Document status. Values from the lookup IBY_DOCS_PAYABLE_STATUSES include PAYMENT CREATED. |
| DOCUMENT_CURRENCY_CODE | VARCHAR2 | (10) | Y | Document currency code |
| DOCUMENT_AMOUNT | NUMBER | Y | Total amount in document currency | |
| PAYMENT_CURRENCY_CODE | VARCHAR2 | (10) | Y | Payment currency code |
| PAYMENT_AMOUNT | NUMBER | Y | Amount to be paid in payment currency | |
| PAYMENT_SERVICE_REQUEST_ID | NUMBER | (15) | Y | Identifier of the payment process request in which this document was submitted |
| PAYMENT_METHOD_CODE | VARCHAR2 | (30) | Y | Payment method Identifier |
| EXCLUSIVE_PAYMENT_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether this document payable should not be grouped with any other documents payable. |
| STRAIGHT_THROUGH_FLAG | VARCHAR2 | (1) | Y | When processing type Printed and if automatically print after formatting check box is selected, the flag is set to Y, otherwise N. Similarly, when processing type is electronic and payment completion point is selected as when payment instruction is transmitted, the flag is set to Y, otherwise, N. |
| EXT_PAYEE_ID | NUMBER | (15) | Y | External payee Identifier |
| PAYEE_PARTY_ID | NUMBER | (15) | Y | TCA party Identifier |
| LEGAL_ENTITY_ID | NUMBER | (15) | Y | Legal entity Identifier |
| ORG_ID | NUMBER | (15) | Y | Unique internal identifier of the Operating Unit. Validated against HR_OPERATING_UNITS.ORGANIZATION_ID. |
| ALLOW_REMOVING_DOCUMENT_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether this document can be removed from a payment or payment process request.AP is passing this value to Payments but no specific processing is happening based on this flag. |
| CREATED_BY | NUMBER | (15) | Y | Standard who column - unique internal identifier of user who created this row. Foreign key to the USER_ID column of the FND_USER table. |
| CREATION_DATE | DATE | Y | Standard who column - date when this row was created. | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard who column - unique internal identifier user who last updated this row. Foreign key to the USER_ID column of the FND_USER table. |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column - date when a user last updated this row. | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. This number is incremented for every update to the row through the application. | |
| CALLING_APP_DOC_UNIQUE_REF1 | VARCHAR2 | (100) | Y | Source product''s first unique document payable Identifier |
| CALLING_APP_DOC_UNIQUE_REF2 | VARCHAR2 | (100) | Source product''s second unique document payable Identifier | |
| CALLING_APP_DOC_UNIQUE_REF3 | VARCHAR2 | (100) | Source product''s third unique document payable Identifier | |
| CALLING_APP_DOC_UNIQUE_REF4 | VARCHAR2 | (100) | Source product''s fourth unique document payable Identifier | |
| CALLING_APP_DOC_UNIQUE_REF5 | VARCHAR2 | (100) | Source product''s fifth unique document payable Identifier | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard who column - operating system login of user who last updated this row. Foreign key to the LOGIN_ID column of the FND_LOGINS table. | |
| PARTY_SITE_ID | NUMBER | (15) | Party Site identifier Party Site Unique identifier from TCA tables. Validated against HZ_PARTY_SITES.PARTY_SITE_ID. | |
| SUPPLIER_SITE_ID | NUMBER | (15) | Supplier site identifier. Validated against PO_VENDOR_SITES_ALL.VENDOR_SITE_ID. | |
| BENEFICIARY_PARTY | NUMBER | (15) | Beneficiary party if payment is made through a third party | |
| ORG_TYPE | VARCHAR2 | (30) | Y | Organization type. Values from the lookup IBY_ORGANIZATION_TYPES include Operating Unit, Business Group, and Legal Entity. |
| ANTICIPATED_VALUE_DATE | DATE | Anticipated value date | ||
| PO_NUMBER | VARCHAR2 | (255) | Purchase order numbers to which this document is matched. If multiple purchase orders, value is comma delimited | |
| DOCUMENT_DESCRIPTION | VARCHAR2 | (255) | Document description | |
| DOCUMENT_CURRENCY_TAX_AMOUNT | NUMBER | Tax amount in document currency | ||
| DOCUMENT_CURR_CHARGE_AMOUNT | NUMBER | Charge amount in document currency | ||
| AMOUNT_WITHHELD | NUMBER | Amount withheld in payment currency | ||
| PAYMENT_CURR_DISCOUNT_TAKEN | NUMBER | Discount taken in payment currency | ||
| DISCOUNT_DATE | DATE | Discount date | ||
| PAYMENT_DUE_DATE | DATE | Date on which the payment is due | ||
| PAYMENT_PROFILE_ID | NUMBER | (15) | Payment process profile Identifier | |
| PAYMENT_ID | NUMBER | (15) | Payment Identifier. This field is populated once this document has been grouped into a payment. | |
| FORMATTING_PAYMENT_ID | NUMBER | (15) | Formatting payment Identifier. This field identifies the payment stub on which this document's details are printed. This field is populated when the document has been grouped into a payment. | |
| INTERNAL_BANK_ACCOUNT_ID | NUMBER | (15) | Internal bank account Identifier | |
| EXTERNAL_BANK_ACCOUNT_ID | NUMBER | (15) | External bank account Identifier | |
| BANK_CHARGE_BEARER | VARCHAR2 | (30) | Bearer of bank charge cost. Bank charge bearers are defined as the lookup IBY_BANK_CHARGE_BEARER. | |
| INTEREST_RATE | NUMBER | Interest rate on which this document payable was created if it is an interest invoice | ||
| PAYMENT_GROUPING_NUMBER | NUMBER | (15) | This attribute is used to link a set of documents payable. All documents payable that have the same payment grouping number are grouped into a single payment. | |
| PAYMENT_REASON_CODE | VARCHAR2 | (30) | Payment reason code | |
| PAYMENT_REASON_COMMENTS | VARCHAR2 | (240) | Free text field available for entering a reason for the payment | |
| SETTLEMENT_PRIORITY | VARCHAR2 | (30) | Priority with which the financial institution or payment system settles payment for this document. The available values for this column come from the FND lookup IBY_SETTLEMENT_PRIORITY. | |
| REMITTANCE_MESSAGE1 | VARCHAR2 | (150) | Remittance message for use in payment processing | |
| REMITTANCE_MESSAGE2 | VARCHAR2 | (150) | Remittance message for use in payment processing | |
| REMITTANCE_MESSAGE3 | VARCHAR2 | (150) | Remittance message for use in payment processing | |
| UNIQUE_REMITTANCE_IDENTIFIER | VARCHAR2 | (30) | Unique remittance Identifier provided by the payee | |
| URI_CHECK_DIGIT | VARCHAR2 | (2) | Unique remittance Identifier check digit | |
| DELIVERY_CHANNEL_CODE | VARCHAR2 | (30) | Delivery channel code | |
| PAYMENT_FORMAT_CODE | VARCHAR2 | (30) | Payment format code | |
| DOCUMENT_SEQUENCE_ID | NUMBER | Sequential numbering document sequence Identifier | ||
| DOCUMENT_SEQUENCE_VALUE | NUMBER | Sequence number of document payable | ||
| DOCUMENT_CATEGORY_CODE | VARCHAR2 | (30) | Sequential numbering document category | |
| BANK_ASSIGNED_REF_CODE | VARCHAR2 | (30) | Payment system-provided reference code for this document | |
| REMIT_TO_LOCATION_ID | NUMBER | (15) | Remit-To address Identifier | |
| COMPLETED_PMTS_GROUP_ID | NUMBER | (15) | Identifier of a group of payments, which include this document, that were marked complete. The value is from the sequence IBY_COMPLETED_PMTS_GROUP_S. | |
| REJECTED_DOCS_GROUP_ID | NUMBER | (15) | Identifier of a group of documents payable, including this one, which were rejected together. The value is from the sequence IBY_REJECTED_DOCS_S. | |
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | Descriptive Flexfield structure defining column | |
| ATTRIBUTE1 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE2 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE3 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE4 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE5 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE6 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE7 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE8 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE9 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE10 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE11 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE12 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE13 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE14 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE15 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ADDRESS_SOURCE | VARCHAR2 | (30) | Source of the address. Possible values from the lookup IBY_ADDRESS_SOURCE_TYPES include TCA and HR. | |
| EMPLOYEE_ADDRESS_CODE | VARCHAR2 | (30) | Type of address. Possible values include HOME and OFFICE. | |
| EMPLOYEE_PERSON_ID | NUMBER | (15) | Employee person Identifier | |
| EMPLOYEE_PAYMENT_FLAG | VARCHAR2 | (1) | Y or N flag indicating whether the payment is of the employee payment type | |
| EMPLOYEE_ADDRESS_ID | NUMBER | (15) | HR Identifier of the address | |
| EXT_INV_PAYEE_ID | NUMBER | (22) | This would be same as EXT_PAYEE_ID if there is no third payments agreement for the trading partner on the invoice. If there is a third party payment agreement with any payee for the trading partner, then this is same as the trading partner on the invoice. | |
| INV_PAYEE_PARTY_ID | NUMBER | (22) | This would be same as PAYEE_PARTY_ID if there is no third payments agreement for the trading partner on the invoice. If there is a third party payment agreement with any payee for the trading partner, then this is the same as the trading partner on the invoice. | |
| INV_PARTY_SITE_ID | NUMBER | (22) | This would be same as PARTY_SITE_ID if there is no third payments agreement for the trading partner on the invoice. If there is a third party payment agreement with any payee for the trading partner, then this is the same as the trading partners site id on the invoice. | |
| INV_SUPPLIER_SITE_ID | NUMBER | (22) | This would be same as SUPPLIER_SITE_ID if there is no third payments agreement for the trading partner on the invoice. If there is a third party payment agreement with any payee for the trading partner, then this is same as the trading partners supplier site id on the invoice. | |
| INV_BENEFICIARY_PARTY | NUMBER | (22) | This field always displays the same value as BENEFICIARY_PARTY. | |
| RELATIONSHIP_ID | NUMBER | (22) | Identifies the relation ship between payee and original trading partner. key from IBY_EXT_PAYEE_RELATIONSHIPS. | |
| GLOBAL_ATTRIBUTE_CATEGORY | VARCHAR2 | (240) | Global Descriptive Flexfield structure defining column. | |
| GLOBAL_ATTRIBUTE1 | VARCHAR2 | (240) | Global Descriptive Flexfield segment. | |
| GLOBAL_ATTRIBUTE2 | VARCHAR2 | (240) | Global Descriptive Flexfield segment. | |
| GLOBAL_ATTRIBUTE3 | VARCHAR2 | (240) | Global Descriptive Flexfield segment. | |
| GLOBAL_ATTRIBUTE4 | VARCHAR2 | (240) | Global Descriptive Flexfield segment. | |
| GLOBAL_ATTRIBUTE5 | VARCHAR2 | (240) | Global Descriptive Flexfield segment. | |
| GLOBAL_ATTRIBUTE6 | VARCHAR2 | (240) | Global Descriptive Flexfield segment. | |
| GLOBAL_ATTRIBUTE7 | VARCHAR2 | (240) | Global Descriptive Flexfield segment. | |
| GLOBAL_ATTRIBUTE8 | VARCHAR2 | (240) | Global Descriptive Flexfield segment. | |
| GLOBAL_ATTRIBUTE9 | VARCHAR2 | (240) | Global Descriptive Flexfield segment. | |
| GLOBAL_ATTRIBUTE10 | VARCHAR2 | (240) | Global Descriptive Flexfield segment. | |
| GLOBAL_ATTRIBUTE11 | VARCHAR2 | (240) | Global Descriptive Flexfield segment. | |
| GLOBAL_ATTRIBUTE12 | VARCHAR2 | (240) | Global Descriptive Flexfield segment. | |
| GLOBAL_ATTRIBUTE13 | VARCHAR2 | (240) | Global Descriptive Flexfield segment. | |
| GLOBAL_ATTRIBUTE14 | VARCHAR2 | (240) | Global Descriptive Flexfield segment. | |
| GLOBAL_ATTRIBUTE15 | VARCHAR2 | (240) | Global Descriptive Flexfield segment. | |
| GLOBAL_ATTRIBUTE16 | VARCHAR2 | (240) | Global Descriptive Flexfield segment. | |
| GLOBAL_ATTRIBUTE17 | VARCHAR2 | (240) | Global Descriptive Flexfield segment. | |
| GLOBAL_ATTRIBUTE18 | VARCHAR2 | (240) | Global Descriptive Flexfield segment. | |
| GLOBAL_ATTRIBUTE19 | VARCHAR2 | (240) | Global Descriptive Flexfield segment. | |
| GLOBAL_ATTRIBUTE20 | VARCHAR2 | (240) | Global Descriptive Flexfield segment. | |
| AFFECTS_REJECTION_LEVEL | VARCHAR2 | (1) |
IBY.IBY_DOCS_PAYABLE_ALL does not reference any database object
IBY.IBY_DOCS_PAYABLE_ALL is referenced by following:
| Description: |
|---|
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_DOCS_PAYABLE_GT_N1 | NONUNIQUE | DOCUMENT_PAYABLE_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| DOCUMENT_PAYABLE_ID | NUMBER | (15) | Y | |
| CALLING_APP_ID | NUMBER | (15) | Y | |
| CALLING_APP_DOC_UNIQUE_REF1 | VARCHAR2 | (100) | Y | |
| CALLING_APP_DOC_UNIQUE_REF2 | VARCHAR2 | (100) | ||
| CALLING_APP_DOC_UNIQUE_REF3 | VARCHAR2 | (100) | ||
| CALLING_APP_DOC_UNIQUE_REF4 | VARCHAR2 | (100) | ||
| CALLING_APP_DOC_UNIQUE_REF5 | VARCHAR2 | (100) | ||
| CALLING_APP_DOC_REF_NUMBER | NUMBER | (15) | ||
| PAY_PROC_TRXN_TYPE_CODE | VARCHAR2 | (100) | Y | |
| PAYMENT_METHOD_CODE | VARCHAR2 | (30) | Y | |
| PAYMENT_FORMAT_CODE | VARCHAR2 | (30) | ||
| PAYMENT_AMOUNT | NUMBER | Y | ||
| EXCLUSIVE_PAYMENT_FLAG | VARCHAR2 | (1) | Y | |
| PAYMENT_PROFILE_ID | NUMBER | (15) | ||
| PAYMENT_FUNCTION | VARCHAR2 | (30) | ||
| PROCESS_TYPE | VARCHAR2 | (30) | ||
| DOCUMENT_DATE | DATE | |||
| DOCUMENT_TYPE | VARCHAR2 | (30) | ||
| DOCUMENT_DESCRIPTION | VARCHAR2 | (255) | ||
| DOCUMENT_AMOUNT | NUMBER | |||
| DOCUMENT_CURRENCY_TAX_AMOUNT | NUMBER | |||
| DOCUMENT_CURR_CHARGE_AMOUNT | NUMBER | |||
| PAYMENT_CURR_DISCOUNT_TAKEN | NUMBER | |||
| PAYMENT_DUE_DATE | DATE | |||
| PAYMENT_GROUPING_NUMBER | NUMBER | (15) | ||
| INTERNAL_BANK_ACCOUNT_ID | NUMBER | (15) | ||
| EXTERNAL_BANK_ACCOUNT_ID | NUMBER | (15) | ||
| PAYEE_PARTY_ID | NUMBER | (15) | ||
| PAYEE_PARTY_SITE_ID | NUMBER | (15) | ||
| SUPPLIER_SITE_ID | NUMBER | (15) | ||
| REMIT_TO_LOCATION_ID | NUMBER | (15) | ||
| LEGAL_ENTITY_ID | NUMBER | |||
| ORG_ID | NUMBER | (15) | ||
| ORG_TYPE | VARCHAR2 | (30) | ||
| DOCUMENT_CURRENCY_CODE | VARCHAR2 | (10) | ||
| PAYMENT_CURRENCY_CODE | VARCHAR2 | (10) | Y | |
| BANK_CHARGE_BEARER | VARCHAR2 | (80) | ||
| BANK_CHARGE_AMOUNT | NUMBER | |||
| PAYMENT_CURR_BANK_CHARGES | NUMBER | (15) | ||
| PAYMENT_DATE | DATE | |||
| ANTICIPATED_VALUE_DATE | DATE | |||
| PAYMENT_REASON_CODE | VARCHAR2 | (30) | ||
| PAYMENT_REASON_COMMENTS | VARCHAR2 | (240) | ||
| SETTLEMENT_PRIORITY | VARCHAR2 | (30) | ||
| REMITTANCE_MESSAGE1 | VARCHAR2 | (150) | ||
| REMITTANCE_MESSAGE2 | VARCHAR2 | (150) | ||
| REMITTANCE_MESSAGE3 | VARCHAR2 | (150) | ||
| UNIQUE_REMITTANCE_IDENTIFIER | VARCHAR2 | (30) | ||
| URI_CHECK_DIGIT | VARCHAR2 | (30) | ||
| BANK_ASSIGNED_REF_CODE | VARCHAR2 | (30) | ||
| DELIVERY_CHANNEL_CODE | VARCHAR2 | (30) | ||
| INTEREST_RATE | NUMBER | |||
| PO_NUMBER | VARCHAR2 | (255) | ||
| AMOUNT_WITHHELD | NUMBER | |||
| DISCOUNT_DATE | DATE | |||
| DOC_SEQUENCE_ID | NUMBER | |||
| DOC_SEQUENCE_VALUE | NUMBER | |||
| ALLOW_REMOVING_DOCUMENT_FLAG | VARCHAR2 | (1) | Y | |
| DOC_CATEGORY_CODE | VARCHAR2 | (30) | ||
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | ||
| ATTRIBUTE1 | VARCHAR2 | (150) | ||
| ATTRIBUTE2 | VARCHAR2 | (150) | ||
| ATTRIBUTE3 | VARCHAR2 | (150) | ||
| ATTRIBUTE4 | VARCHAR2 | (150) | ||
| ATTRIBUTE5 | VARCHAR2 | (150) | ||
| ATTRIBUTE6 | VARCHAR2 | (150) | ||
| ATTRIBUTE7 | VARCHAR2 | (150) | ||
| ATTRIBUTE8 | VARCHAR2 | (150) | ||
| ATTRIBUTE9 | VARCHAR2 | (150) | ||
| ATTRIBUTE10 | VARCHAR2 | (150) | ||
| ATTRIBUTE11 | VARCHAR2 | (150) | ||
| ATTRIBUTE12 | VARCHAR2 | (150) | ||
| ATTRIBUTE13 | VARCHAR2 | (150) | ||
| ATTRIBUTE14 | VARCHAR2 | (150) | ||
| ATTRIBUTE15 | VARCHAR2 | (150) | ||
| CREATED_BY | NUMBER | (15) | Y | |
| CREATION_DATE | DATE | Y | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| LAST_UPDATE_DATE | DATE | Y | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| OBJECT_VERSION_NUMBER | NUMBER | Y |
IBY.IBY_DOCS_PAYABLE_GT does not reference any database object
IBY.IBY_DOCS_PAYABLE_GT is referenced by following:
| Description: |
|---|
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_DOCS_PAYABLE_VAL_GT1_U1 | NONUNIQUE | DOCUMENT_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| CALLING_APP_ID | NUMBER | (15) | Y | |
| CALLING_APP_DOC_ID1 | VARCHAR2 | (100) | Y | |
| CALLING_APP_DOC_ID2 | VARCHAR2 | (100) | ||
| CALLING_APP_DOC_ID3 | VARCHAR2 | (100) | ||
| CALLING_APP_DOC_ID4 | VARCHAR2 | (100) | ||
| CALLING_APP_DOC_ID5 | VARCHAR2 | (100) | ||
| PAY_PROC_TRXN_TYPE_CD | VARCHAR2 | (100) | ||
| DOCUMENT_ID | NUMBER | (15) | Y | |
| DOCUMENT_AMOUNT | NUMBER | |||
| DOCUMENT_PAY_CURRENCY | VARCHAR2 | (10) | ||
| EXCLUSIVE_PAYMENT_FLAG | VARCHAR2 | (1) | ||
| DELIVERY_CHANNEL_CODE | VARCHAR2 | (30) | ||
| DELIVERY_CHN_FORMAT_VAL | VARCHAR2 | (80) | ||
| UNIQUE_REMIT_ID_CODE | VARCHAR2 | (30) | ||
| PAYMENT_REASON_COMMENTS | VARCHAR2 | (240) | ||
| SETTLEMENT_PRIORITY | VARCHAR2 | (30) | ||
| REMITTANCE_MESSAGE1 | VARCHAR2 | (150) | ||
| REMITTANCE_MESSAGE2 | VARCHAR2 | (150) | ||
| REMITTANCE_MESSAGE3 | VARCHAR2 | (150) | ||
| URI_CHECK_DIGIT | VARCHAR2 | (2) | ||
| EXTERNAL_BANK_ACCOUNT_ID | NUMBER | (15) | ||
| INT_BANK_NUM | VARCHAR2 | (30) | ||
| INT_BANK_NAME | VARCHAR2 | (360) | ||
| INT_BANK_NAME_ALT | VARCHAR2 | (320) | ||
| INT_BANK_BRANCH_NUM | VARCHAR2 | (30) | ||
| INT_BANK_BRANCH_NAME | VARCHAR2 | (360) | ||
| INT_BANK_BRANCH_NAME_ALT | VARCHAR2 | (320) | ||
| INT_BANK_ACC_NUM | VARCHAR2 | (30) | ||
| INT_BANK_ACC_NAME | VARCHAR2 | (100) | ||
| INT_BANK_ACC_NAME_ALT | VARCHAR2 | (320) | ||
| INT_BANK_ACC_TYPE | VARCHAR2 | (25) | ||
| INT_BANK_ACC_IBAN | VARCHAR2 | (50) | ||
| INT_BANK_ACC_CURR | VARCHAR2 | (15) | ||
| INT_BANK_ASSIGNED_ID1 | VARCHAR2 | (240) | ||
| INT_BANK_ASSIGNED_ID2 | VARCHAR2 | (240) | ||
| INT_EFT_USER_NUMBER | VARCHAR2 | (30) | ||
| INT_BANK_ACC_CHK_DGTS | VARCHAR2 | (30) | ||
| INT_EFT_REQ_IDENTIFIER | VARCHAR2 | (25) | ||
| INT_BANK_ACC_SHORT_NAME | VARCHAR2 | (30) | ||
| INT_BANK_ACC_HOLDER_NAME | VARCHAR2 | (240) | ||
| INT_BANK_ACC_HOLDER_NAME_ALT | VARCHAR2 | (150) | ||
| PAYER_LE_NAME | VARCHAR2 | (240) | ||
| PAYER_LE_COUNTRY | VARCHAR2 | (60) | ||
| PAYER_PHONE | VARCHAR2 | (100) | ||
| PAYER_REGISTRATION_NUMBER | VARCHAR2 | (30) | ||
| PAYER_TAX_REGISTRATION_NUMBER | VARCHAR2 | (50) | ||
| EXT_BANK_NUM | VARCHAR2 | (30) | ||
| EXT_BANK_NAME | VARCHAR2 | (360) | ||
| EXT_BANK_NAME_ALT | VARCHAR2 | (320) | ||
| EXT_BANK_BRANCH_NUM | VARCHAR2 | (30) | ||
| EXT_BANK_BRANCH_NAME | VARCHAR2 | (360) | ||
| EXT_BANK_BRANCH_NAME_ALT | VARCHAR2 | (320) | ||
| EXT_BANK_COUNTRY | VARCHAR2 | (2) | ||
| EXT_BANK_BRANCH_ADDR1 | VARCHAR2 | (240) | ||
| EXT_BANK_BRANCH_COUNTRY | VARCHAR2 | (60) | ||
| EXT_BANK_ACC_NUM | VARCHAR2 | (100) | ||
| EXT_BANK_ACC_NAME | VARCHAR2 | (80) | ||
| EXT_BANK_ACC_NAME_ALT | VARCHAR2 | (320) | ||
| EXT_BANK_ACC_TYPE | VARCHAR2 | (25) | ||
| EXT_BANK_ACC_IBAN | VARCHAR2 | (50) | ||
| EXT_BANK_ACC_CHK_DGTS | VARCHAR2 | (30) | ||
| EXT_BANK_ACC_SHORT_NAME | VARCHAR2 | (30) | ||
| EXT_BANK_ACC_HOLDER_NAME | VARCHAR2 | (360) | ||
| EXT_BANK_ACC_HOLDER_NAME_ALT | VARCHAR2 | (320) | ||
| EXT_BANK_ACC_BIC | VARCHAR2 | (30) | ||
| PAYEE_PARTY_NAME | VARCHAR2 | (360) | ||
| PAYEE_PARTY_ADDR1 | VARCHAR2 | (240) | ||
| PAYEE_PARTY_ADDR2 | VARCHAR2 | (240) | ||
| PAYEE_PARTY_ADDR3 | VARCHAR2 | (240) | ||
| PAYEE_PARTY_CITY | VARCHAR2 | (60) | ||
| PAYEE_PARTY_STATE | VARCHAR2 | (120) | ||
| PAYEE_PARTY_PROVINCE | VARCHAR2 | (120) | ||
| PAYEE_PARTY_COUNTY | VARCHAR2 | (120) | ||
| PAYEE_PARTY_POSTAL | VARCHAR2 | (60) | ||
| PAYEE_PARTY_COUNTRY | VARCHAR2 | (60) | ||
| BANK_CHARGE_BEARER | VARCHAR2 | (30) | ||
| PAYMENT_REASON_CODE | VARCHAR2 | (30) | ||
| PAYMENT_METHOD_CD | VARCHAR2 | (30) | ||
| PAYEE_PAYMENT_FORMAT_CD | VARCHAR2 | (30) | ||
| PAYEE_PARTY_SITE_NAME | VARCHAR2 | (240) | ||
| INT_BANK_BRANCH_TYPE | VARCHAR2 | (30) | ||
| EXT_BANK_BRANCH_TYPE | VARCHAR2 | (30) |
IBY.IBY_DOCS_PAYABLE_VAL_GT1 does not reference any database object
IBY.IBY_DOCS_PAYABLE_VAL_GT1 is referenced by following:
| Description: | IBY_DOCUMENTS_PAYABLE_H stores historical snapshots of documents payable. This table contains denormalized versions of documents payable from specific points in time, such as when the payment for this document was submitted to a payment sys |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_DOCUMENTS_PAYABLE_H.PAYMENT_PROFILE_ID | IBY_ACCT_PMT_PROFILES_B |
| IBY_DOCUMENTS_PAYABLE_H.PAYMENT_ID | IBY_PAYMENTS_ALL |
| IBY_DOCUMENTS_PAYABLE_H.PAYMENT_HISTORY_ID | IBY_PAYMENTS_H |
| IBY_DOCUMENTS_PAYABLE_H.PAYMENT_METHOD_CODE | IBY_PAYMENT_METHODS_B |
|
IBY_DOCUMENTS_PAYABLE_H.CALLING_APP_ID
IBY_DOCUMENTS_PAYABLE_H.PAY_PROC_TRXN_TYPE_CODE |
IBY_TRXN_TYPES_B |
| IBY_DOCUMENTS_PAYABLE_H.PAYMENT_SERVICE_REQUEST_ID | IBY_PAY_SERVICE_REQUESTS |
| IBY_DOCUMENTS_PAYABLE_H.COUNTRY | FND_TERRITORIES |
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_DOCUMENT_LINES_H.DOCUMENT_PAYABLE_HISTORY_ID | IBY_DOCUMENTS_PAYABLE_H |
IBY_DOCUMENTS_PAYABLE_H stores historical snapshots of documents payable. This table contains denormalized versions of documents payable from specific points in time, such as when the payment for this document was submitted to a payment system. Different snapshots of the same document payable can exist in this table. These snapshots are differentiated by the table's primary key and a snapshot date.
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| DOCUMENT_PAYABLE_HISTORY_ID | NUMBER | (15) | Y | System generated primary key |
| DOCUMENT_PAYABLE_HISTORY_DATE | DATE | Y | Document payable snapshot date | |
| PAYMENT_HISTORY_ID | NUMBER | (15) | Y | Associated payment snapshot Identifier |
| PAY_PROC_TRXN_TYPE_CODE | VARCHAR2 | (100) | Y | Type of payment processing transaction or document |
| CALLING_APP_ID | NUMBER | (15) | Y | Source product Identifier |
| CALLING_APP_DOC_UNIQUE_REF1 | VARCHAR2 | (100) | Y | Source product''s first unique document payable Identifier |
| CALLING_APP_DOC_UNIQUE_REF2 | VARCHAR2 | (100) | Source product''s second unique document payable Identifier | |
| CALLING_APP_DOC_UNIQUE_REF3 | VARCHAR2 | (100) | Source product''s third unique document payable Identifier | |
| CALLING_APP_DOC_UNIQUE_REF4 | VARCHAR2 | (100) | Source product''s fourth unique document payable Identifier | |
| CALLING_APP_DOC_UNIQUE_REF5 | VARCHAR2 | (100) | Source product''s fifth unique document payable Identifier | |
| CALLING_APP_DOC_REF_NUMBER | NUMBER | (15) | Y | Reference number entered by user of the source product. Need not be unique |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| STRAIGHT_THROUGH_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether the document payable has been processed without unexpected manual intervention |
| PO_NUMBER | VARCHAR2 | (255) | Purchase order numbers to which this document is matched. If multiple purchase orders, value is comma delimited. | |
| DOCUMENT_PAYABLE_ID | NUMBER | (15) | Y | Oracle Payments' unique internal document payable Identifier |
| PAYMENT_FUNCTION | VARCHAR2 | (30) | Y | Function or purpose of the payment. Values from the lookup IBY_PAYMENT_FUNCTIONS include SUPPLIER_PAYMENT, CUSTOMER_REFUNDS, and others. |
| DOCUMENT_DATE | DATE | Y | Date of document | |
| DOCUMENT_TYPE | VARCHAR2 | (30) | Y | Type of document payable. Values from the IBY_DOCUMENT_TYPES lookup include INVOICE. |
| DOCUMENT_DESCRIPTION | VARCHAR2 | (255) | Document description | |
| DOCUMENT_STATUS | VARCHAR2 | (30) | Y | Document status. Values from the lookup IBY_DOCS_PAYABLE_STATUSES include PAYMENT CREATED. |
| DOCUMENT_AMOUNT | NUMBER | Y | Total document amount | |
| DOCUMENT_CURRENCY_CODE | VARCHAR2 | (10) | Y | Document currency code |
| DOC_CURRENCY_PAYMENT_AMOUNT | NUMBER | Y | Amount to be paid in document currency | |
| DOCUMENT_CURRENCY_TAX_AMOUNT | NUMBER | Tax amount in document currency | ||
| DOCUMENT_CURR_CHARGE_AMOUNT | NUMBER | Charge amount in document currency | ||
| PAYMENT_AMOUNT | NUMBER | Y | Amount to be paid, in payment currency | |
| PAYMENT_CURRENCY_CODE | VARCHAR2 | (10) | Y | Payment currency code |
| PAYMENT_DUE_DATE | DATE | Y | Date on which the payment is made | |
| PAYMENT_CURR_DISCOUNT_TAKEN | NUMBER | Discount taken, in payment currency | ||
| DISCOUNT_DATE | DATE | Discount date | ||
| AMOUNT_WITHHELD | NUMBER | Amount withheld | ||
| PAYMENT_SERVICE_REQUEST_ID | NUMBER | (15) | Y | Identifier of the payment process request in which this document was submitted. |
| PAYMENT_METHOD_CODE | VARCHAR2 | (30) | Y | Payment method Identifier. |
| PAYMENT_PROFILE_ID | NUMBER | (15) | Y | Payment process profile Identifier |
| PAYMENT_ID | NUMBER | (15) | Y | Identifier of the payment in which this document was paid |
| FORMATTING_PAYMENT_ID | NUMBER | (15) | Formatting payment identifier. This field identifies the payment stub on which this document's details are printed. This field is populated when the document has been grouped into a payment. | |
| EXCLUSIVE_PAYMENT_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether this document payable corresponds to one payment. |
| INT_BANK_ACCOUNT_ROUTING_NUM | VARCHAR2 | (30) | Internal bank account routing number from CE bank accounts | |
| INT_BANK_ACCOUNT_NUMBER | VARCHAR2 | (30) | Internal bank account number from CE bank accounts | |
| INT_BANK_ACCOUNT_IBAN_NUMBER | VARCHAR2 | (50) | Internal bank account IBAN number from CE bank accounts | |
| EXT_BANK_ACCOUNT_ROUTING_NUM | VARCHAR2 | (30) | External bank account routing number from IBY bank accounts | |
| EXT_BANK_ACCOUNT_NUMBER | VARCHAR2 | (30) | External bank account number from IBY bank accounts | |
| EXT_BANK_ACCOUNT_BANK_NAME | VARCHAR2 | (360) | Internal bank account bank name from IBY bank accounts | |
| EXT_BANK_ACCOUNT_BRANCH_NAME | VARCHAR2 | (360) | Internal bank account branch name from IBY bank accounts | |
| EXT_BANK_ACCOUNT_BRANCH_NUMBER | VARCHAR2 | (30) | Internal bank account branch number from IBY bank accounts | |
| EXT_BANK_ACCOUNT_IBAN_NUMBER | VARCHAR2 | (50) | Internal bank account IBAN number from IBY bank accounts | |
| EXT_BANK_ACCOUNT_SWIFT_CODE | VARCHAR2 | (30) | Internal bank account SWIFT code from IBY bank accounts | |
| EXT_PAYEE_ID | NUMBER | (15) | External payee Identifier | |
| PARTY_SITE_ID | NUMBER | (15) | Payee party site Identifier | |
| PAYEE_PARTY_ID | NUMBER | (15) | TCA party Identifier | |
| SUPPLIER_SITE_ID | NUMBER | (15) | Supplier site Identifier | |
| PARTY_NAME | VARCHAR2 | (360) | Name of party from TCA parties | |
| COUNTRY | VARCHAR2 | (60) | Y | Country code from the TERRITORY_CODE column in the FND_TERRITORY table from TCA location |
| ADDRESS1 | VARCHAR2 | (240) | First line for address from TCA location | |
| ADDRESS2 | VARCHAR2 | (240) | Second line for address from TCA location | |
| ADDRESS3 | VARCHAR2 | (240) | Third line for address from TCA location | |
| ADDRESS4 | VARCHAR2 | (240) | Fourth line for address from TCA location | |
| CITY | VARCHAR2 | (60) | City from TCA location | |
| POSTAL_CODE | VARCHAR2 | (60) | Postal code from TCA location | |
| POSTAL_PLUS4_CODE | VARCHAR2 | (10) | Four digit extension to the United States Postal ZIP code from TCA location | |
| STATE | VARCHAR2 | (60) | State from TCA location | |
| PROVINCE | VARCHAR2 | (60) | Province from TCA location | |
| COUNTY | VARCHAR2 | (60) | County from TCA location | |
| BENEFICIARY_PARTY | NUMBER | (15) | Beneficiary party, if payment is made through a third party | |
| ORG_ID | NUMBER | (15) | Y | Organization Identifier |
| ORG_TYPE | VARCHAR2 | (30) | Organization type. Values from the lookup IBY_ORGANIZATION_TYPES include Operating Unit, Business Group, and Legal Entity. | |
| LEGAL_ENTITY_ID | NUMBER | (15) | Y | Legal entity Identifier |
| BANK_CHARGE_BEARER | VARCHAR2 | (30) | Bearer of bank charge cost. Bank charge bearers are defined as the lookup IBY_BANK_CHARGE_BEARER. | |
| INTEREST_RATE | NUMBER | Interest rate on which this document payable was created if it is an interest invoice | ||
| PAYMENT_GROUPING_NUMBER | NUMBER | (15) | Payment grouping number. All documents with the same grouping number are automatically grouped into a single payment. No document in the payment group can be removed from the payment unless the whole payment is removed. | |
| PAYMENT_REASON_FORMAT_VALUE | VARCHAR2 | (80) | Payment reason value required by the payment format that uses this payment reason | |
| PAYMENT_REASON_COMMENTS | VARCHAR2 | (240) | Free text field available for entering a reason for the payment | |
| SETTLEMENT_PRIORITY | VARCHAR2 | (30) | Priority with which the financial institution or payment system settles payment for this document. The available values for this column come from the FND lookup IBY_SETTLEMENT_PRIORITY. | |
| REMITTANCE_MESSAGE1 | VARCHAR2 | (150) | Remittance message for use in payment processing | |
| REMITTANCE_MESSAGE2 | VARCHAR2 | (150) | Remittance message for use in payment processing | |
| REMITTANCE_MESSAGE3 | VARCHAR2 | (150) | Remittance message for use in payment processing | |
| UNIQUE_REMITTANCE_IDENTIFIER | VARCHAR2 | (30) | Unique remittance Identifier provided by the payee | |
| URI_CHECK_DIGIT | VARCHAR2 | (2) | Unique remittance Identifier check digit | |
| DELIVERY_FORMAT_VALUE | VARCHAR2 | (80) | Y | Delivery value required by the payment format that uses this delivery channel |
| FORMAT_TEMPLATE_CODE | VARCHAR2 | (80) | Y | Payment format code, as defined in the XML Publisher registry |
| EXTRACT_CODE | VARCHAR2 | (30) | Code for the extract version | |
| DOCUMENT_CATEGORY_CODE | VARCHAR2 | (30) | Sequential numbering document category | |
| DOCUMENT_SEQUENCE_ID | NUMBER | Sequential numbering document sequence Identifier | ||
| DOCUMENT_SEQUENCE_VALUE | NUMBER | Sequence number of document payable | ||
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | Descriptive Flexfield structure defining column | |
| ATTRIBUTE1 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE2 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE3 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE4 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE5 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE6 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE7 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE8 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE9 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE10 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE11 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE12 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE13 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE14 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE15 | VARCHAR2 | (150) | Descriptive Flexfield segment |
IBY.IBY_DOCUMENTS_PAYABLE_H does not reference any database object
IBY.IBY_DOCUMENTS_PAYABLE_H is referenced by following:
| Description: | IBY_DOCUMENT_LINES stores Oracle Payments' representation of individual line items for documents payable, such as invoice lines for an Oracle Payables invoice. This information is passed according to payment format, but is not used to affec |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_DOCUMENT_LINES.DOCUMENT_PAYABLE_ID | IBY_DOCS_PAYABLE_ALL |
IBY_DOCUMENT_LINES stores Oracle Payments' representation of individual line items for documents payable, such as invoice lines for an Oracle Payables invoice. This information is passed according to payment format, but is not used to affect payment processing. Not every source product needs to have document lines.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_DOCUMENT_LINES_U1 | UNIQUE | APPS_TS_TX_IDX | DOCUMENT_PAYABLE_LINE_ID |
| IBY_DOCUMENT_LINES_N1 | NONUNIQUE | APPS_TS_TX_IDX | DOCUMENT_PAYABLE_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| DOCUMENT_PAYABLE_LINE_ID | NUMBER | (15) | Y | System generated primary key |
| DOCUMENT_PAYABLE_ID | NUMBER | (15) | Y | Oracle Payments' internal payment document Identifier |
| CALLING_APP_DOCUMENT_LINE_CODE | VARCHAR2 | (255) | Y | Source product''s document line Identifier. Since document line Identifiers may be alphanumeric, even numeric document Identifiers are stored as VARCHAR2. |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| PO_NUMBER | VARCHAR2 | (255) | Purhcase order numbers to which this document line is matched. If multiple purchase orders, value is comma delimited. | |
| LINE_NUMBER | NUMBER | (15) | Line number | |
| LINE_TYPE | VARCHAR2 | (30) | Line type | |
| LINE_NAME | VARCHAR2 | (100) | Line name | |
| LINE_AMOUNT | NUMBER | Line amount in document currency | ||
| DESCRIPTION | VARCHAR2 | (255) | Line description | |
| UNIT_PRICE | NUMBER | Unit price | ||
| QUANTITY | NUMBER | Quantity | ||
| UNIT_OF_MEASURE | VARCHAR2 | (100) | Unit of measure |
IBY.IBY_DOCUMENT_LINES does not reference any database object
IBY.IBY_DOCUMENT_LINES is referenced by following:
| Description: | IBY_DOCUMENT_LINES_H stores historical snapshots of document line items. This table contains denormalized versions of document lines from specific points in time, including when the payment for the associated document was submitted to a pay |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_DOCUMENT_LINES_H.DOCUMENT_PAYABLE_ID | IBY_DOCS_PAYABLE_ALL |
| IBY_DOCUMENT_LINES_H.DOCUMENT_PAYABLE_HISTORY_ID | IBY_DOCUMENTS_PAYABLE_H |
IBY_DOCUMENT_LINES_H stores historical snapshots of document line items. This table contains denormalized versions of document lines from specific points in time, including when the payment for the associated document was submitted to a payment system. Different snapshots of the same document line can exist in this table. These snapshots are differentiated by the table's primary key and a snapshot date.
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| DOCUMENT_LINE_HISTORY_ID | NUMBER | (15) | Y | System generated primary key |
| DOCUMENT_LINE_HISTORY_DATE | DATE | Y | Document line snapshot date | |
| DOCUMENT_PAYABLE_HISTORY_ID | NUMBER | (15) | Y | Document payable snapshot with which this line is associated |
| DOCUMENT_PAYABLE_LINE_ID | NUMBER | (15) | Y | Oracle Payments' internal payment document line Identifier |
| DOCUMENT_PAYABLE_ID | NUMBER | (15) | Y | Oracle Payments' internal payment document Identifier |
| CALLING_APP_DOCUMENT_LINE_CODE | VARCHAR2 | (255) | Y | Source product''s document line Identifier. Since document line Identifiers may be alphanumeric, even numeric document Identifiers are stored as VARCHAR2. |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| PO_NUMBER | VARCHAR2 | (255) | Purchase order numbers to which this document line is matched. If multiple purchase orders, value is comma delimited. | |
| LINE_NUMBER | NUMBER | (15) | Line number | |
| LINE_TYPE | VARCHAR2 | (30) | Line type | |
| LINE_NAME | VARCHAR2 | (100) | Line name | |
| LINE_AMOUNT | NUMBER | Line amount, in document currency | ||
| DESCRIPTION | VARCHAR2 | (255) | Line description | |
| UNIT_PRICE | NUMBER | Unit price | ||
| QUANTITY | NUMBER | Quantity | ||
| UNIT_OF_MEASURE | VARCHAR2 | (100) | Unit of measure |
IBY.IBY_DOCUMENT_LINES_H does not reference any database object
IBY.IBY_DOCUMENT_LINES_H is referenced by following:
| Description: | IBY_ECAPP stores information about Electronic Commerce Applications registered with iPayment. Oracle Applications which integrate with iPayment directly - via iPayment Java and PL/SQL API's are treated as EC applications by iPayment. They w |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_PAYEE.ECAPPID | IBY_ECAPP |
IBY_ECAPP stores information about Electronic Commerce Applications registered with iPayment.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_ECAPP_APPSHORTNAME_U2 | UNIQUE | APPS_TS_TX_IDX |
APPLICATION_SHORT_NAME
ZD_EDITION_NAME |
| IBY_ECAPP_ECAPPID_U1 | UNIQUE | APPS_TS_TX_IDX |
ECAPPID
ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ECAPPID | NUMBER | (15) | Y | Electronic Commerce Application identifier |
| NAME | VARCHAR2 | (80) | Y | Electronic Commerce Application name |
| APPLICATION_SHORT_NAME | VARCHAR2 | (50) | Y | Application Short Name |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column - date when a user last updated this row. | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | This column is used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard who column - user who last updated this row (foreign key to FND_USER.USER_ID). |
| CREATION_DATE | DATE | Y | Standard who column - date when this row was created. | |
| CREATED_BY | NUMBER | (15) | Y | Standard who column - user who created this row (foreign key to FND_USER.USER_ID). |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard who column - operating system login of user who last updated this row (foreign key to FND_LOGINS.LOGIN_ID). | |
| SECURITY_GROUP_ID | NUMBER | Used in hosted environments | ||
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_ECAPP does not reference any database object
IBY.IBY_ECAPP is referenced by following:
| Description: | "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. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_EXTERNAL_PAYEES_ALL.BANK_INSTRUCTION1_CODE | IBY_BANK_INSTRUCTIONS_B |
| IBY_EXTERNAL_PAYEES_ALL.DEFAULT_PAYMENT_METHOD_CODE | IBY_PAYMENT_METHODS_B |
| IBY_EXTERNAL_PAYEES_ALL.BANK_INSTRUCTION2_CODE | IBY_BANK_INSTRUCTIONS_B |
| IBY_EXTERNAL_PAYEES_ALL.PAYMENT_REASON_CODE | IBY_PAYMENT_REASONS_B |
| IBY_EXTERNAL_PAYEES_ALL.DELIVERY_CHANNEL_CODE | IBY_DELIVERY_CHANNELS_B |
| IBY_EXTERNAL_PAYEES_ALL.PAYMENT_FORMAT_CODE | IBY_FORMATS_B |
| Foreign Key Column | Foreign Table |
|---|---|
| FV_TPP_ASSIGNMENTS_ALL.EXT_PAYEE_ID | IBY_EXTERNAL_PAYEES_ALL |
| IBY_DOCS_PAYABLE_ALL.EXT_PAYEE_ID | IBY_EXTERNAL_PAYEES_ALL |
| IBY_EXT_PARTY_PMT_MTHDS.EXT_PMT_PARTY_ID | IBY_EXTERNAL_PAYEES_ALL |
| IBY_PAYMENTS_ALL.EXT_PAYEE_ID | IBY_EXTERNAL_PAYEES_ALL |
IBY_EXTERNAL_PAYEES_ALL stores payment-related attributes for the funds disbursement payment process for external party payees. This table corresponds to the supplier attributes.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_EXTERNAL_PAYEES_ALL_U1 | UNIQUE | APPS_TS_TX_IDX | EXT_PAYEE_ID |
| IBY_EXTERNAL_PAYEES_ALL_N1 | NONUNIQUE | APPS_TS_TX_IDX | BANK_INSTRUCTION1_CODE |
| IBY_EXTERNAL_PAYEES_ALL_N2 | NONUNIQUE | APPS_TS_TX_IDX | DEFAULT_PAYMENT_METHOD_CODE |
| IBY_EXTERNAL_PAYEES_ALL_N3 | NONUNIQUE | APPS_TS_TX_IDX | BANK_INSTRUCTION2_CODE |
| IBY_EXTERNAL_PAYEES_ALL_N4 | NONUNIQUE | APPS_TS_TX_IDX | PAYMENT_REASON_CODE |
| IBY_EXTERNAL_PAYEES_ALL_N5 | NONUNIQUE | APPS_TS_TX_IDX | DELIVERY_CHANNEL_CODE |
| IBY_EXTERNAL_PAYEES_ALL_N6 | NONUNIQUE | APPS_TS_TX_IDX | PAYMENT_FORMAT_CODE |
| IBY_EXTERNAL_PAYEES_ALL_N7 | NONUNIQUE | APPS_TS_TX_IDX | SUPPLIER_SITE_ID |
| IBY_EXTERNAL_PAYEES_ALL_N8 | NONUNIQUE | APPS_TS_TX_IDX |
PAYEE_PARTY_ID
PAYMENT_FUNCTION PARTY_SITE_ID SUPPLIER_SITE_ID ORG_ID ORG_TYPE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| EXT_PAYEE_ID | NUMBER | (15) | Y | System generated primary key |
| PAYEE_PARTY_ID | NUMBER | (15) | Y | TCA party Identifier |
| PAYMENT_FUNCTION | VARCHAR2 | (30) | Y | Function or purpose of the payment. Values from the lookup IBY_PAYMENT_FUNCTIONS include SUPPLIER_PAYMENT, CUSTOMER_REFUNDS, and others. |
| EXCLUSIVE_PAYMENT_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether each document payable for this payee corresponds to one payment |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number | |
| PARTY_SITE_ID | NUMBER | (15) | Party site Identifier | |
| SUPPLIER_SITE_ID | NUMBER | (15) | Supplier site Identifier | |
| ORG_ID | NUMBER | (15) | Organization Identifier | |
| ORG_TYPE | VARCHAR2 | (30) | Organization type. Values from the lookup IBY_ORGANIZATION_TYPES include Operating Unit, Business Group, and Legal Entity. | |
| DEFAULT_PAYMENT_METHOD_CODE | VARCHAR2 | (30) | Default payment method Identifier | |
| ECE_TP_LOCATION_CODE | VARCHAR2 | (60) | Trading partner location code for e-Commerce Gateway | |
| BANK_CHARGE_BEARER | VARCHAR2 | (30) | Bearer of bank charge cost. Bank charge bearers are defined as the lookup IBY_BANK_CHARGE_BEARER. | |
| BANK_INSTRUCTION1_CODE | VARCHAR2 | (30) | Code of first bank instruction | |
| BANK_INSTRUCTION2_CODE | VARCHAR2 | (30) | Code of second bank instruction | |
| BANK_INSTRUCTION_DETAILS | VARCHAR2 | (255) | Additional bank instruction details | |
| PAYMENT_REASON_CODE | VARCHAR2 | (30) | Payment reason code | |
| PAYMENT_REASON_COMMENTS | VARCHAR2 | (240) | Free text field available for entering a reason for the payment | |
| INACTIVE_DATE | DATE | Inactive date | ||
| PAYMENT_TEXT_MESSAGE1 | VARCHAR2 | (256) | Text message for use in payment processing | |
| PAYMENT_TEXT_MESSAGE2 | VARCHAR2 | (150) | Text message for use in payment processing | |
| PAYMENT_TEXT_MESSAGE3 | VARCHAR2 | (150) | Text message for use in payment processing | |
| DELIVERY_CHANNEL_CODE | VARCHAR2 | (30) | Default delivery channel code | |
| PAYMENT_FORMAT_CODE | VARCHAR2 | (30) | Default payment format code | |
| SETTLEMENT_PRIORITY | VARCHAR2 | (30) | Priority with which the financial institution or payment system settles payments for this payee. The available values for this column come from the FND lookup IBY_SETTLEMENT_PRIORITY. | |
| REMIT_ADVICE_DELIVERY_METHOD | VARCHAR2 | (30) | Default delivery method set on the payee level. If the Override with Payee Delivery Method Preference flag on the Payment Process Profile is turned off, the setting here is ignored. Values from the lookup IBY_DELIVERY_METHODS include EMAIL, FAX, and PRINTED. | |
| REMIT_ADVICE_EMAIL | VARCHAR2 | (255) | E-mail address at which the payee wishes to receive remittance advice | |
| REMIT_ADVICE_FAX | VARCHAR2 | (100) | Fax number at which the payee wishes to receive remittance advice |
IBY.IBY_EXTERNAL_PAYEES_ALL does not reference any database object
IBY.IBY_EXTERNAL_PAYEES_ALL is referenced by following:
| Description: | "This table contains payment details of an external payer automatically created by the source product. For example when customer or customer site is created manually, system automatically insert row in to the IBY_EXTERNAL_PAYERS_ALL table. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_EXTERNAL_PAYERS_ALL.PARTY_ID | HZ_PARTIES |
| IBY_EXTERNAL_PAYERS_ALL.CUST_ACCOUNT_ID | HZ_CUST_ACCOUNTS |
| IBY_EXTERNAL_PAYERS_ALL.ACCT_SITE_USE_ID | HZ_CUST_SITE_USES_ALL |
Payment attributes of the customer
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_EXTERNAL_PAYERS_ALL_U1 | UNIQUE | APPS_TS_TX_IDX | EXT_PAYER_ID |
| IBY_EXTERNAL_PAYERS_ALL_U2 | UNIQUE | APPS_TS_TX_IDX |
PARTY_ID
PAYMENT_FUNCTION ORG_ID ORG_TYPE CUST_ACCOUNT_ID ACCT_SITE_USE_ID |
| IBY_EXTERNAL_PAYERS_ALL_CA_N2 | NONUNIQUE | APPS_TS_TX_IDX | CUST_ACCOUNT_ID |
| IBY_EXTERNAL_PAYERS_ALL_SU_N3 | NONUNIQUE | APPS_TS_TX_IDX | ACCT_SITE_USE_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| EXT_PAYER_ID | NUMBER | (15) | Y | Sequence: IBY_EXTERNAL_PAYERS_ALL_S.nextval |
| PAYMENT_FUNCTION | VARCHAR2 | (30) | Y | CUSTOMER_PAYMENT |
| PARTY_ID | NUMBER | (15) | Y | TCA party ID |
| ORG_TYPE | VARCHAR2 | (30) | Organization type | |
| ORG_ID | NUMBER | (15) | Party organizational/sub-unit id | |
| CUST_ACCOUNT_ID | NUMBER | (15) | Customer account ID | |
| ACCT_SITE_USE_ID | NUMBER | (15) | Customer account site use ID | |
| BANK_CHARGE_BEARER_CODE | VARCHAR2 | (30) | Bank charge bearer | |
| DIRDEB_INSTRUCTION_CODE | VARCHAR2 | (30) | Direct debit instruction code | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who Column |
| CREATION_DATE | DATE | Y | Standard Who Column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who Column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who Column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who Column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object Version Number | |
| DEBIT_ADVICE_DELIVERY_METHOD | VARCHAR2 | (30) | Default delivery method set on the payer level for debit notification | |
| DEBIT_ADVICE_EMAIL | VARCHAR2 | (255) | Debit notification email address | |
| DEBIT_ADVICE_FAX | VARCHAR2 | (100) | Debit notification fax number |
IBY.IBY_EXTERNAL_PAYERS_ALL does not reference any database object
IBY.IBY_EXTERNAL_PAYERS_ALL is referenced by following:
| Description: | Defines data extracts for payment file creation |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_EXTRACTS_TL.EXTRACT_ID | IBY_EXTRACTS_B |
| IBY_FORMATS_B.EXTRACT_ID | IBY_EXTRACTS_B |
IBY_EXTRACTS stores every extract definition supported by the extract generation engine.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_EXTRACTS_B_EXTRACTID_U1 | UNIQUE | APPS_TS_TX_IDX |
EXTRACT_ID
ZD_EDITION_NAME |
| IBY_EXTRACTS_B_EXTRACTCODE_N1 | NONUNIQUE | APPS_TS_TX_IDX | EXTRACT_CODE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| EXTRACT_ID | NUMBER | (15) | Y | Primary key |
| EXTRACT_CODE | VARCHAR2 | (30) | Y | Extract code |
| EXTRACT_VERSION | NUMBER | (15) | Y | Version number of the extract; multiple extracts of the same type and name but differing version may exist within they system |
| GEN_CODE_LANGUAGE | VARCHAR2 | (30) | Y | Language in which the extract generation codepoint is implemented; possible values include: JAVA , PLSQL |
| GEN_CODE_PACKAGE | VARCHAR2 | (255) | Y | Package where the generator is defined; in PL/SQL this corresponds to a package name, in Java a class name |
| GEN_CODE_ENTRY_POINT | VARCHAR2 | (255) | Y | Entry point for the generator; typically a function or method name |
| DATASOURCE_CODE | VARCHAR2 | (80) | Y | Data source this extract is associated with |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_EXTRACTS_B does not reference any database object
IBY.IBY_EXTRACTS_B is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_EXTRACTS_TL.EXTRACT_ID | IBY_EXTRACTS_B |
IBY_EXTRACTS stores every extract definition supported by the extract generation engine.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_EXTRACTS_TL_U1 | UNIQUE | APPS_TS_TX_IDX |
LANGUAGE
EXTRACT_ID ZD_EDITION_NAME |
| IBY_EXTRACTS_TL_EXTRACTID_N1 | NONUNIQUE | APPS_TS_TX_IDX | EXTRACT_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| EXTRACT_ID | NUMBER | (15) | Y | Primary key |
| LANGUAGE | VARCHAR2 | (4) | Y | Language code |
| SOURCE_LANG | VARCHAR2 | (4) | Y | Language code of the record's current language |
| EXTRACT_DESC | VARCHAR2 | (200) | Readable description of the extract and its purposes. | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_EXTRACTS_TL does not reference any database object
IBY.IBY_EXTRACTS_TL is referenced by following:
| Description: | IBY_EXTRACT_ACTIVATIONS defines which computed fields within an extract are unnecessary for a particular format, with each row corresponding to a single field for that extract. When the extract engine is called for a particular format, ever |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_EXTRACT_ACTIVATIONS.FORMAT_CODE | IBY_FORMATS_B |
IBY_EXTRACT_ACTIVATIONS defines which computed fields within an extract are unnecessary for a particular format, with each row corresponding to a single field for that extract. When the extract engine is called for a particular format, every function generating a computed field checks this table to determine whether to skip computation and immediately return a trivial value.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_EXTRACT_ACTIVATIONS_U1 | UNIQUE | APPS_TS_TX_IDX | ACTIVATION_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ACTIVATION_ID | NUMBER | (15) | Y | System generated primary key |
| FORMAT_CODE | VARCHAR2 | (30) | Y | Indicates which format is associated with the extract |
| FIELD_NAME | VARCHAR2 | (100) | Y | Name of the field |
| ACTIVE_FLAG | VARCHAR2 | (1) | Y | Y or N to indicate whether the field is active within the format |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number |
IBY.IBY_EXTRACT_ACTIVATIONS does not reference any database object
IBY.IBY_EXTRACT_ACTIVATIONS is referenced by following:
| Description: | "This table contains records of the external bank accounts entered manually. This table corresponds to the Banking details page of supplier or customer. This table contains bank, branch, masking, encryption details of the external bank acc |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_EXT_BANK_ACCOUNTS.BA_NUM_SEC_SEGMENT_ID | IBY_SECURITY_SEGMENTS |
| IBY_EXT_BANK_ACCOUNTS.IBAN_SEC_SEGMENT_ID | IBY_SECURITY_SEGMENTS |
| IBY_EXT_BANK_ACCOUNTS.BA_NUM_ELEC_SEC_SEGMENT_ID | IBY_SECURITY_SEGMENTS |
| Foreign Key Column | Foreign Table |
|---|---|
| AR_CASH_RECEIPTS_ALL.CUSTOMER_BANK_ACCOUNT_ID | IBY_EXT_BANK_ACCOUNTS |
| AR_INTERIM_CASH_RECEIPTS_ALL.CUSTOMER_BANK_ACCOUNT_ID | IBY_EXT_BANK_ACCOUNTS |
| AR_PAYMENTS_INTERFACE_ALL.CUSTOMER_BANK_ACCOUNT_ID | IBY_EXT_BANK_ACCOUNTS |
| IBY_ACCOUNT_OWNERS.EXT_BANK_ACCOUNT_ID | IBY_EXT_BANK_ACCOUNTS |
| IBY_INTERMEDIARY_ACCTS.BANK_ACCT_ID | IBY_EXT_BANK_ACCOUNTS |
| POS_ACNT_ADDR_SUMM_REQ.EXT_BANK_ACCOUNT_ID | IBY_EXT_BANK_ACCOUNTS |
IBY_EXT_BANK_ACCOUNTS defines the external bank account entity. This table should not be translated for any columns.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_EXT_BANK_ACCOUNTS_U1 | UNIQUE | APPS_TS_TX_IDX | EXT_BANK_ACCOUNT_ID |
| IBY_EXT_BANK_ACCOUNTS_N1 | NONUNIQUE | APPS_TS_TX_IDX | BANK_ID |
| IBY_EXT_BANK_ACCOUNTS_N2 | NONUNIQUE | APPS_TS_TX_IDX | BRANCH_ID |
| IBY_EXT_BANK_ACCOUNTS_N3 | NONUNIQUE | APPS_TS_TX_IDX |
BANK_ACCOUNT_NUM_HASH1
BANK_ACCOUNT_NUM_HASH2 |
| IBY_EXT_BANK_ACCOUNTS_N4 | NONUNIQUE | APPS_TS_TX_IDX |
IBAN_HASH1
IBAN_HASH2 |
| IBY_EXT_BANK_ACCOUNTS_N5 | NONUNIQUE | APPS_TS_TX_IDX |
BA_MASK_SETTING
BA_UNMASK_LENGTH |
| IBY_EXT_BANK_ACCOUNTS_N6 | NONUNIQUE | APPS_TS_TX_IDX |
BANK_ACCOUNT_NUM
BRANCH_ID BANK_ID |
| IBY_EXT_BANK_ACCOUNTS_N7 | NONUNIQUE | APPS_TS_TX_IDX | BANK_ACCOUNT_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| EXT_BANK_ACCOUNT_ID | NUMBER | (15) | Y | Primary key of this table |
| COUNTRY_CODE | VARCHAR2 | (2) | Country code of the bank account | |
| BRANCH_ID | NUMBER | (15) | Identifier of the bank branch that this bank account belongs to | |
| BANK_ID | NUMBER | (15) | Identifier of the bank that the bank branch belong to | |
| BANK_ACCOUNT_NUM | VARCHAR2 | (100) | Account number | |
| BANK_ACCOUNT_NUM_HASH1 | VARCHAR2 | (64) | Hash of the bank account number | |
| BANK_ACCOUNT_NUM_HASH2 | VARCHAR2 | (64) | Hash of the salted bank account number | |
| MASKED_BANK_ACCOUNT_NUM | VARCHAR2 | (100) | Masked bank account number; to be used for display purposes | |
| BA_MASK_SETTING | VARCHAR2 | (30) | Current bank account masking setting; values taken from lookup IBY_PMT_INSTR_MASKING | |
| BA_UNMASK_LENGTH | NUMBER | (2) | Number of digits to expose in the external bank account mask | |
| CURRENCY_CODE | VARCHAR2 | (15) | Currency code | |
| IBAN | VARCHAR2 | (50) | International Bank Account Number | |
| IBAN_HASH1 | VARCHAR2 | (64) | IBAN hash value | |
| IBAN_HASH2 | VARCHAR2 | (64) | IBAN salted hash value | |
| MASKED_IBAN | VARCHAR2 | (50) | Masked IBAN value; to be used for display purposes | |
| CHECK_DIGITS | VARCHAR2 | (30) | Check digits | |
| BANK_ACCOUNT_TYPE | VARCHAR2 | (25) | Bank account type (e.g. SAVINGS, CHECKING) | |
| ACCOUNT_CLASSIFICATION | VARCHAR2 | (30) | Account classification | |
| ACCOUNT_SUFFIX | VARCHAR2 | (30) | Account suffix | |
| AGENCY_LOCATION_CODE | VARCHAR2 | (30) | Agency location code | |
| PAYMENT_FACTOR_FLAG | VARCHAR2 | (1) | Indicates whether this is a payment factor bank account | |
| FOREIGN_PAYMENT_USE_FLAG | VARCHAR2 | (1) | Y or N flag indicating that this bank account can be used for foreign payments | |
| EXCHANGE_RATE_AGREEMENT_NUM | VARCHAR2 | (80) | Exchange rate agreement number | |
| EXCHANGE_RATE_AGREEMENT_TYPE | VARCHAR2 | (80) | Exchange rate agreement type | |
| EXCHANGE_RATE | NUMBER | Exchange rate | ||
| HEDGING_CONTRACT_REFERENCE | VARCHAR2 | (20) | Hedging contract reference | |
| SECONDARY_ACCOUNT_REFERENCE | VARCHAR2 | (30) | Account number reference such as Building Society Roll Number | |
| BA_NUM_SEC_SEGMENT_ID | NUMBER | (15) | Bank account number security identifier | |
| ENCRYPTED | VARCHAR2 | (1) | Y | Whether the instrument is encrypted |
| IBAN_SEC_SEGMENT_ID | NUMBER | (15) | IBAN security identifier | |
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | Descriptive Flexfield structure defining column | |
| ATTRIBUTE1 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE2 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE3 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE4 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE5 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE6 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE7 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE8 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE9 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE10 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE11 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE12 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE13 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE14 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE15 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| REQUEST_ID | NUMBER | (15) | Current who column | |
| PROGRAM_APPLICATION_ID | NUMBER | (15) | Current who column | |
| PROGRAM_ID | NUMBER | (15) | Current who column | |
| PROGRAM_UPDATE_DATE | DATE | Current who column | ||
| START_DATE | DATE | Start date | ||
| END_DATE | DATE | End date | ||
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. | |
| BANK_ACCOUNT_NAME | VARCHAR2 | (80) | Bank account name | |
| BANK_ACCOUNT_NAME_ALT | VARCHAR2 | (320) | Alternate account name | |
| SHORT_ACCT_NAME | VARCHAR2 | (30) | Short account name | |
| DESCRIPTION | VARCHAR2 | (240) | Description | |
| BANK_ACCOUNT_NUM_ELECTRONIC | VARCHAR2 | (100) | The bank account number used in electronic files, if different from the written form | |
| BA_NUM_ELEC_SEC_SEGMENT_ID | NUMBER | (15) | Electronically-formatted bank number security segment identifier | |
| SALT_VERSION | NUMBER | (2) | Salt Version used for Encryption | |
| CONTACT_NAME | VARCHAR2 | (60) | Point of Contact Name for Bank Account | |
| CONTACT_PHONE | VARCHAR2 | (30) | Point of Contact Phone for Bank Account | |
| CONTACT_FAX | VARCHAR2 | (30) | Point of Contact Fax for Bank Account | |
| CONTACT_EMAIL | VARCHAR2 | (80) | Point of Contact E-Mail for Bank Account |
IBY.IBY_EXT_BANK_ACCOUNTS does not reference any database object
IBY.IBY_EXT_BANK_ACCOUNTS is referenced by following:
| Description: | IBY_EXT_PARTY_PMT_MTHDS stores payment method applicability driven by the preferences of the external party. A payment method is applicable to a party and payment function combination and, optionally and additionally, to a party site and/or |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_EXT_PARTY_PMT_MTHDS.EXT_PMT_PARTY_ID | IBY_EXTERNAL_PAYEES_ALL |
| IBY_EXT_PARTY_PMT_MTHDS.PAYMENT_METHOD_CODE | IBY_PAYMENT_METHODS_B |
IBY_EXT_PARTY_PMT_MTHDS stores payment method applicability driven by the preferences of the external party. A payment method is applicable to a party and payment function combination and, optionally and additionally, to a party site and/or organization. This table is shared by funds capture and fund disbursement flows.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_EXT_PARTY_PMT_MTHDS_U1 | UNIQUE | APPS_TS_TX_IDX | EXT_PARTY_PMT_MTHD_ID |
| IBY_EXT_PARTY_PMT_MTHDS_N1 | NONUNIQUE | APPS_TS_TX_IDX | EXT_PMT_PARTY_ID |
| IBY_EXT_PARTY_PMT_MTHDS_N2 | NONUNIQUE | APPS_TS_TX_IDX | PAYMENT_METHOD_CODE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| EXT_PARTY_PMT_MTHD_ID | NUMBER | (15) | Y | System generated primary key |
| PAYMENT_METHOD_CODE | VARCHAR2 | (30) | Y | Payment method Identifier |
| PAYMENT_FLOW | VARCHAR2 | (30) | Y | Determines the source table for the PAYMENT_METHOD_CODE foreign key. Values from the lookup IBY_PAYMENT_FLOW are DISBURSEMENTS and FUND_CAPTURE. |
| EXT_PMT_PARTY_ID | NUMBER | (15) | Y | External party Identifier, either a payee or payer, depending on the payment flow |
| PAYMENT_FUNCTION | VARCHAR2 | (30) | Y | Function or purpose of the payment. Values from the lookup IBY_PAYMENT_FUNCTIONS include SUPPLIER_PAYMENT, CUSTOMER_REFUNDS, and others. |
| PRIMARY_FLAG | VARCHAR2 | (1) | Y | Indicates if payment method is primary. Y for Yes, N otherwise. |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number | |
| INACTIVE_DATE | DATE | Inactive date |
IBY.IBY_EXT_PARTY_PMT_MTHDS does not reference any database object
IBY.IBY_EXT_PARTY_PMT_MTHDS is referenced by following:
| Description: | "This table stores information about third party payment related relationships and related attributes. IBY_EXT_PAYEE_RELATIONSHIPS contain third payment relationships entered manually using the Relationship region in the supplier page. Eac |
|---|
This table stores information about third party payment related relationships and related attributes. IBY_EXT_PAYEE_RELATIONSHIPS contain third payment relationships entered manually using the Relationship region in the supplier page. Each row stores the relationship details like relationship status, is it a primary relationship, relationship effective dates and additional information for the relationship. This information will be utilized in payables and Payments application to create invoices and process payments.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_EXT_PAYEE_RELATIONSHIPS_N1 | NONUNIQUE | APPS_TS_TX_IDX | PARTY_ID |
| IBY_EXT_PAYEE_RELATIONSHIPS_N2 | NONUNIQUE | APPS_TS_TX_IDX |
PARTY_ID
SUPPLIER_SITE_ID |
| IBY_EXT_PAYEE_RELATIONSHIPS_N3 | NONUNIQUE | APPS_TS_TX_IDX |
PARTY_ID
SUPPLIER_SITE_ID REMIT_PARTY_ID REMIT_SUPPLIER_SITE_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| RELATIONSHIP_ID | NUMBER | (15) | Y | Unique internal Identifier for this record. Generated using a database sequence. |
| PARTY_ID | NUMBER | (15) | Party identifier for whom the third party payment relationship is created. | |
| SUPPLIER_SITE_ID | NUMBER | (15) | Supplier site identifier for whom the third party payment relationship is created. | |
| REMIT_PARTY_ID | NUMBER | (15) | The remit to party identifier on whom the payments will be made. | |
| REMIT_SUPPLIER_SITE_ID | NUMBER | (15) | The remit to supplier site identifier on whom the payments will be made. | |
| FROM_DATE | DATE | The date from which the relationship to make the third party payments is valid for processing. | ||
| TO_DATE | DATE | The date up to which the relationship to make the third party payments is valid for processing. | ||
| PRIMARY_FLAG | VARCHAR2 | (1) | Indicates whether this is the primary relationship for a date range. | |
| ADDITIONAL_INFORMATION | VARCHAR2 | (1000) | Additional information for the third party payment relationship. | |
| ACTIVE | VARCHAR2 | (1) | Indicates whether the relationship is active or not. | |
| CREATED_BY | NUMBER | (15) | Standard who column - unique internal identifier of user who created this row. Foreign key to the USER_ID column of the FND_USER table. | |
| CREATION_DATE | DATE | Standard who column - date when this row was created. | ||
| LAST_UPDATED_BY | NUMBER | (15) | Standard who column - unique internal identifier user who last updated this row. Foreign key to the USER_ID column of the FND_USER table. | |
| LAST_UPDATE_DATE | DATE | Standard who column - operating system login of user who last updated this row. Foreign key to the LOGIN_ID column of the FND_LOGINS table. | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column - date when a user last updated this row. | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. This number is incremented for every update to the row through the application. | |
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | Descriptive flexfield structure definition column. | |
| ATTRIBUTE1 | VARCHAR2 | (240) | Descriptive Flexfield segment | |
| ATTRIBUTE2 | VARCHAR2 | (240) | Descriptive Flexfield segment | |
| ATTRIBUTE3 | VARCHAR2 | (240) | Descriptive Flexfield segment | |
| ATTRIBUTE4 | VARCHAR2 | (240) | Descriptive Flexfield segment | |
| ATTRIBUTE5 | VARCHAR2 | (240) | Descriptive Flexfield segment | |
| ATTRIBUTE6 | VARCHAR2 | (240) | Descriptive Flexfield segment | |
| ATTRIBUTE7 | VARCHAR2 | (240) | Descriptive Flexfield segment | |
| ATTRIBUTE8 | VARCHAR2 | (240) | Descriptive Flexfield segment | |
| ATTRIBUTE9 | VARCHAR2 | (240) | Descriptive Flexfield segment | |
| ATTRIBUTE10 | VARCHAR2 | (240) | Descriptive Flexfield segment | |
| ATTRIBUTE11 | VARCHAR2 | (240) | Descriptive Flexfield segment | |
| ATTRIBUTE12 | VARCHAR2 | (240) | Descriptive Flexfield segment | |
| ATTRIBUTE13 | VARCHAR2 | (240) | Descriptive Flexfield segment | |
| ATTRIBUTE14 | VARCHAR2 | (240) | Descriptive Flexfield segment | |
| ATTRIBUTE15 | VARCHAR2 | (240) | Descriptive Flexfield segment |
IBY.IBY_EXT_PAYEE_RELATIONSHIPS does not reference any database object
IBY.IBY_EXT_PAYEE_RELATIONSHIPS is referenced by following:
| Description: | IBY_FNDCPT_PAYEE_APPL is a mapping table between internal payees and operating units. One payee may be associated with many operating units. An operating unit may be associated with at most one payee. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_FNDCPT_PAYEE_APPL.MPAYEEID | IBY_PAYEE |
IBY_FNDCPT_PAYEE_APPL is a mapping table between internal payees and operating units. One payee may be associated with many operating units. An operating unit may be associated with at most one payee.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_FNDCPT_PAYEE_APPL_U1 | UNIQUE | APPS_TS_TX_IDX |
ORG_TYPE
ORG_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| MPAYEEID | NUMBER | (15) | Y | Payee primary key |
| ORG_TYPE | VARCHAR2 | (30) | Y | Organization type from lookup type IBY_ORGANIZATION_TYPES |
| ORG_ID | NUMBER | (15) | Y | Organization Identifier |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Used for locking purposes that subsequently allows for checking if there is old data on the screen compared to what is in the database. The situation occurs when the HTML application is a stateless application. |
IBY.IBY_FNDCPT_PAYEE_APPL does not reference any database object
IBY.IBY_FNDCPT_PAYEE_APPL is referenced by following:
| Description: | IBY_FNDCPT_PMT_CHNNLS defines all payment methods for the funds capture flow. Payment methods are categorized by instrument types. The instrument types are BANKACCOUNT, CREDITCARD, and DEBITCARD. Each payment method includes the attribute- |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| AR_RECEIPT_METHODS.PAYMENT_CHANNEL_CODE | IBY_FNDCPT_PMT_CHNNLS_B |
| IBY_FNDCPT_TX_EXTENSIONS.PAYMENT_CHANNEL_CODE | IBY_FNDCPT_PMT_CHNNLS_B |
IBY_FNDCPT_PMT_CHNNLS defines all payment methods for the funds capture flow. Payment methods are categorized by instrument types. The instrument types are BANKACCOUNT, CREDITCARD, and DEBITCARD. Each payment method includes the attribute-level applicability settings of the payment attributes on documents receivable.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_FNDCPT_PMT_CHNNLS_B_U1 | UNIQUE | APPS_TS_TX_IDX |
PAYMENT_CHANNEL_CODE
ZD_EDITION_NAME |
| IBY_FNDCPT_PMT_CHNNLS_B_IT_N1 | NONUNIQUE | APPS_TS_TX_IDX | INSTRUMENT_TYPE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYMENT_CHANNEL_CODE | VARCHAR2 | (30) | Y | User entered primary key |
| INSTRUMENT_TYPE | VARCHAR2 | (30) | Instrument type. Values, from the IBY_INSTRUMENT_TYPES lookup, include BANKACCOUNT, CREDITCARD, and DEBITCARD | |
| INACTIVE_DATE | DATE | Inactive date | ||
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | Descriptive flexfield category code | |
| ATTRIBUTE1 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE2 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE3 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE4 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE5 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE6 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE7 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE8 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE9 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE10 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE11 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE12 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE13 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE14 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE15 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. | |
| SEEDED_FLAG | VARCHAR2 | (1) | Y or N flag indicating that the data is seeded record | |
| FORMAT_VALUE | VARCHAR2 | (80) | Value used in the formatted settlement batch | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_FNDCPT_PMT_CHNNLS_B does not reference any database object
IBY.IBY_FNDCPT_PMT_CHNNLS_B is referenced by following:
| Description: | IBY_FNDCPT_PMT_CHNNLS defines all payment methods for the funds capture flow. Payment methods are categorized by instrument types. The instrument types are BANKACCOUNT, CREDITCARD, and DEBITCARD. Each payment method includes the attribute- |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_FNDCPT_PMT_CHNNLS_TL.PAYMENT_CHANNEL_CODE | % |
IBY_FNDCPT_PMT_CHNNLS defines all payment methods for the funds capture flow. Payment methods are categorized by instrument types. The instrument types are BANKACCOUNT, CREDITCARD, and DEBITCARD. Each payment method includes the attribute-level applicability settings of the payment attributes on documents receivable.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_FNDCPT_PMT_CHNNLS_TL_U1 | UNIQUE | APPS_TS_TX_IDX |
LANGUAGE
PAYMENT_CHANNEL_CODE ZD_EDITION_NAME |
| IBY_FNDCPT_PMT_CHNNLS_TL_N1 | NONUNIQUE | APPS_TS_TX_IDX | PAYMENT_CHANNEL_CODE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYMENT_CHANNEL_CODE | VARCHAR2 | (30) | Y | User entered primary key |
| PAYMENT_CHANNEL_NAME | VARCHAR2 | (100) | Y | Payment method name |
| DESCRIPTION | VARCHAR2 | (255) | Payment method description | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. | |
| LANGUAGE | VARCHAR2 | (4) | Y | Language code |
| SOURCE_LANG | VARCHAR2 | (4) | Y | Language code of the record's current language |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_FNDCPT_PMT_CHNNLS_TL does not reference any database object
IBY.IBY_FNDCPT_PMT_CHNNLS_TL is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_FNDCPT_SYS_CC_PF_B.SETTLEMENT_FORMAT_CODE | IBY_FORMATS_B |
| IBY_FNDCPT_SYS_CC_PF_B.SETTLEMENT_TRANS_PRTCL_CODE | IBY_TRANSMIT_PROTOCOLS_B |
| IBY_FNDCPT_SYS_CC_PF_B.SETTLEMENT_ACK_RDR_CODE | IBY_ACK_READERS |
| IBY_FNDCPT_SYS_CC_PF_B.QUERY_FORMAT_CODE | IBY_FORMATS_B |
| IBY_FNDCPT_SYS_CC_PF_B.QUERY_TRANS_PRTCL_CODE | IBY_TRANSMIT_PROTOCOLS_B |
| IBY_FNDCPT_SYS_CC_PF_B.QUERY_ACK_RDR_CODE | IBY_ACK_READERS |
| IBY_FNDCPT_SYS_CC_PF_B.PAYER_NOTIFICATION_FORMAT | IBY_FORMATS_B |
IBY_FNDCPT_SYS_CC_PF stores payment system-defined attributes of the credit card funds capture process.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_FNDCPT_SYS_CC_PF_SPC_U1 | UNIQUE | APPS_TS_TX_IDX |
SYS_CC_PROFILE_CODE
ZD_EDITION_NAME |
| IBY_FNDCPT_SYS_CC_PF_B_N1 | NONUNIQUE | APPS_TS_TX_IDX | PAYER_NOTIFICATION_FORMAT |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| SYS_CC_PROFILE_CODE | VARCHAR2 | (30) | Y | System process profile identifier |
| PAYMENT_SYSTEM_ID | NUMBER | (15) | Y | Payment system identifier |
| ONLINE_AUTH_FORMAT_CODE | VARCHAR2 | (30) | Y | Payment format identifier for online authorization messages. |
| ONLINE_AUTH_TRANS_PRTCL_CODE | VARCHAR2 | (30) | Transmission protocol for online authorization messages | |
| ONLINE_AUTH_ACK_RDR_CODE | VARCHAR2 | (30) | Y | Acknowledgment reader for online authorization responses |
| SETTLEMENT_FORMAT_CODE | VARCHAR2 | (30) | Y | Format for settlement transactions. |
| SETTLEMENT_TRANS_PRTCL_CODE | VARCHAR2 | (30) | Transmission protocol for settlement messages | |
| SETTLEMENT_ACK_RDR_CODE | VARCHAR2 | (30) | Acknowledgment reader for settlement responses | |
| QUERY_FORMAT_CODE | VARCHAR2 | (30) | Format for the query request | |
| QUERY_TRANS_PRTCL_CODE | VARCHAR2 | (30) | Transmission protocol for query requests | |
| QUERY_ACK_RDR_CODE | VARCHAR2 | (30) | Query acknowledgement/response reader | |
| GROUP_BY_ORG | VARCHAR2 | (1) | Y or N flag specifying whether settlements should be grouped into settlement batches by first party organization | |
| GROUP_BY_LEGAL_ENTITY | VARCHAR2 | (1) | Y or N flag specifying whether settlements should be grouped into settlement batches by first party legal entity | |
| GROUP_BY_INT_BANK_ACCOUNT | VARCHAR2 | (1) | Y or N flag specifying whether settlements should be grouped into settlement batches by internal bank account | |
| GROUP_BY_SETTLEMENT_CURR | VARCHAR2 | (1) | Y or N flag specifying whether settlements should be grouped into settlement batches by settlement currency | |
| GROUP_BY_SETTLEMENT_DATE | VARCHAR2 | (1) | Y or N flag specifying whether settlements should be grouped into settlement batches by settlement date | |
| LIMIT_BY_AMT_CURR | VARCHAR2 | (10) | Currency in which the maximum total amount per settlement batch is calculated. | |
| LIMIT_BY_EXCH_RATE_TYPE | VARCHAR2 | (255) | Exchange rate type used to compare the settlement batch total amount to the maximum total amount allowed. Types are defined in the General Ledger currency exchange rate type lookups table. These include CORPORATE, SPOT, and DAILY. | |
| LIMIT_BY_TOTAL_AMT | NUMBER | Maximum total amount for which a settlement batch can be created | ||
| INACTIVE_DATE | DATE | Inactivity date for the profile | ||
| LIMIT_BY_SETTLEMENT_NUM | NUMBER | Maximum number of settlements that can be included in a settlement batch | ||
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. |
| SETTLEMENT_COMPLETE_POINT | VARCHAR2 | (50) | A point when the settlement is considered complete. | |
| OVERRIDE_PAYER_DELIVERY_FLAG | VARCHAR2 | (1) | Y or N Flag indicating whether the payer notification delivery method should be overridden by the payer delivery method preference. | |
| PAYER_NOTIFICATION_FORMAT | VARCHAR2 | (30) | Payment format identifier for payer notification | |
| PAYER_NOTIFICATION_DEL_METHOD | VARCHAR2 | (100) | Remittance advice delivery method. Values, from the lookup IBY_DELIVERY_METHODS, include EMAIL, FAX, and PRINTED | |
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | Descriptive Flexfield structure defining column | |
| ATTRIBUTE1 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE2 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE3 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE4 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE5 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE6 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE7 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE8 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE9 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE10 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE11 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE12 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE13 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE14 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE15 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| AUTOMATIC_PN_SUBMIT_FLAG | VARCHAR2 | (1) | Y or No Flag indicating whether the payer notification is submitted automatically at settlement completion point | |
| PAYER_NOTIFICATION_CONDITION | VARCHAR2 | (30) | Condition for Payer notification to be sent is based on All the receipts or num of receipts | |
| PN_COND_NUM_OF_RECEIPTS | NUMBER | Number of reciptis, Payer Notification will be sent only if Number of receipts in the batch > this number. | ||
| EXCLUDE_TRXN_DET_EXTRACTION | VARCHAR2 | (1) | Indicates to Exclude the Invoice details | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_FNDCPT_SYS_CC_PF_B does not reference any database object
IBY.IBY_FNDCPT_SYS_CC_PF_B is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_FNDCPT_SYS_CC_PF_TL.SYS_CC_PROFILE_CODE | % |
IBY_FNDCPT_SYS_CC_PF stores payment system-defined attributes of the credit card funds capture process.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_FNDCPT_SYS_CC_PF_TL_U1 | UNIQUE | APPS_TS_TX_IDX |
LANGUAGE
SYS_CC_PROFILE_CODE ZD_EDITION_NAME |
| IBY_FNDCPT_SYS_CC_PF_SPC_N1 | NONUNIQUE | APPS_TS_TX_IDX | SYS_CC_PROFILE_CODE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| SYS_CC_PROFILE_CODE | VARCHAR2 | (30) | Y | System process profile identifier |
| LANGUAGE | VARCHAR2 | (4) | Y | Language code |
| SOURCE_LANG | VARCHAR2 | (4) | Y | Language code of the record's current language |
| SYS_CC_PROFILE_NAME | VARCHAR2 | (100) | Y | System process profile name |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. |
| DESCRIPTION | VARCHAR2 | (250) | Description | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_FNDCPT_SYS_CC_PF_TL does not reference any database object
IBY.IBY_FNDCPT_SYS_CC_PF_TL is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_FNDCPT_SYS_DC_PF_B.PAYMENT_SYSTEM_ID | IBY_BEPINFO |
| IBY_FNDCPT_SYS_DC_PF_B.QUERY_ACK_RDR_CODE | % |
| IBY_FNDCPT_SYS_DC_PF_B.PAYER_NOTIFICATION_FORMAT | IBY_FORMATS_B |
| IBY_FNDCPT_SYS_DC_PF_B.ONLINE_DEB_ACK_RDR_CODE | IBY_FORMATS_B |
| IBY_FNDCPT_SYS_DC_PF_B.ONLINE_DEB_TRANS_PRTCL_CODE | IBY_TRANSMIT_PROTOCOLS_B |
| IBY_FNDCPT_SYS_DC_PF_B.ONLINE_DEB_ACK_RDR_CODE | % |
| IBY_FNDCPT_SYS_DC_PF_B.SETTLEMENT_FORMAT_CODE | IBY_FORMATS_B |
| IBY_FNDCPT_SYS_DC_PF_B.SETTLEMENT_TRANS_PRTCL_CODE | IBY_TRANSMIT_PROTOCOLS_B |
| IBY_FNDCPT_SYS_DC_PF_B.SETTLEMENT_ACK_RDR_CODE | % |
| IBY_FNDCPT_SYS_DC_PF_B.QUERY_FORMAT_CODE | IBY_FORMATS_B |
| IBY_FNDCPT_SYS_DC_PF_B.QUERY_TRANS_PRTCL_CODE | IBY_TRANSMIT_PROTOCOLS_B |
IBY_FNDCPT_SYS_DC_PF stores payment system-defined attributes of the bank account electronic funds transfer process.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_FNDCPT_SYS_DC_PF_B_SPC_U1 | UNIQUE | APPS_TS_TX_IDX |
SYS_DC_PROFILE_CODE
ZD_EDITION_NAME |
| IBY_FNDCPT_SYS_DC_PF_B_N1 | NONUNIQUE | APPS_TS_TX_IDX | PAYER_NOTIFICATION_FORMAT |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| SYS_DC_PROFILE_CODE | VARCHAR2 | (30) | Y | System process profile identifier |
| PAYMENT_SYSTEM_ID | NUMBER | (15) | Y | Payment system identifier |
| ONLINE_DEB_FORMAT_CODE | VARCHAR2 | (30) | Y | Payment format identifier for online debits |
| ONLINE_DEB_TRANS_PRTCL_CODE | VARCHAR2 | (30) | Transmission protocol for online debit messages | |
| ONLINE_DEB_ACK_RDR_CODE | VARCHAR2 | (30) | Y | Acknowledgment reader for debit responses |
| SETTLEMENT_REQ_FLAG | VARCHAR2 | (1) | Y | Indicates whether settlement is required by the payment system after the online debit |
| SETTLEMENT_FORMAT_CODE | VARCHAR2 | (30) | Format for settlements | |
| SETTLEMENT_TRANS_PRTCL_CODE | VARCHAR2 | (30) | Transmission protocol for funds transfer messages | |
| SETTLEMENT_ACK_RDR_CODE | VARCHAR2 | (30) | Acknowledgment reader for funds transfer responses | |
| QUERY_FORMAT_CODE | VARCHAR2 | (30) | Format for the query request | |
| QUERY_TRANS_PRTCL_CODE | VARCHAR2 | (30) | Transmission protocol for query requests | |
| QUERY_ACK_RDR_CODE | VARCHAR2 | (30) | Query acknowledgement/response reader | |
| GROUP_BY_ORG | VARCHAR2 | (1) | Y or N flag specifying whether settlements should be grouped into settlement batches by first party organization | |
| GROUP_BY_LEGAL_ENTITY | VARCHAR2 | (1) | Y or N flag specifying whether settlements should be grouped into settlement batches by first party legal entity | |
| GROUP_BY_INT_BANK_ACCOUNT | VARCHAR2 | (1) | Y or N flag specifying whether settlements should be grouped into settlement batches by internal bank account | |
| GROUP_BY_SETTLEMENT_CURR | VARCHAR2 | (1) | Y or N flag specifying whether settlements should be grouped into settlement batches by settlement currency | |
| GROUP_BY_SETTLEMENT_DATE | VARCHAR2 | (1) | Y or N flag specifying whether settlements should be grouped into settlement batches by settlement date | |
| LIMIT_BY_AMT_CURR | VARCHAR2 | (10) | Currency in which the maximum total amount per settlement batch is calculated. | |
| LIMIT_BY_EXCH_RATE_TYPE | VARCHAR2 | (255) | Exchange rate type used to compare the settlement batch total amount to the maximum total amount allowed. Types are defined in the General Ledger currency exchange rate type lookups table. These include CORPORATE, SPOT, and DAILY. | |
| LIMIT_BY_TOTAL_AMT | NUMBER | Maximum total amount for which a settlement batch can be created | ||
| LIMIT_BY_SETTLEMENT_NUM | NUMBER | Maximum number of settlements that can be included in a settlement batch | ||
| INACTIVE_DATE | DATE | Inactivity date for the profile | ||
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. |
| SETTLEMENT_COMPLETE_POINT | VARCHAR2 | (50) | A point when the settlement is considered complete. | |
| OVERRIDE_PAYER_DELIVERY_FLAG | VARCHAR2 | (1) | Y or N Flag indicating whether the payer notification delivery method should be overridden by the payer delivery method preference. | |
| PAYER_NOTIFICATION_FORMAT | VARCHAR2 | (30) | Payment format identifier for payer notification | |
| PAYER_NOTIFICATION_DEL_METHOD | VARCHAR2 | (100) | Remittance advice delivery method. Values, from the lookup IBY_DELIVERY_METHODS, include EMAIL, FAX, and PRINTED | |
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | Descriptive Flexfield structure defining column | |
| ATTRIBUTE1 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE2 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE3 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE4 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE5 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE6 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE7 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE8 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE9 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE10 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE11 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE12 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE13 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE14 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE15 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| AUTOMATIC_PN_SUBMIT_FLAG | VARCHAR2 | (1) | Y or N flag indicating whether the payer notification is submitted automatically at settlement completion point | |
| PAYER_NOTIFICATION_CONDITION | VARCHAR2 | (30) | Condition for Payer notification to be sent is based on All the receipts or num of receipts | |
| PN_COND_NUM_OF_RECEIPTS | NUMBER | Number of reciptis, Payer Notification will be sent only if Number of receipts in the batch > this number. | ||
| EXCLUDE_TRXN_DET_EXTRACTION | VARCHAR2 | (1) | Indicates to exclude the extraction of Invoice details | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_FNDCPT_SYS_DC_PF_B does not reference any database object
IBY.IBY_FNDCPT_SYS_DC_PF_B is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_FNDCPT_SYS_DC_PF_TL.SYS_DC_PROFILE_CODE | % |
IBY_FNDCPT_SYS_DC_PF stores payment system-defined attributes of the bank account electronic funds transfer process.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_FNDCPT_SYS_DC_PF_TL_U1 | UNIQUE | APPS_TS_TX_IDX |
LANGUAGE
SYS_DC_PROFILE_CODE ZD_EDITION_NAME |
| IBY_FNDCPT_SYS_DC_PF_TL_SPC_N1 | NONUNIQUE | APPS_TS_TX_IDX | SYS_DC_PROFILE_CODE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| SYS_DC_PROFILE_CODE | VARCHAR2 | (30) | Y | System process profile identifier |
| LANGUAGE | VARCHAR2 | (4) | Y | Language code |
| SOURCE_LANG | VARCHAR2 | (4) | Y | Language code of the record's current language |
| SYS_DC_PROFILE_NAME | VARCHAR2 | (100) | Y | System process profile name |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. |
| DESCRIPTION | VARCHAR2 | (250) | Description | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_FNDCPT_SYS_DC_PF_TL does not reference any database object
IBY.IBY_FNDCPT_SYS_DC_PF_TL is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_FNDCPT_SYS_EFT_PF_B.PAYMENT_SYSTEM_ID | IBY_BEPINFO |
| IBY_FNDCPT_SYS_EFT_PF_B.QUERY_ACK_RDR_CODE | % |
| IBY_FNDCPT_SYS_EFT_PF_B.PAYER_NOTIFICATION_FORMAT | IBY_FORMATS_B |
| IBY_FNDCPT_SYS_EFT_PF_B.ACCOMPANY_LETTER_FORMAT | IBY_FORMATS_B |
| IBY_FNDCPT_SYS_EFT_PF_B.VERIFY_FORMAT_CODE | IBY_FORMATS_B |
| IBY_FNDCPT_SYS_EFT_PF_B.VERIFY_TRANS_PRTCL_CODE | IBY_TRANSMIT_PROTOCOLS_B |
| IBY_FNDCPT_SYS_EFT_PF_B.VERIFY_ACK_RDR_CODE | % |
| IBY_FNDCPT_SYS_EFT_PF_B.FUNDS_XFER_FORMAT_CODE | IBY_FORMATS_B |
| IBY_FNDCPT_SYS_EFT_PF_B.FUNDS_XFER_TRANS_PRTCL_CODE | IBY_TRANSMIT_PROTOCOLS_B |
| IBY_FNDCPT_SYS_EFT_PF_B.FUNDS_XFER_ACK_RDR_CODE | % |
| IBY_FNDCPT_SYS_EFT_PF_B.QUERY_FORMAT_CODE | IBY_FORMATS_B |
| IBY_FNDCPT_SYS_EFT_PF_B.QUERY_TRANS_PRTCL_CODE | IBY_TRANSMIT_PROTOCOLS_B |
IBY_FNDCPT_SYS_EFT_PF stores payment system-defined attributes of the bank account electronic funds transfer process.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_FNDCPT_SYS_EFT_PF_B_U1 | UNIQUE | APPS_TS_TX_IDX |
SYS_EFT_PROFILE_CODE
ZD_EDITION_NAME |
| IBY_FNDCPT_SYS_EFT_PF_B_N1 | NONUNIQUE | APPS_TS_TX_IDX | PAYER_NOTIFICATION_FORMAT |
| IBY_FNDCPT_SYS_EFT_PF_B_N2 | NONUNIQUE | APPS_TS_TX_IDX | ACCOMPANY_LETTER_FORMAT |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| SYS_EFT_PROFILE_CODE | VARCHAR2 | (30) | Y | System process profile identifier |
| PAYMENT_SYSTEM_ID | NUMBER | (15) | Y | Payment system identifier |
| VERIFY_FORMAT_CODE | VARCHAR2 | (30) | Payment format identifier for verification messages (if supported). | |
| VERIFY_TRANS_PRTCL_CODE | VARCHAR2 | (30) | Transmission protocol for verification messages | |
| VERIFY_ACK_RDR_CODE | VARCHAR2 | (30) | Acknowledgment reader for verification responses | |
| SETTLE_REQUIRE_VRFY_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating that the settlements require pre-existing verification operations |
| FUNDS_XFER_FORMAT_CODE | VARCHAR2 | (30) | Y | Format for funds transfer transactions. |
| FUNDS_XFER_TRANS_PRTCL_CODE | VARCHAR2 | (30) | Transmission protocol for funds transfer messages. | |
| FUNDS_XFER_ACK_RDR_CODE | VARCHAR2 | (30) | Acknowledgment reader for funds transfer responses | |
| QUERY_FORMAT_CODE | VARCHAR2 | (30) | Format for the query request | |
| QUERY_TRANS_PRTCL_CODE | VARCHAR2 | (30) | Transmission protocol for query requests | |
| QUERY_ACK_RDR_CODE | VARCHAR2 | (30) | Query acknowledgement/response reader | |
| GROUP_BY_ORG | VARCHAR2 | (1) | Y or N flag specifying whether settlements should be grouped into settlement batches by first party organization | |
| GROUP_BY_LEGAL_ENTITY | VARCHAR2 | (1) | Y or N flag specifying whether settlements should be grouped into settlement batches by first party legal entity | |
| GROUP_BY_INT_BANK_ACCOUNT | VARCHAR2 | (1) | Y or N flag specifying whether settlements should be grouped into settlement batches by internal bank account | |
| GROUP_BY_SETTLEMENT_CURR | VARCHAR2 | (1) | Y or N flag specifying whether settlements should be grouped into settlement batches by settlement currency | |
| GROUP_BY_SETTLEMENT_DATE | VARCHAR2 | (1) | Y or N flag specifying whether settlements should be grouped into settlement batches by settlement date | |
| LIMIT_BY_AMT_CURR | VARCHAR2 | (10) | Currency in which the maximum total amount per settlement batch is calculated. | |
| LIMIT_BY_EXCH_RATE_TYPE | VARCHAR2 | (255) | Exchange rate type used to compare the settlement batch total amount to the maximum total amount allowed. Types are defined in the General Ledger currency exchange rate type lookups table. These include CORPORATE, SPOT, and DAILY. | |
| LIMIT_BY_TOTAL_AMT | NUMBER | Maximum total amount for which a settlement batch can be created | ||
| LIMIT_BY_SETTLEMENT_NUM | NUMBER | Maximum number of settlements that can be included in a settlement batch | ||
| INACTIVE_DATE | DATE | Inactivity date for the profile | ||
| CREATED_BY | NUMBER | (15) | Standard Who column | |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. | |
| SETTLEMENT_COMPLETE_POINT | VARCHAR2 | (50) | A point when the settlement is considered complete. | |
| OVERRIDE_PAYER_DELIVERY_FLAG | VARCHAR2 | (1) | Y or N flag indicating whether the payer notification delivery method should be overridden by the payer delivery method preference. | |
| PAYER_NOTIFICATION_FORMAT | VARCHAR2 | (30) | Payment format identifier for payer notification | |
| PAYER_NOTIFICATION_DEL_METHOD | VARCHAR2 | (100) | Remittance advice delivery method. Values, from the lookup IBY_DELIVERY_METHODS, include EMAIL, FAX, and PRINTED | |
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | Descriptive Flexfield structure defining column | |
| ATTRIBUTE1 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE2 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE3 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE4 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE5 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE6 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE7 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE8 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE9 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE10 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE11 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE12 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE13 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE14 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE15 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ACCOMPANY_LETTER_FORMAT | VARCHAR2 | (30) | Accompany Letter Format | |
| AUTOMATIC_PN_SUBMIT_FLAG | VARCHAR2 | (1) | Y or N flag indicating whether the payer notification is submitted automatically at settlement completion point | |
| PAYER_NOTIFICATION_CONDITION | VARCHAR2 | (30) | Condition for Payer notification to be sent is based on All the receipts or num of receipts | |
| PN_COND_NUM_OF_RECEIPTS | NUMBER | Number of reciptis, Payer Notification will be sent only if Number of receipts in the batch > this number. | ||
| EXCLUDE_TRXN_DET_EXTRACTION | VARCHAR2 | (1) | Indicates to Excude the extraction of Invoice details | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_FNDCPT_SYS_EFT_PF_B does not reference any database object
IBY.IBY_FNDCPT_SYS_EFT_PF_B is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_FNDCPT_SYS_EFT_PF_TL.SYS_EFT_PROFILE_CODE | % |
IBY_FNDCPT_SYS_EFT_PF stores payment system-defined attributes of the bank account electronic funds transfer process.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_FNDCPT_SYS_EFT_PF_TL_U1 | UNIQUE | APPS_TS_TX_IDX |
LANGUAGE
SYS_EFT_PROFILE_CODE ZD_EDITION_NAME |
| IBY_FNDCPT_SYS_EFT_PF_TL_N1 | NONUNIQUE | APPS_TS_TX_IDX | SYS_EFT_PROFILE_CODE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| SYS_EFT_PROFILE_CODE | VARCHAR2 | (30) | Y | System process profile identifier |
| LANGUAGE | VARCHAR2 | (4) | Y | Language code |
| SOURCE_LANG | VARCHAR2 | (4) | Y | Language code of the record's current language |
| SYS_EFT_PROFILE_NAME | VARCHAR2 | (100) | Y | System process profile name |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. |
| DESCRIPTION | VARCHAR2 | (250) | Description | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_FNDCPT_SYS_EFT_PF_TL does not reference any database object
IBY.IBY_FNDCPT_SYS_EFT_PF_TL is referenced by following:
| Description: | "The data in this table will be created by the source products through the public API IBY_FNDCPT_TRXN_PUB, Create_Transaction_Extension and Copy_Transaction_Extension to register a Funds capture transaction. IBY_FNDCPT_TX_EXTENSIONS table |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_FNDCPT_TX_EXTENSIONS.PAYMENT_CHANNEL_CODE | IBY_FNDCPT_PMT_CHNNLS_B |
| IBY_FNDCPT_TX_EXTENSIONS.INSTR_ASSIGNMENT_ID | IBY_PMT_INSTR_USES_ALL |
| IBY_FNDCPT_TX_EXTENSIONS.ORIGIN_APPLICATION_ID | FND_APPLICATION |
| IBY_FNDCPT_TX_EXTENSIONS.INSTR_CODE_SEC_SEGMENT_ID | IBY_SECURITY_SEGMENTS |
| Foreign Key Column | Foreign Table |
|---|---|
| AR_CASH_RECEIPTS_ALL.PAYMENT_TRXN_EXTENSION_ID | IBY_FNDCPT_TX_EXTENSIONS |
| AR_CC_ERROR_HISTORY.PAYMENT_TRXN_EXTENSION_ID | IBY_FNDCPT_TX_EXTENSIONS |
| IBY_FNDCPT_TX_OPERATIONS.TRXN_EXTENSION_ID | IBY_FNDCPT_TX_EXTENSIONS |
| IBY_FNDCPT_TX_XE_COPIES.COPY_TRXN_EXTENSION_ID | IBY_FNDCPT_TX_EXTENSIONS |
| IBY_FNDCPT_TX_XE_COPIES.SOURCE_TRXN_EXTENSION_ID | IBY_FNDCPT_TX_EXTENSIONS |
| IBY_TRXN_SUMMARIES_ALL.INITIATOR_EXTENSION_ID | IBY_FNDCPT_TX_EXTENSIONS |
| RA_CUSTOMER_TRX_ALL.PAYMENT_TRXN_EXTENSION_ID | IBY_FNDCPT_TX_EXTENSIONS |
| RA_CUSTOMER_TRX_LINES_ALL.PAYMENT_TRXN_EXTENSION_ID | IBY_FNDCPT_TX_EXTENSIONS |
| RA_INTERFACE_LINES_ALL.PAYMENT_TRXN_EXTENSION_ID | IBY_FNDCPT_TX_EXTENSIONS |
Payment attributes for a given funds capture transaction
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_FNDCPT_TX_EXTENSIONS_U1 | UNIQUE | APPS_TS_TX_IDX | TRXN_EXTENSION_ID |
| IBY_FNDCPT_TX_EXTENSIONS_IU_N2 | NONUNIQUE | APPS_TS_TX_IDX | INSTR_ASSIGNMENT_ID |
| IBY_FNDCPT_TX_EXTENSIONS_O_N1 | NONUNIQUE | APPS_TS_TX_IDX | ORDER_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| TRXN_EXTENSION_ID | NUMBER | (15) | Y | Sequence: IBY_FNDCPT_TX_EXTENSIONS_S.nextval |
| PAYMENT_CHANNEL_CODE | VARCHAR2 | (30) | Y | Payment channel code |
| EXT_PAYER_ID | NUMBER | (15) | Foreign key to IBY_EXTERNAL_PAYERS_ALL.EXT_PAYER_ID | |
| INSTR_ASSIGNMENT_ID | NUMBER | (15) | This column is a foreign key to IBY_PMT_INSTR_USES_ALL.INSTRUMENT_PAYMENT_USE_ID | |
| INSTRUMENT_SECURITY_CODE | VARCHAR2 | (10) | Instrument security code. For credit cards this is the 3 or 4-digit security code printed on the card's reverse. Also known as CVVC for MasterCard, CVV2 for Visa, and CID for American Express. This column is encrypted. | |
| INSTR_SEC_CODE_LENGTH | NUMBER | (2) | Instrument security code length; used to help in data compression | |
| VOICE_AUTHORIZATION_FLAG | VARCHAR2 | (1) | Y or N flag indicating this transaction has a voice authorization | |
| VOICE_AUTHORIZATION_DATE | DATE | Voice authorization date | ||
| VOICE_AUTHORIZATION_CODE | VARCHAR2 | (100) | Voice authorization code | |
| ORDER_ID | VARCHAR2 | (75) | Transaction order identifier | |
| PO_NUMBER | VARCHAR2 | (100) | Purchase order number | |
| TRXN_REF_NUMBER1 | VARCHAR2 | (30) | Transaction reference number 1; optional transaction identifier used within the calling application | |
| TRXN_REF_NUMBER2 | VARCHAR2 | (30) | Transaction reference number 2; optional transaction identifier used within the calling application | |
| ADDITIONAL_INFO | VARCHAR2 | (255) | Free-text field for additional information | |
| INSTR_CODE_SEC_SEGMENT_ID | NUMBER | (15) | Foreign key to IBY_SECURITY_SEGMENTS.SEC_SEGMENT_ID | |
| ENCRYPTED | VARCHAR2 | (1) | Y | Whether the extension is encrypted |
| PO_LINE_NUMBER | VARCHAR2 | (100) | Purchase order line number | |
| ORIGIN_APPLICATION_ID | NUMBER | Y | Originating application id | |
| TANGIBLEID | VARCHAR2 | (80) | The tangibleid generated by IBY for the transaction. This column will be used by Oracle Payments to link the upgraded transaction extensions with their associated IBY operations. | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who Column |
| CREATION_DATE | DATE | Y | Standard Who Column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who Column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who Column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who Column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object Version Number | |
| PAYMENT_SYSTEM_ORDER_NUMBER | VARCHAR2 | (80) | This is the Payment System Order Number for the transaction. | |
| SEQ_TYPE_LAST | VARCHAR2 | (1) | Flag to denote the last transaction for a recurrent type |
IBY.IBY_FNDCPT_TX_EXTENSIONS does not reference any database object
IBY.IBY_FNDCPT_TX_EXTENSIONS is referenced by following:
| Description: | IBY_FNDCPT_TX_OPERATIONS stores associations between transaction extension entities and authorization or settlement transactions. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_FNDCPT_TX_OPERATIONS.TRXN_EXTENSION_ID | IBY_FNDCPT_TX_EXTENSIONS |
IBY_FNDCPT_TX_OPERATIONS stores associations between transaction extension entities and authorization or settlement transactions.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_FNDCPT_TX_OPERATIONS_N1 | NONUNIQUE | APPS_TS_TX_IDX | TRXN_EXTENSION_ID |
| IBY_FNDCPT_TX_OPERATIONS_N2 | NONUNIQUE | APPS_TS_TX_IDX | TRANSACTIONID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| TRXN_EXTENSION_ID | NUMBER | (15) | Y | Transaction extension primary key |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. | |
| TRANSACTIONID | NUMBER | (15) | Y | Transaction identifier for the series of Payments transaction operations performed |
IBY.IBY_FNDCPT_TX_OPERATIONS does not reference any database object
IBY.IBY_FNDCPT_TX_OPERATIONS is referenced by following:
| Description: | IBY_FNDCPT_TX_XE_COPIES stores the copy relationship between transaction extension entities. This relationship is many-to-many, since during copy transaction extension, entities may be merged or split. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_FNDCPT_TX_XE_COPIES.COPY_TRXN_EXTENSION_ID | IBY_FNDCPT_TX_EXTENSIONS |
| IBY_FNDCPT_TX_XE_COPIES.SOURCE_TRXN_EXTENSION_ID | IBY_FNDCPT_TX_EXTENSIONS |
IBY_FNDCPT_TX_XE_COPIES stores the copy relationship between transaction extension entities. This relationship is many-to-many, since during copy transaction extension, entities may be merged or split.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_FNDCPT_TX_XE_COPIES_N1 | NONUNIQUE | APPS_TS_TX_IDX | SOURCE_TRXN_EXTENSION_ID |
| IBY_FNDCPT_TX_XE_COPIES_N2 | NONUNIQUE | APPS_TS_TX_IDX | COPY_TRXN_EXTENSION_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| SOURCE_TRXN_EXTENSION_ID | NUMBER | (15) | Y | Source of the transaction extension |
| COPY_TRXN_EXTENSION_ID | NUMBER | (15) | Y | Copy transaction extension |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. |
IBY.IBY_FNDCPT_TX_XE_COPIES does not reference any database object
IBY.IBY_FNDCPT_TX_XE_COPIES is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_FNDCPT_USER_CC_PF_B.SYS_CC_PROFILE_CODE | % |
| IBY_FNDCPT_USER_CC_PF_B.BEP_ACCOUNT_ID | IBY_BEPKEYS |
| IBY_FNDCPT_USER_CC_PF_B.ONLINE_AUTH_TRANS_CONFIG_ID | % |
| IBY_FNDCPT_USER_CC_PF_B.SETTLEMENT_TRANS_CONFIG_ID | % |
| IBY_FNDCPT_USER_CC_PF_B.QUERY_TRANS_CONFIG_ID | % |
IBY_FNDCPT_USER_CC_PF stores a complete credit card process profile defined for a single payment system account..
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_FNDCPT_USER_CC_PF_B_UPC_U1 | UNIQUE | APPS_TS_TX_IDX | USER_CC_PROFILE_CODE |
| IBY_FNDCPT_USER_CC_PF_B_N1 | NONUNIQUE | APPS_TS_TX_IDX | BEP_ACCOUNT_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| USER_CC_PROFILE_CODE | VARCHAR2 | (30) | Y | Funds capture process profile identifier |
| SYS_CC_PROFILE_CODE | VARCHAR2 | (30) | Y | System profile |
| BEP_ACCOUNT_ID | NUMBER | (15) | Y | Associated payment system account |
| ONLINE_AUTH_TRANS_CONFIG_ID | NUMBER | (15) | Identifier of the transmission configuration used for online authorizations | |
| SETTLEMENT_TRANS_CONFIG_ID | NUMBER | (15) | Identifier of the transmission configuration used for settlements | |
| QUERY_TRANS_CONFIG_ID | NUMBER | (15) | Transmission configuration for acknowledgement processing | |
| INACTIVE_DATE | DATE | Inactivity date for the profile | ||
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. |
IBY.IBY_FNDCPT_USER_CC_PF_B does not reference any database object
IBY.IBY_FNDCPT_USER_CC_PF_B is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_FNDCPT_USER_CC_PF_TL.USER_CC_PROFILE_CODE | % |
IBY_FNDCPT_USER_CC_PF stores a complete credit card process profile defined for a single payment system account..
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_FNDCPT_USER_CC_PF_TL_UC_N1 | NONUNIQUE | APPS_TS_TX_IDX | USER_CC_PROFILE_CODE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| USER_CC_PROFILE_CODE | VARCHAR2 | (30) | Y | Funds capture process profile identifier |
| LANGUAGE | VARCHAR2 | (4) | Y | Language code |
| SOURCE_LANG | VARCHAR2 | (4) | Y | Language code of the record's current language |
| USER_CC_PROFILE_NAME | VARCHAR2 | (100) | Y | Funds capture process profile name |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. |
IBY.IBY_FNDCPT_USER_CC_PF_TL does not reference any database object
IBY.IBY_FNDCPT_USER_CC_PF_TL is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_FNDCPT_USER_DC_PF_B.SYS_DC_PROFILE_CODE | % |
| IBY_FNDCPT_USER_DC_PF_B.BEP_ACCOUNT_ID | IBY_BEPKEYS |
| IBY_FNDCPT_USER_DC_PF_B.ONLINE_DEB_TRANS_CONFIG_ID | % |
| IBY_FNDCPT_USER_DC_PF_B.SETTLEMENT_TRANS_CONFIG_ID | % |
| IBY_FNDCPT_USER_DC_PF_B.QUERY_TRANS_CONFIG_ID | % |
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_FNDCPT_USER_DC_PF_TL.USER_DC_PROFILE_CODE | IBY_FNDCPT_USER_DC_PF_B |
IBY_FNDCPT_USER_DC_PF stores a complete credit card process profile defined for a single payment system account.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_FNDCPT_USER_DC_PF_B_UPC_U1 | UNIQUE | APPS_TS_TX_IDX | USER_DC_PROFILE_CODE |
| IBY_FNDCPT_USER_DC_PF_B_N1 | NONUNIQUE | APPS_TS_TX_IDX | BEP_ACCOUNT_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| USER_DC_PROFILE_CODE | VARCHAR2 | (30) | Y | Funds capture process profile identifier |
| SYS_DC_PROFILE_CODE | VARCHAR2 | (30) | Y | System profile |
| BEP_ACCOUNT_ID | NUMBER | (15) | Y | Associated payment system account |
| ONLINE_DEB_TRANS_CONFIG_ID | NUMBER | (15) | Identifier of the transmission configuration used for online debits | |
| SETTLEMENT_TRANS_CONFIG_ID | NUMBER | (15) | Identifier of the transmission configuration used for settlements | |
| QUERY_TRANS_CONFIG_ID | NUMBER | (15) | Transmission configuration for acknowledgement processing | |
| INACTIVE_DATE | DATE | Inactivity date for the profile | ||
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. |
IBY.IBY_FNDCPT_USER_DC_PF_B does not reference any database object
IBY.IBY_FNDCPT_USER_DC_PF_B is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_FNDCPT_USER_DC_PF_TL.USER_DC_PROFILE_CODE | IBY_FNDCPT_USER_DC_PF_B |
IBY_FNDCPT_USER_DC_PF stores a complete credit card process profile defined for a single payment system account.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_FNDCPT_USER_DC_PF_B_UPC_N1 | NONUNIQUE | APPS_TS_TX_IDX | USER_DC_PROFILE_CODE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| USER_DC_PROFILE_CODE | VARCHAR2 | (30) | Y | Funds capture process profile identifier |
| LANGUAGE | VARCHAR2 | (4) | Y | Language code |
| SOURCE_LANG | VARCHAR2 | (4) | Y | Language code of the record's current language |
| USER_DC_PROFILE_NAME | VARCHAR2 | (100) | Y | Funds capture process profile name |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. |
IBY.IBY_FNDCPT_USER_DC_PF_TL does not reference any database object
IBY.IBY_FNDCPT_USER_DC_PF_TL is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_FNDCPT_USER_EFT_PF_B.SYS_EFT_PROFILE_CODE | % |
| IBY_FNDCPT_USER_EFT_PF_B.BEP_ACCOUNT_ID | IBY_BEPKEYS |
| IBY_FNDCPT_USER_EFT_PF_B.VERIFY_TRANS_CONFIG_ID | % |
| IBY_FNDCPT_USER_EFT_PF_B.FUNDS_XFER_TRANS_CONFIG_ID | % |
| IBY_FNDCPT_USER_EFT_PF_B.QUERY_TRANS_CONFIG_ID | % |
IBY_FNDCPT_USER_EFT_PF stores a complete credit card process profile defined for a single payment system account.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_FNDCPT_USER_EFT_PF_B_U1 | UNIQUE | APPS_TS_TX_IDX | USER_EFT_PROFILE_CODE |
| IBY_FNDCPT_USER_EFT_PF_B_N1 | NONUNIQUE | APPS_TS_TX_IDX | BEP_ACCOUNT_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| USER_EFT_PROFILE_CODE | VARCHAR2 | (30) | Y | Funds capture process profile identifier |
| SYS_EFT_PROFILE_CODE | VARCHAR2 | (30) | Y | System profile |
| BEP_ACCOUNT_ID | NUMBER | (15) | Y | Associated payment system account |
| VERIFY_TRANS_CONFIG_ID | NUMBER | (15) | Identifier of the transmission configuration used for online verifications | |
| FUNDS_XFER_TRANS_CONFIG_ID | NUMBER | (15) | Identifier of the transmission configuration used for funds transfers | |
| QUERY_TRANS_CONFIG_ID | NUMBER | (15) | Transmission configuration for acknowledgement processing | |
| INACTIVE_DATE | DATE | Inactivity date for the profile | ||
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. |
IBY.IBY_FNDCPT_USER_EFT_PF_B does not reference any database object
IBY.IBY_FNDCPT_USER_EFT_PF_B is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_FNDCPT_USER_EFT_PF_TL.USER_EFT_PROFILE_CODE | % |
IBY_FNDCPT_USER_EFT_PF stores a complete credit card process profile defined for a single payment system account.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_FNDCPT_USER_EFT_PF_TL_N1 | NONUNIQUE | APPS_TS_TX_IDX | USER_EFT_PROFILE_CODE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| USER_EFT_PROFILE_CODE | VARCHAR2 | (30) | Y | Funds capture process profile identifier |
| LANGUAGE | VARCHAR2 | (4) | Y | Language code |
| SOURCE_LANG | VARCHAR2 | (4) | Y | Language code of the record's current language |
| USER_EFT_PROFILE_NAME | VARCHAR2 | (100) | Y | Funds capture process profile name |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. |
IBY.IBY_FNDCPT_USER_EFT_PF_TL does not reference any database object
IBY.IBY_FNDCPT_USER_EFT_PF_TL is referenced by following:
| Description: | Stores payment processing format types |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_FORMATS_B.EXTRACT_ID | IBY_EXTRACTS_B |
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_DOCS_PAYABLE_ALL.PAYMENT_FORMAT_CODE | IBY_FORMATS_B |
| IBY_EXTERNAL_PAYEES_ALL.PAYMENT_FORMAT_CODE | IBY_FORMATS_B |
| IBY_EXTRACT_ACTIVATIONS.FORMAT_CODE | IBY_FORMATS_B |
| IBY_FNDCPT_SYS_CC_PF_B.SETTLEMENT_FORMAT_CODE | IBY_FORMATS_B |
| IBY_FNDCPT_SYS_CC_PF_B.QUERY_FORMAT_CODE | IBY_FORMATS_B |
| IBY_FNDCPT_SYS_CC_PF_B.PAYER_NOTIFICATION_FORMAT | IBY_FORMATS_B |
| IBY_FNDCPT_SYS_DC_PF_B.PAYER_NOTIFICATION_FORMAT | IBY_FORMATS_B |
| IBY_FNDCPT_SYS_DC_PF_B.ONLINE_DEB_ACK_RDR_CODE | IBY_FORMATS_B |
| IBY_FNDCPT_SYS_DC_PF_B.SETTLEMENT_FORMAT_CODE | IBY_FORMATS_B |
| IBY_FNDCPT_SYS_DC_PF_B.QUERY_FORMAT_CODE | IBY_FORMATS_B |
| IBY_FNDCPT_SYS_EFT_PF_B.PAYER_NOTIFICATION_FORMAT | IBY_FORMATS_B |
| IBY_FNDCPT_SYS_EFT_PF_B.ACCOMPANY_LETTER_FORMAT | IBY_FORMATS_B |
| IBY_FNDCPT_SYS_EFT_PF_B.VERIFY_FORMAT_CODE | IBY_FORMATS_B |
| IBY_FNDCPT_SYS_EFT_PF_B.FUNDS_XFER_FORMAT_CODE | IBY_FORMATS_B |
| IBY_FNDCPT_SYS_EFT_PF_B.QUERY_FORMAT_CODE | IBY_FORMATS_B |
| IBY_PAY_INSTRUCTIONS_H.PAYMENT_FORMAT_CODE | IBY_FORMATS_B |
| IBY_PAY_INSTRUCTIONS_H.POSITIVE_PAY_FORMAT_CODE | IBY_FORMATS_B |
| IBY_PMT_SYS_FORMATS.PAYMENT_FORMAT_CODE | IBY_FORMATS_B |
| IBY_REMIT_ADVICE_SETUP.REMITTANCE_ADVICE_FORMAT_CODE | IBY_FORMATS_B |
| IBY_SYS_PMT_PROFILES_B.PAYMENT_FORMAT_CODE | IBY_FORMATS_B |
| IBY_SYS_PMT_PROFILES_B.POSITIVE_PAY_FORMAT_CODE | IBY_FORMATS_B |
| IBY_SYS_PMT_PROFILES_B.PAY_FILE_LETTER_FORMAT_CODE | IBY_FORMATS_B |
| IBY_TEMP_EXT_PAYEES.PAYMENT_FORMAT_CODE | IBY_FORMATS_B |
IBY_FORMATS stores payment file format information, including the name of the XDO template used to create payment files and the extract upon which the template depends.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_FORMATS_B_FORMATCODE_U1 | UNIQUE | APPS_TS_TX_IDX |
FORMAT_CODE
ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| FORMAT_CODE | VARCHAR2 | (30) | Y | Payment format identifier |
| FORMAT_TYPE_CODE | VARCHAR2 | (30) | Y | Payment format type. Values, from the lookup IBY_FORMAT_TYPES, include OUTBOUND_PAYMENT_INSTRUCTION, PAYMENT_REMITTANCE, POSITIVE_PAY_FILE, FUNDS_CAPTURE_INSTRUCTION |
| FORMAT_TEMPLATE_CODE | VARCHAR2 | (80) | Y | Payment format code, as defined in the XML Publisher registry |
| EXTRACT_ID | NUMBER | (15) | Y | Extract identifier |
| REFERENCE_FORMAT_CODE | VARCHAR2 | (30) | Program name of the check formats | |
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | Descriptive Flexfield structure defining column | |
| ATTRIBUTE1 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE2 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE3 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE4 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE5 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE6 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE7 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE8 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE9 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE10 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE11 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE12 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE13 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE14 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE15 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. |
| SEEDED_FLAG | VARCHAR2 | (1) | Y or N flag indicating that the data is seeded record | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_FORMATS_B does not reference any database object
IBY.IBY_FORMATS_B is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_FORMATS_TL.FORMAT_CODE | % |
IBY_FORMATS stores payment file format information, including the name of the XDO template used to create payment files and the extract upon which the template depends.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_FORMATS_TL_U1 | UNIQUE | APPS_TS_TX_IDX |
LANGUAGE
FORMAT_CODE ZD_EDITION_NAME |
| IBY_FORMATS_TL_FORMATCODE_N1 | NONUNIQUE | APPS_TS_TX_IDX | FORMAT_CODE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| FORMAT_CODE | VARCHAR2 | (30) | Y | Payment format identifier |
| LANGUAGE | VARCHAR2 | (4) | Y | Language code |
| SOURCE_LANG | VARCHAR2 | (4) | Y | Language code of the record's current language |
| FORMAT_NAME | VARCHAR2 | (300) | Y | Payment format name |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_FORMATS_TL does not reference any database object
IBY.IBY_FORMATS_TL is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_F_CRDT_APP_STATUS_TL.CREDIT_APP_STATUS_ID | IBY_F_CRDT_APP_STATUS_B |
| IBY_F_T_CRDT_APPS_ALL_B.CREDIT_APP_STATUS_ID | IBY_F_CRDT_APP_STATUS_B |
| IBY_F_T_CRDT_APP_ST_H.OLD_STATUS_ID | IBY_F_CRDT_APP_STATUS_B |
| IBY_F_T_CRDT_APP_ST_H.NEW_STATUS_ID | IBY_F_CRDT_APP_STATUS_B |
| IBY_G_ST_TRANSITIONS.FROM_STATUS_ID | IBY_F_CRDT_APP_STATUS_B |
| IBY_G_ST_TRANSITIONS.TO_STATUS_ID | IBY_F_CRDT_APP_STATUS_B |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_F_CRDT_APP_STATUS_B_U1 | UNIQUE | APPS_TS_ARCHIVE | CREDIT_APP_STATUS_ID |
| IBY_F_CRDT_APP_STATUS_B_U2 | UNIQUE | APPS_TS_ARCHIVE | STATUS_CODE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| CREDIT_APP_STATUS_ID | NUMBER | (15) | Y | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Application level record locking for three tier stateless applications |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| STATUS_CODE | VARCHAR2 | (30) | Y | |
| START_DATE_ACTIVE | DATE | |||
| END_DATE_ACTIVE | DATE | |||
| UPDATE_ALLOWED_FLAG | VARCHAR2 | (1) | ||
| SEEDED_FLAG | VARCHAR2 | (1) | ||
| STATUS_CATEGORY_CODE | VARCHAR2 | (30) | ||
| STATUS_NUMBER | NUMBER | |||
| SECURITY_GROUP_ID | NUMBER | |||
| ATTRIBUTE_CATEGORY | VARCHAR2 | (240) | ||
| ATTRIBUTE1 | VARCHAR2 | (240) | ||
| ATTRIBUTE2 | VARCHAR2 | (240) | ||
| ATTRIBUTE3 | VARCHAR2 | (240) | ||
| ATTRIBUTE4 | VARCHAR2 | (240) | ||
| ATTRIBUTE5 | VARCHAR2 | (240) | ||
| ATTRIBUTE6 | VARCHAR2 | (240) | ||
| ATTRIBUTE7 | VARCHAR2 | (240) | ||
| ATTRIBUTE8 | VARCHAR2 | (240) | ||
| ATTRIBUTE9 | VARCHAR2 | (240) | ||
| ATTRIBUTE10 | VARCHAR2 | (240) | ||
| ATTRIBUTE11 | VARCHAR2 | (240) | ||
| ATTRIBUTE12 | VARCHAR2 | (240) | ||
| ATTRIBUTE13 | VARCHAR2 | (240) | ||
| ATTRIBUTE14 | VARCHAR2 | (240) | ||
| ATTRIBUTE15 | VARCHAR2 | (240) |
IBY.IBY_F_CRDT_APP_STATUS_B does not reference any database object
IBY.IBY_F_CRDT_APP_STATUS_B is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_F_CRDT_APP_STATUS_TL.CREDIT_APP_STATUS_ID | IBY_F_CRDT_APP_STATUS_B |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_F_CRDT_APP_STATUS_TL_U1 | UNIQUE | APPS_TS_ARCHIVE |
CREDIT_APP_STATUS_ID
LANGUAGE |
| IBY_F_CRDT_APP_STATUS_TL_U2 | UNIQUE | APPS_TS_ARCHIVE |
NAME
LANGUAGE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| CREDIT_APP_STATUS_ID | NUMBER | (15) | Y | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| NAME | VARCHAR2 | (80) | Y | |
| DESCRIPTION | VARCHAR2 | (2000) | ||
| CUST_FACING_NAME | VARCHAR2 | (80) | ||
| LANGUAGE | VARCHAR2 | (4) | Y | |
| SOURCE_LANG | VARCHAR2 | (4) | Y | |
| SECURITY_GROUP_ID | NUMBER |
IBY.IBY_F_CRDT_APP_STATUS_TL does not reference any database object
IBY.IBY_F_CRDT_APP_STATUS_TL is referenced by following:
| Description: |
|---|
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_F_PC_RATES_ALL_U1 | UNIQUE | APPS_TS_ARCHIVE | RATE_ID |
| IBY_F_PC_RATES_ALL_N1 | NONUNIQUE | APPS_TS_ARCHIVE | CUSTOMER_TYPE_CODE |
| IBY_F_PC_RATES_ALL_N2 | NONUNIQUE | APPS_TS_ARCHIVE | PAYMENT_TERM |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| RATE_ID | NUMBER | (15) | Y | |
| REQUEST_ID | NUMBER | (15) | Request Identifier | |
| PROGRAM_APPLICATION_ID | NUMBER | (15) | Application Identifier of last concurrent program to update record | |
| PROGRAM_ID | NUMBER | (15) | Identifier of last concurrent program to update record | |
| PROGRAM_UPDATE_DATE | DATE | Last date concurrent program updated record | ||
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Application level record locking for three tier stateless applications |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| RATE | NUMBER | (10) | Y | |
| CUSTOMER_TYPE_CODE | VARCHAR2 | (30) | ||
| PAYMENT_TERM | VARCHAR2 | (240) | ||
| PAYMENT_TERM_UOM_CODE | VARCHAR2 | (3) | ||
| DEAL_SIZE_MIN | NUMBER | |||
| DEAL_SIZE_MAX | NUMBER | |||
| DEAL_SIZE_CURRENCY_CODE | VARCHAR2 | (30) | ||
| ORG_ID | NUMBER | (15) | ||
| SECURITY_GROUP_ID | NUMBER |
IBY.IBY_F_PC_RATES_ALL does not reference any database object
IBY.IBY_F_PC_RATES_ALL is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_F_T_CA_GRNTRS_B.CREDIT_APP_ID | IBY_F_T_CRDT_APPS_ALL_B |
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_F_T_CA_GRNTRS_TL.CREDIT_APP_GRNTR_ID | IBY_F_T_CA_GRNTRS_B |
| IBY_F_T_CA_GRNTR_H.CREDIT_APP_GRNTR_ID | IBY_F_T_CA_GRNTRS_B |
| IBY_F_T_EMAIL_NOTIF_LOG.CREDIT_APP_GRNTR_ID | IBY_F_T_CA_GRNTRS_B |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_F_T_CA_GRNTRS_B_U1 | UNIQUE | APPS_TS_ARCHIVE | CREDIT_APP_GRNTR_ID |
| IBY_F_T_CA_GRNTRS_B_N1 | NONUNIQUE | APPS_TS_ARCHIVE | CREDIT_APP_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| CREDIT_APP_GRNTR_ID | NUMBER | (15) | Y | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Application level record locking for three tier stateless applications |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| CREDIT_APP_ID | NUMBER | (15) | Y | |
| ACTIVE_FLAG | VARCHAR2 | (1) | ||
| START_DATE_ACTIVE | DATE | |||
| END_DATE_ACTIVE | DATE | |||
| EMAIL_ADDRESS | VARCHAR2 | (2000) | ||
| SECURITY_KEY | VARCHAR2 | (150) | ||
| CREDIT_APP_GRNTR_SEQ | NUMBER | |||
| SECURITY_GROUP_ID | NUMBER |
IBY.IBY_F_T_CA_GRNTRS_B does not reference any database object
IBY.IBY_F_T_CA_GRNTRS_B is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_F_T_CA_GRNTRS_TL.CREDIT_APP_GRNTR_ID | IBY_F_T_CA_GRNTRS_B |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_F_T_CA_GRNTRS_TL_U1 | UNIQUE | APPS_TS_ARCHIVE |
CREDIT_APP_GRNTR_ID
LANGUAGE |
| IBY_F_T_CA_GRNTRS_TL_N1 | NONUNIQUE | APPS_TS_ARCHIVE |
FIRST_NAME
LANGUAGE |
| IBY_F_T_CA_GRNTRS_TL_N2 | NONUNIQUE | APPS_TS_ARCHIVE |
LAST_NAME
LANGUAGE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| CREDIT_APP_GRNTR_ID | NUMBER | (15) | Y | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| FIRST_NAME | VARCHAR2 | (150) | ||
| LAST_NAME | VARCHAR2 | (150) | ||
| LANGUAGE | VARCHAR2 | (4) | Y | |
| SOURCE_LANG | VARCHAR2 | (4) | Y | |
| SECURITY_GROUP_ID | NUMBER |
IBY.IBY_F_T_CA_GRNTRS_TL does not reference any database object
IBY.IBY_F_T_CA_GRNTRS_TL is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_F_T_CA_GRNTR_H.CREDIT_APP_GRNTR_ID | IBY_F_T_CA_GRNTRS_B |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_F_T_CA_GRNTR_H_U1 | UNIQUE | APPS_TS_ARCHIVE | CA_GRNTR_HISTORY_ID |
| IBY_F_T_CA_GRNTR_H_N1 | NONUNIQUE | APPS_TS_ARCHIVE | CREDIT_APP_GRNTR_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| CA_GRNTR_HISTORY_ID | NUMBER | (15) | Y | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Application level record locking for three tier stateless applications |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| CREDIT_APP_GRNTR_ID | NUMBER | (15) | Y | |
| GRNTR_EVENT_CODE | VARCHAR2 | (30) | ||
| GRNTR_EVENT_TIME | DATE | |||
| SECURITY_GROUP_ID | NUMBER |
IBY.IBY_F_T_CA_GRNTR_H does not reference any database object
IBY.IBY_F_T_CA_GRNTR_H is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_F_T_CRDT_APPS_ALL_B.TRXN_SUMMARY_ID | IBY_TRXN_SUMMARIES_ALL |
| IBY_F_T_CRDT_APPS_ALL_B.CREDIT_APP_STATUS_ID | IBY_F_CRDT_APP_STATUS_B |
| IBY_F_T_CRDT_APPS_ALL_B.CREDIT_APP_XML_ID | IBY_TRXN_DOCUMENTS |
| IBY_F_T_CRDT_APPS_ALL_B.TERMS_N_CONDITIONS_XML_ID | IBY_TRXN_DOCUMENTS |
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_F_T_CA_GRNTRS_B.CREDIT_APP_ID | IBY_F_T_CRDT_APPS_ALL_B |
| IBY_F_T_CRDT_APPS_ALL_TL.CREDIT_APP_ID | IBY_F_T_CRDT_APPS_ALL_B |
| IBY_F_T_CRDT_APP_REVS.CREDIT_APP_ID | IBY_F_T_CRDT_APPS_ALL_B |
| IBY_F_T_CRDT_APP_ST_H.CREDIT_APP_ID | IBY_F_T_CRDT_APPS_ALL_B |
| IBY_F_T_EMAIL_NOTIF_LOG.CREDIT_APP_ID | IBY_F_T_CRDT_APPS_ALL_B |
| IBY_G_T_MESSAGES.CREDIT_APP_ID | IBY_F_T_CRDT_APPS_ALL_B |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_F_T_CRDT_APPS_ALL_B_U1 | UNIQUE | APPS_TS_ARCHIVE | CREDIT_APP_ID |
| IBY_F_T_CRDT_APPS_ALL_B_U2 | UNIQUE | APPS_TS_ARCHIVE | TRXN_SUMMARY_ID |
| IBY_F_T_CRDT_APPS_ALL_B_N1 | NONUNIQUE | APPS_TS_ARCHIVE | CREDIT_APP_STATUS_ID |
| IBY_F_T_CRDT_APPS_ALL_B_N2 | NONUNIQUE | APPS_TS_ARCHIVE | CREDIT_APP_XML_ID |
| IBY_F_T_CRDT_APPS_ALL_B_N3 | NONUNIQUE | APPS_TS_ARCHIVE | TERMS_N_CONDITIONS_XML_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| CREDIT_APP_ID | NUMBER | (15) | Y | |
| REQUEST_ID | NUMBER | (15) | Request Identifier | |
| PROGRAM_APPLICATION_ID | NUMBER | (15) | Application Identifier of last concurrent program to update record | |
| PROGRAM_ID | NUMBER | (15) | Identifier of last concurrent program to update record | |
| PROGRAM_UPDATE_DATE | DATE | Last date concurrent program updated record | ||
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Application level record locking for three tier stateless applications |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| TRXN_SUMMARY_ID | NUMBER | (15) | Y | |
| CREDIT_APP_STATUS_ID | NUMBER | (15) | Y | |
| CREDIT_APP_XML_ID | NUMBER | (15) | ||
| TERMS_N_CONDITIONS_XML_ID | NUMBER | (15) | ||
| FINANCING_TYPE_CODE | VARCHAR2 | (30) | ||
| DURATION | NUMBER | |||
| DURATION_UOM_CODE | VARCHAR2 | (3) | ||
| PAYMENT_STRUCTURE_CODE | VARCHAR2 | (30) | ||
| INTEREST_RATE | NUMBER | (10) | ||
| DECISION_TIME_FRAME | NUMBER | |||
| DECISION_TIME_FRAME_UOM_CODE | VARCHAR2 | (30) | ||
| FIRST_SAVED_DATE | DATE | |||
| EXPIRATION_DATE | DATE | |||
| EXP_EXTENDED_COUNT | NUMBER | |||
| EXPIRING_FLAG | VARCHAR2 | (1) | ||
| DOC_RECEIVED_DATE | DATE | |||
| DOC_RECEIVED_FLAG | VARCHAR2 | (1) | ||
| N_PG_REQUESTED | NUMBER | |||
| N_PG_SUBMITTED | NUMBER | |||
| BUYER_FORM_MARKUP_FLAG | VARCHAR2 | (1) | ||
| ORG_ID | NUMBER | (15) | ||
| SECURITY_GROUP_ID | NUMBER | |||
| ATTRIBUTE_CATEGORY | VARCHAR2 | (30) | ||
| ATTRIBUTE1 | VARCHAR2 | (150) | ||
| ATTRIBUTE2 | VARCHAR2 | (150) | ||
| ATTRIBUTE3 | VARCHAR2 | (150) | ||
| ATTRIBUTE4 | VARCHAR2 | (150) | ||
| ATTRIBUTE5 | VARCHAR2 | (150) | ||
| ATTRIBUTE6 | VARCHAR2 | (150) | ||
| ATTRIBUTE7 | VARCHAR2 | (150) | ||
| ATTRIBUTE8 | VARCHAR2 | (150) | ||
| ATTRIBUTE9 | VARCHAR2 | (150) | ||
| ATTRIBUTE10 | VARCHAR2 | (150) | ||
| ATTRIBUTE11 | VARCHAR2 | (150) | ||
| ATTRIBUTE12 | VARCHAR2 | (150) | ||
| ATTRIBUTE13 | VARCHAR2 | (150) | ||
| ATTRIBUTE14 | VARCHAR2 | (150) | ||
| ATTRIBUTE15 | VARCHAR2 | (150) |
IBY.IBY_F_T_CRDT_APPS_ALL_B does not reference any database object
IBY.IBY_F_T_CRDT_APPS_ALL_B is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_F_T_CRDT_APPS_ALL_TL.CREDIT_APP_ID | IBY_F_T_CRDT_APPS_ALL_B |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_F_T_CRDT_APPS_ALL_TL_U1 | UNIQUE | APPS_TS_ARCHIVE |
CREDIT_APP_ID
LANGUAGE |
| IBY_F_T_CRDT_APPS_ALL_TL_N1 | NONUNIQUE | APPS_TS_ARCHIVE |
NAME
LANGUAGE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| CREDIT_APP_ID | NUMBER | (15) | Y | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| NAME | VARCHAR2 | (80) | ||
| DESCRIPTION | VARCHAR2 | (2000) | ||
| LANGUAGE | VARCHAR2 | (4) | Y | |
| SOURCE_LANG | VARCHAR2 | (4) | Y | |
| SECURITY_GROUP_ID | NUMBER |
IBY.IBY_F_T_CRDT_APPS_ALL_TL does not reference any database object
IBY.IBY_F_T_CRDT_APPS_ALL_TL is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_F_T_CRDT_APP_REVS.CREDIT_APP_ID | IBY_F_T_CRDT_APPS_ALL_B |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_F_T_CRDT_APP_REVS_U1 | UNIQUE | APPS_TS_ARCHIVE | REVISION_ID |
| IBY_F_T_CRDT_APP_REVS_N1 | NONUNIQUE | APPS_TS_ARCHIVE | CREDIT_APP_ID |
| IBY_F_T_CRDT_APP_REVS_N2 | NONUNIQUE | APPS_TS_ARCHIVE | REVISION_TYPE_CODE |
| IBY_F_T_CRDT_APP_REVS_N3 | NONUNIQUE | APPS_TS_ARCHIVE | USER_TYPE_CODE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| REVISION_ID | NUMBER | (15) | Y | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Application level record locking for three tier stateless applications |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| CREDIT_APP_ID | NUMBER | (15) | Y | |
| REVISION_XML_DOC_ID | NUMBER | (15) | ||
| CREDIT_APP_REV_NUM | NUMBER | |||
| REVISION_TYPE_CODE | VARCHAR2 | (30) | ||
| USER_ID | NUMBER | (15) | ||
| USER_TYPE_CODE | VARCHAR2 | (30) | ||
| SECURITY_GROUP_ID | NUMBER |
IBY.IBY_F_T_CRDT_APP_REVS does not reference any database object
IBY.IBY_F_T_CRDT_APP_REVS is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_F_T_CRDT_APP_ST_H.CREDIT_APP_ID | IBY_F_T_CRDT_APPS_ALL_B |
| IBY_F_T_CRDT_APP_ST_H.OLD_STATUS_ID | IBY_F_CRDT_APP_STATUS_B |
| IBY_F_T_CRDT_APP_ST_H.NEW_STATUS_ID | IBY_F_CRDT_APP_STATUS_B |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_F_T_CRDT_APP_ST_H_U1 | UNIQUE | APPS_TS_ARCHIVE | STATUS_HISTORY_ID |
| IBY_F_T_CRDT_APP_ST_H_N1 | NONUNIQUE | APPS_TS_ARCHIVE | CREDIT_APP_ID |
| IBY_F_T_CRDT_APP_ST_H_N2 | NONUNIQUE | APPS_TS_ARCHIVE | OLD_STATUS_ID |
| IBY_F_T_CRDT_APP_ST_H_N3 | NONUNIQUE | APPS_TS_ARCHIVE | NEW_STATUS_ID |
| IBY_F_T_CRDT_APP_ST_H_N4 | NONUNIQUE | APPS_TS_ARCHIVE | USER_TYPE_CODE |
| IBY_F_T_CRDT_APP_ST_H_N5 | NONUNIQUE | APPS_TS_ARCHIVE | CA_STATUS_EVENT_CODE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| STATUS_HISTORY_ID | NUMBER | (15) | Y | |
| REQUEST_ID | NUMBER | (15) | Request Identifier | |
| PROGRAM_APPLICATION_ID | NUMBER | (15) | Application Identifier of last concurrent program to update record | |
| PROGRAM_ID | NUMBER | (15) | Identifier of last concurrent program to update record | |
| PROGRAM_UPDATE_DATE | DATE | Last date concurrent program updated record | ||
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Application level record locking for three tier stateless applications |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| CREDIT_APP_ID | NUMBER | (15) | Y | |
| OLD_STATUS_ID | NUMBER | (15) | ||
| NEW_STATUS_ID | NUMBER | (15) | Y | |
| USER_ID | NUMBER | (15) | ||
| USER_TYPE_CODE | VARCHAR2 | (30) | ||
| CA_STATUS_EVENT_CODE | VARCHAR2 | (30) | ||
| CA_STATUS_EVENT_TIME | DATE | |||
| CA_STATUS_EVENT_DESC | VARCHAR2 | (2000) | ||
| SECURITY_GROUP_ID | NUMBER |
IBY.IBY_F_T_CRDT_APP_ST_H does not reference any database object
IBY.IBY_F_T_CRDT_APP_ST_H is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_F_T_EMAIL_NOTIF_LOG.CREDIT_APP_ID | IBY_F_T_CRDT_APPS_ALL_B |
| IBY_F_T_EMAIL_NOTIF_LOG.CREDIT_APP_GRNTR_ID | IBY_F_T_CA_GRNTRS_B |
| IBY_F_T_EMAIL_NOTIF_LOG.MSG_TEMPLATE_ID | IBY_G_MSG_TEMPLATES_B |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_F_T_EMAIL_NOTIF_LOG_U1 | UNIQUE | APPS_TS_ARCHIVE | EMAIL_NOTIF_LOG_ID |
| IBY_F_T_EMAIL_NOTIF_LOG_N1 | NONUNIQUE | APPS_TS_ARCHIVE | CREDIT_APP_ID |
| IBY_F_T_EMAIL_NOTIF_LOG_N2 | NONUNIQUE | APPS_TS_ARCHIVE | CREDIT_APP_GRNTR_ID |
| IBY_F_T_EMAIL_NOTIF_LOG_N3 | NONUNIQUE | APPS_TS_ARCHIVE | MSG_TEMPLATE_ID |
| IBY_F_T_EMAIL_NOTIF_LOG_N4 | NONUNIQUE | APPS_TS_ARCHIVE | ROLE_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| EMAIL_NOTIF_LOG_ID | NUMBER | (15) | Y | |
| REQUEST_ID | NUMBER | (15) | Request Identifier | |
| PROGRAM_APPLICATION_ID | NUMBER | (15) | Application Identifier of last concurrent program to update record | |
| PROGRAM_ID | NUMBER | (15) | Identifier of last concurrent program to update record | |
| PROGRAM_UPDATE_DATE | DATE | Last date concurrent program updated record | ||
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Application level record locking for three tier stateless applications |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| CREDIT_APP_ID | NUMBER | (15) | Y | |
| MSG_TEMPLATE_ID | NUMBER | (15) | Y | |
| CREDIT_APP_GRNTR_ID | NUMBER | (15) | ||
| WF_ITEM_KEY | VARCHAR2 | (240) | ||
| EMAIL_NOTIF_TIME | DATE | |||
| ROLE_NAME | VARCHAR2 | (320) | ||
| EMAIL_ADDRS | VARCHAR2 | (2000) | ||
| EMAIL_ADDR_COUNT | NUMBER | |||
| EMAIL_STATUS_CODE | VARCHAR2 | (30) | ||
| SECURITY_GROUP_ID | NUMBER |
IBY.IBY_F_T_EMAIL_NOTIF_LOG does not reference any database object
IBY.IBY_F_T_EMAIL_NOTIF_LOG is referenced by following:
| Description: | IBY_GEN_DOCS_PAYABLE serves as a template for source product tables or views from which Oracle Payables can import documents payable. |
|---|
IBY_GEN_DOCS_PAYABLE serves as a template for source product tables or views from which Oracle Payables can import documents payable.
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAY_PROC_TRXN_TYPE_CODE | VARCHAR2 | (100) | Y | Type of payment processing transaction or document |
| CALLING_APP_ID | NUMBER | (15) | Y | Source product Identifier |
| CALLING_APP_DOC_UNIQUE_REF1 | VARCHAR2 | (100) | Y | Source product's first unique document payable Identifier |
| CALLING_APP_DOC_UNIQUE_REF2 | VARCHAR2 | (100) | Source product's second unique document payable Identifier | |
| CALLING_APP_DOC_UNIQUE_REF3 | VARCHAR2 | (100) | Source product's third unique document payable Identifier | |
| CALLING_APP_DOC_UNIQUE_REF4 | VARCHAR2 | (100) | Source product's fourth unique document payable Identifier | |
| CALLING_APP_DOC_UNIQUE_REF5 | VARCHAR2 | (100) | Calling application's fifth unique document payable identifier | |
| CALLING_APP_DOC_REF_NUMBER | VARCHAR2 | (100) | Y | Reference number entered by user of the source product. Need not be unique |
| CALL_APP_PAY_SERVICE_REQ_CODE | VARCHAR2 | (255) | Y | Source product''s payment process request identifier. Since the source product''s Identifiers may be alphanumeric, even numeric document Identifiers are stored as VARCHAR2. |
| PAYMENT_FUNCTION | VARCHAR2 | (30) | Y | Function or purpose of the payment. Values from the lookup IBY_PAYMENT_FUNCTIONS include SUPPLIER_PAYMENT, CUSTOMER_REFUNDS, and others. |
| PAYMENT_DATE | DATE | Y | Payment date | |
| DOCUMENT_DATE | DATE | Y | Date of document | |
| DOCUMENT_TYPE | VARCHAR2 | (30) | Y | Type of document payable. Values from the IBY_DOCUMENT_TYPES lookup include INVOICE. |
| DOCUMENT_CURRENCY_CODE | VARCHAR2 | (10) | Y | Document currency code |
| DOCUMENT_AMOUNT | NUMBER | Y | Total amount in document currency | |
| PAYMENT_CURRENCY_CODE | VARCHAR2 | (10) | Y | Payment currency code |
| PAYMENT_AMOUNT | NUMBER | Y | Amount to be paid in payment currency | |
| PAYMENT_METHOD_CODE | VARCHAR2 | (30) | Y | Payment method Identifier |
| EXCLUSIVE_PAYMENT_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether this document payable corresponds to one payment. |
| PAYEE_PARTY_ID | NUMBER | (15) | Y | TCA party Identifier |
| PARTY_SITE_ID | NUMBER | (15) | Y | Payee party site Identifier |
| SUPPLIER_SITE_ID | NUMBER | (15) | Y | Supplier site Identifier |
| BENEFICIARY_PARTY | NUMBER | (15) | Beneficiary party, if payment is made through a third party | |
| LEGAL_ENTITY_ID | NUMBER | (15) | Y | Legal entity Identifier |
| ORG_ID | NUMBER | (15) | Y | Organization Identifier |
| ORG_TYPE | VARCHAR2 | (30) | Organization type. Values from the lookup IBY_ORGANIZATION_TYPES include Operating Unit, Business Group, and Legal Entity. | |
| ALLOW_REMOVING_DOCUMENT_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether this document can be removed from a payment or payment process request |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number | |
| ANTICIPATED_VALUE_DATE | DATE | Anticipated value date | ||
| PO_NUMBER | VARCHAR2 | (255) | Purchase order numbers to which this document is matched. If multiple purchase orders, value is comma delimited. | |
| DOCUMENT_DESCRIPTION | VARCHAR2 | (255) | Document description | |
| DOCUMENT_CURRENCY_TAX_AMOUNT | NUMBER | Tax amount in document currency | ||
| DOCUMENT_CURR_CHARGE_AMOUNT | NUMBER | Charge amount in document currency | ||
| AMOUNT_WITHHELD | NUMBER | Amount withheld in payment currency | ||
| PAYMENT_CURR_DISCOUNT_TAKEN | NUMBER | Discount taken in payment currency | ||
| DISCOUNT_DATE | DATE | Discount date | ||
| PAYMENT_DUE_DATE | DATE | Date on which the payment is made | ||
| PAYMENT_PROFILE_ID | NUMBER | (15) | Payment process profile Identifier | |
| INTERNAL_BANK_ACCOUNT_ID | NUMBER | (15) | Internal bank account Identifier | |
| EXTERNAL_BANK_ACCOUNT_ID | NUMBER | (15) | External bank account Identifier | |
| BANK_CHARGE_BEARER | VARCHAR2 | (30) | Bearer of bank charge cost. Bank charge bearers are defined as the lookup IBY_BANK_CHARGE_BEARER. | |
| INTEREST_RATE | NUMBER | Interest rate based on which this document payable was created if it is an interest invoice | ||
| PAYMENT_GROUPING_NUMBER | NUMBER | (15) | This attribute is used to link a set of documents payable. All documents payable that have the same payment grouping number are grouped into a single payment. | |
| PAYMENT_REASON_CODE | VARCHAR2 | (30) | Payment reason code | |
| PAYMENT_REASON_COMMENTS | VARCHAR2 | (240) | Free text field available for entering a reason for the payment | |
| SETTLEMENT_PRIORITY | VARCHAR2 | (30) | Priority with which the financial institution or payment system settles payment for this document. The available values for this column come from the FND lookup IBY_SETTLEMENT_PRIORITY. | |
| REMITTANCE_MESSAGE1 | VARCHAR2 | (150) | Remittance message for use in payment processing | |
| REMITTANCE_MESSAGE2 | VARCHAR2 | (150) | Remittance message for use in payment processing | |
| REMITTANCE_MESSAGE3 | VARCHAR2 | (150) | Remittance message for use in payment processing | |
| UNIQUE_REMITTANCE_IDENTIFIER | VARCHAR2 | (30) | Unique remittance Identifier provided by the payee | |
| URI_CHECK_DIGIT | VARCHAR2 | (2) | Unique remittance Identifier check digit | |
| DELIVERY_CHANNEL_CODE | VARCHAR2 | (30) | Delivery channel code | |
| PAYMENT_FORMAT_CODE | VARCHAR2 | (30) | Payment format code | |
| DOCUMENT_SEQUENCE_ID | NUMBER | Sequential numbering document sequence Identifier | ||
| DOCUMENT_SEQUENCE_VALUE | NUMBER | Sequence number of document payable | ||
| DOCUMENT_CATEGORY_CODE | VARCHAR2 | (30) | Sequential numbering document category | |
| BANK_ASSIGNED_REF_CODE | VARCHAR2 | (30) | Payment system-provided reference code for this document | |
| REMIT_TO_LOCATION_ID | NUMBER | (15) | Remit-To address Identifier | |
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | Descriptive Flexfield structure defining column | |
| ATTRIBUTE1 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE2 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE3 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE4 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE5 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE6 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE7 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE8 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE9 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE10 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE11 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE12 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE13 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE14 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE15 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ADDRESS_SOURCE | VARCHAR2 | (30) | Source of the address. Possible values from the lookup IBY_ADDRESS_SOURCE_TYPES include TCA and HR. | |
| EMPLOYEE_ADDRESS_CODE | VARCHAR2 | (30) | Type of address. Possible values include HOME and OFFICE. | |
| EMPLOYEE_PERSON_ID | NUMBER | (15) | Employee person Identifier | |
| EMPLOYEE_PAYMENT_FLAG | VARCHAR2 | (1) | Y or N flag indicating whether the payment is of the employee payment type. | |
| EMPLOYEE_ADDRESS_ID | NUMBER | (15) | HR Identifier of the address |
IBY.IBY_GEN_DOCS_PAYABLE does not reference any database object
IBY.IBY_GEN_DOCS_PAYABLE is referenced by following:
| Description: | IBY_GEN_DOCUMENT_LINES serves as a template for source product tables or views from which Oracle Payables can import documents payable. |
|---|
IBY_GEN_DOCUMENT_LINES serves as a template for source product tables or views from which Oracle Payables can import documents payable.
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| CALLING_APP_ID | NUMBER | (15) | Y | Source product Identifier |
| CALLING_APP_DOCUMENT_LINE_CODE | VARCHAR2 | (255) | Y | Source product''s document line Identifier. Since document line Identifiers may be alphanumeric, even numeric document Identifiers are stored as VARCHAR2. |
| CALLING_APP_DOC_UNIQUE_REF1 | VARCHAR2 | (100) | Y | Source product''s first unique document payable Identifier |
| CALLING_APP_DOC_UNIQUE_REF2 | VARCHAR2 | (100) | Source product''s second unique document payable Identifier | |
| CALLING_APP_DOC_UNIQUE_REF3 | VARCHAR2 | (100) | Source product''s third unique document payable Identifier | |
| CALLING_APP_DOC_UNIQUE_REF4 | VARCHAR2 | (100) | Source product''s fourth unique document payable Identifier | |
| CALLING_APP_DOC_UNIQUE_REF5 | VARCHAR2 | (100) | Source product''s fifth unique document payable Identifier | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| PO_NUMBER | VARCHAR2 | (255) | Purchase order numbers to which this document line is matched. If multiple purchase orders, value is comma delimited. | |
| LINE_NUMBER | NUMBER | (15) | Line number | |
| LINE_TYPE | VARCHAR2 | (30) | Line type | |
| LINE_NAME | VARCHAR2 | (100) | Line name | |
| LINE_AMOUNT | NUMBER | Line amount, in document currency | ||
| DESCRIPTION | VARCHAR2 | (255) | Line description | |
| UNIT_PRICE | NUMBER | Unit price | ||
| QUANTITY | NUMBER | Quantity | ||
| UNIT_OF_MEASURE | VARCHAR2 | (100) | Unit of measure |
IBY.IBY_GEN_DOCUMENT_LINES does not reference any database object
IBY.IBY_GEN_DOCUMENT_LINES is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_F_T_EMAIL_NOTIF_LOG.MSG_TEMPLATE_ID | IBY_G_MSG_TEMPLATES_B |
| IBY_G_MSG_TEMPLATES_TL.MSG_TEMPLATE_ID | IBY_G_MSG_TEMPLATES_B |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_G_MSG_TEMPLATES_B_U1 | UNIQUE | APPS_TS_ARCHIVE | MSG_TEMPLATE_ID |
| IBY_G_MSG_TEMPLATES_B_U2 | UNIQUE | APPS_TS_ARCHIVE |
MSG_TEMPLATE_NAME
MSG_TEMPLATE_VERSION |
| IBY_G_MSG_TEMPLATES_B_N1 | NONUNIQUE | APPS_TS_ARCHIVE | MSG_TYPE_CODE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| MSG_TEMPLATE_ID | NUMBER | (15) | Y | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Application level record locking for three tier stateless applications |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| MSG_TEMPLATE_NAME | VARCHAR2 | (240) | Y | |
| MSG_TEMPLATE_NUMBER | NUMBER | (15) | ||
| MSG_TEMPLATE_VERSION | NUMBER | Y | ||
| MSG_TYPE_CODE | VARCHAR2 | (240) | Y | |
| FROZEN_FLAG | VARCHAR2 | (1) | ||
| SEEDED_FLAG | VARCHAR2 | (1) | ||
| START_DATE_ACTIVE | DATE | |||
| END_DATE_ACTIVE | DATE | |||
| SECURITY_GROUP_ID | NUMBER | |||
| ATTRIBUTE_CATEGORY | VARCHAR2 | (240) | ||
| ATTRIBUTE1 | VARCHAR2 | (240) | ||
| ATTRIBUTE2 | VARCHAR2 | (240) | ||
| ATTRIBUTE3 | VARCHAR2 | (240) | ||
| ATTRIBUTE4 | VARCHAR2 | (240) | ||
| ATTRIBUTE5 | VARCHAR2 | (240) | ||
| ATTRIBUTE6 | VARCHAR2 | (240) | ||
| ATTRIBUTE7 | VARCHAR2 | (240) | ||
| ATTRIBUTE8 | VARCHAR2 | (240) | ||
| ATTRIBUTE9 | VARCHAR2 | (240) | ||
| ATTRIBUTE10 | VARCHAR2 | (240) | ||
| ATTRIBUTE11 | VARCHAR2 | (240) | ||
| ATTRIBUTE12 | VARCHAR2 | (240) | ||
| ATTRIBUTE13 | VARCHAR2 | (240) | ||
| ATTRIBUTE14 | VARCHAR2 | (240) | ||
| ATTRIBUTE15 | VARCHAR2 | (240) |
IBY.IBY_G_MSG_TEMPLATES_B does not reference any database object
IBY.IBY_G_MSG_TEMPLATES_B is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_G_MSG_TEMPLATES_TL.MSG_TEMPLATE_ID | IBY_G_MSG_TEMPLATES_B |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_G_MSG_TEMPLATES_TL_U1 | UNIQUE | APPS_TS_ARCHIVE |
MSG_TEMPLATE_ID
LANGUAGE |
| IBY_G_MSG_TEMPLATES_TL_N1 | NONUNIQUE | APPS_TS_ARCHIVE |
NAME
LANGUAGE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| MSG_TEMPLATE_ID | NUMBER | (15) | Y | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| MESSAGE_TEMPLATE | VARCHAR2 | (2000) | ||
| NAME | VARCHAR2 | (80) | Y | |
| DESCRIPTION | VARCHAR2 | (2000) | ||
| LANGUAGE | VARCHAR2 | (4) | Y | |
| SOURCE_LANG | VARCHAR2 | (4) | Y |
IBY.IBY_G_MSG_TEMPLATES_TL does not reference any database object
IBY.IBY_G_MSG_TEMPLATES_TL is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_G_ST_TRANSITIONS.FROM_STATUS_ID | IBY_F_CRDT_APP_STATUS_B |
| IBY_G_ST_TRANSITIONS.TO_STATUS_ID | IBY_F_CRDT_APP_STATUS_B |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_G_ST_TRANSITIONS_U1 | UNIQUE | APPS_TS_ARCHIVE | TRANSITION_ID |
| IBY_G_ST_TRANSITIONS_N1 | NONUNIQUE | APPS_TS_ARCHIVE | FROM_STATUS_ID |
| IBY_G_ST_TRANSITIONS_N2 | NONUNIQUE | APPS_TS_ARCHIVE | TO_STATUS_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| TRANSITION_ID | NUMBER | (15) | Y | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Application level record locking for three tier stateless applications |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| FROM_STATUS_ID | NUMBER | (15) | Y | |
| TO_STATUS_ID | NUMBER | (15) | Y | |
| RULE_CATEGORY_CODE | VARCHAR2 | (30) | Y | |
| ENABLED_FLAG | VARCHAR2 | (1) | Y | |
| SECURITY_GROUP_ID | NUMBER | |||
| ATTRIBUTE_CATEGORY | VARCHAR2 | (240) | ||
| ATTRIBUTE1 | VARCHAR2 | (240) | ||
| ATTRIBUTE2 | VARCHAR2 | (240) | ||
| ATTRIBUTE3 | VARCHAR2 | (240) | ||
| ATTRIBUTE4 | VARCHAR2 | (240) | ||
| ATTRIBUTE5 | VARCHAR2 | (240) | ||
| ATTRIBUTE6 | VARCHAR2 | (240) | ||
| ATTRIBUTE7 | VARCHAR2 | (240) | ||
| ATTRIBUTE8 | VARCHAR2 | (240) | ||
| ATTRIBUTE9 | VARCHAR2 | (240) | ||
| ATTRIBUTE10 | VARCHAR2 | (240) | ||
| ATTRIBUTE11 | VARCHAR2 | (240) | ||
| ATTRIBUTE12 | VARCHAR2 | (240) | ||
| ATTRIBUTE13 | VARCHAR2 | (240) | ||
| ATTRIBUTE14 | VARCHAR2 | (240) | ||
| ATTRIBUTE15 | VARCHAR2 | (240) |
IBY.IBY_G_ST_TRANSITIONS does not reference any database object
IBY.IBY_G_ST_TRANSITIONS is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_G_T_MESSAGES.TRXN_SUMMARY_ID | IBY_TRXN_SUMMARIES_ALL |
| IBY_G_T_MESSAGES.MESSAGE_XML_ID | IBY_TRXN_DOCUMENTS |
| IBY_G_T_MESSAGES.CREDIT_APP_ID | IBY_F_T_CRDT_APPS_ALL_B |
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_G_T_MSG_REQ_LOG.MESSAGE_ID | IBY_G_T_MESSAGES |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_G_T_MESSAGES_U1 | UNIQUE | APPS_TS_ARCHIVE | MESSAGE_ID |
| IBY_G_T_MESSAGES_N1 | NONUNIQUE | APPS_TS_ARCHIVE | TRXN_SUMMARY_ID |
| IBY_G_T_MESSAGES_N2 | NONUNIQUE | APPS_TS_ARCHIVE | MESSAGE_CAT_CODE |
| IBY_G_T_MESSAGES_N3 | NONUNIQUE | APPS_TS_ARCHIVE | MESSAGE_TYPE_CODE |
| IBY_G_T_MESSAGES_N4 | NONUNIQUE | APPS_TS_ARCHIVE | MESSAGE_XML_ID |
| IBY_G_T_MESSAGES_N5 | NONUNIQUE | APPS_TS_ARCHIVE | CREDIT_APP_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| MESSAGE_ID | NUMBER | (15) | Y | |
| REQUEST_ID | NUMBER | (15) | Request Identifier | |
| PROGRAM_APPLICATION_ID | NUMBER | (15) | Application Identifier of last concurrent program to update record | |
| PROGRAM_ID | NUMBER | (15) | Identifier of last concurrent program to update record | |
| PROGRAM_UPDATE_DATE | DATE | Last date concurrent program updated record | ||
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Application level record locking for three tier stateless applications |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| TRXN_SUMMARY_ID | NUMBER | Y | ||
| CREDIT_APP_ID | NUMBER | (15) | ||
| MESSAGE_XML_ID | NUMBER | (15) | ||
| MESSAGE_CAT_CODE | VARCHAR2 | (30) | ||
| MESSAGE_TYPE_CODE | VARCHAR2 | (30) | ||
| MESSAGE_TIME | DATE | |||
| SECURITY_GROUP_ID | NUMBER |
IBY.IBY_G_T_MESSAGES does not reference any database object
IBY.IBY_G_T_MESSAGES is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_G_T_MSG_REQ_LOG.MESSAGE_ID | IBY_G_T_MESSAGES |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_G_T_MSG_REQ_LOG_U1 | UNIQUE | APPS_TS_ARCHIVE | MSG_REQ_LOG_ID |
| IBY_G_T_MSG_REQ_LOG_N1 | NONUNIQUE | APPS_TS_ARCHIVE | MESSAGE_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| MSG_REQ_LOG_ID | NUMBER | (15) | Y | |
| REQUEST_ID | NUMBER | (15) | Request Identifier | |
| PROGRAM_APPLICATION_ID | NUMBER | (15) | Application Identifier of last concurrent program to update record | |
| PROGRAM_ID | NUMBER | (15) | Identifier of last concurrent program to update record | |
| PROGRAM_UPDATE_DATE | DATE | Last date concurrent program updated record | ||
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Application level record locking for three tier stateless applications |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| MESSAGE_ID | NUMBER | (15) | Y | |
| MSG_REQ_COUNT | NUMBER | Y | ||
| MSG_REQ_TIME | DATE | |||
| EXT_SYSTEM_RESP_CODE | VARCHAR2 | (30) | ||
| SECURITY_GROUP_ID | NUMBER |
IBY.IBY_G_T_MSG_REQ_LOG does not reference any database object
IBY.IBY_G_T_MSG_REQ_LOG is referenced by following:
| Description: |
|---|
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_HOOK_DOCS_IN_PMT_T_N1 | NONUNIQUE |
DOCUMENT_PAYABLE_ID
DONT_PAY_FLAG |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYMENT_ID | NUMBER | (15) | Y | |
| DOCUMENT_PAYABLE_ID | NUMBER | (15) | Y | |
| CALLING_APP_ID | NUMBER | (15) | Y | |
| CALLING_APP_DOC_UNIQUE_REF1 | NUMBER | (15) | Y | |
| CALLING_APP_DOC_UNIQUE_REF2 | NUMBER | (15) | ||
| CALLING_APP_DOC_UNIQUE_REF3 | NUMBER | (15) | ||
| CALLING_APP_DOC_UNIQUE_REF4 | NUMBER | (15) | ||
| CALLING_APP_DOC_UNIQUE_REF5 | NUMBER | (15) | ||
| DOCUMENT_AMOUNT | NUMBER | Y | ||
| DOCUMENT_CURRENCY_CODE | VARCHAR2 | (10) | Y | |
| AMOUNT_WITHHELD | NUMBER | |||
| DONT_PAY_FLAG | VARCHAR2 | (1) | ||
| DONT_PAY_REASON_CODE | VARCHAR2 | (30) | ||
| DONT_PAY_DESCRIPTION | VARCHAR2 | (255) | ||
| PAY_PROC_TRXN_TYPE_CODE | VARCHAR2 | (100) | Y | |
| INTERNAL_BANK_ACCOUNT_ID | NUMBER | (15) | Y | |
| EXT_PAYEE_ID | NUMBER | (15) | Y | |
| PAYEE_PARTY_ID | NUMBER | (15) | ||
| PARTY_SITE_ID | NUMBER | (15) | ||
| SUPPLIER_SITE_ID | NUMBER | (15) | ||
| ORG_ID | NUMBER | (15) | ||
| ORG_TYPE | VARCHAR2 | (30) | ||
| EXTERNAL_BANK_ACCOUNT_ID | NUMBER | (15) | ||
| PAYMENT_CURR_DISCOUNT_TAKEN | NUMBER | |||
| CREATED_BY | NUMBER | (15) | Y | |
| CREATION_DATE | DATE | Y | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| LAST_UPDATE_DATE | DATE | Y | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y |
IBY.IBY_HOOK_DOCS_IN_PMT_T does not reference any database object
IBY.IBY_HOOK_DOCS_IN_PMT_T is referenced by following:
| Description: |
|---|
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_HOOK_PAYMENTS_T_N1 | NONUNIQUE | PAYMENT_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| CALLING_APP_ID | NUMBER | (15) | Y | |
| CALL_APP_PAY_SERVICE_REQ_CODE | VARCHAR2 | (255) | Y | |
| PAYMENT_SERVICE_REQUEST_ID | NUMBER | (15) | Y | |
| PAYMENT_ID | NUMBER | (15) | Y | |
| PAYMENT_AMOUNT | NUMBER | |||
| PAYMENT_CURRENCY_CODE | VARCHAR2 | (10) | Y | |
| DONT_PAY_FLAG | VARCHAR2 | (1) | ||
| DONT_PAY_REASON_CODE | VARCHAR2 | (30) | ||
| DONT_PAY_DESCRIPTION | VARCHAR2 | (255) | ||
| INTERNAL_BANK_ACCOUNT_ID | NUMBER | (15) | Y | |
| EXT_PAYEE_ID | NUMBER | (15) | Y | |
| PAYEE_PARTY_ID | NUMBER | (15) | ||
| PARTY_SITE_ID | NUMBER | (15) | ||
| SUPPLIER_SITE_ID | NUMBER | (15) | ||
| ORG_ID | NUMBER | (15) | ||
| ORG_TYPE | VARCHAR2 | (30) | ||
| EXTERNAL_BANK_ACCOUNT_ID | NUMBER | (15) | ||
| DISCOUNT_AMOUNT_TAKEN | NUMBER | |||
| PAYMENT_DATE | DATE | |||
| BANK_CHARGE_AMOUNT | NUMBER | |||
| CREATED_BY | NUMBER | (15) | Y | |
| CREATION_DATE | DATE | Y | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| LAST_UPDATE_DATE | DATE | Y | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y |
IBY.IBY_HOOK_PAYMENTS_T does not reference any database object
IBY.IBY_HOOK_PAYMENTS_T is referenced by following:
| Description: | IBY_INSTRHOLDER stores the information about the holder of the instrment. A payment instrument can be held by different users or payees or payers. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_INSTRHOLDER.INSTRID | IBY_CREDITCARD |
| IBY_INSTRHOLDER.INSTRID | IBY_BANKACCT |
IBY_INSTRHOLDER stores the information about the holder of the instrment. A payment instrument can be held by different users or payees or payers.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_INSTRHOLDER_INSTRID_U1 | UNIQUE | APPS_TS_TX_IDX | INSTRID |
| IBY_INSTRHOLDER_OWNERID_N1 | NONUNIQUE | APPS_TS_TX_IDX | OWNERID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| INSTRID | NUMBER | Y | Instrument identifier, FK to instrument tables (iby_creditcard, iby_bankacct). | |
| INSTRTYPE | VARCHAR2 | (30) | Y | Instrument type |
| OWNERID | VARCHAR2 | (80) | Y | referes to ID of the payee or payer of the instrument. For AR-BR integration, the ownerid for PAYER type is passed from AR as ARcustomer name. |
| OWNERTYPE | VARCHAR2 | (20) | Y | refers to either payee or payer. Used to be hard-coded as "USER", which is used equivalently as "PAYER". For AR-BR integration, it will be either "PAYER" or "PAYEE" |
| ACTIVESTATUS | NUMBER | (1) | referes to whether the instrument is active or not in the system | |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column - date when a user last updated this row. | |
| LAST_UPDATED_BY | NUMBER | Y | Standard who column - user who last updated this row (foreign key to FND_USER.USER_ID). | |
| CREATION_DATE | DATE | Y | Standard who column - date when this row was created. | |
| CREATED_BY | NUMBER | Y | Standard who column - user who created this row (foreign key to FND_USER.USER_ID). | |
| LAST_UPDATE_LOGIN | NUMBER | Standard who column - operating system login of user who last updated this row (foreign key to FND_LOGINS.LOGIN_ID). | ||
| OBJECT_VERSION_NUMBER | NUMBER | Y | This column is used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. | |
| SECURITY_GROUP_ID | NUMBER | Used in hosted environments | ||
| OWNERADDRESSID | NUMBER | (15) | Foreign key to HZ_LOCATIONS. Stores the BILL_TO address of the payee or payer. Added for AR-BR integration |
IBY.IBY_INSTRHOLDER does not reference any database object
IBY.IBY_INSTRHOLDER is referenced by following:
| Description: | IBY_INSTRUCT_SOURCE_APPS stores a list of source products that submitted documents to be paid in each payment instruction. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_INSTRUCT_SOURCE_APPS.PAYMENT_INSTRUCTION_ID | IBY_PAY_INSTRUCTIONS_ALL |
IBY_INSTRUCT_SOURCE_APPS stores a list of source products that submitted documents to be paid in each payment instruction.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_INSTRUCT_SOURCE_APPS_U1 | UNIQUE | APPS_TS_TX_IDX |
PAYMENT_INSTRUCTION_ID
CALLING_APP_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYMENT_INSTRUCTION_ID | NUMBER | (15) | Y | System generated primary key |
| CALLING_APP_ID | NUMBER | (15) | Y | Source product identifier |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column |
IBY.IBY_INSTRUCT_SOURCE_APPS does not reference any database object
IBY.IBY_INSTRUCT_SOURCE_APPS is referenced by following:
| Description: | IBY_INSTR_CREATION_RULES specifies how payments are grouped into payment instructions. Payment instructions are always grouped by internal bank account and payment process profile but additional items stored in this table can be added for f |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_INSTR_CREATION_RULES.SYSTEM_PROFILE_CODE | IBY_SYS_PMT_PROFILES_B |
IBY_INSTR_CREATION_RULES specifies how payments are grouped into payment instructions. Payment instructions are always grouped by internal bank account and payment process profile but additional items stored in this table can be added for further grouping. With more grouping rules, there are likely to be more, but smaller, payment instructions. This table corresponds to the Payment Instruction Creation tab of the Update Payment Process Profile page.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_INSTR_CREATION_RULES_U1 | UNIQUE | APPS_TS_TX_IDX |
SYSTEM_PROFILE_CODE
ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| SYSTEM_PROFILE_CODE | VARCHAR2 | (100) | Y | Unique primary key |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number | |
| GROUP_BY_PAYMENT_DATE | VARCHAR2 | (1) | Y | Y or N flag specifying whether payments are grouped into payment instructions by payment date |
| GROUP_BY_PAYMENT_CURRENCY | VARCHAR2 | (1) | Y | Y or N flag specifying whether payments are grouped into payment instructions by payment currency. If the processing type on the payment process profile is Printed, this flag is automatically set to Y and cannot be overridden. |
| GROUP_BY_INTERNAL_BANK_ACCOUNT | VARCHAR2 | (1) | Y or N flag specifying whether payments are grouped into payment instructions by internal bank account. If the processing type on the payment process profile is Printed, this flag is automatically set to Y and cannot be overridden. | |
| GROUP_BY_MAX_PAYMENTS_FLAG | VARCHAR2 | (1) | Y | Y or N flag that indicates whether the system limits the number of payments in a payment instruction |
| GROUP_BY_PAY_SERVICE_REQUEST | VARCHAR2 | (1) | Y | Y or N flag specifying whether payments are grouped into payment instructions by payment process request |
| GROUP_BY_LEGAL_ENTITY | VARCHAR2 | (1) | Y | Y or N flag specifying whether payments are grouped into payment instructions by the first party legal entity |
| GROUP_BY_BILL_PAYABLE | VARCHAR2 | (1) | Y | Y or N flag specifying whether payments are grouped into payment instructions based on bill payable flag setting on the payments |
| GROUP_BY_ORGANIZATION | VARCHAR2 | (1) | Y | Y or N flag specifying whether payments are grouped into payment instructions by the first party organization |
| GROUP_BY_MAX_INSTRUCTION_FLAG | VARCHAR2 | (1) | Y | Y or N flag specifying whether there is a limit on the total payment amount when payment instructions are created. This value is set to Y when a value is specified in the MAX_AMOUNT_PER_INSTR_VALUE column. |
| GROUP_BY_PAYMENT_FUNCTION | VARCHAR2 | (1) | Y | Y or N flag specifying whether payments are grouped by the payment function |
| GROUP_BY_PAYMENT_REASON | VARCHAR2 | (1) | Y | Y or N flag specifying whether payments are grouped by the payment reason |
| GROUP_BY_RFC | VARCHAR2 | (1) | Y | Y or N flag specifying whether payments are grouped by the RFC, that is, regional finance center Identifier |
| MAX_PAYMENTS_PER_INSTRUCTION | NUMBER | (15) | Maximum number of payments that can be included in a payment instruction. When a value exists in this column, the Create Payment Instructions program uses it as one of its rules for building payment instructions. | |
| MAX_AMOUNT_PER_INSTR_VALUE | NUMBER | (15) | Maximum total amount for which a payment instruction can be created. When a value exists in this column, the Create Payment Instructions program uses it as one of its rules for building payment instructions. | |
| MAX_AMOUNT_PER_INSTR_CURR_CODE | VARCHAR2 | (10) | Currency in which the maximum total amount per payment instruction is calculated | |
| MAX_AMOUNT_FX_RATE_TYPE | VARCHAR2 | (30) | Exchange rate type used to compare the payment instruction total amount to the maximum total amount allowed. Types are defined in the General Ledger currency exchange rate type lookups table. These include CORPORATE, SPOT, and DAILY. | |
| SORT_OPTION_1 | VARCHAR2 | (30) | Primary column by which payments in a payment instruction are sorted. Values from the lookup IBY_PAYMENT_SORT_OPTIONS include PAYEE_NAME, PAYEE_NUMBER, and others. | |
| SORT_ORDER_1 | VARCHAR2 | (30) | Order in which the primary sorting occurs. Values from the lookup IBY_PAYMENT_SORT_ORDERS include ASCENDING and DESCENDING. | |
| SORT_OPTION_2 | VARCHAR2 | (30) | Second column by which payments in a payment instruction are sorted. Values from the lookup IBY_PAYMENT_SORT_OPTIONS include PAYEE_NAME, PAYEE_NUMBER, and others. | |
| SORT_ORDER_2 | VARCHAR2 | (30) | Order in which the secondary sorting occurs. Values from the lookup IBY_PAYMENT_SORT_ORDERS include ASCENDING and DESCENDING. | |
| SORT_OPTION_3 | VARCHAR2 | (30) | Third column by which payments in a payment instruction are sorted. Values from the lookup IBY_PAYMENT_SORT_OPTIONS include PAYEE_NAME, PAYEE_NUMBER, and others. | |
| SORT_ORDER_3 | VARCHAR2 | (30) | Order in which the tertiary sorting occurs. Values from the lookup IBY_PAYMENT_SORT_ORDERS include ASCENDING and DESCENDING. | |
| GROUP_BY_PAYMENT_METHOD | VARCHAR2 | (1) | Y or N specifying whether payments are grouped into payment instructions based on payment method | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_INSTR_CREATION_RULES does not reference any database object
IBY.IBY_INSTR_CREATION_RULES is referenced by following:
| Description: | IBY_INTERMEDIARY_ACCTS defines intermediary bank account information. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_INTERMEDIARY_ACCTS.BANK_ACCT_ID | IBY_EXT_BANK_ACCOUNTS |
| IBY_INTERMEDIARY_ACCTS.INTERNAL_BANK_ACCOUNT_ID | CE_BANK_ACCOUNTS |
IBY_INTERMEDIARY_ACCTS defines intermediary bank account information.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_INTERMEDIARY_ACCTS_U1 | UNIQUE | APPS_TS_TX_IDX | INTERMEDIARY_ACCT_ID |
| IBY_INTERMEDIARY_ACCTS_N1 | NONUNIQUE | APPS_TS_TX_IDX | BANK_ACCT_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| INTERMEDIARY_ACCT_ID | NUMBER | (15) | Y | Intermediary Bank Account Identifier |
| BANK_ACCT_ID | NUMBER | (15) | Foreign key to IBY_EXT_BANK_ACCOUNTS.EXT_BANK_ACCOUNT_ID. The external bank account that uses the intermediary bank account | |
| INTERNAL_BANK_ACCOUNT_ID | NUMBER | (15) | Internal Bank Account Identifier | |
| COUNTRY_CODE | VARCHAR2 | (2) | Country code | |
| BANK_NAME | VARCHAR2 | (360) | Bank name | |
| CITY | VARCHAR2 | (60) | City | |
| BANK_CODE | VARCHAR2 | (30) | Bank code | |
| BRANCH_NUMBER | VARCHAR2 | (30) | Branch Number | |
| BIC | VARCHAR2 | (30) | Bank Identification Code (Swift Code) | |
| ACCOUNT_NUMBER | VARCHAR2 | (100) | Bank account number | |
| CHECK_DIGITS | VARCHAR2 | (30) | Check digits | |
| IBAN | VARCHAR2 | (50) | International Bank Account Number | |
| COMMENTS | VARCHAR2 | (240) | Comments | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. |
IBY.IBY_INTERMEDIARY_ACCTS does not reference any database object
IBY.IBY_INTERMEDIARY_ACCTS is referenced by following:
| Description: | IBY_INTERNAL_PAYERS_ALL stores payment-related attributes for the funds disbursement payment process for all first party payers. These attributes control the flow of payments. |
|---|
IBY_INTERNAL_PAYERS_ALL stores payment-related attributes for the funds disbursement payment process for all first party payers. These attributes control the flow of payments.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_INTERNAL_PAYERS_ALL_U1 | UNIQUE | APPS_TS_TX_IDX |
INT_PAYER_ID
ZD_EDITION_NAME |
| IBY_INTERNAL_PAYERS_ALL_N1 | NONUNIQUE | APPS_TS_TX_IDX |
ORG_ID
ORG_TYPE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| INT_PAYER_ID | NUMBER | (15) | Y | System generated primary key |
| PAYMENT_METHOD_AT_PAYEE_FLAG | VARCHAR2 | (1) | Y | Stores the Allow Payee Override system option. This is a Y or N flag indicating whether defaults for the payment method attribute can be set at the payee or payee site levels. The defaults at payee or payee site levels override the ones set by defaulting rules. If set to N, any defaults previously set at the payee or payee site levels are ignored. There will be no override and the defaults are determined by the defaulting rules only. |
| DOCUMENT_REJECTION_LEVEL_CODE | VARCHAR2 | (30) | Y | Specifies what is rejected if a document payable fails validation. Values from the IBY_DOCUMENT_REJECTION_LEVELS lookup include REQUEST, PAYEE, and DOCUMENT. |
| PAYMENT_REJECTION_LEVEL_CODE | VARCHAR2 | (30) | Y | Specifies how much of a payment process request is rejected if a payment fails validation. Values from the IBY_PAYMENT_REJECTION_LEVELS lookup include REQUEST, PAYMENT, and NONE. |
| REQUIRE_PROP_PMTS_REVIEW_FLAG | VARCHAR2 | (1) | Y | Flag indicating whether Payments should stop the payment creation flow to allow an administrator to review and modify proposed payments before grouping them into payment instructions. Values from the lookup IBY_PROPOSED_PMTS_REVIEW_CODES include Y and N. |
| ALLOW_EXT_ACCT_OVERRIDE_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether the external bank account can be overridden |
| EXCLUSIVE_PAYMENT_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether each document payable corresponds to one payment. The value in this column is a default for new payees. |
| SAVE_PAYMENT_FILE_IN_DB | VARCHAR2 | (1) | Y | Y or N flag indicating whether Oracle Payments saves a copy of the formatted payment instruction file in the database |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number | |
| ORG_ID | NUMBER | (15) | Organization Identifier | |
| ORG_TYPE | VARCHAR2 | (30) | Organization type. Values from the lookup IBY_ORGANIZATION_TYPES include Operating Unit, Business Group, and Legal Entity. | |
| BANK_CHARGE_BEARER | VARCHAR2 | (30) | Bearer of bank charge cost. Bank charge bearers are defined as the lookup IBY_BANK_CHARGE_BEARER. | |
| PPR_REPORT_FORMAT | VARCHAR2 | (60) | Format to be used for the Payment Process Request Status Report. Set in the Disbursement System Options user interface page | |
| AUTOMATIC_PPR_REPORT_SUBMIT | VARCHAR2 | (1) | Y or N flag represented by the Automatically Submit at Payment Process Request Completion checkbox on the Disbursement System Options user interface page | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_INTERNAL_PAYERS_ALL does not reference any database object
IBY.IBY_INTERNAL_PAYERS_ALL is referenced by following:
| Description: | This table stores information pertaining to the payment amount risk factor involved in the payment request. A payment request that has huge amount is possibly a fraudulent payment. But the value of the amount varies from business to busines |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_IRF_PMT_AMOUNT.PAYEEID | IBY_PAYEE |
IBY_IRF_PMT_AMOUNT stores information pertaining to the payment amount risk factor involved in the payment request. A payment request that has a huge amount is possibly a fraudulent payment. The value of the payment amount risk factor varies from business to business.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_IRF_PMT_AMOUNT_SEQ_ID_U1 | UNIQUE | APPS_TS_TX_IDX |
PAYEEID
SEQ ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| LOWER_LIMIT | NUMBER | Lower limit of payment amount. Customer payment amount is equal to or greater then the lower limit. | ||
| SEQ | NUMBER | (15) | Y | Sequence |
| UPPER_LIMIT | NUMBER | Upper limit of payment amount. Customer payment amount is less than or equal to the upper limit. | ||
| SCORE | VARCHAR2 | (30) | Y | LOV of ranges of possible risk scores |
| PAYEEID | VARCHAR2 | (80) | Identifier of the payee passed by electronic commerce application | |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Used for locking purposes that subsequently allows for checking if there is old data on the screen compared to what is in the database. The situation occurs when the HTML application is a stateless application. | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| SECURITY_GROUP_ID | NUMBER | Used in hosted environments | ||
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_IRF_PMT_AMOUNT does not reference any database object
IBY.IBY_IRF_PMT_AMOUNT is referenced by following:
| Description: | This table stores information pertaining to the payment frequency risk factor. It basically has information about the frequency of purchase in the given time frame(duration). This risk fatcor is associated with a risk score - low and high. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_IRF_PMT_FREQUENCY.PAYEEID | IBY_PAYEE |
IBY_IRF_PMT_FREQUENCY stores information pertaining to the payment frequency risk factor. This table contains information about the frequency of purchase in a given time frame. This risk factor is associated with a risk score of low or high.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_IRF_PMT_FREQUENCY_PAYEE_U1 | UNIQUE | APPS_TS_TX_IDX |
FREQUENCY
DURATION_TYPE DURATION PAYEEID ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| DURATION | NUMBER | (15) | Y | Number of days, weeks, months, or years |
| DURATION_TYPE | VARCHAR2 | (15) | Y | Number of days or weeks |
| FREQUENCY | NUMBER | Y | Number of purchases made during the specified duration | |
| PAYEEID | VARCHAR2 | (80) | Identifier of the payee passed by electronic commerce application | |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Used for locking purposes that subsequently allows for checking if there is old data on the screen compared to what is in the database. The situation occurs when the HTML application is a stateless application. | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| SECURITY_GROUP_ID | NUMBER | Used in hosted environments | ||
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_IRF_PMT_FREQUENCY does not reference any database object
IBY.IBY_IRF_PMT_FREQUENCY is referenced by following:
| Description: | This table stores information pertaining to the payment history risk factor. The merchant can set up different time ranges which he considers risky. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_IRF_PMT_HISTORY.PAYEEID | IBY_PAYEE |
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_IRF_PMT_HIST_RANGE.PAYMENT_HIST_ID | IBY_IRF_PMT_HISTORY |
IBY_IRF_PMT_HISTORY stores information pertaining to the payment history risk factor. The merchant can set up different time ranges that he considers risky.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_IRF_PMT_HISTORY_ID_U1 | UNIQUE | APPS_TS_TX_IDX |
ID
ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ID | NUMBER | (15) | Y | System-generated unique identifier |
| DURATION | NUMBER | (15) | Y | Number of months, years |
| DURATION_TYPE | VARCHAR2 | (15) | Y | Month, year |
| PAYEEID | VARCHAR2 | (80) | Identifier of the payee passed by electronic commerce application | |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Used for locking purposes that subsequently allows for checking if there is old data on the screen compared to what is in the database. The situation occurs when the HTML application is a stateless application. | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| SECURITY_GROUP_ID | NUMBER | Used in hosted environments | ||
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_IRF_PMT_HISTORY does not reference any database object
IBY.IBY_IRF_PMT_HISTORY is referenced by following:
| Description: | This table stores the frequency ranges information pertaining to the payment history risk factor. The customer can setup multiple frequency ranges for a specific duration. During Risk Factor evaluation the merchant can setup risk scores (lo |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_IRF_PMT_HIST_RANGE.PAYMENT_HIST_ID | IBY_IRF_PMT_HISTORY |
IBY_IRF_PMT_HIST_RANGE stores the frequency ranges pertaining to the payment history risk factor. The customer can set up multiple frequency ranges for a specific duration. During risk factor evaluation, the merchant can set up risk scores of low, medium, or high for multiple frequency ranges of low range and high range.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_IRF_PMT_HIST_RNG_ID_SEQ_U1 | UNIQUE | APPS_TS_TX_IDX |
PAYMENT_HIST_ID
SEQ ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYMENT_HIST_ID | NUMBER | (15) | Y | Payment history Identifier |
| FREQUENCY_HIGH_RANGE | NUMBER | High limit of purchase frequency | ||
| FREQUENCY_LOW_RANGE | NUMBER | Low limit of purchase frequency | ||
| SEQ | NUMBER | (15) | Y | Sequence |
| SCORE | VARCHAR2 | (30) | Y | LOV of ranges of possible risk scores |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Used for locking purposes that subsequently allows for checking if there is old data on the screen compared to what is in the database. The situation occurs when the HTML application is a stateless application. | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| SECURITY_GROUP_ID | NUMBER | Used in hosted environments | ||
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_IRF_PMT_HIST_RANGE does not reference any database object
IBY.IBY_IRF_PMT_HIST_RANGE is referenced by following:
| Description: | IBY_IRF_RISKY_INSTR stores information pertaining to the risk instrument risk factor. It has information about the merchant who sends the file of risky instruments, the type of instrument and other account information pertaining to the risk |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_IRF_RISKY_INSTR.PAYEEID | IBY_PAYEE |
IBY_IRF_RISKY_INSTR stores information pertaining to the risk instrument risk factor. It has information about the merchant who sends the file of risky instruments, the type of instrument and other account information pertaining to the risky instrument.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_IRF_RISKY_INSTR_PAYEEID_N1 | NONUNIQUE | APPS_TS_TX_IDX | PAYEEID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYEEID | VARCHAR2 | (80) | id of the payee passed by electronic commerce application | |
| INSTRTYPE | VARCHAR2 | (30) | Y | Intrument Type. Bank Account, Credit Card etc |
| ROUTING_NO | VARCHAR2 | (80) | Bank ID to which the account belongs | |
| ACCOUNT_NO | VARCHAR2 | (80) | Bank Account Number | |
| CREDITCARD_NO | VARCHAR2 | (80) | Credit Card Number | |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column - date when a user last updated this row. | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | This column is used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard who column - user who last updated this row (foreign key to FND_USER.USER_ID). |
| CREATION_DATE | DATE | Y | Standard who column - date when this row was created. | |
| CREATED_BY | NUMBER | (15) | Y | Standard who column - user who created this row (foreign key to FND_USER.USER_ID). |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard who column - operating system login of user who last updated this row (foreign key to FND_LOGINS.LOGIN_ID). | |
| SECURITY_GROUP_ID | NUMBER | Used in hosted environments | ||
| CC_NUMBER_HASH1 | VARCHAR2 | (64) | Hash value of card number | |
| CC_NUMBER_HASH2 | VARCHAR2 | (64) | Hash value of card number | |
| ACCT_NUMBER_HASH1 | VARCHAR2 | (64) | Hash value of account number | |
| ACCT_NUMBER_HASH2 | VARCHAR2 | (64) | Hash value of account number |
IBY.IBY_IRF_RISKY_INSTR does not reference any database object
IBY.IBY_IRF_RISKY_INSTR is referenced by following:
| Description: | This table stores information pertaining to the time of purchase risk factor. The merchant can setup different time ranges - and associate a risk score of low risk, medium low risk, medium risk , medium high risk and high risk. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_IRF_TIMEOF_PURCHASE.PAYEEID | IBY_PAYEE |
IBY_IRF_TIMEOF_PURCHASE stores information pertaining to the time of purchase risk factor. The merchant can set up different time ranges and associate a risk score of low risk, medium low risk, medium risk, medium high risk, and high risk.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_IRF_TIMEOF_PUR_ID_SEQ_U1 | UNIQUE | APPS_TS_TX_IDX |
SEQ
PAYEEID ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| DURATION_FROM | VARCHAR2 | (8) | Y | Stores the beginning time HH:MM of the duration range |
| SEQ | NUMBER | (15) | Y | Sequence |
| DURATION_TO | VARCHAR2 | (8) | Y | Stores the end time HH:MM of the duration range |
| SCORE | VARCHAR2 | (30) | Y | LOV of ranges of possible risk scores |
| PAYEEID | VARCHAR2 | (80) | Payee identification passed by electronic commerce application | |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Used for locking purposes that subsequently allows for checking if there is old data on the screen compared to what is in the database. The situation occurs when the HTML application is a stateless application. | |
| LAST_UPDATED_BY | NUMBER | Y | Standard Who column | |
| CREATION_DATE | DATE | Y | Standard Who column | |
| CREATED_BY | NUMBER | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | Standard Who column | ||
| SECURITY_GROUP_ID | NUMBER | Used in hosted environments | ||
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_IRF_TIMEOF_PURCHASE does not reference any database object
IBY.IBY_IRF_TIMEOF_PURCHASE is referenced by following:
| Description: | IBY_IRF_TRXN_AMT_LIMITstores information pertaining to the transaction amount limit risk factor. It is a limit on the total amount of payments made using the same instrument in a particular duration. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_IRF_TRXN_AMT_LIMIT.PAYEEID | IBY_PAYEE |
IBY_IRF_TRXN_AMT_LIMIT stores information pertaining to the transaction amount limit risk factor, which is a limit on the total amount of payments made using the same instrument for a particular duration.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_IRF_TRXN_AMT_LMT_PAYEE_U1 | UNIQUE | APPS_TS_TX_IDX |
AMOUNT
DURATION_TYPE DURATION PAYEEID ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| DURATION | NUMBER | Y | Number of days, weeks, months, or years | |
| DURATION_TYPE | VARCHAR2 | (30) | Y | Days, weeks, months, or years |
| AMOUNT | NUMBER | Y | Transaction amount limit | |
| PAYEEID | VARCHAR2 | (80) | Payee Identifier passed by electronic commerce application | |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Used for locking purposes that subsequently allows for checking if there is old data on the screen compared to what is in the database. The situation occurs when the HTML application is a stateless application. | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| SECURITY_GROUP_ID | NUMBER | Used in hosted environments | ||
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_IRF_TRXN_AMT_LIMIT does not reference any database object
IBY.IBY_IRF_TRXN_AMT_LIMIT is referenced by following:
| Description: | IBY_MAPPINGS stores mapping of codes with risk scores. Each row includes a code and a value for that code. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_MAPPINGS.PAYEEID | IBY_PAYEE |
IBY_MAPPINGS stores mapping of codes with risk scores. Each row includes a code and a value for that code.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_MAPPINGS_TYPE_CODE_U1 | UNIQUE | APPS_TS_TX_IDX |
MAPPING_TYPE
PAYEEID MAPPING_CODE ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| MAPPING_TYPE | VARCHAR2 | (30) | Y | Mapping code type including avs, riskcode, credit rating |
| MAPPING_CODE | VARCHAR2 | (30) | Y | Mapping code |
| VALUE | VARCHAR2 | (240) | Y | Value of a lookup code |
| DESCRIPTION | VARCHAR2 | (240) | Description of the quick code | |
| SEQ | NUMBER | (5) | Sequence | |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Used for locking purposes that subsequently allows for checking if there is old data on the screen compared to what is in the database. The situation occurs when the HTML application is a stateless application. | |
| PAYEEID | VARCHAR2 | (80) | Y | Payee Identifier passed by electronic commerce application |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| SECURITY_GROUP_ID | NUMBER | Used in hosted environments | ||
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_MAPPINGS does not reference any database object
IBY.IBY_MAPPINGS is referenced by following:
| Description: | IBY_PAYEE stores a row for each payee, such as a biller, merchant, or store at this site. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_PAYEE.ECAPPID | IBY_ECAPP |
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_ACCPPMTMTHD.MPAYEEID | IBY_PAYEE |
| IBY_BATCHES_ALL.MPAYEEID | IBY_PAYEE |
| IBY_DEFAULT_BEP.MPAYEEID | IBY_PAYEE |
| IBY_FNDCPT_PAYEE_APPL.MPAYEEID | IBY_PAYEE |
| IBY_IRF_PMT_AMOUNT.PAYEEID | IBY_PAYEE |
| IBY_IRF_PMT_FREQUENCY.PAYEEID | IBY_PAYEE |
| IBY_IRF_PMT_HISTORY.PAYEEID | IBY_PAYEE |
| IBY_IRF_RISKY_INSTR.PAYEEID | IBY_PAYEE |
| IBY_IRF_TIMEOF_PURCHASE.PAYEEID | IBY_PAYEE |
| IBY_IRF_TRXN_AMT_LIMIT.PAYEEID | IBY_PAYEE |
| IBY_MAPPINGS.PAYEEID | IBY_PAYEE |
| IBY_PAYEE_SUBKEYS.MPAYEE_ID | IBY_PAYEE |
| IBY_RISK_FORMULAS.PAYEEID | IBY_PAYEE |
| IBY_ROUTINGINFO.MPAYEEID | IBY_PAYEE |
| IBY_TRXN_SUMMARIES_ALL.MPAYEEID | IBY_PAYEE |
| IBY_TRXN_SUMMARIES_ALL.MPAYEEID | IBY_PAYEE |
IBY_PAYEE stores a row for each payee, such as a biller, merchant, or store at this site.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_PAYEE_MPAYEEID_U2 | UNIQUE | APPS_TS_TX_IDX | MPAYEEID |
| IBY_PAYEE_PAYEEID_U1 | UNIQUE | APPS_TS_TX_IDX | PAYEEID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| MPAYEEID | NUMBER | (15) | Y | System generated Payee Identifier |
| PAYEEID | VARCHAR2 | (80) | Y | Payee Identifier passed by electronic commerce application |
| NAME | VARCHAR2 | (80) | Y | Name of the payee |
| ECAPPID | NUMBER | (15) | Y | Electronic commerce application Identifier |
| USERNAME | VARCHAR2 | (80) | Username for authentication | |
| PASSWORD | VARCHAR2 | (80) | Password for the username above | |
| ACTIVESTATUS | VARCHAR2 | (1) | Y | Y or N flag to indicate whether the merchant is active |
| THRESHOLD | NUMBER | (15) | Threshold value to check against the overall risk score | |
| RISK_ENABLED | VARCHAR2 | (1) | Y or N flag indicating whether risk management feature is enabled | |
| SUPPORTEDOP | NUMBER | Bit map to denote operations supported by the payee | ||
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Used for locking purposes that subsequently allows for checking if there is 'old data on the screen compared to what is in the database. The situation occurs when the HTML application is a stateless application. | |
| LAST_UPDATED_BY | NUMBER | Y | Standard Who column | |
| CREATION_DATE | DATE | Y | Standard Who column | |
| CREATED_BY | NUMBER | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | Standard Who column | ||
| SECURITY_GROUP_ID | NUMBER | Used in hosted environments | ||
| MCC_CODE | NUMBER | (10) | Merchant category code, or MCC, for this payee, if applicable | |
| EMAIL_ADDRESS | VARCHAR2 | (2000) | Oracle internal use only, reserved for future use | |
| FINANCING_PAYEE_FLAG | VARCHAR2 | (1) | Oracle internal use only, reserved for future use | |
| MASTER_KEY | VARCHAR2 | (24) | Oracle internal use only, reserved for future use | |
| SECURITY_ENABLED | VARCHAR2 | (1) | Oracle internal use only, reserved for future use | |
| DBA_NAME | VARCHAR2 | (80) | Payee doing-business-name | |
| DBA_CITY | VARCHAR2 | (80) | Payee doing-business-as address city | |
| DBA_STATE_PROVINCE | VARCHAR2 | (80) | Payee doing-business-as address state or province | |
| DBA_COUNTRY | VARCHAR2 | (80) | Payee doing-business-as address country | |
| INACTIVE_DATE | DATE | Inactive date |
IBY.IBY_PAYEE does not reference any database object
IBY.IBY_PAYEE is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_PAYEE_SUBKEYS.MPAYEE_ID | IBY_PAYEE |
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_TRXN_SUMMARIES_ALL.SUB_KEY_ID | IBY_PAYEE_SUBKEYS |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_PAYEE_SUBKEYS_PAYEEID_N1 | NONUNIQUE | APPS_TS_TX_IDX |
MPAYEE_ID
USE_COUNT |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYEE_SUBKEY_ID | NUMBER | Y | ||
| MPAYEE_ID | NUMBER | Y | ||
| SUBKEY_CIPHER_TEXT | VARCHAR2 | (24) | Y | |
| USE_COUNT | NUMBER | |||
| OBJECT_VERSION_NUMBER | NUMBER | |||
| CREATED_BY | NUMBER | |||
| CREATION_DATE | DATE | |||
| LAST_UPDATED_BY | NUMBER | |||
| LAST_UPDATE_DATE | DATE | |||
| LAST_UPDATE_LOGIN | NUMBER | |||
| SECURITY_GROUP_ID | NUMBER |
IBY.IBY_PAYEE_SUBKEYS does not reference any database object
IBY.IBY_PAYEE_SUBKEYS is referenced by following:
| Description: | "This table stores information about card number for the card programs associated with card type 'Payment Card'.IBY_PAYMENTCARD contain payment card numbers entered manually through the Payables, Credit card setup. The card number can be nu |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_PAYMENTCARD.ADDRESSID | HZ_PARTY_SITE_USES |
| IBY_PAYMENTCARD.CARD_OWNER_ID | HZ_PARTIES |
| IBY_PAYMENTCARD.BILL_ADDR_TERRITORY_CODE | FND_TERRITORIES |
This table stores information about card number for the card programs associated with card type 'Payment Card'.IBY_PAYMENTCARD contain payment card numbers entered manually through the Payables, Credit card setup. The card number can be numeric or alpha numeric characters. The card number is fetched in the internal bank field of the payments workbench when payments are made using the Payment Process Profile with processing type as 'Payment Card
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_PAYMENTCARD_INSTRID_U1 | UNIQUE | APPS_TS_TX_IDX | INSTRID |
| IBY_PAYMENTCARD_N1 | NONUNIQUE | APPS_TS_TX_IDX | CARD_NUMBER |
| IBY_PAYMENTCARD_OWNER | NONUNIQUE | APPS_TS_TX_IDX |
CARD_NUMBER
CARD_OWNER_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| INSTRID | NUMBER | (15) | Y | Sequence: IBY_PAYMENTCARD_S.nextval |
| CARD_NUMBER | VARCHAR2 | (30) | Y | The Payment card number. It can be alphanumeric |
| EXPIRYDATE | DATE | Expiration date of the card | ||
| ADDRESSID | NUMBER | Will become a foreign key to HZ_PARTY_SITE_USES.PARTY_SITE_USE_ID instead of HZ_LOCATIONS.LOCATION_ID ; changes to existing customer data will be implemented in an upgrade script | ||
| BILLING_ADDR_POSTAL_CODE | VARCHAR2 | (50) | Billing address postal code | |
| BILL_ADDR_TERRITORY_CODE | VARCHAR2 | (2) | Billing address territory code | |
| DESCRIPTION | VARCHAR2 | (240) | Description of the instrument | |
| CHNAME | VARCHAR2 | (80) | Card Holder Name | |
| FINAME | VARCHAR2 | (80) | Financial Institution Name | |
| MASKED_CARD_NUMBER | VARCHAR2 | (30) | Masked Payment card number; to be used for display purposes | |
| CARD_MASK_SETTING | VARCHAR2 | (30) | For masking feature | |
| CARD_UNMASK_LENGTH | VARCHAR2 | (2) | For masking feature | |
| CARD_OWNER_ID | NUMBER | (15) | Owner TCA Party ID | |
| INSTRUMENT_TYPE | VARCHAR2 | (30) | Y | PAYMENTCARD |
| CARD_ISSUER_CODE | VARCHAR2 | (30) | COMCHECK | |
| CARD_NUMBER_LENGTH | NUMBER | (3) | For masking/security features | |
| ACTIVE_FLAG | VARCHAR2 | (1) | Y or N denoting the card is active or not | |
| SINGLE_USE_FLAG | VARCHAR2 | (1) | Not Used | |
| INFORMATION_ONLY_FLAG | VARCHAR2 | (1) | Not used | |
| CARD_PURPOSE | VARCHAR2 | (30) | Not used | |
| INACTIVE_DATE | DATE | Inactive date | ||
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | Descriptive Flexfield structure defining column | |
| ATTRIBUTE1 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE2 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE3 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE4 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE5 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE6 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE7 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE8 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE9 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE10 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE11 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE12 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE13 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE14 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE15 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| REQUEST_ID | NUMBER | (15) | Concurrent Who column | |
| PROGRAM_APPLICATION_ID | NUMBER | (15) | Concurrent Who column | |
| PROGRAM_ID | NUMBER | (15) | Concurrent Who column | |
| PROGRAM_UPDATE_DATE | DATE | Concurrent Who column | ||
| SECURITY_GROUP_ID | NUMBER | Used in hosted environments | ||
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | Y | Standard Who column | |
| CREATION_DATE | DATE | Y | Standard Who column | |
| CREATED_BY | NUMBER | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | Standard Who column | ||
| OBJECT_VERSION_NUMBER | NUMBER | Y | This column is used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. |
IBY.IBY_PAYMENTCARD does not reference any database object
IBY.IBY_PAYMENTCARD is referenced by following:
| Description: | "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 |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_PAYMENTS_ALL.PAYMENT_METHOD_CODE | IBY_PAYMENT_METHODS_B |
| IBY_PAYMENTS_ALL.PAYMENT_PROFILE_ID | IBY_ACCT_PMT_PROFILES_B |
| IBY_PAYMENTS_ALL.PAYMENT_SERVICE_REQUEST_ID | IBY_PAY_SERVICE_REQUESTS |
| IBY_PAYMENTS_ALL.PAYMENT_INSTRUCTION_ID | IBY_PAY_INSTRUCTIONS_ALL |
| IBY_PAYMENTS_ALL.PAYMENT_REASON_CODE | IBY_PAYMENT_REASONS_B |
| IBY_PAYMENTS_ALL.DELIVERY_CHANNEL_CODE | IBY_DELIVERY_CHANNELS_B |
| IBY_PAYMENTS_ALL.EXT_PAYEE_ID | IBY_EXTERNAL_PAYEES_ALL |
| IBY_PAYMENTS_ALL.EXTERNAL_BANK_ACCOUNT_ID | CE_BANK_ACCOUNTS |
| IBY_PAYMENTS_ALL.INTERNAL_BANK_ACCOUNT_ID | CE_BANK_ACCOUNTS |
| Foreign Key Column | Foreign Table |
|---|---|
| AP_HISTORY_CHECKS_ALL.PAYMENT_ID | IBY_PAYMENTS_ALL |
| IBY_DOCS_PAYABLE_ALL.FORMATTING_PAYMENT_ID | IBY_PAYMENTS_ALL |
| IBY_DOCS_PAYABLE_ALL.PAYMENT_ID | IBY_PAYMENTS_ALL |
| IBY_DOCUMENTS_PAYABLE_H.PAYMENT_ID | IBY_PAYMENTS_ALL |
IBY_PAYMENTS_ALL stores information on payments. A payment is a single check or fund transfer transaction between first party payer and third party payee. A payment pays one or more documents payable, and there may be one or more payments in a payment instruction. Payments are built by grouping documents payable according to Oracle Payments' grouping rules. This table corresponds to the Payments tab of the Funds Disbursement Process Home.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_PAYMENTS_ALL_U1 | UNIQUE | APPS_TS_TX_IDX | PAYMENT_ID |
| IBY_PAYMENTS_ALL_N1 | NONUNIQUE | APPS_TS_TX_IDX | PAYMENT_PROFILE_ID |
| IBY_PAYMENTS_ALL_N10 | NONUNIQUE | APPS_TS_TX_IDX |
COMPLETED_PMTS_GROUP_ID
ORG_ID ORG_TYPE |
| IBY_PAYMENTS_ALL_N11 | NONUNIQUE | APPS_TS_TX_IDX |
PAYMENT_INSTRUCTION_ID
PAPER_DOCUMENT_NUMBER ORG_ID |
| IBY_PAYMENTS_ALL_N12 | NONUNIQUE | APPS_TS_TX_IDX | PAYMENT_REFERENCE_NUMBER |
| IBY_PAYMENTS_ALL_N13 | NONUNIQUE | APPS_TS_TX_IDX |
DOCUMENT_CATEGORY_CODE
DOCUMENT_SEQUENCE_ID DOCUMENT_SEQUENCE_VALUE |
| IBY_PAYMENTS_ALL_N14 | NONUNIQUE | APPS_TS_TX_IDX | PAYEE_PARTY_ID |
| IBY_PAYMENTS_ALL_N15 | NONUNIQUE | APPS_TS_TX_IDX |
PAYMENT_SERVICE_REQUEST_ID
PAYMENT_STATUS PAYMENTS_COMPLETE_FLAG |
| IBY_PAYMENTS_ALL_N16 | NONUNIQUE | APPS_TS_TX_IDX |
PAYMENT_STATUS
STOP_REQUEST_PLACED_FLAG STOP_CONFIRMED_FLAG |
| IBY_PAYMENTS_ALL_N17 | NONUNIQUE | APPS_TS_TX_IDX |
PAYMENT_INSTRUCTION_ID
PAYMENT_SERVICE_REQUEST_ID |
| IBY_PAYMENTS_ALL_N2 | NONUNIQUE | APPS_TS_TX_IDX | PAYMENT_SERVICE_REQUEST_ID |
| IBY_PAYMENTS_ALL_N3 | NONUNIQUE | APPS_TS_TX_IDX | PAYMENT_REASON_CODE |
| IBY_PAYMENTS_ALL_N4 | NONUNIQUE | APPS_TS_TX_IDX | DELIVERY_CHANNEL_CODE |
| IBY_PAYMENTS_ALL_N5 | NONUNIQUE | APPS_TS_TX_IDX | PAYMENT_DATE |
| IBY_PAYMENTS_ALL_N6 | NONUNIQUE | APPS_TS_TX_IDX | EXT_PAYEE_ID |
| IBY_PAYMENTS_ALL_N7 | NONUNIQUE | APPS_TS_TX_IDX | EXTERNAL_BANK_ACCOUNT_ID |
| IBY_PAYMENTS_ALL_N8 | NONUNIQUE | APPS_TS_TX_IDX | INTERNAL_BANK_ACCOUNT_ID |
| IBY_PAYMENTS_ALL_N9 | NONUNIQUE | APPS_TS_TX_IDX | PAYMENT_STATUS |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYMENT_ID | NUMBER | (15) | Y | Unique internal Identifier for this record. Generated using a database sequence. |
| PAYMENT_METHOD_CODE | VARCHAR2 | (30) | Y | Payment method used for making the payments. |
| PAYMENT_SERVICE_REQUEST_ID | NUMBER | (15) | Y | Payment service request Id and it is the foreign key to the table iby_pay_service_requests. |
| PROCESS_TYPE | VARCHAR2 | (30) | Y | Specifies the process by which the payment is built into a payment instruction. Values, from the lookup IBY_PROCESS_TYPES, include STANDARD, IMMEDIATE, and MANUAL. |
| PAYMENT_STATUS | VARCHAR2 | (30) | Y | The status of the Payment. Values are derived from the lookup IBY_PAYMENT_STATUSES. The possible values are CREATED, FORMATTED, TRANSMITTED, VOID_BY_OVERFLOW, REJECTED, FORMATTED, VOID, etc. |
| PAYMENTS_COMPLETE_FLAG | VARCHAR2 | (1) | Y | Y or N flag that indicates if the payment is complete |
| PAYMENT_FUNCTION | VARCHAR2 | (30) | Y | Function or purpose of the payment. Values from the lookup IBY_PAYMENT_FUNCTIONS include SUPPLIER_PAYMENT, CUSTOMER_REFUNDS, and others. |
| PAYMENT_AMOUNT | NUMBER | Y | Amount of the payment | |
| PAYMENT_CURRENCY_CODE | VARCHAR2 | (10) | Y | Currency of the payment |
| BILL_PAYABLE_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether a payment is a bill payable, that is, a future dated payment |
| EXCLUSIVE_PAYMENT_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether this payment is made up of a single document payable that was meant to be paid alone |
| SEPARATE_REMIT_ADVICE_REQ_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether a separate remittance advice needs to be generated for a payment. |
| INTERNAL_BANK_ACCOUNT_ID | NUMBER | (15) | Y | Internal bank account id used for making the payment. |
| ORG_ID | NUMBER | (15) | Y | Unique internal identifier of the Operating Unit. Validated against HR_OPERATING_UNITS.ORGANIZATION_ID. |
| ORG_TYPE | VARCHAR2 | (30) | Y | Organization type. Values, from the lookup IBY_ORGANIZATION_TYPES Include Operating Unit, Business Group, and Legal Entity |
| LEGAL_ENTITY_ID | NUMBER | (15) | Y | Legal entity identifier |
| DECLARE_PAYMENT_FLAG | VARCHAR2 | (1) | Y | Y or N flag that indicates whether this payment needs to be reported to the central bank of the country in which the payment is being made. |
| DELIVERY_CHANNEL_CODE | VARCHAR2 | (30) | The delivery channel code for the payment. This is updated only when the payment s are grouped by Delivery channel code | |
| EXT_PAYEE_ID | NUMBER | (15) | Y | Payee Identifier to which actual payment is made. |
| PAYMENT_INSTRUCTION_ID | NUMBER | (15) | Payment instruction identifier | |
| PAYMENT_PROFILE_ID | NUMBER | (15) | Y | Payment process profile identifier |
| PREGROUPED_PAYMENT_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether this payment was grouped by the calling application. If the value is Y, all the documents of this payment will contain a non-null value for the payment grouping number attribute. |
| STOP_CONFIRMED_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether a stop has been confirmed on this payment. |
| STOP_RELEASED_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether a stop request has been released on this payment. |
| STOP_REQUEST_PLACED_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether a stop request has been placed on this payment. |
| CREATED_BY | NUMBER | (15) | Y | Standard who column - unique internal identifier of user who created this row. Foreign key to the USER_ID column of the FND_USER table. |
| CREATION_DATE | DATE | Y | Standard who column - date when this row was created. | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard who column - unique internal identifier user who last updated this row. Foreign key to the USER_ID column of the FND_USER table. |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column - date when a user last updated this row. | |
| LAST_UPDATE_DATE | DATE | Y | Standard who column - operating system login of user who last updated this row. Foreign key to the LOGIN_ID column of the FND_LOGINS table. | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. This number is incremented for every update to the row through the application. | |
| PAYEE_PARTY_ID | NUMBER | (15) | TCA party identifier | |
| PARTY_SITE_ID | NUMBER | (15) | Party Site identifier Party Site Unique identifier from TCA tables. Validated against HZ_PARTY_SITES.PARTY_SITE_ID | |
| SUPPLIER_SITE_ID | NUMBER | (15) | Supplier site identifier. Validated against PO_VENDOR_SITES_ALL.VENDOR_SITE_ID. | |
| PAYMENT_REASON_CODE | VARCHAR2 | (30) | The payment reason code for the payment. This is updated only when the payment s are grouped by Payment reason code | |
| PAYMENT_REASON_COMMENTS | VARCHAR2 | (240) | Free text field available for entering a reason for the payment | |
| PAYMENT_DATE | DATE | Payment date | ||
| ANTICIPATED_VALUE_DATE | DATE | With the current flow this would be null for all the payments. The field exists at the document level. This is not getting to payment level as payments can not be grouped by anticipated_value_date. | ||
| DECLARATION_AMOUNT | NUMBER | Sum of all reporting amounts from the documents that constitute this payment. This amount will be in the declaration or reporting currency. | ||
| DECLARATION_CURRENCY_CODE | VARCHAR2 | (10) | Currency of the declaration amount | |
| DISCOUNT_AMOUNT_TAKEN | NUMBER | Discount amount in payment currency | ||
| PAYMENT_DETAILS | VARCHAR2 | (4000) | Concatenated string as per the Payment details formula provided in the Payment process profile. | |
| BANK_CHARGE_BEARER | VARCHAR2 | (30) | Bearer of bank charge cost. Bank charge bearers are defined as the lookup IBY_BANK_CHARGE_BEARER. | |
| BANK_CHARGE_AMOUNT | NUMBER | Bank charge amount in the payment currency | ||
| SETTLEMENT_PRIORITY | VARCHAR2 | (30) | Priority with which the financial institution or payment system settles payment for this document. The available values for this column come from the FND lookup IBY_SETTLEMENT_PRIORITY. | |
| REMITTANCE_MESSAGE1 | VARCHAR2 | (150) | Remittance message for use in payment processing | |
| REMITTANCE_MESSAGE2 | VARCHAR2 | (150) | Remittance message for use in payment processing | |
| REMITTANCE_MESSAGE3 | VARCHAR2 | (150) | Remittance message for use in payment processing | |
| PAYMENT_REFERENCE_NUMBER | NUMBER | (15) | User and bank facing number identifying the payment | |
| PAPER_DOCUMENT_NUMBER | NUMBER | (15) | Payment document number if a printed payment | |
| BANK_ASSIGNED_REF_CODE | VARCHAR2 | (30) | Payment system-provided reference code for this payment | |
| EXTERNAL_BANK_ACCOUNT_ID | NUMBER | (15) | External bank account identifier | |
| UNIQUE_REMITTANCE_IDENTIFIER | VARCHAR2 | (30) | Unique remittance Identifier would be defined at invoice level. If payments are grouped based on Unique remittance Identifier, then it would be populated to payment level. | |
| URI_CHECK_DIGIT | VARCHAR2 | (2) | Unique remittance identifier check digit | |
| BANK_INSTRUCTION1_CODE | VARCHAR2 | (30) | Code of first bank instruction | |
| BANK_INSTRUCTION2_CODE | VARCHAR2 | (30) | Code of second bank instruction | |
| BANK_INSTRUCTION_DETAILS | VARCHAR2 | (255) | Additional bank instruction details | |
| PAYMENT_TEXT_MESSAGE1 | VARCHAR2 | (150) | Text message for use in payment processing | |
| PAYMENT_TEXT_MESSAGE2 | VARCHAR2 | (150) | Text message for use in payment processing | |
| PAYMENT_TEXT_MESSAGE3 | VARCHAR2 | (150) | Text message for use in payment processing | |
| MATURITY_DATE | DATE | Calculated maturity date on a bill payable payment, that is, a future dated payment | ||
| PAYMENT_DUE_DATE | DATE | Date on which the payment is made. This is populated if grouped by payment due date. | ||
| DOCUMENT_CATEGORY_CODE | VARCHAR2 | (30) | Sequential Numbering document category | |
| DOCUMENT_SEQUENCE_ID | NUMBER | Sequential Numbering document sequence identifier | ||
| DOCUMENT_SEQUENCE_VALUE | NUMBER | Sequence number of document payable | ||
| BENEFICIARY_PARTY | NUMBER | (15) | Beneficiary party, if payment is made through a third party | |
| STOP_CONFIRMED_BY | NUMBER | (15) | The user who confirmed the stop. | |
| STOP_CONFIRM_DATE | DATE | Date on which the stop was confirmed. | ||
| STOP_CONFIRM_REASON | VARCHAR2 | (240) | Reason for confirming the stop. | |
| STOP_CONFIRM_REFERENCE | VARCHAR2 | (100) | Payment system reference code for the confirmed stop payment. | |
| STOP_RELEASED_BY | NUMBER | (15) | The user who released the stop request. | |
| STOP_RELEASE_DATE | DATE | Date on which the stop request was released. | ||
| STOP_RELEASE_REASON | VARCHAR2 | (240) | Reason for releasing the stop request. | |
| STOP_RELEASE_REFERENCE | VARCHAR2 | (100) | Payment system reference code for releasing or denying the stop request. | |
| STOP_REQUEST_DATE | DATE | Date on which the stop request was placed. | ||
| STOP_REQUEST_PLACED_BY | NUMBER | (15) | The user who placed the stop request. | |
| STOP_REQUEST_REASON | VARCHAR2 | (240) | Reason for placing the stop request. | |
| STOP_REQUEST_REFERENCE | VARCHAR2 | (100) | Payment system reference code for the stop request. | |
| VOIDED_BY | NUMBER | (15) | The user who voided the payment. | |
| VOID_DATE | DATE | Date on which the payment was voided. | ||
| VOID_REASON | VARCHAR2 | (240) | Reason for voiding the payment. | |
| REMIT_TO_LOCATION_ID | NUMBER | (15) | Remit-To address identifier | |
| COMPLETED_PMTS_GROUP_ID | NUMBER | (15) | The identifier of a group of payments, including this one, which were marked complete. The value is from the sequence IBY_COMPLETED_PMTS_GROUP_S. | |
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | Descriptive flexfield structure definition column. | |
| ATTRIBUTE1 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE2 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE3 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE4 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE5 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE6 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE7 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE8 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE9 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE10 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE11 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE12 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE13 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE14 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE15 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| EXT_BRANCH_NUMBER | VARCHAR2 | (30) | Payee bank routing number (branch number), denormalized from CE bank branches view | |
| EXT_BANK_NUMBER | VARCHAR2 | (30) | Payee bank number, denormalized from CE bank branches view | |
| EXT_BANK_ACCOUNT_NAME | VARCHAR2 | (80) | Payee bank account name, denormalized from CE bank branches view | |
| EXT_BANK_ACCOUNT_NUMBER | VARCHAR2 | (100) | Masked payee bank account number, denormalized from CE bank accounts view | |
| EXT_BANK_ACCOUNT_TYPE | VARCHAR2 | (25) | Payee bank account type, denormalized from CE bank accounts view | |
| EXT_BANK_ACCOUNT_IBAN_NUMBER | VARCHAR2 | (50) | Masked payee bank account IBAN, denormalized from CE bank accounts view | |
| PAYEE_NAME | VARCHAR2 | (360) | Name of payee, if provided by administrator | |
| PAYEE_ADDRESS1 | VARCHAR2 | (240) | First line for payee address, if provided by administrator | |
| PAYEE_ADDRESS2 | VARCHAR2 | (240) | Second line for payee address, if provided by administrator | |
| PAYEE_ADDRESS3 | VARCHAR2 | (240) | Third line for payee address, if provided by administrator | |
| PAYEE_ADDRESS4 | VARCHAR2 | (240) | Fourth line for payee address, if provided by administrator | |
| PAYEE_CITY | VARCHAR2 | (60) | Payee city, if provided by administrator | |
| PAYEE_POSTAL_CODE | VARCHAR2 | (60) | Payee postal code, if provided by administrator | |
| PAYEE_STATE | VARCHAR2 | (120) | Payee state, if provided by administrator | |
| PAYEE_PROVINCE | VARCHAR2 | (120) | Payee province, if provided by administrator | |
| PAYEE_COUNTY | VARCHAR2 | (120) | Payee county, if provided by administrator | |
| PAYEE_COUNTRY | VARCHAR2 | (60) | Payee country code, if provided by administrator | |
| REMIT_ADVICE_DELIVERY_METHOD | VARCHAR2 | (30) | How the remittance advice, if any, is delivered using values from lookup type IBY_DELIVERY_METHODS | |
| REMIT_ADVICE_EMAIL | VARCHAR2 | (255) | E-mail address to which the remittance advice is delivered | |
| REMIT_ADVICE_FAX | VARCHAR2 | (100) | Fax number to which the remittance advice is delivered | |
| PAYMENT_PROFILE_SYS_NAME | VARCHAR2 | (100) | Denormalized from IBY_SYS_PMT_PROFILES; derive via PAYMENT_PROFILE_ ID | |
| PAYMENT_PROFILE_ACCT_NAME | VARCHAR2 | (100) | Denormalized from IBY_ACCT_PMT_PROFILES; derive via PAYMENT_PROFILE_ ID | |
| PAYMENT_PROCESS_REQUEST_NAME | VARCHAR2 | (255) | Denormalized from IBY_PAY_SERVICE_REQUESTS.CALL_APP_PAY_SERVICE_REQ_CODE; derive via PAYMENT_SERVICE_REQUEST_ID | |
| SOURCE_PRODUCT | VARCHAR2 | (50) | Denormalized from product name for product determined by IBY_PAY_SERVICE_REQUESTS. CALLING_APP_ID; derive via PAYMENT_SERVICE_REQUEST_ID | |
| PAYMENT_REASON_FORMAT_VALUE | VARCHAR2 | (80) | Payment reason value that is put into the extract for use by the format | |
| DECLARATION_EXCH_RATE_TYPE | VARCHAR2 | (255) | Exchange rate type used for reporting | |
| DECLARATION_FORMAT | VARCHAR2 | (100) | Format for reporting | |
| DELIVERY_CHANNEL_FORMAT_VALUE | VARCHAR2 | (80) | Delivery channel value that is put into the extract for use by the format | |
| BANK_INSTRUCTION1_FORMAT_VALUE | VARCHAR2 | (80) | Bank instruction value that is put into the extract for use by the format | |
| BANK_INSTRUCTION2_FORMAT_VALUE | VARCHAR2 | (80) | Bank instruction value that is put into the extract for use by the format | |
| SRA_DELIVERY_METHOD | VARCHAR2 | (100) | Denormalized from IBY_REMIT_ADVICE_SETUP.REMIT_ADVICE_ DELIVERY_METHOD derived via PPP | |
| INT_BANK_NAME | VARCHAR2 | (360) | Denormalized from HZ_PARTIES.PARTY_NAME; derived via INTERNAL_BANK_ACCOUNT_ID | |
| INT_BANK_NUMBER | VARCHAR2 | (30) | Denormalized from TCA; derived via INTERNAL_BANK_ACCOUNT_ID | |
| INT_EFT_SWIFT_CODE | VARCHAR2 | (30) | SWIFT code of the payer's bank | |
| INT_BANK_BRANCH_NAME | VARCHAR2 | (360) | Denormalized from TCA; derived via INTERNAL_BANK_ACCOUNT_ID | |
| INT_BANK_BRANCH_NUMBER | VARCHAR2 | (30) | Denormalized from TCA; derived via INTERNAL_BANK_ACCOUNT_ID | |
| INT_BANK_ACCOUNT_NAME | VARCHAR2 | (100) | Denormalized from CE; derived via INTERNAL_BANK_ACCOUNT_ID | |
| INT_BANK_ACCOUNT_NUMBER | VARCHAR2 | (30) | Denormalized from CE; derived via INTERNAL_BANK_ACCOUNT_ID | |
| INT_BANK_ACCOUNT_IBAN | VARCHAR2 | (50) | Denormalized from CE; derived via INTERNAL_BANK_ACCOUNT_ID | |
| EXT_BANK_NAME | VARCHAR2 | (360) | Denormalized from IBY_EXT_BANK_ACCOUNTS_V. BANK_NAME; derived via EXTERNAL_BANK_ACCOUNT_ID | |
| EXT_EFT_SWIFT_CODE | VARCHAR2 | (30) | SWIFT code of the payee's bank | |
| EXT_BANK_BRANCH_NAME | VARCHAR2 | (360) | Denormalized from IBY_EXT_BANK_ACCOUNTS_V. BANK_BRANCH_NAME; derived via EXTERNAL_BANK_ACCOUNT_ID | |
| ORG_NAME | VARCHAR2 | (240) | Denormalized fromHR_ALL_ORGANIZATION_UNITS.NAME; derived via ORG_ID | |
| PAYER_LEGAL_ENTITY_NAME | VARCHAR2 | (240) | Name of the legal entity making the disbursement | |
| PAYER_LE_REGISTRATION_NUM | VARCHAR2 | (240) | Legal registration number of the legal entity making the disbursement | |
| PAYER_TAX_REGISTRATION_NUM | VARCHAR2 | (50) | Tax registration number of the legal entity making the disbursement | |
| PAYEE_PARTY_NAME | VARCHAR2 | (360) | Denormalized from HZ_PARTIES.PARTY_NAME; derived via PAYEE_PARTY_ID | |
| PAYEE_LE_REGISTRATION_NUM | VARCHAR2 | (50) | Legal registration number of the legal entity receiving the disbursement | |
| PAYEE_TAX_REGISTRATION_NUM | VARCHAR2 | (50) | Tax registration number of the legal entity receiving the disbursement | |
| PAYER_PARTY_SITE_NAME | VARCHAR2 | (240) | Payer party site name | |
| PAYEE_ADDRESS_CONCAT | VARCHAR2 | (2000) | Concatenated denormalization from standard address fields HZ_LOCATIONS; derived via PARTY_SITE_ID. | |
| BENEFICIARY_NAME | VARCHAR2 | (360) | Denormalized from HZ_PARTIES.PARTY_NAME; derived via BENEFICIARY_PARTY_ID | |
| PAYER_PARTY_NUMBER | VARCHAR2 | (30) | Payer party number | |
| PAYEE_PARTY_NUMBER | VARCHAR2 | (30) | Payee party number | |
| PAYEE_ALTERNATE_NAME | VARCHAR2 | (320) | Payee party alternate name | |
| PAYEE_SITE_ALTERNATE_NAME | VARCHAR2 | (320) | Payee party site alternate name | |
| PAYEE_SUPPLIER_NUMBER | VARCHAR2 | (30) | Supplier number | |
| PAYEE_FIRST_PARTY_REFERENCE | VARCHAR2 | (30) | Payee first party reference | |
| INT_BANK_BRANCH_RFC_IDENTIFIER | VARCHAR2 | (30) | Internal bank branch RFC identifier | |
| INT_BANK_ACCT_AGENCY_LOC_CODE | VARCHAR2 | (30) | Auditing column for the corresponding value in CE_BANK_ACCOUNTS.AGENCY_LOCATION_CODE | |
| PAYER_ABBREVIATED_AGENCY_CODE | VARCHAR2 | (30) | Agency Location Code used by federal agencies | |
| PAYER_FEDERAL_US_EMPLOYER_ID | VARCHAR2 | (20) | Employer identifier used by federal agencies | |
| EXT_BANK_ACCT_OWNER_PARTY_ID | VARCHAR2 | (360) | Identifier of the bank branch of the payee | |
| EXT_BANK_ACCT_PMT_FACTOR_FLAG | VARCHAR2 | (1) | Identifier of the bank branch of the payee | |
| ADDRESS_SOURCE | VARCHAR2 | (30) | Source of the address. Possible values from the lookup IBY_ADDRESS_SOURCE_TYPES include TCA and HR. | |
| EMPLOYEE_ADDRESS_CODE | VARCHAR2 | (30) | Type of address. Possible values include HOME and OFFICE. | |
| EMPLOYEE_PERSON_ID | NUMBER | (15) | Employee person Identifier | |
| EMPLOYEE_PAYMENT_FLAG | VARCHAR2 | (1) | Y or N flag indicating whether the payment is of the employee payment type | |
| EMPLOYEE_ADDRESS_ID | NUMBER | (15) | HR Identifier of the address | |
| REQUEST_ID | NUMBER | (15) | Concurrent request identifier associated with the current process, used to control updates to processes that are currently active | |
| EXT_BANK_BRANCH_PARTY_ID | NUMBER | Identifier of the bank branch of the payee | ||
| EXT_BANK_ALT_NAME | VARCHAR2 | (320) | Alternate name of the bank of the payee | |
| EXT_BANK_BRANCH_ALT_NAME | VARCHAR2 | (320) | Alternate name of the bank branch of the payee | |
| EXT_BANK_ACCOUNT_ALT_NAME | VARCHAR2 | (320) | Alternate name of the bank account of the payee | |
| EXT_BANK_ACCOUNT_NUM_ELEC | VARCHAR2 | (100) | Auditing column for the corresponding value in IBY_EXT_BANK_ACCOUNTS.BANK_ACCOUNT_NUM_ELEC | |
| EXT_BANK_BRANCH_LOCATION_ID | NUMBER | Identifier of the address of the bank branch of the payee | ||
| EXT_BANK_ACCT_OWNER_PARTY_NAME | VARCHAR2 | (360) | Name of the account owner of the payee bank account | |
| INT_BANK_BRANCH_PARTY_ID | NUMBER | Identifier of the bank branch of the payer | ||
| INT_BANK_ALT_NAME | VARCHAR2 | (320) | Alternate name of the bank of the payer | |
| INT_BANK_BRANCH_ALT_NAME | VARCHAR2 | (320) | Alternate name of the bank branch of the payer | |
| INT_BANK_ACCOUNT_ALT_NAME | VARCHAR2 | (320) | Alternate name of the bank account of the payer | |
| INT_BANK_ACCOUNT_NUM_ELEC | VARCHAR2 | (100) | Auditing column for the corresponding value in CE_BANK_ACCOUNTS.EFT_USER_NUM | |
| INT_BANK_BRANCH_LOCATION_ID | NUMBER | Identifier of the address of the bank branch of the payer | ||
| INT_BANK_BRANCH_EFT_USER_NUM | VARCHAR2 | (30) | Auditing column for the corresponding value in CE_BANK_ACCOUNTS.BANK_ACCOUNT_NUM_ELECTRONIC | |
| PAYER_PARTY_ID | NUMBER | Identifier of the supplier party | ||
| PAYER_LOCATION_ID | NUMBER | Identifier of the supplier party address | ||
| PAYER_PARTY_ATTR_CATEGORY | VARCHAR2 | (150) | Payer party attribute category | |
| PAYER_LE_ATTR_CATEGORY | VARCHAR2 | (150) | Payer party legal entity attribute category | |
| PAYEE_PARTY_ATTR_CATEGORY | VARCHAR2 | (150) | Payer party legal entity attribute category | |
| PAYEE_SUPPLIER_ATTR_CATEGORY | VARCHAR2 | (150) | Payer party supplier attribute category | |
| PAYEE_SPPLR_SITE_ATTR_CATEGORY | VARCHAR2 | (150) | Payer partysupplier site attribute category | |
| PAYEE_SUPPLIER_SITE_NAME | VARCHAR2 | (240) | Supplier site name | |
| PAYEE_SUPPLIER_SITE_ALT_NAME | VARCHAR2 | (320) | Supplier site alternate name | |
| PAYEE_SUPPLIER_ID | NUMBER | Supplier alternate name | ||
| LOGICAL_GROUP_REFERENCE | VARCHAR2 | (200) | Indicates the grouping mode - None, Single, Mixed or Grouped. | |
| POSITIVE_PAY_FILE_CREATED_FLAG | VARCHAR2 | (1) | Indicates whether a Positive Pay file is created for a Payment | |
| EXT_INV_PAYEE_ID | NUMBER | (22) | Payee identifier. | |
| INV_PAYEE_PARTY_ID | NUMBER | (22) | Party (trading partner) identifier. | |
| INV_PARTY_SITE_ID | NUMBER | (22) | Party site identifier | |
| INV_SUPPLIER_SITE_ID | NUMBER | (22) | Supplier site identifier. | |
| INV_BENEFICIARY_PARTY | NUMBER | (22) | Beneficiary party | |
| INV_PAYEE_NAME | VARCHAR2 | (360) | Name of party (trading partner) | |
| INV_PAYEE_ADDRESS1 | VARCHAR2 | (240) | Fourth line of party (trading partner) address line 1 | |
| INV_PAYEE_ADDRESS2 | VARCHAR2 | (240) | Fourth line of party (trading partner) address line 2 | |
| INV_PAYEE_ADDRESS3 | VARCHAR2 | (240) | Fourth line of party (trading partner) address line 3 | |
| INV_PAYEE_ADDRESS4 | VARCHAR2 | (240) | Fourth line of party (trading partner) address line 4 | |
| INV_PAYEE_CITY | VARCHAR2 | (120) | Party (trading partner) city. | |
| INV_PAYEE_POSTAL_CODE | VARCHAR2 | (240) | Party (trading partner) postal code. | |
| INV_PAYEE_STATE | VARCHAR2 | (120) | Party (trading partner) state | |
| INV_PAYEE_PROVINCE | VARCHAR2 | (120) | Party (trading partner) province | |
| INV_PAYEE_COUNTY | VARCHAR2 | (120) | Party (trading partner) county. | |
| INV_PAYEE_COUNTRY | VARCHAR2 | (120) | Party (trading partner) country. | |
| INV_PAYEE_PARTY_NAME | VARCHAR2 | (360) | Payee party name. | |
| INV_PAYEE_LE_REG_NUM | VARCHAR2 | (50) | Legal registration number of the Party (trading partner) | |
| INV_PAYEE_TAX_REG_NUM | VARCHAR2 | (50) | Tax registration number of the Party (trading partner) | |
| INV_PAYEE_ADDRESS_CONCAT | VARCHAR2 | (2000) | Payee concatenated standard address fields | |
| INV_BENEFICIARY_NAME | VARCHAR2 | (360) | Payee party number | |
| INV_PAYEE_PARTY_NUMBER | VARCHAR2 | (30) | Party (trading party) number | |
| INV_PAYEE_ALTERNATE_NAME | VARCHAR2 | (320) | Party (trading partner) alternate name | |
| INV_PAYEE_SITE_ALT_NAME | VARCHAR2 | (320) | Party (trading partner) alternate site name | |
| INV_PAYEE_SUPPLIER_NUMBER | VARCHAR2 | (30) | Supplier (Trading Partner) Number. | |
| INV_PAYEE_FIRST_PARTY_REF | VARCHAR2 | (30) | Party (trading partner) reference | |
| EXT_BNK_ACCT_OWNR_INV_PRTY_ID | VARCHAR2 | (360) | Party (trading partner) . | |
| EXT_BNK_BRANCH_INV_PRTY_ID | NUMBER | (15) | Same as inv_payee_party_id | |
| EXT_BNK_ACCT_OWNR_INV_PRTY_NME | VARCHAR2 | (360) | Same as inv_payee_party_name | |
| INV_PAYEE_PARTY_ATTR_CAT | VARCHAR2 | (150) | Payee party category. | |
| INV_PAYEE_SUPPLIER_ATTR_CAT | VARCHAR2 | (150) | Supplier (Trading Partner) attribute category | |
| INV_PAYEE_SPPLR_SITE_ATTR_CAT | VARCHAR2 | (150) | Supplier (Trading Partner) site attribute category | |
| INV_PAYEE_SUPPLIER_SITE_NAME | VARCHAR2 | (150) | Supplier (Trading Partner) site name | |
| INV_PAYEE_SPPLR_SITE_ALT_NAME | VARCHAR2 | (320) | Supplier (Trading Partner) site alternative name | |
| INV_PAYEE_SUPPLIER_ID | NUMBER | (22) | Supplier (Trading Partner) identifier | |
| PAYEE_ADDRESSEE | VARCHAR2 | (360) | Payee Addressee | |
| PAYEE_PARTY_SITE_NAME | VARCHAR2 | (360) | Payee Party site name | |
| INV_PAYEE_PARTY_SITE_NAME | VARCHAR2 | (360) | Invoice Payee party site name | |
| ACKNOWLEDGED_FLAG | VARCHAR2 | (1) | Acknowledged flag | |
| AFFECTS_REJECTION_LEVEL | VARCHAR2 | (1) |
IBY.IBY_PAYMENTS_ALL does not reference any database object
IBY.IBY_PAYMENTS_ALL is referenced by following:
| Description: | 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 |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_PAYMENTS_H.BANK_INSTRUCTION1_CODE | IBY_BANK_INSTRUCTIONS_B |
| IBY_PAYMENTS_H.PAYMENT_REASON_CODE | IBY_PAYMENT_REASONS_B |
| IBY_PAYMENTS_H.PAYMENT_INSTRUCTION_ID | IBY_PAY_INSTRUCTIONS_ALL |
| IBY_PAYMENTS_H.PAYMENT_SERVICE_REQUEST_ID | IBY_PAY_SERVICE_REQUESTS |
| IBY_PAYMENTS_H.PAYMENT_INSTRUCTION_HISTORY_ID | IBY_PAY_INSTRUCTIONS_H |
| IBY_PAYMENTS_H.BANK_INSTRUCTION2_CODE | IBY_BANK_INSTRUCTIONS_B |
| IBY_PAYMENTS_H.COUNTRY | FND_TERRITORIES |
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_DOCUMENTS_PAYABLE_H.PAYMENT_HISTORY_ID | IBY_PAYMENTS_H |
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 payment can exist in this table. These snapshots are differentiated by the table's primary key and a snapshot date.
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYMENT_HISTORY_ID | NUMBER | (15) | Y | System generated primary key |
| PAYMENT_HISTORY_DATE | DATE | Y | Payment snapshot date | |
| PAYMENT_INSTRUCTION_HISTORY_ID | NUMBER | (15) | Y | Associated payment instruction snapshot Identifier |
| PAYMENT_ID | NUMBER | (15) | Y | Payment Identifier |
| PROCESSING_TYPE | VARCHAR2 | (30) | Y | Specifies the type of processing from the payment process profile. Values from the lookup IBY_PROCESSING_TYPES include ELECTRONIC and PRINTED. |
| BILL_PAYABLE_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether a payment is a bill payable |
| EXCLUSIVE_PAYMENT_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether this payment is made up of a single document payable that was meant to be paid alone. |
| PAYMENTS_COMPLETE_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether the payment has been marked as complete. |
| STOP_CONFIRMED_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether a stop has been confirmed on this payment |
| STOP_RELEASED_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether a stop request has been released on this payment |
| STOP_REQUEST_PLACED_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether a stop request has been placed on this payment. |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| DECLARATION_OPTION | VARCHAR2 | (30) | Specifies the customer's chosen declaration option from the payment process profile | |
| DCL_ONLY_FOREIGN_CURR_PMT_FLAG | VARCHAR2 | (1) | Yor N flag to specify whether only foreign currency payments or all payments are declared from the payment process profile | |
| DECLARATION_REPORT_FORMAT_CODE | VARCHAR2 | (30) | Only needed if the DECLARATION_OPTION is set to DECLARE_DIRECT_TO_CENTRAL_BANK from the payment process profile | |
| DECLARATION_CURR_FX_RATE_TYPE | VARCHAR2 | (255) | Indicates the type of exchange rate from the payment process profile | |
| DECLARATION_CURRENCY_CODE | VARCHAR2 | (10) | Currency of the declaration amount | |
| DECLARATION_THRESHOLD_AMOUNT | NUMBER | From the payment process profile, the threshold amount above which the payment needs to be reported to the central bank | ||
| PAYMENT_DETAILS_FORMULA | VARCHAR2 | (240) | From the payment process profile, SQL function used to concatenate the document attributes into the payment details information | |
| BANK_INSTRUCTION1_CODE | VARCHAR2 | (30) | Y | Code of first bank instruction, from the payment process profile |
| BANK_INSTRUCTION2_CODE | VARCHAR2 | (30) | Y | Code of second bank instruction, from the payment process profile |
| BANK_INSTRUCTION_DETAILS | VARCHAR2 | (255) | Additional bank instruction details from the payment process profile | |
| PAYMENT_TEXT_MESSAGE1 | VARCHAR2 | (150) | From the payment process profile, text message for use in payment processing. | |
| PAYMENT_TEXT_MESSAGE2 | VARCHAR2 | (150) | From the payment process profile, text message for use in payment processing. | |
| PAYMENT_SERVICE_REQUEST_ID | NUMBER | (15) | Y | Payment process request Identifier |
| PROCESS_TYPE | VARCHAR2 | (30) | Y | Specifies the process by which the payment is built into a payment instruction. Values from the lookup IBY_PROCESS_TYPES include STANDARD, IMMEDIATE, and MANUAL. |
| PAYMENT_INSTRUCTION_ID | NUMBER | (15) | Y | Payment instruction Identifier |
| PAYMENT_STATUS | VARCHAR2 | (30) | Y | Payment status. Values from the lookup IBY_PAYMENT_STATUSES include CREATED, FORMATTED, and TRANSMITTED. |
| PAYMENT_FUNCTION | VARCHAR2 | (30) | Y | Function or purpose of the payment. Values from the lookup IBY_PAYMENT_FUNCTIONS include SUPPLIER_PAYMENT, CUSTOMER_REFUNDS, and others. |
| PAYMENT_REASON_CODE | VARCHAR2 | (30) | Y | Payment reason code |
| PAYMENT_REASON_COMMENTS | VARCHAR2 | (240) | Y | Free text field available for entering a reason for the payment |
| PAYMENT_DATE | DATE | Payment date | ||
| ANTICIPATED_VALUE_DATE | DATE | Anticipated value date | ||
| PAYMENT_AMOUNT | NUMBER | Y | Amount of the payment | |
| PAYMENT_CURRENCY_CODE | VARCHAR2 | (10) | Y | Currency of the payment |
| MATURITY_DATE | DATE | Calculated maturity date on a bill payable payment, that is, future dated payment | ||
| PAYMENT_DUE_DATE | DATE | Date on which the payment is made | ||
| DECLARE_PAYMENT_FLAG | VARCHAR2 | (1) | Y or N flag that indicates whether this payment needs to be reported to the central bank | |
| DECLARATION_AMOUNT | NUMBER | Sum of all reporting amounts from the documents that constitute this payment. This amount is in the declaration or reporting currency | ||
| DISCOUNT_AMOUNT_TAKEN | NUMBER | Discount amount, in payment currency | ||
| PAYMENT_DETAILS | VARCHAR2 | (240) | Concatenated string that represents the payment details | |
| BANK_CHARGE_BEARER | VARCHAR2 | (30) | Bearer of bank charge cost. Bank charge bearers are defined as the lookup IBY_BANK_CHARGE_BEARER. | |
| BANK_CHARGE_AMOUNT | NUMBER | Bank charge amount in the payment currency | ||
| DELIVERY_FORMAT_VALUE | VARCHAR2 | (80) | Y | Delivery value required by the payment format that uses this delivery channel |
| SETTLEMENT_PRIORITY | VARCHAR2 | (30) | Priority with which the financial institution or payment system settles payment for this document. The available values for this column come from the FND lookup IBY_SETTLEMENT_PRIORITY. | |
| REMITTANCE_MESSAGE1 | VARCHAR2 | (150) | Remittance message for use in payment processing | |
| REMITTANCE_MESSAGE2 | VARCHAR2 | (150) | Remittance message for use in payment processing | |
| REMITTANCE_MESSAGE3 | VARCHAR2 | (150) | Remittance message for use in payment processing | |
| PAPER_DOCUMENT_NUMBER | NUMBER | (15) | Payment document number, if a printed payment | |
| BANK_ASSIGNED_REF_CODE | VARCHAR2 | (30) | Bank-provided reference code for this payment | |
| INT_BANK_ACCOUNT_NUMBER | VARCHAR2 | (30) | Internal bank account number from CE bank accounts | |
| INT_BANK_ACCOUNT_ROUTING_NUM | VARCHAR2 | (30) | Internal bank account routing number from CE bank accounts | |
| INT_BANK_ACCOUNT_IBAN_NUMBER | VARCHAR2 | (50) | Internal bank account IBAN number from CE bank accounts | |
| EXT_BANK_ACCOUNT_NUMBER | VARCHAR2 | (100) | External bank account number from IBY bank accounts | |
| EXT_BANK_ACCOUNT_ROUTING_NUM | VARCHAR2 | (30) | External bank account routing number from CE bank accounts | |
| EXT_BANK_ACCOUNT_BANK_NAME | VARCHAR2 | (360) | Internal bank account bank name from IBY bank accounts | |
| EXT_BANK_ACCOUNT_BRANCH_NAME | VARCHAR2 | (360) | Internal bank account branch name from IBY bank accounts | |
| EXT_BANK_ACCOUNT_BRANCH_NUMBER | VARCHAR2 | (30) | Internal bank account branch number from IBY bank accounts | |
| EXT_BANK_ACCOUNT_IBAN_NUMBER | VARCHAR2 | (50) | Internal bank account IBAN number from IBY bank accounts | |
| EXT_BANK_ACCOUNT_SWIFT_CODE | VARCHAR2 | (30) | Internal bank account SWIFT code from IBY bank accounts | |
| EXT_PAYEE_ID | NUMBER | (15) | External payee Identifier | |
| PAYEE_PARTY_ID | NUMBER | (15) | TCA party Identifier | |
| PARTY_SITE_ID | NUMBER | (15) | Payee party site Identifier | |
| SUPPLIER_SITE_ID | NUMBER | (15) | Supplier site Identifier | |
| BENEFICIARY_PARTY | NUMBER | (15) | Beneficiary party if payment is made through a third party | |
| ORG_ID | NUMBER | (15) | Y | Organization Identifier |
| ORG_TYPE | VARCHAR2 | (30) | Organization type. Values from the lookup IBY_ORGANIZATION_TYPES nclude Operating Unit, Business Group, and Legal Entity. | |
| ORG_NAME | VARCHAR2 | (240) | Y | Organization name from HR organizations |
| LEGAL_ENTITY_ID | NUMBER | (15) | Y | Legal entity Identifier |
| PARTY_NAME | VARCHAR2 | (360) | Name of party from TCA parties | |
| COUNTRY | VARCHAR2 | (60) | Y | Country code from the TERRITORY_CODE column in the FND_TERRITORY table from TCA location |
| ADDRESS1 | VARCHAR2 | (240) | First line for address from TCA location | |
| ADDRESS2 | VARCHAR2 | (240) | Second line for address from TCA location | |
| ADDRESS3 | VARCHAR2 | (240) | Third line for address from TCA location | |
| ADDRESS4 | VARCHAR2 | (240) | Fourth line for address from TCA location | |
| CITY | VARCHAR2 | (60) | City from TCA location | |
| POSTAL_CODE | VARCHAR2 | (60) | Postal code from TCA location | |
| POSTAL_PLUS4_CODE | VARCHAR2 | (10) | Four digit extension to the United States Postal ZIP code from TCA location | |
| STATE | VARCHAR2 | (60) | State from TCA location | |
| PROVINCE | VARCHAR2 | (60) | Province from TCA location | |
| COUNTY | VARCHAR2 | (60) | County from TCA location | |
| UNIQUE_REMITTANCE_IDENTIFIER | VARCHAR2 | (30) | Unique remittance Identifier provided by the payee | |
| URI_CHECK_DIGIT | VARCHAR2 | (2) | Unique remittance Identifier check digit | |
| DOCUMENT_CATEGORY_CODE | VARCHAR2 | (30) | Document category code | |
| DOCUMENT_SEQUENCE_ID | NUMBER | Document Sequence ID | ||
| DOCUMENT_SEQUENCE_VALUE | NUMBER | Document sequence value | ||
| STOP_CONFIRMED_BY | NUMBER | (15) | User who confirmed the stop | |
| STOP_CONFIRM_DATE | DATE | Date on which the stop was confirmed | ||
| STOP_CONFIRM_REASON | VARCHAR2 | (240) | Reason for confirming the stop | |
| STOP_CONFIRM_REFERENCE | VARCHAR2 | (100) | Payment system reference code for the confirmed stop payment | |
| STOP_RELEASED_BY | NUMBER | (15) | User who released the stop request | |
| STOP_RELEASE_DATE | DATE | Date on which the stop request was released | ||
| STOP_RELEASE_REASON | VARCHAR2 | (240) | Reason for releasing the stop request | |
| STOP_RELEASE_REFERENCE | VARCHAR2 | (100) | Payment system reference code for releasing or denying the stop request. | |
| STOP_REQUEST_DATE | DATE | Date on which the stop request was placed | ||
| STOP_REQUEST_PLACED_BY | NUMBER | (15) | User who placed the stop request | |
| STOP_REQUEST_REASON | VARCHAR2 | (240) | Reason for placing the stop request | |
| STOP_REQUEST_REFERENCE | VARCHAR2 | (100) | Payment system reference code for the stop request | |
| VOIDED_BY | NUMBER | (15) | User who voided the payment | |
| VOID_DATE | DATE | Date on which the payment was voided | ||
| VOID_REASON | VARCHAR2 | (240) | Reason for voiding the payment | |
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | Descriptive Flexfield structure defining column | |
| ATTRIBUTE1 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE2 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE3 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE4 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE5 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE6 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE7 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE8 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE9 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE10 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE11 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE12 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE13 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE14 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE15 | VARCHAR2 | (150) | Descriptive Flexfield segment |
IBY.IBY_PAYMENTS_H does not reference any database object
IBY.IBY_PAYMENTS_H is referenced by following:
| Description: | IBY_PAYMENT_METHODS stores the payment methods that Oracle Payments supports. A payment method is a payment attribute on a document payable that indicates how the first party payer is going to make the payment. Examples of payment methods i |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_APPLICABLE_PMT_MTHDS.PAYMENT_METHOD_CODE | IBY_PAYMENT_METHODS_B |
| IBY_DOCS_PAYABLE_ALL.PAYMENT_METHOD_CODE | IBY_PAYMENT_METHODS_B |
| IBY_DOCUMENTS_PAYABLE_H.PAYMENT_METHOD_CODE | IBY_PAYMENT_METHODS_B |
| IBY_EXTERNAL_PAYEES_ALL.DEFAULT_PAYMENT_METHOD_CODE | IBY_PAYMENT_METHODS_B |
| IBY_EXT_PARTY_PMT_MTHDS.PAYMENT_METHOD_CODE | IBY_PAYMENT_METHODS_B |
| IBY_PAYMENTS_ALL.PAYMENT_METHOD_CODE | IBY_PAYMENT_METHODS_B |
| IBY_PAYMENT_METHODS_TL.PAYMENT_METHOD_CODE | IBY_PAYMENT_METHODS_B |
| IBY_PAYMENT_RULES.PAYMENT_METHOD_CODE | IBY_PAYMENT_METHODS_B |
| IBY_TEMP_EXT_PAYEES.DEFAULT_PAYMENT_METHOD_CODE | IBY_PAYMENT_METHODS_B |
| IBY_VAL_ASSIGNMENTS.PAYMENT_METHOD_CODE | IBY_PAYMENT_METHODS_B |
IBY_PAYMENT_METHODS stores the payment methods that Oracle Payments supports. A payment method is a payment attribute on a document payable that indicates how the first party payer is going to make the payment. Examples of payment methods include printing paper checks in-house, outsourcing checks to be printed by a payment system, and wiring money. A payment method can be very generic, such as EFT, or very specific, such as EFT in Denmark via Citibank using the EDIFACT format. Some payment methods are seeded, but implementers may define their own payment methods. This table corresponds to the Payment Methods pages.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_PAYMENT_METHODS_B_U1 | UNIQUE | APPS_TS_TX_IDX |
PAYMENT_METHOD_CODE
ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYMENT_METHOD_CODE | VARCHAR2 | (30) | Y | User entered primary key |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number | |
| SEEDED_FLAG | VARCHAR2 | (1) | Y or N flag controlling updatability of records. Y indicates record was seeded by Oracle and may have user updates limited. | |
| BANK_CHARGE_BEARER_APL_FLAG | VARCHAR2 | (1) | Y | Indicates whether the bank charge bearer attribute is mandatory, optional or non-applicable to this payment method. The default setting is disabled. |
| PAYMENT_REASON_APL_FLAG | VARCHAR2 | (1) | Y | Indicates whether the payment reason attribute is mandatory, optional, or non-applicable to this payment method. The default setting is disabled. |
| PAYMENT_REASON_COMNT_APL_FLAG | VARCHAR2 | (1) | Y | Indicates whether the payment reason comment attribute is mandatory, optional, or non-applicable to this payment method. The default setting is disabled. |
| REMITTANCE_MESSAGE1_APL_FLAG | VARCHAR2 | (1) | Y | Indicates whether the remittance message1 attribute is mandatory, optional, or non-applicable to this payment method. The default setting is optional. |
| REMITTANCE_MESSAGE2_APL_FLAG | VARCHAR2 | (1) | Y | Indicates whether the remittance message2 attribute is mandatory, optional, or non-applicable to this payment method. The default setting is disabled. |
| REMITTANCE_MESSAGE3_APL_FLAG | VARCHAR2 | (1) | Y | Indicates whether the remittance message3 attribute is mandatory, optional, or non-applicable to this payment method. The default setting is disabled. |
| UNIQUE_REMITTANCE_ID_APL_FLAG | VARCHAR2 | (1) | Y | Indicates whether the unique remittance identifier attribute is mandatory, optional, or non-applicable to this payment method. The default setting is disabled. |
| URI_CHECK_DIGIT_APL_FLAG | VARCHAR2 | (1) | Y | Indicates whether the URI check digit attribute is mandatory, optional, or non-applicable to this payment method. The default setting is disabled. |
| DELIVERY_CHANNEL_APL_FLAG | VARCHAR2 | (1) | Y | Indicates whether the delivery channel attribute is mandatory, optional, or non-applicable to this payment method. The default setting is optional. |
| PAYMENT_FORMAT_APL_FLAG | VARCHAR2 | (1) | Y | Indicates whether the payment format attribute is mandatory, optional, or non-applicable to this payment method. The default setting is disabled. |
| SETTLEMENT_PRIORITY_APL_FLAG | VARCHAR2 | (1) | Y | Indicates whether the settlement priority attribute is mandatory, optional, or non-applicable to this payment method. The default setting is disabled. |
| EXCLUSIVE_PMT_APL_FLAG | VARCHAR2 | (1) | Y | Indicates whether the pay alone attribute is mandatory, optional, or non-applicable to this payment method. The default setting is disabled. |
| EXTERNAL_BANK_ACCT_APL_FLAG | VARCHAR2 | (1) | Y | Indicates whether the external bank account attribute is mandatory, optional, or non-applicable to this payment method. The default setting is disabled. |
| SUPPORT_BILLS_PAYABLE_FLAG | VARCHAR2 | (1) | Y | Indicates whether this payment method can be used to issue bills payable, that is future dated payments |
| DOCUMENT_CATEGORY_CODE | VARCHAR2 | (30) | Document category code that is linked to a payment method. Document category codes are used in providing document sequence numbers for payments. | |
| MATURITY_DATE_OFFSET_DAYS | NUMBER | (15) | With this payment method, number of days to be added to the payment date on a payment, which determines its maturity date | |
| INACTIVE_DATE | DATE | Inactive date | ||
| ANTICIPATED_FLOAT | NUMBER | (15) | Days added to the payment date for use in cash forecasting | |
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | Descriptive Flexfield structure defining column | |
| ATTRIBUTE1 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE2 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE3 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE4 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE5 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE6 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE7 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE8 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE9 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE10 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE11 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE12 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE13 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE14 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE15 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| FORMAT_VALUE | VARCHAR2 | (80) | Value used in the formatted payment instruction | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_PAYMENT_METHODS_B does not reference any database object
IBY.IBY_PAYMENT_METHODS_B is referenced by following:
| Description: | IBY_PAYMENT_METHODS stores the payment methods that Oracle Payments supports. A payment method is a payment attribute on a document payable that indicates how the first party payer is going to make the payment. Examples of payment methods i |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_PAYMENT_METHODS_TL.PAYMENT_METHOD_CODE | IBY_PAYMENT_METHODS_B |
IBY_PAYMENT_METHODS stores the payment methods that Oracle Payments supports. A payment method is a payment attribute on a document payable that indicates how the first party payer is going to make the payment. Examples of payment methods include printing paper checks in-house, outsourcing checks to be printed by a payment system, and wiring money. A payment method can be very generic, such as EFT, or very specific, such as EFT in Denmark via Citibank using the EDIFACT format. Some payment methods are seeded, but implementers may define their own payment methods. This table corresponds to the Payment Methods pages.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_PAYMENT_METHODS_TL_U1 | UNIQUE | APPS_TS_TX_IDX |
PAYMENT_METHOD_CODE
LANGUAGE ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYMENT_METHOD_CODE | VARCHAR2 | (30) | Y | User entered primary key |
| LANGUAGE | VARCHAR2 | (4) | Y | Language code |
| SOURCE_LANG | VARCHAR2 | (4) | Y | Language code of the record's current language |
| PAYMENT_METHOD_NAME | VARCHAR2 | (100) | Y | Payment method name |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number | |
| DESCRIPTION | VARCHAR2 | (240) | Free text description of the payment method | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_PAYMENT_METHODS_TL does not reference any database object
IBY.IBY_PAYMENT_METHODS_TL is referenced by following:
| Description: | IBY_PAYMENT_REASONS stores payment reasons that are used as lookup values for payee records or documents payable, that is, invoices. This table is similar to FND_LOOKUPS, but with a new column for territory identification. Products that use |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_PAYMENT_REASONS_B.TERRITORY_CODE | FND_TERRITORIES |
| Foreign Key Column | Foreign Table |
|---|---|
| FV_PB_SEQ_ASSIGNMENTS_ALL.PAYMENT_REASON_CODE | IBY_PAYMENT_REASONS_B |
| FV_TOP_EXCLUSION_CRITERIA_ALL.PAYMENT_REASON_CODE | IBY_PAYMENT_REASONS_B |
| IBY_DOCS_PAYABLE_ALL.PAYMENT_REASON_CODE | IBY_PAYMENT_REASONS_B |
| IBY_EXTERNAL_PAYEES_ALL.PAYMENT_REASON_CODE | IBY_PAYMENT_REASONS_B |
| IBY_PAYMENTS_ALL.PAYMENT_REASON_CODE | IBY_PAYMENT_REASONS_B |
| IBY_PAYMENTS_H.PAYMENT_REASON_CODE | IBY_PAYMENT_REASONS_B |
| IBY_PAYMENT_REASONS_TL.PAYMENT_REASON_CODE | IBY_PAYMENT_REASONS_B |
| IBY_PAY_INSTRUCTIONS_ALL.PAYMENT_REASON_CODE | IBY_PAYMENT_REASONS_B |
| IBY_PAY_INSTRUCTIONS_H.PAYMENT_REASON_CODE | IBY_PAYMENT_REASONS_B |
| IBY_TEMP_EXT_PAYEES.PAYMENT_REASON_CODE | IBY_PAYMENT_REASONS_B |
IBY_PAYMENT_REASONS stores payment reasons that are used as lookup values for payee records or documents payable, that is, invoices. This table is similar to FND_LOOKUPS, but with a new column for territory identification. Products that use data in this table can code their LOVs to be sensitive to the country context so that only values relevant for the country will appear. This table corresponds to the Payment Reason Codes page.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_PAYMENT_REASONS_B_U1 | UNIQUE | APPS_TS_TX_IDX |
PAYMENT_REASON_CODE
ZD_EDITION_NAME |
| IBY_PAYMENT_REASONS_B_N1 | NONUNIQUE | APPS_TS_TX_IDX | TERRITORY_CODE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYMENT_REASON_CODE | VARCHAR2 | (30) | Y | User entered primary key |
| FORMAT_VALUE | VARCHAR2 | (80) | Value required by the payment format that uses this payment reason | |
| SEEDED_FLAG | VARCHAR2 | (1) | Y or N flag controlling updatability of records. Y indicates record was seeded by Oracle and may have user updates limited. | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number | |
| INACTIVE_DATE | DATE | Inactive date | ||
| TERRITORY_CODE | VARCHAR2 | (2) | Code of the country where the payment reason code is assigned or used | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_PAYMENT_REASONS_B does not reference any database object
IBY.IBY_PAYMENT_REASONS_B is referenced by following:
| Description: | IBY_PAYMENT_REASONS stores payment reasons that are used as lookup values for payee records or documents payable, that is, invoices. This table is similar to FND_LOOKUPS, but with a new column for territory identification. Products that use |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_PAYMENT_REASONS_TL.PAYMENT_REASON_CODE | IBY_PAYMENT_REASONS_B |
IBY_PAYMENT_REASONS stores payment reasons that are used as lookup values for payee records or documents payable, that is, invoices. This table is similar to FND_LOOKUPS, but with a new column for territory identification. Products that use data in this table can code their LOVs to be sensitive to the country context so that only values relevant for the country will appear. This table corresponds to the Payment Reason Codes page.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_PAYMENT_REASONS_TL_U1 | UNIQUE | APPS_TS_TX_IDX |
PAYMENT_REASON_CODE
LANGUAGE ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYMENT_REASON_CODE | VARCHAR2 | (30) | Y | User entered primary key |
| LANGUAGE | VARCHAR2 | (4) | Y | Language code |
| SOURCE_LANG | VARCHAR2 | (4) | Y | Language code of the record's current language |
| MEANING | VARCHAR2 | (80) | Lookup meaning of payment reasons | |
| DESCRIPTION | VARCHAR2 | (240) | Lookup description of payment reason | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_PAYMENT_REASONS_TL does not reference any database object
IBY.IBY_PAYMENT_REASONS_TL is referenced by following:
| Description: | IBY_PAYMENT_REFERENCES stores the current payment reference number. Payment reference numbers are outward facing identifiers assigned to payments during payment instruction creation. |
|---|
IBY_PAYMENT_REFERENCES stores the current payment reference number. Payment reference numbers are outward facing identifiers assigned to payments during payment instruction creation.
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| LAST_USED_REF_NUMBER | NUMBER | (15) | Y | Last used payment reference number |
| LAST_AVAILABLE_REF_NUMBER | NUMBER | (15) | Last available payment reference number | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version Number |
IBY.IBY_PAYMENT_REFERENCES does not reference any database object
IBY.IBY_PAYMENT_REFERENCES is referenced by following:
| Description: | IBY_PAYMENT_RULES stores the header-level information for a payment method defaulting rule. A defaulting rule enables the user to define the default payment method with respect to multiple factors of a transaction context. A defaulting rule |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_PAYMENT_RULES.PAYMENT_METHOD_CODE | IBY_PAYMENT_METHODS_B |
| IBY_PAYMENT_RULES.APPLICATION_ID | FND_APPLICATION |
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_RULE_CONDITIONS.PAYMENT_RULE_ID | IBY_PAYMENT_RULES |
IBY_PAYMENT_RULES stores the header-level information for a payment method defaulting rule. A defaulting rule enables the user to define the default payment method with respect to multiple factors of a transaction context. A defaulting rule has one or more rule conditions stored in the IBY_RULE_CONDITIONS table. Each rule has a priority value. Rules are evaluated in the order of their priority. Higher priority ones with smaller integer values are evaluated first. If a match is found, the lower priority ones are not evaluated. This table corresponds to the Payment Method Defaulting Rules page.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_PAYMENT_RULES_U1 | UNIQUE | APPS_TS_TX_IDX | PAYMENT_RULE_ID |
| IBY_PAYMENT_RULES_N1 | NONUNIQUE | APPS_TS_TX_IDX | APPLICATION_ID |
| IBY_PAYMENT_RULES_N2 | NONUNIQUE | APPS_TS_TX_IDX | PAYMENT_METHOD_CODE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYMENT_RULE_ID | NUMBER | (15) | Y | System generated primary key |
| PAYMENT_RULE_NAME | VARCHAR2 | (240) | Y | Rule name |
| PAYMENT_METHOD_CODE | VARCHAR2 | (30) | Y | Payment method Identifier. Although this field is nullable at database level, a value is always be entered. |
| PAYMENT_RULE_PRIORITY | NUMBER | (15) | Y | Rule priority. Smaller number has higher priority. |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number | |
| APPLICATION_ID | NUMBER | (15) | Y | Application Identifier of the calling product. Although this field is nullable at database level, a value is always be entered. |
IBY.IBY_PAYMENT_RULES does not reference any database object
IBY.IBY_PAYMENT_RULES is referenced by following:
| Description: | Stores batch level payment information as submitted by payable programs |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
|
IBY_PAY_BATCHES_ALL.IBY_BATCH_ID
IBY_PAY_BATCHES_ALL.PAYER_ID |
IBY_BATCHES_ALL |
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_PAY_PAYMENTS_ALL.BATCH_ID | IBY_PAY_BATCHES_ALL |
IBY_PAY_BATCHES_ALL is used to store the batch level payment information submitted by payable programs such Oracle Payables. This includes the paying party, originating bank and bank account, and various batch summary information. If batch merge is enabled, the IBY_BATCH_ID will point to the parent batch in IBY_BATCHES_ALL that the payable batch is merged to. The payment requests are submitted through iPayment PL/SQL APIs. For Oracle Payables, each row in this table corresponds to a row in AP_INV_SELECTION_CRITERIA_ALL.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_PAY_BATCHES_ALL_PK | UNIQUE | APPS_TS_TX_IDX | BATCH_ID |
| IBY_PAY_BATCHES_ALL_N1 | NONUNIQUE | APPS_TS_TX_IDX | BATCH_STATUS |
| IBY_PAY_BATCHES_ALL_N10 | NONUNIQUE | APPS_TS_TX_IDX | PMT_BATCH_NAME |
| IBY_PAY_BATCHES_ALL_N11 | NONUNIQUE | APPS_TS_TX_IDX | PMT_METHOD |
| IBY_PAY_BATCHES_ALL_N2 | NONUNIQUE | APPS_TS_TX_IDX | BEPID |
| IBY_PAY_BATCHES_ALL_N3 | NONUNIQUE | APPS_TS_TX_IDX | CUST_NAME |
| IBY_PAY_BATCHES_ALL_N4 | NONUNIQUE | APPS_TS_TX_IDX | IBY_BATCH_ID |
| IBY_PAY_BATCHES_ALL_N5 | NONUNIQUE | APPS_TS_TX_IDX | ORIG_BANK_ACCT_NUMBER |
| IBY_PAY_BATCHES_ALL_N6 | NONUNIQUE | APPS_TS_TX_IDX | ORIG_BANK_BRANCH_NUM |
| IBY_PAY_BATCHES_ALL_N7 | NONUNIQUE | APPS_TS_TX_IDX | ORIG_BANK_NAME |
| IBY_PAY_BATCHES_ALL_N8 | NONUNIQUE | APPS_TS_TX_IDX | ORIG_BANK_NUMBER |
| IBY_PAY_BATCHES_ALL_N9 | NONUNIQUE | APPS_TS_TX_IDX | PAYER_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PMT_BATCH_REQUEST_ID | NUMBER | (15) | The parent concurrent request which initiated the payment request that submitted the batch to iPayment. For Oracle Payables, this is the Payment Process Manager request | |
| PAYER_ID | VARCHAR2 | (80) | Y | Payer identifier. The payer you registered in iPayment |
| MPAYER_ID | NUMBER | (15) | Payer identifier. Primary key of IBY_PAYEE | |
| BATCH_ID | NUMBER | (15) | Y | System generated primary key |
| IBY_BATCH_ID | VARCHAR2 | (80) | Merged parent batch in IBY_BATCHES_ALL | |
| IBY_MBATCH_ID | NUMBER | (15) | Merged parent batch in IBY_BATCHES_ALL. Primary key of IBY_BATCHES_ALL | |
| ECAPP_ID | NUMBER | (15) | Y | EC application registration Identifier. For Oracle Applications such as Oracle Payables, this is the APPLICATION_ID in FND_APPLICATION for the corresponding app |
| BEPID | NUMBER | (15) | Back-end Payment System Identifier. Foreign key to IBY_BEPINFO. This is the third party bank or payment processor that will process the payment request | |
| BEPKEY | VARCHAR2 | (80) | Payment System Merchant Identifier | |
| CUST_ID | NUMBER | (15) | Customer identifier from the external calling payable program. For Oracle Payables, this is the ORG_ID of the payment request originating operating unit | |
| CUST_NAME | VARCHAR2 | (240) | Name of the paying customer. For Oracle Payables, this is the orgnization name (HR_ALL_ORGNIZATION_UNITS.NAME) for which the payable request is originated. | |
| CUST_ADDR1 | VARCHAR2 | (240) | Address line1 of the paying customer. For Oracle Payables, this is the default org location (HR_LOCATIONS_ALL) associated with the operating unit. | |
| CUST_ADDR2 | VARCHAR2 | (240) | Address line2 of the paying customer. For Oracle Payables, this is the default org location (HR_LOCATIONS_ALL) associated with the operating unit. | |
| CUST_ADDR3 | VARCHAR2 | (240) | Address line3 of the paying customer. For Oracle Payables, this is the default org location (HR_LOCATIONS_ALL) associated with the operating unit. | |
| CUST_ADDR_CITY | VARCHAR2 | (240) | City of the paying customer | |
| CUST_ADDR_COUNTY | VARCHAR2 | (240) | County (US, UK); Province (CA) | |
| CUST_ADDR_STATE | VARCHAR2 | (240) | State or Province of the paying customer | |
| CUST_ADDR_ZIP | VARCHAR2 | (240) | Zip code of the paying customer | |
| CUST_ADDR_COUNTRY | VARCHAR2 | (240) | Country code of the paying customer | |
| CUST_ADDR_ADDN | VARCHAR2 | (240) | Additional address segment | |
| ORIG_BANK_NAME | VARCHAR2 | (60) | Y | Paying customer bank name. AP_BANK_BRANCHES.BANK_NAME |
| ORIG_BANK_NUMBER | VARCHAR2 | (30) | AP_BANK_BRANCHES.BANK_NUMBER. Holds the number by some countries to identify bank. | |
| ORIG_BANK_BRANCH_NAME | VARCHAR2 | (60) | Y | AP_BANK_BRANCHES.BANK_BRANCH_NAME. |
| ORIG_BANK_BRANCH_TYPE | VARCHAR2 | (25) | AP_BANK_BRANCHES.BANK_BRANCH_TYPE. Indicates which list the bank routing number is on. Valid values are ABA, CHIPS, SWIFT and OTHER. | |
| ORIG_BANK_BRANCH_NUM | VARCHAR2 | (25) | AP_BANK_BRANCHES.BANK_NUM. Bank branch number. | |
| ORIG_EFT_SWIFT_CODE | VARCHAR2 | (12) | AP_BANK_BRANCHES.EFT_SWIFT_CODE | |
| ORIG_BANK_ACCOUNT_NAME | VARCHAR2 | (80) | Y | Paying customer bank account name. AP_BANK_ACCOUNTS_ALL.BANK_ACCOUNT_NAME |
| ORIG_BANK_ACCT_NUMBER | VARCHAR2 | (30) | Y | Paying customer bank account number. AP_BANK_ACCOUNTS_ALL.BANK_ACCOUNT_NUM |
| ORIG_BANK_ACCT_CHECK_DIGITS | VARCHAR2 | (30) | AP_BANK_ACCOUNTS_ALL.CHECK_DIGITS | |
| ORIG_BANK_ACCT_TYPE | VARCHAR2 | (25) | Paying customer bank account type. AP_BANK_ACCOUNTS_ALL.BANK_ACCOUNT_TYPE | |
| ORIG_BANK_ADDR_LINE1 | VARCHAR2 | (35) | AP_BANK_BRANCHES.ADDRESS_LINE1 | |
| ORIG_BANK_ADDR_CITY | VARCHAR2 | (25) | AP_BANK_BRANCHES.CITY | |
| ORIG_BANK_ADDR_STATE | VARCHAR2 | (25) | AP_BANK_BRANCHES.STATE | |
| ORIG_BANK_ADDR_ZIP | VARCHAR2 | (20) | AP_BANK_BRANCHES.ZIP | |
| ORIG_COUNTRY_CODE | VARCHAR2 | (25) | AP_BANK_BRANCHES.COUNTRY | |
| PMT_METHOD | VARCHAR2 | (25) | AP_INV_SELECTION_CRITERIA_ALL.PAYMENT_METHOD_LOOKUP_CODE. Only CHECK, WIRE, and EFT are supported | |
| CURRENCY_CODE | VARCHAR2 | (15) | Y | AP_INV_SELECTION_CRITERIA_ALL.CURRENCY_CODE |
| REF_CURRENCY_CODE | VARCHAR2 | (15) | not used | |
| DOC_ORDER_LOOKUP_CODE | VARCHAR2 | (25) | AP_INV_SELECTION_CRITERIA_ALL.DOCUMENT_ORDER_LOOKUP_CODE | |
| NUM_OF_TRXNS | NUMBER | (15) | Y | Number of transactions in this payment batch |
| BATCH_TOTAL | NUMBER | Y | total payment amount of the batch | |
| BATCH_STATUS | NUMBER | Y | batch status | |
| REQUEST_DATE | DATE | Y | date and time when the batch is submitted to iPayment | |
| PMT_BATCH_NAME | VARCHAR2 | (80) | Y | Batch name as given in Oracle Payables. |
| PMT_BATCH_SET_ID | NUMBER | (15) | AP_INV_SELECTION_CRITERIA_ALL.BATCH_SET_ID | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Application level record locking for three tier stateless applications | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| ERROR_LOCATION | NUMBER | Identifies the location of error | ||
| ORG_ID | NUMBER | (15) | AP_INV_SELECTION_CRITERIA_ALL.ORG_ID | |
| BEP_CODE | VARCHAR2 | (80) | Error code from Back End Payment System | |
| BEP_MESSAGE | VARCHAR2 | (1024) | Error message from Back End Payment System |
IBY.IBY_PAY_BATCHES_ALL does not reference any database object
IBY.IBY_PAY_BATCHES_ALL is referenced by following:
| Description: |
|---|
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_PAY_DASHBOARD_GT_N1 | NONUNIQUE | CHECKRUN_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYMENT_SERVICE_REQUEST_ID | NUMBER | (15) | ||
| CHECKRUN_ID | NUMBER | (15) | ||
| CHECKRUN_NAME | VARCHAR2 | (255) | Y | |
| STATE | VARCHAR2 | (30) | Y |
APPS.IBY_PAY_DASHBOARD_GT does not reference any database object
APPS.IBY_PAY_DASHBOARD_GT is referenced by following:
| Description: | "This table contains records of the payment instructions. Instructions are created based on the Payment Process Request options. Data is inserted in to the table IBY_PAY_INSTRUCTIONS_AL after payment instruction creation, based on the opt |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_PAY_INSTRUCTIONS_ALL.PAYMENT_PROFILE_ID | IBY_ACCT_PMT_PROFILES_B |
| IBY_PAY_INSTRUCTIONS_ALL.PAYMENT_SERVICE_REQUEST_ID | IBY_PAY_SERVICE_REQUESTS |
| IBY_PAY_INSTRUCTIONS_ALL.PAYMENT_REASON_CODE | IBY_PAYMENT_REASONS_B |
| IBY_PAY_INSTRUCTIONS_ALL.INTERNAL_BANK_ACCOUNT_ID | CE_BANK_ACCOUNTS |
| Foreign Key Column | Foreign Table |
|---|---|
| AP_CHECKS_ALL.PAYMENT_INSTRUCTION_ID | IBY_PAY_INSTRUCTIONS_ALL |
| FV_SUMMARY_CONSOLIDATE_ALL.PAYMENT_INSTRUCTION_ID | IBY_PAY_INSTRUCTIONS_ALL |
| FV_TP_TS_AMT_DATA.PAYMENT_INSTRUCTION_ID | IBY_PAY_INSTRUCTIONS_ALL |
| IBY_INSTRUCT_SOURCE_APPS.PAYMENT_INSTRUCTION_ID | IBY_PAY_INSTRUCTIONS_ALL |
| IBY_PAYMENTS_ALL.PAYMENT_INSTRUCTION_ID | IBY_PAY_INSTRUCTIONS_ALL |
| IBY_PAYMENTS_H.PAYMENT_INSTRUCTION_ID | IBY_PAY_INSTRUCTIONS_ALL |
| JL_AR_AP_AWT_CERTIF_ALL.PAYMENT_INSTRUCTION_ID | IBY_PAY_INSTRUCTIONS_ALL |
IBY_PAY_INSTRUCTIONS_ALL stores information on payment instructions. A payment instruction is a set of one or more payments submitted together to a payment system. This table corresponds to the Payment Instructions tab of the Funds Disbursement Process Home.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_PAY_INSTRUCTIONS_ALL_U1 | UNIQUE | APPS_TS_TX_IDX | PAYMENT_INSTRUCTION_ID |
| IBY_PAY_INSTRUCTIONS_ALL_N1 | NONUNIQUE | APPS_TS_TX_IDX | PAYMENT_PROFILE_ID |
| IBY_PAY_INSTRUCTIONS_ALL_N10 | NONUNIQUE | APPS_TS_TX_IDX | LAST_UPDATE_DATE |
| IBY_PAY_INSTRUCTIONS_ALL_N11 | NONUNIQUE | APPS_TS_TX_IDX |
PAYMENT_INSTRUCTION_ID
PAYMENT_INSTRUCTION_STATUS PAYMENTS_COMPLETE_CODE |
| IBY_PAY_INSTRUCTIONS_ALL_N2 | NONUNIQUE | APPS_TS_TX_IDX | PAYMENT_DATE |
| IBY_PAY_INSTRUCTIONS_ALL_N3 | NONUNIQUE | APPS_TS_TX_IDX | PAYMENT_SERVICE_REQUEST_ID |
| IBY_PAY_INSTRUCTIONS_ALL_N4 | NONUNIQUE | APPS_TS_TX_IDX | PAYMENT_REASON_CODE |
| IBY_PAY_INSTRUCTIONS_ALL_N5 | NONUNIQUE | APPS_TS_TX_IDX | INTERNAL_BANK_ACCOUNT_ID |
| IBY_PAY_INSTRUCTIONS_ALL_N6 | NONUNIQUE | APPS_TS_TX_IDX | PAYMENT_INSTRUCTION_STATUS |
| IBY_PAY_INSTRUCTIONS_ALL_N7 | NONUNIQUE | APPS_TS_TX_IDX | BANK_ASSIGNED_REF_CODE |
| IBY_PAY_INSTRUCTIONS_ALL_N8 | NONUNIQUE | APPS_TS_TX_IDX | PAY_ADMIN_ASSIGNED_REF_CODE |
| IBY_PAY_INSTRUCTIONS_ALL_N9 | NONUNIQUE | APPS_TS_TX_IDX | CREATION_DATE |
| IBY_PAY_INSTRUCTIONS_ALL_U2 | NONUNIQUE | APPS_TS_TX_IDX |
PAYMENT_INSTRUCTION_ID
PAYMENT_INSTRUCTION_STATUS |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYMENT_INSTRUCTION_ID | NUMBER | (15) | Y | Unique internal Identifier for this record. Generated using a database sequence. |
| PAYMENT_PROFILE_ID | NUMBER | (15) | Y | Payment process profile Identifier |
| PROCESS_TYPE | VARCHAR2 | (30) | Y | Specifies the process by which payments are built into payment instructions. Values from the lookup IBY_PROCESS_TYPES include STANDARD, IMMEDIATE, and MANUAL. |
| PAYMENT_INSTRUCTION_STATUS | VARCHAR2 | (30) | Y | Payment instruction status. Values from the lookup IBY_PAY_INSTRUCTION_STATUSES include CREATED, FORMATTED, and TRANSMITTED. |
| PAYMENTS_COMPLETE_CODE | VARCHAR2 | (30) | Y | Code indicating whether payments in the payment instruction have been marked as complete. Values from the lookup IBY_PAYMENTS_COMPLETE include YES, NO, and PARTIAL. |
| GENERATE_SEP_REMIT_ADVICE_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether a separate remittance advice needs to be created for a payment instruction. If the flag is set to Y, then at least one payment within the payment instruction requires a separate remittance advice. |
| REMITTANCE_ADVICE_CREATED_FLAG | VARCHAR2 | (1) | Y | Indicates whether any separate remittance advice documents were created for a payment instruction. By default this flag is set to N. |
| REGULATORY_REPORT_CREATED_FLAG | VARCHAR2 | (1) | Y | Indicates whether a regulatory report, for example, for central bank reporting, has been created for a payment instruction |
| BILL_PAYABLE_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether a payment instruction consists of bills payable |
| LEGAL_ENTITY_ID | NUMBER | (15) | Legal entity Identifier of the payment instruction. This column is populated only when first party legal entity is specified as a grouping rule for payment instruction creation. | |
| PAYMENT_COUNT | NUMBER | (15) | Y | Number of payments comprising this instruction |
| POSITIVE_PAY_FILE_CREATED_FLAG | VARCHAR2 | (1) | Y | Indicates whether a positive pay file has been created for a payment instruction |
| PRINT_INSTRUCTION_IMMED_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether the payment instruction is printed immediately after the payment instruction is created |
| TRANSMIT_INSTR_IMMED_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether the payment instruction is transmitted immediately after the payment instruction is created |
| CREATED_BY | NUMBER | (15) | Y | Standard who column - unique internal identifier of user who created this row. Foreign key to the USER_ID column of the FND_USER table. |
| CREATION_DATE | DATE | Y | Standard who column - date when this row was created. | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard who column - unique internal identifier user who last updated this row. Foreign key to the USER_ID column of the FND_USER table. |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column - date when a user last updated this row. | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard who column - operating system login of user who last updated this row. Foreign key to the LOGIN_ID column of the FND_LOGINS table | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. This number is incremented for every update to the row through the application. | |
| INTERNAL_BANK_ACCOUNT_ID | NUMBER | (15) | Internal bank account Identifier of the payment instruction. This column is populated only when internal bank account is specified as a grouping rule for payment instruction creation. This column is always populated for printed payment instructions, as they are required to be created for a single internal bank account. | |
| PAY_ADMIN_ASSIGNED_REF_CODE | VARCHAR2 | (255) | Administrator assigned reference code | |
| TRANSMISSION_DATE | DATE | Date that the payment instruction is sent to the bank | ||
| ACKNOWLEDGEMENT_DATE | DATE | Date on which the acknowledgement is received | ||
| COMMENTS | VARCHAR2 | (240) | Comments entered while submitting following concurrent requests: -> ""Create Electronic Payment Instructions"" -> ""Create Printed Payment Instructions""" | |
| BANK_ASSIGNED_REF_CODE | VARCHAR2 | (30) | Payment system-provided reference code for this payment instruction | |
| ORG_ID | NUMBER | (15) | Organization Identifier of the payment instruction. This column is populated only when first party organization is specified as a grouping rule for payment instruction creation. | |
| ORG_TYPE | VARCHAR2 | (30) | Organization type. Values from the lookup IBY_ORGANIZATION_TYPES include Operating Unit, Business Group, and Legal Entity. | |
| PAYMENT_DATE | DATE | Payment date of the payment instruction. This column is populated only when payment date is specified as a grouping rule for payment instruction creation. | ||
| PAYMENT_CURRENCY_CODE | VARCHAR2 | (10) | Currency of the payment instruction. This column is populated only when payment currency is specified as a grouping rule for payment instruction creation. This column is always populated for printed payment instructions, as they are required to be for a single payment currency. | |
| PAYMENT_SERVICE_REQUEST_ID | NUMBER | (15) | Identifier of the payment process request which had its payments grouped into the payment instruction. This column is populated when payment process request is specified as a grouping rule for payment instruction creation. | |
| PAYMENT_FUNCTION | VARCHAR2 | (30) | Function or purpose of the payment. Values from the lookup IBY_PAYMENT_FUNCTIONS include SUPPLIER_PAYMENT, CUSTOMER_REFUNDS, and others. | |
| PAYMENT_REASON_CODE | VARCHAR2 | (30) | Payment reason code. This column is populated when Payment Reason is specified as a grouping rule for payment instruction creation. | |
| RFC_IDENTIFIER | VARCHAR2 | (30) | Identifier of the regional finance center at the bank branch level pertaining to the payments in the instruction. This column is populated when RFC is specified as a grouping rule for payment instruction creation. | |
| PAYMENT_REASON_COMMENTS | VARCHAR2 | (240) | Free text describing a reason for the payments in the instruction. This column is populated when Payment Reason is specified as a grouping rule for payment instruction creation. | |
| PAYMENT_DOCUMENT_ID | NUMBER | (15) | Payment document that was passed to the payment instruction creation program, if it is different from the default in the payment process profile | |
| PRINTER_NAME | VARCHAR2 | (255) | Name of the printer to be used for printed checks | |
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | Descriptive Flexfield structure defining column | |
| ATTRIBUTE1 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE2 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE3 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE4 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE5 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE6 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE7 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE8 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE9 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE10 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE11 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE12 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE13 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE14 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE15 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| REFERENCE_FORMAT_CODE | VARCHAR2 | (30) | Reference format code | |
| REQUEST_ID | NUMBER | (15) | Concurrent request identifier associated with the current process, used to control updates to processes that are currently active | |
| PAYMENT_METHOD_CODE | VARCHAR2 | (50) | Payment method identifier | |
| CARD_ISSUER_FILE_SEQ_NO | NUMBER | Card Issuer file sequence number |
IBY.IBY_PAY_INSTRUCTIONS_ALL does not reference any database object
IBY.IBY_PAY_INSTRUCTIONS_ALL is referenced by following:
| Description: | IBY_PAY_INSTRUCTIONS_H stores historical snapshots of payment instructions. This table contains denormalized versions of payment instructions from specific points in time, including when the payment instruction was submitted to a payment sy |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_PAY_INSTRUCTIONS_H.BEPID | IBY_BEPINFO |
| IBY_PAY_INSTRUCTIONS_H.PAYMENT_FORMAT_CODE | IBY_FORMATS_B |
| IBY_PAY_INSTRUCTIONS_H.PAYMENT_REASON_CODE | IBY_PAYMENT_REASONS_B |
| IBY_PAY_INSTRUCTIONS_H.TRANSMIT_CONFIGURATION_ID | IBY_TRANSMIT_CONFIGS_B |
| IBY_PAY_INSTRUCTIONS_H.POSITIVE_PAY_FORMAT_CODE | IBY_FORMATS_B |
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_PAYMENTS_H.PAYMENT_INSTRUCTION_HISTORY_ID | IBY_PAY_INSTRUCTIONS_H |
IBY_PAY_INSTRUCTIONS_H stores historical snapshots of payment instructions. This table contains denormalized versions of payment instructions from specific points in time, including when the payment instruction was submitted to a payment system. Different snapshots of the same payment instruction can exist in this table. These snapshots are differentiated by the table's primary key and a snapshot date.
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYMENT_INSTRUCTION_HISTORY_ID | NUMBER | (15) | Y | Payment instruction identifier |
| PMT_INSTRUCTION_HISTORY_DATE | DATE | Y | Payment instruction date | |
| PAYMENT_INSTRUCTION_ID | NUMBER | (15) | Y | Payment instruction identifier |
| PAYMENT_INSTRUCTION_NAME | VARCHAR2 | (255) | Y | Payment instruction name |
| PAYMENT_FORMAT_CODE | VARCHAR2 | (30) | Y | Format used for the payment instruction |
| BILL_PAYABLE_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether a payment instruction consists of bills payable |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number | |
| BEPID | NUMBER | (15) | Y | Payment system identifier |
| PRINT_INSTRUCTION_IMMED_FLAG | VARCHAR2 | (1) | Y | Y or N that indicates if the instruction is printed immediately after formatting |
| TRANSMIT_INSTR_IMMED_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether the payment instruction is transmitted immediately after the payment instruction is created. |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| TRANSMIT_CONFIGURATION_ID | NUMBER | (15) | Y | Transmission configuration identifier |
| SECURITY_CONFIGURATION_ID | NUMBER | (15) | Security configuration Identifier from the payment process profile | |
| POSITIVE_PAY_FORMAT_CODE | VARCHAR2 | (30) | Y | Positive pay format code from the payment process profile |
| PROCESS_TYPE | VARCHAR2 | (30) | Y | Specifies the process by which payments are built into payment instructions. Values from the lookup IBY_PROCESS_TYPES include STANDARD, IMMEDIATE, and MANUAL. |
| PAYMENT_INSTRUCTION_STATUS | VARCHAR2 | (30) | Y | Payment instruction status. Values from the lookup IBY_PAY_INSTRUCTION_STATUSES include CREATED, FORMATTED, and TRANSMITTED. |
| PAYMENTS_COMPLETE_FLAG | VARCHAR2 | (1) | Y | Y or N flag that indicates if the payments are complete |
| INT_BANK_ACCOUNT_ROUTING_NUM | VARCHAR2 | (30) | Internal bank account routing number from CE bank accounts | |
| INT_BANK_ACCOUNT_NUMBER | VARCHAR2 | (30) | Internal bank account number from CE bank accounts | |
| INT_BANK_ACCOUNT_IBAN_NUMBER | VARCHAR2 | (50) | Internal bank account IBAN number from CE bank accounts | |
| SEQUENCE_NUMBER | VARCHAR2 | (100) | Sequence number assigned to the payment instruction | |
| PAY_ADMIN_ASSIGNED_REF_CODE | VARCHAR2 | (255) | Administrator-assigned reference code | |
| PAYMENT_COUNT | NUMBER | (15) | Y | Number of payments comprising this instruction |
| TRANSMISSION_DATE | DATE | Date that the payment instruction is sent to the payment system | ||
| ACKNOWLEDGEMENT_DATE | DATE | Date on which the acknowledgement is received | ||
| COMMENTS | VARCHAR2 | (240) | User entered notes | |
| REMITTANCE_ADVICE_CREATED_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether any separate remittance advice documents were created for a payment instruction. By default this flag is set to N. |
| BANK_ASSIGNED_REF_CODE | VARCHAR2 | (30) | Payment system-provided reference code for this payment instruction | |
| LEGAL_ENTITY_ID | NUMBER | (15) | Y | Legal entity Identifier |
| PAYMENT_FUNCTION | VARCHAR2 | (30) | Function or purpose of the payment. Values from the lookup IBY_PAYMENT_FUNCTIONS include SUPPLIER_PAYMENT, CUSTOMER_REFUNDS, and others. | |
| PRINTER_NAME | VARCHAR2 | (255) | Printer name | |
| PAYMENT_REASON_CODE | VARCHAR2 | (30) | Y | Payment reason code. This column is populated when Payment Reason is specified as a grouping rule for payment instruction creation. |
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | Descriptive Flexfield structure defining column | |
| ATTRIBUTE1 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE2 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE3 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE4 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE5 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE6 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE7 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE8 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE9 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE10 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE11 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE12 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE13 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE14 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE15 | VARCHAR2 | (150) | Descriptive Flexfield segment |
IBY.IBY_PAY_INSTRUCTIONS_H does not reference any database object
IBY.IBY_PAY_INSTRUCTIONS_H is referenced by following:
| Description: | Stores a reference to the invoice in the calling payable programs |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_PAY_INVOICEPMTS.PMT_TRXN_ID | IBY_PAY_PAYMENTS_ALL |
IBY_PAY_INVOICEPMTS is used to store a reference to the invoice information in the originating payable programs that submitted the payment request. Each row in this table must belong to a payment row in IBY_PAY_PAYMENTS_ALL; each row in IBY_PAY_PAYMENTS_ALL can have zero to n invoice rows. The invoice information may be used for payment reconciliation. For Oracle Payables, each row in this table corresponds to a row in AP_SELECTED_INVOICES_ALL.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_PAY_INVOICEPMTS_PK | UNIQUE | APPS_TS_TX_IDX |
PMT_TRXN_ID
INVOICE_NUMBER |
| IBY_PAY_IP_PK_U1 | UNIQUE | APPS_TS_TX_IDX |
PMT_BATCH_REQUEST_ID
BATCH_ID PMT_TRXN_ID INVOICE_NUMBER |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PMT_BATCH_REQUEST_ID | NUMBER | |||
| BATCH_ID | NUMBER | |||
| PMT_TRXN_ID | NUMBER | (15) | Y | Foreign key to IBY_PAY_PAYMENTS_ALL. Reference to the owning payment transaction |
| INVOICE_NUMBER | VARCHAR2 | (60) | Y | Stores AP_SELECTED_INVOICES_ALL.INVOICE_NUM |
| INVOICE_DATE | DATE | Y | Stores AP_SELECTED_INVOICES_ALL.INVOICE_DATE | |
| INVOICE_AMOUNT | NUMBER | Y | Stores AP_SELECTED_INVOICES_ALL.INVOICE_AMOUNT | |
| PAYMENT_AMOUNT | NUMBER | Y | Stores AP_SELECTED_INVOICES_ALL.PAYMENT_AMOUNT | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Application level record locking for three tier stateless applications | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| ERROR_LOCATION | NUMBER | |||
| BEP_CODE | VARCHAR2 | (80) | ||
| BEP_MESSAGE | VARCHAR2 | (80) | ||
| ECAPP_ID | NUMBER | (15) | Electronic Commerce Application Identifier |
IBY.IBY_PAY_INVOICEPMTS does not reference any database object
IBY.IBY_PAY_INVOICEPMTS is referenced by following:
| Description: | Stores transaction level payment information as submitted by payable programs |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_PAY_PAYMENTS_ALL.BATCH_ID | IBY_PAY_BATCHES_ALL |
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_PAY_INVOICEPMTS.PMT_TRXN_ID | IBY_PAY_PAYMENTS_ALL |
IBY_PAY_PAYMENTS_ALL is used to store the transaction level payment information submitted by payable programs such Oracle Payables. This includes the beneficiary, receiving bank and bank account, and various payment processing information. Each payment row in this table must belong to a payment batch in IBY_PAY_BATCHES_ALL; each batch row in IBY_PAY_BATCHES_ALL can have one to n payment rows. For Oracle Payables, each row in this table corresponds to a row in AP_SELECTED_INVOICE_CHECKS_ALL.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_PAY_PAYMENTS_ALL_PK | UNIQUE | APPS_TS_TX_IDX | PMT_TRXN_ID |
| IBY_PAY_PAYMENTS_ALL_N1 | NONUNIQUE | APPS_TS_TX_IDX | BATCH_ID |
| IBY_PAY_PAYMENTS_ALL_N2 | NONUNIQUE | APPS_TS_TX_IDX | BNF_BANK_ACCT_NUMBER |
| IBY_PAY_PAYMENTS_ALL_N3 | NONUNIQUE | APPS_TS_TX_IDX | BNF_BANK_BRANCH_NUM |
| IBY_PAY_PAYMENTS_ALL_N4 | NONUNIQUE | APPS_TS_TX_IDX | BNF_BANK_NUM |
| IBY_PAY_PAYMENTS_ALL_N5 | NONUNIQUE | APPS_TS_TX_IDX | BNF_NAME |
| IBY_PAY_PAYMENTS_ALL_N6 | NONUNIQUE | APPS_TS_TX_IDX | CUST_REF |
| IBY_PAY_PAYMENTS_ALL_N7 | NONUNIQUE | APPS_TS_TX_IDX | PAYER_ID |
| IBY_PAY_PAYMENTS_ALL_N8 | NONUNIQUE | APPS_TS_TX_IDX | PMT_STATUS |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ECAPP_ID | NUMBER | (15) | Electronic Commerce Application Identifier | |
| PAYER_ID | VARCHAR2 | (80) | Y | Payer Identifier |
| BATCH_ID | NUMBER | (15) | Y | Batch Identifier. Foreign key to IBY_PAY_BATCHES_ALL |
| PMT_TRXN_ID | NUMBER | (15) | Y | System generated primary key |
| PMT_PRIORITY | VARCHAR2 | (10) | PO_VENDOR_SITES.PAYMENT_PRIORITY | |
| DEBIT_ACCT_NUMBER | VARCHAR2 | (30) | AP_BANK_ACCOUNTS_ALL.BANK_ACCOUNT_NUM. Same as IBY_PAY_BATCHES_ALL.ORIG_BANK_ACCT_NUMBER | |
| FAX_MAIL_TO_NAME | VARCHAR2 | (240) | AP_SELECTED_INVOICE_CHECKS_ALL.VENDOR_NAME. Same as BNF_NAME | |
| MAIL_ADDRESS1 | VARCHAR2 | (240) | Beneficiary address line1. AP_SELECTED_INVOICE_CHECKS_ALL.ADDRESS_LINE1 | |
| MAIL_ADDRESS2 | VARCHAR2 | (240) | AP_SELECTED_INVOICE_CHECKS_ALL.ADDRESS_LINE2 | |
| MAIL_ADDRESS3 | VARCHAR2 | (240) | AP_SELECTED_INVOICE_CHECKS_ALL.ADDRESS_LINE3 | |
| MAIL_ADDR_CITY | VARCHAR2 | (25) | AP_SELECTED_INVOICE_CHECKS_ALL.CITY | |
| MAIL_ADDR_STATE | VARCHAR2 | (150) | AP_SELECTED_INVOICE_CHECKS_ALL.STATE | |
| MAIL_ADDR_ZIP | VARCHAR2 | (20) | AP_SELECTED_INVOICE_CHECKS_ALL.ZIP | |
| PMT_LOC_COUNTRY_CODE | VARCHAR2 | (25) | Country code of the beneficiary address. AP_SELECTED_INVOICE_CHECKS_ALL.COUNTRY | |
| VALUE_AMOUNT | NUMBER | Y | AP_SELECTED_INVOICE_CHECKS_ALL.CHECK_AMOUNT | |
| REF_AMOUNT | NUMBER | Amount in the reference currency | ||
| VALUE_DATE | DATE | Y | AP_SELECTED_INVOICE_CHECKS_ALL.PAYMENT_DATE | |
| CHARGE_DETAILS | VARCHAR2 | (6) | PO_VENDOR_SITES_ALL.BANK_CHARGE_BEARER | |
| VAT_AMOUNT | NUMBER | Oracle Internal use only - reserved for future use | ||
| WHT_AMOUNT | NUMBER | Oracle Internal use only - reserved for future use | ||
| PMT_DETAILS_1 | VARCHAR2 | (20) | Oracle Internal use only - reserved for future use | |
| PMT_DETAILS_2 | VARCHAR2 | (20) | Oracle Internal use only - reserved for future use | |
| PMT_DETAILS_3 | VARCHAR2 | (20) | Oracle Internal use only - reserved for future use | |
| PMT_DETAILS_4 | VARCHAR2 | (20) | Oracle Internal use only - reserved for future use | |
| TRXN_CODE_CLRID | VARCHAR2 | (30) | Transaction code from PO_VENDOR_SITES_ALL flexfield | |
| BNF_NAME | VARCHAR2 | (240) | Y | AP_SELECTED_INVOICE_CHECKS_ALL.VENDOR_NAME |
| BNF_ID | VARCHAR2 | (30) | PO_VENDORS.SEGMENT1. Supplier number | |
| BNF_ADDRESS_LINE1 | VARCHAR2 | (240) | PO_VENDOR_SITES_ALL.ADDRESS_LINE1 | |
| BNF_ADDRESS_LINE2 | VARCHAR2 | (240) | PO_VENDOR_SITES_ALL.ADDRESS_LINE2 | |
| BNF_ADDRESS_LINE3 | VARCHAR2 | (240) | PO_VENDOR_SITES_ALL.ADDRESS_LINE3 | |
| BNF_ADDR_CITY | VARCHAR2 | (25) | PO_VENDOR_SITES_ALL.CITY | |
| BNF_ADDR_STATE | VARCHAR2 | (150) | PO_VENDOR_SITES_ALL.STATE | |
| BNF_ADDR_ZIP | VARCHAR2 | (20) | PO_VENDOR_SITES_ALL.ZIP | |
| BNF_ADDR_COUNTRY | VARCHAR2 | (25) | Oracle Internal use only - reserved for future use | |
| BNF_ADDR_PHONE | VARCHAR2 | (15) | PO_VENDOR_SITES_ALL.PHONE | |
| BNF_REMARKS | VARCHAR2 | (80) | Oracle Internal use only - reserved for future use | |
| BNF_CHARGE_AMT | NUMBER | Oracle Internal use only - reserved for future use | ||
| BNF_ADJUSTMENT_AMT | VARCHAR2 | (30) | Oracle Internal use only - reserved for future use | |
| BNF_BANK_NAME | VARCHAR2 | (60) | AP_BANK_BRANCHES.BANK_NAME | |
| BNF_BANK_NUM | VARCHAR2 | (30) | AP_BANK_BRANCHES.BANK_NUMBER | |
| BNF_BANK_ADDRESS | VARCHAR2 | (35) | AP_BANK_BRANCHES.ADDRESS_LINE1 | |
| BNF_BANK_ADDR_CITY | VARCHAR2 | (25) | AP_BANK_BRANCHES.CITY | |
| BNF_BANK_ADDR_STATE | VARCHAR2 | (25) | AP_BANK_BRANCHES.STATE | |
| BNF_BANK_ADDR_ZIP | VARCHAR2 | (20) | AP_BANK_BRANCHES.ZIP | |
| BNF_BANK_ADDR_COUNTRY | VARCHAR2 | (25) | AP_BANK_BRANCHES.COUNTRY | |
| BNF_BANK_BRANCH_NAME | VARCHAR2 | (60) | AP_BANK_BRANCHES.BANK_BRANCH_NAME | |
| BNF_BANK_BRANCH_NUM | VARCHAR2 | (25) | AP_BANK_BRANCHES.BANK_NUM | |
| BNF_BANK_BRANCH_TYPE | VARCHAR2 | (25) | AP_BANK_BRANCHES.BANK_BRANCH_TYPE | |
| BNF_BANK_SWIFT_CODE | VARCHAR2 | (12) | AP_BANK_BRANCHES.EFT_SWIFT_CODE | |
| BNF_BANK_ACCOUNT_NAME | VARCHAR2 | (80) | AP_BANK_ACCOUNTS_ALL.BANK_ACCOUNT_NAME | |
| BNF_BANK_ACCT_NUMBER | VARCHAR2 | (30) | AP_BANK_ACCOUNTS_ALL.BANK_ACCOUNT_NUM | |
| BNF_BANK_ACCT_CHECK_DIGITS | VARCHAR2 | (30) | AP_BANK_ACCOUNTS_ALL.CHECK_DIGITS | |
| BNF_BANK_ACCT_IBAN_NUMBER | VARCHAR2 | (40) | International Bank Account Number. Corresponds to IBAN_NUMBER in AP_BANK_ACCOUNTS_ALL | |
| BNF_BANK_ACCT_TYPE | VARCHAR2 | (25) | AP_BANK_ACCOUNTS_ALL.BANK_ACCOUNT_TYPE | |
| BNF_FAXNO_CABLEADDR | VARCHAR2 | (35) | Store the concatenated fax number from PO_VENDER_SITES_ALL | |
| BNF_SITE_CODE | VARCHAR2 | (15) | PO_VENDER_SITES_ALL.VENDER_SITE_CODE | |
| BNF_BANK_CLEARING_MTD | VARCHAR2 | (60) | Oracle Internal use only - reserved for future use | |
| BNF_TAXPAYER_ID | VARCHAR2 | (30) | PO_VENDORS_ALL.NUM_1099 | |
| FUTURE_PAY_DUE_DATE | DATE | AP_SELECTED_INVOICE_CHECKS_ALL.FUTURE_PAY_DUE_DATE | ||
| CUST_REF | NUMBER | AP_SELECTED_INVOICE_CHECKS_ALL.CHECK_NUMBER | ||
| INTRM_BANK_CODE | VARCHAR2 | (30) | Oracle Internal use only - reserved for future use | |
| INTRM_SWIFT_CODE | VARCHAR2 | (30) | Oracle Internal use only - reserved for future use | |
| INTRM_BANK_NAME | VARCHAR2 | (60) | Oracle Internal use only - reserved for future use | |
| INTRM_BANK_FAXNO_CBL | VARCHAR2 | (35) | Oracle Internal use only - reserved for future use | |
| PMT_STATUS | NUMBER | status of this transaction | ||
| PMT_APPROVAL_STATUS | NUMBER | Oracle Internal use only - reserved for future use | ||
| UPDATE_DATE | DATE | Oracle Internal use only - reserved for future use | ||
| OBJECT_VERSION_NUMBER | NUMBER | Y | Application level record locking for three tier stateless applications | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| ORG_ID | NUMBER | (15) | AP_INV_SELECTION_CRITERIA_ALL.ORG_ID | |
| ERROR_LOCATION | NUMBER | Identifies the location of error | ||
| BEP_CODE | VARCHAR2 | (80) | Error code from Back End Payment System | |
| BEP_MESSAGE | VARCHAR2 | (1024) | Error message from Back End Payment System |
IBY.IBY_PAY_PAYMENTS_ALL does not reference any database object
IBY.IBY_PAY_PAYMENTS_ALL is referenced by following:
| Description: | "This table contains records of the payment process requests which are created by system while processing 'Build payments' program.IBY_PAY_SERVICE_REQUESTS stores payment process requests from source products. A payment process request is |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_PAY_SERVICE_REQUESTS.INTERNAL_BANK_ACCOUNT_ID | CE_BANK_ACCOUNTS |
| IBY_PAY_SERVICE_REQUESTS.PAYMENT_PROFILE_ID | IBY_ACCT_PMT_PROFILES_B |
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_DOCS_PAYABLE_ALL.PAYMENT_SERVICE_REQUEST_ID | IBY_PAY_SERVICE_REQUESTS |
| IBY_DOCUMENTS_PAYABLE_H.PAYMENT_SERVICE_REQUEST_ID | IBY_PAY_SERVICE_REQUESTS |
| IBY_PAYMENTS_ALL.PAYMENT_SERVICE_REQUEST_ID | IBY_PAY_SERVICE_REQUESTS |
| IBY_PAYMENTS_H.PAYMENT_SERVICE_REQUEST_ID | IBY_PAY_SERVICE_REQUESTS |
| IBY_PAY_INSTRUCTIONS_ALL.PAYMENT_SERVICE_REQUEST_ID | IBY_PAY_SERVICE_REQUESTS |
IBY_PAY_SERVICE_REQUESTS stores payment process requests from source products. A payment process request is a group of documents payable that a source product submits to Oracle Payments for payment service processing. This table corresponds to the Payment Process Requests page.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_PAY_SERVICE_REQUESTS_U1 | UNIQUE | APPS_TS_TX_IDX | PAYMENT_SERVICE_REQUEST_ID |
| IBY_PAY_SERVICE_REQUESTS_U2 | UNIQUE | APPS_TS_TX_IDX |
CALLING_APP_ID
CALL_APP_PAY_SERVICE_REQ_CODE |
| IBY_PAY_SERVICE_REQUESTS_N1 | NONUNIQUE | APPS_TS_TX_IDX | INTERNAL_BANK_ACCOUNT_ID |
| IBY_PAY_SERVICE_REQUESTS_N2 | NONUNIQUE | APPS_TS_TX_IDX | PAYMENT_PROFILE_ID |
| IBY_PAY_SERVICE_REQUESTS_N3 | NONUNIQUE | APPS_TS_TX_IDX | PAYMENT_SERVICE_REQUEST_STATUS |
| IBY_PAY_SERVICE_REQUESTS_N4 | NONUNIQUE | APPS_TS_TX_IDX |
PAYMENT_SERVICE_REQUEST_STATUS
PROCESS_TYPE LAST_UPDATE_DATE |
| IBY_PAY_SERVICE_REQUESTS_N5 | NONUNIQUE | APPS_TS_TX_IDX |
PAYMENT_SERVICE_REQUEST_ID
CALLING_APP_ID PROCESS_TYPE PAYMENT_SERVICE_REQUEST_STATUS |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYMENT_SERVICE_REQUEST_ID | NUMBER | (15) | Y | System generated primary key |
| CALLING_APP_ID | NUMBER | (15) | Y | Source product Identifier |
| CALL_APP_PAY_SERVICE_REQ_CODE | VARCHAR2 | (255) | Y | Source product''s payment process request Identifier. Since the source product''s Identifiers may be alphanumeric, even numeric document Identifiers are stored as VARCHAR2. |
| PAYMENT_SERVICE_REQUEST_STATUS | VARCHAR2 | (30) | Y | Payment process request status. Values from the lookup IBY_REQUEST_STATUSES include PAYMENTS_CREATED. |
| PROCESS_TYPE | VARCHAR2 | (30) | Y | Specifies the process by which documents payable are built into payments and payments into payment instructions. Values from the lookup IBY_PROCESS_TYPES include STANDARD, IMMEDIATE, and MANUAL. |
| ALLOW_ZERO_PAYMENTS_FLAG | VARCHAR2 | (1) | Y | Y or N flag that indicates whether zero payments are allowed for this payment request. If set to N, any zero value payments created for this payment request will be failed. |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| INTERNAL_BANK_ACCOUNT_ID | NUMBER | (15) | Internal bank account identifier | |
| PAYMENT_PROFILE_ID | NUMBER | (15) | Payment process profile Identifier. This is mandatory if COMPLETE_INSTRUCTION_FLAG is Y. | |
| MAXIMUM_PAYMENT_AMOUNT | NUMBER | Maximum payment amount used to override default maximum payment amount | ||
| MINIMUM_PAYMENT_AMOUNT | NUMBER | Minimum payment amount used to override default minimum payment amount | ||
| DOCUMENT_REJECTION_LEVEL_CODE | VARCHAR2 | (30) | Specifies what is rejected if a document payable fails validation. Values from the IBY_DOCUMENT_REJECTION_LEVELS lookup include REQUEST, PAYEE, and DOCUMENT. | |
| PAYMENT_REJECTION_LEVEL_CODE | VARCHAR2 | (30) | Specifies how much of a payment process request is rejected if a payment fails validation. Values from the IBY_PAYMENT_REJECTION_LEVELS lookup include REQUEST, PAYMENT, and NONE. | |
| REQUIRE_PROP_PMTS_REVIEW_FLAG | VARCHAR2 | (1) | Flag indicating whether Oracle Payments should stop the payment creation flow to allow an administrator to review and modify proposed payments before grouping them into payment instructions. Values from the lookup IBY_PROPOSED_PMTS_REVIEW_CODES include Y and N. | |
| ORG_TYPE | VARCHAR2 | (30) | Organization type. Values from the lookup IBY_ORGANIZATION_TYPES include Operating Unit, Business Group, and Legal Entity. | |
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | Descriptive Flexfield structure defining column | |
| ATTRIBUTE1 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE2 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE3 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE4 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE5 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE6 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE7 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE8 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE9 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE10 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE11 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE12 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE13 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE14 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE15 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| CREATE_PMT_INSTRUCTIONS_FLAG | VARCHAR2 | (1) | Flag indicating whether the Build Payments program automatically kicks off the Create Payment Instructions program after payment build completes. | |
| PAYMENT_DOCUMENT_ID | NUMBER | (15) | Stores the payment document Identifier on which the payment instructions created from the payments of this request are printed. This parameter is only applicable where the Build Payments program kicks off the Create Payment Instructions program. | |
| REQUEST_ID | NUMBER | (15) | Concurrent request identifier associated with the current process, used to control updates to processes that are currently active |
IBY.IBY_PAY_SERVICE_REQUESTS does not reference any database object
IBY.IBY_PAY_SERVICE_REQUESTS is referenced by following:
| Description: | Stores the BIN ranges for all valid purchase cards. |
|---|
IBY_PCARD_BIN_RANGE stores the BIN ranges for all valid purchase cards.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_PCARD_BIN_RANGE_U1 | UNIQUE | APPS_TS_TX_IDX |
LAST_UPDATED_BY
UPPERLIMIT LOWERLIMIT ZD_EDITION_NAME |
| IBY_BINRANGE_LIMITS_N1 | NONUNIQUE | APPS_TS_TX_IDX |
LOWERLIMIT
UPPERLIMIT |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| LOWERLIMIT | NUMBER | Lower limit of the BIN range | ||
| UPPERLIMIT | NUMBER | Upper limit of the BIN range | ||
| PCARD_SUBTYPE | VARCHAR2 | (4) | Character value giving the subtype of the purchase card. Multiple characters are used if the card belongs to more than a single subtype. | |
| OBJECT_VERSION_NUMBER | NUMBER | Used for locking purposes that subsequently allows for checking if there is old data on the screen compared to what is in the database. The situation occurs when the HTML application is a stateless application. | ||
| LAST_UPDATE_DATE | DATE | Standard Who column | ||
| LAST_UPDATED_BY | NUMBER | Standard Who column | ||
| CREATION_DATE | DATE | Standard Who column | ||
| CREATED_BY | NUMBER | Standard Who column | ||
| LAST_UPDATE_LOGIN | NUMBER | Standard Who column | ||
| SECURITY_GROUP_ID | NUMBER | Used in hosted environments | ||
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_PCARD_BIN_RANGE does not reference any database object
IBY.IBY_PCARD_BIN_RANGE is referenced by following:
| Description: | IBY_PMTMTHD_CONDITIONS stores the conditions for payment methods. Each condition is comprised of a parameter, operation, and value. The condition is evaluated at runtime to determine if the payment system account and funds capture process p |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_PMTMTHD_CONDITIONS.PAYMENTMETHODID | IBY_ROUTINGINFO |
IBY_PMTMTHD_CONDITIONS stores the conditions for payment methods. Each condition is comprised of a parameter, operation, and value. The condition is evaluated at runtime to determine if the payment system account and funds capture process profile is applicable to the transaction.
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYMENTMETHODID | NUMBER | (15) | Y | Payment method Identifier |
| PARAMETER_CODE | VARCHAR2 | (30) | Y | AMOUNT, INSTRTYPE, or other condition |
| OPERATION_CODE | VARCHAR2 | (15) | Y | EQUALS, NEQUALS, or other operation |
| VALUE | VARCHAR2 | (30) | Value for the condition | |
| IS_VALUE_STRING | VARCHAR2 | (1) | Value type such as number or character | |
| ENTRY_SEQUENCE | NUMBER | (4) | Number which denotes the order in which the admin user has entered the conditions. When queried, it needs to be displayed in the same order that the user entered it. | |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Used for locking purposes that subsequently allows for checking if there is old data on the screen compared to what is in the database. The situation occurs when the HTML application is a stateless application. | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| SECURITY_GROUP_ID | NUMBER | Used in hosted environments | ||
| CONDITION_NAME | VARCHAR2 | (80) | Mnemonic created by the user for one of the conditions which constitutes a routing rule |
IBY.IBY_PMTMTHD_CONDITIONS does not reference any database object
IBY.IBY_PMTMTHD_CONDITIONS is referenced by following:
| Description: | IBY_PMTSCHEMES stores a list of payment schemes that are supported by a payment system. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_PMTSCHEMES.BEPID | IBY_BEPINFO |
IBY_PMTSCHEMES stores a list of payment schemes that are supported by a payment system.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_PMTSCHEMEID_BEPID_U1 | UNIQUE | APPS_TS_TX_IDX |
PMTSCHEMEID
BEPID ZD_EDITION_NAME |
| IBY_PMTSCHEMES_N1 | NONUNIQUE | APPS_TS_TX_IDX | PMTSCHEMENAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| BEPID | NUMBER | Y | Payment system identifier | |
| PMTSCHEMEID | NUMBER | (15) | Y | Obsolete: this ID is not used to retrieve which payment instrument processing is allowed for a payment system. The code only uses PMTSCHEMENAME |
| PMTSCHEMENAME | VARCHAR2 | (30) | Y | Name of the Payment Scheme : SSL,SET,Bank Account or FI |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| CREATION_DATE | DATE | Y | Standard Who column | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (5) | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. |
| SECURITY_GROUP_ID | NUMBER | Used in hosted environments | ||
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_PMTSCHEMES does not reference any database object
IBY.IBY_PMTSCHEMES is referenced by following:
| Description: | IBY_PMT_CREATION_RULES specifies how documents payable are grouped into payments. Creation rules are determined by payment process profiles. This table corresponds to the Payment Creation tab of the Update Payment Process Profile page. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_PMT_CREATION_RULES.SYSTEM_PROFILE_CODE | IBY_SYS_PMT_PROFILES_B |
IBY_PMT_CREATION_RULES specifies how documents payable are grouped into payments. Creation rules are determined by payment process profiles. This table corresponds to the Payment Creation tab of the Update Payment Process Profile page.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_PMT_CREATION_RULES_U1 | UNIQUE | APPS_TS_TX_IDX |
SYSTEM_PROFILE_CODE
ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| SYSTEM_PROFILE_CODE | VARCHAR2 | (100) | Y | Unique primary key |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number | |
| GROUP_BY_PAYMENT_DETAILS_FLAG | VARCHAR2 | (1) | Y | Y or N flag specifying whether documents payable are grouped by the length of the payment detail record |
| GROUP_BY_BANK_CHARGE_BEARER | VARCHAR2 | (1) | Y | Y or N flag specifying whether documents payable are grouped by the bank charge bearer |
| GROUP_BY_DELIVERY_CHANNEL | VARCHAR2 | (1) | Y | Y or N flag specifying whether documents payable are grouped by delivery channel |
| GROUP_BY_REMITTANCE_MESSAGE | VARCHAR2 | (1) | Y | Y or N flag specifying whether documents payable are grouped by remittance message |
| GROUP_BY_MAX_DOCUMENTS_FLAG | VARCHAR2 | (1) | Y | Y or N flag specifying whether there is a limit on how many documents can be grouped into a payment |
| GROUP_BY_UNIQUE_REMIT_ID_FLAG | VARCHAR2 | (1) | Y | Y or N flag specifying whether documents with unique remittance Identifiers are paid alone |
| GROUP_BY_SETTLE_PRIORITY_FLAG | VARCHAR2 | (1) | Y | Y or N flag specifying whether documents payable are grouped by the settlement priority value |
| GROUP_BY_PAYMENT_REASON | VARCHAR2 | (1) | Y | Y or N flag specifying whether documents payable are grouped by the payment reason |
| GROUP_BY_DUE_DATE_FLAG | VARCHAR2 | (1) | Y | Y or N flag specifying whether documents payable are grouped into payments by due date |
| MAX_DOCUMENTS_PER_PAYMENT | NUMBER | (15) | Maximum number of documents that can be grouped into a single payment. This value will only be used if GROUP_BY_MAX_DOCUMENTS_FLAG is set to Y. | |
| PAYMENT_DETAILS_LENGTH_LIMIT | NUMBER | (15) | Maximum length of the payment detail record. Typically, this is a type of description record in a payment format that allows concatenated details of the payment to be included, for example, invoice numbers. If this length is exceeded, then the payment will be split into multiple payments. | |
| PAYMENT_DETAILS_FORMULA | VARCHAR2 | (240) | SQL function to be used to concatenate the document attributes into the payment details information | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_PMT_CREATION_RULES does not reference any database object
IBY.IBY_PMT_CREATION_RULES is referenced by following:
| Description: | "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 |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_FNDCPT_TX_EXTENSIONS.INSTR_ASSIGNMENT_ID | IBY_PMT_INSTR_USES_ALL |
| IBY_TRXN_SUMMARIES_ALL.PAYER_INSTR_ASSIGNMENT_ID | IBY_PMT_INSTR_USES_ALL |
Payment instruments assignments
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_PMT_INSTR_USES_ALL_U1 | UNIQUE | APPS_TS_TX_IDX | INSTRUMENT_PAYMENT_USE_ID |
| IBY_PMT_INSTR_USES_ALL_N1 | NONUNIQUE | APPS_TS_TX_IDX |
PAYMENT_FLOW
EXT_PMT_PARTY_ID |
| IBY_PMT_INSTR_USES_ALL_N2 | NONUNIQUE | APPS_TS_TX_IDX |
INSTRUMENT_TYPE
INSTRUMENT_ID |
| IBY_PMT_INSTR_USES_ALL_N3 | NONUNIQUE | APPS_TS_TX_IDX |
PAYMENT_FLOW
INSTRUMENT_TYPE INSTRUMENT_ID START_DATE END_DATE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| INSTRUMENT_PAYMENT_USE_ID | NUMBER | (15) | Y | Sequence: IBY_PMT_INSTR_USES_ALL_S.nextval |
| PAYMENT_FLOW | VARCHAR2 | (30) | Y | Value of Funds Capture or Disbursement from lookup type IBY_PAYMENT_FLOW |
| EXT_PMT_PARTY_ID | NUMBER | (15) | Y | Foreign key to IBY_EXTERNAL_PAYERS_ALL.EXT_PAYER_ID |
| INSTRUMENT_TYPE | VARCHAR2 | (30) | Y | CREDITCARD or BANKACCOUNT. |
| INSTRUMENT_ID | NUMBER | (15) | Y | Instrument ID |
| PAYMENT_FUNCTION | VARCHAR2 | (30) | Y | Payment function |
| ORDER_OF_PREFERENCE | NUMBER | (15) | Y | 1 |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number | |
| START_DATE | DATE | Y | Sysdate | |
| END_DATE | DATE | End date | ||
| DEBIT_AUTH_FLAG | VARCHAR2 | (1) | Whether authorization was obtained from the account holder for debits against the instrument. Only applicable for bank account instruments | |
| DEBIT_AUTH_METHOD | VARCHAR2 | (30) | Method used to obtain debit authorization, with values taken from lookup IBY_EFT_IN_AUTH_METHOD. Only applicable for bank account instruments | |
| DEBIT_AUTH_REFERENCE | VARCHAR2 | (100) | Reference code or number given at the time of debit authorization approval. Only applicable for bank account instruments | |
| DEBIT_AUTH_BEGIN | DATE | Beginning of debit authorization. Only applicable for bank account instruments | ||
| DEBIT_AUTH_END | DATE | End of debit authorization. Only applicable for bank account instruments | ||
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | Descriptive Flexfield structure defining column | |
| ATTRIBUTE1 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE2 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE3 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE4 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE5 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE6 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE7 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE8 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE9 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE10 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE11 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE12 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE13 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE14 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE15 | VARCHAR2 | (150) | Descriptive Flexfield segment |
IBY.IBY_PMT_INSTR_USES_ALL does not reference any database object
IBY.IBY_PMT_INSTR_USES_ALL is referenced by following:
| Description: | IBY_PMT_LOGICAL_GRP_RULES specifies the attributes for grouping the payments in a payment instruction. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_PMT_LOGICAL_GRP_RULES.SYSTEM_PROFILE_CODE | IBY_SYS_PMT_PROFILES_B |
IBY_PMT_LOGICAL_GRP_RULES specifies the attributes for grouping the payments in a payment instruction.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_PMT_LOGICAL_GRP_RULES_U1 | UNIQUE | APPS_TS_TX_IDX |
SYSTEM_PROFILE_CODE
ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| SYSTEM_PROFILE_CODE | VARCHAR2 | (100) | Y | Unique primary key |
| GROUP_BY_PAYMENT_DATE | VARCHAR2 | (1) | Y | Y or N specifying whether payments are grouped by payment date |
| GROUP_BY_PAYMENT_CURRENCY | VARCHAR2 | (1) | Y | Y or N specifying whether payments are grouped by payment currency |
| GROUP_BY_INTERNAL_BANK_ACCOUNT | VARCHAR2 | (1) | Y | Y or N specifying if the payments will be grouped by internal bank account |
| GROUP_BY_LEGAL_ENTITY | VARCHAR2 | (1) | Y | Y or N specifying if payments are grouped by legal entity |
| GROUP_BY_PAYMENT_METHOD | VARCHAR2 | (1) | Y | Y or N specifying if payments are grouped by payment method |
| GROUP_BY_PAYMENT_REASON | VARCHAR2 | (1) | Y | Y or N specifying if payments are grouped by payment reason |
| GROUP_BY_OPERATING_UNIT | VARCHAR2 | (1) | Y | Y or N specifying if the payments are grouped by operating unit |
| CREATED_BY | NUMBER | (15) | Y | Standard Who Column |
| CREATION_DATE | DATE | Y | Standard Who Column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who Column |
| LAST_UPDATE_DATE | DATE | Y | Standard When Column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object Version Number | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who Column | |
| GROUP_BY_SETTLEMENT_PRIORITY | VARCHAR2 | (1) | Y or N specifying if the payments are grouped by settlement priority | |
| GROUP_BY_PAYMENT_FUNCTION | VARCHAR2 | (1) | Y or N specifying if the payments are grouped by payment function | |
| GROUP_BY_DELIVERY_CHANNEL | VARCHAR2 | (1) | Y or N flag specifying whether documents payable are grouped by delivery channel | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_PMT_LOGICAL_GRP_RULES does not reference any database object
IBY.IBY_PMT_LOGICAL_GRP_RULES is referenced by following:
| Description: | IBY_PMT_MTHD_ATTRIB_APPL stores payment channel or method attribute applicability settings. |
|---|
IBY_PMT_MTHD_ATTRIB_APPL stores payment channel or method attribute applicability settings.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_PMT_MTHD_ATTRIB_APPL_U1 | UNIQUE | APPS_TS_TX_IDX |
PAYMENT_FLOW
PAYMENT_METHOD_CODE ATTRIBUTE_CODE ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYMENT_METHOD_CODE | VARCHAR2 | (240) | Y | Payment method identifier |
| PAYMENT_FLOW | VARCHAR2 | (30) | Y | Determines the source table for the PAYMENT_METHOD_CODE foreign key. Lookup values of IBY_PAYMENT_FLOW lookup type. Values are DISBURSEMENTS, and FUNDS_CAPTURE. If value is DISBURSEMENTS, the PAYMENT_METHOD_CODE comes from IBY_PAYMENT_METHODS table; otherwise it comes from IBY_FNDCPT_PMT_CHNNLS table. |
| ATTRIBUTE_CODE | VARCHAR2 | (30) | Y | Code for the attribute |
| ATTRIBUTE_APPLICABILITY | VARCHAR2 | (30) | Attribute applicability; value taken from IBY_PMT_ATTRIB_APL_TYPES | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Object Version Number |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_PMT_MTHD_ATTRIB_APPL does not reference any database object
IBY.IBY_PMT_MTHD_ATTRIB_APPL is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_PMT_SYS_FORMATS.PAYMENT_SYSTEM_ID | IBY_BEPINFO |
| IBY_PMT_SYS_FORMATS.PAYMENT_FORMAT_CODE | IBY_FORMATS_B |
IBY_PMT_SYS_FORMATS links payment system to the payment formats they support. When a user creates a process profile, this table stores the formats that the payment system accepts.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_PMT_SYS_FORMATS_ID_CODE_U1 | UNIQUE | APPS_TS_TX_IDX |
PAYMENT_FORMAT_CODE
PAYMENT_SYSTEM_ID ZD_EDITION_NAME |
| IBY_PMT_SYS_FORMATS_PSID_N1 | NONUNIQUE | APPS_TS_TX_IDX | PAYMENT_SYSTEM_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYMENT_SYSTEM_ID | NUMBER | (15) | Y | Payment system identifier |
| PAYMENT_FORMAT_CODE | VARCHAR2 | (30) | Y | Identifier of a payment format supported by the bank |
| INACTIVE_DATE | DATE | Inactive date | ||
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_PMT_SYS_FORMATS does not reference any database object
IBY.IBY_PMT_SYS_FORMATS is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_PMT_SYS_TRANSMISSIONS.TRANSMIT_PROTOCOL_CODE | IBY_TRANSMIT_PROTOCOLS_B |
| IBY_PMT_SYS_TRANSMISSIONS.BEPID | IBY_BEPINFO |
IBY_BEP_TRANSMISSIONS links payment systems to the transmission protocols they support. When a user creates a payment process profile, this table gives him or her the correct choice of protocols to use with a given payment system.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_PMT_SYS_TRANSMISSIONS_U1 | UNIQUE | APPS_TS_TX_IDX |
BEPID
TRANSMIT_PROTOCOL_CODE ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| TRANSMIT_PROTOCOL_CODE | VARCHAR2 | (240) | Y | Transmission protocol identifier |
| BEPID | NUMBER | (15) | Y | Payment system identifier |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_PMT_SYS_TRANSMISSIONS does not reference any database object
IBY.IBY_PMT_SYS_TRANSMISSIONS is referenced by following:
| Description: | Concurrent requests |
|---|
Concurrent requests
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_PROCESS_CONC_REQUESTS_N1 | NONUNIQUE | APPS_TS_TX_IDX |
OBJECT_ID
OBJECT_TYPE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| OBJECT_ID | NUMBER | (15) | Y | Object identifier |
| OBJECT_TYPE | VARCHAR2 | (30) | Y | Object type |
| REQUEST_ID | NUMBER | (15) | Y | Concurrent request identifier |
| COMPLETED_FLAG | VARCHAR2 | (1) | Y | Y or N flag that indicates if the payments are complete |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Object version number |
IBY.IBY_PROCESS_CONC_REQUESTS does not reference any database object
IBY.IBY_PROCESS_CONC_REQUESTS is referenced by following:
| Description: | Populated by build program - list of all functions within any given PPR |
|---|
Populated by build program - list of all functions within any given PPR
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_PROCESS_FUNCTIONS_N1 | NONUNIQUE | APPS_TS_TX_IDX |
OBJECT_ID
OBJECT_TYPE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| OBJECT_ID | NUMBER | (15) | Y | Object identifier |
| OBJECT_TYPE | VARCHAR2 | (30) | Y | Object type |
| PAYMENT_FUNCTION | VARCHAR2 | (30) | Y | Payment function |
IBY.IBY_PROCESS_FUNCTIONS does not reference any database object
IBY.IBY_PROCESS_FUNCTIONS is referenced by following:
| Description: | Populated by build program - list of all orgs within any given PPR |
|---|
Populated by build program - list of all orgs within any given PPR
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_PROCESS_ORGS_N1 | NONUNIQUE | APPS_TS_TX_IDX |
OBJECT_ID
OBJECT_TYPE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| OBJECT_ID | NUMBER | (15) | Y | Object identifier |
| OBJECT_TYPE | VARCHAR2 | (30) | Y | Object type |
| ORG_TYPE | VARCHAR2 | (30) | Y | Organization type |
| ORG_ID | NUMBER | (15) | Y | Organization Identifier |
IBY.IBY_PROCESS_ORGS does not reference any database object
IBY.IBY_PROCESS_ORGS is referenced by following:
| Description: |
|---|
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_PYO_INVOICE_GT_N1 | NONUNIQUE |
PAYMENT_INSTRUCTION_ID
PAYMENT_ID VENDOR_ID VENDOR_SITE_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYMENT_ID | NUMBER | (15) | ||
| PAYMENT_INSTRUCTION_ID | NUMBER | (15) | ||
| PAY_SELECTED_CHECK_ID | VARCHAR2 | (100) | ||
| VENDOR_NUM | VARCHAR2 | (30) | ||
| CUSTOMER_NUM | VARCHAR2 | (100) | ||
| INVOICE_NUM | VARCHAR2 | (100) | Y | |
| INVOICE_DATE | DATE | Y | ||
| INVOICE_DESCRIPTION | VARCHAR2 | (255) | ||
| PROPOSED_PAYMENT_AMOUNT | NUMBER | Y | ||
| INVOICE_AMOUNT | NUMBER | Y | ||
| DISCOUNT_AMOUNT | VARCHAR2 | (100) | ||
| PRINT_SELECTED_CHECK_ID | VARCHAR2 | (100) | ||
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | ||
| ATTRIBUTE1 | VARCHAR2 | (150) | ||
| ATTRIBUTE2 | VARCHAR2 | (150) | ||
| ATTRIBUTE3 | VARCHAR2 | (150) | ||
| ATTRIBUTE4 | VARCHAR2 | (150) | ||
| ATTRIBUTE5 | VARCHAR2 | (150) | ||
| ATTRIBUTE6 | VARCHAR2 | (150) | ||
| ATTRIBUTE7 | VARCHAR2 | (150) | ||
| ATTRIBUTE8 | VARCHAR2 | (150) | ||
| ATTRIBUTE9 | VARCHAR2 | (150) | ||
| ATTRIBUTE10 | VARCHAR2 | (150) | ||
| ATTRIBUTE11 | VARCHAR2 | (150) | ||
| ATTRIBUTE12 | VARCHAR2 | (150) | ||
| ATTRIBUTE13 | VARCHAR2 | (150) | ||
| ATTRIBUTE14 | VARCHAR2 | (150) | ||
| ATTRIBUTE15 | VARCHAR2 | (150) | ||
| INV_GLOBAL_ATTRIBUTE_CATEGORY | VARCHAR2 | (240) | ||
| INV_GLOBAL_ATTRIBUTE1 | VARCHAR2 | (240) | ||
| INV_GLOBAL_ATTRIBUTE2 | VARCHAR2 | (240) | ||
| INV_GLOBAL_ATTRIBUTE3 | VARCHAR2 | (240) | ||
| INV_GLOBAL_ATTRIBUTE4 | VARCHAR2 | (240) | ||
| INV_GLOBAL_ATTRIBUTE5 | VARCHAR2 | (240) | ||
| INV_GLOBAL_ATTRIBUTE6 | VARCHAR2 | (240) | ||
| INV_GLOBAL_ATTRIBUTE7 | VARCHAR2 | (240) | ||
| INV_GLOBAL_ATTRIBUTE8 | VARCHAR2 | (240) | ||
| INV_GLOBAL_ATTRIBUTE9 | VARCHAR2 | (240) | ||
| INV_GLOBAL_ATTRIBUTE10 | VARCHAR2 | (240) | ||
| INV_GLOBAL_ATTRIBUTE11 | VARCHAR2 | (240) | ||
| INV_GLOBAL_ATTRIBUTE12 | VARCHAR2 | (240) | ||
| INV_GLOBAL_ATTRIBUTE13 | VARCHAR2 | (240) | ||
| INV_GLOBAL_ATTRIBUTE14 | VARCHAR2 | (240) | ||
| INV_GLOBAL_ATTRIBUTE15 | VARCHAR2 | (240) | ||
| INV_GLOBAL_ATTRIBUTE16 | VARCHAR2 | (240) | ||
| INV_GLOBAL_ATTRIBUTE17 | VARCHAR2 | (240) | ||
| INV_GLOBAL_ATTRIBUTE18 | VARCHAR2 | (240) | ||
| INV_GLOBAL_ATTRIBUTE19 | VARCHAR2 | (240) | ||
| INV_GLOBAL_ATTRIBUTE20 | VARCHAR2 | (240) | ||
| BANK_CHARGE_BEARER | VARCHAR2 | (30) | ||
| PAYMENT_REASON_CODE | VARCHAR2 | (30) | ||
| PAYMENT_REASON_COMMENTS | VARCHAR2 | (240) | ||
| REMITTANCE_MESSAGE1 | VARCHAR2 | (150) | ||
| REMITTANCE_MESSAGE2 | VARCHAR2 | (150) | ||
| REMITTANCE_MESSAGE3 | VARCHAR2 | (150) | ||
| UNIQUE_REMITTANCE_IDENTIFIER | VARCHAR2 | (30) | ||
| URI_CHECK_DIGIT | VARCHAR2 | (2) | ||
| DELIVERY_CHANNEL_CODE | VARCHAR2 | (30) | ||
| SETTLEMENT_PRIORITY | VARCHAR2 | (30) | ||
| EXTERNAL_BANK_ACCOUNT_ID | NUMBER | (15) | ||
| PAYMENT_METHOD_CODE | VARCHAR2 | (30) | Y | |
| VENDOR_ID | NUMBER | |||
| VENDOR_SITE_ID | NUMBER | (15) | ||
| PAYMENT_MEAN | VARCHAR2 | (150) | ||
| PAYMENT_CHANNEL | VARCHAR2 | (150) | ||
| COUNTRY | VARCHAR2 | (60) | ||
| PAYMENT_PROCESS_REQUEST_NAME | VARCHAR2 | (255) | ||
| BANK_ACCOUNT_ID | NUMBER | (15) | ||
| VENDOR_BANK_ACCOUNT_ID | NUMBER | (15) | ||
| PAYMENT_REFERENCE_NUMBER | NUMBER | (15) | ||
| CHECK_NUMBER | NUMBER | (15) | ||
| AMOUNT_WITHHELD | NUMBER | |||
| CALLING_APP_ID | NUMBER | (15) | ||
| CALLING_APP_DOC_UNIQUE_REF1 | VARCHAR2 | (100) | ||
| CALLING_APP_DOC_UNIQUE_REF2 | VARCHAR2 | (100) | ||
| CALLING_APP_DOC_UNIQUE_REF3 | VARCHAR2 | (100) | ||
| CALLING_APP_DOC_UNIQUE_REF4 | VARCHAR2 | (100) | ||
| CALLING_APP_DOC_UNIQUE_REF5 | VARCHAR2 | (100) | ||
| DOCUMENT_SEQUENCE_ID | NUMBER | |||
| DOCUMENT_SEQUENCE_VALUE | NUMBER | |||
| DOCUMENT_CATEGORY_CODE | VARCHAR2 | (30) |
APPS.IBY_PYO_INVOICE_GT does not reference any database object
APPS.IBY_PYO_INVOICE_GT is referenced by following:
| Description: |
|---|
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_PYO_PAYMENT_GT_N1 | NONUNIQUE | DOCUMENT_CODE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| COMMUNICATION_METHOD | CHAR | (3) | ||
| TEST_FLAG | VARCHAR2 | (1) | ||
| DOCUMENT_ID | CHAR | (3) | ||
| DOCUMENT_CODE | NUMBER | (15) | Y | |
| BK_TP_TRANSLATOR_CODE | VARCHAR2 | (30) | ||
| BK_TP_LOCATION_CODE_EXT | VARCHAR2 | (40) | ||
| BK_TP_DESCRIPTION | VARCHAR2 | (240) | ||
| BK_TP_REFERENCE_EXT1 | VARCHAR2 | (240) | ||
| BK_TP_REFERENCE_EXT2 | VARCHAR2 | (240) | ||
| TRANSACTION_DATE | DATE | |||
| TPH_ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | ||
| TPH_ATTRIBUTE1 | VARCHAR2 | (150) | ||
| TPH_ATTRIBUTE2 | VARCHAR2 | (150) | ||
| TPH_ATTRIBUTE3 | VARCHAR2 | (150) | ||
| TPH_ATTRIBUTE4 | VARCHAR2 | (150) | ||
| TPH_ATTRIBUTE5 | VARCHAR2 | (150) | ||
| TPH_ATTRIBUTE6 | VARCHAR2 | (150) | ||
| TPH_ATTRIBUTE7 | VARCHAR2 | (150) | ||
| TPH_ATTRIBUTE8 | VARCHAR2 | (150) | ||
| TPH_ATTRIBUTE9 | VARCHAR2 | (150) | ||
| TPH_ATTRIBUTE10 | VARCHAR2 | (150) | ||
| TPH_ATTRIBUTE11 | VARCHAR2 | (150) | ||
| TPH_ATTRIBUTE12 | VARCHAR2 | (150) | ||
| TPH_ATTRIBUTE13 | VARCHAR2 | (150) | ||
| TPH_ATTRIBUTE14 | VARCHAR2 | (150) | ||
| TPH_ATTRIBUTE15 | VARCHAR2 | (150) | ||
| TPD_ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | ||
| TPD_ATTRIBUTE1 | VARCHAR2 | (150) | ||
| TPD_ATTRIBUTE2 | VARCHAR2 | (150) | ||
| TPD_ATTRIBUTE3 | VARCHAR2 | (150) | ||
| TPD_ATTRIBUTE4 | VARCHAR2 | (150) | ||
| TPD_ATTRIBUTE5 | VARCHAR2 | (150) | ||
| DOCUMENT_STANDARD | VARCHAR2 | (30) | ||
| TRANSACTION_HANDLING_CODE | VARCHAR2 | (30) | ||
| CHECK_AMOUNT | NUMBER | Y | ||
| CURRENCY_CODE | VARCHAR2 | (10) | Y | |
| EDI_PAYMENT_METHOD | VARCHAR2 | (30) | Y | |
| EDI_PAYMENT_FORMAT | VARCHAR2 | (30) | ||
| BANK_BRANCH_TYPE | VARCHAR2 | (30) | ||
| BANK_ACCOUNT_TYPE | VARCHAR2 | (25) | ||
| BANK_ACCOUNT_NUM | VARCHAR2 | (30) | ||
| BANK_EDI_ID_NUMBER | VARCHAR2 | (30) | ||
| VENDOR_BANK_BRANCH_TYPE | VARCHAR2 | (30) | ||
| VENDOR_BANK_ACCOUNT_TYPE | VARCHAR2 | (25) | ||
| VENDOR_BANK_ACCOUNT_NUM | VARCHAR2 | (100) | ||
| PAYMENT_DATE | DATE | |||
| BANK_NUM | VARCHAR2 | (30) | ||
| VENDOR_BANK_NUM | VARCHAR2 | (30) | ||
| EDI_REMITTANCE_METHOD | VARCHAR2 | (30) | ||
| EDI_REMITTANCE_INSTRUCTION | VARCHAR2 | (150) | ||
| PAYMENT_INSTRUCTION_ID | NUMBER | (15) | ||
| CHECK_VOUCHER_NUM | VARCHAR2 | (100) | ||
| SELECTED_CHECK_ID | VARCHAR2 | (100) | ||
| CHECK_NUMBER | NUMBER | (15) | ||
| CUSTOMER_NUM | VARCHAR2 | (25) | ||
| SEGMENT1 | VARCHAR2 | (30) | ||
| VENDOR_EDI_ID_NUMBER | VARCHAR2 | (30) | ||
| SEGMENT2 | VARCHAR2 | (30) | ||
| SEGMENT3 | VARCHAR2 | (30) | ||
| SEGMENT4 | VARCHAR2 | (30) | ||
| SEGMENT5 | VARCHAR2 | (30) | ||
| BANK_BRANCH_ID | NUMBER | |||
| BK_BANK_BRANCH_NAME | VARCHAR2 | (360) | ||
| BK_ADDRESS_LINE1 | VARCHAR2 | (240) | ||
| BK_ADDRESS_LINE2 | VARCHAR2 | (240) | ||
| BK_ADDRESS_LINE3 | VARCHAR2 | (240) | ||
| BK_CITY | VARCHAR2 | (60) | ||
| BK_ZIP | VARCHAR2 | (60) | ||
| BK_COUNTRY | VARCHAR2 | (60) | ||
| BK_STATE | VARCHAR2 | (60) | ||
| BK_PROVINCE | VARCHAR2 | (60) | ||
| BK_CONTACT_FIRST_NAME | VARCHAR2 | (100) | ||
| BK_CONTACT_MIDDLE_NAME | VARCHAR2 | (100) | ||
| BK_CONTACT_LAST_NAME | VARCHAR2 | (100) | ||
| BK_CONTACT_TITLE | VARCHAR2 | (100) | ||
| BK_CONTACT_PREFIX | VARCHAR2 | (100) | ||
| BK_CONTACT_AREA_CODE | VARCHAR2 | (100) | ||
| BK_CONTACT_PHONE | VARCHAR2 | (100) | ||
| VENDOR_SITE_CODE | VARCHAR2 | (15) | ||
| VENDOR_NAME | VARCHAR2 | (360) | ||
| ADDRESS_LINE1 | VARCHAR2 | (240) | ||
| ADDRESS_LINE2 | VARCHAR2 | (240) | ||
| ADDRESS_LINE3 | VARCHAR2 | (240) | ||
| ADDRESS_LINE4 | VARCHAR2 | (240) | ||
| CITY | VARCHAR2 | (60) | ||
| ZIP | VARCHAR2 | (60) | ||
| COUNTRY | VARCHAR2 | (60) | ||
| STATE | VARCHAR2 | (120) | ||
| PROVINCE | VARCHAR2 | (120) | ||
| ABA_GLOBAL_ATTRIBUTE_CATEGORY | VARCHAR2 | (100) | ||
| ABA_GLOBAL_ATTRIBUTE1 | VARCHAR2 | (100) | ||
| ABA_GLOBAL_ATTRIBUTE2 | VARCHAR2 | (100) | ||
| ABA_GLOBAL_ATTRIBUTE3 | VARCHAR2 | (100) | ||
| ABA_GLOBAL_ATTRIBUTE4 | VARCHAR2 | (100) | ||
| ABA_GLOBAL_ATTRIBUTE5 | VARCHAR2 | (100) | ||
| ABA_GLOBAL_ATTRIBUTE6 | VARCHAR2 | (100) | ||
| ABA_GLOBAL_ATTRIBUTE7 | VARCHAR2 | (100) | ||
| ABA_GLOBAL_ATTRIBUTE8 | VARCHAR2 | (100) | ||
| ABA_GLOBAL_ATTRIBUTE9 | VARCHAR2 | (100) | ||
| ABA_GLOBAL_ATTRIBUTE10 | VARCHAR2 | (100) | ||
| ABA_GLOBAL_ATTRIBUTE11 | VARCHAR2 | (100) | ||
| ABA_GLOBAL_ATTRIBUTE12 | VARCHAR2 | (100) | ||
| ABA_GLOBAL_ATTRIBUTE13 | VARCHAR2 | (100) | ||
| ABA_GLOBAL_ATTRIBUTE14 | VARCHAR2 | (100) | ||
| ABA_GLOBAL_ATTRIBUTE15 | VARCHAR2 | (100) | ||
| ABA_GLOBAL_ATTRIBUTE16 | VARCHAR2 | (100) | ||
| ABA_GLOBAL_ATTRIBUTE17 | VARCHAR2 | (100) | ||
| ABA_GLOBAL_ATTRIBUTE18 | VARCHAR2 | (100) | ||
| ABA_GLOBAL_ATTRIBUTE19 | VARCHAR2 | (100) | ||
| ABA_GLOBAL_ATTRIBUTE20 | VARCHAR2 | (100) | ||
| ABAS_GLOBAL_ATTRIBUTE_CATEGORY | VARCHAR2 | (100) | ||
| ABAS_GLOBAL_ATTRIBUTE1 | VARCHAR2 | (100) | ||
| ABAS_GLOBAL_ATTRIBUTE2 | VARCHAR2 | (100) | ||
| ABAS_GLOBAL_ATTRIBUTE3 | VARCHAR2 | (60) | ||
| ABAS_GLOBAL_ATTRIBUTE4 | VARCHAR2 | (100) | ||
| ABAS_GLOBAL_ATTRIBUTE5 | VARCHAR2 | (30) | ||
| ABAS_GLOBAL_ATTRIBUTE6 | VARCHAR2 | (100) | ||
| ABAS_GLOBAL_ATTRIBUTE7 | VARCHAR2 | (100) | ||
| ABAS_GLOBAL_ATTRIBUTE8 | VARCHAR2 | (30) | ||
| ABAS_GLOBAL_ATTRIBUTE9 | VARCHAR2 | (100) | ||
| ABAS_GLOBAL_ATTRIBUTE10 | VARCHAR2 | (100) | ||
| ABAS_GLOBAL_ATTRIBUTE11 | VARCHAR2 | (100) | ||
| ABAS_GLOBAL_ATTRIBUTE12 | VARCHAR2 | (100) | ||
| ABAS_GLOBAL_ATTRIBUTE13 | VARCHAR2 | (100) | ||
| ABAS_GLOBAL_ATTRIBUTE14 | VARCHAR2 | (100) | ||
| ABAS_GLOBAL_ATTRIBUTE15 | VARCHAR2 | (100) | ||
| ABAS_GLOBAL_ATTRIBUTE16 | VARCHAR2 | (100) | ||
| ABAS_GLOBAL_ATTRIBUTE17 | VARCHAR2 | (100) | ||
| ABAS_GLOBAL_ATTRIBUTE18 | VARCHAR2 | (100) | ||
| ABAS_GLOBAL_ATTRIBUTE19 | VARCHAR2 | (100) | ||
| ABAS_GLOBAL_ATTRIBUTE20 | VARCHAR2 | (100) | ||
| PVS_GLOBAL_ATTRIBUTE_CATEGORY | VARCHAR2 | (30) | ||
| PVS_GLOBAL_ATTRIBUTE1 | VARCHAR2 | (150) | ||
| PVS_GLOBAL_ATTRIBUTE2 | VARCHAR2 | (150) | ||
| PVS_GLOBAL_ATTRIBUTE3 | VARCHAR2 | (150) | ||
| PVS_GLOBAL_ATTRIBUTE4 | VARCHAR2 | (150) | ||
| PVS_GLOBAL_ATTRIBUTE5 | VARCHAR2 | (150) | ||
| PVS_GLOBAL_ATTRIBUTE6 | VARCHAR2 | (150) | ||
| PVS_GLOBAL_ATTRIBUTE7 | VARCHAR2 | (150) | ||
| PVS_GLOBAL_ATTRIBUTE8 | VARCHAR2 | (150) | ||
| PVS_GLOBAL_ATTRIBUTE9 | VARCHAR2 | (150) | ||
| PVS_GLOBAL_ATTRIBUTE10 | VARCHAR2 | (150) | ||
| PVS_GLOBAL_ATTRIBUTE11 | VARCHAR2 | (150) | ||
| PVS_GLOBAL_ATTRIBUTE12 | VARCHAR2 | (150) | ||
| PVS_GLOBAL_ATTRIBUTE13 | VARCHAR2 | (150) | ||
| PVS_GLOBAL_ATTRIBUTE14 | VARCHAR2 | (150) | ||
| PVS_GLOBAL_ATTRIBUTE15 | VARCHAR2 | (150) | ||
| PVS_GLOBAL_ATTRIBUTE16 | VARCHAR2 | (150) | ||
| PVS_GLOBAL_ATTRIBUTE17 | VARCHAR2 | (150) | ||
| PVS_GLOBAL_ATTRIBUTE18 | VARCHAR2 | (150) | ||
| PVS_GLOBAL_ATTRIBUTE19 | VARCHAR2 | (150) | ||
| PVS_GLOBAL_ATTRIBUTE20 | VARCHAR2 | (150) | ||
| BK_EFT_SWIFT_CODE | VARCHAR2 | (30) | ||
| SBK_BANK_BRANCH_NUMBER | VARCHAR2 | (30) | ||
| SBK_BANK_BRANCH_NAME | VARCHAR2 | (360) | ||
| SBK_ADDRESS_LINE1 | VARCHAR2 | (240) | ||
| SBK_ADDRESS_LINE2 | VARCHAR2 | (240) | ||
| SBK_ADDRESS_LINE3 | VARCHAR2 | (240) | ||
| SBK_CITY | VARCHAR2 | (60) | ||
| SBK_STATE | VARCHAR2 | (60) | ||
| SBK_ZIP | VARCHAR2 | (60) | ||
| SBK_PROVINCE | VARCHAR2 | (60) | ||
| SBK_COUNTRY | VARCHAR2 | (60) | ||
| SBK_EFT_SWIFT_CODE | VARCHAR2 | (30) | ||
| BILL_TO_INT_LOCATION_NAME | VARCHAR2 | (60) | ||
| BILL_TO_INT_ADDRESS1 | VARCHAR2 | (240) | ||
| BILL_TO_INT_ADDRESS2 | VARCHAR2 | (240) | ||
| BILL_TO_INT_ADDRESS3 | VARCHAR2 | (240) | ||
| BILL_TO_INT_CITY | VARCHAR2 | (30) | ||
| BILL_TO_INT_POSTAL_CODE | VARCHAR2 | (30) | ||
| BILL_TO_INT_COUNTRY | VARCHAR2 | (60) | ||
| FI_VAT_REGISTRATION_NUM | VARCHAR2 | (50) | ||
| BILL_TO_INT_LOCATION_ID | NUMBER | (15) | ||
| ECE_TP_LOCATION_CODE | VARCHAR2 | (35) | ||
| BILL_TO_INT_REGION1 | VARCHAR2 | (120) | ||
| BILL_TO_INT_REGION2 | VARCHAR2 | (120) | ||
| BILL_TO_INT_REGION3 | VARCHAR2 | (120) | ||
| MAP_ID | NUMBER | (15) | ||
| FUTURE_PAY_DUE_DATE | DATE | |||
| VENDOR_ALTERNATE_NAME | VARCHAR2 | (320) | ||
| VENDOR_ALTERNATE_SITE_CODE | VARCHAR2 | (320) | ||
| SUPPLIER_CHECK_DIGITS | VARCHAR2 | (2) | ||
| SBK_BANK_NAME | VARCHAR2 | (360) | ||
| IBAN_NUMBER | VARCHAR2 | (50) | ||
| VENDOR_IBAN_NUMBER | VARCHAR2 | (50) | ||
| PAYMENT_MEAN | VARCHAR2 | (150) | ||
| PAYMENT_CHANNEL | VARCHAR2 | (150) | ||
| VENDOR_ID | NUMBER | |||
| VENDOR_SITE_ID | NUMBER | |||
| PAYMENT_REFERENCE_NUMBER | NUMBER | (15) | ||
| SBK_BANK_CODE | VARCHAR2 | (30) | ||
| PAYMENT_PROCESS_REQUEST_NAME | VARCHAR2 | (255) | ||
| PAYMENT_ORG_ID | NUMBER | (15) | ||
| BANK_NAME | VARCHAR2 | (360) | ||
| BRANCH_NUMBER | VARCHAR2 | (30) | ||
| BANK_ACCOUNT_ID | NUMBER | (15) | ||
| BANK_ACCOUNT_NAME | VARCHAR2 | (100) | ||
| BK_ACCT_ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | ||
| BK_ACCT_ATTRIBUTE1 | VARCHAR2 | (150) | ||
| BK_ACCT_ATTRIBUTE2 | VARCHAR2 | (150) | ||
| BK_ACCT_ATTRIBUTE3 | VARCHAR2 | (150) | ||
| BK_ACCT_ATTRIBUTE4 | VARCHAR2 | (150) | ||
| BK_ACCT_ATTRIBUTE5 | VARCHAR2 | (150) | ||
| BK_ACCT_ATTRIBUTE6 | VARCHAR2 | (150) | ||
| BK_ACCT_ATTRIBUTE7 | VARCHAR2 | (150) | ||
| BK_ACCT_ATTRIBUTE8 | VARCHAR2 | (150) | ||
| BK_ACCT_ATTRIBUTE9 | VARCHAR2 | (150) | ||
| BK_ACCT_ATTRIBUTE10 | VARCHAR2 | (150) | ||
| BK_ACCT_ATTRIBUTE11 | VARCHAR2 | (150) | ||
| BK_ACCT_ATTRIBUTE12 | VARCHAR2 | (150) | ||
| BK_ACCT_ATTRIBUTE13 | VARCHAR2 | (150) | ||
| BK_ACCT_ATTRIBUTE14 | VARCHAR2 | (150) | ||
| BK_ACCT_ATTRIBUTE15 | VARCHAR2 | (150) | ||
| VENDOR_BANK_ACCOUNT_ID | NUMBER | (15) | ||
| SBK_ACCT_ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | ||
| SBK_ACCT_ATTRIBUTE1 | VARCHAR2 | (150) | ||
| SBK_ACCT_ATTRIBUTE2 | VARCHAR2 | (150) | ||
| SBK_ACCT_ATTRIBUTE3 | VARCHAR2 | (150) | ||
| SBK_ACCT_ATTRIBUTE4 | VARCHAR2 | (150) | ||
| SBK_ACCT_ATTRIBUTE5 | VARCHAR2 | (150) | ||
| SBK_ACCT_ATTRIBUTE6 | VARCHAR2 | (150) | ||
| SBK_ACCT_ATTRIBUTE7 | VARCHAR2 | (150) | ||
| SBK_ACCT_ATTRIBUTE8 | VARCHAR2 | (150) | ||
| SBK_ACCT_ATTRIBUTE9 | VARCHAR2 | (150) | ||
| SBK_ACCT_ATTRIBUTE10 | VARCHAR2 | (150) | ||
| SBK_ACCT_ATTRIBUTE11 | VARCHAR2 | (150) | ||
| SBK_ACCT_ATTRIBUTE12 | VARCHAR2 | (150) | ||
| SBK_ACCT_ATTRIBUTE13 | VARCHAR2 | (150) | ||
| SBK_ACCT_ATTRIBUTE14 | VARCHAR2 | (150) | ||
| SBK_ACCT_ATTRIBUTE15 | VARCHAR2 | (150) | ||
| VEND_SITE_COUNTY | VARCHAR2 | (150) | ||
| VEND_SITE_ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | ||
| VEND_SITE_ATTRIBUTE1 | VARCHAR2 | (150) | ||
| VEND_SITE_ATTRIBUTE2 | VARCHAR2 | (150) | ||
| VEND_SITE_ATTRIBUTE3 | VARCHAR2 | (150) | ||
| VEND_SITE_ATTRIBUTE4 | VARCHAR2 | (150) | ||
| VEND_SITE_ATTRIBUTE5 | VARCHAR2 | (150) | ||
| VEND_SITE_ATTRIBUTE6 | VARCHAR2 | (150) | ||
| VEND_SITE_ATTRIBUTE7 | VARCHAR2 | (150) | ||
| VEND_SITE_ATTRIBUTE8 | VARCHAR2 | (150) | ||
| VEND_SITE_ATTRIBUTE9 | VARCHAR2 | (150) | ||
| VEND_SITE_ATTRIBUTE10 | VARCHAR2 | (150) | ||
| VEND_SITE_ATTRIBUTE11 | VARCHAR2 | (150) | ||
| VEND_SITE_ATTRIBUTE12 | VARCHAR2 | (150) | ||
| VEND_SITE_ATTRIBUTE13 | VARCHAR2 | (150) | ||
| VEND_SITE_ATTRIBUTE14 | VARCHAR2 | (150) | ||
| VEND_SITE_ATTRIBUTE15 | VARCHAR2 | (150) | ||
| VENDOR_TYPE_LOOKUP_CODE | VARCHAR2 | (30) | ||
| VENDOR_ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | ||
| VENDOR_ATTRIBUTE1 | VARCHAR2 | (150) | ||
| VENDOR_ATTRIBUTE2 | VARCHAR2 | (150) | ||
| VENDOR_ATTRIBUTE3 | VARCHAR2 | (150) | ||
| VENDOR_ATTRIBUTE4 | VARCHAR2 | (150) | ||
| VENDOR_ATTRIBUTE5 | VARCHAR2 | (150) | ||
| VENDOR_ATTRIBUTE6 | VARCHAR2 | (150) | ||
| VENDOR_ATTRIBUTE7 | VARCHAR2 | (150) | ||
| VENDOR_ATTRIBUTE8 | VARCHAR2 | (150) | ||
| VENDOR_ATTRIBUTE9 | VARCHAR2 | (150) | ||
| VENDOR_ATTRIBUTE10 | VARCHAR2 | (150) | ||
| VENDOR_ATTRIBUTE11 | VARCHAR2 | (150) | ||
| VENDOR_ATTRIBUTE12 | VARCHAR2 | (150) | ||
| VENDOR_ATTRIBUTE13 | VARCHAR2 | (150) | ||
| VENDOR_ATTRIBUTE14 | VARCHAR2 | (150) | ||
| VENDOR_ATTRIBUTE15 | VARCHAR2 | (150) |
APPS.IBY_PYO_PAYMENT_GT does not reference any database object
APPS.IBY_PYO_PAYMENT_GT is referenced by following:
| Description: | IBY_REMIT_ADVICE_SETUP stores information on creating and delivering remittance information, or remittance advice, for a payee separately from the payment itself. Remittance advice setup is organized by payment process profile. Each payment |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_REMIT_ADVICE_SETUP.SYSTEM_PROFILE_CODE | IBY_SYS_PMT_PROFILES_B |
| IBY_REMIT_ADVICE_SETUP.REMITTANCE_ADVICE_FORMAT_CODE | IBY_FORMATS_B |
IBY_REMIT_ADVICE_SETUP stores information on creating and delivering remittance information, or remittance advice, for a payee separately from the payment itself. Remittance advice setup is organized by payment process profile. Each payment process profile for which remittance advice is required has a row in this table, which specifes how the remittance advice is to be created and delivered to the payer. This table corresponds to the Separate Remittance Advice region on the Payment Process Profiles page.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_REMIT_ADVICE_SETUP_U1 | UNIQUE | APPS_TS_TX_IDX |
SYSTEM_PROFILE_CODE
ZD_EDITION_NAME |
| IBY_REMIT_ADVICE_SETUP_N1 | NONUNIQUE | APPS_TS_TX_IDX | REMITTANCE_ADVICE_FORMAT_CODE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| SYSTEM_PROFILE_CODE | VARCHAR2 | (100) | Y | Unique primary key |
| DOCUMENT_COUNT_LIMIT | NUMBER | This number acts as a rule for inclusion of a payment in a remittance advice. If the number of documents within a payment exceeds this number, then the payment is included in a remittance advice. | ||
| ALLOW_MULTIPLE_COPY_FLAG | VARCHAR2 | (1) | Y or N flag indicating whether multiple copies of the remittance advice can be created for a payment instruction | |
| SEEDED_FLAG | VARCHAR2 | (1) | Y or N flag controlling updatability of records. Y indicates record was seeded by Oracle and may have user updates limited. | |
| PAYMENT_DETAILS_LENGTH_LIMIT | NUMBER | Maximum length of the payment detail record. Typically this is a type of description record in a payment format that allows concatenated details of the payment to be included, for example, invoices paid. If the length is exceeded, then the payment is included in a remittance advice. | ||
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number | |
| REMITTANCE_ADVICE_FORMAT_CODE | VARCHAR2 | (30) | Remittance format code | |
| SRA_OVERRIDE_PAYEE_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether the delivery method preference in the payment process profile overrides the setting at the payee level. Y to override, N otherwise. |
| REMIT_ADVICE_DELIVERY_METHOD | VARCHAR2 | (100) | Remittance advice delivery method. Values from the lookup IBY_DELIVERY_METHODS include EMAIL, FAX, and PRINTED. | |
| AUTOMATIC_SRA_SUBMIT_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether the remittance advice should be submitted automatically at payment completion point. |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_REMIT_ADVICE_SETUP does not reference any database object
IBY.IBY_REMIT_ADVICE_SETUP is referenced by following:
| Description: | Result codes |
|---|
Result codes
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_RESULT_CODES_U1 | UNIQUE | APPS_TS_TX_IDX |
REQUEST_INTERFACE_CODE
RESULT_CODE ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| RESULT_CODE | VARCHAR2 | (30) | Y | API result code |
| REQUEST_INTERFACE_CODE | VARCHAR2 | (30) | Y | Code that the public interface result code belongs to |
| RESULT_CATEGORY | VARCHAR2 | (30) | Y | General category of the API result |
| MESSAGE_NAME | VARCHAR2 | (30) | Y | FND message code for the API result |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_RESULT_CODES does not reference any database object
IBY.IBY_RESULT_CODES is referenced by following:
| Description: | 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 customer who wants to purchase its goods and services. Risk Management feature will contain bundled |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_RISK_FORMULA_ITEM.RISK_FACTOR_ID | IBY_RISK_FACTORS |
IBY_RISK_FACTORS stores information about the risk factors. These are factors which a merchant uses to evaluate the risk of the customer who wants to purchase its goods and services. The Risk Management feature contains bundled risk factors which can be set up at the site level.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_RISK_FACTORS_FACTORID_U1 | UNIQUE | APPS_TS_TX_IDX |
RISK_FACTOR_ID
ZD_EDITION_NAME |
| IBY_RISK_FACTOR_NAME_U2 | UNIQUE | APPS_TS_TX_IDX |
RISK_FACTOR_CODE
ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| RISK_FACTOR_ID | NUMBER | (15) | Y | System-generated unique identifier for a particular risk factor |
| RISK_FACTOR_CODE | VARCHAR2 | (30) | Y | Look up type to fnd_lookups |
| FACTOR_TYPE | NUMBER | (15) | Y | Risk factor type |
| INTERFACE_NAME | VARCHAR2 | (240) | Class name of the object, which will be loaded dynamically at runtime | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| OBJECT_VERSION_NUMBER | NUMBER | (5) | Y | Used for locking purposes that subsequently allows for checking if there is old data on the screen compared to what is in the database. The situation occurs when the HTML application is an stateless application. |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| CREATION_DATE | DATE | Y | Standard Who column | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| SECURITY_GROUP_ID | NUMBER | Used in hosted environments | ||
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_RISK_FACTORS does not reference any database object
IBY.IBY_RISK_FACTORS is referenced by following:
| Description: | IBY_RISK_FORMULAS stores risk formula retaled information . Risk Formula is used by merchants to evaluate the risk of the customer. This formula could be different for different goods/services offered by the merchants. A Risk Formula may be |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_RISK_FORMULAS.PAYEEID | IBY_PAYEE |
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_RISK_FORMULA_ITEM.RISK_FORMULA_ID | IBY_RISK_FORMULAS |
IBY_RISK_FORMULAS stores risk formula-retaled information. Risk formulas are used by merchants to evaluate the risk of the customer. This formula can be different for different goods or services offered by the merchants. A risk formula may be comprised of multiple risk factors with varying weights assigned to each one.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_RISK_FORMULA_ID_U2 | UNIQUE | APPS_TS_TX_IDX | RISK_FORMULA_ID |
| IBY_RISK_FORMULAS_N1 | NONUNIQUE | APPS_TS_TX_IDX | PAYEEID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| RISK_FORMULA_ID | NUMBER | (15) | Y | System-generated unique identifier for a particular risk formula |
| FORMULA_NAME | VARCHAR2 | (80) | Y | Risk formula name |
| DESCRIPTION | VARCHAR2 | (240) | Description of the risk formula | |
| PAYEEID | VARCHAR2 | (80) | Y | Payee associated with this risk formula |
| IMPLICIT_FLAG | NUMBER | (2) | Flag indicating that the formula is implicit or not. Valid values are 0 and 1. | |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Used for locking purposes that subsequently allows for checking if there is old data on the screen compared to what is in the database. The situation occurs when the HTML application is a stateless application. | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| SECURITY_GROUP_ID | NUMBER | Used in hosted environments |
IBY.IBY_RISK_FORMULAS does not reference any database object
IBY.IBY_RISK_FORMULAS is referenced by following:
| Description: | IBY_RISK_FORMULA_ITEM table is an intersection table between the IBY_RISK_FORMULA and IBY_RISK_FACTORS. It stores weight for different Risk Factors. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_RISK_FORMULA_ITEM.RISK_FACTOR_ID | IBY_RISK_FACTORS |
| IBY_RISK_FORMULA_ITEM.RISK_FORMULA_ID | IBY_RISK_FORMULAS |
IBY_RISK_FORMULA_ITEM is an intersection table between IBY_RISK_FORMULA and IBY_RISK_FACTORS. It stores weights for different risk factors. Weight is a number indicating the degree of importance assigned to a particular risk factor. Different merchants may assign different weights for the same risk factor, even if they are offering the same goods and services to the customer. Weights are in the range of 0, or no weight, to 100, which is full weight. Each weight is identified by a unique ID, which is generated by the system.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_RISK_FORMULAID_FACORTID_U1 | UNIQUE | APPS_TS_TX_IDX |
RISK_FACTOR_ID
RISK_FORMULA_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| WEIGHT | NUMBER | (15) | Y | Weights are in the range of 0 for no weight to 100 for full weight. |
| RISK_FORMULA_ID | NUMBER | (15) | Y | Risk Formula defining column |
| RISK_FACTOR_ID | NUMBER | (15) | Y | Risk factor defining column |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| OBJECT_VERSION_NUMBER | NUMBER | (5) | Y | Used for locking purposes that subsequently allows for checking if there is old data on the screen compared to what is in the database. The situation occurs when the HTML application is a stateless application. |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| CREATION_DATE | DATE | Y | Standard Who column | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| SECURITY_GROUP_ID | NUMBER | Used in hosted environments |
IBY.IBY_RISK_FORMULA_ITEM does not reference any database object
IBY.IBY_RISK_FORMULA_ITEM is referenced by following:
| Description: | IBY_ROUTINGINFO stores information that maps payment method to the payment system and funds capture process profile via conditions. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_ROUTINGINFO.BEPID | IBY_BEPINFO |
| IBY_ROUTINGINFO.MPAYEEID | IBY_PAYEE |
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_PMTMTHD_CONDITIONS.PAYMENTMETHODID | IBY_ROUTINGINFO |
IBY_ROUTINGINFO stores information that maps payment method to the payment system and funds capture process profile via conditions.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_RTINFO_PAYMENTMETHODID_U1 | UNIQUE | APPS_TS_TX_IDX | PAYMENTMETHODID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYEEID | VARCHAR2 | (80) | Payee Identifier passed by electronic commerce application | |
| BEPID | NUMBER | (15) | Y | Payment system Identifier |
| PAYMENTMETHODID | NUMBER | (15) | Y | System-generated identifier of the payment method |
| PAYMENTMETHODNAME | VARCHAR2 | (80) | Y | Name of the payment method |
| MPAYEEID | NUMBER | Payee Identifier | ||
| CONFIGURED | NUMBER | (2) | Y | Indicates whether payment method is active or not. 1 is active and 0 is inactive. |
| PRIORITY | NUMBER | (15) | Order in which the payment methods are selected | |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (5) | Y | Used for locking purposes that subsequently allows for checking if there is old data on the screen compared to what is in the database. The situation occurs when the HTML application is a stateless application. |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| SECURITY_GROUP_ID | NUMBER | Used in hosted environments | ||
| HITCOUNTER | NUMBER | (15) | Count of the number of times the routing rule was chosen | |
| INSTR_TYPE | VARCHAR2 | (30) | Y | Instrument type for which this routing rule applies. One of CREDITCARD, PURCHASECARD, or BANKACCOUNT |
| BEPKEY | VARCHAR2 | (80) | Merchant account Identifier associated with this routing rule | |
| INSTR_SUB_TYPE | VARCHAR2 | (30) | If INSTR_TYPE is BANKACCOUNT, subtype can be either ACH or BR | |
| INACTIVE_DATE | DATE | Inactive Date | ||
| FNDCPT_USER_PROFILE_CODE | VARCHAR2 | (30) | Funds capture process profile | |
| PAYMENT_CHANNEL_CODE | VARCHAR2 | (30) | Payment method | |
| BEP_ACCOUNT_ID | NUMBER | Payment system account |
IBY.IBY_ROUTINGINFO does not reference any database object
IBY.IBY_ROUTINGINFO is referenced by following:
| Description: | IBY_RULE_CONDITIONS stores the detail-level information for a payment method defaulting rule. Each row in the IBY_PAYMENT_RULES table has one or more rows in this table. Conditions of different types are combined with the AND logical operat |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_RULE_CONDITIONS.PAYMENT_RULE_ID | IBY_PAYMENT_RULES |
IBY_RULE_CONDITIONS stores the detail-level information for a payment method defaulting rule. Each row in the IBY_PAYMENT_RULES table has one or more rows in this table. Conditions of different types are combined with the AND logical operator. Conditions of the same type are combined with the OR logical operator. This table corresponds to the Payment Method Defaulting Rules page.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_RULE_CONDITIONS_U1 | UNIQUE | APPS_TS_TX_IDX | RULE_CONDITION_ID |
| IBY_RULE_CONDITIONS_N1 | NONUNIQUE | APPS_TS_TX_IDX | PAYMENT_RULE_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| RULE_CONDITION_ID | NUMBER | (15) | Y | System generated primary key |
| PAYMENT_RULE_ID | NUMBER | (15) | Y | Rule header Identifier |
| RULE_CONDITION_TYPE_CODE | VARCHAR2 | (30) | Y | Rule condition type. Each type corresponds to one driver parameter for payment method defaulting. Lookup values of IBY_PMT_MTHD_DEFAULTING_CONDITION lookup type |
| OPERATOR_CODE | VARCHAR2 | (30) | Y | Rule condition operator. Lookup codes, such as EQ, GT, LE, and others, which are defined by the IBY_PMT_MTHD_DEFAULTING_OPS lookup type. Applicable operators vary depending on the condition type. |
| RULE_CONDITION_VALUE | VARCHAR2 | (240) | Rule condition value | |
| STRING_VALUE_FLAG | VARCHAR2 | (1) | Y if the value is a string. Otherwise it is treated as a number. | |
| RULE_CONDITION_ENTRY_SEQUENCE | NUMBER | (15) | Number that denotes the order in which the user has entered the conditions. When queried, it needs to be displayed in the same order that the user has entered the rule condition. | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number |
IBY.IBY_RULE_CONDITIONS does not reference any database object
IBY.IBY_RULE_CONDITIONS is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_SECURITY_SEGMENTS.SEC_SUBKEY_ID | IBY_SYS_SECURITY_SUBKEYS |
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_BEP_ACCT_OPT_VALS.VAL_SEC_SEGMENT_ID | IBY_SECURITY_SEGMENTS |
| IBY_CREDITCARD.CHNAME_SEC_SEGMENT_ID | IBY_SECURITY_SEGMENTS |
| IBY_CREDITCARD.EXPIRY_SEC_SEGMENT_ID | IBY_SECURITY_SEGMENTS |
| IBY_CREDITCARD_H.CHNAME_SEC_SEGMENT_ID | IBY_SECURITY_SEGMENTS |
| IBY_EXT_BANK_ACCOUNTS.BA_NUM_SEC_SEGMENT_ID | IBY_SECURITY_SEGMENTS |
| IBY_EXT_BANK_ACCOUNTS.IBAN_SEC_SEGMENT_ID | IBY_SECURITY_SEGMENTS |
| IBY_FNDCPT_TX_EXTENSIONS.INSTR_CODE_SEC_SEGMENT_ID | IBY_SECURITY_SEGMENTS |
| IBY_EXT_BANK_ACCOUNTS.BA_NUM_ELEC_SEC_SEGMENT_ID | IBY_SECURITY_SEGMENTS |
| IBY_TRANSMIT_VALUES.VAL_SEC_SEGMENT_ID | IBY_SECURITY_SEGMENTS |
| IBY_TRXN_CORE.CHNAME_SEC_SEGMENT_ID | IBY_SECURITY_SEGMENTS |
| IBY_TRXN_CORE.EXPIRY_SEC_SEGMENT_ID | IBY_SECURITY_SEGMENTS |
Holds encrypted data such as credit card, debit card and bank account numbers. It also holds encrypted security codes for credit cards.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_SECURITY_SEGMENTS_U1 | UNIQUE | APPS_TS_TX_IDX | SEC_SEGMENT_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| SEC_SEGMENT_ID | NUMBER | (15) | Y | Primary key of the entity |
| SEGMENT_CIPHER_TEXT | RAW | (128) | Cipher text of encrypted data | |
| SEC_SUBKEY_ID | NUMBER | (15) | Y | Identifier of the sub-key encrypting the data |
| ENCODING_SCHEME | VARCHAR2 | (30) | Y | Binary encoding scheme used with data |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Object version number |
| CC_NUMBER_HASH1 | VARCHAR2 | (64) | No longer used | |
| CC_NUMBER_HASH2 | VARCHAR2 | (64) | No longer used | |
| CC_ISSUER_RANGE_ID | NUMBER | (15) | No longer used | |
| CC_NUMBER_LENGTH | NUMBER | (15) | No longer used | |
| CC_UNMASK_DIGITS | VARCHAR2 | (4) | No longer used | |
| SALT_VERSION | NUMBER | (2) | Salt Version used for Encryption |
IBY.IBY_SECURITY_SEGMENTS does not reference any database object
IBY.IBY_SECURITY_SEGMENTS is referenced by following:
| Description: | IBY_SETUP_TASKS stores the status of all Oracle Payments' setup tasks. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_SETUP_TASKS_TL.TASK_CODE | IBY_SETUP_TASKS_B |
IBY_SETUP_TASKS stores the status of all Oracle Payments' setup tasks.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_SETUP_TASKS_B_CODE_U1 | UNIQUE | APPS_TS_TX_IDX |
TASK_CODE
ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| TASK_CODE | VARCHAR2 | (30) | Y | Primary key for setup tasks |
| STATUS | VARCHAR2 | (30) | Lookup Type: IBY_TASK_STATUS | |
| LEAF_NODE_FLAG | VARCHAR2 | (1) | Y | Leaf node flag |
| PARENT_TASK_CODE | VARCHAR2 | (30) | Parent task code | |
| DEST_FUNCTION_NAME | VARCHAR2 | (100) | FND form function of the task setup page | |
| SETUP_FLOW_CODE | VARCHAR2 | (30) | Disbursements / Funds capture | |
| DISPLAY_ORDER | NUMBER | (15) | Display order | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_SETUP_TASKS_B does not reference any database object
IBY.IBY_SETUP_TASKS_B is referenced by following:
| Description: | IBY_SETUP_TASKS stores the status of all Oracle Payments' setup tasks. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_SETUP_TASKS_TL.TASK_CODE | IBY_SETUP_TASKS_B |
IBY_SETUP_TASKS stores the status of all Oracle Payments' setup tasks.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_SETUP_TASKS_TL_U1 | UNIQUE | APPS_TS_TX_IDX |
LANGUAGE
TASK_CODE ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| TASK_CODE | VARCHAR2 | (30) | Y | Primary key for setup tasks per language |
| TASK_NAME | VARCHAR2 | (100) | Name of the task | |
| LANGUAGE | VARCHAR2 | (4) | Y | Language code |
| SOURCE_LANG | VARCHAR2 | (4) | Y | Language code of the record's current language |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. |
| DESCRIPTION | VARCHAR2 | (240) | Description of the task | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_SETUP_TASKS_TL does not reference any database object
IBY.IBY_SETUP_TASKS_TL is referenced by following:
| Description: | "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 |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_SYS_PMT_PROFILES_B.BEPID | IBY_BEPINFO |
| IBY_SYS_PMT_PROFILES_B.TRANSMIT_PROTOCOL_CODE | IBY_TRANSMIT_PROTOCOLS_B |
| IBY_SYS_PMT_PROFILES_B.PAYMENT_FORMAT_CODE | IBY_FORMATS_B |
| IBY_SYS_PMT_PROFILES_B.POSITIVE_PAY_FORMAT_CODE | IBY_FORMATS_B |
| IBY_SYS_PMT_PROFILES_B.PAY_FILE_LETTER_FORMAT_CODE | IBY_FORMATS_B |
| IBY_SYS_PMT_PROFILES_B.BANK_INSTRUCTION1_CODE | IBY_BANK_INSTRUCTIONS_B |
| IBY_SYS_PMT_PROFILES_B.BANK_INSTRUCTION2_CODE | IBY_BANK_INSTRUCTIONS_B |
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_ACCT_PMT_PROFILES_B.SYSTEM_PROFILE_CODE | IBY_SYS_PMT_PROFILES_B |
| IBY_APPLICABLE_PMT_PROFS.SYSTEM_PROFILE_CODE | IBY_SYS_PMT_PROFILES_B |
| IBY_INSTR_CREATION_RULES.SYSTEM_PROFILE_CODE | IBY_SYS_PMT_PROFILES_B |
| IBY_PMT_LOGICAL_GRP_RULES.SYSTEM_PROFILE_CODE | IBY_SYS_PMT_PROFILES_B |
| IBY_REMIT_ADVICE_SETUP.SYSTEM_PROFILE_CODE | IBY_SYS_PMT_PROFILES_B |
| IBY_SYS_PMT_PROFILES_TL.SYSTEM_PROFILE_CODE | IBY_SYS_PMT_PROFILES_B |
| IBY_PMT_CREATION_RULES.SYSTEM_PROFILE_CODE | IBY_SYS_PMT_PROFILES_B |
IBY_SYS_PMT_PROFILES stores seeded information that specifies the bulk of payment processing behavior. The rest of the behavior is specified in a user-defined account payment process profile stored in IBY_ACCT_PMT_PROFILES. A combination of the two tables is defined in the view IBY_PAYMENT_PROFILES. The payment process profile as a whole controls the behavior of the payment process. To create a payment process profile, the user specifies how the payment instruction should be formatted, how it should be transmitted, how its acknowledgment and clearing files should be handled by the system, and other relevant information. This table corresponds to the Payment Process Profile pages.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_SYS_PMT_PROFILES_B_U1 | UNIQUE | APPS_TS_TX_IDX |
SYSTEM_PROFILE_CODE
ZD_EDITION_NAME |
| IBY_SYS_PMT_PROFILES_B_N1 | NONUNIQUE | APPS_TS_TX_IDX | BEPID |
| IBY_SYS_PMT_PROFILES_B_N2 | NONUNIQUE | APPS_TS_TX_IDX | TRANSMIT_PROTOCOL_CODE |
| IBY_SYS_PMT_PROFILES_B_N3 | NONUNIQUE | APPS_TS_TX_IDX | PAYMENT_FORMAT_CODE |
| IBY_SYS_PMT_PROFILES_B_N4 | NONUNIQUE | APPS_TS_TX_IDX | POSITIVE_PAY_FORMAT_CODE |
| IBY_SYS_PMT_PROFILES_B_N5 | NONUNIQUE | APPS_TS_TX_IDX | PAY_FILE_LETTER_FORMAT_CODE |
| IBY_SYS_PMT_PROFILES_B_N6 | NONUNIQUE | APPS_TS_TX_IDX | BANK_INSTRUCTION1_CODE |
| IBY_SYS_PMT_PROFILES_B_N7 | NONUNIQUE | APPS_TS_TX_IDX | BANK_INSTRUCTION2_CODE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| SYSTEM_PROFILE_CODE | VARCHAR2 | (100) | Y | The unique Payment Process profile code entered while defining the payment process profile. |
| BEPID | NUMBER | (15) | Payment system Id attached to the Payment process profile. | |
| SECURITY_PROTOCOL_CODE | VARCHAR2 | (100) | Security protocol Identifier | |
| TRANSMIT_PROTOCOL_CODE | VARCHAR2 | (100) | Transmission protocol Identifier | |
| PAYMENT_FORMAT_CODE | VARCHAR2 | (30) | Y | The Format attached to the Payment process profile for generating the payment instruction. |
| POSITIVE_PAY_FORMAT_CODE | VARCHAR2 | (30) | The Format attached to the Payment process profile for generating the Positive pay file. | |
| PAY_FILE_LETTER_FORMAT_CODE | VARCHAR2 | (30) | The Format attached to the Payment process profile for generating the Payment file accompanying letter. | |
| PRINT_INSTRUCTION_IMMED_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether a printed payment instruction should be printed immediately after the payment instruction is created. The value of this flag defaults to the Print Directly After Formatting parameter of the Create Payment Instruction Program. This is applicable only when the Payment process profiles processing type is 'Printed'. |
| DEFAULT_PRINTER | VARCHAR2 | (255) | Printer to be used by default for printing payments. This is applicable only when the Payment process profiles processing type is 'Printed' and when the option 'Automatically print after formatting' is selected. | |
| DEFAULT_PAYMENT_DOCUMENT_ID | NUMBER | (15) | Payment document to be used by default for printing payments. | |
| PERIODIC_SEQUENCE_NAME_1 | VARCHAR2 | (80) | Name of the sequence. The name is referenced in the payment format templates. | |
| PERIODIC_SEQUENCE_NAME_2 | VARCHAR2 | (80) | Name of the sequence. The name is referenced in the payment format templates. | |
| PERIODIC_SEQUENCE_NAME_3 | VARCHAR2 | (80) | Name of the sequence. The name is referenced in the payment format templates. | |
| PROCESSING_TYPE | VARCHAR2 | (30) | Y | Specifies the processing type of the payment process profile. Values from IBY_PROCESSING_TYPES lookup are displayed. The values are 'Electronic', 'Printed' and 'Payment Card'. |
| MARK_COMPLETE_EVENT | VARCHAR2 | (30) | Y | "Event at which payments in a payment instruction are automatically marked complete for processing type 'Electronic'. Values are from the lookup IBY_MARK_COMPLETE_EVENTS. If the processing type is 'Printed', the field 'Payment completion point' is hidden and it is always updated as PRINTED." |
| MANUAL_MARK_COMPLETE_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether the user should manually mark the payment as complete after the instruction is formatted. This is applicable only when the Payment process profiles processing type is 'Electronic'. |
| POSITIVE_PAY_DELIVERY_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether Positive Pay is automatically delivered using the same transmission configuration as the payment instruction. |
| TRANSMIT_INSTR_IMMED_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether an electronic payment instruction should be transmitted immediately after the payment instruction is created. The default value of this flag is N. The value of this flag defaults to the Print Directly After Formatting parameter of the Create Payment Instruction program. |
| SEEDED_FLAG | VARCHAR2 | (1) | Y or N flag controlling updatability of records. Y indicates record was seeded by Oracle and may have user updates limited. | |
| AUTOMATIC_PI_REG_SUBMIT | VARCHAR2 | (1) | Y | Y or N flag indicating whether the concurrent request for generating the payment instruction register is submitted automatically at the payment completion point |
| CREATED_BY | NUMBER | (15) | Y | Standard who column - unique internal identifier of user who created this row. Foreign key to the USER_ID column of the FND_USER table. |
| CREATION_DATE | DATE | Y | Standard who column - date when this row was created. | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard who column - unique internal identifier user who last updated this row. Foreign key to the USER_ID column of the FND_USER table. |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column - date when a user last updated this row | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard who column - operating system login of user who last updated this row. Foreign key to the LOGIN_ID column of the FND_LOGINS table. | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. This number is incremented for every update to the row through the application. |
| DECLARATION_OPTION | VARCHAR2 | (30) | Specifies the customer's option for the 'Regulatory reporting'. The declaration options are defined in IBY_CENTRAL_BANK_REPORT_OPTION lookup. They include 'No reporting', 'Report directly to Central bank' and Reporting made by bank' | |
| DCL_ONLY_FOREIGN_CURR_PMT_FLAG | VARCHAR2 | (1) | Y or N flag to specify whether only foreign currency payments or all payments are declared. Applicable only when Regulatory reporting (DECLARATION_OPTION) option is set to 'Report Directly to Central bank' or 'Reporting Made by Bank' | |
| DECLARATION_REPORT_FORMAT_CODE | VARCHAR2 | (30) | Format of the Regulatory Report. Only needed if the DECLARATION_OPTION is set to DECLARE_DIRECT_TO_CENTRAL_BANK | |
| DECLARATION_CURR_FX_RATE_TYPE | VARCHAR2 | (255) | Indicates the type of exchange rate to be used for converting the thresh hold amount to the payment amount currency. Types are defined in the General Ledger currency exchange rate type lookups table. These include SPOT, CORPORATE, and DAILY. | |
| DECLARATION_CURRENCY_CODE | VARCHAR2 | (10) | The currency of the threshold amount in the process of regulatory reporting. | |
| DECLARATION_THRESHOLD_AMOUNT | NUMBER | Threshold amount, above which the payment needs to be reported to the central bank | ||
| BANK_INSTRUCTION1_CODE | VARCHAR2 | (30) | The instructions to the bank can be selected here. There is a separate setup for defining the bank instruction code. | |
| BANK_INSTRUCTION2_CODE | VARCHAR2 | (30) | The instructions to the bank can be selected here. There is a separate setup for defining the bank instruction code. | |
| BANK_INSTRUCTION_DETAILS | VARCHAR2 | (255) | It is a free text field that can be included for additional bank instructions. | |
| PAYMENT_TEXT_MESSAGE1 | VARCHAR2 | (150) | It is a free text field that can be used payment processing. | |
| PAYMENT_TEXT_MESSAGE2 | VARCHAR2 | (150) | It is a free text field that can be used payment processing. | |
| INACTIVE_DATE | DATE | The date on which the PPP was made inactive. | ||
| ACK_TRANSMIT_PROTOCOL_CODE | VARCHAR2 | (100) | Transmission protocol Identifier for acknowledgement file | |
| ACK_SECURITY_PROTOCOL_CODE | VARCHAR2 | (100) | Security protocol Identifier for acknowledgement file | |
| SEND_TO_FILE_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether the payment format output should be 'Send to file' or 'Send to Printer'. Value 'Y' indicates that the formatted output is sent to a file and the payments may be printed outside of Oracle Payments. Value 'N' indicates that the printing of the formatted output is managed within Oracle Payments |
| PI_REGISTER_FORMAT | VARCHAR2 | (30) | The Format attached to the Payment process profile for generating the Payment Instruction Register. | |
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | Descriptive Flexfield structure defining column | |
| ATTRIBUTE1 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE2 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE3 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE4 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE5 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE6 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE7 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE8 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE9 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE10 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE11 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE12 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE13 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE14 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE15 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| OUTBOUND_PMT_FILE_DIRECTORY | VARCHAR2 | (255) | File directory where output of outbound payment file is stored | |
| OUTBOUND_PMT_FILE_EXTENSION | VARCHAR2 | (255) | File extension of outbound payment files | |
| OUTBOUND_PMT_FILE_PREFIX | VARCHAR2 | (255) | File name prefix of outbound payment files | |
| POSITIVE_PAY_FILE_DIRECTORY | VARCHAR2 | (255) | File directory where output of positive pay file is stored | |
| POSITIVE_PAY_FILE_EXTENSION | VARCHAR2 | (255) | File extension of positive pay files | |
| POSITIVE_PAY_FILE_PREFIX | VARCHAR2 | (255) | File name prefix of positive pay files | |
| ELECTRONIC_PROCESSING_CHANNEL | VARCHAR2 | (50) | Indicates whether payment instruction formatting needs to be from Payments or from e-Commerce Gateway. The values flow from lookup IBY_FD_PPP_PROCESS_CHANNEL. The possible values are 'Oracle payments' and 'Oracle e-Commerce Gateway' | |
| LOGICAL_GROUPING_MODE | VARCHAR2 | (50) | Indicates the grouping mode introduced for the SEPA payments. Values include - None, Single, Mixed or Grouped. | |
| BATCH_BOOKING_FLAG | VARCHAR2 | (1) | Indicates the batch booking option introduced for the SEPA payment. The option is Y or N. | |
| DISALLOW_SAVE_PRINT_FLAG | VARCHAR2 | (1) | Indicates whether to allow the payment instruction to be saved and reprinted. | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_SYS_PMT_PROFILES_B does not reference any database object
IBY.IBY_SYS_PMT_PROFILES_B is referenced by following:
| Description: | IBY_SYS_PMT_PROFILES stores seeded information that specifies the bulk of payment processing behavior. The rest of the behavior is specified in a user-defined account payment process profile stored in IBY_ACCT_PMT_PROFILES. A combination of |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_SYS_PMT_PROFILES_TL.SYSTEM_PROFILE_CODE | IBY_SYS_PMT_PROFILES_B |
IBY_SYS_PMT_PROFILES stores seeded information that specifies the bulk of payment processing behavior. The rest of the behavior is specified in a user-defined account payment process profile stored in IBY_ACCT_PMT_PROFILES. A combination of the two tables is defined in the view IBY_PAYMENT_PROFILES. The payment process profile as a whole controls the behavior of the payment process. To create a payment process profile, the user specifies how the payment instruction should be formatted, how it should be transmitted, how its acknowledgment and clearing files should be handled by the system, and other relevant information. This table corresponds to the Payment Process Profile pages.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_SYS_PMT_PROFILES_TL_U1 | UNIQUE | APPS_TS_TX_IDX |
SYSTEM_PROFILE_CODE
LANGUAGE ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| SYSTEM_PROFILE_CODE | VARCHAR2 | (100) | Y | User entered primary key |
| SYSTEM_PROFILE_NAME | VARCHAR2 | (100) | Y | System payment process profile name |
| LANGUAGE | VARCHAR2 | (4) | Y | Language code |
| SOURCE_LANG | VARCHAR2 | (4) | Y | Language code of the record's current language |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Object version number |
| SYSTEM_PROFILE_DESCRIPTION | VARCHAR2 | (255) | Description of system payment process profile | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_SYS_PMT_PROFILES_TL does not reference any database object
IBY.IBY_SYS_PMT_PROFILES_TL is referenced by following:
| Description: |
|---|
IBY_SYS_SECURITY_OPTIONS stores the system security options that are used for funds capture processing and funds disbursement processing.
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| SYS_KEY_FILE_LOCATION | VARCHAR2 | (500) | Location of the system password file | |
| SYS_KEY_HASH | RAW | (100) | Hash of the system key; used for verification purposes | |
| CC_ENCRYPTION_MODE | VARCHAR2 | (30) | Y | Encryption mode for credit card instruments; values taken from the lookup IBY_ENCRYPTION_MODE. Possible values can be NULL, Scheduled and Immediate. |
| EXT_BA_ENCRYPTION_MODE | VARCHAR2 | (30) | Y | External bank account encryption mode; values taken from the lookup IBY_ENCRYPTION_MODE. Possible values can be Scheduled or NULL. |
| INSTR_SEC_CODE_ENCRYPTION_MODE | VARCHAR2 | (30) | Y | Instrument security code encryption mode. Value used is same as CC_ENCRYPTION_MODE. |
| CREDIT_CARD_MASK_SETTING | VARCHAR2 | (30) | Y | Setup value for the masking of the credit card number. The possible values are - Display Last Digits, Display First Digits and Display None. Value are taken from lookup IBY_PMT_INSTR_MASKING |
| CREDIT_CARD_UNMASK_LEN | NUMBER | (2) | The number of digits that can be exposed while displaying the credit card number on the UI or reports | |
| EXT_BA_MASK_SETTING | VARCHAR2 | (30) | Y | Setup value for the masking of the bank account number. The possible values are - Display Last Digits, Display First Digits and Display None. Value are taken from lookup IBY_PMT_INSTR_MASKING |
| EXT_BA_UNMASK_LEN | NUMBER | (2) | The number of digits that can be exposed while displaying the bank account number on the UI or reports | |
| SUBKEY_USE_MAXIMUM | NUMBER | (10) | Y | Maximum use count for security sub-keys |
| CREATED_BY | NUMBER | (15) | Y | Standard who column - unique internal identifier of user who created this row. Foreign key to the USER_ID column of the FND_USER table. |
| CREATION_DATE | DATE | Y | Standard who column - date when this row was created | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard who column - unique internal identifier user who last updated this row. Foreign key to the USER_ID column of the FND_USER table. |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column - date when a user last updated this row. | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard who column - operating system login of user who last updated this row. Foreign key to the LOGIN_ID column of the FND_LOGINS table. | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. This number is incremented for every update to the row through the application. |
| SALT_VERSION | NUMBER | (2) | Denotes the versions of the encryption algorithm used for the Bank account or Credit card number encryption | |
| SUBKEY_AGE_MAXIMUM | NUMBER | (3) | Maximum subkey age | |
| ENCRYPT_SUPPLEMENTAL_CARD_DATA | VARCHAR2 | (1) | Y or N flag to denote if the supplemental cardholder data needs to be encrypted. | |
| ENCRYPTION_PATCH_LEVEL | VARCHAR2 | (30) | Stores the current encryption patch level i.e., NORMAL, PADSS etc | |
| SYSTEM_SALT_VERSION | NUMBER | (2) | Security Column |
IBY.IBY_SYS_SECURITY_OPTIONS does not reference any database object
IBY.IBY_SYS_SECURITY_OPTIONS is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_SECURITY_SEGMENTS.SEC_SUBKEY_ID | IBY_SYS_SECURITY_SUBKEYS |
IBY_SYS_SECURITY_SUBKEYS stores the security sub-keys used for data encryption. A sub-key is a randomly generated number used to encrypt only a fixed number of data rows, after which a new sub-key is randomly generated. The sub-key is stored as cipher-text in this table.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_SECURITY_SUBKEYS_U1 | UNIQUE | APPS_TS_TX_IDX | SEC_SUBKEY_ID |
| IBY_SECURITY_SUBKEYS_N1 | NONUNIQUE | APPS_TS_TX_IDX | USE_COUNT |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| SEC_SUBKEY_ID | NUMBER | (15) | Y | Sequence-generated primary key |
| SUBKEY_CIPHER_TEXT | RAW | (50) | Y | Cipher-text of the subkey |
| USE_COUNT | NUMBER | (15) | Y | Number of times the sub-key was used to encrypt data |
| CREATED_BY | NUMBER | (15) | Y | Standard Who Column |
| CREATION_DATE | DATE | Y | Standard Who Column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who Column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who Column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who Column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Object Version Number |
IBY.IBY_SYS_SECURITY_SUBKEYS does not reference any database object
IBY.IBY_SYS_SECURITY_SUBKEYS is referenced by following:
| Description: | IBY_TANGIBLE stores information about the bills or orders. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_TANGIBLE.SOURCE_OBJECT_TYPE_CODE | JTF_OBJECTS_B |
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_TRXN_SUMMARIES_ALL.MTANGIBLEID | IBY_TANGIBLE |
| IBY_TRXN_SUMMARIES_ALL.MTANGIBLEID | IBY_TANGIBLE |
IBY_TANGIBLE stores information about the bills or orders.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_TANGIBLE_MTANGIBLEID_U1 | UNIQUE | APPS_TS_TX_IDX | MTANGIBLEID |
| IBY_TANGIBLE_N3 | NONUNIQUE | APPS_TS_TX_IDX | SOURCE_OBJECT_TYPE_CODE |
| IBY_TANGIBLE_N4 | NONUNIQUE | APPS_TS_TX_IDX | SOURCE_OBJECT_ID |
| IBY_TANGIBLE_REFINFO_N2 | NONUNIQUE | APPS_TS_TX_IDX | REFINFO |
| IBY_TANGIBLE_TANGIBLEID_N1 | NONUNIQUE | APPS_TS_TX_IDX | TANGIBLEID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| MTANGIBLEID | NUMBER | (15) | Y | system generated ID, this id is exposed to Electronic application unlike others |
| TANGIBLEID | VARCHAR2 | (80) | Y | bill or orderid |
| AMOUNT | NUMBER | Y | Amount | |
| CURRENCYNAMECODE | VARCHAR2 | (15) | Y | code for currency name such USD |
| ACCTNO | VARCHAR2 | (80) | customer account number with the biller or merchant | |
| REFINFO | VARCHAR2 | (80) | any reference information passed by the Electronic Commerce Application | |
| MEMO | VARCHAR2 | (80) | memo for the payment | |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column - date when a user last updated this row. | |
| OBJECT_VERSION_NUMBER | NUMBER | (5) | Y | This column is used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard who column - user who last updated this row (foreign key to FND_USER.USER_ID). |
| CREATED_BY | NUMBER | (15) | Y | Standard who column - user who created this row (foreign key to FND_USER.USER_ID). |
| CREATION_DATE | DATE | Y | Standard who column - date when this row was created. | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard who column - operating system login of user who last updated this row (foreign key to FND_LOGINS.LOGIN_ID). | |
| SECURITY_GROUP_ID | NUMBER | Used in hosted environments | ||
| SOURCE_OBJECT_TYPE_CODE | VARCHAR2 | (30) | Type of the originating EC App quote or order. Foreign Key to JTF_OBJECTS_B | |
| SOURCE_OBJECT_ID | NUMBER | (15) | Primary Key of the source object | |
| ISSUEDATE | DATE | Date the Bills Receivable or Receipt was issued. Added for AR-BR integration | ||
| ORDER_MEDIUM | VARCHAR2 | (30) | Order medium/channel from lookup type IBY_ORDER_MEDIUM_TYPE | |
| EFT_AUTH_METHOD | VARCHAR2 | (30) | Method used in obtaining authorization for performing EFT debits against the payer's bank account |
IBY.IBY_TANGIBLE does not reference any database object
IBY.IBY_TANGIBLE is referenced by following:
| Description: |
|---|
IBY_TEMP_EXT_BANK_ACCTS defines the temporary records for external bank accounts.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_TEMP_EXT_BANK_ACCTS_U1 | UNIQUE | APPS_TS_TX_IDX | TEMP_EXT_BANK_ACCT_ID |
| IBY_TEMP_EXT_BANK_ACCTS_N1 | NONUNIQUE | APPS_TS_TX_IDX | EXT_BANK_ACCOUNT_ID |
| IBY_TEMP_EXT_BANK_ACCTS_N2 | NONUNIQUE | APPS_TS_TX_IDX | ACCOUNT_OWNER_PARTY_ID |
| IBY_TEMP_EXT_BANK_ACCTS_N3 | NONUNIQUE | APPS_TS_TX_IDX |
BANK_ID
BRANCH_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| TEMP_EXT_BANK_ACCT_ID | NUMBER | (15) | Y | Primary key of this table |
| EXT_BANK_ACCOUNT_ID | NUMBER | (15) | Bank account Identifier of the table IBY_EXT_BANK_ACCOUNTS_B | |
| COUNTRY_CODE | VARCHAR2 | (2) | Y | Country code of the bank account |
| BRANCH_ID | NUMBER | (15) | Identifier of the bank branch to which this bank account belongs. This column is used if the bank has been created in the system already. | |
| BANK_ID | NUMBER | (15) | Identifier of the bank to which this bank branch belongs. This column is used if the branch has been created in the system already. | |
| BANK_NAME | VARCHAR2 | (80) | Bank name | |
| BANK_NUMBER | VARCHAR2 | (30) | Bank number | |
| BANK_NAME_ALT | VARCHAR2 | (80) | Alternative bank name | |
| BANK_INSTITUTION_TYPE | VARCHAR2 | (80) | Bank institution type | |
| BANK_ADDRESS_ID | NUMBER | (15) | Bank location | |
| BRANCH_NUMBER | VARCHAR2 | (30) | Branch number | |
| BRANCH_TYPE | VARCHAR2 | (30) | Branch type | |
| BRANCH_NAME | VARCHAR2 | (80) | Branch name | |
| BRANCH_NAME_ALT | VARCHAR2 | (80) | Alternative branch name | |
| BIC | VARCHAR2 | (30) | BIC | |
| RFC_IDENTIFIER | VARCHAR2 | (30) | Branch RFC Identifier | |
| BANK_CODE | VARCHAR2 | (100) | Bank code | |
| BRANCH_ADDRESS_ID | NUMBER | (15) | Branch location | |
| ACCOUNT_OWNER_PARTY_ID | NUMBER | (15) | Owner party Identifier | |
| OWNER_PRIMARY_FLAG | VARCHAR2 | (1) | Primary flag for the owner | |
| BANK_ACCOUNT_NAME | VARCHAR2 | (80) | Bank account name | |
| BANK_ACCOUNT_NUM | VARCHAR2 | (100) | Account number | |
| CURRENCY_CODE | VARCHAR2 | (15) | Currency code | |
| IBAN | VARCHAR2 | (50) | IBAN | |
| CHECK_DIGITS | VARCHAR2 | (30) | Check digits | |
| BANK_ACCOUNT_NAME_ALT | VARCHAR2 | (320) | Alternate account name | |
| BANK_ACCOUNT_TYPE | VARCHAR2 | (25) | Bank account type, that is, SAVINGS, or CHECKING | |
| ACCOUNT_SUFFIX | VARCHAR2 | (30) | Account suffix | |
| DESCRIPTION | VARCHAR2 | (240) | Description | |
| AGENCY_LOCATION_CODE | VARCHAR2 | (30) | Agency location code | |
| PAYMENT_FACTOR_FLAG | VARCHAR2 | (1) | Indicates whether this is a payment factor bank account | |
| FOREIGN_PAYMENT_USE_FLAG | VARCHAR2 | (1) | Flag that indicates whether to use this bank account for foreign payment | |
| EXCHANGE_RATE_AGREEMENT_NUM | VARCHAR2 | (80) | Exchange rate agreement number | |
| EXCHANGE_RATE_AGREEMENT_TYPE | VARCHAR2 | (80) | Exchange rate agreement type | |
| EXCHANGE_RATE | NUMBER | Exchange rate | ||
| START_DATE | DATE | Start date | ||
| END_DATE | DATE | End date | ||
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | Descriptive Flexfield structure defining column | |
| NOTE | VARCHAR2 | (240) | Note | |
| NOTE_ALT | VARCHAR2 | (240) | Alternative note | |
| ATTRIBUTE1 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE2 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE3 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE4 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE5 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE6 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE7 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE8 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE9 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE10 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE11 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE12 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE13 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE14 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| ATTRIBUTE15 | VARCHAR2 | (150) | Descriptive Flexfield segment | |
| STATUS | VARCHAR2 | (30) | Status of the bank account approval process | |
| LAST_UPDATE_DATE | DATE | Y | Standard Who Column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who Column |
| CREATION_DATE | DATE | Y | Standard Who Column | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who Column |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who Column | |
| REQUEST_ID | NUMBER | (15) | Current Who column | |
| PROGRAM_APPLICATION_ID | NUMBER | (15) | Current Who column | |
| PROGRAM_ID | NUMBER | (15) | Current Who column | |
| PROGRAM_UPDATE_DATE | DATE | Current Who column | ||
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Object version number |
| CALLING_APP_UNIQUE_REF1 | VARCHAR2 | (100) | First unique identifier of the owner in the source product | |
| CALLING_APP_UNIQUE_REF2 | VARCHAR2 | (100) | Second unique identifier of the owner in the source product | |
| EXT_PAYEE_ID | NUMBER | (15) | Payee to whom the bank account should be assigned | |
| CONTACT_NAME | VARCHAR2 | (60) | Contact name | |
| CONTACT_PHONE | VARCHAR2 | (30) | Contact phone number | |
| CONTACT_FAX | VARCHAR2 | (30) | Contact fax number | |
| CONTACT_EMAIL | VARCHAR2 | (80) | Contact Email address |
IBY.IBY_TEMP_EXT_BANK_ACCTS does not reference any database object
IBY.IBY_TEMP_EXT_BANK_ACCTS is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_TEMP_EXT_PAYEES.BANK_INSTRUCTION1_CODE | IBY_BANK_INSTRUCTIONS_B |
| IBY_TEMP_EXT_PAYEES.DEFAULT_PAYMENT_METHOD_CODE | IBY_PAYMENT_METHODS_B |
| IBY_TEMP_EXT_PAYEES.BANK_INSTRUCTION2_CODE | IBY_BANK_INSTRUCTIONS_B |
| IBY_TEMP_EXT_PAYEES.DELIVERY_CHANNEL_CODE | IBY_DELIVERY_CHANNELS_B |
| IBY_TEMP_EXT_PAYEES.PAYMENT_FORMAT_CODE | IBY_FORMATS_B |
| IBY_TEMP_EXT_PAYEES.PAYMENT_REASON_CODE | IBY_PAYMENT_REASONS_B |
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_TEMP_PMT_INSTR_USES.TEMP_EXT_PARTY_ID | IBY_TEMP_EXT_PAYEES |
IBY_TEMP_EXT_PAYEES stores payment processing attributes for external payees.
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| TEMP_EXT_PAYEE_ID | NUMBER | (15) | Y | Primary Identifier. The value comes from sequence IBY_TEMP_EXT_PAYEE_S. |
| PAYMENT_FUNCTION | VARCHAR2 | (30) | Y | Payment function |
| PARTY_ID | NUMBER | (15) | Y | Identifier of the party |
| ORG_TYPE | VARCHAR2 | (30) | Organization type | |
| ORG_ID | NUMBER | (15) | Organization Identifier | |
| BANK_CHARGE_BEARER | VARCHAR2 | (30) | Bank charge bearer | |
| PARTY_SITE_ID | NUMBER | (15) | Party site use Identifier | |
| SUPPLIER_SITE_ID | NUMBER | (15) | Supplier site Identifier | |
| DEFAULT_PAYMENT_METHOD_CODE | VARCHAR2 | (30) | Y | Default payment method Identifier |
| ECE_TP_LOCATION_CODE | VARCHAR2 | (60) | Trading partner location code for e-Commerce Gateway | |
| BANK_INSTRUCTION1_CODE | VARCHAR2 | (30) | Y | Code of first bank instruction |
| BANK_INSTRUCTION2_CODE | VARCHAR2 | (30) | Y | Code of second bank instruction |
| BANK_INSTRUCTION_DETAILS | VARCHAR2 | (255) | Additional bank instruction details | |
| PAYMENT_REASON_CODE | VARCHAR2 | (30) | Y | Payment reason code |
| PAYMENT_REASON_COMMENTS | VARCHAR2 | (240) | Free text field available for entering a reason for the payment | |
| PAYMENT_TEXT_MESSAGE1 | VARCHAR2 | (150) | Text message for use in payment processing | |
| PAYMENT_TEXT_MESSAGE2 | VARCHAR2 | (150) | Payment text message | |
| PAYMENT_TEXT_MESSAGE3 | VARCHAR2 | (150) | Payment text message | |
| DELIVERY_CHANNEL_CODE | VARCHAR2 | (30) | Y | Delivery method |
| PAYMENT_FORMAT_CODE | VARCHAR2 | (30) | Y | Payment format code |
| EXCLUSIVE_PAYMENT_FLAG | VARCHAR2 | (1) | Y | Y or N flag that indicates if a document payable should be prevented from grouping with others into a payment |
| INACTIVE_DATE | DATE | Inactive date | ||
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Object version number |
IBY.IBY_TEMP_EXT_PAYEES does not reference any database object
IBY.IBY_TEMP_EXT_PAYEES is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_TEMP_PMT_INSTR_USES.TEMP_EXT_PARTY_ID | IBY_TEMP_EXT_PAYEES |
IBY_TEMP_PMT_INSTR_USES links external payees and payers to their external payment instruments.
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| TEMP_EXT_PARTY_ID | NUMBER | (15) | Y | External party Identifier in the table IBY_TEMP_EXT_PAYEES |
| EXT_PARTY_ID | NUMBER | (15) | External party Identifier if it is already defined in the system, that is, IBY_EXTERNAL_PAYEES_ALL or IBY_EXTERNAL_PAYERS_ALL | |
| INSTRUMENT_TYPE | VARCHAR2 | (30) | Y | Instrument type. Values from the IBY_INSTRUMENT_TYPES lookup include BANKACCOUNT, CREDITCARD, and DEBITCARD. |
| TEMP_INSTRUMENT_ID | NUMBER | (15) | Y | Instrument Identifier in the temporary instrument table. For example, IBY_TEMP_EXT_BANK_ACCTS |
| PAYMENT_FUNCTION | VARCHAR2 | (30) | Y | Function or purpose of the payment. Values from the lookup IBY_PAYMENT_FUNCTIONS include SUPPLIER_PAYMENT, CUSTOMER_REFUNDS, and others. |
| ORDER_OF_PREFERENCE | NUMBER | (15) | Y | Order of preference assigned by the external party to the account use |
| STATUS | VARCHAR2 | (1) | Status of the instrument use | |
| START_DATE | DATE | Y | Start date | |
| END_DATE | DATE | End date | ||
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Object version number |
IBY.IBY_TEMP_PMT_INSTR_USES does not reference any database object
IBY.IBY_TEMP_PMT_INSTR_USES is referenced by following:
| Description: | IBY_TRANSACTION_ERRORS stores any errors encountered during payment processing validations. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
|
IBY_TRANSACTION_ERRORS.CALLING_APP_ID
IBY_TRANSACTION_ERRORS.PAY_PROC_TRXN_TYPE_CODE |
IBY_TRXN_TYPES_B |
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_TRXN_ERROR_TOKENS.TRANSACTION_ERROR_ID | IBY_TRANSACTION_ERRORS |
IBY_TRANSACTION_ERRORS stores any errors encountered during payment processing validations.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_TRANSACTION_ERRORS_U1 | UNIQUE | APPS_TS_TX_IDX | TRANSACTION_ERROR_ID |
| IBY_TRANSACTION_ERRORS_N1 | NONUNIQUE | APPS_TS_TX_IDX |
CALLING_APP_ID
PAY_PROC_TRXN_TYPE_CODE |
| IBY_TRANSACTION_ERRORS_N2 | NONUNIQUE | APPS_TS_TX_IDX |
TRANSACTION_ID
TRANSACTION_TYPE |
| IBY_TRANSACTION_ERRORS_N3 | NONUNIQUE | APPS_TS_TX_IDX | ERROR_DATE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| TRANSACTION_ERROR_ID | NUMBER | (15) | Y | System generated primary key |
| TRANSACTION_TYPE | VARCHAR2 | (30) | Y | Transaction type. Values from the lookup IBY_TRANSACTION_TYPES include DOCUMENT_PAYABLE, PAYMENT, and PAYMENT_INSTRUCTION. |
| TRANSACTION_ID | NUMBER | (15) | Y | Transaction Identifier |
| ERROR_CODE | VARCHAR2 | (30) | Y | Error code for failed transaction. If ERROR_TYPE is BANK, this is a bank-specific error code. |
| ERROR_DATE | DATE | Y | Date on which the error occurred | |
| ERROR_STATUS | VARCHAR2 | (30) | Y | Whether the error is still active, that is, the error still applies, passed, or overridden. Values from the lookup IBY_TRANSACTION_ERROR_STATUSES include ACTIVE, PASSED, and OVERRIDDEN. The last two values only apply to validation errors. |
| CALLING_APP_DOC_UNIQUE_REF1 | VARCHAR2 | (100) | Source product''s first unique document payable Identifier | |
| OVERRIDE_ALLOWED_ON_ERROR_FLAG | VARCHAR2 | (1) | Y | Y or N flag specifying whether this validation error can be overridden by the payment administrator. Some validation errors are fatal and the condition causing the error must be corrected so the payment instruction can be validated successfully. By default, this flag is Y. For fatal errors, the Create Payment Instructions program sets this flag to N. |
| DO_NOT_APPLY_ERROR_FLAG | VARCHAR2 | (1) | Y | Y or N flag which only applies to errors on payment instructions. The value is N by default and only changes to Y if an administrator overrides the error. When a payment instruction is resubmitted to the Create Payment Instructions program and validations are applied, this error is not applied when the value is Y. |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| CALLING_APP_ID | NUMBER | (15) | Source product Identifier | |
| PAY_PROC_TRXN_TYPE_CODE | VARCHAR2 | (100) | Payment processing transaction type striped by application | |
| CALLING_APP_DOC_UNIQUE_REF2 | VARCHAR2 | (100) | Source product''s second unique document payable Identifier | |
| CALLING_APP_DOC_UNIQUE_REF3 | VARCHAR2 | (100) | Source product''s third unique document payable Identifier | |
| CALLING_APP_DOC_UNIQUE_REF4 | VARCHAR2 | (100) | Source product''s fourth unique document payable Identifier | |
| CALLING_APP_DOC_UNIQUE_REF5 | VARCHAR2 | (100) | Source product''s fifth unique document payable Identifier | |
| ERROR_TYPE | VARCHAR2 | (30) | Type of error. Values from the lookup IBY_TRANSACTION_ERROR_TYPES include VALIDATION and BANK. | |
| ERROR_MESSAGE | VARCHAR2 | (255) | Error message for failed transaction. If ERROR_TYPE is BANK, this is a bank-specific error code. | |
| VALIDATION_SET_CODE | VARCHAR2 | (30) | Identifier of the validation set that was violated if ERROR_TYPE is VALIDATION. | |
| PASS_DATE | DATE | Date on which the validation set that gave rise to this error was passed. This column is not be populated if the DO_NOT_APPLY_ERROR_FLAG is Y. | ||
| OVERRIDE_JUSTIFICATION | VARCHAR2 | (255) | Justification for overriding validation error. This column is only populated if the DO_NOT_APPLY_ERROR_FLAG is Y. | |
| OVERRIDE_DATE | DATE | Date on which the error was overridden. This column is only populated if the DO_NOT_APPLY_ERROR_FLAG is Y. |
IBY.IBY_TRANSACTION_ERRORS does not reference any database object
IBY.IBY_TRANSACTION_ERRORS is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_TRANSMIT_CONFIGS_B.TRANSMIT_PROTOCOL_CODE | IBY_TRANSMIT_PROTOCOLS_B |
| IBY_TRANSMIT_CONFIGS_B.TUNNELING_TRANS_CONFIG_ID | IBY_TRANSMIT_CONFIGS_B |
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_ACCT_PMT_PROFILES_B.TRANSMIT_CONFIGURATION_ID | IBY_TRANSMIT_CONFIGS_B |
| IBY_PAY_INSTRUCTIONS_H.TRANSMIT_CONFIGURATION_ID | IBY_TRANSMIT_CONFIGS_B |
| IBY_TRANSMIT_CONFIGS_B.TUNNELING_TRANS_CONFIG_ID | IBY_TRANSMIT_CONFIGS_B |
IBY_TRANSMIT_CONFIGS defines a transmission channel with all parameters for the communication scheme, such as network addresses, defined. A transmission configuration is associated with one of the funds capture profiles.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_TRANSMIT_CONFIGS_B_CID_U1 | UNIQUE | APPS_TS_TX_IDX | TRANSMIT_CONFIGURATION_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| TRANSMIT_CONFIGURATION_ID | NUMBER | (15) | Y | System generated primary key |
| TRANSMIT_PROTOCOL_CODE | VARCHAR2 | (30) | Y | Transmission protocol identifier |
| TUNNELING_TRANS_CONFIG_ID | NUMBER | (15) | Transmission configuration for the tunneling protocol used to encapsulate this one- for example, a web service request to perform FTP transmission | |
| INACTIVE_DATE | DATE | Inactive date | ||
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Y | Standard Who column |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. |
IBY.IBY_TRANSMIT_CONFIGS_B does not reference any database object
IBY.IBY_TRANSMIT_CONFIGS_B is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_TRANSMIT_CONFIGS_TL.TRANSMIT_CONFIGURATION_ID | % |
IBY_TRANSMIT_CONFIGS defines a transmission channel with all parameters for the communication scheme, such as network addresses, defined. A transmission configuration is associated with one of the funds capture profiles.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_TRANSMIT_CONFIGS_TL_CID_N1 | NONUNIQUE | APPS_TS_TX_IDX | TRANSMIT_CONFIGURATION_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| TRANSMIT_CONFIGURATION_ID | NUMBER | (15) | Y | System generated primary key |
| LANGUAGE | VARCHAR2 | (4) | Y | Language code |
| SOURCE_LANG | VARCHAR2 | (4) | Y | Language code of the record's current language |
| TRANSMIT_CONFIGURATION_NAME | VARCHAR2 | (100) | Y | Transmission configuration name |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. |
IBY.IBY_TRANSMIT_CONFIGS_TL does not reference any database object
IBY.IBY_TRANSMIT_CONFIGS_TL is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_TRANSMIT_PARAMETERS_B.TRANSMIT_PROTOCOL_CODE | IBY_TRANSMIT_PROTOCOLS_B |
IBY_TRANSMIT_PARAMETERS stores a transmission protocol's input parameters. For example, this table is used to indicate that the FTP protocol requires a destination IP address and a destination directory, among other parameters. It is referred to by the transmission configuration table.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_TRANSMIT_PARAMETERS_B_U1 | UNIQUE | APPS_TS_TX_IDX |
TRANSMIT_PROTOCOL_CODE
TRANSMIT_PARAMETER_CODE ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| TRANSMIT_PARAMETER_CODE | VARCHAR2 | (30) | Y | User entered primary key |
| TRANSMIT_PARAMETER_TYPE | VARCHAR2 | (30) | Y | Data type of the parameter. Values, from the lookup IBY_PARAMETER_TYPES, include VARCHAR2, NUMBER, and DATE. |
| TRANSMIT_PROTOCOL_CODE | VARCHAR2 | (30) | Y | Identifier of the transmission protocol for which this parameter is needed |
| MANDATORY_FLAG | VARCHAR2 | (1) | Y | Y or N flag indicating whether this parameter is mandatory. |
| DYNAMIC_FLAG | VARCHAR2 | (1) | Y or N flag indicating whether this parameter is dynamically generated using transactional data | |
| DYN_CODE_LANGUAGE | VARCHAR2 | (30) | Language of the code that is used for dynamic parameter value generation. Possible values would be 'PL/SQL' and 'Java'. | |
| DYN_CODE_PACKAGE | VARCHAR2 | (255) | Package used for dynamic parameter value generation; in PL/SQL this corresponds to a package name, in Java a class name | |
| DYN_CODE_ENTRY_POINT | VARCHAR2 | (255) | Code entry point used for dynamic parameter value generation. For example, this could be in the form of a PL/SQL package and procedure, or a Java class and method. | |
| SECURED_FLAG | VARCHAR2 | (1) | Y or N flag that indicates whether the transmission parameter is security-sensitive | |
| DISPLAY_ORDER | NUMBER | (15) | Y | Display order within the set of all options for protocol |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_TRANSMIT_PARAMETERS_B does not reference any database object
IBY.IBY_TRANSMIT_PARAMETERS_B is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
|
IBY_TRANSMIT_PARAMETERS_TL.TRANSMIT_PROTOCOL_CODE
IBY_TRANSMIT_PARAMETERS_TL.TRANSMIT_PARAMETER_CODE |
% |
IBY_TRANSMIT_PARAMETERS stores a transmission protocol's input parameters. For example, this table is used to indicate that the FTP protocol requires a destination IP address and a destination directory, among other parameters. It is referred to by the transmission configuration table.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_TRANSMIT_PARAMETERS_TL_U1 | UNIQUE | APPS_TS_TX_IDX |
LANGUAGE
TRANSMIT_PROTOCOL_CODE TRANSMIT_PARAMETER_CODE ZD_EDITION_NAME |
| IBY_TRANSMIT_PARAMETERS_TL_N1 | NONUNIQUE | APPS_TS_TX_IDX |
TRANSMIT_PROTOCOL_CODE
TRANSMIT_PARAMETER_CODE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| TRANSMIT_PARAMETER_CODE | VARCHAR2 | (30) | Y | User entered primary key |
| TRANSMIT_PROTOCOL_CODE | VARCHAR2 | (30) | Y | Identifier of the transmission protocol for which this parameter is needed |
| LANGUAGE | VARCHAR2 | (4) | Y | Language code |
| SOURCE_LANG | VARCHAR2 | (4) | Y | Language code of the record's current language |
| TRANSMIT_PARAMETER_NAME | VARCHAR2 | (100) | Y | Transmission parameter name |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_TRANSMIT_PARAMETERS_TL does not reference any database object
IBY.IBY_TRANSMIT_PARAMETERS_TL is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_FNDCPT_SYS_CC_PF_B.SETTLEMENT_TRANS_PRTCL_CODE | IBY_TRANSMIT_PROTOCOLS_B |
| IBY_FNDCPT_SYS_CC_PF_B.QUERY_TRANS_PRTCL_CODE | IBY_TRANSMIT_PROTOCOLS_B |
| IBY_FNDCPT_SYS_DC_PF_B.ONLINE_DEB_TRANS_PRTCL_CODE | IBY_TRANSMIT_PROTOCOLS_B |
| IBY_FNDCPT_SYS_DC_PF_B.SETTLEMENT_TRANS_PRTCL_CODE | IBY_TRANSMIT_PROTOCOLS_B |
| IBY_FNDCPT_SYS_DC_PF_B.QUERY_TRANS_PRTCL_CODE | IBY_TRANSMIT_PROTOCOLS_B |
| IBY_FNDCPT_SYS_EFT_PF_B.VERIFY_TRANS_PRTCL_CODE | IBY_TRANSMIT_PROTOCOLS_B |
| IBY_FNDCPT_SYS_EFT_PF_B.FUNDS_XFER_TRANS_PRTCL_CODE | IBY_TRANSMIT_PROTOCOLS_B |
| IBY_FNDCPT_SYS_EFT_PF_B.QUERY_TRANS_PRTCL_CODE | IBY_TRANSMIT_PROTOCOLS_B |
| IBY_PMT_SYS_TRANSMISSIONS.TRANSMIT_PROTOCOL_CODE | IBY_TRANSMIT_PROTOCOLS_B |
| IBY_SYS_PMT_PROFILES_B.TRANSMIT_PROTOCOL_CODE | IBY_TRANSMIT_PROTOCOLS_B |
| IBY_TRANSMIT_CONFIGS_B.TRANSMIT_PROTOCOL_CODE | IBY_TRANSMIT_PROTOCOLS_B |
| IBY_TRANSMIT_PARAMETERS_B.TRANSMIT_PROTOCOL_CODE | IBY_TRANSMIT_PROTOCOLS_B |
| IBY_TRANSMIT_PROTOCOLS_TL.TRANSMIT_PROTOCOL_CODE | IBY_TRANSMIT_PROTOCOLS_B |
IBY_TRANSMIT_PROTOCOLS specifies the transmission protocols used by various process profiles. This table is seeded with the most common protocols, such as FTP. It can be expanded with new or customized protocols by providing a link to the code entry point. A transmission protocol is further defined by specifying the protocol's input parameters. This is done in the IBY_TRANSMIT_PARAMETERS table.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_TRANSMIT_PROTOCOLS_B_PC_U1 | UNIQUE | APPS_TS_TX_IDX |
TRANSMIT_PROTOCOL_CODE
ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| TRANSMIT_PROTOCOL_CODE | VARCHAR2 | (30) | Y | User entered primary key |
| TRANSMIT_CODE_LANGUAGE | VARCHAR2 | (30) | Language of the code that implements the transmission protocol. Possible values would be 'PL/SQL' and 'Java'. | |
| TRANSMIT_CODE_PACKAGE | VARCHAR2 | (255) | Package where the reader is defined; in PL/SQL this corresponds to a package name, in Java a class name | |
| TRANSMIT_CODE_ENTRY_POINT | VARCHAR2 | (255) | Entry point of the code that implements the transmission protocol. For example, this could be in the form of a PL/SQL package and procedure, or a Java class and method. | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_TRANSMIT_PROTOCOLS_B does not reference any database object
IBY.IBY_TRANSMIT_PROTOCOLS_B is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_TRANSMIT_PROTOCOLS_TL.TRANSMIT_PROTOCOL_CODE | IBY_TRANSMIT_PROTOCOLS_B |
IBY_TRANSMIT_PROTOCOLS specifies the transmission protocols used by various process profiles. This table is seeded with the most common protocols, such as FTP. It can be expanded with new or customized protocols by providing a link to the code entry point. A transmission protocol is further defined by specifying the protocol's input parameters. This is done in the IBY_TRANSMIT_PARAMETERS table.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_TRANSMIT_PROTOCOLS_TL_U1 | UNIQUE | APPS_TS_TX_IDX |
LANGUAGE
TRANSMIT_PROTOCOL_CODE ZD_EDITION_NAME |
| IBY_TRANSMIT_PROTOCOLS_TL_N1 | NONUNIQUE | APPS_TS_TX_IDX | TRANSMIT_PROTOCOL_CODE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| TRANSMIT_PROTOCOL_CODE | VARCHAR2 | (30) | Y | User entered primary key |
| LANGUAGE | VARCHAR2 | (4) | Y | Language code |
| SOURCE_LANG | VARCHAR2 | (4) | Y | Language code of the record's current language |
| TRANSMIT_PROTOCOL_NAME | VARCHAR2 | (100) | Y | Transmission protocol name |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_TRANSMIT_PROTOCOLS_TL does not reference any database object
IBY.IBY_TRANSMIT_PROTOCOLS_TL is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_TRANSMIT_VALUES.TRANSMIT_CONFIGURATION_ID | % |
| IBY_TRANSMIT_VALUES.VAL_SEC_SEGMENT_ID | IBY_SECURITY_SEGMENTS |
IBY_TRANSMIT_VALUES stores the values for the parameters defined in IBY_TRANSMIT_PARAMETERS for a given transmission protocol. Each value is associated with a single transmission configuration in table IBY_TRANSMIT_VALUES.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_TRANSMIT_VALUES_CID_N1 | NONUNIQUE | APPS_TS_TX_IDX | TRANSMIT_CONFIGURATION_ID |
| IBY_TRANSMIT_VALUES_PCODE_N1 | NONUNIQUE | APPS_TS_TX_IDX | TRANSMIT_PARAMETER_CODE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| TRANSMIT_VALUE_ID | NUMBER | (15) | Y | Unique internal Identifier for this record. Generated using a database sequence. |
| TRANSMIT_CONFIGURATION_ID | NUMBER | (15) | Y | Transmission configuration identifier |
| TRANSMIT_PARAMETER_CODE | VARCHAR2 | (30) | Y | Identifier of the transmission parameter for which this entry provides a value |
| TRANSMIT_VARCHAR2_VALUE | VARCHAR2 | (255) | Value of the transmission parameter for this transmission configuration, if it is of type VARCHAR2 | |
| TRANSMIT_NUMBER_VALUE | NUMBER | Value of the transmission parameter for this transmission configuration, if it is of type NUMBER | ||
| TRANSMIT_DATE_VALUE | DATE | Value of the transmission parameter for this transmission configuration, if it is of type DATE | ||
| CREATED_BY | NUMBER | (15) | Y | Standard who column - unique internal identifier of user who created this row. Foreign key to the USER_ID column of the FND_USER table |
| CREATION_DATE | DATE | Y | Standard who column - date when this row was created. | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard who column - unique internal identifier user who last updated this row. Foreign key to the USER_ID column of the FND_USER table. |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column - date when a user last updated this row. | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard who column - operating system login of user who last updated this row. Foreign key to the LOGIN_ID column of the FND_LOGINS table. | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. This number is incremented for every update to the row through the application. |
| VAL_SEC_SEGMENT_ID | NUMBER | (15) | Value Sec Segment ID |
IBY.IBY_TRANSMIT_VALUES does not reference any database object
IBY.IBY_TRANSMIT_VALUES is referenced by following:
| Description: | IBY_BEPKEYS stores information about the payment systems. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_TRXN_CORE.TRXNMID | IBY_TRXN_SUMMARIES_ALL |
| IBY_TRXN_CORE.CHNAME_SEC_SEGMENT_ID | IBY_SECURITY_SEGMENTS |
| IBY_TRXN_CORE.EXPIRY_SEC_SEGMENT_ID | IBY_SECURITY_SEGMENTS |
IBY_BEPKEYS stores information about the payment systems.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_TRXN_CORE_TRXNMID_U1 | UNIQUE | APPS_TS_TX_IDX | TRXNMID |
| IBY_TRXN_CORE_N1 | NONUNIQUE | APPS_TS_TX_IDX | AUTHCODE |
| IBY_TRXN_CORE_N2 | NONUNIQUE | APPS_TS_TX_IDX | TRACENUMBER |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| TRXNMID | NUMBER | Y | Primary key as well as foreign key associating the POS data with a single credit card transaction | |
| TERMINALID | VARCHAR2 | (80) | used for credit card processing. A merchant can get multiple terminal Ids and there is a batch open for each Terminal Id. The merchant could perform operations on those batches independantly. | |
| TRACENUMBER | VARCHAR2 | (80) | Unique Transaction id for payworks Back End Payment System follow-on transactions | |
| AUTHCODE | VARCHAR2 | (80) | authorization code received from Credit Card Processing System for authorization. | |
| REFERENCECODE | VARCHAR2 | (80) | reference code received from Back End Payment Systems or processing system which can be used for reference. | |
| OPERATIONCODE | VARCHAR2 | (80) | generic code for any operation such as auth, capture etc | |
| INSTRNAME | VARCHAR2 | (80) | payment instrument name such as Visa, MasterCard etc. | |
| AUTHTYPE | VARCHAR2 | (20) | denotes whether authorization is authonly or authcapture. | |
| AVSCODE | VARCHAR2 | (80) | Address Verification Code from back end payment systems. | |
| ACQUIRER | VARCHAR2 | (80) | merchant bank which may be optionally returned by back end payment system. | |
| AUXMSG | VARCHAR2 | (255) | auxillary message that may be returned by the payment system or processing system. | |
| OBJECT_VERSION_NUMBER | NUMBER | (5) | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. This number is incremented for every update to the row through the application. |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column - date when a user last updated this row. | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard who column - user who last updated this row (foreign key to FND_USER.USER_ID). |
| CREATED_BY | NUMBER | (15) | Y | Standard who column - user who created this row (foreign key to FND_USER.USER_ID). |
| CREATION_DATE | DATE | Y | Standard who column - date when this row was created. | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard who column - operating system login of user who last updated this row (foreign key to FND_LOGINS.LOGIN_ID). | |
| PONUMBER | VARCHAR2 | (80) | Buyer's Purchase Order Number | |
| TAXAMOUNT | NUMBER | The amount, out of the total price, that consists of tax. | ||
| SHIPFROMZIP | VARCHAR2 | (80) | The ZIP code from which merchandise is to be sent. | |
| SHIPTOZIP | VARCHAR2 | (80) | The ZIP code to which merchandise is to be sent. | |
| SECURITY_GROUP_ID | NUMBER | Used in hosted environments | ||
| VOICEAUTHFLAG | VARCHAR2 | (1) | Indicates whether Authorization was done manually | |
| CVV2RESULT | VARCHAR2 | (5) | CVV2 validation result returned by the payment system/credit card network. | |
| PROC_TRACENUMBER | VARCHAR2 | (80) | Processor trace/reference number column. Required by certain processors. | |
| DATE_OF_VOICE_AUTHORIZATION | DATE | Date Of Voice Authorization | ||
| POS_READER_CAPABILITY_CODE | VARCHAR2 | (30) | Card reader capability at the point-of-sale from lookup type IBY_POS_CAPABILITY_TYPE | |
| POS_ENTRY_METHOD_CODE | VARCHAR2 | (30) | Card entry method from lookup type IBY_POS_ENTRY_TYPE | |
| POS_ID_METHOD_CODE | VARCHAR2 | (30) | Card holder identification method from lookup type IBY_POS_CARD_ID_TYPE | |
| POS_AUTH_SOURCE_CODE | VARCHAR2 | (30) | Card authorization source from lookup type IBY_POS_AUTH_SRC_TYPE | |
| READER_DATA | VARCHAR2 | (255) | Card reader data, encoded in a text format | |
| POS_TRXN_FLAG | VARCHAR2 | (1) | Indicates whether the transaction occurred at a point-of-sale | |
| INSTR_EXPIRYDATE | DATE | Expiration date for the card | ||
| CARD_SUBTYPE_CODE | VARCHAR2 | (30) | Subtype, used for purchase cards from lookup type IBY_PURCHASECARD_SUBTYPE | |
| CARD_DATA_LEVEL | VARCHAR2 | (10) | Purchase card data level from lookup type IBY_PCARD_DATA_LEVEL | |
| INSTR_OWNER_NAME | VARCHAR2 | (80) | Card holder name, as a single string | |
| INSTR_OWNER_ADDRESS_LINE1 | VARCHAR2 | (240) | Card holder billing address line 1 information. | |
| INSTR_OWNER_ADDRESS_LINE2 | VARCHAR2 | (240) | Card holder billing address line 2 information. | |
| INSTR_OWNER_ADDRESS_LINE3 | VARCHAR2 | (240) | Card holder billing address line 2 information. | |
| INSTR_OWNER_CITY | VARCHAR2 | (80) | Card holder billing address city information | |
| INSTR_OWNER_STATE_PROVINCE | VARCHAR2 | (80) | Card holder billing address state or province information | |
| INSTR_OWNER_COUNTRY | VARCHAR2 | (80) | Card holder billing address country information | |
| INSTR_OWNER_POSTALCODE | VARCHAR2 | (80) | Card holder billing address information | |
| INSTR_OWNER_PHONE | VARCHAR2 | (80) | Card holder billing address phone information | |
| INSTR_OWNER_EMAIL | VARCHAR2 | (80) | Card holder email information | |
| DEBIT_NETWORK_CODE | VARCHAR2 | (80) | Debit card network code | |
| SURCHARGE_AMOUNT | NUMBER | Debit card surcharge amount | ||
| ENCRYPTED | VARCHAR2 | (240) | Y | Indicates whether the card holder name and the expiry date details are encrypted or not. |
| EXPIRY_SEC_SEGMENT_ID | NUMBER | (15) | Expiry date segment identifier - for security purposes | |
| CHNAME_SEC_SEGMENT_ID | NUMBER | (15) | Card holder name segment identifier - for security purposes |
IBY.IBY_TRXN_CORE does not reference any database object
IBY.IBY_TRXN_CORE is referenced by following:
| Description: | Table used to store XML documents associated with a particular transaction. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_TRXN_DOCUMENTS.TRXNMID | IBY_TRXN_SUMMARIES_ALL |
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_F_T_CRDT_APPS_ALL_B.CREDIT_APP_XML_ID | IBY_TRXN_DOCUMENTS |
| IBY_F_T_CRDT_APPS_ALL_B.TERMS_N_CONDITIONS_XML_ID | IBY_TRXN_DOCUMENTS |
| IBY_G_T_MESSAGES.MESSAGE_XML_ID | IBY_TRXN_DOCUMENTS |
Table used to store XML documents associated with a particular transaction.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_TRXN_DOCUMENTS_U1 | UNIQUE | APPS_TS_TX_IDX | TRXN_DOCUMENT_ID |
| IBY_TRXN_DOCUMENTS_U2 | UNIQUE | APPS_TS_TX_IDX |
TRXNMID
DOCTYPE |
| SYS_IL0000195185C00003$$ | UNIQUE | APPS_TS_TX_DATA | |
| IBY_TRXN_DOCUMENTS_N1 | NONUNIQUE | APPS_TS_TX_IDX | PAYMENT_INSTRUCTION_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| TRXNMID | NUMBER | Column is a foreign key into table IBY_TRXN_SUMMARIES_ALL . Indicates which transaction | ||
| DOCTYPE | NUMBER | Y | Column holds an application defined number indicating what type of document this is. | |
| DOCUMENT | CLOB | (4000) | Column holds the actual XML document. | |
| FROZEN_FLAG | VARCHAR2 | (1) | Oracle Internal use only - reserved for future use | |
| TO_BE_PURGED_FLAG | VARCHAR2 | (1) | Oracle Internal use only - reserved for future use | |
| OBJECT_VERSION_NUMBER | NUMBER | (5) | This column is used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. | |
| LAST_UPDATE_DATE | DATE | Standard Who column - date when a user last updated this row. | ||
| LAST_UPDATED_BY | NUMBER | (15) | Standard who column - user who last updated this row (foreign key to FND_USER.USER_ID). | |
| CREATION_DATE | DATE | Standard who column - date when this row was created. | ||
| CREATED_BY | NUMBER | (15) | Standard who column - user who created this row (foreign key to FND_USER.USER_ID). | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard who column - operating system login of user who last updated this row (foreign key to FND_LOGINS.LOGIN_ID). | |
| SECURITY_GROUP_ID | NUMBER | Used in hosted environments | ||
| TRXN_DOCUMENT_ID | NUMBER | Y | System generated Primary Key | |
| REQUEST_ID | NUMBER | (15) | Request Identifier | |
| PROGRAM_APPLICATION_ID | NUMBER | (15) | Application Identifier of last concurrent program to update record | |
| PROGRAM_ID | NUMBER | (15) | Identifier of last concurrent program to update record | |
| PROGRAM_UPDATE_DATE | DATE | Last date concurrent program updated record | ||
| DOCUMENT_PURGED_FLAG | VARCHAR2 | (1) | Oracle Internal use only - reserved for future use | |
| DOCUMENT_PURGED_DATE | DATE | Oracle Internal use only - reserved for future use | ||
| PAYMENT_INSTRUCTION_ID | NUMBER | Payment instruction for the transaction |
IBY.IBY_TRXN_DOCUMENTS does not reference any database object
IBY.IBY_TRXN_DOCUMENTS is referenced by following:
| Description: | IBY_TRXN_ERROR_TOKENS stores the values that are used to fill out the tokens in transaction error messages. For each error in IBY_TRANSACTION_ERRORS, this table contains one or more rows with one row for each token included in the correspon |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_TRXN_ERROR_TOKENS.TRANSACTION_ERROR_ID | IBY_TRANSACTION_ERRORS |
IBY_TRXN_ERROR_TOKENS stores the values that are used to fill out the tokens in transaction error messages. For each error in IBY_TRANSACTION_ERRORS, this table contains one or more rows with one row for each token included in the corresponding error message. Each row contains the token name, or code, the value to be substituted for that token, and the lookup from which the value came, if applicable.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_TRXN_ERROR_TOKENS_U1 | UNIQUE | APPS_TS_TX_IDX |
TRANSACTION_ERROR_ID
TOKEN_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| TRANSACTION_ERROR_ID | NUMBER | (15) | Y | Transaction error Identifier |
| TOKEN_NAME | VARCHAR2 | (100) | Y | Name or code of the token |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object Version number | |
| TOKEN_VALUE | VARCHAR2 | (240) | Value to be populated into the error message | |
| LOOKUP_TYPE_SOURCE | VARCHAR2 | (30) | FND lookup type to which the token value belongs | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column |
IBY.IBY_TRXN_ERROR_TOKENS does not reference any database object
IBY.IBY_TRXN_ERROR_TOKENS is referenced by following:
| Description: | IBY_TRXN_EXTENDED stores the details of a payment request that are specific for extended set functionality for credit cards. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_TRXN_EXTENDED.TRXNMID | IBY_TRXN_SUMMARIES_ALL |
IBY_TRXN_EXTENDED stores the details of a payment request that are specific for extended set functionality for credit cards.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_TRXN_EXTENDED_TRXNMID_U1 | UNIQUE | APPS_TS_TX_IDX | TRXNMID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| TRXNMID | NUMBER | Y | Transaction Identifier | |
| SETTRXNID | VARCHAR2 | (80) | Transaction Identifier from payment system | |
| APPROVALCODE | VARCHAR2 | (80) | SET approval code for an operation. For example, for authorization transaction, it contains the authorization code. | |
| COMPLETIONCODE | VARCHAR2 | (80) | Additional SET status code for completion of transaction | |
| SPLITID | NUMBER | Counter that indicates the sequence in the split shipment | ||
| TERMINALID | VARCHAR2 | (80) | Used for credit card processing. A merchant can get multiple terminal identifiers and there is a batch open for each Terminal Identifier. The merchant can perform operations on those batches independantly. | |
| SUBAUTHIND | NUMBER | Subsequent authorization indicator | ||
| CARDBIN | VARCHAR2 | (10) | First five or six digits that identifies the card | |
| BATCHSEQNUM | NUMBER | Sequence of the transaction in a batch | ||
| BATCHTRXNSTATUS | NUMBER | Indicates the status of the row if it is included in batch operation | ||
| SETREQTYPE | NUMBER | Denotes whether pinit or preq SET request type | ||
| PREVSPLITID | NUMBER | Used during subsequent authorization | ||
| SUBSAUTHTYPE | VARCHAR2 | (20) | Authorization type for subsequent authorization | |
| SPLITSHIPMENT | NUMBER | Y or N flag indicating if the shipment has been split | ||
| AUTHCURRENCY | VARCHAR2 | (10) | Authorized currency | |
| AUTHPRICE | NUMBER | Authorized price | ||
| INSTALLTOTALTRXNS | NUMBER | Number of installments | ||
| RECURRINGFREQ | NUMBER | Frequency in number of days of recurring authorization | ||
| RECURRINGEXPDATE | DATE | Date for final installment | ||
| CUSTREFNUM | VARCHAR2 | (80) | Customer reference number | |
| DESTPOSTALCODE | VARCHAR2 | (10) | Destination postal code | |
| LOCALTAXPRICE | NUMBER | Local tax price | ||
| LOCALTAXCURRENCY | VARCHAR2 | (10) | Local tax currency | |
| CREDITCOUNTER | NUMBER | Indicates the nth return for multiple returns | ||
| OBJECT_VERSION_NUMBER | NUMBER | (5) | Y | Used for locking purposes that subsequently allows for checking if there is 'old data on the screen compared to what is in the database. The situation occurs when the HTML application is a stateless application. |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| CREATION_DATE | DATE | Y | Standard Who column | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| SECURITY_GROUP_ID | NUMBER | Used in hosted environments |
IBY.IBY_TRXN_EXTENDED does not reference any database object
IBY.IBY_TRXN_EXTENDED is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_TRXN_EXTENSIBILITY.TRXNMID | IBY_TRXN_SUMMARIES_ALL |
IBY_TRXN_EXTENSIBILITY stores payment system transactional data, which cannot be accommodated in the Oracle Payments data model. Each datum is stored as a name-value pair and associated with a single transaction from IBY_TRXN_SUMMARIES_ALL .
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_TRXN_EXTENSIBILITY_TXID_U1 | UNIQUE | APPS_TS_TX_IDX | TRXN_EXTEND_ID |
| IBY_TRXN_EXTENSIBILITY_TMID_N1 | NONUNIQUE | APPS_TS_TX_IDX | TRXNMID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| TRXN_EXTEND_ID | NUMBER | (15) | Y | Primary key for this table |
| TRXNMID | NUMBER | (15) | Y | Foreign key to the transaction summaries table |
| EXTEND_NAME | VARCHAR2 | (100) | Y | Extensibility parameter name |
| EXTEND_VALUE | VARCHAR2 | (200) | Y | Extensibility parameter value |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. |
IBY.IBY_TRXN_EXTENSIBILITY does not reference any database object
IBY.IBY_TRXN_EXTENSIBILITY is referenced by following:
| Description: | IBY_TRXN_FI contains the details of a payment request that are specific for systems that support both bank account transfers and credit cards such as Financial Institutions. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_TRXN_FI.TRXNMID | IBY_TRXN_SUMMARIES_ALL |
IBY_TRXN_FI contains the details of a payment request that are specific for systems that support both bank account transfers and credit cards such as Financial Institutions.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_TRXN_FI_TRXNMID_U1 | UNIQUE | APPS_TS_TX_IDX | TRXNMID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| TRXNMID | NUMBER | Y | Transaction Identifier | |
| SPLITID | NUMBER | Y | counter that indicates the sequence in the split shipment | |
| PSREQID | VARCHAR2 | (80) | system generated ID that will be sent to FI Back End Payment Systems during schedule of payments with them | |
| REFERENCECODE | VARCHAR2 | (80) | referencecode from Back End Payment System | |
| AUXMSG | VARCHAR2 | (255) | any auxillary message that may be returned by the payment system or processing system | |
| SRVID | VARCHAR2 | (80) | ID returned by Back End Payment System when the payment is scheduled | |
| PROCESSFEE | NUMBER | The fee charged for processing a transaction | ||
| OBJECT_VERSION_NUMBER | NUMBER | (5) | Y | This column is used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column - date when a user last updated this row. | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard who column - user who last updated this row (foreign key to FND_USER.USER_ID). |
| CREATION_DATE | DATE | Y | Standard who column - date when this row was created. | |
| CREATED_BY | NUMBER | (15) | Y | Standard who column - user who created this row (foreign key to FND_USER.USER_ID). |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard who column - operating system login of user who last updated this row (foreign key to FND_LOGINS.LOGIN_ID). | |
| SECURITY_GROUP_ID | NUMBER | Used in hosted environments |
IBY.IBY_TRXN_FI does not reference any database object
IBY.IBY_TRXN_FI is referenced by following:
| Description: | 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 |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_TRXN_SUMMARIES_ALL.MPAYEEID | IBY_PAYEE |
| IBY_TRXN_SUMMARIES_ALL.CC_ISSUER_RANGE_ID | IBY_CC_ISSUER_RANGES |
| IBY_TRXN_SUMMARIES_ALL.INSTRNUM_SEC_SEGMENT_ID | % |
| IBY_TRXN_SUMMARIES_ALL.PAYER_INSTR_ASSIGNMENT_ID | IBY_PMT_INSTR_USES_ALL |
| IBY_TRXN_SUMMARIES_ALL.AR_RECEIPT_METHOD_ID | AR_RECEIPT_METHODS |
| IBY_TRXN_SUMMARIES_ALL.INITIATOR_EXTENSION_ID | IBY_FNDCPT_TX_EXTENSIONS |
| IBY_TRXN_SUMMARIES_ALL.MBATCHID | IBY_BATCHES_ALL |
| IBY_TRXN_SUMMARIES_ALL.BEPID | IBY_BEPINFO |
| IBY_TRXN_SUMMARIES_ALL.MTANGIBLEID | IBY_TANGIBLE |
| IBY_TRXN_SUMMARIES_ALL.CUST_ACCOUNT_ID | HZ_CUST_ACCOUNTS |
| IBY_TRXN_SUMMARIES_ALL.SALES_REP_PARTY_ID | HZ_PARTIES |
| IBY_TRXN_SUMMARIES_ALL.SUB_KEY_ID | IBY_PAYEE_SUBKEYS |
| IBY_TRXN_SUMMARIES_ALL.MPAYEEID | IBY_PAYEE |
| IBY_TRXN_SUMMARIES_ALL.BEPID | IBY_BEPINFO |
| IBY_TRXN_SUMMARIES_ALL.MTANGIBLEID | IBY_TANGIBLE |
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_F_T_CRDT_APPS_ALL_B.TRXN_SUMMARY_ID | IBY_TRXN_SUMMARIES_ALL |
| IBY_G_T_MESSAGES.TRXN_SUMMARY_ID | IBY_TRXN_SUMMARIES_ALL |
| IBY_TRXN_CORE.TRXNMID | IBY_TRXN_SUMMARIES_ALL |
| IBY_TRXN_DOCUMENTS.TRXNMID | IBY_TRXN_SUMMARIES_ALL |
| IBY_TRXN_EXTENDED.TRXNMID | IBY_TRXN_SUMMARIES_ALL |
| IBY_TRXN_EXTENSIBILITY.TRXNMID | IBY_TRXN_SUMMARIES_ALL |
| IBY_TRXN_FI.TRXNMID | IBY_TRXN_SUMMARIES_ALL |
IBY_TRXN_SUMMARIES_ALL stores 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 instruments and the operations on them. The specific details are stored in other detail tables such as IBY_TRXN_CORE, IBY_TRXN_EXTENDED, and IBY_TRXN_FI, based on the type of operation and the payment instrument used for payment.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_TRXN_SUMM_TRXNMID_U1 | UNIQUE | APPS_TS_TX_IDX | TRXNMID |
| IBY_TRXN_SUMMARIES_ALL_N10 | NONUNIQUE | APPS_TS_TX_IDX | CUST_ACCOUNT_ID |
| IBY_TRXN_SUMMARIES_ALL_N11 | NONUNIQUE | APPS_TS_TX_IDX | REQDATE |
| IBY_TRXN_SUMMARIES_ALL_N12 | NONUNIQUE | APPS_TS_TX_IDX | TRXNREF |
| IBY_TRXN_SUMMARIES_ALL_N13 | NONUNIQUE | APPS_TS_TX_IDX | INSTRNUM_HASH |
| IBY_TRXN_SUMMARIES_ALL_N14 | NONUNIQUE | APPS_TS_TX_IDX | MBATCHID |
| IBY_TRXN_SUMMARIES_ALL_N15 | NONUNIQUE | APPS_TS_TX_IDX | TRXNTYPEID |
| IBY_TRXN_SUMMARIES_ALL_N16 | NONUNIQUE | APPS_TS_TX_IDX |
PAYERID
MPAYEEID |
| IBY_TRXN_SUMMARIES_ALL_N7 | NONUNIQUE | APPS_TS_TX_IDX | INSTRNUMBER |
| IBY_TRXN_SUMMARIES_ALL_N8 | NONUNIQUE | APPS_TS_TX_IDX | PAYERINSTRID |
| IBY_TRXN_SUMMARIES_ALL_N9 | NONUNIQUE | APPS_TS_TX_IDX | BATCHID |
| IBY_TRXN_SUMM_MTANGIBLEID_N5 | NONUNIQUE | APPS_TS_TX_IDX | MTANGIBLEID |
| IBY_TRXN_SUMM_NEEDSUPD_N4 | NONUNIQUE | APPS_TS_TX_IDX | NEEDSUPDT |
| IBY_TRXN_SUMM_PAYEEID_N6 | NONUNIQUE | APPS_TS_TX_IDX | PAYEEID |
| IBY_TRXN_SUMM_STATUS_N3 | NONUNIQUE | APPS_TS_TX_IDX | STATUS |
| IBY_TRXN_SUMM_TANGIBLEID_N2 | NONUNIQUE | APPS_TS_TX_IDX | TANGIBLEID |
| IBY_TRXN_SUMM_TRANS_ID_N1 | NONUNIQUE | APPS_TS_TX_IDX | TRANSACTIONID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| TRXNMID | NUMBER | Y | System-generated Identifier | |
| TRANSACTIONID | NUMBER | Y | Identifier generated for each payment request, or orapmtreq, and passed back to electronic commerce application | |
| TANGIBLEID | VARCHAR2 | (80) | Y | Bill or order Identifier |
| PAYEEID | VARCHAR2 | (80) | Y | Identifier of the payee passed by electronic commerce application |
| BEPID | NUMBER | (15) | Payment system Identifier | |
| MPAYEEID | NUMBER | Y | Payee Identifier | |
| ECAPPID | NUMBER | (15) | Y | Electronic commerce application Identifier |
| ORG_ID | NUMBER | (15) | Organization Identifier | |
| PAYMENTMETHODNAME | VARCHAR2 | (80) | Payment method name | |
| MTANGIBLEID | NUMBER | Y | Master identifier that points to iby_tangible table for additional information about orders | |
| PAYEEINSTRID | NUMBER | Instrument Identifier for the payee | ||
| PAYERID | VARCHAR2 | (80) | Payer Identifier | |
| PAYERINSTRID | NUMBER | Instrument Identifier for the payer | ||
| DETAILLOOKUP | VARCHAR2 | (30) | Lookup column for CORE, EXTENDED, or FI transactions | |
| AMOUNT | NUMBER | Transaction amount | ||
| INSTRNUMBER | VARCHAR2 | (60) | Instrument number can be credit card number for 11i in case of unregistered instruments. | |
| CURRENCYNAMECODE | VARCHAR2 | (15) | Currency code | |
| STATUS | NUMBER | (15) | Y | Status of the transaction from lookup type IBY_TRANSACTION_STATUS |
| UPDATEDATE | DATE | Date that scheduled payment is updated | ||
| TRXNTYPEID | NUMBER | (15) | From lookup type IBY_TRXNTYPES | |
| ERRORLOCATION | NUMBER | Identifies the location of error | ||
| BEPCODE | VARCHAR2 | (40) | Error code from payment system | |
| BEPMESSAGE | VARCHAR2 | (255) | Error message from payment system | |
| BATCHID | VARCHAR2 | (80) | Batch Identifier provided by electronic commerce application | |
| SETTLEDATE | DATE | Scheduled date for the bill or order used for offline payments only | ||
| MBATCHID | NUMBER | Batch Identifier | ||
| REQDATE | DATE | Date when the batch operation request is received | ||
| REQTYPE | VARCHAR2 | (20) | Type of request such as closebatch, purgebatch, or openbatch | |
| REQSEQ | NUMBER | (4) | Request sequence | |
| DESTURL | VARCHAR2 | (1024) | Payment system URL constructed during schedule of payments | |
| NLSLANG | VARCHAR2 | (80) | NLS language | |
| NEEDSUPDT | VARCHAR2 | (3) | Y or N flag indicating that the row has changed status | |
| OVERALL_SCORE | NUMBER | Overall risk score | ||
| OBJECT_VERSION_NUMBER | NUMBER | (5) | Y | Used for locking purposes that subsequently allows for checking if there is old data on the screen compared to what is in the database. The situation occurs when the HTML application is a stateless application. |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| INSTRTYPE | VARCHAR2 | (30) | Instrument type | |
| SECURITY_GROUP_ID | NUMBER | Used in hosted environments | ||
| SALES_REP_PARTY_ID | NUMBER | (15) | Party Identifier for the sales representative who initiated the transaction. Foreign key to HZ_PARTIES | |
| BEPKEY | VARCHAR2 | (80) | Merchant account Identifier used with this transaction | |
| CUST_ACCOUNT_ID | NUMBER | (15) | Customer account for which the payment transaction is being processed. Foreign key to HZ_CUST_ACCOUNTS | |
| INSTRSUBTYPE | VARCHAR2 | (40) | Holds the instrument subtype for the payment transaction | |
| SUB_KEY_ID | NUMBER | Oracle internal use only, reserved for future use | ||
| ECBATCHID | VARCHAR2 | (80) | Used for AR bills receivable integration. RA_BATCHES_ALL.BATCH_ID | |
| TRXNREF | VARCHAR2 | (240) | Optional, secondary transaction Identifier to be passed by source application. Useful in distinguishing transactions when the tangible or order ID must be shared | |
| PROCESS_PROFILE_CODE | VARCHAR2 | (30) | Funds capture process profile | |
| ACCT_SITE_USE_ID | NUMBER | (15) | Account site use identifier | |
| ORG_TYPE | VARCHAR2 | (30) | Organization type from lookup type IBY_ORGANIZATION_TYPES | |
| LEGAL_ENTITY_ID | NUMBER | (15) | Legal entity identifier | |
| BILL_TO_ADDRESS_ID | NUMBER | (15) | Identifier of the bill-to address | |
| FACTORED_FLAG | VARCHAR2 | (1) | Y or N flag that indicates if this payment comes from a third party on behalf of the ultimate payer | |
| INSTRNUM_HASH | VARCHAR2 | (60) | Hash value of the transaction payment instrument number | |
| INSTRNUM_LENGTH | NUMBER | (3) | Length of the transaction payment instrument | |
| PAYMENT_CHANNEL_CODE | VARCHAR2 | (30) | Payment method | |
| CC_ISSUER_RANGE_ID | NUMBER | (15) | Identifier of the credit card number range the payment instrument number belongs to | |
| INSTRNUM_SEC_SEGMENT_ID | NUMBER | (15) | Identifier of the security segment holding the encrypted payment instrument number | |
| PROC_REFERENCE_CODE | VARCHAR2 | (240) | Payment processor reference code | |
| PROC_REFERENCE_AMOUNT | NUMBER | Payment processor reference amount | ||
| SETTLEMENT_CUSTOMER_REFERENCE | VARCHAR2 | (255) | Settlement customer reference | |
| BR_MATURITY_DATE | DATE | Bills receivable maturity date | ||
| SETTLEMENT_DUE_DATE | DATE | Settlement due date | ||
| CALL_APP_SERVICE_REQ_CODE | VARCHAR2 | (255) | External application request set identifier | |
| BANK_CHARGE_BEARER_CODE | VARCHAR2 | (30) | Bank charge bearer | |
| DIRDEB_INSTRUCTION_CODE | VARCHAR2 | (30) | Direct debit instruction code | |
| DEBIT_ADVICE_DELIVERY_METHOD | VARCHAR2 | (30) | Default delivery method set on the payer level for debit notification | |
| DEBIT_ADVICE_EMAIL | VARCHAR2 | (255) | Debit notification email address | |
| DEBIT_ADVICE_FAX | VARCHAR2 | (100) | Debit notification fax number | |
| PAYER_PARTY_ID | NUMBER | Payer TCA party identifier | ||
| FIRST_TRXN_FLAG | VARCHAR2 | (1) | Y or N flag | |
| ACCT_SITE_ID | NUMBER | (15) | Identifier of the account site for a funds capture transaction | |
| DEBIT_AUTH_FLAG | VARCHAR2 | (1) | Debit authorization flag | |
| DEBIT_AUTH_METHOD | VARCHAR2 | (30) | Debit authorization method | |
| DEBIT_AUTH_REFERENCE | VARCHAR2 | (100) | Debit authorization reference | |
| PAYER_INSTR_ASSIGNMENT_ID | NUMBER | (15) | Instrument assignment identifier for the payer instrument | |
| PAYER_NOTIFICATION_REQUIRED | VARCHAR2 | (1) | Y or N flag indicating whether payer notification is created for this transaction if it is a settlement | |
| PAYER_NOTIFICATION_CREATED | VARCHAR2 | (1) | Y or N flag indicating whether payer notification is created for this transaction if it is a settlement | |
| AR_RECEIPT_METHOD_ID | NUMBER | (15) | Oracle Receivables receipt method | |
| BR_DRAWEE_ISSUED_FLAG | VARCHAR2 | (1) | Y or N flag that indicates if the the drawee issues the bill recievable | |
| BR_SIGNED_FLAG | VARCHAR2 | (1) | Y or N flag that indicates if the drawee needs to accept the bill receivable | |
| SALT_VERSION | NUMBER | (2) | Salt Version used for Encryption | |
| INITIATOR_EXTENSION_ID | NUMBER | (15) | Y | This is a foreign key to IBY_FNDCPT_TX_EXTENSIONS.TRXN_EXTENSION_ID. This denotes the extension that initiated the transaction. |
| LOGICAL_GROUP_REFERENCE | VARCHAR2 | (80) | Stroes the logical group reference of a transaction. | |
| SEQ_TYPE | VARCHAR2 | (30) | payment type code | |
| SERVICE_LEVEL | VARCHAR2 | (30) | service level for a transaction | |
| LOCALINSTR | VARCHAR2 | (30) | local instrument of a transction | |
| CATEGORY_PURPOSE | VARCHAR2 | (30) | category purpose of a trxn. | |
| DEBIT_AUTHORIZATION_ID | NUMBER | (15) | Mandate ID | |
| CREDITOR_REFERENCE | VARCHAR2 | (35) | Creditor reference for a transaction. |
IBY.IBY_TRXN_SUMMARIES_ALL does not reference any database object
IBY.IBY_TRXN_SUMMARIES_ALL is referenced by following:
| Description: | IBY_TRXN_TYPES stores the payment processing transaction types required by the dependent products for submitting payment transactions to Oracle Payments. This is used for both funds disbursement and funds capture transactions. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
|
IBY_DOCS_PAYABLE_ALL.CALLING_APP_ID
IBY_DOCS_PAYABLE_ALL.PAY_PROC_TRXN_TYPE_CODE |
IBY_TRXN_TYPES_B |
|
IBY_DOCUMENTS_PAYABLE_H.CALLING_APP_ID
IBY_DOCUMENTS_PAYABLE_H.PAY_PROC_TRXN_TYPE_CODE |
IBY_TRXN_TYPES_B |
|
IBY_TRANSACTION_ERRORS.CALLING_APP_ID
IBY_TRANSACTION_ERRORS.PAY_PROC_TRXN_TYPE_CODE |
IBY_TRXN_TYPES_B |
|
IBY_TRXN_TYPES_TL.APPLICATION_ID
IBY_TRXN_TYPES_TL.PAY_PROC_TRXN_TYPE_CODE |
IBY_TRXN_TYPES_B |
IBY_TRXN_TYPES stores the payment processing transaction types required by the dependent products for submitting payment transactions to Oracle Payments. This is used for both funds disbursement and funds capture transactions.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_TRXN_TYPES_B_U1 | UNIQUE | APPS_TS_TX_IDX |
APPLICATION_ID
PAY_PROC_TRXN_TYPE_CODE ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| APPLICATION_ID | NUMBER | (15) | Y | Application Identifier of the calling product |
| PAY_PROC_TRXN_TYPE_CODE | VARCHAR2 | (30) | Y | System code for the transaction type. Must be unique per calling application |
| SEEDED_FLAG | VARCHAR2 | (1) | Y | Y or N flag for whether the payment processing transaction type is seeded |
| PAYMENT_FLOW | VARCHAR2 | (30) | Y | Category of this transaction type. Values are defined in the IBY_PAYMENT_FLOW lookup and include DISBURSEMENTS and FUND CAPTURE. |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_TRXN_TYPES_B does not reference any database object
IBY.IBY_TRXN_TYPES_B is referenced by following:
| Description: | IBY_TRXN_TYPES stores the payment processing transaction types required by the dependent products for submitting payment transactions to Oracle Payments. This is used for both funds disbursement and funds capture transactions. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
|
IBY_TRXN_TYPES_TL.APPLICATION_ID
IBY_TRXN_TYPES_TL.PAY_PROC_TRXN_TYPE_CODE |
IBY_TRXN_TYPES_B |
IBY_TRXN_TYPES stores the payment processing transaction types required by the dependent products for submitting payment transactions to Oracle Payments. This is used for both funds disbursement and funds capture transactions.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_TRXN_TYPES_TL_U1 | UNIQUE | APPS_TS_TX_IDX |
APPLICATION_ID
PAY_PROC_TRXN_TYPE_CODE LANGUAGE ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| APPLICATION_ID | NUMBER | (15) | Y | Application Identifier of the calling product |
| PAY_PROC_TRXN_TYPE_CODE | VARCHAR2 | (30) | Y | System code for the transaction type. Must be unique per calling application |
| LANGUAGE | VARCHAR2 | (4) | Y | Language code |
| SOURCE_LANG | VARCHAR2 | (4) | Y | Language code of the record's current language |
| NAME | VARCHAR2 | (80) | Y | User friendly name |
| DESCRIPTION | VARCHAR2 | (240) | Free text description of the payment processing transaction type | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_TRXN_TYPES_TL does not reference any database object
IBY.IBY_TRXN_TYPES_TL is referenced by following:
| Description: |
|---|
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_UPG_GDFS_N1 | NONUNIQUE | APPS_TS_TX_IDX |
CUST_ACCOUNT_ID
ACCT_SITE_USE_ID |
| IBY_UPG_GDFS_N2 | NONUNIQUE | APPS_TS_TX_IDX | SUPPLIER_SITE_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| CUST_ACCOUNT_ID | NUMBER | (15) | ||
| ACCT_SITE_USE_ID | NUMBER | (15) | ||
| SUPPLIER_ID | NUMBER | (15) | ||
| SUPPLIER_SITE_ID | NUMBER | (15) | ||
| DIRDEB_INSTRUCTION_CODE | VARCHAR2 | (30) | ||
| BANK_CHARGE_BEARER | VARCHAR2 | (30) | ||
| BANK_INSTRUCTION1_CODE | VARCHAR2 | (30) | ||
| BANK_INSTRUCTION2_CODE | VARCHAR2 | (30) | ||
| BANK_INSTRUCTION_DETAILS | VARCHAR2 | (255) | ||
| PAYMENT_REASON_CODE | VARCHAR2 | (30) | ||
| PAYMENT_TEXT_MESSAGE1 | VARCHAR2 | (150) | ||
| PAYMENT_TEXT_MESSAGE2 | VARCHAR2 | (150) | ||
| PAYMENT_TEXT_MESSAGE3 | VARCHAR2 | (150) | ||
| PAYMENT_FORMAT_CODE | VARCHAR2 | (30) | ||
| DELIVERY_CHANNEL_CODE | VARCHAR2 | (30) | ||
| CREATED_BY | NUMBER | (15) | Y | |
| CREATION_DATE | DATE | Y | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| LAST_UPDATE_DATE | DATE | Y | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| OBJECT_VERSION_NUMBER | NUMBER | Y |
IBY.IBY_UPG_GDFS does not reference any database object
IBY.IBY_UPG_GDFS is referenced by following:
| Description: |
|---|
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_UPG_INSTRUMENTS_N1 | NONUNIQUE | APPS_TS_TX_IDX | BANK_ACCOUNT_USES_ID |
| IBY_UPG_INSTRUMENTS_N2 | NONUNIQUE | APPS_TS_TX_IDX |
BANK_ACCOUNT_ID
INSTRUMENT_TYPE |
| IBY_UPG_INSTRUMENTS_N3 | NONUNIQUE | APPS_TS_TX_IDX |
PAYMENT_FUNCTION
ORG_ID ORG_TYPE ACCT_SITE_USE_ID CUST_ACCOUNT_ID |
| IBY_UPG_INSTRUMENTS_N4 | NONUNIQUE | APPS_TS_TX_IDX | EXT_PARTY_ID |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| INSTR_ASSIGNMENT_ID | NUMBER | (15) | Y | Instrument assignment Identifier |
| EXT_PARTY_ID | NUMBER | (15) | Y | Either payee Identifier or payer Identifier |
| INSTRUMENT_TYPE | VARCHAR2 | (30) | Y | Instrument type. Values from the IBY_INSTRUMENT_TYPES lookup include BANKACCOUNT, CREDITCARD, and DEBITCARD. |
| INSTRUMENT_ID | NUMBER | (15) | Y | Instrument Identifier |
| PAYMENT_FUNCTION | VARCHAR2 | (30) | Y | Function or purpose of the payment. Values from the lookup IBY_PAYMENT_FUNCTIONS include SUPPLIER_PAYMENT, CUSTOMER_REFUNDS, and others. |
| ORG_TYPE | VARCHAR2 | (30) | Organization type | |
| ORG_ID | NUMBER | (15) | Organization Identifier | |
| PARTY_SITE_ID | NUMBER | (15) | Party site use Identifier | |
| CUST_ACCOUNT_ID | NUMBER | (15) | Customer account Identifier. Products with CUSTOMER_PAYMENT payment function can pass this parameter to the payment components as additional context for the payer definition. | |
| ACCT_SITE_USE_ID | NUMBER | (15) | Customer account site use Identifier. Products with CUSTOMER_PAYMENT payment function can pass this parameter to the payment components as additional context for the payer definition. | |
| SUPPLIER_SITE_ID | NUMBER | (15) | Supplier site Identifier of the payee | |
| BANK_ACCOUNT_ID | NUMBER | (15) | Y | Old AP bank account Identifier |
| BANK_ACCOUNT_USES_ID | NUMBER | (15) | ||
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Object version number |
IBY.IBY_UPG_INSTRUMENTS does not reference any database object
IBY.IBY_UPG_INSTRUMENTS is referenced by following:
| Description: |
|---|
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_UPG_PPP_B_U1 | UNIQUE | APPS_TS_TX_IDX | SYSTEM_PROFILE_CODE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| SYSTEM_PROFILE_CODE | VARCHAR2 | (100) | Y | |
| BEP_SUFFIX | VARCHAR2 | (10) | ||
| SECURITY_PROTOCOL_CODE | VARCHAR2 | (100) | ||
| TRANSMIT_PROTOCOL_CODE | VARCHAR2 | (100) | ||
| PAYMENT_FORMAT_CODE | VARCHAR2 | (30) | Y | |
| POSITIVE_PAY_FORMAT_CODE | VARCHAR2 | (30) | ||
| PAY_FILE_LETTER_FORMAT_CODE | VARCHAR2 | (30) | ||
| PRINT_INSTRUCTION_IMMED_FLAG | VARCHAR2 | (1) | Y | |
| PERIODIC_SEQUENCE_NAME_1 | VARCHAR2 | (80) | ||
| PERIODIC_SEQUENCE_NAME_2 | VARCHAR2 | (80) | ||
| PERIODIC_SEQUENCE_NAME_3 | VARCHAR2 | (80) | ||
| PROCESSING_TYPE | VARCHAR2 | (30) | Y | |
| MARK_COMPLETE_EVENT | VARCHAR2 | (30) | Y | |
| MANUAL_MARK_COMPLETE_FLAG | VARCHAR2 | (1) | Y | |
| POSITIVE_PAY_DELIVERY_FLAG | VARCHAR2 | (1) | Y | |
| TRANSMIT_INSTR_IMMED_FLAG | VARCHAR2 | (1) | Y | |
| AUTOMATIC_PI_REG_SUBMIT | VARCHAR2 | (1) | Y | |
| DECLARATION_OPTION | VARCHAR2 | (30) | ||
| DCL_ONLY_FOREIGN_CURR_PMT_FLAG | VARCHAR2 | (1) | ||
| DECLARATION_REPORT_FORMAT_CODE | VARCHAR2 | (30) | ||
| DECLARATION_CURR_FX_RATE_TYPE | VARCHAR2 | (255) | ||
| DECLARATION_CURRENCY_CODE | VARCHAR2 | (10) | ||
| DECLARATION_THRESHOLD_AMOUNT | NUMBER | |||
| BANK_INSTRUCTION1_CODE | VARCHAR2 | (30) | ||
| BANK_INSTRUCTION2_CODE | VARCHAR2 | (30) | ||
| BANK_INSTRUCTION_DETAILS | VARCHAR2 | (255) | ||
| PAYMENT_TEXT_MESSAGE1 | VARCHAR2 | (150) | ||
| PAYMENT_TEXT_MESSAGE2 | VARCHAR2 | (150) | ||
| ACK_TRANSMIT_PROTOCOL_CODE | VARCHAR2 | (100) | ||
| ACK_SECURITY_PROTOCOL_CODE | VARCHAR2 | (100) | ||
| SEND_TO_FILE_FLAG | VARCHAR2 | (1) | Y | |
| PI_REGISTER_FORMAT | VARCHAR2 | (30) | ||
| BEP_ACCOUNT_ID | NUMBER | (15) | ||
| APPLICABLE_PMT_METHOD | VARCHAR2 | (240) | ||
| APPLICABLE_CURRENCY | VARCHAR2 | (240) | ||
| APPLICABLE_PAYER_ORG | VARCHAR2 | (240) | ||
| APPLICABLE_INT_BANK_ACCOUNT | VARCHAR2 | (240) | ||
| PMT_GROUP_BY_PAYMENT_DETAILS | VARCHAR2 | (1) | Y | |
| PMT_GROUP_BY_BANK_CHARGE_BEAR | VARCHAR2 | (1) | Y | |
| PMT_GROUP_BY_DELIVERY_CHANNEL | VARCHAR2 | (1) | Y | |
| PMT_GROUP_BY_REMITTANCE_MES | VARCHAR2 | (1) | Y | |
| PMT_GROUP_BY_MAX_DOCUMENTS | VARCHAR2 | (1) | Y | |
| PMT_GROUP_BY_UNIQUE_REMIT_ID | VARCHAR2 | (1) | Y | |
| PMT_GROUP_BY_SETTLE_PRIORITY | VARCHAR2 | (1) | Y | |
| PMT_GROUP_BY_PAYMENT_REASON | VARCHAR2 | (1) | Y | |
| PMT_GROUP_BY_DUE_DATE_FLAG | VARCHAR2 | (1) | Y | |
| PMT_MAX_DOCUMENTS_PER_PAYMENT | NUMBER | (15) | ||
| PMT_PAYMENT_DETAILS_LENGTH_LIM | NUMBER | (15) | ||
| PMT_PAYMENT_DETAILS_FORMULA | VARCHAR2 | (240) | ||
| INST_GROUP_BY_PAYMENT_DATE | VARCHAR2 | (1) | Y | |
| INST_GROUP_BY_PAYMENT_CURRENCY | VARCHAR2 | (1) | Y | |
| INST_GROUP_BY_INT_BANK_ACCT | VARCHAR2 | (1) | Y | |
| INST_GROUP_BY_MAX_PAYMENTS | VARCHAR2 | (1) | Y | |
| INST_GROUP_BY_PAY_SERVICE_REQ | VARCHAR2 | (1) | Y | |
| INST_GROUP_BY_LEGAL_ENTITY | VARCHAR2 | (1) | Y | |
| INST_GROUP_BY_BILL_PAYABLE | VARCHAR2 | (1) | Y | |
| INST_GROUP_BY_MAX_INSTRUCTION | VARCHAR2 | (1) | Y | |
| INST_GROUP_BY_ORGANIZATION | VARCHAR2 | (1) | Y | |
| INST_GROUP_BY_PAYMENT_FUNCTION | VARCHAR2 | (1) | Y | |
| INST_GROUP_BY_PAYMENT_REASON | VARCHAR2 | (1) | Y | |
| INST_GROUP_BY_RFC | VARCHAR2 | (1) | Y | |
| INST_MAX_PAYMENTS_PER_INSTR | NUMBER | (15) | ||
| INST_MAX_AMOUNT_PER_INSTR_VAL | NUMBER | (15) | ||
| INST_MAX_AMOUNT_PER_INSTR_CURR | VARCHAR2 | (10) | ||
| INST_MAX_AMOUNT_FX_RATE_TYPE | VARCHAR2 | (30) | ||
| INST_SORT_OPTION_1 | VARCHAR2 | (30) | ||
| INST_SORT_ORDER_1 | VARCHAR2 | (30) | ||
| INST_SORT_OPTION_2 | VARCHAR2 | (30) | ||
| INST_SORT_ORDER_2 | VARCHAR2 | (30) | ||
| INST_SORT_OPTION_3 | VARCHAR2 | (30) | ||
| INST_SORT_ORDER_3 | VARCHAR2 | (30) | ||
| REMIT_DOCUMENT_COUNT_LIMIT | NUMBER | |||
| REMIT_ALLOW_MULTIPLE_COPY_FLAG | VARCHAR2 | (1) | ||
| REMIT_PMT_DETAILS_LENGTH_LIM | NUMBER | |||
| REMIT_REMITTANCE_ADVICE_FORMAT | VARCHAR2 | (30) | ||
| REMIT_SRA_OVERRIDE_PAYEE_FLAG | VARCHAR2 | (1) | Y | |
| REMIT_ADVICE_DELIVERY_METHOD | VARCHAR2 | (100) | ||
| REMIT_AUTOMATIC_SRA_SUBMIT | VARCHAR2 | (1) | Y | Y or N flag indicating whether the remittance advice should be submitted automatically at payment completion point. |
| CREATED_BY | NUMBER | (15) | Y | |
| CREATION_DATE | DATE | Y | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| LAST_UPDATE_DATE | DATE | Y | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | |
| ELECTRONIC_PROCESSING_CHANNEL | VARCHAR2 | (50) | ||
| LOGICAL_GROUPING_MODE | VARCHAR2 | (50) | Specifies the grouping mode through which payments in an instruction are grouped | |
| BATCH_BOOKING_FLAG | VARCHAR2 | (1) | ||
| INST_GROUP_BY_PAYMENT_METHOD | VARCHAR2 | (1) | Specifies whether payments are grouped by payment method to form instruction. | |
| INACTIVE_DATE | DATE |
IBY.IBY_UPG_PPP_B does not reference any database object
IBY.IBY_UPG_PPP_B is referenced by following:
| Description: |
|---|
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_UPG_PPP_TL_U1 | UNIQUE | APPS_TS_TX_IDX |
SYSTEM_PROFILE_CODE
LANGUAGE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| SYSTEM_PROFILE_CODE | VARCHAR2 | (100) | Y | |
| LANGUAGE | VARCHAR2 | (4) | Y | |
| SOURCE_LANG | VARCHAR2 | (4) | Y | |
| SYSTEM_PROFILE_NAME | VARCHAR2 | (100) | Y | |
| SYSTEM_PROFILE_DESCRIPTION | VARCHAR2 | (255) | ||
| CREATED_BY | NUMBER | (15) | Y | |
| CREATION_DATE | DATE | Y | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| LAST_UPDATE_DATE | DATE | Y | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y |
IBY.IBY_UPG_PPP_TL does not reference any database object
IBY.IBY_UPG_PPP_TL is referenced by following:
| Description: | IBY_USED_PAYMENT_DOCS tracks information about which payment documents have been used when printing payments. |
|---|
IBY_USED_PAYMENT_DOCS tracks information about which payment documents have been used when printing payments.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_USED_PAYMENT_DOCS_N1 | NONUNIQUE | APPS_TS_TX_IDX |
PAYMENT_DOCUMENT_ID
USED_DOCUMENT_NUMBER |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYMENT_DOCUMENT_ID | NUMBER | (15) | Y | Payment document Identifier |
| USED_DOCUMENT_NUMBER | NUMBER | (15) | Y | Number of payment document used |
| DATE_USED | DATE | Date that the payment document was used | ||
| DOCUMENT_USE | VARCHAR2 | (30) | This column can be populated with any of the values defined in the IBY_PAYMENT_DOCUMENT_USES lookup. | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who Column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number |
IBY.IBY_USED_PAYMENT_DOCS does not reference any database object
IBY.IBY_USED_PAYMENT_DOCS is referenced by following:
| Description: | IBY_VALIDATION_PARAMS stores parameters for each validation. For example, one validation controls the maximum amount that can be paid in a single payment instruction. The maximum amount parameter is stored in this table, and the actual valu |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_VALIDATION_PARAMS_B.VALIDATION_SET_CODE | IBY_VALIDATION_SETS_B |
| Foreign Key Column | Foreign Table |
|---|---|
|
IBY_VALIDATION_PARAMS_TL.VALIDATION_SET_CODE
IBY_VALIDATION_PARAMS_TL.VALIDATION_PARAMETER_CODE |
IBY_VALIDATION_PARAMS_B |
IBY_VALIDATION_PARAMS stores parameters for each validation. For example, one validation controls the maximum amount that can be paid in a single payment instruction. The maximum amount parameter is stored in this table, and the actual value is stored in the associated table, IBY_VALIDATION_VALUES. This table corresponds to the Validations regions on the Payment Method and Format pages.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_VALIDATION_PARAMS_B_U1 | UNIQUE | APPS_TS_TX_IDX |
VALIDATION_PARAMETER_CODE
VALIDATION_SET_CODE ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| VALIDATION_SET_CODE | VARCHAR2 | (30) | Y | Validation set code |
| VALIDATION_PARAMETER_CODE | VARCHAR2 | (100) | Y | User entered primary key. Name or token of the parameter that should use this value |
| VALIDATION_PARAMETER_TYPE | VARCHAR2 | (30) | Y | Data type of the parameter. Values from the lookup IBY_PARAMETER_TYPES include VARCHAR2, NUMBER, and DATE. |
| VALIDATION_PARAM_DISPLAY_ORDER | NUMBER | (15) | Y | Number used to order the parameters |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_VALIDATION_PARAMS_B does not reference any database object
IBY.IBY_VALIDATION_PARAMS_B is referenced by following:
| Description: | IBY_VALIDATION_PARAMS stores parameters for each validation. For example, one validation controls the maximum amount that can be paid in a single payment instruction. The maximum amount parameter is stored in this table, and the actual valu |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
|
IBY_VALIDATION_PARAMS_TL.VALIDATION_SET_CODE
IBY_VALIDATION_PARAMS_TL.VALIDATION_PARAMETER_CODE |
IBY_VALIDATION_PARAMS_B |
IBY_VALIDATION_PARAMS stores parameters for each validation. For example, one validation controls the maximum amount that can be paid in a single payment instruction. The maximum amount parameter is stored in this table, and the actual value is stored in the associated table, IBY_VALIDATION_VALUES. This table corresponds to the Validations regions on the Payment Method and Format pages.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_VALIDATION_PARAMS_TL_U1 | UNIQUE | APPS_TS_TX_IDX |
VALIDATION_SET_CODE
VALIDATION_PARAMETER_CODE LANGUAGE ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| VALIDATION_SET_CODE | VARCHAR2 | (30) | Y | Validation set code |
| VALIDATION_PARAMETER_CODE | VARCHAR2 | (100) | Y | User entered primary key. Name or token of the parameter that should use this value |
| VALIDATION_PARAM_DISPLAY_NAME | VARCHAR2 | (100) | Y | Validation value name |
| LANGUAGE | VARCHAR2 | (4) | Y | Language code |
| SOURCE_LANG | VARCHAR2 | (4) | Y | Language code of the record's current language |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Object version number | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_VALIDATION_PARAMS_TL does not reference any database object
IBY.IBY_VALIDATION_PARAMS_TL is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_VALIDATION_PARAMS_B.VALIDATION_SET_CODE | IBY_VALIDATION_SETS_B |
| IBY_VALIDATION_VALUES.VALIDATION_SET_CODE | IBY_VALIDATION_SETS_B |
IBY_VALIDATION_SETS stores links to payment validations. These validations must be performed before submitting transactions to a payment system. Validations may be required for many reasons, including bank account restrictions or the countries, currencies, or payment systems involved in a transaction. Payment validations are currently implemented in code, rather than in metadata. Thus, each validation in this table should be accompanied by a pointer to the code in which the validation is implemented. Validations can be further defined by specifying the entity with which they are associated. This determines when the validation should take place. Payment method validations are done immediately when a calling application submits a payment process request to Oracle Payments, and in some cases earlier as well. Other validations are done later, after Oracle Payments assigns the appropriate entities, such as payment format, to the payment. This division is done in the IBY_VAL_ASSIGNMENTS table.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_VALIDATION_SETS_B_VSCID_U1 | UNIQUE | APPS_TS_TX_IDX |
VALIDATION_SET_CODE
ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| VALIDATION_SET_CODE | VARCHAR2 | (30) | Y | User entered primary key |
| PAYMENT_FLOW | VARCHAR2 | (30) | Lookup Type: IBY_PAYMENT_FLOW Lookup Values: DISBURSEMENTS, FUND_CAPTURE | |
| VALIDATION_LEVEL_CODE | VARCHAR2 | (30) | Y | Level at which this validation should apply. Values, from the IBY_VALIDATION_LEVELS lookup, include DOCUMENT, PAYMENT, and INSTRUCTION |
| VALIDATION_CODE_PACKAGE | VARCHAR2 | (255) | Y | Package where the validation is defined; in PL/SQL this corresponds to a package name, in Java a class name |
| VALIDATION_CODE_ENTRY_POINT | VARCHAR2 | (255) | Y | Entry point of the code that implements the validation set. For example, this could be in the form of a PL/SQL package and procedure, or a Java class and method. |
| VALIDATION_CODE_LANGUAGE | VARCHAR2 | (30) | Y | Language of the code that implements the validation set. Possible values are PLSQL and JAVA. |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_VALIDATION_SETS_B does not reference any database object
IBY.IBY_VALIDATION_SETS_B is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_VALIDATION_SETS_TL.VALIDATION_SET_CODE | % |
IBY_VALIDATION_SETS stores links to payment validations. These validations must be performed before submitting transactions to a payment system. Validations may be required for many reasons, including bank account restrictions or the countries, currencies, or payment systems involved in a transaction. Payment validations are currently implemented in code, rather than in metadata. Thus, each validation in this table should be accompanied by a pointer to the code in which the validation is implemented. Validations can be further defined by specifying the entity with which they are associated. This determines when the validation should take place. Payment method validations are done immediately when a calling application submits a payment process request to Oracle Payments, and in some cases earlier as well. Other validations are done later, after Oracle Payments assigns the appropriate entities, such as payment format, to the payment. This division is done in the IBY_VAL_ASSIGNMENTS table.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_VALIDATION_SETS_TL_U1 | UNIQUE | APPS_TS_TX_IDX |
LANGUAGE
VALIDATION_SET_CODE ZD_EDITION_NAME |
| IBY_VALIDATION_SETS_TL_VSID_N1 | NONUNIQUE | APPS_TS_TX_IDX | VALIDATION_SET_CODE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| VALIDATION_SET_CODE | VARCHAR2 | (30) | Y | User entered primary key |
| LANGUAGE | VARCHAR2 | (4) | Y | Language code |
| SOURCE_LANG | VARCHAR2 | (4) | Y | Language code of the record's current language |
| VALIDATION_SET_DISPLAY_NAME | VARCHAR2 | (100) | Y | Validation set name |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_VALIDATION_SETS_TL does not reference any database object
IBY.IBY_VALIDATION_SETS_TL is referenced by following:
| Description: | IBY_VALIDATION_VALUES stores the values for each validation parameter. For example, one validation controls the maximum amount that can be paid in a single payment instruction. The maximum amount parameter is stored in this table, and the a |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_VALIDATION_VALUES.VALIDATION_SET_CODE | IBY_VALIDATION_SETS_B |
| IBY_VALIDATION_VALUES.VALIDATION_ASSIGNMENT_ID | IBY_VAL_ASSIGNMENTS |
IBY_VALIDATION_VALUES stores the values for each validation parameter. For example, one validation controls the maximum amount that can be paid in a single payment instruction. The maximum amount parameter is stored in this table, and the actual value is stored in the associated table, IBY_VALIDATION_VALUES. This table corresponds to the Validations regions on the Payment Method and Format pages.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_VALIDATION_VALUES_U1 | UNIQUE | APPS_TS_TX_IDX |
VALIDATION_ASSIGNMENT_ID
VALIDATION_PARAMETER_CODE ZD_EDITION_NAME |
| IBY_VALIDATION_VALUES_N1 | NONUNIQUE | APPS_TS_TX_IDX | VALIDATION_SET_CODE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| VALIDATION_ASSIGNMENT_ID | NUMBER | (15) | Y | Validation assignment Identifier |
| VALIDATION_PARAMETER_CODE | VARCHAR2 | (100) | Y | Name or token of the parameter that uses this value |
| VALIDATION_SET_CODE | VARCHAR2 | (30) | Y | Validation set code |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Object version number |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| VAL_PARAM_VARCHAR2_VALUE | VARCHAR2 | (3000) | Value of the validation parameter if it is of type VARCHAR2 | |
| VAL_PARAM_NUMBER_VALUE | NUMBER | Value of the validation parameter if it is of type NUMBER | ||
| VAL_PARAM_DATE_VALUE | DATE | Value of the validation parameter if it is of type DATE | ||
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_VALIDATION_VALUES does not reference any database object
IBY.IBY_VALIDATION_VALUES is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_VAL_ASSIGNMENTS.VALIDATION_SET_CODE | % |
| IBY_VAL_ASSIGNMENTS.PAYMENT_METHOD_CODE | IBY_PAYMENT_METHODS_B |
| IBY_VAL_ASSIGNMENTS.TERRITORY_CODE | FND_TERRITORIES |
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_VALIDATION_VALUES.VALIDATION_ASSIGNMENT_ID | IBY_VAL_ASSIGNMENTS |
IBY_VAL_ASSIGNMENTS links validation sets to the appropriate validation entity. Through this table, individual validation sets are assigned to the payment method, payment format, or other entity that requires the validation encoded in that validation set. Payment method validation sets are those that should be evaluated as soon as possible once a transaction is assigned a payment method. Since each transaction is required to have a payment method assigned, these validations are evaluated immediately upon submission to Oracle Payments. All other types of validations are done offline, once the appropriate format or other entity has been assigned to the transaction. The determination of what type of entity a validation set should be associated with is based on the deploying company's business rules, the rules of the countries that have jurisdiction over the transaction, and ease-of-use. Typically, validations should be performed as early as possible, so users have immediate feedback and opportunity to modify invalid transactions.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_VAL_ASSIGNMENTS_VAID_U1 | UNIQUE | APPS_TS_TX_IDX |
VALIDATION_ASSIGNMENT_ID
ZD_EDITION_NAME |
| IBY_VAL_ASSIGNMENTS_N1 | NONUNIQUE | APPS_TS_TX_IDX |
VAL_ASSIGNMENT_ENTITY_TYPE
ASSIGNMENT_ENTITY_ID |
| IBY_VAL_ASSIGNMENTS_N2 | NONUNIQUE | APPS_TS_TX_IDX | PAYMENT_METHOD_CODE |
| IBY_VAL_ASSIGNMENTS_N3 | NONUNIQUE | APPS_TS_TX_IDX | TERRITORY_CODE |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| VALIDATION_ASSIGNMENT_ID | NUMBER | (15) | Y | System generated primary key |
| VALIDATION_SET_CODE | VARCHAR2 | (30) | Y | Validation set code |
| VAL_ASSIGNMENT_ENTITY_TYPE | VARCHAR2 | (30) | Y | Type of entity to which this validation is assigned. Values, from the lookup IBY_VALIDATION_ASSIGN_ENTITIES, include METHOD, FORMAT, BANK, TRANSPROTOCOL, and INTBANKACCOUNT |
| ASSIGNMENT_ENTITY_ID | VARCHAR2 | (30) | Y | Identifier of the appropriate entity, for example, payment method, payment format. |
| INACTIVE_DATE | DATE | Inactive date | ||
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. | |
| TERRITORY_CODE | VARCHAR2 | (2) | Country to which the validation is applicable | |
| PAYMENT_METHOD_CODE | VARCHAR2 | (30) | Payment method to which the validation is applicable | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_VAL_ASSIGNMENTS does not reference any database object
IBY.IBY_VAL_ASSIGNMENTS is referenced by following:
| Description: | Stores the combinations of EC app, payee and org id for a visibility class |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_VISBLTY_CLASS_DTLS.VISIBILITY_CLASS_ID | IBY_VISIBILITY_CLASSES |
IBY_VISBLTY_CLASS_DTLS is used to store the combinations of EC app, payee and org id for a visibility class.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_VISBLTY_CLASS_DTLS_ID_U1 | UNIQUE | APPS_TS_SEED |
VISBLTY_CLASS_DTL_ID
ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| VISBLTY_CLASS_DTL_ID | NUMBER | (15) | Y | System generated primary key |
| VISIBILITY_CLASS_ID | NUMBER | (15) | Y | Foreign key to parent visibility class |
| VIS_PAYEEID | VARCHAR2 | (80) | The payee for the visibility detial | |
| VIS_ECAPPID | NUMBER | (15) | The EC app for the visibility detial | |
| VIS_ORG_ID | NUMBER | (15) | The orgnization for the visibility detial | |
| VIS_ALL_PAYEE_FLAG | VARCHAR2 | (1) | Indicating if this visibility class details is for all payees. Value are 'Y', 'N', or null. If 'Y', the VIS_PAYEEID is ignored | |
| VIS_ALL_ECAPP_FLAG | VARCHAR2 | (1) | Indicating if this visibility class details is for all EC applications. Value are 'Y', 'N', or null. If 'Y', the VIS_ECAPPID is ignored | |
| VIS_ALL_ORG_FLAG | VARCHAR2 | (1) | Indicating if this visibility class details is for all organizations. Value are 'Y', 'N', or null. If 'Y', the VIS_ORG_ID is ignored | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | Application level record locking for three tier stateless applications | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| SECURITY_GROUP_ID | NUMBER | (15) | Used in hosted environments | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_VISBLTY_CLASS_DTLS does not reference any database object
IBY.IBY_VISBLTY_CLASS_DTLS is referenced by following:
| Description: | Stores the user privilege settings for viewing sensitive data in iPayment operations UI |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_VISBLTY_CLASS_DTLS.VISIBILITY_CLASS_ID | IBY_VISIBILITY_CLASSES |
IBY_VISIBILITY_CLASSES is used to store the user privilege settings for viewing sensitive data in iPayment operations UI. A visibility class essentially defines a token that can be assigned to a user or responsibility through the IBY: UI visibility class profile option. When iPayment UI is displayed the sensitive data will be masked according to the visibility class setting.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_VISIBILITY_CLASSES_ID_U1 | UNIQUE | APPS_TS_SEED |
VISIBILITY_CLASS_ID
ZD_EDITION_NAME |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| VISIBILITY_CLASS_ID | NUMBER | (15) | Y | System generated primary key |
| VISIBILITY_CLASS_NAME | VARCHAR2 | (80) | Y | Name of the visibility class |
| INSTR_NUMBER_MASK | VARCHAR2 | (30) | How to mask instrument numbers used for a transaction | |
| AMOUNT_MASK | VARCHAR2 | (30) | How the transaction amount is masked. Set to masked values for Payroll originated data | |
| BENEFICIARY_MASK | VARCHAR2 | (30) | How the beneficiary name is masked. Set to masked values for Payroll originated data | |
| START_DATE_ACTIVE | DATE | Date when the visibility class become active | ||
| END_DATE_ACTIVE | DATE | Date after which the visibility class will no longer be active | ||
| OBJECT_VERSION_NUMBER | NUMBER | Y | Application level record locking for three tier stateless applications | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| SECURITY_GROUP_ID | NUMBER | (15) | Used in hosted environments | |
| ZD_EDITION_NAME | VARCHAR2 | (30) | Y |
IBY.IBY_VISIBILITY_CLASSES does not reference any database object
IBY.IBY_VISIBILITY_CLASSES is referenced by following:
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ROW_ID | ROWID | (10) | ||
| PAYMENT_PROFILE_ID | NUMBER | (15) | Y | |
| PAYMENT_PROFILE_NAME | VARCHAR2 | (100) | Y | |
| SYSTEM_PROFILE_CODE | VARCHAR2 | (100) | Y | |
| CREATED_BY | NUMBER | (15) | Y | |
| CREATION_DATE | DATE | Y | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| LAST_UPDATE_DATE | DATE | Y | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| OBJECT_VERSION_NUMBER | NUMBER | Y | ||
| BEP_ACCOUNT_ID | NUMBER | (15) | ||
| SECURITY_CONFIGURATION_ID | NUMBER | (15) | ||
| TRANSMIT_CONFIGURATION_ID | NUMBER | (15) | ||
| RESET_VALUE_1 | NUMBER | (15) | ||
| LAST_USED_NUMBER_1 | NUMBER | (15) | ||
| RESET_REQUEST_1 | NUMBER | (15) | ||
| RESET_VALUE_2 | NUMBER | (15) | ||
| LAST_USED_NUMBER_2 | NUMBER | (15) | ||
| RESET_REQUEST_2 | NUMBER | (15) | ||
| RESET_VALUE_3 | NUMBER | (15) | ||
| LAST_USED_NUMBER_3 | NUMBER | (15) | ||
| RESET_REQUEST_3 | NUMBER | (15) | ||
| INACTIVE_DATE | DATE | |||
| ACK_SEC_CONFIG_ID | NUMBER | (15) | ||
| ACK_TRANSMIT_CONFIG_ID | NUMBER | (15) |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| SCORE_TYPE | VARCHAR2 | (30) | Y | |
| MEANING | VARCHAR2 | (80) | Y | |
| SEQ | NUMBER | (5) |
APPS.IBY_AVS_RSTYPES_V is not referenced by any database object
A public view which may be useful for custom reporting or other data requirements.
View used to work with registered bank accounts.
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| INSTRID | NUMBER | (15) | Y | ID that iPayment uses to identify a registered |
| BANKACCOUNTID | VARCHAR2 | (80) | Y | The bank account number of a registered bank account. |
| FINAME | VARCHAR2 | (80) | The name of the financial institution (bank) to which a bank account belongs. | |
| BRANCHID | VARCHAR2 | (60) | The ID or name of the bank branch at which the account holder does business. | |
| ACCTTYPE | VARCHAR2 | (30) | The type of bank account (e.g. savings, checking). | |
| INSTRBUF | VARCHAR2 | (240) | Description of registered bank account. | |
| INSTRNAME | VARCHAR2 | (80) | Mnemonic for a registered bank account. | |
| ACCOUNT_HOLDER_NAME | VARCHAR2 | (240) | Name of the bank account holder. | |
| BANKID | VARCHAR2 | (25) | Routing number of financial institution (bank). | |
| OWNERID | VARCHAR2 | (80) | Y | ID that iPayment uses to identify bank account holder. |
| OWNERTYPE | VARCHAR2 | (20) | Y | The type of the account holder (e.g. user). |
| CHECK_DIGITS | VARCHAR2 | (30) | Check digits for bank accounts that identify them separately from the bank account numbers |
APPS.IBY_BANKACCT_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| BANK_INSTRUCTION_CODE | VARCHAR2 | (30) | Y | |
| FORMAT_VALUE | VARCHAR2 | (80) | ||
| INACTIVE_DATE | DATE | |||
| TERRITORY_CODE | VARCHAR2 | (2) | ||
| CREATED_BY | NUMBER | (15) | Y | |
| CREATION_DATE | DATE | Y | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| LAST_UPDATE_DATE | DATE | Y | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| OBJECT_VERSION_NUMBER | NUMBER | Y | ||
| MEANING | VARCHAR2 | (80) | ||
| DESCRIPTION | VARCHAR2 | (240) | ||
| SEEDED_FLAG | VARCHAR2 | (1) |
A public view which may be useful for custom reporting or other data requirements.
IBY_BATCHES_ALL view allows a merchant or business to view Batch details.
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| MERCHBATCHID | VARCHAR2 | (80) | Y | Batch identifer |
| BATCHSTATUS | NUMBER | Status of the batch | ||
| PAYEENAME | VARCHAR2 | (80) | NAME is name of the Payee | |
| BATCHCLOSEDATE | DATE | close date of this batch. | ||
| BEPNAME | VARCHAR2 | (80) | Name of the Back end Payment system like Cybercash, Verifone etc | |
| VPSBATCHID | VARCHAR2 | (80) | VPSBatchID is the batchid from BEP | |
| NUMTRXNS | NUMBER | NUMTRXNS is number of transactions in this batch | ||
| BATCHSTATE | VARCHAR2 | (80) | It denotes state of the batch. Various batch states are: batch-accepted 0 batch-sent 1,batch-queued 2,batch-rejected 3,batch-processed 4 (not used currently) batch-error-at-cc 5,batch-not-found 6,batch-unknown 7. | |
| BATCHTOTAL | NUMBER | BATCHTOTAL is the total net for this batch | ||
| BATCHSALES | NUMBER | BATCHSALES is the total inflow | ||
| BATCHCREDIT | NUMBER | BATCHCREDIT is the total outflow and includes return and credit transaction amounts. | ||
| PAYMENTMETHODNAME | VARCHAR2 | (80) | Payment Method Name | |
| ORG_ID | NUMBER | (15) | Organization identifier |
APPS.IBY_BATCHES_ALL_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ROW_ID | ROWID | (10) | ||
| BEPID | NUMBER | (15) | Y | |
| ACCOUNT_OPTION_CODE | VARCHAR2 | (30) | Y | |
| ACCOUNT_OPTION_DATATYPE | VARCHAR2 | (30) | Y | |
| CREATED_BY | NUMBER | (15) | Y | |
| CREATION_DATE | DATE | Y | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| LAST_UPDATE_DATE | DATE | Y | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| OBJECT_VERSION_NUMBER | NUMBER | (15) | ||
| DISPLAY_ORDER | NUMBER | (15) | Y | |
| ACCOUNT_OPTION_NAME | VARCHAR2 | (100) | Y | |
| SECURED_FLAG | VARCHAR2 | (1) | Indicates if the option should be secured- i.e., is sensitive | |
| UNIQUE_PER_BATCH_FLAG | VARCHAR2 | (1) | Indicates if the option should unique per settlement batch file. |
APPS.IBY_BEP_ACCT_OPT_NAME_VL is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| CLEARED_CONTENT | XMLTYPE | (40) | ||
| REQUEST_ID | NUMBER | (15) | Y | |
| REQUEST_STATUS | VARCHAR2 | (30) | Y | |
| PAYMENT_ID | NUMBER | (15) | Y | |
| PAYMENT_STATUS | VARCHAR2 | (30) | Y | |
| INSTRUCTION_ID | NUMBER | (15) | Y | |
| INSTRUCTION_STATUS | VARCHAR2 | (30) | Y |
APPS.IBY_CLEARED_PMT_XML_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| COMPLETED_CONTENT | XMLTYPE | (40) | ||
| REQUEST_ID | NUMBER | (15) | Y | |
| REQUEST_STATUS | VARCHAR2 | (30) | Y | |
| PAYMENT_ID | NUMBER | (15) | Y | |
| PAYMENT_STATUS | VARCHAR2 | (30) | Y | |
| INSTRUCTION_ID | NUMBER | (15) | Y | |
| INSTRUCTION_STATUS | VARCHAR2 | (30) | Y |
APPS.IBY_COMPLETED_PMT_XML_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| SCORE_TYPE | VARCHAR2 | (30) | Y | |
| MEANING | VARCHAR2 | (80) | Y | |
| SEQ | NUMBER | (5) |
APPS.IBY_CRC_RSTYPES_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ROW_ID | ROWID | (10) | ||
| CARD_ISSUER_ACCEPTED_FLAG | VARCHAR2 | (1) | Y | |
| AUTHORIZATION_VALIDITY_PERIOD | NUMBER | (15) | ||
| DIGIT_CHECK_FLAG | VARCHAR2 | (1) | Y | |
| CREATED_BY | NUMBER | (15) | Y | |
| CREATION_DATE | DATE | Y | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| LAST_UPDATE_DATE | DATE | Y | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| OBJECT_VERSION_NUMBER | NUMBER | Y | ||
| CARD_ISSUER_CODE | VARCHAR2 | (30) | Y | |
| CARD_ISSUER_NAME | VARCHAR2 | (100) | Y | |
| DESCRIPTION | VARCHAR2 | (240) |
APPS.IBY_CREDITCARD_ISSUERS_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ROW_ID | ROWID | (10) | ||
| CREATED_BY | NUMBER | (15) | Y | |
| CREATION_DATE | DATE | Y | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| LAST_UPDATE_DATE | DATE | Y | ||
| OBJECT_VERSION_NUMBER | NUMBER | Y | ||
| CARD_ISSUER_CODE | VARCHAR2 | (30) | Y | |
| CARD_ISSUER_ACCEPTED_FLAG | VARCHAR2 | (1) | Y | |
| AUTHORIZATION_VALIDITY_PERIOD | NUMBER | (15) | ||
| DIGIT_CHECK_FLAG | VARCHAR2 | (1) | Y | |
| AUTH_REVERSAL_FLAG | VARCHAR2 | (1) | ||
| ALLOW_CAPTURE_EX_AUTH_FLAG | VARCHAR2 | (1) | ||
| CARD_ISSUER_NAME | VARCHAR2 | (100) | Y | |
| DESCRIPTION | VARCHAR2 | (240) |
A public view which may be useful for custom reporting or other data requirements.
View used to work with registered credit cards.
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| INSTRID | NUMBER | (15) | Y | ID that iPayment uses to identify a registered credit card. |
| CARD_OWNER_ID | NUMBER | (15) | Card Owner ID | |
| CCNUMBER | VARCHAR2 | (30) | Y | Credit card number. |
| CC_NUMBER_HASH1 | VARCHAR2 | (64) | Credit card number hash #1 | |
| CC_NUMBER_HASH2 | VARCHAR2 | (64) | Credit card number hash #2 | |
| EXPIRYDATE | DATE | Date after which the credit card expires. | ||
| FINAME | VARCHAR2 | (80) | The name of the financial institution (bank) that issued the card. | |
| ACCTTYPE | VARCHAR2 | (0) | Type of credit card account. | |
| CHNAME | VARCHAR2 | (80) | Card holder name. | |
| INSTRNAME | VARCHAR2 | (80) | Mnemonic for a registered credit card. | |
| OWNERTYPE | VARCHAR2 | (0) | The type of the account holder (e.g. user). | |
| OWNERID | VARCHAR2 | (0) | ID that iPayment uses to identify credit card holder. | |
| INSTRBUF | VARCHAR2 | (240) | Description of registered credit card. | |
| ENCRYPTED | VARCHAR2 | (1) | Indicates if the instrument is encrypted |
APPS.IBY_CREDITCARD_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ROW_ID | ROWID | (10) | ||
| DELIVERY_CHANNEL_CODE | VARCHAR2 | (30) | Y | |
| FORMAT_VALUE | VARCHAR2 | (80) | ||
| TERRITORY_CODE | VARCHAR2 | (2) | ||
| INACTIVE_DATE | DATE | |||
| CREATED_BY | NUMBER | (15) | Y | |
| CREATION_DATE | DATE | Y | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| LAST_UPDATE_DATE | DATE | Y | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| OBJECT_VERSION_NUMBER | NUMBER | Y | ||
| MEANING | VARCHAR2 | (80) | ||
| DESCRIPTION | VARCHAR2 | (240) | ||
| SEEDED_FLAG | VARCHAR2 | (1) |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAY_PROC_TRXN_TYPE_CODE | VARCHAR2 | (100) | Y | |
| CALLING_APP_ID | NUMBER | (15) | Y | |
| CALLING_APP_DOC_REF_NUMBER | VARCHAR2 | (100) | Y | |
| DOCUMENT_PAYABLE_ID | NUMBER | (15) | Y | |
| PAYMENT_FUNCTION | VARCHAR2 | (30) | Y | |
| PAYMENT_DATE | DATE | Y | ||
| DOCUMENT_DATE | DATE | Y | ||
| DOCUMENT_TYPE | VARCHAR2 | (30) | Y | |
| DOCUMENT_STATUS | VARCHAR2 | (30) | Y | |
| DOCUMENT_CURRENCY_CODE | VARCHAR2 | (10) | Y | |
| DOCUMENT_AMOUNT | NUMBER | Y | ||
| PAYMENT_CURRENCY_CODE | VARCHAR2 | (10) | Y | |
| PAYMENT_AMOUNT | NUMBER | Y | ||
| PAYMENT_SERVICE_REQUEST_ID | NUMBER | (15) | Y | |
| PAYMENT_METHOD_CODE | VARCHAR2 | (30) | Y | |
| STRAIGHT_THROUGH_FLAG | VARCHAR2 | (1) | Y | |
| EXCLUSIVE_PAYMENT_FLAG | VARCHAR2 | (1) | Y | |
| EXT_PAYEE_ID | NUMBER | (15) | Y | |
| PAYEE_PARTY_ID | NUMBER | (15) | Y | |
| LEGAL_ENTITY_ID | NUMBER | (15) | Y | |
| ORG_ID | NUMBER | (15) | Y | |
| CREATED_BY | NUMBER | (15) | Y | |
| CREATION_DATE | DATE | Y | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| LAST_UPDATE_DATE | DATE | Y | ||
| OBJECT_VERSION_NUMBER | NUMBER | Y | ||
| CALLING_APP_DOC_UNIQUE_REF1 | VARCHAR2 | (100) | Y | |
| CALLING_APP_DOC_UNIQUE_REF2 | VARCHAR2 | (100) | ||
| CALLING_APP_DOC_UNIQUE_REF3 | VARCHAR2 | (100) | ||
| CALLING_APP_DOC_UNIQUE_REF4 | VARCHAR2 | (100) | ||
| CALLING_APP_DOC_UNIQUE_REF5 | VARCHAR2 | (100) | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| PARTY_SITE_ID | NUMBER | (15) | ||
| SUPPLIER_SITE_ID | NUMBER | (15) | ||
| ORG_TYPE | VARCHAR2 | (30) | Y | |
| ANTICIPATED_VALUE_DATE | DATE | |||
| PO_NUMBER | VARCHAR2 | (255) | ||
| DOCUMENT_DESCRIPTION | VARCHAR2 | (255) | ||
| DOCUMENT_CURRENCY_TAX_AMOUNT | NUMBER | |||
| DOCUMENT_CURR_CHARGE_AMOUNT | NUMBER | |||
| AMOUNT_WITHHELD | NUMBER | |||
| PAYMENT_CURR_DISCOUNT_TAKEN | NUMBER | |||
| DISCOUNT_DATE | DATE | |||
| PAYMENT_DUE_DATE | DATE | |||
| PAYMENT_PROFILE_ID | NUMBER | (15) | ||
| PAYMENT_ID | NUMBER | (15) | ||
| FORMATTING_PAYMENT_ID | NUMBER | (15) | ||
| INTERNAL_BANK_ACCOUNT_ID | NUMBER | (15) | ||
| EXTERNAL_BANK_ACCOUNT_ID | NUMBER | (15) | ||
| BANK_CHARGE_BEARER | VARCHAR2 | (30) | ||
| INTEREST_RATE | NUMBER | |||
| PAYMENT_GROUPING_NUMBER | NUMBER | (15) | ||
| PAYMENT_REASON_CODE | VARCHAR2 | (30) | ||
| PAYMENT_REASON_COMMENTS | VARCHAR2 | (240) | ||
| SETTLEMENT_PRIORITY | VARCHAR2 | (30) | ||
| REMITTANCE_MESSAGE1 | VARCHAR2 | (150) | ||
| REMITTANCE_MESSAGE2 | VARCHAR2 | (150) | ||
| REMITTANCE_MESSAGE3 | VARCHAR2 | (150) | ||
| UNIQUE_REMITTANCE_IDENTIFIER | VARCHAR2 | (30) | ||
| URI_CHECK_DIGIT | VARCHAR2 | (2) | ||
| DELIVERY_CHANNEL_CODE | VARCHAR2 | (30) | ||
| PAYMENT_FORMAT_CODE | VARCHAR2 | (30) | ||
| DOCUMENT_SEQUENCE_ID | NUMBER | |||
| DOCUMENT_SEQUENCE_VALUE | NUMBER | |||
| DOCUMENT_CATEGORY_CODE | VARCHAR2 | (30) | ||
| BANK_ASSIGNED_REF_CODE | VARCHAR2 | (30) | ||
| REMIT_TO_LOCATION_ID | NUMBER | (15) | ||
| ALLOW_REMOVING_DOCUMENT_FLAG | VARCHAR2 | (1) | Y | |
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | ||
| ATTRIBUTE1 | VARCHAR2 | (150) | ||
| ATTRIBUTE2 | VARCHAR2 | (150) | ||
| ATTRIBUTE3 | VARCHAR2 | (150) | ||
| ATTRIBUTE4 | VARCHAR2 | (150) | ||
| ATTRIBUTE5 | VARCHAR2 | (150) | ||
| ATTRIBUTE6 | VARCHAR2 | (150) | ||
| ATTRIBUTE7 | VARCHAR2 | (150) | ||
| ATTRIBUTE8 | VARCHAR2 | (150) | ||
| ATTRIBUTE9 | VARCHAR2 | (150) | ||
| ATTRIBUTE10 | VARCHAR2 | (150) | ||
| ATTRIBUTE11 | VARCHAR2 | (150) | ||
| ATTRIBUTE12 | VARCHAR2 | (150) | ||
| ATTRIBUTE13 | VARCHAR2 | (150) | ||
| ATTRIBUTE14 | VARCHAR2 | (150) | ||
| ATTRIBUTE15 | VARCHAR2 | (150) | ||
| COMPLETED_PMTS_GROUP_ID | NUMBER | (15) | ||
| REJECTED_DOCS_GROUP_ID | NUMBER | (15) |
APPS.IBY_DOCS_PAYABLE_SEC_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ECAPPID | NUMBER | |||
| APPLICATION_SHORT_NAME | VARCHAR2 | (50) | ||
| NAME | VARCHAR2 | (240) |
APPS.IBY_ECAPP_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| EXT_PAYEE_ID | NUMBER | (15) | Y | |
| PAYEE_PARTY_ID | NUMBER | (15) | Y | |
| PAYMENT_FUNCTION | VARCHAR2 | (30) | Y | |
| PARTY_SITE_ID | NUMBER | (15) | ||
| SUPPLIER_SITE_ID | NUMBER | (15) | ||
| ORG_ID | NUMBER | (15) | ||
| ORG_TYPE | VARCHAR2 | (30) | ||
| EXCLUSIVE_PAYMENT_FLAG | VARCHAR2 | (1) | Y | |
| DEFAULT_PAYMENT_METHOD_CODE | VARCHAR2 | (30) | ||
| ECE_TP_LOCATION_CODE | VARCHAR2 | (60) | ||
| BANK_CHARGE_BEARER | VARCHAR2 | (30) | ||
| BANK_INSTRUCTION1_CODE | VARCHAR2 | (30) | ||
| BANK_INSTRUCTION2_CODE | VARCHAR2 | (30) | ||
| BANK_INSTRUCTION_DETAILS | VARCHAR2 | (255) | ||
| PAYMENT_REASON_CODE | VARCHAR2 | (30) | ||
| PAYMENT_REASON_COMMENTS | VARCHAR2 | (240) | ||
| INACTIVE_DATE | DATE | |||
| PAYMENT_TEXT_MESSAGE1 | VARCHAR2 | (256) | ||
| PAYMENT_TEXT_MESSAGE2 | VARCHAR2 | (150) | ||
| PAYMENT_TEXT_MESSAGE3 | VARCHAR2 | (150) | ||
| DELIVERY_CHANNEL_CODE | VARCHAR2 | (30) | ||
| PAYMENT_FORMAT_CODE | VARCHAR2 | (30) | ||
| SETTLEMENT_PRIORITY | VARCHAR2 | (30) |
APPS.IBY_EXTERNAL_PAYEES_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ROW_ID | ROWID | (10) | ||
| DATASOURCE_CODE | VARCHAR2 | (80) | Y | |
| GEN_CODE_LANGUAGE | VARCHAR2 | (30) | Y | |
| GEN_CODE_PACKAGE | VARCHAR2 | (255) | Y | |
| GEN_CODE_ENTRY_POINT | VARCHAR2 | (255) | Y | |
| EXTRACT_ID | NUMBER | (15) | Y | |
| EXTRACT_CODE | VARCHAR2 | (30) | Y | |
| EXTRACT_VERSION | NUMBER | (15) | Y | |
| CREATED_BY | NUMBER | (15) | Y | |
| CREATION_DATE | DATE | Y | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| LAST_UPDATE_DATE | DATE | Y | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | |
| EXTRACT_DESC | VARCHAR2 | (200) |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| BANK_PARTY_ID | NUMBER | (15) | Y | |
| HOME_COUNTRY | VARCHAR2 | (2) | ||
| BANK_NAME | VARCHAR2 | (360) | Y | |
| BANK_NUMBER | VARCHAR2 | (30) | ||
| BANK_INSTITUTION_TYPE | VARCHAR2 | (30) | Y | |
| BANK_NAME_ALT | VARCHAR2 | (320) | ||
| SHORT_BANK_NAME | VARCHAR2 | (240) | ||
| DESCRIPTION | VARCHAR2 | (2000) | ||
| END_DATE | DATE | |||
| ADDRESS1 | VARCHAR2 | (240) | ||
| ADDRESS2 | VARCHAR2 | (240) | ||
| ADDRESS3 | VARCHAR2 | (240) | ||
| CITY | VARCHAR2 | (60) | ||
| STATE | VARCHAR2 | (60) | ||
| POSTAL_CODE | VARCHAR2 | (60) | ||
| COUNTRY | VARCHAR2 | (60) | ||
| CREATED_BY | NUMBER | |||
| CREATION_DATE | DATE | |||
| LAST_UPDATED_BY | NUMBER | |||
| LAST_UPDATE_DATE | DATE | |||
| LAST_UPDATE_LOGIN | NUMBER | |||
| OBJECT_VERSION_NUMBER | NUMBER | |||
| OPERATION_FLAG | CHAR | (1) | ||
| SITE_LOCATION_ID | NUMBER | (15) | ||
| TAX_PAYER_ID | VARCHAR2 | (20) |
APPS.IBY_EXT_BANKS_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ROW_ID | ROWID | (10) | ||
| EXT_BANK_ACCOUNT_ID | NUMBER | (15) | Y | |
| BANK_PARTY_ID | NUMBER | (15) | ||
| COUNTRY_CODE | VARCHAR2 | (2) | ||
| BANK_NAME | VARCHAR2 | (360) | ||
| BANK_NUMBER | VARCHAR2 | (30) | ||
| BRANCH_PARTY_ID | NUMBER | (15) | ||
| BANK_BRANCH_NAME | VARCHAR2 | (360) | ||
| BRANCH_NUMBER | VARCHAR2 | (30) | ||
| BRANCH_TYPE | VARCHAR2 | (30) | ||
| BANK_BRANCH_ADDRESS_ID | NUMBER | (15) | ||
| EFT_SWIFT_CODE | VARCHAR2 | (30) | ||
| BANK_ACCOUNT_ID | NUMBER | (15) | Y | |
| BANK_ACCOUNT_NAME | VARCHAR2 | (80) | ||
| BANK_ACCOUNT_NUMBER | VARCHAR2 | (100) | ||
| BANK_ACCT_NUM_HASH1 | VARCHAR2 | (64) | ||
| BANK_ACCT_NUM_HASH2 | VARCHAR2 | (64) | ||
| CURRENCY_CODE | VARCHAR2 | (15) | ||
| DESCRIPTION | VARCHAR2 | (240) | ||
| CHECK_DIGITS | VARCHAR2 | (30) | ||
| MULTI_CURRENCY_ALLOWED_FLAG | VARCHAR2 | (1) | ||
| ALTERNATE_ACCOUNT_NAME | VARCHAR2 | (320) | ||
| SHORT_ACCT_NAME | VARCHAR2 | (30) | ||
| ACCOUNT_SUFFIX | VARCHAR2 | (30) | ||
| IBAN_NUMBER | VARCHAR2 | (50) | ||
| IBAN_NUMBER_HASH1 | VARCHAR2 | (64) | ||
| IBAN_NUMBER_HASH2 | VARCHAR2 | (64) | ||
| PRIMARY_ACCT_OWNER_PARTY_ID | NUMBER | (15) | ||
| PRIMARY_ACCT_OWNER_NAME | VARCHAR2 | (360) | ||
| ACCOUNT_CLASSIFICATION | VARCHAR2 | (30) | ||
| BANK_ACCOUNT_TYPE | VARCHAR2 | (25) | ||
| AGENCY_LOCATION_CODE | VARCHAR2 | (30) | ||
| START_DATE | DATE | |||
| END_DATE | DATE | |||
| PAYMENT_FACTOR_FLAG | VARCHAR2 | (1) | ||
| FOREIGN_PAYMENT_USE_FLAG | VARCHAR2 | (1) | ||
| EXCHANGE_RATE_AGREEMENT_NUM | VARCHAR2 | (80) | ||
| EXCHANGE_RATE_AGREEMENT_TYPE | VARCHAR2 | (80) | ||
| EXCHANGE_RATE | NUMBER | |||
| HEDGING_CONTRACT_REFERENCE | VARCHAR2 | (20) | ||
| SECONDARY_ACCOUNT_REFERENCE | VARCHAR2 | (30) | ||
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | ||
| ATTRIBUTE1 | VARCHAR2 | (150) | ||
| ATTRIBUTE2 | VARCHAR2 | (150) | ||
| ATTRIBUTE3 | VARCHAR2 | (150) | ||
| ATTRIBUTE4 | VARCHAR2 | (150) | ||
| ATTRIBUTE5 | VARCHAR2 | (150) | ||
| ATTRIBUTE6 | VARCHAR2 | (150) | ||
| ATTRIBUTE7 | VARCHAR2 | (150) | ||
| ATTRIBUTE8 | VARCHAR2 | (150) | ||
| ATTRIBUTE9 | VARCHAR2 | (150) | ||
| ATTRIBUTE10 | VARCHAR2 | (150) | ||
| ATTRIBUTE11 | VARCHAR2 | (150) | ||
| ATTRIBUTE12 | VARCHAR2 | (150) | ||
| ATTRIBUTE13 | VARCHAR2 | (150) | ||
| ATTRIBUTE14 | VARCHAR2 | (150) | ||
| ATTRIBUTE15 | VARCHAR2 | (150) | ||
| OBJECT_VERSION_NUMBER | NUMBER | Y | ||
| BANK_ACCOUNT_NUM_ELECTRONIC | VARCHAR2 | (100) | ||
| BANK_CODE | VARCHAR2 | (30) | ||
| ENCRYPTED | VARCHAR2 | (1) | Y |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| BRANCH_PARTY_ID | NUMBER | (15) | Y | |
| HOME_COUNTRY | VARCHAR2 | (60) | ||
| BANK_BRANCH_NAME | VARCHAR2 | (360) | Y | |
| BANK_BRANCH_NAME_ALT | VARCHAR2 | (320) | ||
| BRANCH_NUMBER | VARCHAR2 | (30) | ||
| START_DATE | DATE | Y | ||
| END_DATE | DATE | |||
| ADDRESS_LINE1 | VARCHAR2 | (240) | ||
| ADDRESS_LINE2 | VARCHAR2 | (240) | ||
| ADDRESS_LINE3 | VARCHAR2 | (240) | ||
| ADDRESS_LINE4 | VARCHAR2 | (240) | ||
| CITY | VARCHAR2 | (60) | ||
| STATE | VARCHAR2 | (60) | ||
| PROVINCE | VARCHAR2 | (60) | ||
| ZIP | VARCHAR2 | (60) | ||
| COUNTRY | VARCHAR2 | (60) | ||
| BANK_BRANCH_TYPE | VARCHAR2 | (30) | ||
| DESCRIPTION | VARCHAR2 | (2000) | ||
| EFT_SWIFT_CODE | VARCHAR2 | (30) | ||
| EFT_USER_NUMBER | VARCHAR2 | (30) | ||
| BANK_PARTY_ID | NUMBER | (15) | Y | |
| CREATED_BY | NUMBER | |||
| CREATION_DATE | DATE | |||
| LAST_UPDATED_BY | NUMBER | |||
| LAST_UPDATE_DATE | DATE | |||
| LAST_UPDATE_LOGIN | NUMBER | |||
| OBJECT_VERSION_NUMBER | NUMBER | |||
| OPERATION_FLAG | CHAR | (1) |
APPS.IBY_EXT_BANK_BRANCHES_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| TRXNMID | NUMBER | Y | ||
| PARTY_ID | NUMBER | (15) | ||
| PARTY_NUMBER | VARCHAR2 | (30) | ||
| PARTY_NAME | VARCHAR2 | (360) | ||
| PARTY_TYPE | VARCHAR2 | (30) | ||
| ALTERNATIVE_NAME | VARCHAR2 | (320) | ||
| CUST_ACCOUNT_ID | NUMBER | (15) | ||
| ACCOUNT_NUMBER | VARCHAR2 | (30) | ||
| ORG_ID | NUMBER | (15) | ||
| OPERATING_UNIT | VARCHAR2 | (240) | ||
| CUST_ACCT_SITE_ID | NUMBER | (15) | ||
| ACCOUNT_SITE_USE_ID | NUMBER | (15) | ||
| LOCATION | VARCHAR2 | (40) | ||
| BILL_TO_ADDRESS_ID | NUMBER | (15) | ||
| TAX_REGISTRATION_NUMBER | VARCHAR2 | (4000) | ||
| LE_REGISTRATION_NUMBER | VARCHAR2 | (20) | ||
| PARTY_ATTR_CAT | VARCHAR2 | (30) |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYMENT_ID | NUMBER | (15) | ||
| DOCUMENT_PAYABLE_ID | NUMBER | (15) | ||
| PAYMENT_SERVICE_REQUEST_ID | NUMBER | (15) | ||
| CALLING_APP_DOC_UNIQUE_REF1 | VARCHAR2 | (100) | ||
| CALLING_APP_DOC_UNIQUE_REF2 | VARCHAR2 | (100) | ||
| CALLING_APP_DOC_UNIQUE_REF3 | VARCHAR2 | (100) | ||
| CALLING_APP_DOC_UNIQUE_REF4 | VARCHAR2 | (100) | ||
| CALLING_APP_DOC_UNIQUE_REF5 | VARCHAR2 | (100) | ||
| CALLING_APP_ID | NUMBER | (15) | ||
| PAY_PROC_TRXN_TYPE_CODE | VARCHAR2 | (100) | ||
| CALLING_APP_DOCUMENT_UNIQUE_ID | VARCHAR2 | (100) | ||
| CALLING_APP_DOC_REF_NUMBER | VARCHAR2 | (100) | ||
| BANK_ASSIGNED_REF_CODE | VARCHAR2 | (4000) | ||
| UNIQUE_REMITTANCE_IDENTIFIER | VARCHAR2 | (30) | ||
| URI_CHECK_DIGIT | VARCHAR2 | (2) | ||
| DOC_CATEGORY | VARCHAR2 | (30) | ||
| DOC_SEQUENCE_NAME | VARCHAR2 | (30) | ||
| DOC_SEQUENCE_VALUE | NUMBER | |||
| PO_NUMBER | VARCHAR2 | (255) | ||
| DOCUMENT_STATUS | VARCHAR2 | (30) | ||
| DOCUMENT_STATUS_MEANING | VARCHAR2 | (80) | ||
| DOCUMENT_DATE | DATE | |||
| DOCUMENT_CREATION_DATE | DATE | |||
| PAYMENT_DUE_DATE | DATE | |||
| DOCUMENT_TYPE | VARCHAR2 | (30) | ||
| DOCUMENT_TYPE_MEANING | VARCHAR2 | (80) | ||
| DOCUMENT_DESCRIPTION | VARCHAR2 | (255) | ||
| DOCUMENT_AMOUNT | NUMBER | |||
| DOCUMENT_CURRENCY_CODE | VARCHAR2 | (10) | ||
| PAYMENT_AMOUNT | NUMBER | |||
| PAYMENT_CURRENCY_CODE | VARCHAR2 | (10) | ||
| DISCOUNT_DATE | DATE | |||
| PAYMENT_CURR_DISCOUNT_TAKEN | NUMBER | |||
| DOCUMENT_CURR_CHARGE_AMOUNT | NUMBER | |||
| INTEREST_RATE | NUMBER | |||
| BANK_CHARGE_BEARER | VARCHAR2 | (30) | ||
| BANK_CHARGE_BEARER_MEANING | VARCHAR2 | (80) | ||
| EXCLUSIVE_PAYMENT_FLAG | VARCHAR2 | (1) | ||
| DELIVERY_CHANNEL_CODE | VARCHAR2 | (30) | ||
| DELIVERY_CHANNEL_MEANING | VARCHAR2 | (80) | ||
| DELIVERY_CHANNEL_FORMAT_VALUE | VARCHAR2 | (80) | ||
| SETTLEMENT_PRIORITY | VARCHAR2 | (30) | ||
| SETTLEMENT_PRIORITY_MEANING | VARCHAR2 | (80) | ||
| AMOUNT_WITHHELD | NUMBER | |||
| PAYMENT_REASON_CODE | VARCHAR2 | (30) | ||
| PAYMENT_REASON_MEANING | VARCHAR2 | (80) | ||
| PAYMENT_REASON_FORMAT_VALUE | VARCHAR2 | (80) | ||
| PAYMENT_REASON_COMMENTS | VARCHAR2 | (240) | ||
| REMITTANCE_MESSAGE1 | VARCHAR2 | (150) | ||
| REMITTANCE_MESSAGE2 | VARCHAR2 | (150) | ||
| REMITTANCE_MESSAGE3 | VARCHAR2 | (150) | ||
| DOC_PAYABLE_ATTR_CAT | VARCHAR2 | (150) | ||
| FORMATTING_PAYMENT_ID | NUMBER | (15) | ||
| EMPLOYEE_PAYMENT_FLAG | VARCHAR2 | (1) | ||
| BORDERO_INT_AMT | NUMBER | |||
| BORDERO_ABATEMENT | NUMBER | |||
| DOCUMENT_CURRENCY_TAX_AMOUNT | NUMBER | |||
| EXPENSE_RPT_CC_NUM | VARCHAR2 | (4000) | ||
| GLOBAL_ATTRIBUTE_CATEGORY | VARCHAR2 | (240) | ||
| GLOBAL_ATTRIBUTE1 | VARCHAR2 | (240) | ||
| GLOBAL_ATTRIBUTE2 | VARCHAR2 | (240) | ||
| GLOBAL_ATTRIBUTE3 | VARCHAR2 | (240) | ||
| GLOBAL_ATTRIBUTE4 | VARCHAR2 | (240) | ||
| GLOBAL_ATTRIBUTE5 | VARCHAR2 | (240) | ||
| GLOBAL_ATTRIBUTE6 | VARCHAR2 | (240) | ||
| GLOBAL_ATTRIBUTE7 | VARCHAR2 | (240) | ||
| GLOBAL_ATTRIBUTE8 | VARCHAR2 | (240) | ||
| GLOBAL_ATTRIBUTE9 | VARCHAR2 | (240) | ||
| GLOBAL_ATTRIBUTE10 | VARCHAR2 | (240) | ||
| GLOBAL_ATTRIBUTE11 | VARCHAR2 | (240) | ||
| GLOBAL_ATTRIBUTE12 | VARCHAR2 | (240) | ||
| GLOBAL_ATTRIBUTE13 | VARCHAR2 | (240) | ||
| GLOBAL_ATTRIBUTE14 | VARCHAR2 | (240) | ||
| GLOBAL_ATTRIBUTE15 | VARCHAR2 | (240) | ||
| GLOBAL_ATTRIBUTE16 | VARCHAR2 | (240) | ||
| GLOBAL_ATTRIBUTE17 | VARCHAR2 | (240) | ||
| GLOBAL_ATTRIBUTE18 | VARCHAR2 | (240) | ||
| GLOBAL_ATTRIBUTE19 | VARCHAR2 | (240) | ||
| GLOBAL_ATTRIBUTE20 | VARCHAR2 | (240) | ||
| DOC_PAYER_LE_NAME | VARCHAR2 | (240) | ||
| DOC_PAYER_LE_REG_NUM | VARCHAR2 | (30) | ||
| DOC_PAYER_TAX_REG_NUM | VARCHAR2 | (4000) |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| DOCUMENT_PAYABLE_ID | NUMBER | (15) | Y | |
| TRANSACTION_ERROR_ID | NUMBER | (15) | Y | |
| ERROR_TYPE | VARCHAR2 | (30) | ||
| ERROR_TYPE_MEANING | VARCHAR2 | (80) | QuickCode meaning | |
| ERROR_CODE | VARCHAR2 | (30) | Y | |
| ERROR_MESSAGE | VARCHAR2 | (255) | ||
| ERROR_DATE | DATE | Y | ||
| ERROR_STATUS | VARCHAR2 | (30) | Y | |
| ERROR_STATUS_MEANING | VARCHAR2 | (80) | QuickCode meaning |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYMENT_INSTRUCTION_ID | NUMBER | (15) | Y | |
| INSTRUCTION_CREATED_DATE | DATE | Y | ||
| PAYMENT_INSTRUCTION_STATUS | VARCHAR2 | (30) | Y | |
| INSTRUCTION_STATUS_MEANING | VARCHAR2 | (80) | Y | QuickCode meaning |
| PROCESSING_TYPE | VARCHAR2 | (30) | Y | |
| PAY_ADMIN_ASSIGNED_REF_CODE | VARCHAR2 | (255) | ||
| BANK_ASSIGNED_REF_CODE | VARCHAR2 | (30) | ||
| PERIODIC_SEQUENCE_NAME_1 | VARCHAR2 | (80) | ||
| LAST_USED_NUMBER_1 | NUMBER | (15) | ||
| PERIODIC_SEQUENCE_NAME_2 | VARCHAR2 | (80) | ||
| LAST_USED_NUMBER_2 | NUMBER | (15) | ||
| PERIODIC_SEQUENCE_NAME_3 | VARCHAR2 | (80) | ||
| LAST_USED_NUMBER_3 | NUMBER | (15) | ||
| BANK_INSTRUCTION1_CODE | VARCHAR2 | (30) | ||
| BANK_INSTRUCTION1_MEANING | VARCHAR2 | (80) | ||
| BANK_INSTRUCTION1_FORMAT_VALUE | VARCHAR2 | (80) | ||
| BANK_INSTRUCTION2_CODE | VARCHAR2 | (30) | ||
| BANK_INSTRUCTION2_MEANING | VARCHAR2 | (80) | ||
| BANK_INSTRUCTION2_FORMAT_VALUE | VARCHAR2 | (80) | ||
| BANK_INSTRUCTION_DETAILS | VARCHAR2 | (255) | ||
| PAYMENT_TEXT_MESSAGE1 | VARCHAR2 | (150) | ||
| PAYMENT_TEXT_MESSAGE2 | VARCHAR2 | (150) | ||
| DECLARATION_OPTION | VARCHAR2 | (30) | ||
| BEP_ACCOUNT_NAME | VARCHAR2 | (80) | ||
| BEP_ACCOUNT_ID | NUMBER | (15) | ||
| PAYSYS_ACCT_ATTR_CAT | VARCHAR2 | (150) | ||
| COMMENTS | VARCHAR2 | (240) | ||
| PI_ATTR_CAT | VARCHAR2 | (150) | ||
| PAYMENT_PROFILE_ID | NUMBER | (15) | ||
| SYSTEM_PROFILE_CODE | VARCHAR2 | (100) | Y | |
| PAYMENT_PROFILE_NAME | VARCHAR2 | (100) | ||
| LOGICAL_GROUPING_MODE | VARCHAR2 | (50) | Specifies the grouping mode of the payment process profile | |
| BATCH_BOOKING_FLAG | VARCHAR2 | (1) | Specifies whether the bank will send statement based on payment/group | |
| PAYMENT_PROFILE_ATTR_CAT | VARCHAR2 | (150) | ||
| PAYMENT_FORMAT_CODE | VARCHAR2 | (30) | Y | |
| PAYMENT_FORMAT_NAME | VARCHAR2 | (300) | Y | |
| PAYMENT_FORMAT_ATTR_CAT | VARCHAR2 | (150) | ||
| PAYER_INSTRUMENT_COUNT | NUMBER | |||
| PAYMENT_COUNT | NUMBER | (15) | Y | |
| PAYMENT_DATE | DATE | |||
| PAYMENT_CURRENCY_CODE | VARCHAR2 | (10) | ||
| PAYMENT_SERVICE_REQUEST_ID | NUMBER | (15) | ||
| ORG_ID | NUMBER | (15) | ||
| ORG_TYPE | VARCHAR2 | (30) | ||
| ORG_TYPE_MEANING | VARCHAR2 | (80) | ||
| ORG_NAME | VARCHAR2 | (240) | ||
| PAYMENT_REASON_CODE | VARCHAR2 | (30) | ||
| PAY_REASON_MEANING | VARCHAR2 | (80) | ||
| PAY_REASON_FORMAT_VALUE | VARCHAR2 | (80) | ||
| PAYMENT_REASON_COMMENTS | VARCHAR2 | (240) | ||
| GROUP_BY_PAYMENT_DATE | VARCHAR2 | (1) | ||
| GROUP_BY_PAYMENT_CURRENCY | VARCHAR2 | (1) | ||
| GROUP_BY_PAY_SERVICE_REQUEST | VARCHAR2 | (1) | ||
| GROUP_BY_LEGAL_ENTITY | VARCHAR2 | (1) | ||
| GROUP_BY_ORGANIZATION | VARCHAR2 | (1) | ||
| GROUP_BY_PAYMENT_REASON | VARCHAR2 | (1) | ||
| LEGAL_ENTITY_ID | NUMBER | (15) | ||
| GROUP_BY_INTERNAL_BANK_ACCOUNT | VARCHAR2 | (1) | ||
| GROUP_BY_PAYMENT_FUNCTION | VARCHAR2 | (1) | ||
| GROUP_BY_RFC | VARCHAR2 | (1) | ||
| GROUP_BY_PAYMENT_METHOD | VARCHAR2 | (1) | Specifies whether payments must be grouped by payment method to form instruction | |
| INTERNAL_BANK_ACCOUNT_ID | NUMBER | (15) | ||
| PAYMENT_FUNCTION | VARCHAR2 | (30) | ||
| PAYMENT_FUNCTION_MEANING | VARCHAR2 | (80) | ||
| RFC_IDENTIFIER | VARCHAR2 | (30) | ||
| PAYMENT_METHOD_CODE | VARCHAR2 | (50) | Code of the payment method of the payment instruction | |
| PROCESS_TYPE | VARCHAR2 | (30) | Y | |
| TOTAL_PMT_AMOUNT | NUMBER | |||
| MOAC_DATA_BLOCKED_FLAG | VARCHAR2 | (1) | ||
| PAYMENT_DOCUMENT_NAME | VARCHAR2 | (100) | ||
| PAPER_STOCK_TYPE | VARCHAR2 | (30) | ||
| PAPER_STOCK_TYPE_MEANING | VARCHAR2 | (80) | ||
| CARD_ISSUER_FILE_SEQ_NO | NUMBER |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYMENT_ID | NUMBER | (15) | Y | |
| PARTY_ID | NUMBER | (15) | Y | |
| VENDOR_ID | NUMBER | |||
| VENDOR_SITE_ID | NUMBER | (15) | ||
| SUPPLIER_NUMBER | VARCHAR2 | (30) | ||
| PARTY_NUMBER | VARCHAR2 | (30) | Y | |
| PARTY_NAME | VARCHAR2 | (360) | Y | |
| ALTERNATE_NAME | VARCHAR2 | (320) | ||
| SITE_NAME | VARCHAR2 | (240) | ||
| ALTERNATE_SITE_NAME | VARCHAR2 | (320) | ||
| PARTY_TYPE | VARCHAR2 | (30) | Y | |
| PARTY_TYPE_MEANING | VARCHAR2 | (80) | Y | |
| TAX_REGISTRATION_NUMBER | VARCHAR2 | (4000) | ||
| LE_REGISTRATION_NUMBER | VARCHAR2 | (4000) | ||
| PARTY_ATTR_CAT | VARCHAR2 | (30) | ||
| PAYMENT_LOCATION_ID | NUMBER | (15) | ||
| CUSTOMER_NUM | VARCHAR2 | (25) | ||
| PARTY_SITE_ID | NUMBER | (15) |
APPS.IBY_EXT_FD_PAYEE_1_0_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PARTY_ID | NUMBER | (15) | Y | |
| PARTY_NUMBER | VARCHAR2 | (30) | Y | |
| PARTY_NAME | VARCHAR2 | (360) | Y | |
| PARTY_TYPE | VARCHAR2 | (30) | Y | |
| PARTY_TYPE_MEANING | VARCHAR2 | (80) | Y | |
| TAX_REGISTRATION_NUMBER | VARCHAR2 | (4000) | ||
| LE_REGISTRATION_NUMBER | VARCHAR2 | (30) | Y | |
| PARTY_ATTR_CAT | VARCHAR2 | (30) | ||
| LEGAL_ENTITY_ID | NUMBER | (15) | Y | |
| LEGAL_ENTITY_NAME | VARCHAR2 | (240) | Y | |
| LE_LOCATION_ID | NUMBER | (15) | ||
| LE_ATTR_CAT | VARCHAR2 | (30) |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYMENT_INSTRUCTION_ID | NUMBER | (15) | ||
| PAYMENT_ID | NUMBER | (15) | ||
| INTERNAL_BANK_ACCOUNT_ID | NUMBER | (15) | ||
| LEGAL_ENTITY_ID | NUMBER | (15) | ||
| CALLING_APP_ID | NUMBER | |||
| APPLICATION_NAME | VARCHAR2 | (50) | ||
| PAYMENT_SERVICE_REQUEST_ID | NUMBER | (15) | ||
| PAYMENT_FUNCTION | VARCHAR2 | (30) | ||
| PAYMENT_FUNCTION_MEANING | VARCHAR2 | (80) | ||
| PAYMENT_ORG_ID | NUMBER | (15) | ||
| PAYMENT_ORG_TYPE | VARCHAR2 | (30) | ||
| PAYMENT_ORG_TYPE_MEANING | VARCHAR2 | (80) | ||
| PAYMENT_ORG_NAME | VARCHAR2 | (240) | ||
| PAYMENT_DOC_CATEGORY | VARCHAR2 | (30) | ||
| PAYMENT_DOC_SEQUENCE_NAME | VARCHAR2 | (30) | ||
| PAYMENT_DOC_SEQUENCE_VALUE | NUMBER | |||
| PAYMENT_REFERENCE_NUMBER | NUMBER | (15) | ||
| PAPER_DOCUMENT_NUMBER | NUMBER | (15) | ||
| PAYMENT_DATE | DATE | |||
| PAYMENT_DUE_DATE | DATE | |||
| MATURITY_DATE | DATE | |||
| PAYMENT_STATUS | VARCHAR2 | (30) | ||
| PAYMENT_STATUS_MEANING | VARCHAR2 | (80) | ||
| PAYEE_PARTY_ID | NUMBER | (15) | ||
| PAYEE_PARTY_SITE_USE_ID | NUMBER | (15) | ||
| EXTERNAL_BANK_ACCOUNT_ID | NUMBER | (15) | ||
| PAYMENT_AMOUNT | NUMBER | |||
| PAYMENT_CURRENCY_CODE | VARCHAR2 | (10) | ||
| PAYMENT_AMOUNT_TEXT | VARCHAR2 | (4000) | ||
| PAYMENT_METHOD_CODE | VARCHAR2 | (30) | ||
| PAYMENT_METHOD_NAME | VARCHAR2 | (100) | ||
| PAYMENT_METHOD_ATTR_CAT | VARCHAR2 | (150) | ||
| EXCLUSIVE_PAYMENT_FLAG | VARCHAR2 | (1) | ||
| SETTLEMENT_PRIORITY | VARCHAR2 | (30) | ||
| SETTLEMENT_PRIORITY_MEANING | VARCHAR2 | (80) | ||
| AMOUNT_WITHHELD | NUMBER | |||
| DISCOUNT_AMOUNT_TAKEN | NUMBER | |||
| BANK_CHARGE_BEARER | VARCHAR2 | (30) | ||
| BANK_CHARGE_BEARER_MEANING | VARCHAR2 | (80) | ||
| BANK_CHARGE_AMOUNT | NUMBER | |||
| DELIVERY_CHANNEL_CODE | VARCHAR2 | (30) | ||
| DELIVERY_CHANNEL_MEANING | VARCHAR2 | (80) | ||
| DELIVERY_CHANNEL_FORMAT_VALUE | VARCHAR2 | (80) | ||
| BANK_INSTRUCTION1_CODE | VARCHAR2 | (30) | ||
| BANK_INSTRUCTION1_MEANING | VARCHAR2 | (80) | ||
| BANK_INSTRUCTION1_FORMAT_VALUE | VARCHAR2 | (80) | ||
| BANK_INSTRUCTION2_CODE | VARCHAR2 | (30) | ||
| BANK_INSTRUCTION2_MEANING | VARCHAR2 | (80) | ||
| BANK_INSTRUCTION2_FORMAT_VALUE | VARCHAR2 | (80) | ||
| BANK_INSTRUCTION_DETAILS | VARCHAR2 | (255) | ||
| PAYMENT_TEXT_MESSAGE1 | VARCHAR2 | (150) | ||
| PAYMENT_TEXT_MESSAGE2 | VARCHAR2 | (150) | ||
| PAYMENT_TEXT_MESSAGE3 | VARCHAR2 | (150) | ||
| PAYMENT_DETAILS | VARCHAR2 | (4000) | ||
| UNIQUE_REMITTANCE_IDENTIFIER | VARCHAR2 | (30) | ||
| URI_CHECK_DIGIT | VARCHAR2 | (2) | ||
| PAYMENT_REASON_CODE | VARCHAR2 | (30) | ||
| PAYMENT_REASON_MEANING | VARCHAR2 | (80) | ||
| PAYMENT_REASON_FORMAT_VALUE | VARCHAR2 | (80) | ||
| PAYMENT_REASON_COMMENTS | VARCHAR2 | (240) | ||
| REMITTANCE_MESSAGE1 | VARCHAR2 | (150) | ||
| REMITTANCE_MESSAGE2 | VARCHAR2 | (150) | ||
| REMITTANCE_MESSAGE3 | VARCHAR2 | (150) | ||
| DECLARE_PAYMENT_FLAG | VARCHAR2 | (1) | ||
| DECLARATION_AMOUNT | NUMBER | |||
| DECLARATION_CURRENCY_CODE | VARCHAR2 | (10) | ||
| FEDERAL_ALLOTMENT_CODE | VARCHAR2 | (4000) | ||
| FEDERAL_OFFSET_ELIGIBILITY | VARCHAR2 | (4000) | ||
| PAYMENT_ATTR_CAT | VARCHAR2 | (150) | ||
| BENEFICIARY_NAME | VARCHAR2 | (360) | ||
| FEDERAL_SPS_TREASURY_SYMBOL | VARCHAR2 | (4000) | ||
| EMPLOYEE_PAYMENT_FLAG | VARCHAR2 | (1) | ||
| PAYMENT_METHOD_FORMAT_VALUE | VARCHAR2 | (80) | ||
| POSITIVE_PAY_FILE_CREATED_FLAG | VARCHAR2 | (1) | ||
| VOID_DATE | DATE | |||
| LOGICAL_GROUP_REFERENCE | VARCHAR2 | (200) | Specifies the reference of the group to which this payment belongs to | |
| PAYMENT_PROFILE_ID | NUMBER | (15) | ||
| ANTICIPATED_VALUE_DATE | DATE |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYMENT_ID | NUMBER | (15) | Y | |
| TRANSACTION_ERROR_ID | NUMBER | (15) | Y | |
| ERROR_TYPE | VARCHAR2 | (30) | ||
| ERROR_TYPE_MEANING | VARCHAR2 | (80) | QuickCode meaning | |
| ERROR_CODE | VARCHAR2 | (30) | Y | |
| ERROR_MESSAGE | VARCHAR2 | (255) | ||
| ERROR_DATE | DATE | Y | ||
| ERROR_STATUS | VARCHAR2 | (30) | Y | |
| ERROR_STATUS_MEANING | VARCHAR2 | (80) | QuickCode meaning |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYMENT_SERVICE_REQUEST_ID | NUMBER | (15) | Y | |
| CALLING_APP_ID | NUMBER | (15) | Y | |
| APPLICATION_NAME | VARCHAR2 | (240) | Y | |
| CALL_APP_PAY_SERVICE_REQ_CODE | VARCHAR2 | (255) | Y | |
| CREATION_DATE | DATE | Y | ||
| PAYMENT_SERVICE_REQUEST_STATUS | VARCHAR2 | (30) | Y | |
| PPR_STATUS_MEANING | VARCHAR2 | (80) | Y | |
| PROCESS_TYPE | VARCHAR2 | (30) | Y | |
| PPR_ATTR_CAT | VARCHAR2 | (150) | ||
| PPR_PROCESS_TYPE_MEANING | VARCHAR2 | (80) | Y |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| BANK_ACCOUNT_ID | NUMBER | (15) | Y | |
| BANK_NAME | VARCHAR2 | (360) | Y | |
| BANK_NUMBER | VARCHAR2 | (30) | ||
| BRANCH_PARTY_ID | NUMBER | (15) | Y | |
| BANK_BRANCH_NAME | VARCHAR2 | (360) | Y | |
| BRANCH_NUMBER | VARCHAR2 | (30) | ||
| BANK_BRANCH_TYPE | VARCHAR2 | (30) | ||
| BANK_BRANCH_TYPE_MEANING | VARCHAR2 | (80) | ||
| BANK_ACCOUNT_NAME | VARCHAR2 | (100) | Y | |
| BANK_ACCOUNT_NUMBER | VARCHAR2 | (30) | ||
| ACCOUNT_SUFFIX | VARCHAR2 | (30) | ||
| EFT_SWIFT_CODE | VARCHAR2 | (30) | ||
| IBAN_NUMBER | VARCHAR2 | (50) | ||
| CHECK_DIGITS | VARCHAR2 | (30) | ||
| BANK_ACCOUNT_TYPE | VARCHAR2 | (25) | ||
| BANK_ACCOUNT_TYPE_MEANING | VARCHAR2 | (80) | ||
| CURRENCY_CODE | VARCHAR2 | (15) | ||
| BANK_BRANCH_ADDRESS_ID | NUMBER | (15) | ||
| BANK_ACCOUNT_ATTR_CAT | VARCHAR2 | (150) | ||
| REGIONAL_FINANCE_CENTER_ID | VARCHAR2 | (30) | ||
| AGENCY_LOCATION_CODE | VARCHAR2 | (30) | ||
| ABBREVIATED_AGENCY_CODE | VARCHAR2 | (4000) | ||
| FEDERAL_EMPLOYER_ID_NUMBER | VARCHAR2 | (4000) | ||
| BRANCH_LEVEL_EFT_USER_NUMBER | VARCHAR2 | (30) | ||
| ACCOUNT_LEVEL_EFT_USER_NUMBER | VARCHAR2 | (30) | ||
| BANK_ACCOUNT_NUM_ELECTRONIC | VARCHAR2 | (100) | ||
| BANK_ACCOUNT_NAME_ALT | VARCHAR2 | (320) | ||
| INT_BANK_ALT_NAME | VARCHAR2 | (320) | ||
| INT_BANK_BRANCH_ALT_NAME | VARCHAR2 | (320) | ||
| BANK_BRANCH_HOME_COUNTRY | VARCHAR2 | (2) |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| DOCUMENT_AMOUNT | NUMBER | Y | ||
| PAYMENT_CURRENCY_CODE | VARCHAR2 | (10) | Y | |
| PAYMENT_AMOUNT | NUMBER | Y | ||
| ALLOW_REMOVING_DOCUMENT_FLAG | VARCHAR2 | (1) | Y | |
| REMIT_TO_LOCATION_ID | NUMBER | (15) | ||
| STRAIGHT_THROUGH_FLAG | VARCHAR2 | (1) | Y | |
| PAYMENT_SERVICE_REQUEST_ID | NUMBER | (15) | Y | |
| PAYMENT_METHOD_CODE | VARCHAR2 | (30) | Y | |
| EXCLUSIVE_PAYMENT_FLAG | VARCHAR2 | (1) | Y | |
| EXT_PAYEE_ID | NUMBER | (15) | Y | |
| PAYEE_PARTY_ID | NUMBER | (15) | Y | |
| LEGAL_ENTITY_ID | NUMBER | (15) | Y | |
| ORG_ID | NUMBER | (15) | Y | |
| CREATED_BY | NUMBER | (15) | Y | |
| CREATION_DATE | DATE | Y | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| LAST_UPDATE_DATE | DATE | Y | ||
| OBJECT_VERSION_NUMBER | NUMBER | Y | ||
| CALLING_APP_DOC_UNIQUE_REF1 | VARCHAR2 | (100) | Y | |
| CALLING_APP_DOC_UNIQUE_REF2 | VARCHAR2 | (100) | ||
| ORG_TYPE | VARCHAR2 | (30) | Y | |
| COMPLETED_PMTS_GROUP_ID | NUMBER | (15) | ||
| REJECTED_DOCS_GROUP_ID | NUMBER | (15) | ||
| DELIVERY_CHANNEL_CODE | VARCHAR2 | (30) | ||
| PAYMENT_FORMAT_CODE | VARCHAR2 | (30) | ||
| PAY_PROC_TRXN_TYPE_CODE | VARCHAR2 | (100) | Y | |
| CALLING_APP_ID | NUMBER | (15) | Y | |
| CALLING_APP_DOC_REF_NUMBER | VARCHAR2 | (100) | Y | |
| DOCUMENT_PAYABLE_ID | NUMBER | (15) | Y | |
| PAYMENT_FUNCTION | VARCHAR2 | (30) | Y | |
| PAYMENT_DATE | DATE | Y | ||
| DOCUMENT_DATE | DATE | Y | ||
| DOCUMENT_TYPE | VARCHAR2 | (30) | Y | |
| DOCUMENT_STATUS | VARCHAR2 | (30) | Y | |
| DOCUMENT_CURRENCY_CODE | VARCHAR2 | (10) | Y | |
| PAYMENT_REASON_CODE | VARCHAR2 | (30) | ||
| REMITTANCE_MESSAGE1 | VARCHAR2 | (150) | ||
| DOCUMENT_SEQUENCE_ID | NUMBER | |||
| DOCUMENT_SEQUENCE_VALUE | NUMBER | |||
| DOCUMENT_CATEGORY_CODE | VARCHAR2 | (30) | ||
| BANK_ASSIGNED_REF_CODE | VARCHAR2 | (30) | ||
| PO_NUMBER | VARCHAR2 | (255) | ||
| CALLING_APP_DOC_UNIQUE_REF4 | VARCHAR2 | (100) | ||
| CALLING_APP_DOC_UNIQUE_REF5 | VARCHAR2 | (100) | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| PARTY_SITE_ID | NUMBER | (15) | ||
| SUPPLIER_SITE_ID | NUMBER | (15) | ||
| REMITTANCE_MESSAGE2 | VARCHAR2 | (150) | ||
| REMITTANCE_MESSAGE3 | VARCHAR2 | (150) | ||
| PAYMENT_REASON_COMMENTS | VARCHAR2 | (240) | ||
| ANTICIPATED_VALUE_DATE | DATE | |||
| DOCUMENT_DESCRIPTION | VARCHAR2 | (255) | ||
| DOCUMENT_CURRENCY_TAX_AMOUNT | NUMBER | |||
| DOCUMENT_CURR_CHARGE_AMOUNT | NUMBER | |||
| AMOUNT_WITHHELD | NUMBER | |||
| PAYMENT_CURR_DISCOUNT_TAKEN | NUMBER | |||
| DISCOUNT_DATE | DATE | |||
| PAYMENT_DUE_DATE | DATE | |||
| PAYMENT_PROFILE_ID | NUMBER | (15) | ||
| PAYMENT_ID | NUMBER | (15) | ||
| FORMATTING_PAYMENT_ID | NUMBER | (15) | ||
| INTERNAL_BANK_ACCOUNT_ID | NUMBER | (15) | ||
| EXTERNAL_BANK_ACCOUNT_ID | NUMBER | (15) | ||
| BANK_CHARGE_BEARER | VARCHAR2 | (30) | ||
| INTEREST_RATE | NUMBER | |||
| PAYMENT_GROUPING_NUMBER | NUMBER | (15) | ||
| UNIQUE_REMITTANCE_IDENTIFIER | VARCHAR2 | (30) | ||
| URI_CHECK_DIGIT | VARCHAR2 | (2) | ||
| CALLING_APP_DOC_UNIQUE_REF3 | VARCHAR2 | (100) | ||
| BENEFICIARY_PARTY | NUMBER | (15) | ||
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | ||
| ATTRIBUTE1 | VARCHAR2 | (150) | ||
| ATTRIBUTE2 | VARCHAR2 | (150) | ||
| ATTRIBUTE3 | VARCHAR2 | (150) | ||
| ATTRIBUTE4 | VARCHAR2 | (150) | ||
| ATTRIBUTE5 | VARCHAR2 | (150) | ||
| ATTRIBUTE6 | VARCHAR2 | (150) | ||
| ATTRIBUTE7 | VARCHAR2 | (150) | ||
| ATTRIBUTE8 | VARCHAR2 | (150) | ||
| ATTRIBUTE9 | VARCHAR2 | (150) | ||
| ATTRIBUTE10 | VARCHAR2 | (150) | ||
| ATTRIBUTE11 | VARCHAR2 | (150) | ||
| ATTRIBUTE12 | VARCHAR2 | (150) | ||
| ATTRIBUTE13 | VARCHAR2 | (150) | ||
| ATTRIBUTE14 | VARCHAR2 | (150) | ||
| ATTRIBUTE15 | VARCHAR2 | (150) | ||
| SETTLEMENT_PRIORITY | VARCHAR2 | (30) | ||
| ADDRESS_SOURCE | VARCHAR2 | (30) | ||
| EMPLOYEE_ADDRESS_CODE | VARCHAR2 | (30) | ||
| EMPLOYEE_PERSON_ID | NUMBER | (15) | ||
| EMPLOYEE_PAYMENT_FLAG | VARCHAR2 | (1) | ||
| EMPLOYEE_ADDRESS_ID | NUMBER | (15) |
APPS.IBY_FD_DOCS_PAYABLE_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| COMPLETED_PMTS_GROUP_ID | NUMBER | (15) | ||
| PAYMENT_REASON_COMMENTS | VARCHAR2 | (240) | ||
| PAYMENT_DATE | DATE | |||
| ANTICIPATED_VALUE_DATE | DATE | |||
| DECLARATION_AMOUNT | NUMBER | |||
| DECLARATION_CURRENCY_CODE | VARCHAR2 | (10) | ||
| DISCOUNT_AMOUNT_TAKEN | NUMBER | |||
| BANK_CHARGE_AMOUNT | NUMBER | |||
| SETTLEMENT_PRIORITY | VARCHAR2 | (30) | ||
| PAYMENT_ID | NUMBER | (15) | Y | |
| PAYMENT_METHOD_CODE | VARCHAR2 | (30) | Y | |
| PAYMENT_SERVICE_REQUEST_ID | NUMBER | (15) | Y | |
| PROCESS_TYPE | VARCHAR2 | (30) | Y | |
| PAYMENT_STATUS | VARCHAR2 | (30) | Y | |
| PAYMENTS_COMPLETE_FLAG | VARCHAR2 | (1) | Y | |
| PAYMENT_FUNCTION | VARCHAR2 | (30) | Y | |
| PAYMENT_AMOUNT | NUMBER | Y | ||
| PAYMENT_CURRENCY_CODE | VARCHAR2 | (10) | Y | |
| STOP_CONFIRMED_BY | NUMBER | (15) | ||
| STOP_CONFIRM_DATE | DATE | |||
| STOP_CONFIRM_REASON | VARCHAR2 | (240) | ||
| STOP_CONFIRM_REFERENCE | VARCHAR2 | (100) | ||
| STOP_RELEASED_BY | NUMBER | (15) | ||
| STOP_RELEASE_DATE | DATE | |||
| STOP_RELEASE_REASON | VARCHAR2 | (240) | ||
| STOP_RELEASE_REFERENCE | VARCHAR2 | (100) | ||
| STOP_REQUEST_DATE | DATE | |||
| STOP_REQUEST_PLACED_BY | NUMBER | (15) | ||
| STOP_REQUEST_REASON | VARCHAR2 | (240) | ||
| STOP_REQUEST_REFERENCE | VARCHAR2 | (100) | ||
| VOIDED_BY | NUMBER | (15) | ||
| VOID_DATE | DATE | |||
| VOID_REASON | VARCHAR2 | (240) | ||
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | ||
| ATTRIBUTE1 | VARCHAR2 | (150) | ||
| ATTRIBUTE2 | VARCHAR2 | (150) | ||
| ATTRIBUTE3 | VARCHAR2 | (150) | ||
| ATTRIBUTE4 | VARCHAR2 | (150) | ||
| ATTRIBUTE5 | VARCHAR2 | (150) | ||
| ATTRIBUTE6 | VARCHAR2 | (150) | ||
| ATTRIBUTE7 | VARCHAR2 | (150) | ||
| ATTRIBUTE8 | VARCHAR2 | (150) | ||
| ATTRIBUTE9 | VARCHAR2 | (150) | ||
| ATTRIBUTE10 | VARCHAR2 | (150) | ||
| ATTRIBUTE11 | VARCHAR2 | (150) | ||
| ATTRIBUTE12 | VARCHAR2 | (150) | ||
| ATTRIBUTE13 | VARCHAR2 | (150) | ||
| ATTRIBUTE14 | VARCHAR2 | (150) | ||
| ATTRIBUTE15 | VARCHAR2 | (150) | ||
| STOP_CONFIRMED_FLAG | VARCHAR2 | (1) | Y | |
| STOP_RELEASED_FLAG | VARCHAR2 | (1) | Y | |
| STOP_REQUEST_PLACED_FLAG | VARCHAR2 | (1) | Y | |
| CREATED_BY | NUMBER | (15) | Y | |
| CREATION_DATE | DATE | Y | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| LAST_UPDATE_DATE | DATE | Y | ||
| OBJECT_VERSION_NUMBER | NUMBER | Y | ||
| PAYEE_PARTY_ID | NUMBER | (15) | ||
| PARTY_SITE_ID | NUMBER | (15) | ||
| SUPPLIER_SITE_ID | NUMBER | (15) | ||
| PAYMENT_REASON_CODE | VARCHAR2 | (30) | ||
| REMIT_TO_LOCATION_ID | NUMBER | (15) | ||
| ORG_ID | NUMBER | (15) | Y | |
| ORG_TYPE | VARCHAR2 | (30) | Y | |
| LEGAL_ENTITY_ID | NUMBER | (15) | Y | |
| DECLARE_PAYMENT_FLAG | VARCHAR2 | (1) | Y | |
| DELIVERY_CHANNEL_CODE | VARCHAR2 | (30) | ||
| EXT_PAYEE_ID | NUMBER | (15) | Y | |
| PAYMENT_INSTRUCTION_ID | NUMBER | (15) | ||
| PAYMENT_PROFILE_ID | NUMBER | (15) | Y | |
| PREGROUPED_PAYMENT_FLAG | VARCHAR2 | (1) | Y | |
| REMITTANCE_MESSAGE1 | VARCHAR2 | (150) | ||
| REMITTANCE_MESSAGE2 | VARCHAR2 | (150) | ||
| PAYMENT_DETAILS | VARCHAR2 | (4000) | ||
| BANK_CHARGE_BEARER | VARCHAR2 | (30) | ||
| SEPARATE_REMIT_ADVICE_REQ_FLAG | VARCHAR2 | (1) | Y | |
| INTERNAL_BANK_ACCOUNT_ID | NUMBER | (15) | Y | |
| BILL_PAYABLE_FLAG | VARCHAR2 | (1) | Y | |
| EXCLUSIVE_PAYMENT_FLAG | VARCHAR2 | (1) | Y | |
| REMITTANCE_MESSAGE3 | VARCHAR2 | (150) | ||
| PAYMENT_REFERENCE_NUMBER | NUMBER | (15) | ||
| PAPER_DOCUMENT_NUMBER | NUMBER | (15) | ||
| BANK_ASSIGNED_REF_CODE | VARCHAR2 | (30) | ||
| EXTERNAL_BANK_ACCOUNT_ID | NUMBER | (15) | ||
| UNIQUE_REMITTANCE_IDENTIFIER | VARCHAR2 | (30) | ||
| URI_CHECK_DIGIT | VARCHAR2 | (2) | ||
| BANK_INSTRUCTION1_CODE | VARCHAR2 | (30) | ||
| BANK_INSTRUCTION2_CODE | VARCHAR2 | (30) | ||
| BANK_INSTRUCTION_DETAILS | VARCHAR2 | (255) | ||
| PAYMENT_TEXT_MESSAGE1 | VARCHAR2 | (150) | ||
| PAYMENT_TEXT_MESSAGE2 | VARCHAR2 | (150) | ||
| PAYMENT_TEXT_MESSAGE3 | VARCHAR2 | (150) | ||
| MATURITY_DATE | DATE | |||
| PAYMENT_DUE_DATE | DATE | |||
| DOCUMENT_CATEGORY_CODE | VARCHAR2 | (30) | ||
| DOCUMENT_SEQUENCE_ID | NUMBER | |||
| EXT_BRANCH_NUMBER | VARCHAR2 | (30) | ||
| DOCUMENT_SEQUENCE_VALUE | NUMBER | |||
| EXT_BANK_NUMBER | VARCHAR2 | (30) | ||
| BENEFICIARY_PARTY | NUMBER | (15) | ||
| EXT_BANK_ACCOUNT_NAME | VARCHAR2 | (80) | ||
| EXT_BANK_ACCOUNT_NUMBER | VARCHAR2 | (100) | ||
| EXT_BANK_ACCOUNT_TYPE | VARCHAR2 | (25) | ||
| EXT_BANK_ACCOUNT_IBAN_NUMBER | VARCHAR2 | (50) | ||
| PAYEE_NAME | VARCHAR2 | (360) | ||
| PAYEE_ADDRESS1 | VARCHAR2 | (240) | ||
| PAYEE_ADDRESS2 | VARCHAR2 | (240) | ||
| PAYEE_ADDRESS3 | VARCHAR2 | (240) | ||
| PAYEE_ADDRESS4 | VARCHAR2 | (240) | ||
| PAYEE_CITY | VARCHAR2 | (60) | ||
| PAYEE_POSTAL_CODE | VARCHAR2 | (60) | ||
| PAYEE_STATE | VARCHAR2 | (120) | ||
| PAYEE_PROVINCE | VARCHAR2 | (120) | ||
| PAYEE_COUNTY | VARCHAR2 | (120) | ||
| PAYEE_COUNTRY | VARCHAR2 | (60) | ||
| PAYMENT_DOCUMENT_ID | NUMBER | (15) | ||
| ADDRESS_SOURCE | VARCHAR2 | (30) | ||
| EMPLOYEE_ADDRESS_CODE | VARCHAR2 | (30) | ||
| EMPLOYEE_PERSON_ID | NUMBER | (15) | ||
| EMPLOYEE_PAYMENT_FLAG | VARCHAR2 | (1) | ||
| EMPLOYEE_ADDRESS_ID | NUMBER | (15) | ||
| REQUEST_ID | NUMBER | (15) | ||
| LOGICAL_GROUP_REFERENCE | VARCHAR2 | (200) | ||
| EXT_INV_PAYEE_ID | NUMBER | (22) | ||
| INV_PAYEE_PARTY_ID | NUMBER | (22) | ||
| INV_PARTY_SITE_ID | NUMBER | (22) | ||
| INV_SUPPLIER_SITE_ID | NUMBER | (22) | ||
| INV_BENEFICIARY_PARTY | NUMBER | (22) | ||
| INV_PAYEE_NAME | VARCHAR2 | (360) | ||
| INV_PAYEE_ADDRESS1 | VARCHAR2 | (240) | ||
| INV_PAYEE_ADDRESS2 | VARCHAR2 | (240) | ||
| INV_PAYEE_ADDRESS3 | VARCHAR2 | (240) | ||
| INV_PAYEE_ADDRESS4 | VARCHAR2 | (240) | ||
| INV_PAYEE_CITY | VARCHAR2 | (120) | ||
| INV_PAYEE_POSTAL_CODE | VARCHAR2 | (240) | ||
| INV_PAYEE_STATE | VARCHAR2 | (120) | ||
| INV_PAYEE_PROVINCE | VARCHAR2 | (120) | ||
| INV_PAYEE_COUNTY | VARCHAR2 | (120) | ||
| INV_PAYEE_COUNTRY | VARCHAR2 | (120) | ||
| RELATIONSHIP_ID | NUMBER |
APPS.IBY_FD_PAYMENTS_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ROW_ID | ROWID | (10) | ||
| PAYMENT_CHANNEL_NAME | VARCHAR2 | (100) | Y | |
| PAYMENT_CHANNEL_CODE | VARCHAR2 | (30) | Y | |
| INSTRUMENT_TYPE | VARCHAR2 | (30) |
APPS.IBY_FNDCPT_ALL_PMT_CHANNELS_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PARTY_ID | NUMBER | (15) | ||
| INSTRUMENT_TYPE | VARCHAR2 | (11) | ||
| INSTRUMENT_ID | NUMBER | (15) | ||
| CURRENCY_CODE | VARCHAR2 | (15) | ||
| CARD_NUMBER | VARCHAR2 | (30) | ||
| CC_NUMBER_HASH1 | VARCHAR2 | (64) | ||
| CC_NUMBER_HASH2 | VARCHAR2 | (64) | ||
| CARD_EXPIRYDATE | VARCHAR2 | (9) | Obsoleted as part of PA-DSS uptake. | |
| MASKED_CARD_EXPIRYDATE | VARCHAR2 | (5) | ||
| CARD_EXPIRED_FLAG | VARCHAR2 | (1) | ||
| CARD_ISSUER_CODE | VARCHAR2 | (30) | ||
| CARD_ISSUER_NAME | VARCHAR2 | (100) | ||
| PURCHASECARD_SUBTYPE | VARCHAR2 | (30) | ||
| CARD_HOLDER_NAME | VARCHAR2 | (80) | ||
| CARD_BILLING_ADDRESS_ID | NUMBER | |||
| CARD_FI_NAME | VARCHAR2 | (80) | ||
| CARD_SINGLE_USE_FLAG | VARCHAR2 | (1) | ||
| ACCOUNT_NUMBER | VARCHAR2 | (100) | ||
| BANK_ACCT_NUM_HASH1 | VARCHAR2 | (64) | ||
| BANK_ACCT_NUM_HASH2 | VARCHAR2 | (64) | ||
| BANK_NAME | VARCHAR2 | (360) | ||
| BANK_NUMBER | VARCHAR2 | (30) | ||
| BRANCH_NAME | VARCHAR2 | (360) | ||
| BRANCH_NUMBER | VARCHAR2 | (30) | ||
| BIC_NUMBER | VARCHAR2 | (0) | ||
| DESCRIPTION | VARCHAR2 | (240) | ||
| ENCRYPTED | VARCHAR2 | (1) | ||
| CARD_EXPIRATION_STATUS | VARCHAR2 | (80) |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ROW_ID | ROWID | (10) | ||
| INSTR_ASSIGNMENT_ID | NUMBER | (15) | Y | |
| EXT_PAYER_ID | NUMBER | (15) | Y | |
| PAYMENT_FUNCTION | VARCHAR2 | (30) | Y | |
| PARTY_ID | NUMBER | (15) | Y | |
| ORG_TYPE | VARCHAR2 | (30) | ||
| ORG_ID | NUMBER | (15) | ||
| CUST_ACCOUNT_ID | NUMBER | (15) | ||
| ACCT_SITE_USE_ID | NUMBER | (15) | ||
| INSTRUMENT_TYPE | VARCHAR2 | (30) | Y | |
| INSTRUMENT_ID | NUMBER | (15) | Y | |
| ORDER_OF_PREFERENCE | NUMBER | (15) | Y | |
| CURRENCY_CODE | VARCHAR2 | (15) | ||
| CARD_NUMBER | VARCHAR2 | (30) | ||
| CC_NUMBER_HASH1 | VARCHAR2 | (64) | ||
| CC_NUMBER_HASH2 | VARCHAR2 | (64) | ||
| CARD_EXPIRYDATE | VARCHAR2 | (9) | Obsoleted as part of PA-DSS uptake. | |
| MASKED_CARD_EXPIRYDATE | VARCHAR2 | (5) | ||
| CARD_EXPIRED_FLAG | VARCHAR2 | (1) | ||
| CARD_ISSUER_CODE | VARCHAR2 | (30) | ||
| CARD_ISSUER_NAME | VARCHAR2 | (100) | ||
| CARD_ISSUER_ACCEPTED_FLAG | VARCHAR2 | (1) | ||
| PURCHASECARD_SUBTYPE | VARCHAR2 | (30) | ||
| CARD_HOLDER_NAME | VARCHAR2 | (360) | ||
| CARD_BILLING_ADDRESS_ID | NUMBER | |||
| CARD_FI_NAME | VARCHAR2 | (80) | ||
| CARD_SINGLE_USE_FLAG | VARCHAR2 | (1) | ||
| CARD_INFO_ONLY_FLAG | VARCHAR2 | (1) | ||
| ACCOUNT_NUMBER | VARCHAR2 | (100) | ||
| BANK_NAME | VARCHAR2 | (360) | ||
| BANK_NUMBER | VARCHAR2 | (30) | ||
| BANK_ACCT_NUM_HASH1 | VARCHAR2 | (64) | ||
| BANK_ACCT_NUM_HASH2 | VARCHAR2 | (64) | ||
| BRANCH_NAME | VARCHAR2 | (360) | ||
| BRANCH_NUMBER | VARCHAR2 | (30) | ||
| BIC_NUMBER | VARCHAR2 | (0) | ||
| DESCRIPTION | VARCHAR2 | (240) | ||
| ASSIGNMENT_LAST_UPDATE | DATE | Y | ||
| ASSIGNMENT_START_DATE | DATE | Y | ||
| ASSIGNMENT_END_DATE | DATE | |||
| CREATED_BY | NUMBER | (15) | Y | |
| CREATION_DATE | DATE | Y | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| LAST_UPDATE_DATE | DATE | Y | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| OBJECT_VERSION_NUMBER | NUMBER | Y | ||
| ENCRYPTED | VARCHAR2 | (1) | ||
| CARD_EXPIRATION_STATUS | VARCHAR2 | (80) |
APPS.IBY_FNDCPT_PAYER_ASSGN_INSTR_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ROW_ID | ROWID | (10) | ||
| ATTRIBUTE13 | VARCHAR2 | (150) | ||
| ATTRIBUTE14 | VARCHAR2 | (150) | ||
| ATTRIBUTE15 | VARCHAR2 | (150) | ||
| CREATED_BY | NUMBER | (15) | Y | |
| CREATION_DATE | DATE | Y | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| LAST_UPDATE_DATE | DATE | Y | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| OBJECT_VERSION_NUMBER | NUMBER | Y | ||
| PAYMENT_CHANNEL_CODE | VARCHAR2 | (30) | Y | |
| INSTRUMENT_TYPE | VARCHAR2 | (30) | ||
| INACTIVE_DATE | DATE | |||
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | ||
| ATTRIBUTE1 | VARCHAR2 | (150) | ||
| ATTRIBUTE2 | VARCHAR2 | (150) | ||
| ATTRIBUTE3 | VARCHAR2 | (150) | ||
| ATTRIBUTE4 | VARCHAR2 | (150) | ||
| ATTRIBUTE5 | VARCHAR2 | (150) | ||
| ATTRIBUTE6 | VARCHAR2 | (150) | ||
| ATTRIBUTE7 | VARCHAR2 | (150) | ||
| ATTRIBUTE8 | VARCHAR2 | (150) | ||
| ATTRIBUTE9 | VARCHAR2 | (150) | ||
| ATTRIBUTE10 | VARCHAR2 | (150) | ||
| ATTRIBUTE11 | VARCHAR2 | (150) | ||
| ATTRIBUTE12 | VARCHAR2 | (150) | ||
| PAYMENT_CHANNEL_NAME | VARCHAR2 | (100) | Y | |
| DESCRIPTION | VARCHAR2 | (255) | ||
| SEEDED_FLAG | VARCHAR2 | (1) | ||
| FORMAT_VALUE | VARCHAR2 | (80) |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ROW_ID | ROWID | (10) | ||
| SETTLEMENT_TRANS_PRTCL_CODE | VARCHAR2 | (30) | ||
| SETTLEMENT_ACK_RDR_CODE | VARCHAR2 | (30) | ||
| QUERY_FORMAT_CODE | VARCHAR2 | (30) | ||
| QUERY_TRANS_PRTCL_CODE | VARCHAR2 | (30) | ||
| QUERY_ACK_RDR_CODE | VARCHAR2 | (30) | ||
| INACTIVE_DATE | DATE | |||
| CREATED_BY | NUMBER | (15) | Y | |
| CREATION_DATE | DATE | Y | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| LAST_UPDATE_DATE | DATE | Y | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| GROUP_BY_ORG | VARCHAR2 | (1) | ||
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | |
| GROUP_BY_LEGAL_ENTITY | VARCHAR2 | (1) | ||
| ONLINE_AUTH_FORMAT_CODE | VARCHAR2 | (30) | Y | |
| GROUP_BY_INT_BANK_ACCOUNT | VARCHAR2 | (1) | ||
| ONLINE_AUTH_TRANS_PRTCL_CODE | VARCHAR2 | (30) | ||
| GROUP_BY_SETTLEMENT_CURR | VARCHAR2 | (1) | ||
| ONLINE_AUTH_ACK_RDR_CODE | VARCHAR2 | (30) | Y | |
| GROUP_BY_SETTLEMENT_DATE | VARCHAR2 | (1) | ||
| SETTLEMENT_FORMAT_CODE | VARCHAR2 | (30) | Y | |
| LIMIT_BY_AMT_CURR | VARCHAR2 | (10) | ||
| SYS_CC_PROFILE_CODE | VARCHAR2 | (30) | Y | |
| LIMIT_BY_EXCH_RATE_TYPE | VARCHAR2 | (255) | ||
| PAYMENT_SYSTEM_ID | NUMBER | (15) | Y | |
| LIMIT_BY_TOTAL_AMT | NUMBER | |||
| SYS_CC_PROFILE_NAME | VARCHAR2 | (100) | Y | |
| LIMIT_BY_SETTLEMENT_NUM | NUMBER | |||
| AUTOMATIC_PN_SUBMIT_FLAG | VARCHAR2 | (1) | ||
| OVERRIDE_PAYER_DELIVERY_FLAG | VARCHAR2 | (1) | Y or N Flag indicating whether the payer notification delivery method should be overridden by the payer delivery method preference. | |
| PAYER_NOTIFICATION_FORMAT | VARCHAR2 | (30) | Payer notification format | |
| PAYER_NOTIFICATION_DEL_METHOD | VARCHAR2 | (100) | Payer notification delivery method | |
| SETTLEMENT_COMPLETE_POINT | VARCHAR2 | (50) | A point when the settlement is considered complete. | |
| DESCRIPTION | VARCHAR2 | (250) | Description | |
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | ||
| ATTRIBUTE1 | VARCHAR2 | (150) | ||
| ATTRIBUTE2 | VARCHAR2 | (150) | ||
| ATTRIBUTE3 | VARCHAR2 | (150) | ||
| ATTRIBUTE4 | VARCHAR2 | (150) | ||
| ATTRIBUTE5 | VARCHAR2 | (150) | ||
| ATTRIBUTE6 | VARCHAR2 | (150) | ||
| ATTRIBUTE7 | VARCHAR2 | (150) | ||
| ATTRIBUTE8 | VARCHAR2 | (150) | ||
| ATTRIBUTE9 | VARCHAR2 | (150) | ||
| ATTRIBUTE10 | VARCHAR2 | (150) | ||
| ATTRIBUTE11 | VARCHAR2 | (150) | ||
| ATTRIBUTE12 | VARCHAR2 | (150) | ||
| ATTRIBUTE13 | VARCHAR2 | (150) | ||
| ATTRIBUTE14 | VARCHAR2 | (150) | ||
| ATTRIBUTE15 | VARCHAR2 | (150) | ||
| PAYER_NOTIFICATION_CONDITION | VARCHAR2 | (30) | ||
| PN_COND_NUM_OF_RECEIPTS | NUMBER |
APPS.IBY_FNDCPT_SYS_CC_PF_VL is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ROW_ID | ROWID | (10) | ||
| ONLINE_DEB_FORMAT_CODE | VARCHAR2 | (30) | Y | |
| ONLINE_DEB_TRANS_PRTCL_CODE | VARCHAR2 | (30) | ||
| ONLINE_DEB_ACK_RDR_CODE | VARCHAR2 | (30) | Y | |
| SETTLEMENT_REQ_FLAG | VARCHAR2 | (1) | Y | |
| SETTLEMENT_FORMAT_CODE | VARCHAR2 | (30) | ||
| SETTLEMENT_TRANS_PRTCL_CODE | VARCHAR2 | (30) | ||
| SETTLEMENT_ACK_RDR_CODE | VARCHAR2 | (30) | ||
| QUERY_FORMAT_CODE | VARCHAR2 | (30) | ||
| QUERY_TRANS_PRTCL_CODE | VARCHAR2 | (30) | ||
| QUERY_ACK_RDR_CODE | VARCHAR2 | (30) | ||
| INACTIVE_DATE | DATE | |||
| GROUP_BY_ORG | VARCHAR2 | (1) | ||
| CREATED_BY | NUMBER | (15) | Y | |
| GROUP_BY_LEGAL_ENTITY | VARCHAR2 | (1) | ||
| CREATION_DATE | DATE | Y | ||
| GROUP_BY_INT_BANK_ACCOUNT | VARCHAR2 | (1) | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| GROUP_BY_SETTLEMENT_CURR | VARCHAR2 | (1) | ||
| LAST_UPDATE_DATE | DATE | Y | ||
| GROUP_BY_SETTLEMENT_DATE | VARCHAR2 | (1) | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| LIMIT_BY_AMT_CURR | VARCHAR2 | (10) | ||
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | |
| LIMIT_BY_EXCH_RATE_TYPE | VARCHAR2 | (255) | ||
| SYS_DC_PROFILE_CODE | VARCHAR2 | (30) | Y | |
| LIMIT_BY_TOTAL_AMT | NUMBER | |||
| LIMIT_BY_SETTLEMENT_NUM | NUMBER | |||
| PAYMENT_SYSTEM_ID | NUMBER | (15) | Y | |
| SYS_DC_PROFILE_NAME | VARCHAR2 | (100) | Y | |
| AUTOMATIC_PN_SUBMIT_FLAG | VARCHAR2 | (1) | ||
| OVERRIDE_PAYER_DELIVERY_FLAG | VARCHAR2 | (1) | Y or N Flag indicating whether the payer notification delivery method should be overridden by the payer delivery method preference. | |
| PAYER_NOTIFICATION_FORMAT | VARCHAR2 | (30) | Payer notification format | |
| PAYER_NOTIFICATION_DEL_METHOD | VARCHAR2 | (100) | Payer notification delivery method | |
| SETTLEMENT_COMPLETE_POINT | VARCHAR2 | (50) | A point when the settlement is considered complete. | |
| DESCRIPTION | VARCHAR2 | (250) | Description | |
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | ||
| ATTRIBUTE1 | VARCHAR2 | (150) | ||
| ATTRIBUTE2 | VARCHAR2 | (150) | ||
| ATTRIBUTE3 | VARCHAR2 | (150) | ||
| ATTRIBUTE4 | VARCHAR2 | (150) | ||
| ATTRIBUTE5 | VARCHAR2 | (150) | ||
| ATTRIBUTE6 | VARCHAR2 | (150) | ||
| ATTRIBUTE7 | VARCHAR2 | (150) | ||
| ATTRIBUTE8 | VARCHAR2 | (150) | ||
| ATTRIBUTE9 | VARCHAR2 | (150) | ||
| ATTRIBUTE10 | VARCHAR2 | (150) | ||
| ATTRIBUTE11 | VARCHAR2 | (150) | ||
| ATTRIBUTE12 | VARCHAR2 | (150) | ||
| ATTRIBUTE13 | VARCHAR2 | (150) | ||
| ATTRIBUTE14 | VARCHAR2 | (150) | ||
| ATTRIBUTE15 | VARCHAR2 | (150) | ||
| PAYER_NOTIFICATION_CONDITION | VARCHAR2 | (30) | ||
| PN_COND_NUM_OF_RECEIPTS | NUMBER |
APPS.IBY_FNDCPT_SYS_DC_PF_VL is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ROW_ID | ROWID | (10) | ||
| QUERY_ACK_RDR_CODE | VARCHAR2 | (30) | ||
| INACTIVE_DATE | DATE | |||
| CREATED_BY | NUMBER | (15) | ||
| CREATION_DATE | DATE | Y | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| LAST_UPDATE_DATE | DATE | Y | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| OBJECT_VERSION_NUMBER | NUMBER | (15) | ||
| FUNDS_XFER_ACK_RDR_CODE | VARCHAR2 | (30) | ||
| QUERY_FORMAT_CODE | VARCHAR2 | (30) | ||
| QUERY_TRANS_PRTCL_CODE | VARCHAR2 | (30) | ||
| GROUP_BY_ORG | VARCHAR2 | (1) | ||
| SYS_EFT_PROFILE_CODE | VARCHAR2 | (30) | Y | |
| GROUP_BY_LEGAL_ENTITY | VARCHAR2 | (1) | ||
| PAYMENT_SYSTEM_ID | NUMBER | (15) | Y | |
| GROUP_BY_INT_BANK_ACCOUNT | VARCHAR2 | (1) | ||
| VERIFY_FORMAT_CODE | VARCHAR2 | (30) | ||
| GROUP_BY_SETTLEMENT_CURR | VARCHAR2 | (1) | ||
| VERIFY_TRANS_PRTCL_CODE | VARCHAR2 | (30) | ||
| GROUP_BY_SETTLEMENT_DATE | VARCHAR2 | (1) | ||
| VERIFY_ACK_RDR_CODE | VARCHAR2 | (30) | ||
| LIMIT_BY_AMT_CURR | VARCHAR2 | (10) | ||
| FUNDS_XFER_FORMAT_CODE | VARCHAR2 | (30) | Y | |
| LIMIT_BY_EXCH_RATE_TYPE | VARCHAR2 | (255) | ||
| FUNDS_XFER_TRANS_PRTCL_CODE | VARCHAR2 | (30) | ||
| LIMIT_BY_TOTAL_AMT | NUMBER | |||
| SYS_EFT_PROFILE_NAME | VARCHAR2 | (100) | Y | |
| LIMIT_BY_SETTLEMENT_NUM | NUMBER | |||
| SETTLE_REQUIRE_VRFY_FLAG | VARCHAR2 | (1) | Y | |
| AUTOMATIC_PN_SUBMIT_FLAG | VARCHAR2 | (1) | ||
| OVERRIDE_PAYER_DELIVERY_FLAG | VARCHAR2 | (1) | Y or N Flag indicating whether the payer notification delivery method should be overridden by the payer delivery method preference. | |
| PAYER_NOTIFICATION_FORMAT | VARCHAR2 | (30) | Payer notification format | |
| PAYER_NOTIFICATION_DEL_METHOD | VARCHAR2 | (100) | Payer notification delivery method | |
| SETTLEMENT_COMPLETE_POINT | VARCHAR2 | (50) | A point when the settlement is considered complete. | |
| DESCRIPTION | VARCHAR2 | (250) | Description | |
| ACCOMPANY_LETTER_FORMAT | VARCHAR2 | (30) | ||
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | ||
| ATTRIBUTE1 | VARCHAR2 | (150) | ||
| ATTRIBUTE2 | VARCHAR2 | (150) | ||
| ATTRIBUTE3 | VARCHAR2 | (150) | ||
| ATTRIBUTE4 | VARCHAR2 | (150) | ||
| ATTRIBUTE5 | VARCHAR2 | (150) | ||
| ATTRIBUTE6 | VARCHAR2 | (150) | ||
| ATTRIBUTE7 | VARCHAR2 | (150) | ||
| ATTRIBUTE8 | VARCHAR2 | (150) | ||
| ATTRIBUTE9 | VARCHAR2 | (150) | ||
| ATTRIBUTE10 | VARCHAR2 | (150) | ||
| ATTRIBUTE11 | VARCHAR2 | (150) | ||
| ATTRIBUTE12 | VARCHAR2 | (150) | ||
| ATTRIBUTE13 | VARCHAR2 | (150) | ||
| ATTRIBUTE14 | VARCHAR2 | (150) | ||
| ATTRIBUTE15 | VARCHAR2 | (150) | ||
| PAYER_NOTIFICATION_CONDITION | VARCHAR2 | (30) | ||
| PN_COND_NUM_OF_RECEIPTS | NUMBER |
APPS.IBY_FNDCPT_SYS_EFT_PF_VL is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ROW_ID | ROWID | (10) | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| LAST_UPDATE_DATE | DATE | Y | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | |
| BEP_ACCOUNT_ID | NUMBER | (15) | Y | |
| USER_CC_PROFILE_CODE | VARCHAR2 | (30) | Y | |
| SYS_CC_PROFILE_CODE | VARCHAR2 | (30) | Y | |
| INACTIVE_DATE | DATE | |||
| CREATED_BY | NUMBER | (15) | Y | |
| CREATION_DATE | DATE | Y | ||
| QUERY_TRANS_CONFIG_ID | NUMBER | (15) | ||
| ONLINE_AUTH_TRANS_CONFIG_ID | NUMBER | (15) | ||
| SETTLEMENT_TRANS_CONFIG_ID | NUMBER | (15) | ||
| USER_CC_PROFILE_NAME | VARCHAR2 | (100) | Y |
APPS.IBY_FNDCPT_USER_CC_PF_VL is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ROW_ID | ROWID | (10) | ||
| SETTLEMENT_TRANS_CONFIG_ID | NUMBER | (15) | ||
| QUERY_TRANS_CONFIG_ID | NUMBER | (15) | ||
| INACTIVE_DATE | DATE | |||
| CREATED_BY | NUMBER | (15) | Y | |
| CREATION_DATE | DATE | Y | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| LAST_UPDATE_DATE | DATE | Y | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | |
| ONLINE_DEB_TRANS_CONFIG_ID | NUMBER | (15) | ||
| BEP_ACCOUNT_ID | NUMBER | (15) | Y | |
| SYS_DC_PROFILE_CODE | VARCHAR2 | (30) | Y | |
| USER_DC_PROFILE_CODE | VARCHAR2 | (30) | Y | |
| USER_DC_PROFILE_NAME | VARCHAR2 | (100) | Y |
APPS.IBY_FNDCPT_USER_DC_PF_VL is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ROW_ID | ROWID | (10) | ||
| LAST_UPDATE_DATE | DATE | Y | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | |
| BEP_ACCOUNT_ID | NUMBER | (15) | Y | |
| VERIFY_TRANS_CONFIG_ID | NUMBER | (15) | ||
| USER_EFT_PROFILE_CODE | VARCHAR2 | (30) | Y | |
| SYS_EFT_PROFILE_CODE | VARCHAR2 | (30) | Y | |
| CREATION_DATE | DATE | Y | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| INACTIVE_DATE | DATE | |||
| CREATED_BY | NUMBER | (15) | Y | |
| FUNDS_XFER_TRANS_CONFIG_ID | NUMBER | (15) | ||
| QUERY_TRANS_CONFIG_ID | NUMBER | (15) | ||
| USER_EFT_PROFILE_NAME | VARCHAR2 | (100) | Y |
APPS.IBY_FNDCPT_USER_EFT_PF_VL is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| DURATION_TYPE | VARCHAR2 | (30) | Y | |
| MEANING | VARCHAR2 | (80) | Y |
APPS.IBY_FOP_DTYPES_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ROW_ID | ROWID | (10) | ||
| FORMAT_CODE | VARCHAR2 | (30) | Y | |
| FORMAT_TYPE_CODE | VARCHAR2 | (30) | Y | |
| FORMAT_TEMPLATE_CODE | VARCHAR2 | (80) | Y | |
| REFERENCE_FORMAT_CODE | VARCHAR2 | (30) | ||
| EXTRACT_ID | NUMBER | (15) | Y | |
| FORMAT_NAME | VARCHAR2 | (300) | Y | |
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | ||
| ATTRIBUTE1 | VARCHAR2 | (150) | ||
| ATTRIBUTE2 | VARCHAR2 | (150) | ||
| ATTRIBUTE3 | VARCHAR2 | (150) | ||
| ATTRIBUTE4 | VARCHAR2 | (150) | ||
| ATTRIBUTE5 | VARCHAR2 | (150) | ||
| ATTRIBUTE6 | VARCHAR2 | (150) | ||
| ATTRIBUTE7 | VARCHAR2 | (150) | ||
| ATTRIBUTE8 | VARCHAR2 | (150) | ||
| ATTRIBUTE9 | VARCHAR2 | (150) | ||
| ATTRIBUTE10 | VARCHAR2 | (150) | ||
| ATTRIBUTE11 | VARCHAR2 | (150) | ||
| ATTRIBUTE12 | VARCHAR2 | (150) | ||
| ATTRIBUTE13 | VARCHAR2 | (150) | ||
| CREATED_BY | NUMBER | (15) | Y | |
| ATTRIBUTE14 | VARCHAR2 | (150) | ||
| CREATION_DATE | DATE | Y | ||
| ATTRIBUTE15 | VARCHAR2 | (150) | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| LAST_UPDATE_DATE | DATE | Y | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | |
| SEEDED_FLAG | VARCHAR2 | (1) |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| RISK_FACTOR_CODE | VARCHAR2 | (30) | Y | |
| FACTOR_TYPE | NUMBER | (15) | Y | |
| INTERFACE_NAME | VARCHAR2 | (240) | ||
| FORMULA_NAME | VARCHAR2 | (80) | Y | |
| PAYEEID | VARCHAR2 | (80) | Y | |
| IMPLICIT_FLAG | NUMBER | (2) | ||
| WEIGHT | NUMBER | (15) | Y |
APPS.IBY_FORMULA_FACTOR_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
MultiLingual view (a language resolved view of the data.)
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ROW_ID | ROWID | (10) | ||
| CREDIT_APP_STATUS_ID | NUMBER | (15) | Y | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Application level record locking for three tier stateless applications |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| NAME | VARCHAR2 | (80) | Y | |
| DESCRIPTION | VARCHAR2 | (2000) | ||
| CUST_FACING_NAME | VARCHAR2 | (80) | ||
| STATUS_CODE | VARCHAR2 | (30) | Y | |
| START_DATE_ACTIVE | DATE | |||
| END_DATE_ACTIVE | DATE | |||
| UPDATE_ALLOWED_FLAG | VARCHAR2 | (1) | ||
| SEEDED_FLAG | VARCHAR2 | (1) | ||
| STATUS_CATEGORY_CODE | VARCHAR2 | (30) | ||
| STATUS_NUMBER | NUMBER | |||
| SECURITY_GROUP_ID | NUMBER | |||
| ATTRIBUTE_CATEGORY | VARCHAR2 | (240) | ||
| ATTRIBUTE1 | VARCHAR2 | (240) | ||
| ATTRIBUTE2 | VARCHAR2 | (240) | ||
| ATTRIBUTE3 | VARCHAR2 | (240) | ||
| ATTRIBUTE4 | VARCHAR2 | (240) | ||
| ATTRIBUTE5 | VARCHAR2 | (240) | ||
| ATTRIBUTE6 | VARCHAR2 | (240) | ||
| ATTRIBUTE7 | VARCHAR2 | (240) | ||
| ATTRIBUTE8 | VARCHAR2 | (240) | ||
| ATTRIBUTE9 | VARCHAR2 | (240) | ||
| ATTRIBUTE10 | VARCHAR2 | (240) | ||
| ATTRIBUTE11 | VARCHAR2 | (240) | ||
| ATTRIBUTE12 | VARCHAR2 | (240) | ||
| ATTRIBUTE13 | VARCHAR2 | (240) | ||
| ATTRIBUTE14 | VARCHAR2 | (240) | ||
| ATTRIBUTE15 | VARCHAR2 | (240) |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| BEPID | NUMBER | (15) | Y | Back End Payment System identifier |
| BEPINFO_OVN | NUMBER | Y | This column is used for locking purposes that subsequently allows for checking if there is 'dirty' or old data on the screen compared to what is in the database. The situation occurs when the HTML application is an 'stateless' application. | |
| CREATED_BY | NUMBER | (15) | Y | Standard who column - user who created this row (foreign key to FND_USER.USER_ID). |
| CREATION_DATE | DATE | Y | Standard who column - date when this row was created. | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard who column - user who last updated this row (foreign key to FND_USER.USER_ID). |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column - date when a user last updated this row. | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard who column - operating system login of user who last updated this row (foreign key to FND_LOGINS.LOGIN_ID). | |
| SYSTEM_NAME | VARCHAR2 | (80) | Y | Name of the Back End Payment System like Cybercash, Verifone etc |
| BASEURL | VARCHAR2 | (1024) | URL to the Back End Payment System | |
| SUFFIX | VARCHAR2 | (10) | Y | Three-letter Back End Payment System suffix. This is unique per Back End Payment System |
| BEPUSERNAME | VARCHAR2 | (80) | Username for authenticating from iPayment to Back End Payment System. | |
| BEPPASSWORD | VARCHAR2 | (80) | password for BEPUSERNAME. | |
| SUPPORTEDOP | NUMBER | bitmap to denote operations supported by Back End Payment System | ||
| ADMINURL | VARCHAR2 | (1024) | URL to the native Back End Payment System admin pages | |
| LOGINURL | VARCHAR2 | (1024) | loginurl to the Back End Payment System | |
| ACTIVESTATUS | VARCHAR2 | (1) | Indicates whether Back End Payment System is active or not | |
| BEP_TYPE | VARCHAR2 | (10) | ||
| DEFAULT_BEP_FLAG | VARCHAR2 | (1) | ||
| BEPLANG | VARCHAR2 | (80) | language supported by the Back End Payment System | |
| PREFERRED_FLAG | NUMBER | denotes whether this is the preferred language of the Back End Payment System | ||
| PARTY_ID | NUMBER | (15) | ||
| LENDER_NAME | VARCHAR2 | (360) | Name of this party | |
| LOCATION_ID | NUMBER | (15) | Y | |
| ADDRESS1 | VARCHAR2 | (240) | Y | First line of the Identifying address |
| ADDRESS2 | VARCHAR2 | (724) | Second line of the Identifying address | |
| CITY | VARCHAR2 | (60) | City of the Identifying address | |
| POSTAL_CODE | VARCHAR2 | (60) | Postal Code of the Identifying address | |
| STATE | VARCHAR2 | (60) | State of the Identifying address | |
| PROVINCE | VARCHAR2 | (60) | Province of the Identifying address | |
| COUNTRY | VARCHAR2 | (60) | Y | County of the Identifying address |
| LOCATION_OVN | NUMBER | |||
| SECURITY_GROUP_ID | NUMBER | Used in hosted environments | ||
| PARTY_OVN | NUMBER |
APPS.IBY_F_LENDERS_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| BEPID | NUMBER | (15) | Y | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| LENDER_PARTY_ID | NUMBER | (15) | Y | |
| LENDER_NAME | VARCHAR2 | (360) | Y | |
| CONTACT_PARTY_ID | NUMBER | (15) | Y | Party identifier |
| CONTACT_NAME | VARCHAR2 | (360) | Y | Name of this party |
| PERSON_FIRST_NAME | VARCHAR2 | (150) | ||
| PERSON_LAST_NAME | VARCHAR2 | (150) | ||
| PERSON_PARTY_OVN | NUMBER | |||
| EMAIL_CONTACT_POINT_ID | NUMBER | (15) | Y | |
| EMAIL_FORMAT | VARCHAR2 | (30) | ||
| EMAIL_ADDRESS | VARCHAR2 | (2000) | E-mail address | |
| EMAIL_ADDR_OVN | NUMBER | |||
| PHONE_CONTACT_POINT_ID | NUMBER | (15) | Y | |
| PHONE_COUNTRY_CODE | VARCHAR2 | (10) | ||
| PHONE_AREA_CODE | VARCHAR2 | (10) | ||
| PHONE_NUMBER | VARCHAR2 | (40) | ||
| PHONE_EXTENSION | VARCHAR2 | (20) | ||
| PHONE_LINE_TYPE | VARCHAR2 | (30) | ||
| PHONE_OVN | NUMBER | |||
| JOB_TITLE | VARCHAR2 | (100) | Job title of the contact | |
| DEPARTMENT | VARCHAR2 | (60) | Free form text used to name the department | |
| LOCATION_ID | NUMBER | (15) | Y | |
| ADDRESS1 | VARCHAR2 | (240) | Y | First line of the Identifying address |
| ADDRESS2 | VARCHAR2 | (724) | Second line of the Identifying address | |
| CITY | VARCHAR2 | (60) | City of the Identifying address | |
| STATE | VARCHAR2 | (60) | State of the Identifying address | |
| POSTAL_CODE | VARCHAR2 | (60) | Postal Code of the Identifying address | |
| PROVINCE | VARCHAR2 | (60) | Province of the Identifying address | |
| COUNTRY | VARCHAR2 | (60) | Y | The country listed in the TERRITORY_CODE column of the FND_TERRITORY table. for the Identifying address. |
| LOCATION_OVN | NUMBER |
APPS.IBY_F_LENDER_CONTACTS_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| RATE_ID | NUMBER | (15) | Y | |
| REQUEST_ID | NUMBER | (15) | Request Identifier | |
| PROGRAM_APPLICATION_ID | NUMBER | (15) | Application Identifier of last concurrent program to update record | |
| PROGRAM_ID | NUMBER | (15) | Identifier of last concurrent program to update record | |
| PROGRAM_UPDATE_DATE | DATE | Last date concurrent program updated record | ||
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Application level record locking for three tier stateless applications |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| RATE | NUMBER | (10) | Y | |
| CUSTOMER_TYPE_CODE | VARCHAR2 | (30) | ||
| PAYMENT_TERM | VARCHAR2 | (240) | ||
| PAYMENT_TERM_UOM_CODE | VARCHAR2 | (3) | ||
| DEAL_SIZE_MIN | NUMBER | |||
| DEAL_SIZE_MAX | NUMBER | |||
| DEAL_SIZE_CURRENCY_CODE | VARCHAR2 | (30) | ||
| ORG_ID | NUMBER | (15) | ||
| SECURITY_GROUP_ID | NUMBER |
APPS.IBY_F_PC_RATES_ALL_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
MultiLingual view (a language resolved view of the data.)
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ROW_ID | ROWID | (10) | ||
| CREDIT_APP_GRNTR_ID | NUMBER | (15) | Y | |
| CREDIT_APP_ID | NUMBER | (15) | Y | |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| ACTIVE_FLAG | VARCHAR2 | (1) | ||
| START_DATE_ACTIVE | DATE | |||
| END_DATE_ACTIVE | DATE | |||
| FIRST_NAME | VARCHAR2 | (150) | ||
| LAST_NAME | VARCHAR2 | (150) | ||
| EMAIL_ADDRESS | VARCHAR2 | (2000) | ||
| SECURITY_KEY | VARCHAR2 | (150) | ||
| CREDIT_APP_GRNTR_SEQ | NUMBER | |||
| SECURITY_GROUP_ID | NUMBER | |||
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Application level record locking for three tier stateless applications |
APPS.IBY_F_T_CA_GRNTRS_VL is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| STATUS_HISTORY_ID | NUMBER | (15) | Y | |
| REQUEST_ID | NUMBER | (15) | Request Identifier | |
| PROGRAM_APPLICATION_ID | NUMBER | (15) | Application Identifier of last concurrent program to update record | |
| PROGRAM_ID | NUMBER | (15) | Identifier of last concurrent program to update record | |
| PROGRAM_UPDATE_DATE | DATE | Last date concurrent program updated record | ||
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Application level record locking for three tier stateless applications |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| CREDIT_APP_ID | NUMBER | (15) | Y | |
| OLD_STATUS_ID | NUMBER | (15) | ||
| OLD_STATUS_CODE | VARCHAR2 | (30) | ||
| OLD_STATUS_NAME | VARCHAR2 | (80) | ||
| OLD_STATUS_DESC | VARCHAR2 | (2000) | ||
| NEW_STATUS_ID | NUMBER | (15) | Y | |
| NEW_STATUS_CODE | VARCHAR2 | (30) | Y | |
| NEW_STATUS_NAME | VARCHAR2 | (80) | Y | |
| NEW_STATUS_DESC | VARCHAR2 | (2000) | ||
| USER_ID | NUMBER | (15) | ||
| USER_NAME | VARCHAR2 | (100) | ||
| USER_TYPE_CODE | VARCHAR2 | (30) | ||
| CA_STATUS_EVENT_TIME | DATE | |||
| CA_STATUS_EVENT_CODE | VARCHAR2 | (30) | ||
| CA_STATUS_EVENT_DESC | VARCHAR2 | (2000) | ||
| SECURITY_GROUP_ID | NUMBER |
APPS.IBY_F_T_CA_STATUS_H_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
MultiLingual view (a language resolved view of the data.)
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ROW_ID | ROWID | (10) | ||
| CREDIT_APP_ID | NUMBER | (15) | Y | |
| TRXN_SUMMARY_ID | NUMBER | (15) | Y | |
| REQUEST_ID | NUMBER | (15) | Request Identifier | |
| PROGRAM_APPLICATION_ID | NUMBER | (15) | Application Identifier of last concurrent program to update record | |
| PROGRAM_ID | NUMBER | (15) | Identifier of last concurrent program to update record | |
| PROGRAM_UPDATE_DATE | DATE | Last date concurrent program updated record | ||
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Application level record locking for three tier stateless applications |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| NAME | VARCHAR2 | (80) | ||
| DESCRIPTION | VARCHAR2 | (2000) | ||
| FINANCING_TYPE_CODE | VARCHAR2 | (30) | ||
| CREDIT_APP_STATUS_ID | NUMBER | (15) | Y | |
| DURATION | NUMBER | |||
| DURATION_UOM_CODE | VARCHAR2 | (3) | ||
| INTEREST_RATE | NUMBER | (10) | ||
| PAYMENT_STRUCTURE_CODE | VARCHAR2 | (30) | ||
| DECISION_TIME_FRAME | NUMBER | |||
| DECISION_TIME_FRAME_UOM_CODE | VARCHAR2 | (30) | ||
| CREDIT_APP_XML_ID | NUMBER | (15) | ||
| TERMS_N_CONDITIONS_XML_ID | NUMBER | (15) | ||
| FIRST_SAVED_DATE | DATE | |||
| EXPIRATION_DATE | DATE | |||
| EXP_EXTENDED_COUNT | NUMBER | |||
| EXPIRING_FLAG | VARCHAR2 | (1) | ||
| DOC_RECEIVED_DATE | DATE | |||
| DOC_RECEIVED_FLAG | VARCHAR2 | (1) | ||
| N_PG_REQUESTED | NUMBER | |||
| N_PG_SUBMITTED | NUMBER | |||
| BUYER_FORM_MARKUP_FLAG | VARCHAR2 | (1) | ||
| ORG_ID | NUMBER | (15) | ||
| SECURITY_GROUP_ID | NUMBER | |||
| ATTRIBUTE_CATEGORY | VARCHAR2 | (30) | ||
| ATTRIBUTE1 | VARCHAR2 | (150) | ||
| ATTRIBUTE2 | VARCHAR2 | (150) | ||
| ATTRIBUTE3 | VARCHAR2 | (150) | ||
| ATTRIBUTE4 | VARCHAR2 | (150) | ||
| ATTRIBUTE5 | VARCHAR2 | (150) | ||
| ATTRIBUTE6 | VARCHAR2 | (150) | ||
| ATTRIBUTE7 | VARCHAR2 | (150) | ||
| ATTRIBUTE8 | VARCHAR2 | (150) | ||
| ATTRIBUTE9 | VARCHAR2 | (150) | ||
| ATTRIBUTE10 | VARCHAR2 | (150) | ||
| ATTRIBUTE11 | VARCHAR2 | (150) | ||
| ATTRIBUTE12 | VARCHAR2 | (150) | ||
| ATTRIBUTE13 | VARCHAR2 | (150) | ||
| ATTRIBUTE14 | VARCHAR2 | (150) | ||
| ATTRIBUTE15 | VARCHAR2 | (150) |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| CREDIT_APP_ID | NUMBER | (15) | Y | |
| REQUEST_ID | NUMBER | (15) | Request Identifier | |
| PROGRAM_APPLICATION_ID | NUMBER | (15) | Application Identifier of last concurrent program to update record | |
| PROGRAM_ID | NUMBER | (15) | Identifier of last concurrent program to update record | |
| PROGRAM_UPDATE_DATE | DATE | Last date concurrent program updated record | ||
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Application level record locking for three tier stateless applications |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| TRXN_SUMMARY_ID | NUMBER | (15) | Y | |
| TRANSACTIONID | NUMBER | Y | ID generated for each payment request (orapmtreq) and passed back toElectronic Commerce Application. | |
| CREDIT_APP_STATUS_ID | NUMBER | (15) | Y | |
| STATUS_NAME | VARCHAR2 | (80) | Y | |
| STATUS_DESCRIPTION | VARCHAR2 | (2000) | ||
| CUST_FACING_STATUS_NAME | VARCHAR2 | (80) | ||
| STATUS_NUMBER | NUMBER | |||
| CREDIT_APP_XML_ID | NUMBER | (15) | ||
| TERMS_N_CONDITIONS_XML_ID | NUMBER | (15) | ||
| BEPID | NUMBER | (15) | Back End Payment System Identifier | |
| LENDER_PARTY_ID | NUMBER | (15) | ||
| LENDER_PARTY_NAME | VARCHAR2 | (360) | Name of this party | |
| CUST_ACCOUNT_ID | NUMBER | (15) | ||
| CUSTOMER_NAME | VARCHAR2 | (360) | Y | Name of this party |
| FINANCING_TYPE_CODE | VARCHAR2 | (30) | ||
| DURATION | NUMBER | |||
| DURATION_UOM_CODE | VARCHAR2 | (3) | ||
| PAYMENT_STRUCTURE_CODE | VARCHAR2 | (30) | ||
| INTEREST_RATE | NUMBER | (10) | ||
| DECISION_TIME_FRAME | NUMBER | |||
| DECISION_TIME_FRAME_UOM_CODE | VARCHAR2 | (30) | ||
| FIRST_SAVED_DATE | DATE | |||
| EXPIRATION_DATE | DATE | |||
| EXP_EXTENDED_COUNT | NUMBER | |||
| EXPIRING_FLAG | VARCHAR2 | (1) | ||
| DOC_RECEIVED_DATE | DATE | |||
| DOC_RECEIVED_FLAG | VARCHAR2 | (1) | ||
| N_PG_REQUESTED | NUMBER | |||
| N_PG_SUBMITTED | NUMBER | |||
| BUYER_FORM_MARKUP_FLAG | VARCHAR2 | (1) | ||
| CREDIT_APP_NAME | VARCHAR2 | (80) | ||
| CREDIT_APP_DESCRIPTION | VARCHAR2 | (2000) | ||
| MTANGIBLEID | NUMBER | Y | master id that points to iby_tangible table for additional information about tangible(orders) | |
| AMOUNT | NUMBER | Y | Amount | |
| CURRENCYNAMECODE | VARCHAR2 | (15) | Y | code for currency name such USD |
| PAYEEID | VARCHAR2 | (80) | Y | id of the payee passed by Electronic Commerce Application |
| MPAYEEID | NUMBER | Y | Payee identifier | |
| ECAPPID | NUMBER | (15) | Y | Electronic Commerce Application Identifier |
| SOURCE_OBJECT_TYPE_CODE | VARCHAR2 | (30) | ||
| SOURCE_OBJECT_ID | NUMBER | (15) | ||
| ORG_ID | NUMBER | (15) | ||
| SECURITY_GROUP_ID | NUMBER | |||
| ATTRIBUTE_CATEGORY | VARCHAR2 | (30) | ||
| ATTRIBUTE1 | VARCHAR2 | (150) | ||
| ATTRIBUTE2 | VARCHAR2 | (150) | ||
| ATTRIBUTE3 | VARCHAR2 | (150) | ||
| ATTRIBUTE4 | VARCHAR2 | (150) | ||
| ATTRIBUTE5 | VARCHAR2 | (150) | ||
| ATTRIBUTE6 | VARCHAR2 | (150) | ||
| ATTRIBUTE7 | VARCHAR2 | (150) | ||
| ATTRIBUTE8 | VARCHAR2 | (150) | ||
| ATTRIBUTE9 | VARCHAR2 | (150) | ||
| ATTRIBUTE10 | VARCHAR2 | (150) | ||
| ATTRIBUTE11 | VARCHAR2 | (150) | ||
| ATTRIBUTE12 | VARCHAR2 | (150) | ||
| ATTRIBUTE13 | VARCHAR2 | (150) | ||
| ATTRIBUTE15 | VARCHAR2 | (150) | ||
| ATTRIBUTE14 | VARCHAR2 | (150) |
APPS.IBY_F_T_CRDT_APPS_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
MultiLingual view (a language resolved view of the data.)
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ROW_ID | ROWID | (10) | ||
| MSG_TEMPLATE_ID | NUMBER | (15) | Y | |
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | Application level record locking for three tier stateless applications |
| CREATED_BY | NUMBER | (15) | Y | Standard Who column |
| CREATION_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATED_BY | NUMBER | (15) | Y | Standard Who column |
| LAST_UPDATE_DATE | DATE | Y | Standard Who column | |
| LAST_UPDATE_LOGIN | NUMBER | (15) | Standard Who column | |
| MSG_TEMPLATE_NAME | VARCHAR2 | (240) | Y | |
| MSG_TEMPLATE_NUMBER | NUMBER | (15) | ||
| MSG_TEMPLATE_VERSION | NUMBER | Y | ||
| MSG_TYPE_CODE | VARCHAR2 | (240) | Y | |
| MSG_TYPE_MEANING | VARCHAR2 | (80) | Y | |
| FROZEN_FLAG | VARCHAR2 | (1) | ||
| SEEDED_FLAG | VARCHAR2 | (1) | ||
| START_DATE_ACTIVE | DATE | |||
| END_DATE_ACTIVE | DATE | |||
| SECURITY_GROUP_ID | NUMBER | |||
| ATTRIBUTE_CATEGORY | VARCHAR2 | (240) | ||
| ATTRIBUTE1 | VARCHAR2 | (240) | ||
| ATTRIBUTE2 | VARCHAR2 | (240) | ||
| ATTRIBUTE3 | VARCHAR2 | (240) | ||
| ATTRIBUTE4 | VARCHAR2 | (240) | ||
| ATTRIBUTE5 | VARCHAR2 | (240) | ||
| ATTRIBUTE6 | VARCHAR2 | (240) | ||
| ATTRIBUTE7 | VARCHAR2 | (240) | ||
| ATTRIBUTE8 | VARCHAR2 | (240) | ||
| ATTRIBUTE9 | VARCHAR2 | (240) | ||
| ATTRIBUTE10 | VARCHAR2 | (240) | ||
| ATTRIBUTE11 | VARCHAR2 | (240) | ||
| ATTRIBUTE12 | VARCHAR2 | (240) | ||
| ATTRIBUTE13 | VARCHAR2 | (240) | ||
| ATTRIBUTE14 | VARCHAR2 | (240) | ||
| ATTRIBUTE15 | VARCHAR2 | (240) | ||
| NAME | VARCHAR2 | (80) | Y | |
| DESCRIPTION | VARCHAR2 | (2000) | ||
| MESSAGE_TEMPLATE | VARCHAR2 | (2000) |
APPS.IBY_G_MSG_TEMPLATES_VL is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| INSTRID | NUMBER | Y | ||
| INSTRTYPE | VARCHAR2 | (30) | Y |
APPS.IBY_INSTR_HOLDER_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| CLEARED_CONTENT | XMLTYPE | (40) | ||
| INSTRUCTION_ID | NUMBER | (15) | Y | |
| INSTRUCTION_STATUS | VARCHAR2 | (30) | Y |
APPS.IBY_INS_LVL_PMT_STS_CHG_XML_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| INSTRUCTION_CONTENT | XMLTYPE | (40) | ||
| INSTRUCTION_ID | NUMBER | (15) | Y | |
| INSTRUCTION_STATUS | VARCHAR2 | (30) | Y |
APPS.IBY_NOTIFY_INS_FAIL_XML_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| REQUEST_CONTENT | XMLTYPE | (40) | ||
| PAY_SERVICE_REQUEST_ID | NUMBER | (15) | Y | |
| REQUEST_STATUS | VARCHAR2 | (30) | Y |
APPS.IBY_NOTIFY_REQ_XML_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| INSTRUCTION_CONTENT | XMLTYPE | (40) | ||
| INSTRUCTION_ID | NUMBER | (15) | Y | |
| INSTRUCTION_STATUS | VARCHAR2 | (30) | Y |
APPS.IBY_NOTIFY_XMISSION_FAIL_XML_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PARTY_ID | NUMBER | (15) | Y | |
| EXT_BANK_ACCOUNT_ID | NUMBER | (15) | Y | |
| COUNTRY_CODE | VARCHAR2 | (2) | ||
| BRANCH_ID | NUMBER | (15) | ||
| BANK_ID | NUMBER | (15) | ||
| BANK_ACCOUNT_NAME | VARCHAR2 | (80) | ||
| BANK_ACCOUNT_NUM | VARCHAR2 | (100) | ||
| CURRENCY_CODE | VARCHAR2 | (15) | ||
| IBAN | VARCHAR2 | (50) | ||
| CHECK_DIGITS | VARCHAR2 | (30) | ||
| BANK_ACCOUNT_NAME_ALT | VARCHAR2 | (320) | ||
| BANK_ACCOUNT_TYPE | VARCHAR2 | (25) | ||
| ACCOUNT_SUFFIX | VARCHAR2 | (30) | ||
| DESCRIPTION | VARCHAR2 | (240) | ||
| AGENCY_LOCATION_CODE | VARCHAR2 | (30) | ||
| PAYMENT_FACTOR_FLAG | VARCHAR2 | (1) | ||
| FOREIGN_PAYMENT_USE_FLAG | VARCHAR2 | (1) | ||
| EXCHANGE_RATE_AGREEMENT_NUM | VARCHAR2 | (80) | ||
| EXCHANGE_RATE_AGREEMENT_TYPE | VARCHAR2 | (80) | ||
| EXCHANGE_RATE | NUMBER | |||
| START_DATE | DATE | |||
| END_DATE | DATE | |||
| BANK_NAME | VARCHAR2 | (360) | ||
| BANK_NUMBER | VARCHAR2 | (30) | ||
| BRANCH_NAME | VARCHAR2 | (360) | ||
| BRANCH_NUMBER | VARCHAR2 | (30) | ||
| BIC_NUMBER | VARCHAR2 | (30) | ||
| BANK_NAME_ALT | VARCHAR2 | (320) | ||
| BANK_BRANCH_NAME_ALT | VARCHAR2 | (320) | ||
| BANK_INSTITUTION_TYPE | VARCHAR2 | (30) | ||
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | ||
| ATTRIBUTE1 | VARCHAR2 | (150) | ||
| ATTRIBUTE2 | VARCHAR2 | (150) | ||
| ATTRIBUTE3 | VARCHAR2 | (150) | ||
| ATTRIBUTE4 | VARCHAR2 | (150) | ||
| ATTRIBUTE5 | VARCHAR2 | (150) | ||
| ATTRIBUTE6 | VARCHAR2 | (150) | ||
| ATTRIBUTE7 | VARCHAR2 | (150) | ||
| ATTRIBUTE8 | VARCHAR2 | (150) | ||
| ATTRIBUTE9 | VARCHAR2 | (150) | ||
| ATTRIBUTE10 | VARCHAR2 | (150) | ||
| ATTRIBUTE11 | VARCHAR2 | (150) | ||
| ATTRIBUTE12 | VARCHAR2 | (150) | ||
| ATTRIBUTE13 | VARCHAR2 | (150) | ||
| ATTRIBUTE14 | VARCHAR2 | (150) | ||
| ATTRIBUTE15 | VARCHAR2 | (150) | ||
| CREATED_BY | NUMBER | (15) | Y | |
| CREATION_DATE | DATE | Y | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| LAST_UPDATE_DATE | DATE | Y | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) |
APPS.IBY_PAYEE_ALL_BANKACCT_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ROW_ID | ROWID | (10) | ||
| INSTR_ASSIGNMENT_ID | NUMBER | (15) | Y | |
| PAYMENT_FUNCTION | VARCHAR2 | (30) | Y | |
| PARTY_ID | NUMBER | (15) | Y | |
| ORG_ID | NUMBER | (15) | ||
| ORG_TYPE | VARCHAR2 | (30) | ||
| PARTY_SITE_ID | NUMBER | (15) | ||
| SUPPLIER_SITE_ID | NUMBER | (15) | ||
| ORDER_OF_PREFERENCE | NUMBER | (15) | Y | |
| START_DATE | DATE | Y | ||
| END_DATE | DATE | |||
| EXT_BANK_ACCOUNT_ID | NUMBER | (15) | Y | |
| CURRENCY_CODE | VARCHAR2 | (15) | ||
| IBAN | VARCHAR2 | (50) | ||
| ACCOUNT_NUMBER | VARCHAR2 | (100) | ||
| BANK_NAME | VARCHAR2 | (360) | ||
| BANK_NUMBER | VARCHAR2 | (30) | ||
| BRANCH_NAME | VARCHAR2 | (360) | ||
| BRANCH_NUMBER | VARCHAR2 | (30) | ||
| BIC_NUMBER | VARCHAR2 | (50) | ||
| DESCRIPTION | VARCHAR2 | (240) | ||
| CREATED_BY | NUMBER | (15) | Y | |
| CREATION_DATE | DATE | Y | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| LAST_UPDATE_DATE | DATE | Y | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) |
APPS.IBY_PAYEE_ASSIGNED_BANKACCT_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAPER_DOCUMENT_NUMBER | NUMBER | (15) | ||
| BANK_ASSIGNED_REF_CODE | VARCHAR2 | (30) | ||
| EXTERNAL_BANK_ACCOUNT_ID | NUMBER | (15) | ||
| DOCUMENT_SEQUENCE_ID | NUMBER | |||
| DOCUMENT_SEQUENCE_VALUE | NUMBER | |||
| DOCUMENT_CATEGORY_CODE | VARCHAR2 | (30) | ||
| UNIQUE_REMITTANCE_IDENTIFIER | VARCHAR2 | (30) | ||
| URI_CHECK_DIGIT | VARCHAR2 | (2) | ||
| BANK_INSTRUCTION1_CODE | VARCHAR2 | (30) | ||
| BANK_INSTRUCTION2_CODE | VARCHAR2 | (30) | ||
| PAYMENT_TEXT_MESSAGE1 | VARCHAR2 | (150) | ||
| PAYMENT_TEXT_MESSAGE2 | VARCHAR2 | (150) | ||
| PAYMENT_TEXT_MESSAGE3 | VARCHAR2 | (150) | ||
| BILL_PAYABLE_FLAG | VARCHAR2 | (1) | Y | |
| MATURITY_DATE | DATE | |||
| PAYMENT_DUE_DATE | DATE | |||
| STOP_REQUEST_PLACED_FLAG | VARCHAR2 | (1) | Y | |
| STOP_REQUEST_REASON | VARCHAR2 | (240) | ||
| STOP_REQUEST_PLACED_BY | NUMBER | (15) | ||
| STOP_REQUEST_DATE | DATE | |||
| STOP_REQUEST_REFERENCE | VARCHAR2 | (100) | ||
| STOP_RELEASED_FLAG | VARCHAR2 | (1) | Y | |
| STOP_RELEASE_REASON | VARCHAR2 | (240) | ||
| STOP_RELEASED_BY | NUMBER | (15) | ||
| STOP_RELEASE_DATE | DATE | |||
| STOP_RELEASE_REFERENCE | VARCHAR2 | (100) | ||
| STOP_CONFIRMED_FLAG | VARCHAR2 | (1) | Y | |
| STOP_CONFIRM_REASON | VARCHAR2 | (240) | ||
| STOP_CONFIRMED_BY | NUMBER | (15) | ||
| STOP_CONFIRM_DATE | DATE | |||
| STOP_CONFIRM_REFERENCE | VARCHAR2 | (100) | ||
| VOID_REASON | VARCHAR2 | (240) | ||
| VOIDED_BY | NUMBER | (15) | ||
| VOID_DATE | DATE | |||
| REMIT_TO_LOCATION_ID | NUMBER | (15) | ||
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | ||
| ATTRIBUTE1 | VARCHAR2 | (150) | ||
| ATTRIBUTE2 | VARCHAR2 | (150) | ||
| ATTRIBUTE3 | VARCHAR2 | (150) | ||
| ATTRIBUTE4 | VARCHAR2 | (150) | ||
| ATTRIBUTE5 | VARCHAR2 | (150) | ||
| ATTRIBUTE6 | VARCHAR2 | (150) | ||
| ATTRIBUTE7 | VARCHAR2 | (150) | ||
| ATTRIBUTE8 | VARCHAR2 | (150) | ||
| ATTRIBUTE9 | VARCHAR2 | (150) | ||
| ATTRIBUTE10 | VARCHAR2 | (150) | ||
| ATTRIBUTE11 | VARCHAR2 | (150) | ||
| ATTRIBUTE12 | VARCHAR2 | (150) | ||
| ATTRIBUTE13 | VARCHAR2 | (150) | ||
| ATTRIBUTE14 | VARCHAR2 | (150) | ||
| ATTRIBUTE15 | VARCHAR2 | (150) | ||
| PAYMENT_ID | NUMBER | (15) | Y | |
| PAYMENT_METHOD_CODE | VARCHAR2 | (30) | Y | |
| PAYMENT_SERVICE_REQUEST_ID | NUMBER | (15) | Y | |
| PROCESS_TYPE | VARCHAR2 | (30) | Y | |
| PAYMENT_STATUS | VARCHAR2 | (30) | Y | |
| PAYMENTS_COMPLETE_FLAG | VARCHAR2 | (1) | Y | |
| PAYMENT_FUNCTION | VARCHAR2 | (30) | Y | |
| PAYMENT_AMOUNT | NUMBER | Y | ||
| PAYMENT_CURRENCY_CODE | VARCHAR2 | (10) | Y | |
| SEPARATE_REMIT_ADVICE_REQ_FLAG | VARCHAR2 | (1) | Y | |
| INTERNAL_BANK_ACCOUNT_ID | NUMBER | (15) | Y | |
| SUPPLIER_SITE_ID | NUMBER | (15) | ||
| PAYEE_PARTY_ID | NUMBER | (15) | ||
| PARTY_SITE_ID | NUMBER | (15) | ||
| DECLARE_PAYMENT_FLAG | VARCHAR2 | (1) | Y | |
| DECLARATION_AMOUNT | NUMBER | |||
| DECLARATION_CURRENCY_CODE | VARCHAR2 | (10) | ||
| DISCOUNT_AMOUNT_TAKEN | NUMBER | |||
| PAYMENT_DETAILS | VARCHAR2 | (4000) | ||
| BANK_CHARGE_BEARER | VARCHAR2 | (30) | ||
| BANK_CHARGE_AMOUNT | NUMBER | |||
| DELIVERY_CHANNEL_CODE | VARCHAR2 | (30) | ||
| SETTLEMENT_PRIORITY | VARCHAR2 | (30) | ||
| REMITTANCE_MESSAGE1 | VARCHAR2 | (150) | ||
| REMITTANCE_MESSAGE2 | VARCHAR2 | (150) | ||
| REMITTANCE_MESSAGE3 | VARCHAR2 | (150) | ||
| PAYMENT_REFERENCE_NUMBER | NUMBER | (15) | ||
| ORG_TYPE | VARCHAR2 | (30) | Y | |
| LEGAL_ENTITY_ID | NUMBER | (15) | Y | |
| EXT_PAYEE_ID | NUMBER | (15) | Y | |
| ORG_ID | NUMBER | (15) | Y | |
| PREGROUPED_PAYMENT_FLAG | VARCHAR2 | (1) | Y | |
| CREATED_BY | NUMBER | (15) | Y | |
| CREATION_DATE | DATE | Y | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| LAST_UPDATE_DATE | DATE | Y | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| OBJECT_VERSION_NUMBER | NUMBER | Y | ||
| PAYMENT_PROFILE_ID | NUMBER | (15) | Y | |
| PAYMENT_INSTRUCTION_ID | NUMBER | (15) | ||
| PAYMENT_REASON_CODE | VARCHAR2 | (30) | ||
| PAYMENT_REASON_COMMENTS | VARCHAR2 | (240) | ||
| PAYMENT_DATE | DATE | |||
| ANTICIPATED_VALUE_DATE | DATE | |||
| COMPLETED_PMTS_GROUP_ID | NUMBER | (15) | ||
| EXT_BRANCH_NUMBER | VARCHAR2 | (30) | ||
| EXT_BANK_NUMBER | VARCHAR2 | (30) | ||
| EXT_BANK_ACCOUNT_NAME | VARCHAR2 | (80) | ||
| EXT_BANK_ACCOUNT_NUMBER | VARCHAR2 | (100) | ||
| EXT_BANK_ACCOUNT_TYPE | VARCHAR2 | (25) | ||
| EXT_BANK_ACCOUNT_IBAN_NUMBER | VARCHAR2 | (50) | ||
| PAYEE_NAME | VARCHAR2 | (360) | ||
| PAYEE_ADDRESS1 | VARCHAR2 | (240) | ||
| PAYEE_ADDRESS2 | VARCHAR2 | (240) | ||
| PAYEE_ADDRESS3 | VARCHAR2 | (240) | ||
| PAYEE_ADDRESS4 | VARCHAR2 | (240) | ||
| PAYEE_CITY | VARCHAR2 | (60) | ||
| PAYEE_POSTAL_CODE | VARCHAR2 | (60) | ||
| PAYEE_STATE | VARCHAR2 | (120) | ||
| PAYEE_PROVINCE | VARCHAR2 | (120) | ||
| PAYEE_COUNTY | VARCHAR2 | (120) | ||
| PAYEE_COUNTRY | VARCHAR2 | (60) | ||
| REQUEST_ID | NUMBER | (15) |
APPS.IBY_PAYMENTS_SEC_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| TRANSACTIONID | NUMBER | Y | ||
| PAYEEID | VARCHAR2 | (80) | Y | |
| ECAPPID | NUMBER | (15) | Y | |
| SCHEDDATE | DATE | |||
| SCHEDMODE | VARCHAR2 | (7) | ||
| NLSLANG | VARCHAR2 | (80) | ||
| PAYMENTMETHODNAME | VARCHAR2 | (80) | ||
| TANGIBLEID | VARCHAR2 | (80) | Y | |
| AMOUNT | NUMBER | Y | ||
| CURRENCYNAMECODE | VARCHAR2 | (15) | Y | |
| ACCTNO | VARCHAR2 | (80) | ||
| REFINFO | VARCHAR2 | (80) | ||
| MEMO | VARCHAR2 | (80) | ||
| PAYERID | VARCHAR2 | (80) | ||
| PAYERINSTRID | NUMBER | |||
| INSTRTYPE | VARCHAR2 | (30) | ||
| ORG_ID | NUMBER | (15) | Organization identifier |
APPS.IBY_PAYMENTS_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ROW_ID | ROWID | (10) | ||
| PAYMENT_FORMAT_APL_FLAG | VARCHAR2 | (1) | Y | |
| LAST_UPDATE_DATE | DATE | Y | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| PAYMENT_METHOD_CODE | VARCHAR2 | (30) | Y | |
| CREATED_BY | NUMBER | (15) | Y | |
| CREATION_DATE | DATE | Y | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| OBJECT_VERSION_NUMBER | NUMBER | Y | ||
| BANK_CHARGE_BEARER_APL_FLAG | VARCHAR2 | (1) | Y | |
| PAYMENT_REASON_APL_FLAG | VARCHAR2 | (1) | Y | |
| PAYMENT_REASON_COMNT_APL_FLAG | VARCHAR2 | (1) | Y | |
| REMITTANCE_MESSAGE1_APL_FLAG | VARCHAR2 | (1) | Y | |
| REMITTANCE_MESSAGE2_APL_FLAG | VARCHAR2 | (1) | Y | |
| REMITTANCE_MESSAGE3_APL_FLAG | VARCHAR2 | (1) | Y | |
| UNIQUE_REMITTANCE_ID_APL_FLAG | VARCHAR2 | (1) | Y | |
| URI_CHECK_DIGIT_APL_FLAG | VARCHAR2 | (1) | Y | |
| DELIVERY_CHANNEL_APL_FLAG | VARCHAR2 | (1) | Y | |
| INACTIVE_DATE | DATE | |||
| ANTICIPATED_FLOAT | NUMBER | (15) | ||
| SETTLEMENT_PRIORITY_APL_FLAG | VARCHAR2 | (1) | Y | |
| EXCLUSIVE_PMT_APL_FLAG | VARCHAR2 | (1) | Y | |
| EXTERNAL_BANK_ACCT_APL_FLAG | VARCHAR2 | (1) | Y | |
| DOCUMENT_CATEGORY_CODE | VARCHAR2 | (30) | ||
| SUPPORT_BILLS_PAYABLE_FLAG | VARCHAR2 | (1) | Y | |
| MATURITY_DATE_OFFSET_DAYS | NUMBER | (15) | ||
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | ||
| ATTRIBUTE1 | VARCHAR2 | (150) | ||
| ATTRIBUTE2 | VARCHAR2 | (150) | ||
| ATTRIBUTE3 | VARCHAR2 | (150) | ||
| ATTRIBUTE4 | VARCHAR2 | (150) | ||
| ATTRIBUTE5 | VARCHAR2 | (150) | ||
| ATTRIBUTE6 | VARCHAR2 | (150) | ||
| ATTRIBUTE7 | VARCHAR2 | (150) | ||
| ATTRIBUTE8 | VARCHAR2 | (150) | ||
| ATTRIBUTE9 | VARCHAR2 | (150) | ||
| ATTRIBUTE10 | VARCHAR2 | (150) | ||
| ATTRIBUTE11 | VARCHAR2 | (150) | ||
| ATTRIBUTE12 | VARCHAR2 | (150) | ||
| ATTRIBUTE13 | VARCHAR2 | (150) | ||
| ATTRIBUTE14 | VARCHAR2 | (150) | ||
| ATTRIBUTE15 | VARCHAR2 | (150) | ||
| PAYMENT_METHOD_NAME | VARCHAR2 | (100) | Y | |
| DESCRIPTION | VARCHAR2 | (240) | ||
| SEEDED_FLAG | VARCHAR2 | (1) | ||
| FORMAT_VALUE | VARCHAR2 | (80) |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| SYSTEM_PROFILE_CODE | VARCHAR2 | (100) | Y | |
| SYSTEM_PROFILE_NAME | VARCHAR2 | (100) | Y | |
| SYSTEM_PROFILE_DESCRIPTION | VARCHAR2 | (255) | ||
| BEPID | NUMBER | (15) | ||
| SECURITY_PROTOCOL_CODE | VARCHAR2 | (100) | ||
| TRANSMIT_PROTOCOL_CODE | VARCHAR2 | (100) | ||
| PAYMENT_FORMAT_CODE | VARCHAR2 | (30) | Y | |
| POSITIVE_PAY_FORMAT_CODE | VARCHAR2 | (30) | ||
| PAY_FILE_LETTER_FORMAT_CODE | VARCHAR2 | (30) | ||
| PRINT_INSTRUCTION_IMMED_FLAG | VARCHAR2 | (1) | Y | |
| TRANSMIT_INSTR_IMMED_FLAG | VARCHAR2 | (1) | Y | |
| DEFAULT_PRINTER | VARCHAR2 | (255) | ||
| DEFAULT_PAYMENT_DOCUMENT_ID | NUMBER | (15) | ||
| PERIODIC_SEQUENCE_NAME_1 | VARCHAR2 | (80) | ||
| PERIODIC_SEQUENCE_NAME_2 | VARCHAR2 | (80) | ||
| PERIODIC_SEQUENCE_NAME_3 | VARCHAR2 | (80) | ||
| PROCESSING_TYPE | VARCHAR2 | (30) | Y | |
| MARK_COMPLETE_EVENT | VARCHAR2 | (30) | Y | |
| MANUAL_MARK_COMPLETE_FLAG | VARCHAR2 | (1) | Y | |
| LOGICAL_GROUPING_MODE | VARCHAR2 | (50) | Specifies the grouping mode of the payment process profile. | |
| BATCH_BOOKING_FLAG | VARCHAR2 | (1) | Specifies whether bank will send statement based on payment/group | |
| POSITIVE_PAY_DELIVERY_FLAG | VARCHAR2 | (1) | Y | |
| CREATED_BY | NUMBER | (15) | Y | |
| CREATION_DATE | DATE | Y | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| LAST_UPDATE_DATE | DATE | Y | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | |
| DECLARATION_OPTION | VARCHAR2 | (30) | ||
| DCL_ONLY_FOREIGN_CURR_PMT_FLAG | VARCHAR2 | (1) | ||
| DECLARATION_REPORT_NAME | VARCHAR2 | (30) | ||
| DECLARATION_CURR_FX_RATE_TYPE | VARCHAR2 | (255) | ||
| DECLARATION_CURRENCY_CODE | VARCHAR2 | (10) | ||
| DECLARATION_THRESHOLD_AMOUNT | NUMBER | |||
| BANK_INSTRUCTION1_CODE | VARCHAR2 | (30) | ||
| BANK_INSTRUCTION2_CODE | VARCHAR2 | (30) | ||
| BANK_INSTRUCTION_DETAILS | VARCHAR2 | (255) | ||
| PAYMENT_TEXT_MESSAGE1 | VARCHAR2 | (150) | ||
| PAYMENT_TEXT_MESSAGE2 | VARCHAR2 | (150) | ||
| INACTIVE_DATE | DATE | |||
| ACK_TRANSMIT_PROTOCOL_CODE | VARCHAR2 | (100) | ||
| ACK_SECURITY_PROTOCOL_CODE | VARCHAR2 | (100) | ||
| SEEDED_FLAG | VARCHAR2 | (1) | ||
| SEND_TO_FILE_FLAG | VARCHAR2 | (1) | Y | |
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | ||
| ATTRIBUTE1 | VARCHAR2 | (150) | ||
| ATTRIBUTE2 | VARCHAR2 | (150) | ||
| ATTRIBUTE3 | VARCHAR2 | (150) | ||
| ATTRIBUTE4 | VARCHAR2 | (150) | ||
| ATTRIBUTE5 | VARCHAR2 | (150) | ||
| ATTRIBUTE6 | VARCHAR2 | (150) | ||
| ATTRIBUTE7 | VARCHAR2 | (150) | ||
| ATTRIBUTE8 | VARCHAR2 | (150) | ||
| ATTRIBUTE9 | VARCHAR2 | (150) | ||
| ATTRIBUTE10 | VARCHAR2 | (150) | ||
| ATTRIBUTE11 | VARCHAR2 | (150) | ||
| ATTRIBUTE12 | VARCHAR2 | (150) | ||
| ATTRIBUTE13 | VARCHAR2 | (150) | ||
| ATTRIBUTE14 | VARCHAR2 | (150) | ||
| ATTRIBUTE15 | VARCHAR2 | (150) | ||
| PAYMENT_PROFILE_ID | NUMBER | (15) | ||
| PAYMENT_PROFILE_NAME | VARCHAR2 | (100) | ||
| BEP_ACCOUNT_ID | NUMBER | (15) | ||
| SECURITY_CONFIGURATION_ID | NUMBER | (15) | ||
| TRANSMIT_CONFIGURATION_ID | NUMBER | (15) | ||
| RESET_VALUE_1 | NUMBER | (15) | ||
| LAST_USED_NUMBER_1 | NUMBER | (15) | ||
| RESET_REQUEST_1 | NUMBER | (15) | ||
| RESET_VALUE_2 | NUMBER | (15) | ||
| LAST_USED_NUMBER_2 | NUMBER | (15) | ||
| RESET_REQUEST_2 | NUMBER | (15) | ||
| RESET_VALUE_3 | NUMBER | (15) | ||
| LAST_USED_NUMBER_3 | NUMBER | (15) | ||
| RESET_REQUEST_3 | NUMBER | (15) | ||
| ACK_SEC_CONFIG_ID | NUMBER | (15) | ||
| ACK_TRANSMIT_CONFIG_ID | NUMBER | (15) | ||
| OUTBOUND_PMT_FILE_DIRECTORY | VARCHAR2 | (255) | File directory where output of outbound payment file should be stored. | |
| OUTBOUND_PMT_FILE_EXTENSION | VARCHAR2 | (255) | File extension of outbound payment files. | |
| OUTBOUND_PMT_FILE_PREFIX | VARCHAR2 | (255) | File name prefix of outbound payment files. | |
| POSITIVE_PAY_FILE_DIRECTORY | VARCHAR2 | (255) | File directory where output of positive pay file should be stored. | |
| POSITIVE_PAY_FILE_EXTENSION | VARCHAR2 | (255) | File extension of positive pay files. | |
| POSITIVE_PAY_FILE_PREFIX | VARCHAR2 | (255) | File name prefix of positive pay files. | |
| ELECTRONIC_PROCESSING_CHANNEL | VARCHAR2 | (50) | ||
| DISALLOW_SAVE_PRINT_FLAG | VARCHAR2 | (1) |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ROW_ID | ROWID | (10) | ||
| PAYMENT_REASON_CODE | VARCHAR2 | (30) | Y | |
| FORMAT_VALUE | VARCHAR2 | (80) | ||
| TERRITORY_CODE | VARCHAR2 | (2) | ||
| INACTIVE_DATE | DATE | |||
| CREATED_BY | NUMBER | (15) | Y | |
| CREATION_DATE | DATE | Y | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| LAST_UPDATE_DATE | DATE | Y | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| OBJECT_VERSION_NUMBER | NUMBER | Y | ||
| MEANING | VARCHAR2 | (80) | ||
| DESCRIPTION | VARCHAR2 | (240) | ||
| SEEDED_FLAG | VARCHAR2 | (1) |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ATTRIBUTE14 | VARCHAR2 | (150) | ||
| ATTRIBUTE15 | VARCHAR2 | (150) | ||
| REGULATORY_REPORT_CREATED_FLAG | VARCHAR2 | (1) | Y | |
| LEGAL_ENTITY_ID | NUMBER | (15) | ||
| PAYMENT_COUNT | NUMBER | (15) | Y | |
| CREATED_BY | NUMBER | (15) | Y | |
| CREATION_DATE | DATE | Y | ||
| REMITTANCE_ADVICE_CREATED_FLAG | VARCHAR2 | (1) | Y | |
| ATTRIBUTE13 | VARCHAR2 | (150) | ||
| PAYMENT_INSTRUCTION_ID | NUMBER | (15) | Y | |
| PAYMENT_PROFILE_ID | NUMBER | (15) | Y | |
| PROCESS_TYPE | VARCHAR2 | (30) | Y | |
| PAYMENT_INSTRUCTION_STATUS | VARCHAR2 | (30) | Y | |
| PAYMENTS_COMPLETE_CODE | VARCHAR2 | (30) | Y | |
| GENERATE_SEP_REMIT_ADVICE_FLAG | VARCHAR2 | (1) | Y | |
| ATTRIBUTE8 | VARCHAR2 | (150) | ||
| ATTRIBUTE9 | VARCHAR2 | (150) | ||
| ATTRIBUTE10 | VARCHAR2 | (150) | ||
| ATTRIBUTE11 | VARCHAR2 | (150) | ||
| ATTRIBUTE12 | VARCHAR2 | (150) | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| LAST_UPDATE_DATE | DATE | Y | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| OBJECT_VERSION_NUMBER | NUMBER | Y | ||
| INTERNAL_BANK_ACCOUNT_ID | NUMBER | (15) | ||
| PAY_ADMIN_ASSIGNED_REF_CODE | VARCHAR2 | (255) | ||
| TRANSMISSION_DATE | DATE | |||
| ACKNOWLEDGEMENT_DATE | DATE | |||
| COMMENTS | VARCHAR2 | (240) | ||
| BANK_ASSIGNED_REF_CODE | VARCHAR2 | (30) | ||
| ORG_ID | NUMBER | (15) | ||
| ORG_TYPE | VARCHAR2 | (30) | ||
| PAYMENT_DATE | DATE | |||
| PAYMENT_CURRENCY_CODE | VARCHAR2 | (10) | ||
| PAYMENT_SERVICE_REQUEST_ID | NUMBER | (15) | ||
| PAYMENT_FUNCTION | VARCHAR2 | (30) | ||
| PAYMENT_REASON_CODE | VARCHAR2 | (30) | ||
| BILL_PAYABLE_FLAG | VARCHAR2 | (1) | Y | |
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | ||
| ATTRIBUTE1 | VARCHAR2 | (150) | ||
| ATTRIBUTE2 | VARCHAR2 | (150) | ||
| ATTRIBUTE3 | VARCHAR2 | (150) | ||
| ATTRIBUTE4 | VARCHAR2 | (150) | ||
| ATTRIBUTE5 | VARCHAR2 | (150) | ||
| ATTRIBUTE6 | VARCHAR2 | (150) | ||
| ATTRIBUTE7 | VARCHAR2 | (150) | ||
| POSITIVE_PAY_FILE_CREATED_FLAG | VARCHAR2 | (1) | Y | |
| RFC_IDENTIFIER | VARCHAR2 | (30) | ||
| PAYMENT_REASON_COMMENTS | VARCHAR2 | (240) | ||
| PAYMENT_DOCUMENT_ID | NUMBER | (15) | ||
| PRINT_INSTRUCTION_IMMED_FLAG | VARCHAR2 | (1) | Y | |
| TRANSMIT_INSTR_IMMED_FLAG | VARCHAR2 | (1) | Y | |
| PRINTER_NAME | VARCHAR2 | (255) | ||
| REQUEST_ID | NUMBER | (15) |
APPS.IBY_PAY_INSTRUCTIONS_SEC_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYMENT_SERVICE_REQUEST_ID | NUMBER | (15) | Y | |
| CALLING_APP_ID | NUMBER | (15) | Y | |
| CALL_APP_PAY_SERVICE_REQ_CODE | VARCHAR2 | (255) | Y | |
| PAYMENT_SERVICE_REQUEST_STATUS | VARCHAR2 | (30) | Y | |
| PROCESS_TYPE | VARCHAR2 | (30) | Y | |
| ALLOW_ZERO_PAYMENTS_FLAG | VARCHAR2 | (1) | Y | |
| CREATED_BY | NUMBER | (15) | Y | |
| CREATION_DATE | DATE | Y | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| LAST_UPDATE_DATE | DATE | Y | ||
| OBJECT_VERSION_NUMBER | NUMBER | Y | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| INTERNAL_BANK_ACCOUNT_ID | NUMBER | (15) | ||
| PAYMENT_PROFILE_ID | NUMBER | (15) | ||
| MAXIMUM_PAYMENT_AMOUNT | NUMBER | |||
| MINIMUM_PAYMENT_AMOUNT | NUMBER | |||
| DOCUMENT_REJECTION_LEVEL_CODE | VARCHAR2 | (30) | ||
| PAYMENT_REJECTION_LEVEL_CODE | VARCHAR2 | (30) | ||
| REQUIRE_PROP_PMTS_REVIEW_FLAG | VARCHAR2 | (1) | ||
| ORG_TYPE | VARCHAR2 | (30) | ||
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | ||
| ATTRIBUTE1 | VARCHAR2 | (150) | ||
| ATTRIBUTE2 | VARCHAR2 | (150) | ||
| ATTRIBUTE3 | VARCHAR2 | (150) | ||
| ATTRIBUTE4 | VARCHAR2 | (150) | ||
| ATTRIBUTE5 | VARCHAR2 | (150) | ||
| ATTRIBUTE6 | VARCHAR2 | (150) | ||
| ATTRIBUTE7 | VARCHAR2 | (150) | ||
| ATTRIBUTE8 | VARCHAR2 | (150) | ||
| ATTRIBUTE9 | VARCHAR2 | (150) | ||
| ATTRIBUTE10 | VARCHAR2 | (150) | ||
| ATTRIBUTE11 | VARCHAR2 | (150) | ||
| ATTRIBUTE12 | VARCHAR2 | (150) | ||
| ATTRIBUTE13 | VARCHAR2 | (150) | ||
| ATTRIBUTE14 | VARCHAR2 | (150) | ||
| ATTRIBUTE15 | VARCHAR2 | (150) | ||
| REQUEST_ID | NUMBER | (15) |
APPS.IBY_PAY_REQUEST_SEC_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| SCORE_TYPE | VARCHAR2 | (30) | Y | |
| MEANING | VARCHAR2 | (80) | Y | |
| SEQ | NUMBER | (5) |
APPS.IBY_PA_RSTYPES_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| DURATION_TYPE | VARCHAR2 | (30) | Y | |
| MEANING | VARCHAR2 | (80) | Y |
APPS.IBY_PH_DTYPES_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| SCORE_TYPE | VARCHAR2 | (30) | Y | |
| MEANING | VARCHAR2 | (80) | Y | |
| SEQ | NUMBER | (5) |
APPS.IBY_PH_RSTYPES_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| DOCUMENT_CONTENT | XMLTYPE | (40) | ||
| CALLING_APP_ID | NUMBER | (15) | Y | |
| PAYMENT_ID | NUMBER | (15) | Y | |
| PAYMENT_STATUS | VARCHAR2 | (30) | Y | |
| PAY_REQ_ID | NUMBER | (15) | Y | |
| REQUEST_STATUS | VARCHAR2 | (30) | Y |
APPS.IBY_PMT_FAILED_DOCS_XML_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| CLEARED_CONTENT | XMLTYPE | (40) | ||
| INSTRUCTION_ID | NUMBER | (15) | Y | |
| INSTRUCTION_STATUS | VARCHAR2 | (30) | Y |
APPS.IBY_PMT_LVL_PMT_STS_CHG_XML_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PARTY_ID | NUMBER | (15) | Y | |
| PARTY_NUMBER | VARCHAR2 | (30) | Y | |
| PARTY_NAME | VARCHAR2 | (360) | Y | |
| PARTY_LEGAL_ID | NUMBER | (15) | Y | |
| PARTY_LEGAL_NAME | VARCHAR2 | (240) | Y | |
| PARTY_TAX_ID | VARCHAR2 | (60) | ||
| PARTY_TYPE_CODE | VARCHAR2 | (30) | Y | |
| PARTY_TYPE | VARCHAR2 | (0) | ||
| PARTY_ADDRESS_ID | VARCHAR2 | (0) | ||
| PARTY_REGISTRATION_NUMBER | VARCHAR2 | (30) | Y | |
| PARTY_ADDRESS_LINE1 | VARCHAR2 | (240) | ||
| PARTY_ADDRESS_LINE2 | VARCHAR2 | (240) | ||
| PARTY_ADDRESS_LINE3 | VARCHAR2 | (0) | ||
| PARTY_ADDRESS_CITY | VARCHAR2 | (30) | ||
| PARTY_ADDRESS_COUNTY | VARCHAR2 | (0) | ||
| PARTY_ADDRESS_STATE | VARCHAR2 | (120) | ||
| PARTY_ADDRESS_COUNTRY | VARCHAR2 | (60) | ||
| PARTY_ADDRESS_POSTAL_CODE | VARCHAR2 | (30) | ||
| PARTY_PHONE | VARCHAR2 | (0) | ||
| PARTY_FAX | VARCHAR2 | (0) | ||
| PARTY_EMAIL | VARCHAR2 | (0) | ||
| PARTY_WEBSITE | VARCHAR2 | (0) |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| NEED_ACTION | NUMBER | |||
| PROCESSING | NUMBER | |||
| TERMINATED | NUMBER | |||
| ERRORS | NUMBER | |||
| COMPLETED | NUMBER |
APPS.IBY_PSR_SNAPSHOT_COUNT is not referenced by any database object
A public view which may be useful for custom reporting or other data requirements.
View used to work with registered purchase cards.
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| INSTRID | NUMBER | (15) | Y | ID that iPayment uses to identify a registered purchase card. |
| PCNUMBER | VARCHAR2 | (30) | Y | Purchase card number. |
| EXPIRYDATE | DATE | Date after which the purchase card expires. | ||
| FINAME | VARCHAR2 | (80) | The name of the financial institution (bank) that issued the card. | |
| ACCTTYPE | VARCHAR2 | (30) | Type of purchase card account. | |
| CHNAME | VARCHAR2 | (80) | Card holder name. | |
| INSTRNAME | VARCHAR2 | (80) | Mnemonic for a registered purchase card. | |
| SUBTYPE | VARCHAR2 | (80) | Subtype of purchase card (e.g. commercial card, business card, etc.). | |
| OWNERTYPE | VARCHAR2 | (20) | Y | The type of the account holder. |
| OWNERID | VARCHAR2 | (80) | Y | ID that iPayment uses to identify purchase. |
| INSTRBUF | VARCHAR2 | (240) | Description of registered purchase card. | |
| ENCRYPTED | VARCHAR2 | (1) | Indicates if the instrument is encrypted |
APPS.IBY_PURCHASECARD_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| SCORE_TYPE | VARCHAR2 | (30) | Y | |
| MEANING | VARCHAR2 | (80) | Y | |
| SEQ | NUMBER | (5) |
APPS.IBY_RC_RSTYPES_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| DOCUMENT_CONTENT | XMLTYPE | (40) | ||
| PAY_REQ_ID | NUMBER | (15) | Y | |
| REQUEST_STATUS | VARCHAR2 | (30) | Y |
APPS.IBY_REJECTED_DOCS_XML_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| REQUEST_CONTENT | XMLTYPE | (40) | ||
| CALLING_APP_ID | NUMBER | (15) | Y | |
| PAY_SERVICE_REQUEST_ID | NUMBER | (15) | Y | |
| REQUEST_STATUS | VARCHAR2 | (30) | Y |
APPS.IBY_REJECT_REQ_XML_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ROW_ID | ROWID | (10) | ||
| TASK_CODE | VARCHAR2 | (30) | Y | |
| TASK_NAME | VARCHAR2 | (100) | ||
| STATUS | VARCHAR2 | (30) | ||
| DESCRIPTION | VARCHAR2 | (240) | ||
| LEAF_NODE_FLAG | VARCHAR2 | (1) | Y | |
| PARENT_TASK_CODE | VARCHAR2 | (30) | ||
| DEST_FUNCTION_NAME | VARCHAR2 | (100) | ||
| SETUP_FLOW_CODE | VARCHAR2 | (30) | ||
| DISPLAY_ORDER | NUMBER | (15) | ||
| CREATED_BY | NUMBER | (15) | Y | |
| CREATION_DATE | DATE | Y | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| LAST_UPDATE_DATE | DATE | Y | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y |
APPS.IBY_SETUP_TASKS_VL is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| DOCUMENT_CONTENT | XMLTYPE | (40) | ||
| CALLING_APP_ID | NUMBER | (15) | Y | |
| DOCUMENT_ID | NUMBER | (15) | Y | |
| DOCUMENT_STATUS | VARCHAR2 | (30) | Y |
APPS.IBY_SINGLE_REJECTED_DOC_XML_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ROW_ID | ROWID | (10) | ||
| SYSTEM_PROFILE_CODE | VARCHAR2 | (100) | Y | |
| SYSTEM_PROFILE_NAME | VARCHAR2 | (100) | Y | |
| SYSTEM_PROFILE_DESCRIPTION | VARCHAR2 | (255) | ||
| BEPID | NUMBER | (15) | ||
| SECURITY_PROTOCOL_CODE | VARCHAR2 | (100) | ||
| TRANSMIT_PROTOCOL_CODE | VARCHAR2 | (100) | ||
| PAYMENT_FORMAT_CODE | VARCHAR2 | (30) | Y | |
| POSITIVE_PAY_FORMAT_CODE | VARCHAR2 | (30) | ||
| PAY_FILE_LETTER_FORMAT_CODE | VARCHAR2 | (30) | ||
| PRINT_INSTRUCTION_IMMED_FLAG | VARCHAR2 | (1) | Y | |
| TRANSMIT_INSTR_IMMED_FLAG | VARCHAR2 | (1) | Y | |
| DEFAULT_PRINTER | VARCHAR2 | (255) | ||
| DEFAULT_PAYMENT_DOCUMENT_ID | NUMBER | (15) | ||
| PERIODIC_SEQUENCE_NAME_1 | VARCHAR2 | (80) | ||
| PERIODIC_SEQUENCE_NAME_2 | VARCHAR2 | (80) | ||
| PERIODIC_SEQUENCE_NAME_3 | VARCHAR2 | (80) | ||
| PROCESSING_TYPE | VARCHAR2 | (30) | Y | |
| MARK_COMPLETE_EVENT | VARCHAR2 | (30) | Y | |
| MANUAL_MARK_COMPLETE_FLAG | VARCHAR2 | (1) | Y | |
| LOGICAL_GROUPING_MODE | VARCHAR2 | (50) | Specifies the grouping mode of the payment process profile | |
| BATCH_BOOKING_FLAG | VARCHAR2 | (1) | Specifies whether bank will send statement based on payment/group | |
| POSITIVE_PAY_DELIVERY_FLAG | VARCHAR2 | (1) | Y | |
| CREATED_BY | NUMBER | (15) | Y | |
| CREATION_DATE | DATE | Y | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| LAST_UPDATE_DATE | DATE | Y | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | |
| DECLARATION_OPTION | VARCHAR2 | (30) | ||
| DCL_ONLY_FOREIGN_CURR_PMT_FLAG | VARCHAR2 | (1) | ||
| DECLARATION_REPORT_FORMAT_CODE | VARCHAR2 | (30) | ||
| DECLARATION_CURR_FX_RATE_TYPE | VARCHAR2 | (255) | ||
| DECLARATION_CURRENCY_CODE | VARCHAR2 | (10) | ||
| DECLARATION_THRESHOLD_AMOUNT | NUMBER | |||
| BANK_INSTRUCTION1_CODE | VARCHAR2 | (30) | ||
| BANK_INSTRUCTION2_CODE | VARCHAR2 | (30) | ||
| BANK_INSTRUCTION_DETAILS | VARCHAR2 | (255) | ||
| PAYMENT_TEXT_MESSAGE1 | VARCHAR2 | (150) | ||
| PAYMENT_TEXT_MESSAGE2 | VARCHAR2 | (150) | ||
| INACTIVE_DATE | DATE | |||
| ACK_TRANSMIT_PROTOCOL_CODE | VARCHAR2 | (100) | ||
| ACK_SECURITY_PROTOCOL_CODE | VARCHAR2 | (100) | ||
| SEEDED_FLAG | VARCHAR2 | (1) | ||
| SEND_TO_FILE_FLAG | VARCHAR2 | (1) | Y | |
| ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | ||
| ATTRIBUTE1 | VARCHAR2 | (150) | ||
| ATTRIBUTE2 | VARCHAR2 | (150) | ||
| ATTRIBUTE3 | VARCHAR2 | (150) | ||
| ATTRIBUTE4 | VARCHAR2 | (150) | ||
| ATTRIBUTE5 | VARCHAR2 | (150) | ||
| ATTRIBUTE6 | VARCHAR2 | (150) | ||
| ATTRIBUTE7 | VARCHAR2 | (150) | ||
| ATTRIBUTE8 | VARCHAR2 | (150) | ||
| ATTRIBUTE9 | VARCHAR2 | (150) | ||
| ATTRIBUTE10 | VARCHAR2 | (150) | ||
| ATTRIBUTE11 | VARCHAR2 | (150) | ||
| ATTRIBUTE12 | VARCHAR2 | (150) | ||
| ATTRIBUTE13 | VARCHAR2 | (150) | ||
| ATTRIBUTE14 | VARCHAR2 | (150) | ||
| ATTRIBUTE15 | VARCHAR2 | (150) | ||
| PI_REGISTER_FORMAT | VARCHAR2 | (30) | ||
| AUTOMATIC_PI_REG_SUBMIT | VARCHAR2 | (1) | Y | |
| OUTBOUND_PMT_FILE_DIRECTORY | VARCHAR2 | (255) | File directory where output of outbound payment file should be stored. | |
| OUTBOUND_PMT_FILE_EXTENSION | VARCHAR2 | (255) | File extension of outbound payment files. | |
| OUTBOUND_PMT_FILE_PREFIX | VARCHAR2 | (255) | File name prefix of outbound payment files. | |
| POSITIVE_PAY_FILE_DIRECTORY | VARCHAR2 | (255) | File directory where output of positive pay file should be stored. | |
| POSITIVE_PAY_FILE_EXTENSION | VARCHAR2 | (255) | File extension of positive pay files. | |
| POSITIVE_PAY_FILE_PREFIX | VARCHAR2 | (255) | File name prefix of positive pay files. | |
| ELECTRONIC_PROCESSING_CHANNEL | VARCHAR2 | (50) | ||
| DISALLOW_SAVE_PRINT_FLAG | VARCHAR2 | (1) |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| DURATION_TYPE | VARCHAR2 | (30) | Y | |
| MEANING | VARCHAR2 | (80) | Y |
APPS.IBY_TAL_DTYPES_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| SCORE_TYPE | VARCHAR2 | (30) | Y | |
| MEANING | VARCHAR2 | (80) | Y | |
| SEQ | NUMBER | (5) |
APPS.IBY_TAL_RSTYPES_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| SCORE_TYPE | VARCHAR2 | (30) | Y | |
| MEANING | VARCHAR2 | (80) | Y | |
| SEQ | NUMBER | (5) |
APPS.IBY_TOP_RSTYPES_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ORDER_ID | VARCHAR2 | (80) | Y | |
| MERCHANT_ID | VARCHAR2 | (80) | Y | |
| VENDOR_ID | NUMBER | (15) | ||
| TRXN_TYPE | NUMBER | (15) | ||
| AMOUNT | NUMBER | |||
| CURRENCY | VARCHAR2 | (15) | ||
| TIME | DATE | |||
| STATUS | NUMBER | (15) | Y | |
| SPLIT_ID | NUMBER | |||
| SET_TRXN_ID | VARCHAR2 | (80) | ||
| BATCH_ID | VARCHAR2 | (80) | ||
| BATCH_SEQ_NUM | NUMBER | |||
| BATCH_TRXN_STATUS | NUMBER | |||
| COMPLETION_CODE | VARCHAR2 | (80) | ||
| CARD_BIN | VARCHAR2 | (10) | ||
| TERMINAL_ID | VARCHAR2 | (80) | ||
| REQUEST_TYPE | NUMBER | |||
| SUBSEQ_AUTH_IND | NUMBER | |||
| ERROR_LOCATION | NUMBER | |||
| VENDOR_CODE | VARCHAR2 | (40) | ||
| VENDOR_MESSAGE | VARCHAR2 | (255) | ||
| ORG_ID | NUMBER | (15) | Organization identifier |
APPS.IBY_TRANSACTIONS_SET_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ORDER_ID | VARCHAR2 | (80) | Y | TANGIBLEID is the bill or order ID |
| BEPKEY | VARCHAR2 | (80) | BEPKEY is the Bep Key (merchant account ID) used with this transaction | |
| MERCHANT_ID | VARCHAR2 | (80) | Y | Payee Identifier |
| VENDOR_ID | NUMBER | (15) | ||
| TRXN_TYPE | NUMBER | (15) | ||
| AMOUNT | NUMBER | |||
| CURRENCY | VARCHAR2 | (15) | ||
| TIME | DATE | |||
| STATUS | NUMBER | (15) | Y | |
| PAYMENT_TYPE | VARCHAR2 | (80) | ||
| MERCHBATCHID | VARCHAR2 | (80) | ||
| PAYMENT_NAME | VARCHAR2 | (80) | ||
| AUTHCODE | VARCHAR2 | (80) | ||
| AVSCODE | VARCHAR2 | (80) | ||
| REFERENCECODE | VARCHAR2 | (80) | ||
| ERROR_LOCATION | NUMBER | |||
| VENDOR_CODE | VARCHAR2 | (40) | ||
| ACQUIRER | VARCHAR2 | (80) | ||
| VENDOR_MESSAGE | VARCHAR2 | (255) | ||
| AUXMSG | VARCHAR2 | (255) | ||
| TERMINALID | VARCHAR2 | (80) | ||
| TRACENUMBER | VARCHAR2 | (80) | ||
| ORG_ID | NUMBER | (15) | Organization identifier |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ROW_ID | ROWID | (10) | ||
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | |
| TUNNELING_TRANS_CONFIG_ID | NUMBER | (15) | ||
| TRANSMIT_CONFIGURATION_ID | NUMBER | (15) | Y | |
| TRANSMIT_PROTOCOL_CODE | VARCHAR2 | (30) | Y | |
| INACTIVE_DATE | DATE | |||
| CREATED_BY | NUMBER | (15) | Y | |
| CREATION_DATE | DATE | Y | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| LAST_UPDATE_DATE | DATE | Y | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | Y | |
| TRANSMIT_CONFIGURATION_NAME | VARCHAR2 | (100) | Y |
APPS.IBY_TRANSMIT_CONFIGS_VL is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ROW_ID | ROWID | (10) | ||
| TRANSMIT_PARAMETER_CODE | VARCHAR2 | (30) | Y | |
| TRANSMIT_PARAMETER_TYPE | VARCHAR2 | (30) | Y | |
| TRANSMIT_PROTOCOL_CODE | VARCHAR2 | (30) | Y | |
| MANDATORY_FLAG | VARCHAR2 | (1) | Y | |
| CREATED_BY | NUMBER | (15) | Y | |
| CREATION_DATE | DATE | Y | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| LAST_UPDATE_DATE | DATE | Y | ||
| DISPLAY_ORDER | NUMBER | (15) | Y | |
| DYNAMIC_FLAG | VARCHAR2 | (1) | ||
| DYN_CODE_LANGUAGE | VARCHAR2 | (30) | ||
| DYN_CODE_PACKAGE | VARCHAR2 | (255) | ||
| DYN_CODE_ENTRY_POINT | VARCHAR2 | (255) | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | |
| TRANSMIT_PARAMETER_NAME | VARCHAR2 | (100) | Y | |
| SECURED_FLAG | VARCHAR2 | (1) |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ROW_ID | ROWID | (10) | ||
| LAST_UPDATE_DATE | DATE | Y | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | |
| TRANSMIT_PROTOCOL_CODE | VARCHAR2 | (30) | Y | |
| TRANSMIT_CODE_LANGUAGE | VARCHAR2 | (30) | ||
| TRANSMIT_CODE_PACKAGE | VARCHAR2 | (255) | ||
| TRANSMIT_CODE_ENTRY_POINT | VARCHAR2 | (255) | ||
| CREATED_BY | NUMBER | (15) | Y | |
| CREATION_DATE | DATE | Y | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| TRANSMIT_PROTOCOL_NAME | VARCHAR2 | (100) | Y |
APPS.IBY_TRANSMIT_PROTOCOLS_VL is not referenced by any database object
A public view which may be useful for custom reporting or other data requirements.
IBY_TRANS_ALL view allows a merchant or business to view transactional detail.
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| TRANSACTIONID | NUMBER | Y | TRANSACTIONID is the ID generated for each payment request (orapmtreq) and passed back to ECApp. | |
| TANGIBLEID | VARCHAR2 | (80) | Y | TANGIBLEID is the bill or order ID |
| PAYEEID | VARCHAR2 | (80) | Y | Payee Identifier |
| BEPID | NUMBER | (15) | BEP Identifier | |
| ECAPPID | NUMBER | (15) | Y | ECAPP Identifier |
| TRXNMID | NUMBER | Y | TRXNMID is system generated ID | |
| AMOUNT | NUMBER | Transaction Amount | ||
| CURRENCYNAMECODE | VARCHAR2 | (15) | CURRENCYNAMECODE is the code for currency name such USD | |
| REQDATE | DATE | REQDATE is the date when the batch operation request is received | ||
| REQTYPE | VARCHAR2 | (20) | REQTYPE is the type of request such as closebatch, purgebatch, openbatch | |
| STATUS | NUMBER | (15) | Y | Status of the transaction |
| SETTLEDATE | DATE | SETTLEDATE is the scheduled date for the bill or order used for offline payments only | ||
| UPDATEDATE | DATE | UPDATEDATE is the date scheduled payment is updated | ||
| TRXNTYPEID | NUMBER | (15) | The TRXTYPE columns is a Lookup code for lookup type IBY_TRXNTYPES | |
| TRXNREF | VARCHAR2 | (240) | Optional, secondary transaction identifier to be passed by calling application; useful in distinguishing transactions when the tangible/order id must be shared. | |
| ERRORLOCATION | NUMBER | ERRORLOCATION is numeric code for where the error occured. | ||
| BEPCODE | VARCHAR2 | (40) | BEPCODE is any BEP specific code | |
| BEPMESSAGE | VARCHAR2 | (255) | BEPMESSAGE is Payment System specific message | |
| BATCHID | VARCHAR2 | (80) | Batch Identifier | |
| NEEDSUPDT | VARCHAR2 | (3) | NEEDSUPDT is a flag to identify the rows that has changed status. Used by Schedular | |
| ORG_ID | NUMBER | (15) | Organization identifier | |
| PAYMENTMETHODNAME | VARCHAR2 | (80) | Payment Method Name | |
| MTANGIBLEID | NUMBER | Y | MTANGIBLEID is the master id that points to iby_tangible table for additional information about tangible | |
| DETAILLOOKUP | VARCHAR2 | (30) | DETAILLOOKUP is a lookup column for CORE, EXTENDED or FI | |
| REQSEQ | NUMBER | (4) | Request Sequence | |
| DESTURL | VARCHAR2 | (1024) | DESTURL is used for storing the constructed bep url during schedule of Payments | |
| NLSLANG | VARCHAR2 | (80) | NLS Language | |
| TERMINALID | VARCHAR2 | (80) | Terminal Id is a concept for credit card processing. A merchant can get multiple terminal Ids and there is a batch open for each Terminal Id. The merchant could perform operations on those batches independantly. | |
| TRACENUMBER | VARCHAR2 | (80) | Unique Transaction id for payworks BEP follow-on transactions | |
| AUTHCODE | VARCHAR2 | (80) | AUTHCODE is the authorization code received from Credit Card Processing System for authorization. | |
| REFERENCECODE | VARCHAR2 | (80) | REFERENCECODE is any reference code received from Payment Systems or processing system which can be used for reference. | |
| OPERATIONCODE | VARCHAR2 | (80) | OPERATIONCODE is generic code for any operation such as auth, capture etc | |
| INSTRNAME | VARCHAR2 | (80) | INSTRNAME is the payment instrument name such as Visa, MasterCard etc. | |
| AUTHTYPE | VARCHAR2 | (20) | AUTHTYPE denotes whether authorization is authonly or authcapture. | |
| AVSCODE | VARCHAR2 | (80) | AVSCODE is the Address Verification Code from payment systems. | |
| ACQUIRER | VARCHAR2 | (80) | ACQUIRER is the merchant bank which may be optionally returned. | |
| AUXMSG | VARCHAR2 | (255) | AUXMSG is any auxillary message that may be returned by the payment system or processing system. | |
| ACCTNO | VARCHAR2 | (80) | ACCTNO is customer account number with the biller or merchant | |
| REFINFO | VARCHAR2 | (80) | REFINFO is any reference information passed by the ECApp | |
| MEMO | VARCHAR2 | (80) | MEMO is any memo for the payment | |
| ORDER_MEDIUM | VARCHAR2 | (30) | Medium or channel through which the order was sent. Possible values defined by lookup IBY_ORDER_MEDIUM_TYPE. | |
| EFT_AUTH_METHOD | VARCHAR2 | (30) | Electronic funds transfer authorization method |
APPS.IBY_TRANS_ALL_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| BEPKEY | VARCHAR2 | (80) | BEPKEY is the Bep Key (merchant account ID) used with this transaction | |
| TRANSACTIONID | NUMBER | Y | ||
| PAYEEID | VARCHAR2 | (80) | Y | |
| BEPID | NUMBER | (15) | ||
| ECAPPID | NUMBER | (15) | Y | |
| TRXNMID | NUMBER | Y | ||
| PAYERID | VARCHAR2 | (80) | ||
| PAYERINSTRID | NUMBER | |||
| REQDATE | DATE | |||
| REQTYPE | VARCHAR2 | (20) | ||
| STATUS | NUMBER | (15) | Y | |
| SETTLEDATE | DATE | |||
| UPDATEDATE | DATE | |||
| TRXNTYPEID | NUMBER | (15) | ||
| ERRORLOCATION | NUMBER | |||
| BEPCODE | VARCHAR2 | (40) | ||
| BEPMESSAGE | VARCHAR2 | (255) | ||
| BATCHID | VARCHAR2 | (80) | ||
| NEEDSUPDT | VARCHAR2 | (3) | ||
| DESTURL | VARCHAR2 | (1024) | ||
| PAYMENTMETHODNAME | VARCHAR2 | (80) | ||
| AMOUNT | NUMBER | |||
| CURRENCYNAMECODE | VARCHAR2 | (15) | Y | |
| ACCTNO | VARCHAR2 | (80) | ||
| REFINFO | VARCHAR2 | (80) | ||
| MEMO | VARCHAR2 | (80) | ||
| TANGIBLEID | VARCHAR2 | (80) | Y | |
| PMTSCHEMEID | NUMBER | (15) | Y | |
| REFERENCECODE | VARCHAR2 | (80) | ||
| SRVID | VARCHAR2 | (80) | ||
| PSREQID | VARCHAR2 | (80) | ||
| PROCESSFEE | NUMBER | |||
| SPLITID | NUMBER | Y | ||
| BANKACCOUNTID | VARCHAR2 | (80) | Y | |
| ADDRESSID | NUMBER | |||
| FINAME | VARCHAR2 | (80) | ||
| ACCTTYPEID | NUMBER | Y | ||
| BRANCHNAME | VARCHAR2 | (60) | ||
| ROUTINGNO | VARCHAR2 | (25) | ||
| INSTRNAME | VARCHAR2 | (80) | ||
| ACCOUNT_HOLDER_NAME | VARCHAR2 | (240) | ||
| ORG_ID | NUMBER | (15) | Organization identifier | |
| NLSLANG | VARCHAR2 | (80) | ||
| KEY | VARCHAR2 | (80) | Y | |
| ACCTTYPE | VARCHAR2 | (30) | ||
| PAYEENAME | VARCHAR2 | (80) | Y | |
| ORDER_MEDIUM | VARCHAR2 | (30) | Medium or channel through which the order was sent. Possible values defined by lookup IBY_ORDER_MEDIUM_TYPE. | |
| EFT_AUTH_METHOD | VARCHAR2 | (30) |
APPS.IBY_TRANS_BANKACCT_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| TRANSACTIONID | NUMBER | Y | ||
| BEPKEY | VARCHAR2 | (80) | BEPKEY is the Bep Key (merchant account ID) used with this transaction | |
| PAYEEID | VARCHAR2 | (80) | Y | |
| BEPID | NUMBER | (15) | ||
| ECAPPID | NUMBER | (15) | Y | |
| TRXNMID | NUMBER | Y | ||
| PAYERID | VARCHAR2 | (80) | ||
| PAYERINSTRID | NUMBER | |||
| PROFCODE | VARCHAR2 | (30) | ||
| CHNAME | VARCHAR2 | (80) | ||
| CCNUMBER | VARCHAR2 | (30) | ||
| EXPIRYDATE | DATE | |||
| ENCRYPTED | VARCHAR2 | (1) | ||
| ACCTTYPE | VARCHAR2 | (30) | ||
| REQDATE | DATE | |||
| REQTYPE | VARCHAR2 | (20) | ||
| STATUS | NUMBER | (15) | Y | |
| SETTLEDATE | DATE | |||
| UPDATEDATE | DATE | |||
| TRXNTYPEID | NUMBER | (15) | ||
| ERRORLOCATION | NUMBER | |||
| BEPCODE | VARCHAR2 | (40) | ||
| BEPMESSAGE | VARCHAR2 | (255) | ||
| BATCHID | VARCHAR2 | (80) | ||
| NEEDSUPDT | VARCHAR2 | (3) | ||
| DESTURL | VARCHAR2 | (1024) | ||
| PAYMENTMETHODNAME | VARCHAR2 | (80) | ||
| AMOUNT | NUMBER | |||
| CURRENCYNAMECODE | VARCHAR2 | (15) | ||
| ACCTNO | VARCHAR2 | (80) | ||
| REFINFO | VARCHAR2 | (80) | ||
| MEMO | VARCHAR2 | (80) | ||
| TANGIBLEID | VARCHAR2 | (80) | Y | |
| AUTHCODE | VARCHAR2 | (80) | ||
| REFERENCECODE | VARCHAR2 | (80) | ||
| OPERATIONCODE | VARCHAR2 | (80) | ||
| INSTRNAME | VARCHAR2 | (80) | ||
| AUTHTYPE | VARCHAR2 | (20) | ||
| AVSCODE | VARCHAR2 | (80) | ||
| ACQUIRER | VARCHAR2 | (80) | ||
| AUXMSG | VARCHAR2 | (255) | ||
| ADDRESS1 | VARCHAR2 | (240) | ||
| ADDRESS2 | VARCHAR2 | (240) | ||
| ADDRESS3 | VARCHAR2 | (240) | ||
| CITY | VARCHAR2 | (60) | ||
| STATE | VARCHAR2 | (60) | ||
| ZIP | VARCHAR2 | (60) | ||
| COUNTY | VARCHAR2 | (60) | ||
| COUNTRY | VARCHAR2 | (60) | ||
| ORG_ID | NUMBER | (15) | Organization identifier | |
| NLSLANG | VARCHAR2 | (80) | ||
| VOICEAUTHFLAG | VARCHAR2 | (1) | Indicates whether Authorization was done manually | |
| DEBIT_NETWORK_CODE | VARCHAR2 | (80) | ||
| SURCHARGE_AMOUNT | NUMBER | |||
| PROC_TRACENUMBER | VARCHAR2 | (80) | ||
| ORDER_MEDIUM | VARCHAR2 | (30) | Medium or channel through which the order was sent. Possible values defined by lookup IBY_ORDER_MEDIUM_TYPE. | |
| EFT_AUTH_METHOD | VARCHAR2 | (30) |
APPS.IBY_TRANS_CORE_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| TRANSACTIONID | NUMBER | Y | ||
| PAYEEID | VARCHAR2 | (80) | Y | |
| BEPID | NUMBER | (15) | ||
| ECAPPID | NUMBER | (15) | Y | |
| TRXNMID | NUMBER | Y | ||
| PAYERID | VARCHAR2 | (80) | ||
| PAYERINSTRID | NUMBER | |||
| PAYEEINSTRID | NUMBER | |||
| REQDATE | DATE | |||
| REQTYPE | VARCHAR2 | (20) | ||
| STATUS | NUMBER | (15) | Y | |
| SETTLEDATE | DATE | |||
| UPDATEDATE | DATE | |||
| TRXNTYPE | NUMBER | (15) | ||
| ERRORLOCATION | NUMBER | |||
| BEPCODE | VARCHAR2 | (40) | ||
| BEPMESSAGE | VARCHAR2 | (255) | ||
| BATCHID | VARCHAR2 | (80) | ||
| NEEDSUPDT | VARCHAR2 | (3) | ||
| DESTURL | VARCHAR2 | (1024) | ||
| PAYMENTMETHODNAME | VARCHAR2 | (80) | ||
| AMOUNT | NUMBER | |||
| CURRENCYNAMECODE | VARCHAR2 | (15) | Y | |
| ACCTNO | VARCHAR2 | (80) | ||
| REFINFO | VARCHAR2 | (80) | ||
| MEMO | VARCHAR2 | (80) | ||
| TANGIBLEID | VARCHAR2 | (80) | Y | |
| PMTSCHEMEID | NUMBER | (15) | Y | |
| REFERENCECODE | VARCHAR2 | (80) | ||
| SRVID | VARCHAR2 | (80) | ||
| PSREQID | VARCHAR2 | (80) | ||
| ORG_ID | NUMBER | (15) | Organization identifier | |
| NLSLANG | VARCHAR2 | (80) | ||
| NAME | VARCHAR2 | (80) | Y | |
| ORDER_MEDIUM | VARCHAR2 | (30) | Medium or channel through which the order was sent. Possible values defined by lookup IBY_ORDER_MEDIUM_TYPE. | |
| EFT_AUTH_METHOD | VARCHAR2 | (30) |
APPS.IBY_TRANS_FI_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| TRANSACTIONID | NUMBER | Y | ||
| BEPKEY | VARCHAR2 | (80) | BEPKEY is the Bep Key (merchant account ID) used with this transaction | |
| PAYEEID | VARCHAR2 | (80) | Y | |
| BEPID | NUMBER | (15) | ||
| ECAPPID | NUMBER | (15) | Y | |
| TRXNMID | NUMBER | Y | ||
| PAYERID | VARCHAR2 | (80) | ||
| PAYERINSTRID | NUMBER | |||
| CHNAME | VARCHAR2 | (80) | ||
| PCNUMBER | VARCHAR2 | (30) | ||
| EXPIRYDATE | DATE | |||
| SUBTYPE | VARCHAR2 | (80) | ||
| ENCRYPTED | VARCHAR2 | (1) | ||
| ACCTTYPE | VARCHAR2 | (30) | ||
| REQDATE | DATE | |||
| REQTYPE | VARCHAR2 | (20) | ||
| STATUS | NUMBER | (15) | Y | |
| SETTLEDATE | DATE | |||
| UPDATEDATE | DATE | |||
| TRXNTYPEID | NUMBER | (15) | ||
| ERRORLOCATION | NUMBER | |||
| BEPCODE | VARCHAR2 | (40) | ||
| BEPMESSAGE | VARCHAR2 | (255) | ||
| BATCHID | VARCHAR2 | (80) | ||
| NEEDSUPDT | VARCHAR2 | (3) | ||
| DESTURL | VARCHAR2 | (1024) | ||
| PAYMENTMETHODNAME | VARCHAR2 | (80) | ||
| AMOUNT | NUMBER | |||
| CURRENCYNAMECODE | VARCHAR2 | (15) | Y | |
| ACCTNO | VARCHAR2 | (80) | ||
| REFINFO | VARCHAR2 | (80) | ||
| MEMO | VARCHAR2 | (80) | ||
| TANGIBLEID | VARCHAR2 | (80) | Y | |
| AUTHCODE | VARCHAR2 | (80) | ||
| REFERENCECODE | VARCHAR2 | (80) | ||
| OPERATIONCODE | VARCHAR2 | (80) | ||
| INSTRNAME | VARCHAR2 | (80) | ||
| AUTHTYPE | VARCHAR2 | (20) | ||
| AVSCODE | VARCHAR2 | (80) | ||
| ACQUIRER | VARCHAR2 | (80) | ||
| AUXMSG | VARCHAR2 | (255) | ||
| PONUMBER | VARCHAR2 | (80) | ||
| TAXAMOUNT | NUMBER | |||
| SHIPTOZIP | VARCHAR2 | (80) | ||
| SHIPFROMZIP | VARCHAR2 | (80) | ||
| ADDRESS1 | VARCHAR2 | (240) | ||
| ADDRESS2 | VARCHAR2 | (240) | ||
| ADDRESS3 | VARCHAR2 | (240) | ||
| CITY | VARCHAR2 | (60) | ||
| STATE | VARCHAR2 | (60) | ||
| ZIP | VARCHAR2 | (60) | ||
| COUNTY | VARCHAR2 | (60) | ||
| COUNTRY | VARCHAR2 | (60) | ||
| ORG_ID | NUMBER | (15) | Organization identifier | |
| NLSLANG | VARCHAR2 | (80) | ||
| VOICEAUTHFLAG | VARCHAR2 | (1) | Indicates whether Authorization was done manually | |
| ORDER_MEDIUM | VARCHAR2 | (30) | Medium or channel through which the order was sent. Possible values defined by lookup IBY_ORDER_MEDIUM_TYPE. | |
| EFT_AUTH_METHOD | VARCHAR2 | (30) |
APPS.IBY_TRANS_PCARD_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| TRANSACTIONID | NUMBER | Y | ||
| TANGIBLEID | VARCHAR2 | (80) | Y | |
| PAYEEID | VARCHAR2 | (80) | Y | |
| BEPID | NUMBER | (15) | ||
| ECAPPID | NUMBER | (15) | Y | |
| TRXNMID | NUMBER | Y | ||
| PMTSCHEMEID | NUMBER | (15) | Y | |
| AMOUNT | NUMBER | |||
| CURRENCYNAMECODE | VARCHAR2 | (15) | ||
| REQDATE | DATE | |||
| REQTYPE | VARCHAR2 | (20) | ||
| STATUS | NUMBER | (15) | Y | |
| SETTLEDATE | DATE | |||
| UPDATEDATE | DATE | |||
| TRXNTYPEID | NUMBER | (15) | ||
| ERRORLOCATION | NUMBER | |||
| BEPCODE | VARCHAR2 | (40) | ||
| BEPMESSAGE | VARCHAR2 | (255) | ||
| BATCHID | VARCHAR2 | (80) | ||
| DESTURL | VARCHAR2 | (1024) | ||
| NEEDSUPDT | VARCHAR2 | (3) | ||
| SETTRXNID | VARCHAR2 | (80) | ||
| COMPLETIONCODE | VARCHAR2 | (80) | ||
| SPLITID | NUMBER | |||
| TERMINALID | VARCHAR2 | (80) | ||
| SUBAUTHIND | NUMBER | |||
| CARDBIN | VARCHAR2 | (10) | ||
| BATCHSEQNUM | NUMBER | |||
| BATCHTRXNSTATUS | NUMBER | |||
| SETREQTYPE | NUMBER | |||
| PREVSPLITID | NUMBER | |||
| SUBSAUTHTYPE | VARCHAR2 | (20) | ||
| SPLITSHIPMENT | NUMBER | |||
| AUTHCURRENCY | VARCHAR2 | (10) | ||
| AUTHPRICE | NUMBER | |||
| INSTALLTOTALTRXNS | NUMBER | |||
| RECURRINGFREQ | NUMBER | |||
| RECURRINGEXPDATE | DATE | |||
| CUSTREFNUM | VARCHAR2 | (80) | ||
| DESTPOSTALCODE | VARCHAR2 | (10) | ||
| LOCALTAXPRICE | NUMBER | |||
| LOCALTAXCURRENCY | VARCHAR2 | (10) | ||
| CREDITCOUNTER | NUMBER | |||
| ORG_ID | NUMBER | (15) | Organization identifier |
APPS.IBY_TRANS_SET_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ROW_ID | ROWID | (10) | ||
| TRXN_EXTENSION_ID | NUMBER | (15) | Y | |
| PAYMENT_CHANNEL_CODE | VARCHAR2 | (30) | Y | |
| PAYMENT_CHANNEL_NAME | VARCHAR2 | (100) | Y | |
| INSTR_ASSIGNMENT_ID | NUMBER | (15) | ||
| INSTRUMENT_TYPE | VARCHAR2 | (30) | ||
| INSTRUMENT_ID | NUMBER | (15) | ||
| CURRENCY_CODE | VARCHAR2 | (15) | ||
| CARD_NUMBER | VARCHAR2 | (30) | ||
| CARD_NUMBER_HASH1 | VARCHAR2 | (64) | ||
| CARD_NUMBER_HASH2 | VARCHAR2 | (64) | ||
| CARD_EXPIRYDATE | DATE | Obsoleted as part of PA-DSS uptake. | ||
| MASKED_CARD_EXPIRYDATE | VARCHAR2 | (5) | ||
| CARD_EXPIRED_FLAG | VARCHAR2 | (1) | ||
| CARD_ISSUER_CODE | VARCHAR2 | (30) | ||
| CARD_ISSUER_NAME | VARCHAR2 | (100) | ||
| PURCHASECARD_SUBTYPE | VARCHAR2 | (30) | ||
| CARD_HOLDER_NAME | VARCHAR2 | (360) | ||
| ACCOUNT_NUMBER | VARCHAR2 | (100) | ||
| BANK_NUMBER | VARCHAR2 | (30) | ||
| INSTRUMENT_SECURITY_CODE | VARCHAR2 | (5) | ||
| VOICE_AUTHORIZATION_FLAG | VARCHAR2 | (1) | ||
| VOICE_AUTHORIZATION_DATE | DATE | |||
| VOICE_AUTHORIZATION_CODE | VARCHAR2 | (100) | ||
| ORIGIN_APPLICATION_ID | NUMBER | Y | ||
| ORDER_ID | VARCHAR2 | (75) | ||
| PO_NUMBER | VARCHAR2 | (100) | ||
| PO_LINE_NUMBER | VARCHAR2 | (100) | ||
| TRXN_REF_NUMBER1 | VARCHAR2 | (30) | ||
| TRXN_REF_NUMBER2 | VARCHAR2 | (30) | ||
| PAYMENT_SYSTEM_ORDER_NUMBER | VARCHAR2 | (80) | ||
| ADDITIONAL_INFO | VARCHAR2 | (255) | ||
| AUTHORIZED_FLAG | VARCHAR2 | (1) | ||
| AUTHORIZATION_STATUS | VARCHAR2 | (12) | ||
| SETTLED_FLAG | VARCHAR2 | (1) | ||
| SETTLEMENT_STATUS | VARCHAR2 | (18) | ||
| RETURNED_FLAG | VARCHAR2 | (1) | ||
| RETURN_STATUS | VARCHAR2 | (14) | ||
| BANK_NAME | VARCHAR2 | (360) | ||
| BANK_BRANCH_NAME | VARCHAR2 | (360) | ||
| ENCRYPTED | VARCHAR2 | (1) | ||
| CARD_EXPIRATION_STATUS | VARCHAR2 | (80) | ||
| SEQ_TYPE_LAST | VARCHAR2 | (1) | Denotes the last transaction |
APPS.IBY_TRXN_EXTENSIONS_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| TRXN_EXTENSION_ID | NUMBER | (15) | Y | |
| PAYMENT_CHANNEL_CODE | VARCHAR2 | (30) | Y | |
| PAYMENT_CHANNEL_NAME | VARCHAR2 | (100) | Y | |
| INSTR_ASSIGNMENT_ID | NUMBER | (15) | ||
| AUTHORIZATION_ID | NUMBER | (15) | Y | |
| AUTHORIZATION_RESULT_CODE | VARCHAR2 | (21) | ||
| AUTHORIZATION_STATUS | NUMBER | (15) | Y | |
| AUTHORIZATION_DATE | DATE | |||
| AUTHORIZATION_AMOUNT | NUMBER | |||
| EFFECTIVE_AUTH_AMOUNT | NUMBER | |||
| PAYEE_ID | VARCHAR2 | (80) | Y | |
| PROCESS_PROFILE_CODE | VARCHAR2 | (30) | ||
| INSTRUMENT_TYPE | VARCHAR2 | (30) | ||
| PAYMENT_SYSTEM_ORDER_NUMBER | VARCHAR2 | (80) | Y | |
| PMT_SYS_ERR_CODE | VARCHAR2 | (40) | ||
| PMT_SYS_ERR_MSG | VARCHAR2 | (255) | ||
| AUTHORIZATION_CODE | VARCHAR2 | (80) | ||
| AVS_CODE | VARCHAR2 | (80) | ||
| INSTR_SEC_CODE_CHECK | VARCHAR2 | (5) | ||
| SETTLE_REQ_AUTH_FLAG | VARCHAR2 | (1) | ||
| INITIATOR_EXTENSION_ID | NUMBER | (15) | Y | |
| ORIGIN_APPLICATION_ID | NUMBER | Y | ||
| REVERSAL_ALLOWED | VARCHAR2 | (1) | Y/N flag denoting whether or not full reversal is allowed on the authorization. | |
| CAPTURE_EX_AUTH_ALLOWED | VARCHAR2 | (1) | Y/N flag denoting whther or not Capture amount exceeding authorization amount is allowed on the transaction. |
APPS.IBY_TRXN_EXT_AUTHS_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| SETTLEMENT_ID | NUMBER | Y | ||
| TRXN_EXTENSION_ID | NUMBER | (15) | Y | |
| SETTLEMENT_GROUP_ID | NUMBER | |||
| PAYMENT_CHANNEL_CODE | VARCHAR2 | (30) | Y | |
| INSTR_ASSIGNMENT_ID | NUMBER | (15) | ||
| SETTLEMENT_RESULT_CODE | VARCHAR2 | (21) | ||
| SETTLEMENT_DATE | DATE | |||
| PMT_SYS_ERR_CODE | VARCHAR2 | (40) | ||
| PMT_SYS_ERR_MSG | VARCHAR2 | (255) | ||
| PAYMENT_SYSTEM_ORDER_NUMBER | VARCHAR2 | (80) | Y | |
| PAYEE_ID | VARCHAR2 | (80) | Y | |
| ORG_TYPE | VARCHAR2 | (30) | ||
| ORG_ID | NUMBER | (15) | ||
| INITIATOR_EXTENSION_ID | NUMBER | (15) | Y | |
| ORIGIN_APPLICATION_ID | NUMBER | Y |
APPS.IBY_TRXN_EXT_SETTLEMENTS_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ROW_ID | ROWID | (10) | ||
| APPLICATION_ID | NUMBER | (15) | Y | |
| PAY_PROC_TRXN_TYPE_CODE | VARCHAR2 | (30) | Y | |
| SEEDED_FLAG | VARCHAR2 | (1) | Y | |
| PAYMENT_FLOW | VARCHAR2 | (30) | Y | |
| CREATION_DATE | DATE | Y | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| LAST_UPDATE_DATE | DATE | Y | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| OBJECT_VERSION_NUMBER | NUMBER | Y | ||
| CREATED_BY | NUMBER | (15) | Y | |
| NAME | VARCHAR2 | (80) | Y | |
| DESCRIPTION | VARCHAR2 | (240) |
APPS.IBY_TRXN_TYPES_VL is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| UNCLEARED_CONTENT | XMLTYPE | (40) | ||
| PAYMENT_ID | NUMBER | (15) | Y | |
| PAYMENT_STATUS | VARCHAR2 | (30) | Y |
APPS.IBY_UNCLEARED_PMT_XML_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYMENT_FUNCTION | VARCHAR2 | (30) | Y |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ROW_ID | ROWID | (10) | ||
| VALIDATION_SET_CODE | VARCHAR2 | (30) | Y | |
| VALIDATION_PARAMETER_CODE | VARCHAR2 | (100) | Y | |
| VALIDATION_PARAMETER_TYPE | VARCHAR2 | (30) | Y | |
| VALIDATION_PARAM_DISPLAY_ORDER | NUMBER | (15) | Y | |
| CREATED_BY | NUMBER | (15) | Y | |
| CREATION_DATE | DATE | Y | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| LAST_UPDATE_DATE | DATE | Y | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| OBJECT_VERSION_NUMBER | NUMBER | Y | ||
| VALIDATION_PARAM_DISPLAY_NAME | VARCHAR2 | (100) | Y |
APPS.IBY_VALIDATION_PARAMS_VL is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ROW_ID | ROWID | (10) | ||
| VALIDATION_SET_CODE | VARCHAR2 | (30) | Y | |
| VALIDATION_LEVEL_CODE | VARCHAR2 | (30) | Y | |
| VALIDATION_CODE_PACKAGE | VARCHAR2 | (255) | Y | |
| VALIDATION_CODE_ENTRY_POINT | VARCHAR2 | (255) | Y | |
| VALIDATION_CODE_LANGUAGE | VARCHAR2 | (30) | Y | |
| CREATED_BY | NUMBER | (15) | Y | |
| CREATION_DATE | DATE | Y | ||
| LAST_UPDATED_BY | NUMBER | (15) | Y | |
| LAST_UPDATE_DATE | DATE | Y | ||
| LAST_UPDATE_LOGIN | NUMBER | (15) | ||
| OBJECT_VERSION_NUMBER | NUMBER | (15) | Y | |
| VALIDATION_SET_DISPLAY_NAME | VARCHAR2 | (100) | Y |
APPS.IBY_VALIDATION_SETS_VL is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| VOIDED_CONTENT | XMLTYPE | (40) | ||
| PAYMENT_ID | NUMBER | (15) | Y | |
| PAYMENT_STATUS | VARCHAR2 | (30) | Y |
APPS.IBY_VOID_PMT_XML_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| INSTRUCTION | XMLTYPE | (40) | ||
| MBATCHID | NUMBER | (15) | Y |
APPS.IBY_XML_BATCH_FCI_1_0_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ACCOUNT_OPTIONS | XMLTYPE | (40) | ||
| BEP_ACCOUNT_ID | NUMBER | (15) | Y |
APPS.IBY_XML_BEP_ACCT_OPTIONS_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ACCOUNT_SETTING | XMLTYPE | (40) | ||
| BEP_ACCOUNT_ID | NUMBER | (15) | Y |
APPS.IBY_XML_FD_ACCT_SETTINGS_1_0_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| DOC_LINE | XMLTYPE | (40) | ||
| DOCUMENT_PAYABLE_ID | NUMBER | (15) | Y |
APPS.IBY_XML_FD_DOCLINE_1_0_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| DOC_PAYABLE | XMLTYPE | (40) | ||
| PAYMENT_ID | NUMBER | (15) | ||
| FORMATTING_PAYMENT_ID | NUMBER | (15) | ||
| PAYMENT_SERVICE_REQUEST_ID | NUMBER | (15) | ||
| DOCUMENT_PAYABLE_ID | NUMBER | (15) | ||
| DOCUMENT_STATUS | VARCHAR2 | (30) |
APPS.IBY_XML_FD_DOC_1_0_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| DOC_PAYABLE_ERROR | XMLTYPE | (40) | ||
| DOCUMENT_PAYABLE_ID | NUMBER | (15) | Y |
APPS.IBY_XML_FD_DOC_ERR_1_0_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| INSTRUCTION | XMLTYPE | (40) | ||
| PAYMENT_INSTRUCTION_ID | NUMBER | (15) | Y |
APPS.IBY_XML_FD_INS_1_0_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYEE | XMLTYPE | (40) | ||
| PARTY_ID | NUMBER | (15) | ||
| PAYMENT_ID | NUMBER | (15) | Y |
APPS.IBY_XML_FD_PAYEE_1_0_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYER | XMLTYPE | (40) | ||
| PARTY_ID | NUMBER | |||
| LEGAL_ENTITY_ID | NUMBER | (15) | Y | |
| PAYMENT_ID | NUMBER | (15) | Y |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| EXT_BANK_ACCOUNT | XMLTYPE | (40) | ||
| BANK_ACCOUNT_ID | NUMBER | (15) | Y |
APPS.IBY_XML_FD_PEBA_1_0_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYMENT | XMLTYPE | (40) | ||
| PAYMENT_INSTRUCTION_ID | NUMBER | (15) | ||
| INTERNAL_BANK_ACCOUNT_ID | NUMBER | (15) | ||
| LEGAL_ENTITY_ID | NUMBER | (15) | ||
| PAYMENT_ID | NUMBER | (15) | ||
| PAYMENT_REFERENCE_NUMBER | NUMBER | (15) | ||
| PAYMENT_STATUS | VARCHAR2 | (30) | ||
| PAYMENT_CURRENCY_CODE | VARCHAR2 | (10) | ||
| PAYMENT_SERVICE_REQUEST_ID | NUMBER | (15) | ||
| POSITIVE_PAY_FILE_CREATED_FLAG | VARCHAR2 | (1) | ||
| PAYMENT_DATE | DATE | Specifies the date on which payment is made | ||
| VOID_DATE | DATE | |||
| LOGICAL_GROUP_REFERENCE | VARCHAR2 | (200) | Specifies the reference of the group to which this payment belongs to | |
| PAYMENT_PROFILE_ID | NUMBER | (15) | ||
| LOGICAL_REFERENCE_NUMBER | NUMBER |
APPS.IBY_XML_FD_PMT_1_0_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYMENT_ERROR | XMLTYPE | (40) | ||
| PAYMENT_ID | NUMBER | (15) | Y |
APPS.IBY_XML_FD_PMT_ERR_1_0_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYMENT_PROCESS_REQUEST | XMLTYPE | (40) | ||
| PAYMENT_SERVICE_REQUEST_ID | NUMBER | (15) | Y |
APPS.IBY_XML_FD_PPR_1_0_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| INT_BANK_ACCOUNT | XMLTYPE | (40) | ||
| BANK_ACCOUNT_ID | NUMBER | (15) | Y | |
| PAYMENT_ID | NUMBER | (15) | Y |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYEE_ACCOUNT | XMLTYPE | (40) | ||
| MBATCHID | NUMBER | (15) | Y | |
| BEPKEY | VARCHAR2 | (80) |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| BANK_ACCOUNT_CONTENT | XMLTYPE | (40) | ||
| INSTRID | NUMBER | (15) | Y |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| CREDIT_CARD | XMLTYPE | (40) | ||
| TRXNMID | NUMBER | Y |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| DEBIT_CARD | XMLTYPE | (40) | ||
| TRXNMID | NUMBER | Y |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| DOCUMENT_HEADERS | XMLTYPE | (40) | ||
| TRXN_EXTENSION_ID | NUMBER | (15) | Y |
APPS.IBY_XML_FNDCPT_DOC_HEADERS_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| DOCUMENT_HEADER | XMLTYPE | (40) | ||
| TANGIBLEID | VARCHAR2 | (0) | ||
| TRANSACTIONID | NUMBER | Y | ||
| TRXN_EXTENSION_ID | NUMBER | (15) | Y |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| DOCUMENT_LINES | XMLTYPE | (40) | ||
| DOC_UNIQUE_REF | NUMBER | (15) | Y |
APPS.IBY_XML_FNDCPT_DOC_LINES_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| DOCUMENT_LINE | XMLTYPE | (40) | ||
| CUSTOMER_TRX_LINE_ID | NUMBER | Y | ||
| DOC_UNIQUE_REF | NUMBER | (15) | Y | |
| LINE_NUMBER | NUMBER | Y |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| FNDCPT_ORDER | XMLTYPE | (40) | ||
| TRXNMID | NUMBER | Y | ||
| MBATCHID | NUMBER | |||
| BEPKEY | VARCHAR2 | (80) |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| XML_PAYEE | XMLTYPE | (40) | ||
| PARTY_ID | NUMBER | (15) | Y | |
| LEGAL_ENTITY_ID | NUMBER | (15) | Y |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| PAYER | XMLTYPE | (40) | ||
| PARTY_ID | NUMBER | (15) | ||
| TRXNMID | NUMBER | Y |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ADDRESS | XMLTYPE | (40) | ||
| LOCATION_ID | NUMBER | (15) | Y |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ADDRESS | XMLTYPE | (40) | ||
| LOCATION_ID | NUMBER | (15) | Y |
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| INSTRUCTION | XMLTYPE | (40) | ||
| TRXNMID | NUMBER | Y |
APPS.IBY_XML_ONLINE_FCI_1_0_V is not referenced by any database object
Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.
Internal
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| EXTEND_LIST | XMLTYPE | (40) | ||
| TRXNMID | NUMBER | (15) | Y |
|
|
|
| Copyright (c) 2001 - 2005, Oracle | - Use Restricted by Contract |