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_PMT_INSTR_USES_ALL

Object Details

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

"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."

Storage Details

Tablespace:	APPS_TS_TX_DATA
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
IBY_PMT_INSTR_USES_ALL_U1	NORMAL	UNIQUE	APPS_TS_TX_IDX	INSTRUMENT_PAYMENT_USE_ID
IBY_PMT_INSTR_USES_ALL_N1	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	PAYMENT_FLOW EXT_PMT_PARTY_ID
IBY_PMT_INSTR_USES_ALL_N2	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	INSTRUMENT_TYPE INSTRUMENT_ID

Columns

Name	Datatype	Length	Mandatory	Comments
INSTRUMENT_PAYMENT_USE_ID	NUMBER	(15)	Yes	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)	Yes	Values from lookup IBY_PAYMENT_FLOW. Possible values can be FUNDS_CAPTURE or DISBURSEMENTS.
EXT_PMT_PARTY_ID	NUMBER	(15)	Yes	Foreign key to IBY_EXTERNAL_PAYERS_ALL.EXT_PAYER_ID
INSTRUMENT_TYPE	VARCHAR2	(30)	Yes	CREDITCARD or BANKACCOUNT.
INSTRUMENT_ID	NUMBER	(15)	Yes	Instrument ID
PAYMENT_FUNCTION	VARCHAR2	(30)	Yes	Payment Function. Possible values can be CUSTOMER_PAYMENT or PAYABLES_DISB.
ORDER_OF_PREFERENCE	NUMBER	(15)	Yes	The priority of the bank account or the credit card as per the setup.
CREATED_BY	NUMBER	(15)	Yes	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		Yes	Standard who column - date when this row was created.
LAST_UPDATED_BY	NUMBER	(15)	Yes	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		Yes	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		Yes	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		Yes	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

Query Text

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


SELECT INSTRUMENT_PAYMENT_USE_ID
,      PAYMENT_FLOW
,      EXT_PMT_PARTY_ID
,      INSTRUMENT_TYPE
,      INSTRUMENT_ID
,      PAYMENT_FUNCTION
,      ORDER_OF_PREFERENCE
,      CREATED_BY
,      CREATION_DATE
,      LAST_UPDATED_BY
,      LAST_UPDATE_DATE
,      LAST_UPDATE_LOGIN
,      OBJECT_VERSION_NUMBER
,      START_DATE
,      END_DATE
,      DEBIT_AUTH_FLAG
,      DEBIT_AUTH_METHOD
,      DEBIT_AUTH_REFERENCE
,      DEBIT_AUTH_BEGIN
,      DEBIT_AUTH_END
,      ATTRIBUTE_CATEGORY
,      ATTRIBUTE1
,      ATTRIBUTE2
,      ATTRIBUTE3
,      ATTRIBUTE4
,      ATTRIBUTE5
,      ATTRIBUTE6
,      ATTRIBUTE7
,      ATTRIBUTE8
,      ATTRIBUTE9
,      ATTRIBUTE10
,      ATTRIBUTE11
,      ATTRIBUTE12
,      ATTRIBUTE13
,      ATTRIBUTE14
,      ATTRIBUTE15
FROM IBY.IBY_PMT_INSTR_USES_ALL;

Dependencies

[top of page]

IBY.IBY_PMT_INSTR_USES_ALL does not reference any database object

IBY.IBY_PMT_INSTR_USES_ALL is referenced by following:

APPS: IBY_PMT_INSTR_USES_ALL