S/4Accelerate Code Extraction - with a Central Check System

We gathered a shortlisted guideline list for your Panaya SAP S/4Accelerate Extraction Process.
This article includes links and references to other valuable resources. 

These instructions are for an S/4HANA upgrade using Panaya S/4Accelerate.  If you are upgrading your ECC version or performing a conversion to S/4HANA from ECC using Panaya S/4Convert, please use these instructions.

These instructions assume you will be executing the ABAP Test Cockpit using a Central Check system.  If you are going to run ATC locally on your S/4Hana system, please use these instructions.

Step A - Downloading and Importing the SI Catalog and executing the SI check report 

1. Navigate to https://launchpad.support.sap.com/#sic
   

   

2. Select the S4/HANA target version

3. Click on the right-hand side of the Item Overview menu bar to download the Simplification Item Catalog < todaysdate >.zip .
   

   

4. On your system where Panaya code extractor is running and if applicable on the target SI system, Execute SE38
   Execute program /SDF/RC_START_CHECK
   Select Upload Simplification Item Catalog and then select the ZIP file downloaded in the previous step (make sure to save the zip and reuse the same version in other systems).
   
   

5.  Login to your target SI system (QA or Prod) using client 000, select your "Target SAP S/4HANA Version", and then Execute (F8):
   

   

   
   6. From the result screen of /SDF/RC_START_CHECK, start the consistency checks for all relevant Simplification Items with the “Check Consistency for All” button
   

   

   7. If Step 6 is taking too long, please review the following article.
   
   
   

Step B - ABAP Test Cockpit (ATC) Preparations

Setup of SAP NetWeaver 7.51, 7.52, or later (SAP_BASIS) and using a Central Check System. The ATC runs here. Please read this article first.
You can also use your own system if it is SAP S/4 1709 or higher, then follow this article instead.

Implement these SAP Notes on Checked and on the Central Check System (Make sure to address manual post-implementation instructions).

• 2436688 - Recommended SAP Notes for using SAP S/4HANA custom code checks in ATC (with manual post/ imp. steps)

• 2423013 - Code Inspector test checksum infrastructure

• 2505671 - Uniform saving of navigation information

• 2518335 - ATC or Code Inspector incorrectly displays findings

• 2524014 - ATC: Problems When Checking Modified SAP Code (with manual post imp. steps)

• 2942419 - Include ATC check 'S/4HANA: Readiness Check for SAP Queries' to the SAP S/4HANA custom code checks

• 3105801 - API: Internal error for call of function IQAPI_CONVERT_CODETYPE

Apply the note that corresponds to your S/4HANA target version -

• 2659194 - Check variant for SAP S/4HANA 1809 custom code checks (with manual post imp. steps) if Target version is S/4HANA 1809 only

• 2812556 - Check variant for SAP S/4HANA 1909 custom code checks (with manual post imp. steps) If Target version is S/4HANA 1909 only

• 2959341 - Check variant for SAP S/4HANA 2020 custom code checks (with manual post imp. steps) If Target version is S/4HANA 2020 only

• 3090106 - Check variant for SAP S/4HANA 2021 custom code checks (with manual post imp. steps) If Target version is S/4HANA 2021 only

• 3231748 - Check variant for SAP S/4HANA 2022 custom code checks (with manual post imp. steps) If Target version is S/4HANA 2022 only

• 3365357 - Check variant for SAP S/4HANA 2023 custom code checks (with manual post imp. steps) If Target version is S/4HANA 2023 only

Additional Notes to implement only in case of issues -

• 2546419 - ASSERTION_FAILED in get_message_text

• 2250196 - Update of Report MFLE_CLS4H_CHECKS_CC ( based on 2216958)

• 2423931 - MFLE_CLS4H_CHECKS_CC dumps with SAPSQL_LIKE_PATTERN_TOO_LONG

• 2794505 - ATC reports finding for in SAP includes belonging to USER-EXITS function groups (if ATC includes User exits)

• 2973326 - Short dump during check of programs with DynPro logic by CL_CI_TEST_ANALYZE_SELECT_HANA

• 2503289 - ATC: The display of ATC results is extremely slow

• 2546419 - ASSERTION_FAILED in get_message_text

Apply these notes on the Central Check System -

• 2485231 - Remote ATC Checks of Modifications and Enhancements 

• 2270689 - RFC Extractor for performing static checks 

• 2190065 - ATC/CI: Remote Code Analysis - Object Provider Stub 

• 2527903 - Remote analysis (for check system)

• 2364916 - Recommended SAP Notes for using ATC to perform remote analysis

Step C - Downloading & Importing the Simplification Database Content

To download the Simplification Database Content - 

1. Navigate to https://support.sap.com/swdc

2. Select Software Downloads

3. Search for Component CCMSIDB (select Downloads and enter CCMSIDB in the search area of the screen)

4. Download the latest patch of the displayed Simplification Database Content
   See SAP Note 2241080 - SAP S/4HANA: Content for checking customer-specific code

5. Save the Simplification Database Content ZIP file locally

To import the Simplification Database Content - 

After you have successfully downloaded the ZIP file from the SAP Service Marketplace.

Check you have the following authorizations -

1. On your system or if applicable on the Central Check System, run transaction SYCM.

2. Use the menu to select Simplification Database Import from ZIP File

3. Select the ZIP file previously downloaded, then confirm with Open

The ATC uses the SCI and runs the following predefined SCI variants -

• S4HANA_READINESS: Provides checks for SAP S/4HANA readiness (search for DB operations, field length extensions, and so on)
  

• FUNCTIONAL_DB: Provides functional checks for optimizing database access

Step D - ATC Setup, Configuration & Execution 

1. Set up User with Role SAP_SATC_ADMIN
   (Description - Authorization for setting up ABAP Test Cockpit (ATC) for central quality checking)
   Add the following Authorization Objects to enable import of the simulation DB
   
   

   Authorization Object	Field	Value
   S_YCM	SYCM_AREA	SDB
   S_YCM	ACTVT	SDB

2.  SET up an ATC RFC to the SBX as described in the section “Create RFC Connection.”  
   Click here for the required authorizations.
   
   

3. Run transaction ATC in the central check system and configure the remote ATC Checks as described here.  

Step E - SAP Code Inspector (SCI) for HANA 2.0  (optional)

For HANA 2.0 Migration prep. and performance results, the SAP Code Inspector needs to be run and its results uploaded in the extract process.
Run the SCI for 2 variants - ZPANAYA_FUNCTIONAL_ADDITION_DB and PERFORMANCE_DB.
Learn more

Step F - Creating RFC Connections

1. Identify a User for the RFC to use on each system to be accessed (Not a personal user).

2. Set Authorizations required for the code extraction RFC user

3. Use SM59 to create RFCs as follows (more details here).
   1 RFC per Application server per direction is required unless different clients are used.
   For instance, SI needs to be run on client 000 but the production client is different. SAP suggest also alternative RFC strategies here.
   
   

   	RFC Destination	Connection Type	Description 1
   From ATC system to SBX	ATC_RFC	3 (ABAP connection)	ATC_RFC
   From SBX to PROD	PANAYA_PRD	3 (ABAP connection)	PANAYA_PRD
   From SBX to ATC system	PANAYA_ATC	3 (ABAP connection)	PANAYA_ATC
   From SBX to PROD/Quality system (client 000)	PANAYA_SI *	3 (ABAP connection)	PANAYA_SI

• Additional RFC's to enrich the Analysis Results (validation can be disabled if required)
  

  From SBX to SOLMAN	PANAYA_SM	3 (ABAP connection)	PANAYA_SM
  From SBX to BW	PANAYA_BW	3 (ABAP connection)	PANAYA_BW

* The PANAYA_SI RFC is applicable for SAP S/4HANA version upgrades (e.g. 1709-2020). For SP upgrades, this RFC is optional.

Step G - Downloading & Extracting Code, Configuring & Executing

1. In Panaya, click on the Settingsbutton to open up the settings panel

2. Select your current ERP version
    

3. Download the ABAP code
    

4. Create an executable program named ZPANAYA_EXTRACT_PROG_LIB and import or paste the ABAP code

5. Execute transaction SE38 and type the program name ZPANAYA_EXTRACT_PROG_LIB and click on the execute button. 

6. Select Background mode and enter the Background Directory path (e.g. \tmp) on the SAP application server. Running the extraction in Foreground mode is not recommended and may fail on larger SAP systems. For best performance and reliability, please use the Background mode.

7. For Target system under RFC destination, type - PANAYA_PRD, Enter the RFC destinations for Solution Manager target system, PANAYA_SM, and BW target system (optional) PANAYA_BW:

   

   

8. For the Simplification Items Check RFC Destination, type - PANAYA_SI 
   Use client 000 when running SI checks (results in reporting all errors for all other clients). Be sure to configure the PANAYA_SI RFC destination to use client 000, more information can be found here.
   If you have previously extracted & uploaded SI results, these can be reused by checking Use previous SI | Contact Panaya Support for more details 

9. For the ATC for S/4 HANA RFC Destination, type PANAYA_ATC, and then click on Choose and select the relevant check from the list of checks that were previously executed in Step D.

10. Optional - For the ATC - CDS S/4 HANA Core Data Services RFC Destination, type PANAYA_ATC, and then click on Choose and select the relevant check from the list of checks that were previously executed here.

11. For the HANA SAP Code Inspector execution mode choose option A or read here for more options. 

12. For the Fiori Apps, ODATA Services and ODATA Usage, the default is NONE and Panaya_PRD.  This means that they will be extracted from the same system where the Panaya code extraction is running, and their usage from the target Production system.  For different configuration options, please see this guide.

13. Execute in Background mode.
    Help on these steps can be found here and a link to a recording showing this step here.

Step H - Upload Your Custom Code

1. Locate the extraction file. Click here to learn how.

2. Compress the XML file on the server using Gzip (RAR files are not supported). Alternatively, enable "Compress Results File Run Mode"  by manually configuring the parameters.

3. Do not edit or transfer the file using SAP transactions like AL11, CG3Z, or others. The file must stay in UTF-8 encoding format.

4. Use a file-transfer tool like WinSCP to download the file to your local computer.

5. After compression, upload the file to Panaya Code Box.

6. Select the relevant System in Panaya.  If you are not sure, check the PROJECTS page for the name of the System that is linked to the project, for example -
   Then select this System on the Code Box page -

   

7. Drop the ZIP file back to Panaya Code Box, or click to browse and select it.

8. Click on the Upload button.
   For Release Dynamix - Select whether you wish to update all active projects or only non-upgrade active projects (Release Dynamix projects only)

   

9. Once uploaded, you should receive a confirmation email regarding your custom code upload.

10. Users with the following permissions will be notified by email once the analysis is available (this usually takes 48 hours or less) -
    - Code Box - Upload ETL permission
    - Users - Create and Edit permission