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_INSTR_CREATION_RULES

Object Details

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

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.

Storage Details

Tablespace:	APPS_TS_TX_DATA
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
IBY_INSTR_CREATION_RULES_U1	NORMAL	UNIQUE	APPS_TS_TX_IDX	SYSTEM_PROFILE_CODE ZD_EDITION_NAME

Columns

Name	Datatype	Length	Mandatory	Comments
SYSTEM_PROFILE_CODE	VARCHAR2	(100)	Yes	Unique primary key
CREATED_BY	NUMBER	(15)	Yes	Standard Who column
CREATION_DATE	DATE		Yes	Standard Who column
LAST_UPDATED_BY	NUMBER	(15)	Yes	Standard Who column
LAST_UPDATE_DATE	DATE		Yes	Standard Who column
LAST_UPDATE_LOGIN	NUMBER	(15)		Standard Who column
OBJECT_VERSION_NUMBER	NUMBER		Yes	Object version number
GROUP_BY_PAYMENT_DATE	VARCHAR2	(1)	Yes	Y or N flag specifying whether payments are grouped into payment instructions by payment date
GROUP_BY_PAYMENT_CURRENCY	VARCHAR2	(1)	Yes	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)	Yes	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)	Yes	Y or N flag specifying whether payments are grouped into payment instructions by payment process request
GROUP_BY_LEGAL_ENTITY	VARCHAR2	(1)	Yes	Y or N flag specifying whether payments are grouped into payment instructions by the first party legal entity
GROUP_BY_BILL_PAYABLE	VARCHAR2	(1)	Yes	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)	Yes	Y or N flag specifying whether payments are grouped into payment instructions by the first party organization
GROUP_BY_MAX_INSTRUCTION_FLAG	VARCHAR2	(1)	Yes	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)	Yes	Y or N flag specifying whether payments are grouped by the payment function
GROUP_BY_PAYMENT_REASON	VARCHAR2	(1)	Yes	Y or N flag specifying whether payments are grouped by the payment reason
GROUP_BY_RFC	VARCHAR2	(1)	Yes	Y or N flag specifying whether payments are grouped by the RFC, that is, regional finance center Identifier
MAX_PAYMENTS_PER_INSTRUCTION	NUMBER	(15)		Maximum number of payments that can be included in a payment instruction. When a value exists in this column, the Create Payment Instructions program uses it as one of its rules for building payment instructions.
MAX_AMOUNT_PER_INSTR_VALUE	NUMBER	(15)		Maximum total amount for which a payment instruction can be created. When a value exists in this column, the Create Payment Instructions program uses it as one of its rules for building payment instructions.
MAX_AMOUNT_PER_INSTR_CURR_CODE	VARCHAR2	(10)		Currency in which the maximum total amount per payment instruction is calculated
MAX_AMOUNT_FX_RATE_TYPE	VARCHAR2	(30)		Exchange rate type used to compare the payment instruction total amount to the maximum total amount allowed. Types are defined in the General Ledger currency exchange rate type lookups table. These include CORPORATE, SPOT, and DAILY.
SORT_OPTION_1	VARCHAR2	(30)		Primary column by which payments in a payment instruction are sorted. Values from the lookup IBY_PAYMENT_SORT_OPTIONS include PAYEE_NAME, PAYEE_NUMBER, and others.
SORT_ORDER_1	VARCHAR2	(30)		Order in which the primary sorting occurs. Values from the lookup IBY_PAYMENT_SORT_ORDERS include ASCENDING and DESCENDING.
SORT_OPTION_2	VARCHAR2	(30)		Second column by which payments in a payment instruction are sorted. Values from the lookup IBY_PAYMENT_SORT_OPTIONS include PAYEE_NAME, PAYEE_NUMBER, and others.
SORT_ORDER_2	VARCHAR2	(30)		Order in which the secondary sorting occurs. Values from the lookup IBY_PAYMENT_SORT_ORDERS include ASCENDING and DESCENDING.
SORT_OPTION_3	VARCHAR2	(30)		Third column by which payments in a payment instruction are sorted. Values from the lookup IBY_PAYMENT_SORT_OPTIONS include PAYEE_NAME, PAYEE_NUMBER, and others.
SORT_ORDER_3	VARCHAR2	(30)		Order in which the tertiary sorting occurs. Values from the lookup IBY_PAYMENT_SORT_ORDERS include ASCENDING and DESCENDING.
GROUP_BY_PAYMENT_METHOD	VARCHAR2	(1)		Y or N specifying whether payments are grouped into payment instructions based on payment method
ZD_EDITION_NAME	VARCHAR2	(30)	Yes

Query Text

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


SELECT SYSTEM_PROFILE_CODE
,      CREATED_BY
,      CREATION_DATE
,      LAST_UPDATED_BY
,      LAST_UPDATE_DATE
,      LAST_UPDATE_LOGIN
,      OBJECT_VERSION_NUMBER
,      GROUP_BY_PAYMENT_DATE
,      GROUP_BY_PAYMENT_CURRENCY
,      GROUP_BY_INTERNAL_BANK_ACCOUNT
,      GROUP_BY_MAX_PAYMENTS_FLAG
,      GROUP_BY_PAY_SERVICE_REQUEST
,      GROUP_BY_LEGAL_ENTITY
,      GROUP_BY_BILL_PAYABLE
,      GROUP_BY_ORGANIZATION
,      GROUP_BY_MAX_INSTRUCTION_FLAG
,      GROUP_BY_PAYMENT_FUNCTION
,      GROUP_BY_PAYMENT_REASON
,      GROUP_BY_RFC
,      MAX_PAYMENTS_PER_INSTRUCTION
,      MAX_AMOUNT_PER_INSTR_VALUE
,      MAX_AMOUNT_PER_INSTR_CURR_CODE
,      MAX_AMOUNT_FX_RATE_TYPE
,      SORT_OPTION_1
,      SORT_ORDER_1
,      SORT_OPTION_2
,      SORT_ORDER_2
,      SORT_OPTION_3
,      SORT_ORDER_3
,      GROUP_BY_PAYMENT_METHOD
,      ZD_EDITION_NAME
FROM IBY.IBY_INSTR_CREATION_RULES;

Dependencies

[top of page]

IBY.IBY_INSTR_CREATION_RULES does not reference any database object

IBY.IBY_INSTR_CREATION_RULES is referenced by following:

IBY: IBY_INSTR_CREATION_RULES#