Description
This page handle the issue of missing objects after analyzing a SAP / ABAP application.
Observed in CAST AIP
Release | Yes/No |
|---|---|
| 8.3.x |  |
Observed on RDBMS
RDBMS | Yes/No |
|---|---|
| CSS | |
Action Plan
Check if the ABAP files start with LSVIM*, The LSVIM* files are skipped by ABAP analyzer.
These files are generated by the SAP system and they are not part of the actual source-code, hence these files are not picked by the analyzer.
These included files are generated as a standard when a table maintenance dialog is created. These Included files should be excluded when the extractor program runs.
Please refer the list for the patterns of files.txt which are getting excluded by ABAP analyzer.
- Check if the Author field in the file PG_DESCR_*.xml is set to "SAP". If it is, then set it to the same value as the lastmodificationauthor field (as long as it is not SAP). The ABAP analyze will set as external any object with a lastmodificationauthor or author as "SAP" and not provide results for it. There will be a fix in a future release of the SAP analyzer for the "author' field being "SAP" and the lastmodificationauthor field being something other than "SAP" to recognize this as non-external.
- See the documentation here for more information: SAP ABAP - Technical notes and limitations#Codeconsideredasexternal/generated
- Select the page you are interested in (if you are missing LSVIM* files, please see the page below on 'No file to parse' for further details):
- If the problem you are facing does not match any case listed in this page, report your problem to CAST Technical Support and provide the below relevant input.
Relevant input
Sherlock export with the following options: Export Logs , Export Configuration files, Export CAST Bases, Source code
Notes/comments
Related Pages
