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_PAY_SERVICE_REQUESTS

Object Details

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

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

Storage Details

Tablespace:	APPS_TS_TX_DATA
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
IBY_PAY_SERVICE_REQUESTS_U1	NORMAL	UNIQUE	APPS_TS_TX_IDX	PAYMENT_SERVICE_REQUEST_ID
IBY_PAY_SERVICE_REQUESTS_U2	NORMAL	UNIQUE	APPS_TS_TX_IDX	CALLING_APP_ID CALL_APP_PAY_SERVICE_REQ_CODE
IBY_PAY_SERVICE_REQUESTS_N1	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	INTERNAL_BANK_ACCOUNT_ID
IBY_PAY_SERVICE_REQUESTS_N2	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	PAYMENT_PROFILE_ID
IBY_PAY_SERVICE_REQUESTS_N3	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	PAYMENT_SERVICE_REQUEST_STATUS

Columns

Name	Datatype	Length	Mandatory	Comments
PAYMENT_SERVICE_REQUEST_ID	NUMBER	(15)	Yes	System generated primary key
CALLING_APP_ID	NUMBER	(15)	Yes	Source product Identifier
CALL_APP_PAY_SERVICE_REQ_CODE	VARCHAR2	(255)	Yes	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)	Yes	Payment process request status. Values from the lookup IBY_REQUEST_STATUSES include PAYMENTS_CREATED.
PROCESS_TYPE	VARCHAR2	(30)	Yes	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)	Yes	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)	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.
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.
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

Query Text

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


SELECT PAYMENT_SERVICE_REQUEST_ID
,      CALLING_APP_ID
,      CALL_APP_PAY_SERVICE_REQ_CODE
,      PAYMENT_SERVICE_REQUEST_STATUS
,      PROCESS_TYPE
,      ALLOW_ZERO_PAYMENTS_FLAG
,      CREATED_BY
,      CREATION_DATE
,      LAST_UPDATED_BY
,      LAST_UPDATE_DATE
,      OBJECT_VERSION_NUMBER
,      LAST_UPDATE_LOGIN
,      INTERNAL_BANK_ACCOUNT_ID
,      PAYMENT_PROFILE_ID
,      MAXIMUM_PAYMENT_AMOUNT
,      MINIMUM_PAYMENT_AMOUNT
,      DOCUMENT_REJECTION_LEVEL_CODE
,      PAYMENT_REJECTION_LEVEL_CODE
,      REQUIRE_PROP_PMTS_REVIEW_FLAG
,      ORG_TYPE
,      ATTRIBUTE_CATEGORY
,      ATTRIBUTE1
,      ATTRIBUTE2
,      ATTRIBUTE3
,      ATTRIBUTE4
,      ATTRIBUTE5
,      ATTRIBUTE6
,      ATTRIBUTE7
,      ATTRIBUTE8
,      ATTRIBUTE9
,      ATTRIBUTE10
,      ATTRIBUTE11
,      ATTRIBUTE12
,      ATTRIBUTE13
,      ATTRIBUTE14
,      ATTRIBUTE15
,      CREATE_PMT_INSTRUCTIONS_FLAG
,      PAYMENT_DOCUMENT_ID
,      REQUEST_ID
FROM IBY.IBY_PAY_SERVICE_REQUESTS;

Dependencies

[top of page]

IBY.IBY_PAY_SERVICE_REQUESTS does not reference any database object

IBY.IBY_PAY_SERVICE_REQUESTS is referenced by following:

APPS: IBY_PAY_SERVICE_REQUESTS