Contents: Related pages: |
To analyze ABAP code in Kiuwan, source code and information from SAP system need to be exported previously to be analyzed by Kiuwan. SAP Extractor (SAPEX) for Kiuwan performs these tasks. NOTE: SAPEX is expected to run in any SAP NetWeaver 7.4+ platform. Please read How to know the SAP NetWeaver version if you need to know the SAP NetWeaver verion your are using. Contact Kiuwan Technical Support Kiuwan Support for previous platform versions. |
Using SAPGUI to check the version of NetWeaver (ABAP Application Server)
Depending on your use of SAPEX (Remote or Local) the permissions are different.
Remote usage of SAPEX means that SAPEX functionality is executed within an external system. This means that you will use KLA to remotely connect to the SAP Server to extract the code and analysis it. In this remote scenario, SAP Server acts as a pure server host that provides the needed APB source files so KLA can execute the analysis on them. Therefore, KLA will use a SAP user to connect to SAP server to extract the code (i.e. to invoke the SAPEX RFCs).
In a Local usage of SAPEX, you will need to configure a SAP user with permissions to run the code extraction and execute the SAPEX programs.
Regardless of local vs remote usage, there are some common permissions the SAPEX user needs to be granted:
Object : S_DATASET
ACTVT = 06, 33, 34
FILENAME = DIR_HOME/sape4k/*
Note: if you configure the SAP instance to be balanced to a group of SAP servers, you will need to configure this permission in every SAP server (because DIR_HOME will be different for every SAP instance)
Object : S_LOG_COM
COMMAND = 'ZKW_MKDIR', 'ZKW_RMDIR'
OPSYSTEM = Operating System type ( SY-OPSYS system variable) established for SM69 commands (for example, Linux, UNIX, ANYOS, Windows NT, etc… )
HOST = SAP server where above commands will be executed ( "*" or SY-HOST system variable, recommended * )
Object : S_RZL_ADM
ACTVT = 03
Needed to remove export temporary directories of SAP server
For SAPEX remote usage, SAP user must be type B ("system") .
A type B user with above privileges should also be granted next authorizations:
Object : S_RFC
ACTVT = 16
RFC_TYPE = ‘FUGR’
RFC_NAME = ‘ZKW_SAPEX_FG’, ‘SYST’,’ RFC1’,’ SDIFRUNTIME’
In a Local scenario, SAP user must be type A ("dialog").
Besides common authorizations (above explained), this SAP user must also have next ones:
Object : S_TCODE
ZKW_COD,
ZKW_MET
ZKW_ANA
ZKW_SAPEX_CODE
ZKW_SAPEX_METADATA
ZKW_ANALYSIS
ZKW_ANALYSIS_TO
SAP Extractor for Kiuwan (SAPEX) is distributed as a Transport Request. This way, you can easily install all the required SAPEX source programs importing the transport request into your target SAP system. SAPEX binay files (data-file and co-file) are contained into
Note: If you cannot use this installation mechanism you can also install SAPEX by manually installing source code ( please visit Manual Installation of SAP Extractor) |
In this section we will import the Transport Request for SAPEX that is included in your Kiuwan Local Analyzer distribution.
You can find the Transport Request as a zip file ( |
First, just unzip into your local system. This will extract two files :
Please note that last 3 digits of the transport numbers might be different in most recent versions.
Next, you need to copy the extracted co-file and data-file to your SAP System.
Please note that destination directories are for a unix sap system. In case of a SAP Windows system, typically is <drive>:\usr\sap\trans |
If you have direct access to your SAP system, you can directly copy them.
Otherwise, execute SE37 and execute ARCHIVFILE_CLIENT_TO_SERVER function. Click on Test/Execute
Then select the files you want to import (in your local machine) and the target path (in the SAP server), check the Uppercase/Lowercase and Execute it.
In order to confirm the copy, you can use AL11 to check the transfer was done to the correct places.
Execute it and double click on DIR_TRANS row.
For cofiles, you should see something like tha below image. Similarly for data directory.
Next, SAPEX Transport Request must be imported into your SAP system |
Execute STMS and click on Import Overview
Then you will see your Import Queue(s).
Double-click on the queue and you will see the requests for that queue.
Now you should add the SAPEX Transport Request ( Extras >> Other Requests >> Add)
Click on the Transp. Request to see available Transport Requests:
Select it
Then you will see the SAPEX Transport Request, select it and click on Import Request
Check the Options tab as below.
Once finished the import process, you can check it using SE09.
After importing SAPEX Transport Request, you must create OS commands (ZKW_MKDIR and ZKW_RMDIR)
To do it, please follow instructions at Create OS commands (ZKW_MKDIR and ZKW_RMDIR)
Only in case you decide a local scenario, you must create OS command (ZKW_KLA_AGENT)
To do it, please follow instructions at Create OS command to launch the analysis (ZKW_KLA_AGENT)