1. Tables and Views for Financials
  2. IBY_PMT_CREATION_RULES

IBY_PMT_CREATION_RULES

IBY_PMT_CREATION_RULES specifies how documents payable are grouped into payments. Creation rules are determined by payment process profiles. This table corresponds to the Payment 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_PMT_CREATION_RULES_PK

SYSTEM_PROFILE_CODE

Columns

Name Datatype Length Precision Not-null Comments
SYSTEM_PROFILE_CODE VARCHAR2 100 Yes Unique primary key
GROUP_BY_ULTIMATE_DEBTOR VARCHAR2 1 Yes or No flag indicating whether documents payable should be built into separate payments when they have different values for ultimate debtor.
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_DETAILS_FLAG VARCHAR2 1 Yes Yes or No flag indicating whether documents payable should be built into separate payments when they have different values for payment details.
GROUP_BY_BANK_CHARGE_BEARER VARCHAR2 1 Yes Yes or No flag indicating whether documents payable should be built into separate payments when they have different values for bank charge bearer.
GROUP_BY_DELIVERY_CHANNEL VARCHAR2 1 Yes Yes or No flag indicating whether documents payable should be built into separate payments when they have different values for delivery channel.
GROUP_BY_REMITTANCE_MESSAGE VARCHAR2 1 Yes Yes or No flag indicating whether documents payable should be built into separate payments when they have different values for remittance message.
GROUP_BY_MAX_DOCUMENTS_FLAG VARCHAR2 1 Yes Yes or No flag indicating whether there is a limit on the number of documents payable that can be grouped into one payment.
GROUP_BY_UNIQUE_REMIT_ID_FLAG VARCHAR2 1 Yes Yes or No flag indicating whether documents payable should be built into separate payments when they have different values for unique remittance identifier.
GROUP_BY_SETTLE_PRIORITY_FLAG VARCHAR2 1 Yes Yes or No flag indicating whether documents payable should be built into separate payments when they have different values for settlement priority.
GROUP_BY_PAYMENT_REASON VARCHAR2 1 Yes Yes or No flag indicating whether documents payable should be built into separate payments when they have different values for payment reason.
GROUP_BY_DUE_DATE_FLAG VARCHAR2 1 Yes Yes or No flag indicating whether documents payable should be built into separate payments when they have different values for due date.
MAX_DOCUMENTS_PER_PAYMENT NUMBER 18 Maximum number of documents that can be grouped into a single payment. This value will only be used if GROUP_BY_MAX_DOCUMENTS_FLAG is set to Y.
PAYMENT_DETAILS_LENGTH_LIMIT NUMBER 18 Maximum length of the payment detail record. Typically, this is a type of description record in a payment format that allows concatenated details of the payment to be included, for example, invoice numbers. If this length is exceeded, then the payment will be split into multiple payments.
PAYMENT_DETAILS_FORMULA VARCHAR2 240 SQL function to be used to concatenate the document attributes into the payment details information
GROUP_BY_INVOICING_ORG VARCHAR2 1 Yes Yes or No flag indicating whether documents payable should be built into separate payments when they have different values for invoicing business unit.
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_PMT_CREATION_RULES iby_sys_pmt_profiles_b SYSTEM_PROFILE_CODE

Indexes

Index Uniqueness Tablespace Columns
IBY_PMT_CREATION_RULES_U1 Unique Default SYSTEM_PROFILE_CODE, ORA_SEED_SET1
IBY_PMT_CREATION_RULES_U11 Unique Default SYSTEM_PROFILE_CODE, ORA_SEED_SET2