How to Install Panaya's Intelligent Code Remediation Synchronizer?

The installation of the Intelligent Code Remediation solution consists of the following -

  1. Server-Side Installation

  2. Client-Side Installation



Before starting the installation process, make sure that you have the following privileges:

  1. Access to the relevant SAP Development

  2. User with Display, create and execute ABAP programs permissions

  3. Panaya username and password

  4. .NET Framework, version 4.6.2 and above

  5. At least 100MB available in the Windows temp files directory

  6. SAP GUI for Windows: release 7.20, patch level 7 and later releases (including 7.30)

Supported operating systems: Windows 2000, Windows XP, Windows Vista, Windows 7, Windows 10
Supported browsersClick here for supported browsers information



  • Keep the original system for 3rd party packages
  • Panaya uses standard SAP Workbench Change Requests (CRs). For accurate results, verify that the CR includes all the required information to be considered as a valid transport (e.g., routing information).
  • You cannot submit an automatic fix for objects with Syntax errors. Your sync request will be declined to protect the existing code.
  • For every Object, a target system must be allocated. Panaya requires this information to be able to determine where to submit the CR.
  • To submit Intelligent Code Remediation (ICR) fixes to your SAP development or sandbox system, all custom objects Original System should point to the system where the fixes are submitted.
    Click here to learn how to change the original system for objects


Server Side Installation


Step 1 - Download the Source Code

The Intelligent Code Remediation fixes should be synced with your Development environment.

To download the Panaya Intelligent Code Remediation Synchronizer - 

  1. Click on the Settings button 

  2. Verify that the relevant System is selected in the drop-down list


  3. In SAP Development > Intelligent Code Remediation - Tool , select Download Code

Step 2 - Create an Executable Program & Transaction

  1. Open the downloaded TXT file and copy the entire source code displayed

  2. Use the copied source code to create a new executable program in SAP

  3. Name the program ZPANAYA_ACC_SYNC

  4. Create a transaction for the program named ZPANAYA_ACC_SYNC.
    The transaction type should be Program and selection screen (report transaction)

  5. Set permission to use the transaction ZPANAYA_ACC_SYNC for all users who are to sync Intelligent Code Remediation fixes

For further instructions on how to create an executable program & transaction in SAP, click here


Panaya RDx synchronizer requires that a transaction with the exact hard coded name ZPANAYA_ACC_SYNC be present in the system.
Be sure to create such a transaction and keep the name unchanged.

How to Uninstall?
To remove the Intelligent Code Remediation Synchronizer, delete the ABAP program ZPANAYA_ACC_SYNC.

Step 3 - Set Server Parameters

  • Enable GUI Scripting
    The Intelligent Code Remediation synchronizer requires SAP GUI scripting to be enabled.
    Please set the system profile parameters as shown below - 

    - sapgui/user_scripting = TRUE
    - sapgui/user_scripting_disable_recording = FALSE
    - sapgui/user_scripting_set_readonly = FALSE

More detailed information can be found here - 

How to set server parameters to enable GUI scripting?


Step 4 - Enable Authorizations for Users

Each user running the Panaya Synchronizer must have a set of authorizations within the SAP system as listed below:

  1. Object S_TCODE

  2. Object S_GUI (Authorization for GUI activities)
    a. ACTVT (Activity) – 61 (Export)
    Note - This authorization is required only in versions 4.7 and higher

Step 5 – Create a Transport

  1. Create a Workbench transport request for each target system where changes are required. All transports should be created before the sync run begins.
  2. In the created transport, create tasks for each user who will be required to submit changes.
  3. The transport(s) must have this exact description - 
    “PANAYA Automatic Code Corrections”

Good to Know!
If you only plan to apply changes to a single target system, one transport request is sufficient. 



Client Side Installation


Step 1 - Enable GUI Scripting & Deny Pop-Up Notifications

Panaya sync requires SAP GUI scripting to be enabled as well as disabling SAP pop-up notifications for accelerated testing.
The process described here must be repeated for every client machine using the Synchronizer.

Step 2 - Set SAP Network Settings to High-Speed Connection

To assure completeness and accuracy of data recorded please make sure the Network Settings is set to High Speed Connection for every client machine using the Synchronizer.
Follow the instructions described here.


Step 3 - Install .NET Framework
.NET Framework version 4.6.2 or above must be present on the local machine of each user running the Intelligent Code Remediation Synchronizer.
We recommend using .NET Framework version 4.0. Most computers already have .NET Framework, so normally no installation is needed.
If you experience issues while installing the Synchronizer, please install the .NET Framework from Microsoft .NET Framework 4.0.

Step 4 - Security Settings Configuration
Please ensure that proxy settings are not preventing the Synchronizer from working properly. 

If you have an anti-virus, VPN, Remote Machine or Virtual Machine, you might need to add Panaya to the safe domains list. Sites on this list do not require proxy or any other security permission.

Please add * to your white-list, or to your exceptions lists (e.g. proxy, anti-virus etc.)

Alternatively, add the following URL's to your white-list: or

Step 5 - Browser Configuration

  • Installation of a Click-Once add-on is required in order to use Google Chrome with Panaya's Intelligent Code Remediation synchronizer

  • Installation of a Click-Once add-on is required in order to use Microsoft Edge with Panaya's Intelligent Code Remediation synchronizer

  • If you are using Internet Explorer, no additional browser configuration is required