To Do Message

Feature configuration %1 option %2 for customer contact type %3 and class %4 is missing.

Start Date of Bill Line period must be <= End Date of Bill period.

Reading must be a non-negative number.

%1 field should be greater than zero.

Actual Change Date %1 on transaction is the same as the Effective Date for existing Meter Config %2.
Error Message %1 %2 not found.
Base or Custom? Rootcause

This message will only be triggered when:

- Customer Contact was updated/created
- Customer Contact Type and Action Type combination is existing in Feature
Custom config CM_CC_UXP

Algorithm CM-CMPREBADJ only apply adjustment against eligible SA with SALES

case, however if the quote (case) is cancelled or withdrawn after SA Activation,
then the adjustments should be manully reversed. Recent change for CTP is
QC810 (Fix NPE in getCampaignRebateContractValue last 12/20/18). This is not a
case exception though. The created adjustment by this Algo might/might not
Base affect the creation of bill, thus creating this exception on the case.

select * from ci_sa_char where sa_Id in (select sa_id from ci_sa_sp where
sp_id='6048908128') and char_type_cd='PRODSW';
select * from ci_sa_sp where sa_sp_id='1370264554';
select sachar.effdt, sa.start_dt, sa.sa_id, sachar.char_type_cd from ci_sa_char
sachar, ci_sa sa where sachar.sa_id = sa.sa_id and sa.sa_Id in (select sa_id from
ci_sa_sp where sp_id='6048908128') and char_type_cd='PRODSW';
The condition in the program for the creation of the new meter read is
product switch char found in SA AND product switch char effective date == SA
Base start date AND SASP start meter read ID is empty

It was being triggered by ProgramCMPITPSX_Impl (converted cobol to java

program). This message will be created having the criteria:
-Read Days is less than Actual Days
-Apply TOU switch is Y
-TOU days configured is either null or zero in value.
Base Raju will replicate this in v2.1 environment

Error was encountered upon processing meter and register (Case type: CM-
ESDCR, Status: PROCMTREG, Enter Processing Algo: CMEUMTREG, Seq: 10) This
message was triggered upon processing via category B having criteria:
-Energy type is Electricity
-Connected meters with register
-Has meter configuration matched to SP and Meter
-Installation type is Basic
-Category B (Meter is connected to SP and Meter Configuration is changed)
-CATS actual change date = Meter Config effective date
The reason why the created to do was C1-CSEXC is because it was a base To Do
Custom type being created when an exception occurs upon trying to transition a case.
Base In Progress - New to do message identified