Page tree
Skip to end of metadata
Go to start of metadata

This page presents the different messages that are produced by the SAP ABAP Analyzer during application source code analysis. Messages are documented with their identifier (referenced in the analysis log files), a description, and a possible remediation. The following information will help you to validate your analysis. 

ABAP.01

IdentifierABAP.01
MessageUnresolved Reference to '<CALLEE_NAME>' found in object '<CALLER_NAME>'.
SeverityWarning
ExplanationThe analyzer found a reference to an object called <CALLEE_NAME> and was not able to find out that object in the source code to be analyzed. 
User Action

Select the object <CALLEE_NAME> in the list of objects in the Unresolved folder of the technical browser in CAST Enlighten. Check the source code with the application team. If this is an application specific component, then it is recommended to add it to the analysis scope. Missing components could affect reference resolution and potentially quality rules.

 

ABAP.02

IdentifierABAP.02
MessageUnresolved Include '<INCLUDE_NAME>' found in object '<CALLER_NAME>'.
SeverityWarning
ExplanationThe analyzer found a reference to an include file called <INCLUDE_NAME> and was not able to find out the corresponding file in the source code to be analyzed. 
User Action

Select the object <INCLUDE_NAME> in the list of objects in the Unresolved folder of the technical browser in CAST Enlighten. Check the source code with the application team. If this is an application specific include, then it is recommended to add it to the analysis scope. Missing components could affect reference resolution and potentially quality rules.

ABAP.03

IdentifierABAP.03
MessageInclude resolution completed.
SeverityInformation
Explanation

All the include file references have been processed. The analyzer will now start the analysis. 

User ActionNothing special to do.  

ABAP.04

IdentifierABAP.04
MessageUnsupported syntax found at line <LINE> and column <COLUMN> in file '<FILENAME>' (<CODE>).
SeverityWarning
Explanation

The analyzer is not able to parse the piece of ABAP source code <CODE> correctly. The parsing of the source file <FILENAME> will not complete and only the corresponding object will be created without any properties and children objects.

Example:

- Unsupported syntax found at line 230 and column 28 in file 
  'C:\ABAP\CASTPUBS\ZPACKAGES\ZPACKAGESZMMRST\ZMMZ00X4_MAT_CHNG_DEL_RPT.ABAP_CAST' 
(
SELECT changenr tabname tabkey fname chngind INTO TABLE icdocs
      FROM cdpos
      FOR ALL ENTRIES IN icdhdr
      WHERE objectclas = 'MATERIAL'
        AND objectid   = icdhdr-objectid
        AND changenr   = icdhdr-changenr
        AND tabname    in ('MARA',
                           '
        AND chngind    <> 'I'.
---------------------------^
)


User ActionIdentify with the application team whether it is an incorrect syntax on the customer side (the source code should compile correctly). If not, then contact CAST Support.

ABAP.05

IdentifierABAP.05
MessageDuplicated object '<OBJECT_NAME>' found in file '<FILENAME>'.
SeverityWarning
ExplanationThe analyzer found 2 objects with the name <OBJECT_NAME> and same type in the source file <FILENAME>. Only the first one is taken in account.
User ActionIdentify with the application team the ABAP element and check if the source code compile correctly. If yes, then contact CAST Support.

ABAP.06

IdentifierABAP.06
MessageStarting macros resolution. This action may take a while...
SeverityInformation
ExplanationThe analyzer starts to process the macro directives in the source code. 
User Action

Nothing special to do. 

ABAP.07

IdentifierABAP.07
MessageMacros resolution completed.
SeverityInformation
ExplanationAll the macro directives found in the source code have been processed. 
User ActionNothing special to do. 

ABAP.08

IdentifierABAP.08
MessageThe following file will not be processed '<FILENAME>': duplicated program or report '<PROGRAM_NAME>'.
SeverityWarning
ExplanationThe analyzer found a source file containing a program called <PROGRAM_NAME> that has been already analyzed in another source file. In order to avoid duplicates, the second source file is not analyzed. This situation can occur when 2 versions of the same program have been delivered.
User ActionIdentify the duplicated object with the application team. Exclude the file from the next analysis.

ABAP.09

IdentifierABAP.09
MessageThe following file will not be processed '<FILENAME>': duplicated include '<INCLUDE_NAME>'.
SeverityWarning
ExplanationThe analyzer found a source file containing a include called <INCLUDE_NAME> that has been already analyzed in another source file. In order to avoid duplicates, the second source file is not analyzed. This situation can occur when 2 versions of the same include have been delivered.
User ActionIdentify the duplicated object with the application team. Exclude the file from the next analysis.

ABAP.10

IdentifierABAP.10
MessageThe following file will not be processed '<FILENAME>': duplicated function-pool '<FUNCTION_POOL_NAME>'.
SeverityWarning
ExplanationThe analyzer found a source file containing a function pool called <FUNCTION_POOL_NAME> that has been already analyzed in another source file. In order to avoid duplicates, the second source file is not analyzed. This situation can occur when 2 versions of the same function pool have been delivered.
User ActionIdentify the duplicated object with the application team. Exclude the file from the next analysis.

ABAP.11

IdentifierABAP.11
MessageThe following file will not be processed '<FILENAME>': duplicated type-pool '<TYPE_POOL_NAME>'.
SeverityWarning
ExplanationThe analyzer found a source file containing a type pool called <TYPE_POOL_NAME> that has been already analyzed in another source file. In order to avoid duplicates, the second source file is not analyzed. This situation can occur when 2 versions of the same type pool have been delivered.
User ActionIdentify the duplicated object with the application team. Exclude the file from the next analysis.

ABAP.12

IdentifierABAP.12
MessageThe following file will not be processed '<FILENAME>': duplicated user-exit '<USER_EXIT_NAME>'.
SeverityWarning
ExplanationThe analyzer found a source file containing a user-exit called <USER_EXIT_NAME> that has been already analyzed in another source file. In order to avoid duplicates, the second source file is not analyzed. This situation can occur when 2 versions of the same user-exit have been delivered.
User ActionIdentify the duplicated object with the application team. Exclude the file from the next analysis.

ABAP.13

 

IdentifierABAP.13
MessageLoading SAP tables . . .
SeverityInformation
ExplanationThe analyzer is loading the extraction files containing the information on database tables. The number of files depends on the size of the extraction.
User ActionNothing special to do.

ABAP.14

IdentifierABAP.14
Message<DB_TABLE_NUMBER> tables <DB_VIEW_NUMBER> views have been loaded.
SeverityInformation
ExplanationThis message presents the number of database tables and database views that have been identified in extraction files. This information can be used to validate the number of database tables that have been created in the Local base compared to the database tables that are used by the ABAP code.
User ActionNothing special to do.

ABAP.15

IdentifierABAP.15
MessageNo file to parse.
SeverityError
ExplanationThe analysis settings are not correct and no ABAP source files has been selected for being analyzed. 
User Action

Review the Analysis Unit configuration and the source file settings.

ABAP.16

IdentifierABAP.16
MessageUnresolved SAP database table or view: '<DB_TABLE_NAME>' called in object '<CALLER_NAME>'.
SeverityWarning
ExplanationThe analyzer found an Open SQL query refering to a database table or a database view called <DB_TABLE_NAME> that has not been identified in the extraction files. 
User Action

Select the object <DB_TABLE_NAME> in the list of objects in the Unresolved folder of the technical browser in CAST Enlighten. Check the SAP table extracted files with the application team and investigate why these tables or views have not been extracted. Missing components could affect reference resolution and potentially quality rules.

ABAP.17

 

IdentifierABAP.17
MessageUnresolved Class or Interface: '<NAME>' called in object '<CALLER_NAME>'.
SeverityWarning
ExplanationThe analyzer found a reference to a class or an interface called <NAME> that is not defined in any ABAP source file belonging to the analysis scope.  
User Action

Select the object <NAME> in the list of objects in the Unresolved folder of the technical browser in CAST Enlighten. Check the source code with the application team. Missing components could affect reference resolution and potentially quality rules.

ABAP.18

IdentifierABAP.18
MessageUnresolved Method: '<METHOD_NAME>' in class '<CLASS_NAME>' called in object '<CALLER_NAME>'.
SeverityWarning
ExplanationThe analyzer found a reference to a class method called <METHOD_NAME> for which no source code has been identified in the analysis scope. This could also occur when a parent class in which the method is defined has not been delivered.
User Action

Select the object <METHOD_NAME> in the list of objects in the Unresolved folder of the technical browser in CAST Enlighten. Check the source code with the application team. Missing components could affect reference resolution and potentially quality rules.

ABAP.19

IdentifierABAP.19
MessageUnresolved Member: '<MEMBER_NAME>' in class '<CLASS_NAME>' called in object '<CALLER_NAME>'.
SeverityWarning
ExplanationThe analyzer found a reference to a class member called <MEMBER_NAME> for which no source code has been identified in the analysis scope. This could also occur when a parent class in which the member is defined has not been delivered.
User ActionSelect the object <MEMBER_NAME> in the list of objects in the Unresolved folder of the technical browser in CAST Enlighten. Check the source code with the application team. Missing components could affect reference resolution and potentially quality rules.

ABAP.20

IdentifierABAP.20
MessageUnresolved Events: '<EVENT_NAME>' in class '<CLASS_NAME>' called in object '<CALLER_NAME>'.
SeverityWarning
ExplanationThe analyzer found a reference to a class event called <EVENT_NAME> for which no source code has been identified in the analysis scope. This could also occur when a parent class in which the event is defined has not been delivered.
User Action

Select the object <EVENT_NAME> in the list of objects in the Unresolved folder of the technical browser in CAST Enlighten. Check the source code with the application team. Missing components could affect reference resolution and potentially quality rules.

ABAP.21

IdentifierABAP.21
Message<MESSAGE>
SeverityWarning
ExplanationThe analyzer is not able to read a LIST file that contains the information on SAP transactions and various cases can be described by this message. This occurs when the file is not correctly generated by the CAST SAP Extractor.
User ActionIdentify the LIST file for which the message has been produced and contact CAST Support.

ABAP.22

IdentifierABAP.22
MessageLight processing file '<FILENAME>'.
SeverityInformation
ExplanationThe analyzer processes the source files in 2 steps. The first one aims to identify the different objects across the source files. The second one parses the code and resolves references. This message appears when the first step starts.  
User ActionNothing special to do.  

ABAP.23

IdentifierABAP.23
MessageProcessing file '<FILENAME>'.
SeverityInformation
ExplanationThe analyzer processes the source files in 2 steps. The first one aims to identify the different objects across the source files. The second one parses the code and resolves references. This message appears when the second step starts.  
User ActionNothing special to do.  

ABAP.24

IdentifierABAP.24
MessageUnresolved Transaction: '<TRANSACTION_NAME>' called in object '<CALLER_NAME>'.
SeverityWarning
ExplanationThe analyzer found a reference to a transaction called <TRANSACTION_NAME> that has not been identified in any extraction file. This can occur when the package in which the transaction is defined has not been delivered or is not part of the analysis scope.
User ActionSelect the object <TRANSACTION_NAME> in the list of objects in the Unresolved folder of the technical browser in CAST Enlighten. Check the source code with the application team. Missing components could affect reference resolution and potentially quality rules.

ABAP.25

IdentifierABAP.25
MessageLoading SAP database tables file '<FILENAME>'. . .
SeverityInformation
ExplanationThe analyzer is loading one of the extraction files containing the information on database tables.
User ActionNothing special to do.  

ABAP.26

IdentifierABAP.26
MessageResolving SAP database table Foreign Keys. . .
SeverityInformation
ExplanationThe analyzer creates links between database tables by following the Foreign Keys relations. 
User ActionNothing special to do.  

ABAP.27

IdentifierABAP.27
MessageSAP database table Foreign Keys resolved.
SeverityInformation
ExplanationThe analyzer completed the creation of links between database tables. 
User ActionNothing special to do.  
  • No labels