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: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_ACCOUNT_OWNERS.EXT_BANK_ACCOUNT_ID | % |
| IBY_ACCOUNT_OWNERS.ACCOUNT_OWNER_PARTY_ID | HZ_PARTIES |
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 to this table as well as IBY_EXT_BANK_ACCOUNTS. The external bank account can be shared by multiple parties. When a joint owner is added to the external bank account, then one more entry with the joint owner details is entered in the IBY_ACCOUNT_OWNERS table. This table holds the primary flag, owner party identifier etc. details of the external bank account owner.This is a common table used by both Funds disbursement and Funds Capture modules.
| 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 |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| ACCOUNT_OWNER_ID | NUMBER | (15) | Y | Unique internal Identifier for this record. Generated using a database sequence. |
| EXT_BANK_ACCOUNT_ID | NUMBER | (15) | Y | This is the foreign key to the IBY_EXT_BANK_ACCOUNTS table. |
| ACCOUNT_OWNER_PARTY_ID | NUMBER | (15) | Y | This column represents the party id of the account owner or the joint owner of the external bank account. |
| END_DATE | DATE | The date on which the bank account is end dated | ||
| PRIMARY_FLAG | VARCHAR2 | (1) | Y or N flag indicating whether the party is the primary owner of the bank account | |
| 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. |
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 |
| 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 |
IBY.IBY_ACCTTYPE does not reference any database object
IBY.IBY_ACCTTYPE is referenced by following:
| Description: |
|---|
| 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_ACCT_PMT_PROFILES_B.TRANSMIT_CONFIGURATION_ID | % |
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_DOCUMENTS_PAYABLE_H.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 |
| 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 |
IBY.IBY_ACCT_PMT_PROFILES_B does not reference any database object
IBY.IBY_ACCT_PMT_PROFILES_B is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_ACCT_PMT_PROFILES_TL.PAYMENT_PROFILE_ID | % |
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 |
| 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 |
IBY.IBY_ACCT_PMT_PROFILES_TL does not reference any database object
IBY.IBY_ACCT_PMT_PROFILES_TL 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 |
| 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. |
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: |
|---|
| 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 |
| 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 |
IBY.IBY_APPLICABLE_PMT_MTHDS does not reference any database object
IBY.IBY_APPLICABLE_PMT_MTHDS is referenced by following:
| Description: |
|---|
| 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 |
| 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 |
IBY.IBY_APPLICABLE_PMT_PROFS does not reference any database object
IBY.IBY_APPLICABLE_PMT_PROFS 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: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_BANK_INSTRUCTIONS_B.TERRITORY_CODE | FND_TERRITORIES |
| Foreign Key Column | Foreign Table |
|---|---|
| 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 |
| 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 |
IBY.IBY_BANK_INSTRUCTIONS_B does not reference any database object
IBY.IBY_BANK_INSTRUCTIONS_B is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_BANK_INSTRUCTIONS_TL.BANK_INSTRUCTION_CODE | % |
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 |
| 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 |
IBY.IBY_BANK_INSTRUCTIONS_TL does not reference any database object
IBY.IBY_BANK_INSTRUCTIONS_TL is referenced by following:
| Description: | IBY_BATCHES holds the information about batch operations for SSL credit card transactions. A terminal based merchant will need to have batch operations. The status of the payees batch will be contained in this table. |
|---|
| 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 |
"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 transfer transactions. A terminal-based merchant needs to have batch operations.
This table stores the funds capture settlement information at batch level.� This is applicable for processor model payment systems.� This table contains the information like Payment System code, process profile code, status of batch, number of transactions in the batch, settlement date, payer notification creation etc. "
| 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 | Unique internal Identifier for this record. Generated using a database sequence. |
| 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 | Back End Payment system Identifier. | ||
| MPAYEEID | NUMBER | Payee Identifier | ||
| ECAPPID | NUMBER | Electronic commerce application Identifier | ||
| PAYMENTMETHODNAME | VARCHAR2 | (80) | Name of the payment method | |
| BATCHSTATUS | NUMBER | "Batch status like scuccess-0, failed-7, pending-11, submitted-18, Batch Partially Succeded-6from Lookup type : IBY_TRANSACTION_STATUS" | ||
| 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) | "Request type like oraPmtCloseBatch,oraPmtQueryBatch from lookup type IBY_TRXN_REQTYPES" | |
| 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 - 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. | |
| 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. |
| CREATION_DATE | DATE | Y | Standard who column - date when this row was 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. |
| 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. | |
| ORG_ID | NUMBER | (15) | Unique internal identifier of the Operating Unit. Validated against HR_OPERATING_UNITS.ORGANIZATION_ID. | |
| 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) | The funds capture process profiles code used in 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 needs to be 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_BEPINFO has a row for every BEP(Back End Payment System) configured in system. A BEP is a payment provider such as Cybercash, Verifone etc |
|---|
| 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 |
| IBY_BEPINFO_NAME_U2 | UNIQUE | APPS_TS_TX_IDX | NAME |
| IBY_BEPINFO_SUFFIX_U3 | UNIQUE | APPS_TS_TX_IDX | SUFFIX |
| 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 |
IBY.IBY_BEPINFO does not reference any database object
IBY.IBY_BEPINFO is referenced by following:
| Description: | IBY_BEPKEYS contains a list of all the keys that identifies a payee or payer with a Back End Payment System. |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_BEPKEYS.BEPID | IBY_BEPINFO |
| Foreign Key Column | Foreign Table |
|---|---|
| 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 |
| 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 |
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
| 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 |
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 |
| 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. |
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_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. |
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 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: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_CC_ISSUER_RANGES.CARD_ISSUER_CODE | % |
| 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 |
| 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 |
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.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 |
| Foreign Key Column | Foreign Table |
|---|---|
| AP_CARDS_ALL.CARD_REFERENCE_ID | IBY_CREDITCARD |
| IBY_CREDITCARD_H.INSTRID | IBY_CREDITCARD |
| IBY_INSTRHOLDER.INSTRID | IBY_CREDITCARD |
"This table contains records of the credit card details of the customers entered manually or imported through IBY_FNDCPT_SETUP_PUB.Create_Card API.
IBY_CREDITCARD table stores the credit card information. This is the related� table for Create Credit Card UI. This table stores information like credit card number, expiry date, card holder's name, billing address, card brand, purchase card subtype, inactive date, etc. "
| 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_MASK_SETTING
CARD_UNMASK_LENGTH |
| 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 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 credit card number. 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 2 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 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 the instrument number | ||
| 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 |
IBY.IBY_CREDITCARD does not reference any database object
IBY.IBY_CREDITCARD is referenced by following:
| Description: |
|---|
| 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 |
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) | Stores the segment_ID of the encrypted expiry date. | |
| CHNAME_SEC_SEGMENT_ID | NUMBER | (15) | Stores the segment_ID of the encrypted cardholder name |
IBY.IBY_CREDITCARD_H does not reference any database object
IBY.IBY_CREDITCARD_H is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_CREDITCARD.CARD_ISSUER_CODE | IBY_CREDITCARD_ISSUERS_B |
| IBY_CREDITCARD_H.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 |
| 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. |
IBY.IBY_CREDITCARD_ISSUERS_B does not reference any database object
IBY.IBY_CREDITCARD_ISSUERS_B is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_CREDITCARD_ISSUERS_TL.CARD_ISSUER_CODE | % |
Holds the list of accepted card brands
| Index | Type | Tablespace | Column |
|---|---|---|---|
| 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 |
IBY.IBY_CREDITCARD_ISSUERS_TL does not reference any database object
IBY.IBY_CREDITCARD_ISSUERS_TL is referenced by following:
| Description: | IBY_DEFAULT_BEP contains the default Back End Payment System information. Based on the instrument type the payment request gets routed to this Back End Payment System. |
|---|
| 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_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 |
IBY.IBY_DEFAULT_BEP does not reference any database object
IBY.IBY_DEFAULT_BEP is referenced by following:
| Description: |
|---|
| 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 |
| 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 |
IBY.IBY_DELIVERY_CHANNELS_B does not reference any database object
IBY.IBY_DELIVERY_CHANNELS_B is referenced by following:
| Description: |
|---|
| 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 |
| 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 |
IBY.IBY_DELIVERY_CHANNELS_TL does not reference any database object
IBY.IBY_DELIVERY_CHANNELS_TL is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
|
IBY_DOCS_PAYABLE_ALL.CALLING_APP_ID
IBY_DOCS_PAYABLE_ALL.PAY_PROC_TRXN_TYPE_CODE |
% |
| IBY_DOCS_PAYABLE_ALL.PAYMENT_SERVICE_REQUEST_ID | % |
| IBY_DOCS_PAYABLE_ALL.EXTERNAL_BANK_ACCOUNT_ID | CE_BANK_ACCOUNTS |
| IBY_DOCS_PAYABLE_ALL.PAYMENT_METHOD_CODE | IBY_PAYMENT_METHODS_B |
| IBY_DOCS_PAYABLE_ALL.PAYMENT_PROFILE_ID | % |
| IBY_DOCS_PAYABLE_ALL.PAYMENT_ID | % |
| IBY_DOCS_PAYABLE_ALL.EXT_PAYEE_ID | % |
| IBY_DOCS_PAYABLE_ALL.PAYMENT_REASON_CODE | % |
| IBY_DOCS_PAYABLE_ALL.DELIVERY_CHANNEL_CODE | IBY_DELIVERY_CHANNELS_B |
| IBY_DOCS_PAYABLE_ALL.PAYMENT_FORMAT_CODE | % |
| 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 |
"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 payable is a supplier invoice or similar document that needs to be paid. In addition, this table contains whatever document information is necessary for payment processing.
This table contains transaction details, document details, payer, payee, etc."
| 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_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 | (15) | 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 | (15) | 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 | (15) | 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 | (15) | 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 | (15) | This field always displays the same value as BENEFICIARY_PARTY. | |
| RELATIONSHIP_ID | NUMBER | (15) | 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. |
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: |
|---|
| 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 |
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: |
|---|
| 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: |
|---|
| 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_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 |
| IBY_ECAPP_ECAPPID_U1 | UNIQUE | APPS_TS_TX_IDX | ECAPPID |
| 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 |
IBY.IBY_ECAPP does not reference any database object
IBY.IBY_ECAPP is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_EXTERNAL_PAYEES_ALL.BANK_INSTRUCTION1_CODE | % |
| IBY_EXTERNAL_PAYEES_ALL.DEFAULT_PAYMENT_METHOD_CODE | IBY_PAYMENT_METHODS_B |
| IBY_EXTERNAL_PAYEES_ALL.BANK_INSTRUCTION2_CODE | % |
| IBY_EXTERNAL_PAYEES_ALL.PAYMENT_REASON_CODE | % |
| IBY_EXTERNAL_PAYEES_ALL.DELIVERY_CHANNEL_CODE | IBY_DELIVERY_CHANNELS_B |
| IBY_EXTERNAL_PAYEES_ALL.PAYMENT_FORMAT_CODE | % |
| Foreign Key Column | Foreign Table |
|---|---|
| FV_TPP_ASSIGNMENTS_ALL.EXT_PAYEE_ID | IBY_EXTERNAL_PAYEES_ALL |
| IBY_PAYMENTS_ALL.EXT_PAYEE_ID | IBY_EXTERNAL_PAYEES_ALL |
"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.
A party can have multiple payees at following levels -
Party or
Site or
Address or
Address operating unit
This table contains the details of all such payees.
IBY_EXTERNAL_PAYEES_ALL stores payment-related attributes for the funds disbursement payment process for external party payees. "
| 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 | Unique internal Identifier for this record. Generated using a database sequence. |
| 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 should be paid alone without grouping with any other document payable. |
| 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. | |
| 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) | The supplier site Id for which the payment details are being entered. If the payment details are entered at supplier level, the Party side id is NULL. | |
| ORG_ID | NUMBER | (15) | When the payment details are defined for a site, address operating unit, etc., the organization details are updated along with the site id or address operating unit. | |
| 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) | The default payment method at the time defining the Payee. While creating a Payee, default payment method is updated in both iby_external_payees_all and iby_ext_party_pmt_mthds. Later, the changes are update only in IBY_EXT_PARTY_PMT_MTHDS. | |
| ECE_TP_LOCATION_CODE | VARCHAR2 | (60) | Trading partner location code for e-Commerce Gateway | |
| BANK_CHARGE_BEARER | VARCHAR2 | (30) | This field indicates the bearer of the bank charges. The bank charge bearer values are defined in the lookup IBY_BANK_CHARGE_BEARER. The possible values are Payer, Payee, Shared, etc. | |
| 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_REASON_CODE | VARCHAR2 | (30) | There is a separate setup for defining the payment reasons. The values mentioned in the payment details of the supplier setup are defaulted on the invoice workbench. | |
| PAYMENT_REASON_COMMENTS | VARCHAR2 | (240) | The Payment reason comments is a free text field. The value mentioned in the payment details of the supplier setup are defaulted on the invoice workbench. | |
| INACTIVE_DATE | DATE | Inactive date | ||
| 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. | |
| PAYMENT_TEXT_MESSAGE3 | VARCHAR2 | (150) | It is a free text field that can be used payment processing. | |
| DELIVERY_CHANNEL_CODE | VARCHAR2 | (30) | There is a separate setup for defining the Delivery Channel codes. The values mentioned in the payment details of the supplier setup are defaulted on the invoice workbench. | |
| PAYMENT_FORMAT_CODE | VARCHAR2 | (30) | Payment format attached under the payment specification tab of the suppliers payments details screen. | |
| 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 for the Separate remittance advice report. The value can be set at Payee or payee site level also. If the override with Payee delivery option is checked in the Payment process profile, the setting at the payee and payee site level is ignored. Values from the lookup IBY_DELIVERY_METHODS include EMAIL, FAX, and PRINT | |
| 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: |
|---|
| 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 |
"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.
A customer account can have multiple payers at following levels -
Party or
Site or
Address or
Address operating unit
This table contains the details of all such payers.
IBY_EXTERNAL_PAYERS_ALL stores payment-related attributes for the funds capture process for external party payers.
This table stores the data entered through the payment details (header) screen of the customer account setup UI. "
| 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 | Unique internal Identifier for this record. Generated using a database sequence. The sequence used is IBY_EXTERNAL_PAYERS_ALL_S.nextval |
| PAYMENT_FUNCTION | VARCHAR2 | (30) | Y | Function or purpose of the payment. Values from the lookup IBY_PAYMENT_FUNCTIONS include CUSTOMER_PAYMENT and others. |
| PARTY_ID | NUMBER | (15) | Y | TCA party ID |
| ORG_TYPE | VARCHAR2 | (30) | When the payment details are updated for a site, the organization type is also saved along with the site. | |
| ORG_ID | NUMBER | (15) | When the payment details are updated for a site, the organization id is also saved along with the site. | |
| 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 field indicates the bearer of the bank charges. The dropdown box has values Payer, Payee and Shared. | |
| DIRDEB_INSTRUCTION_CODE | VARCHAR2 | (30) | Direct debit instruction code | |
| 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 | |
| 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. | |
| DEBIT_ADVICE_DELIVERY_METHOD | VARCHAR2 | (30) | Debit notification delivery method option selected. The possible values are Blank, E-mail, Fax and Printed. | |
| DEBIT_ADVICE_EMAIL | VARCHAR2 | (255) | When the user selects the Debit notification delivery method as 'E-mail', the email details can be entered in this field. | |
| DEBIT_ADVICE_FAX | VARCHAR2 | (100) | When the user selects the Debit notification delivery method as 'Fax', the fax details can be entered in this field. |
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 |
| 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. |
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_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. |
IBY.IBY_EXTRACTS_TL does not reference any database object
IBY.IBY_EXTRACTS_TL is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_EXTRACT_ACTIVATIONS.FORMAT_CODE | % |
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: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_EXT_BANK_ACCOUNTS.BA_NUM_SEC_SEGMENT_ID | % |
| IBY_EXT_BANK_ACCOUNTS.IBAN_SEC_SEGMENT_ID | % |
| 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_INTERMEDIARY_ACCTS.BANK_ACCT_ID | IBY_EXT_BANK_ACCOUNTS |
"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 accounts.
This table should not be translated for any columns. This is a common table used by both Funds disbursement and funds Capture module."
| 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 | Unique internal Identifier for this record. Generated using a database sequence. |
| COUNTRY_CODE | VARCHAR2 | (2) | Country code of the bank for which the bank accounts is created. | |
| 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) | Hash1 of the bank account number. Used for the encryption of the bank account number. | |
| BANK_ACCOUNT_NUM_HASH2 | VARCHAR2 | (64) | Hash2 of the bank account number. Used for the encryption of the bank account number. | |
| MASKED_BANK_ACCOUNT_NUM | VARCHAR2 | (100) | The bank account number masked as per the setup. This is used for displaying the bank account number on the UI. | |
| BA_MASK_SETTING | VARCHAR2 | (30) | 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. | |
| BA_UNMASK_LENGTH | NUMBER | (2) | The number of digits that can be exposed while displaying the bank account number on the UI or reports. | |
| CURRENCY_CODE | VARCHAR2 | (15) | Currency code of the bank account with which the bank account is defined. | |
| IBAN | VARCHAR2 | (50) | International Bank Account Number | |
| IBAN_HASH1 | VARCHAR2 | (64) | IBAN hash1 value. Used for the encryption of the International Bank Account Number. | |
| IBAN_HASH2 | VARCHAR2 | (64) | IBAN hash2 value. Used for the encryption of the International Bank Account Number. | |
| MASKED_IBAN | VARCHAR2 | (50) | Masked IBAN value; to be used for display purposes | |
| CHECK_DIGITS | VARCHAR2 | (30) | Bank account check digit value as entered. | |
| 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 as entered under the details heading of the bank account setup. | |
| 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) | Secondary Account Reference as entered under the details heading of the bank account setup. | |
| BA_NUM_SEC_SEGMENT_ID | NUMBER | (15) | Bank Account Number Security Segment ID, used for encryption. | |
| ENCRYPTED | VARCHAR2 | (1) | Y | Y or N indicating whether bank account number is encrypted. |
| IBAN_SEC_SEGMENT_ID | NUMBER | (15) | Used for the encryption of the International Bank Account Number. | |
| 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) | 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. | ||
| START_DATE | DATE | Start date | ||
| END_DATE | DATE | End 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 | 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) | The name of the bank account. | |
| BANK_ACCOUNT_NAME_ALT | VARCHAR2 | (320) | The alternate name of the bank account. | |
| SHORT_ACCT_NAME | VARCHAR2 | (30) | The short name of the bank account. | |
| DESCRIPTION | VARCHAR2 | (240) | The description regarding the bank account. | |
| 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) | Denotes the versions of the encryption algorithm used for the Bank account number encryption. |
IBY.IBY_EXT_BANK_ACCOUNTS does not reference any database object
IBY.IBY_EXT_BANK_ACCOUNTS is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_EXT_PARTY_PMT_MTHDS.EXT_PMT_PARTY_ID | % |
| 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: |
|---|
| 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: |
|---|
| 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 |
| 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 |
IBY.IBY_FNDCPT_PMT_CHNNLS_B does not reference any database object
IBY.IBY_FNDCPT_PMT_CHNNLS_B is referenced by following:
| Description: |
|---|
| 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_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 |
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 Funds Capture processing rules for a Payment system for the credit card funds capture process.
This table corresponds to the Funds capture process profile UI. "
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_FNDCPT_SYS_CC_PF_SPC_U1 | UNIQUE | APPS_TS_TX_IDX | SYS_CC_PROFILE_CODE |
| 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 | Funds Capture Process Profile code. |
| PAYMENT_SYSTEM_ID | NUMBER | (15) | Y | Payment system identifier |
| ONLINE_AUTH_FORMAT_CODE | VARCHAR2 | (30) | Y | Format code of online authorization message. |
| ONLINE_AUTH_TRANS_PRTCL_CODE | VARCHAR2 | (30) | Transmission protocol for online authorization messages | |
| ONLINE_AUTH_ACK_RDR_CODE | VARCHAR2 | (30) | Y | Format code of acknowledgement message for online authorization transaction. |
| SETTLEMENT_FORMAT_CODE | VARCHAR2 | (30) | Y | Format code of settlement message. |
| SETTLEMENT_TRANS_PRTCL_CODE | VARCHAR2 | (30) | Transmission protocol for settlement messages | |
| SETTLEMENT_ACK_RDR_CODE | VARCHAR2 | (30) | Format code of acknowledgement message for settlement transaction. | |
| QUERY_FORMAT_CODE | VARCHAR2 | (30) | Format code for query request message. | |
| QUERY_TRANS_PRTCL_CODE | VARCHAR2 | (30) | Transmission protocol for query requests | |
| QUERY_ACK_RDR_CODE | VARCHAR2 | (30) | Format code of acknowledgement message for query request transaction. | |
| 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 - 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. |
| 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) | Format code of payer notification message | |
| 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 |
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_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 |
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 |
| 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 |
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_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 |
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 |
| 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 |
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_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 |
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: |
|---|
| 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 | % |
| Foreign Key Column | Foreign Table |
|---|---|
| AR_CASH_RECEIPTS_ALL.PAYMENT_TRXN_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 |
"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 stores the payment processing-specific attributes of a source product's transaction. The payment entities and attributes include payment method, payment instrument assignment, and payment method-driven transaction attributes. The payment method-driven transaction attributes are credit card, security value, voice authorization flag, voice authorization code, and voice authorization date.
"
| 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 | Unique internal Identifier for this record. Generated using a database sequence. Sequence used is IBY_FNDCPT_TX_EXTENSIONS_S.nextval |
| PAYMENT_CHANNEL_CODE | VARCHAR2 | (30) | Y | Payment channel code. Possible values can be CREDIT_CARD, BANK_ACCT_XFER and BILLS_RECEIVABLE. |
| 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 | (20) | Transaction reference number 1; optional transaction identifier used within the calling application | |
| TRXN_REF_NUMBER2 | VARCHAR2 | (20) | 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 is used by Oracle Payments to link the upgraded transaction extensions with their associated IBY operations. | |
| 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. | |
| PAYMENT_SYSTEM_ORDER_NUMBER | VARCHAR2 | (80) | Payment System Order Number for the transaction. |
IBY.IBY_FNDCPT_TX_EXTENSIONS does not reference any database object
IBY.IBY_FNDCPT_TX_EXTENSIONS is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_FNDCPT_TX_OPERATIONS.TRXN_EXTENSION_ID | % |
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: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_FNDCPT_TX_XE_COPIES.COPY_TRXN_EXTENSION_ID | % |
| IBY_FNDCPT_TX_XE_COPIES.SOURCE_TRXN_EXTENSION_ID | % |
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_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_PMT_SYS_FORMATS.PAYMENT_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 |
| 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 |
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_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. |
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.
| 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.
| 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: |
|---|
| 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: |
|---|
| 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: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_INSTRUCT_SOURCE_APPS.PAYMENT_INSTRUCTION_ID | % |
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: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_INSTR_CREATION_RULES.SYSTEM_PROFILE_CODE | % |
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 |
| 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 |
IBY.IBY_INSTR_CREATION_RULES does not reference any database object
IBY.IBY_INSTR_CREATION_RULES is referenced by following:
| Description: |
|---|
| 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.
| Index | Type | Tablespace | Column |
|---|---|---|---|
| IBY_INTERNAL_PAYERS_ALL_U1 | UNIQUE | APPS_TS_TX_IDX | INT_PAYER_ID |
| 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 | (30) | 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 |
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.
| 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 |
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.
| 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 |
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 |
| 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 |
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.
| 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 |
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 | (30) | Hash value of card number | |
| CC_NUMBER_HASH2 | VARCHAR2 | (30) | Hash value of card number | |
| ACCT_NUMBER_HASH1 | VARCHAR2 | (30) | Hash value of account number | |
| ACCT_NUMBER_HASH2 | VARCHAR2 | (30) | 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.
| 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 |
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.
| 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 |
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 |
| 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 |
IBY.IBY_MAPPINGS does not reference any database object
IBY.IBY_MAPPINGS is referenced by following:
| Description: | IBY_PAYEE holds a row for each payee such as a biller or merchant/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: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_PAYMENTS_ALL.PAYMENT_METHOD_CODE | IBY_PAYMENT_METHODS_B |
| IBY_PAYMENTS_ALL.PAYMENT_PROFILE_ID | % |
| IBY_PAYMENTS_ALL.PAYMENT_SERVICE_REQUEST_ID | % |
| IBY_PAYMENTS_ALL.PAYMENT_INSTRUCTION_ID | % |
| 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 |
|---|---|
| IBY_DOCUMENTS_PAYABLE_H.PAYMENT_ID | IBY_PAYMENTS_ALL |
"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 this table corresponds to one or more documents payable. Payments are build by grouping documents payable according to Oracle Payments' grouping rules.
This table also stores information of payments at grouping level. The groups can be Single, Mixed and Grouped as defined in Payment Process Profile for the purpose of SEPA.
The payment details are displayed on the Payments tab of the Funds Disbursement Process Home page. "
| 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 |
| 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 |
| 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 contains 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 is 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) | Settlement Priority would be defined at invoice level. If payments are grouped based on settlement priority, then it would be populated at payment level. 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) | Paper document number when it is 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) of the banks branch. | |
| 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 | (30) | 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 | (60) | Payee state, if provided by administrator | |
| PAYEE_PROVINCE | VARCHAR2 | (60) | Payee province, if provided by administrator | |
| PAYEE_COUNTY | VARCHAR2 | (60) | 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) | Specifies the name of the Payment process request. | |
| 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 format value that is put into the extract for use by the format. | |
| DECLARATION_EXCH_RATE_TYPE | VARCHAR2 | (255) | Exchange rate type used for regulatory reporting. | |
| DECLARATION_FORMAT | VARCHAR2 | (100) | Format used for regulatory reporting. | |
| DELIVERY_CHANNEL_FORMAT_VALUE | VARCHAR2 | (80) | Delivery channel format value that is put into the extract for use by the format. | |
| BANK_INSTRUCTION1_FORMAT_VALUE | VARCHAR2 | (80) | Bank instruction format value that is put into the extract for use by the format. | |
| BANK_INSTRUCTION2_FORMAT_VALUE | VARCHAR2 | (80) | Bank instruction format value that is put into the extract for use by the format. | |
| SRA_DELIVERY_METHOD | VARCHAR2 | (100) | Separate Remittance Advice delivery method selected. The look up used is IBY_REMIT_ADVICE_SETUP.REMIT_ADVICE_ DELIVERY_METHOD. Possible values are Null, Printed, E-mail, etc. | |
| 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 | Payer identifier | ||
| PAYER_LOCATION_ID | NUMBER | Payer location Identifier | ||
| PAYER_PARTY_ATTR_CATEGORY | VARCHAR2 | (150) | Payee 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) | Payee supplier attribute category | |
| PAYEE_SUPPLIER_SITE_NAME | VARCHAR2 | (150) | Payee supplier site name. | |
| PAYEE_SUPPLIER_SITE_ALT_NAME | VARCHAR2 | (320) | Payee supplier sites alternative name. | |
| PAYEE_SUPPLIER_ID | NUMBER | Supplier identifier | ||
| LOGICAL_GROUP_REFERENCE | VARCHAR2 | (200) | Indicates the grouping mode - None, Single, Mixed or Grouped. | |
| POSITIVE_PAY_FILE_CREATED_FLAG | VARCHAR2 | (1) | Indicates whether the transaction has been included in any of the Positive pay file or not. | |
| EXT_INV_PAYEE_ID | NUMBER | (15) | Payee identifier. | |
| INV_PAYEE_PARTY_ID | NUMBER | (15) | Party (trading partner) identifier. | |
| INV_PARTY_SITE_ID | NUMBER | (15) | Party site identifier | |
| INV_SUPPLIER_SITE_ID | NUMBER | (15) | Supplier site identifier. | |
| INV_BENEFICIARY_PARTY | NUMBER | (15) | Beneficiary party | |
| INV_PAYEE_NAME | VARCHAR2 | (360) | Name of party (trading partner) | |
| INV_PAYEE_ADDRESS1 | VARCHAR2 | (240) | First line of party (trading partner) address line 1 | |
| INV_PAYEE_ADDRESS2 | VARCHAR2 | (240) | Second line of party (trading partner) address line 2 | |
| INV_PAYEE_ADDRESS3 | VARCHAR2 | (240) | Third 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 | (60) | 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 | (15) | Supplier (Trading Partner) identifier |
IBY.IBY_PAYMENTS_ALL does not reference any database object
IBY.IBY_PAYMENTS_ALL is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_PAYMENTS_H.BANK_INSTRUCTION1_CODE | % |
| IBY_PAYMENTS_H.PAYMENT_REASON_CODE | IBY_PAYMENT_REASONS_B |
| IBY_PAYMENTS_H.PAYMENT_INSTRUCTION_ID | % |
| IBY_PAYMENTS_H.PAYMENT_SERVICE_REQUEST_ID | % |
| IBY_PAYMENTS_H.PAYMENT_INSTRUCTION_HISTORY_ID | % |
| IBY_PAYMENTS_H.BANK_INSTRUCTION2_CODE | % |
| 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 | (30) | 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: |
|---|
| 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_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 |
| 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 |
IBY.IBY_PAYMENT_METHODS_B does not reference any database object
IBY.IBY_PAYMENT_METHODS_B is referenced by following:
| Description: |
|---|
| 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 |
| 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 |
IBY.IBY_PAYMENT_METHODS_TL does not reference any database object
IBY.IBY_PAYMENT_METHODS_TL is referenced by following:
| Description: |
|---|
| 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_PAYMENTS_ALL.PAYMENT_REASON_CODE | IBY_PAYMENT_REASONS_B |
| IBY_PAYMENTS_H.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 |
| 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 |
IBY.IBY_PAYMENT_REASONS_B does not reference any database object
IBY.IBY_PAYMENT_REASONS_B is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_PAYMENT_REASONS_TL.PAYMENT_REASON_CODE | % |
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 |
| 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 |
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.
| 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: |
|---|
| 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: |
|---|
| 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 |
| JL_AR_AP_AWT_CERTIF_ALL.PAYMENT_INSTRUCTION_ID | IBY_PAY_INSTRUCTIONS_ALL |
"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 options selected in the Payment process request. If automatic creation is selected, 'Build Payments' will trigger the payment instruction creation otherwise, user has to manually submit concurrent requests 'Create Printed/Electronic Payment Instructions' programs to create payment instruction.
IA payment instruction is a set of one or more payments submitted together to a payment system. A payment instruction can be a printed/electronic instruction
The payment details are displayed on the Payment instruction tab of the Funds Disbursement Process Home page."
| 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_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 |
| 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. Applicable when the processing type is 'Printed'. |
| 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. Applicable when the processing type is 'Electronic'. |
| 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 | (100) | 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) | Automatically print after formatting' is selected, it is mandatory to provide the default printer. | |
| 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) | Indicates the payment method code when the instruction is grouped by payment method. |
IBY.IBY_PAY_INSTRUCTIONS_ALL does not reference any database object
IBY.IBY_PAY_INSTRUCTIONS_ALL is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_PAY_INSTRUCTIONS_H.BEPID | IBY_BEPINFO |
| IBY_PAY_INSTRUCTIONS_H.PAYMENT_FORMAT_CODE | % |
| IBY_PAY_INSTRUCTIONS_H.PAYMENT_REASON_CODE | IBY_PAYMENT_REASONS_B |
| IBY_PAY_INSTRUCTIONS_H.TRANSMIT_CONFIGURATION_ID | % |
| IBY_PAY_INSTRUCTIONS_H.POSITIVE_PAY_FORMAT_CODE | % |
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 | (100) | 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: |
|---|
| 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_DOCUMENTS_PAYABLE_H.PAYMENT_SERVICE_REQUEST_ID | IBY_PAY_SERVICE_REQUESTS |
| IBY_PAY_INSTRUCTIONS_ALL.PAYMENT_SERVICE_REQUEST_ID | IBY_PAY_SERVICE_REQUESTS |
"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 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.
This table contains the parameters like Calling application identifier, Internal bank account, Allow zero payments flag, etc. selected in the Payment Process Request."
| 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 |
| 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 is failed. |
| 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. | |
| 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. | |
| 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_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 |
IBY.IBY_PCARD_BIN_RANGE does not reference any database object
IBY.IBY_PCARD_BIN_RANGE is referenced by following:
| Description: | IBY_PMTMTHD_CONDITIONS contains the conditions for the payment method. Each condition is composed of a parameter, operation and value. The condition is evaluated at runtime to check if the condition is satisfied |
|---|
| 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 contains a list of Payment Schemes that will be supported by a BEP |
|---|
| 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 |
| 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 |
IBY.IBY_PMTSCHEMES does not reference any database object
IBY.IBY_PMTSCHEMES is referenced by following:
| Description: |
|---|
| 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 |
| 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 |
IBY.IBY_PMT_CREATION_RULES does not reference any database object
IBY.IBY_PMT_CREATION_RULES is referenced by following:
| Description: |
|---|
| Foreign Key Column | Foreign Table |
|---|---|
| IBY_FNDCPT_TX_EXTENSIONS.INSTR_ASSIGNMENT_ID | IBY_PMT_INSTR_USES_ALL |
"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 by both the funds disbursement and funds capture modules of Oracle Payments. The payment instruments can be credit cards, bank accounts, etc."
| 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 |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| INSTRUMENT_PAYMENT_USE_ID | NUMBER | (15) | Y | Unique internal Identifier for this record. Generated using a database sequence. Sequence used is IBY_PMT_INSTR_USES_ALL_S.nextval |
| PAYMENT_FLOW | VARCHAR2 | (30) | Y | Values from lookup IBY_PAYMENT_FLOW. Possible values can be FUNDS_CAPTURE or DISBURSEMENTS. |
| 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. Possible values can be CUSTOMER_PAYMENT or PAYABLES_DISB. |
| ORDER_OF_PREFERENCE | NUMBER | (15) | Y | The priority of the bank account or the credit card as per the setup. |
| 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. | |
| START_DATE | DATE | Y | Date when relationship of payment instrument with payer is started. | |
| END_DATE | DATE | Date when relationship of payment instrument with payer is ended. | ||
| 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_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 |
| 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 |
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_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. |
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 |
| 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. |
IBY.IBY_PMT_SYS_TRANSMISSIONS does not reference any database object
IBY.IBY_PMT_SYS_TRANSMISSIONS is referenced by following:
| Description: |
|---|
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
| 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: |
|---|
| 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_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