Transaction Configuration Center - AFP Calibration - Data Function - Incorrect DET - DET value is not equal to the number of columns in Enlighten

TCC is showing number of DETs that is not equal to the number of columns in Enlighten. For example DET is set to 1, even though number of columns in the I/p file is more than 1.

This page describes how to handle the issue related to DET value computed by TCC.

1. Check whether the reported issue is part of the known cases

   1. Case 1: When having an end point custom definition, DET is set to default FP value

      Here is a scenario explaining this case. Transaction A has an FP on 1. When looking in the call graph of the transaction (right click on the transaction "view call graph"), it ends up with B (a transaction end point that is part of custom definition). if the default FP value associated to B end point is 1, it is the expected behavior to get a DET of 1 at transaction level.

   2. Case 2: DET value of some PL/SQL data functions has changed after a migration from CAST AIP 7.0.x to 7.3.x even though the source code itself has not changed

   Contrary to CAST AIP 7.0.x (x<10), in CAST AIP 7.3.x/8.0.x, the offline PL/SQL Analyzer deletes from the CAST local database all objects that no longer exist in the source code. Consequently, the DET value of data functions involving any of these "ghost" objects will change since they will have been cleaned up in 7.3.x/8.0.x. The phenomenon can be observed for table, table columns, materialized views, and columns of materialized views.

   As a direct result of the clean-up of these "ghost" objects, when migrating from CAST AIP 7.0.x (x<0)  to CAST AIP 7.3.x/8.0.x and after running a snapshot in CAST AIP 7.3.x/8.0.x, results may show:

   • • 1. A decrease in the DET value of some PL/SQL data functions (the 7.3.x/8.0.x's DET value is smaller than the 7.0.x's because some "ghost" objects and/or columns have been cleaned up)

       2. A decrease in the Function Point value of some of the above data functions which DET value has decreased enough for crossing a threshold (since the number of FPs does not linearly depend on the DET value).

2.  if not, contact CAST Support with the following Relevant input.

Relevant input

1. Sherlock export without source code.

2. Screenshots showing the DET value from TCC and another one from enlighten explaining why the DET value is not the expected one (showing number of column for the tables being part of the Datafunction /transaction.
   

SCRAIP - 3242,SCRAIP - 5486