To successfully deliver and analyze SAP ABAP technologies, the following third-party software is required:
Install on workstation running the DMT (for extraction)
Install on workstation running CMS (for analysis)
|SAP||A specific extractor is delivered by CAST (see the section SAP Extractor below) and this must be installed and run on the SAP instance BEFORE the packaging/extraction is actioned in the CAST Delivery Manager Tool.||Nothing required||Nothing required|
CAST supports the analysis of ABAP client code and can also identify links from this client code to SAP tables/programs. To do so, information about the SAP tables and programs needs to be extracted from the SAP system and analyzed at the same time as the ABAP client code. To perform the extraction, a specific SAP extractor must be installed and run on the SAP instance BEFORE the extraction is actioned in the CAST Delivery Manager Tool. This extractor is run from the SAP instance and extracts information into flat files: these files are then manually or automatically transferred onto a Windows workstation for packaging/extraction via the CAST Delivery Tool Manager. You can find out more about this process in the CAST SAP Extractor NG.
Note that in order for CAST AIP to save SAP tables and programs in the CAST Analysis Service schema during an analysis, the following must be true:
- The SAP tables and programs must have been successfully extracted from the SAP system and analyzed with the ABAP client code
- AND the SAP tables and programs must be referenced in the ABAP client code
If only one of these things is true then the tables and programs will not be saved in the CAST Analysis Service schema.