Transaction Configuration Center - Enhancement - Automated Enhancement Technical Points variation - MODIFIED AETP with unchanged source code

This page troubleshoot the case when there is Modified AETP without change in the source code:

Step by Step scenario

1. Compute snapshot
2. Connect to TCC
3. Go to the Enhancement node

Perform the below actions

1. Get the list of objects contributing to the MODIFIED automated enhancement technical point for a snapshot by referring to SQL Queries - CAST Central Base - Queries on Objects - How to get the list of objects contributing to the MODIFIED automated enhancement technical point for a snapshot
   1. If the query returns rows
      1. Check if the objects contributing to the MODIFIED automated enhancement technical point for the current snapshot are modified between the two snapshots , for this refer to SQL Queries - CAST Central Base - Queries on Objects - How to get the list of modified objects between two snapshots, here we can encounter 3 cases:
         
         1. All the objects contributing to the MODIFIED automated enhancement technical point for the current snapshot are modified between the two snapshots, in this case we need to check if this modification is a legitimate modification, for this we need to compare the source code of the objects between the two run.
            
            1. If the source code of the object is changed between the two runs then its expected that the objects are modified between the two snapshots hence its expected to get MODIFIED automated enhancement technical point.
            2. Else If the source code of the object has not changed between the two runs then compare the checksum of the objects between the two knowledge schema corresponding to the two snapshots from where the automated enhancement technical point is modified, to get the checksum of an object from the knowledge schema refer to SQL Queries - CAST Central Base - Queries on objects - How to get the Checksum value of an object:
               1. If the checksum is changed between the two knowledge schema then the checksum was wrongly calculated during the analysis step, to investigate the issue refer to CMS Snapshot Analysis - Run Analyzer
               2. If the checksum has not changed between the two knowledge schema then the checksum was wrongly transferred from the knowledge schema to the central schema, to investigate the issue refer to CMS Snapshot Analysis - Compute Snapshot
                  
         2. All the objects contributing to the MODIFIED automated enhancement technical point for the current snapshot are unchanged between the two snapshots, in this case the issue is located in the metric calculation of modified objects, contact CAST Technical Support. with the following  Relevant input 
         3. Part of the objects contributing to the MODIFIED automated enhancement technical point for the current snapshot are modified between the two snapshots and the other part are not modified between the two snapshots, for each part proceed as above.
   2. else if the query does not returns rows then contact CAST Technical Support. with the following  Relevant input 
      
2. If the above steps do not solve your issue contact CAST Technical Support. with the following  Relevant input 

Ticket # Number, Number