IBY_INSTR_CREATION_RULES
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.
Details
-
Schema: FUSION
-
Object owner: IBY
-
Object type: TABLE
-
Tablespace: REFERENCE
Primary Key
| Name | Columns |
|---|---|
|
IBY_INSTR_CREATION_RULES_PK |
SYSTEM_PROFILE_CODE |
Columns
| Name | Datatype | Length | Precision | Not-null | Comments |
|---|---|---|---|---|---|
| SYSTEM_PROFILE_CODE | VARCHAR2 | 100 | Yes | Unique primary key | |
| ORG_ID_FLAG | VARCHAR2 | 1 | Business unit flag | ||
| CREATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who created the row. | |
| CREATION_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the creation of the row. | ||
| LAST_UPDATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who last updated the row. | |
| LAST_UPDATE_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the last update of the row. | ||
| LAST_UPDATE_LOGIN | VARCHAR2 | 32 | Who column: indicates the session login associated to the user who last updated the row. | ||
| OBJECT_VERSION_NUMBER | NUMBER | 9 | Yes | Used to implement optimistic locking. This number is incremented every time that the row is updated. The number is compared at the start and end of a transaction to detect whether another session has updated the row since it was queried. | |
| GROUP_BY_PAYMENT_DATE | VARCHAR2 | 1 | Yes | Yes or No flag indicating whether payments should be put into separate payment files when they have different values for payment date. | |
| GROUP_BY_PAYMENT_CURRENCY | VARCHAR2 | 1 | Yes | Yes or No flag indicating whether payments should be put into separate payment files when they have different values for payment currency. | |
| GROUP_BY_INTERNAL_BANK_ACCOUNT | VARCHAR2 | 1 | Yes | Yes or No flag indicating whether payments should be put into separate payment files when they have different values for disbursement bank account. If the processing type on the payment process profile is Printed, this flag is automatically set to Yes and cannot be overridden. | |
| GROUP_BY_MAX_PAYMENTS_FLAG | VARCHAR2 | 1 | Yes | Yes or No flag indicating whether there is a limit on the number of payments that can be grouped into one payment file. | |
| GROUP_BY_PAY_SERVICE_REQUEST | VARCHAR2 | 1 | Yes | Yes or No flag indicating whether payments should be put into separate payment files when they originated in different payment process requests. | |
| GROUP_BY_LEGAL_ENTITY | VARCHAR2 | 1 | Yes | Yes or No flag indicating whether payments should be put into separate payment files when they have different values for legal entity. | |
| GROUP_BY_BILL_PAYABLE | VARCHAR2 | 1 | Yes | Yes or No flag indicating whether payments should be put into separate payment files when they have different values for bill payable. | |
| GROUP_BY_ORGANIZATION | VARCHAR2 | 1 | Yes | Yes or No flag indicating whether payments should be put into separate payment files when they have different values for business unit. | |
| GROUP_BY_MAX_INSTRUCTION_FLAG | VARCHAR2 | 1 | Yes | Yes or No flag indicating whether there is a limit on the total payment amount when payment file is created. This value is set to Yes when a value is specified in the MAX_AMOUNT_PER_INSTR_VALUE column. | |
| GROUP_BY_PAYMENT_FUNCTION | VARCHAR2 | 1 | Yes | Yes or No flag indicating whether payments should be put into separate payment files when they have different values for payment function. | |
| GROUP_BY_PAYMENT_REASON | VARCHAR2 | 1 | Yes | Yes or No flag indicating whether payments should be put into separate payment files when they have different values for payment reason. | |
| GROUP_BY_RFC | VARCHAR2 | 1 | Yes | Yes or No flag indicating whether payments should be put into separate payment files when they have different values for regional finance center. | |
| MAX_PAYMENTS_PER_INSTRUCTION | NUMBER | 18 | 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 | 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, such as corporate, spot, and daily, used to compare the payment file total amount to the maximum total amount allowed. Types are defined in the General Ledger currency exchange rate type table. | ||
| 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 | Yes | Yes or No flag indicating whether payments should be put into separate payment files when they have different values for payment method. | |
| SEED_DATA_SOURCE | VARCHAR2 | 512 | Source of seed data record. A value of 'BULK_SEED_DATA_SCRIPT' indicates that record was bulk loaded. Otherwise, specifies the name of the seed data file. | ||
| ORA_SEED_SET1 | VARCHAR2 | 1 | Yes | Oracle internal use only. Indicates the edition-based redefinition (EBR) context of the row for SET1. Context values are Y or N. | |
| ORA_SEED_SET2 | VARCHAR2 | 1 | Yes | Oracle internal use only. Indicates the edition-based redefinition (EBR) context of the row for SET2. Context values are Y or N. |
Foreign Keys
| Table | Foreign Table | Foreign Key Column |
|---|---|---|
| IBY_INSTR_CREATION_RULES | iby_sys_pmt_profiles_b | SYSTEM_PROFILE_CODE |
Indexes
| Index | Uniqueness | Tablespace | Columns |
|---|---|---|---|
| IBY_INSTR_CREATION_RULES_U1 | Unique | Default | SYSTEM_PROFILE_CODE, ORA_SEED_SET1 |
| IBY_INSTR_CREATION_RULES_U11 | Unique | Default | SYSTEM_PROFILE_CODE, ORA_SEED_SET2 |