Business Rules table validation range overlap

During table validation, range overlap errors occur when the range values are not configured properly for range key fields.

When defining the records for Business Rules tables, the values in the key fields must be unique for every record in the table. For tables that have ranges as key fields, the range values cannot overlap for records where all of the non-range key fields have the same values. A range overlap occurs when the range value for one record either lies completely within or contains part of the same range of another record. The values for a range key can be exactly the same for two records as long as there is some other key field that makes each record unique.

The tables can have more than one range as key fields. The following examples are for a table that has two ranges, credit amount and delta credit amount, as key fields. All of the fields except for the number of reviews are key fields.

Example of a table with range overlaps

Table 1 shows the sample data for a table that has range overlaps.
Table 1. Example of a table with range overlaps
  CATEGORY ACTION ACCT_NUM CREDIT_AMT_LOW CREDIT_AMT_HIGH DELTA_CREDIT_AMT_LOW DELTA_CREDIT_AMT_HIGH NUM_REVIEWS
Record 1 TCR ReviewInsert 9876543210 0 9999.99 0 9999.99 2
Record 2 TCR ReviewEdit 9876543210 1000 9999.99 1000 9999.99 1
Record 3 TCR ReviewInsert 9876543210 0 999.99 0 999.99 1
Record 4 TCR ReviewInsert 9876543210 10000 99999.99 5000 9999.99 2
Record 5 TCR ReviewInsert 9876543210 10000 99999.99 10000 99999.99 2
The following records in this table have range overlaps:
  • Record 1 and record 3 overlap because the credit range of record 3 (0-999.99) is completely within the credit range of record 1 (0-9999.99).
  • Record 1 and record 4 overlap because the delta credit range of record 4 (5000-9999.99) is completely within the delta credit range of record 1 (0-9999.99).
The following records in this table do not have a range overlap:
  • Record 2 does not overlap because at least one of the non-range key fields is different. Even though both the credit range and delta credit range of record 2 overlaps with record 1, the action field is different and makes the record unique.

Example of a table without range overlaps

Table 2 shows the sample data for a table that does not have range overlaps.
Table 2. Example of a table without range overlaps
Record identifier CATEGORY ACTION ACCT_NUM CREDIT_AMT_LOW CREDIT_AMT_HIGH DELTA_CREDIT_AMT_LOW DELTA_CREDIT_AMT_HIGH NUM_REVIEWS
Record 1 TCR ReviewInsert 9876543210 100 999.99 0 0 1
Record 2 TCR ReviewInsert 9876543210 100 999.99 100 999.99 1
Record 3 TCR ReviewInsert 9876543210 10000 99999.99 1000 9999.99 2
Record 4 TCR ReviewInsert 9876543210 10000 99999.99 10000 99999.99 2
The records in this table do not overlap for the following reasons:
  • Record 1 and record 2 do not overlap because their credit ranges are exactly the same and do not overlap. Also, the delta credit range is a key field and the range values do not overlap for the two records (0-0 and 100-999.99), which makes each record unique.
  • Record 3 and record 4 do not overlap because their credit ranges are exactly the same and do not overlap with the credit ranges of any other record. Also, their delta credit ranges do not overlap.