Page tree
Skip to end of metadata
Go to start of metadata
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(tick)
8.2.x(tick)
8.1.x (tick) 
8.0.x (tick)
7.3.x(tick)
Observed on RDBMS
RDBMS
Yes/No
Oracle Server(tick)
Microsoft SQL Server(tick)
CSS3(tick)
CSS2(tick)
Action Plan
  1. 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.

  2. 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):
  3. 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 filesExport CAST Bases, Source code

Notes/comments


Related Pages



        

  • No labels