eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

DBA Data [Home] [Help] [Dependency Information]

TABLE: IBY.IBY_ROUTINGINFO

Object Details

Object Name:	IBY_ROUTINGINFO
Object Type:	TABLE
Owner:	IBY
FND Design Data:	IBY.IBY_ROUTINGINFO
Subobject Name:
Status:	VALID

IBY_ROUTINGINFO stores information that maps payment method to the payment system and funds capture process profile via conditions.

Storage Details

Tablespace:	APPS_TS_TX_DATA
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
IBY_RTINFO_PAYMENTMETHODID_U1	NORMAL	UNIQUE	APPS_TS_TX_IDX	PAYMENTMETHODID

Columns

Name	Datatype	Length	Mandatory	Comments
PAYEEID	VARCHAR2	(80)		Payee Identifier passed by electronic commerce application
BEPID	NUMBER	(15)	Yes	Payment system Identifier
PAYMENTMETHODID	NUMBER	(15)	Yes	System-generated identifier of the payment method
PAYMENTMETHODNAME	VARCHAR2	(80)	Yes	Name of the payment method
MPAYEEID	NUMBER			Payee Identifier
CONFIGURED	NUMBER	(2)	Yes	Indicates whether payment method is active or not. 1 is active and 0 is inactive.
PRIORITY	NUMBER	(15)		Order in which the payment methods are selected
LAST_UPDATE_DATE	DATE		Yes	Standard Who column
OBJECT_VERSION_NUMBER	NUMBER	(5)	Yes	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)	Yes	Standard Who column
CREATION_DATE	DATE		Yes	Standard Who column
CREATED_BY	NUMBER	(15)	Yes	Standard Who column
LAST_UPDATE_LOGIN	NUMBER	(15)		Standard Who column
SECURITY_GROUP_ID	NUMBER			Used in hosted environments
HITCOUNTER	NUMBER	(15)		Count of the number of times the routing rule was chosen
INSTR_TYPE	VARCHAR2	(30)	Yes	Instrument type for which this routing rule applies. One of CREDITCARD, PURCHASECARD, or BANKACCOUNT
BEPKEY	VARCHAR2	(80)		Merchant account Identifier associated with this routing rule
INSTR_SUB_TYPE	VARCHAR2	(30)		If INSTR_TYPE is BANKACCOUNT, subtype can be either ACH or BR
INACTIVE_DATE	DATE			Inactive Date
FNDCPT_USER_PROFILE_CODE	VARCHAR2	(30)		Funds capture process profile
PAYMENT_CHANNEL_CODE	VARCHAR2	(30)		Payment method
BEP_ACCOUNT_ID	NUMBER			Payment system account

Query Text

Cut, paste (and edit) the following text to query this object:


SELECT PAYEEID
,      BEPID
,      PAYMENTMETHODID
,      PAYMENTMETHODNAME
,      MPAYEEID
,      CONFIGURED
,      PRIORITY
,      LAST_UPDATE_DATE
,      OBJECT_VERSION_NUMBER
,      LAST_UPDATED_BY
,      CREATION_DATE
,      CREATED_BY
,      LAST_UPDATE_LOGIN
,      SECURITY_GROUP_ID
,      HITCOUNTER
,      INSTR_TYPE
,      BEPKEY
,      INSTR_SUB_TYPE
,      INACTIVE_DATE
,      FNDCPT_USER_PROFILE_CODE
,      PAYMENT_CHANNEL_CODE
,      BEP_ACCOUNT_ID
FROM IBY.IBY_ROUTINGINFO;

Dependencies

[top of page]

IBY.IBY_ROUTINGINFO does not reference any database object

IBY.IBY_ROUTINGINFO is referenced by following:

IBY: IBY_ROUTINGINFO#