How to extract and upload your custom code?

Panaya's solution requires an ABAP program installation on your SAP systems. This program performs the following high-level activities:
  • Extraction of custom developed ABAP code.
  • Identification and extraction of used transactions - finding out which transactions are used in your production system.
  • Extraction of defined systems in Solution Manager.
Before starting the installation process, make sure you have the following privileges:
  1. Access to your SAP Development, QA and Production system
  2. User with development permissions to:
    a. Display, create and execute ABAP programs
    b. Running jobs
    We recommend selecting a user with SAP_ALL or a similar strong BASIS user authorizations
  3. A Panaya username and password
  4. Internet Explorer browser versions 9 and above, Google Chrome 15 and above, or Firefox 16 and above.
  5. If migrating to HANA, please follow these instructions before you continue with this process

Execute the following steps to complete the process:

  1. Click on the Settings button
  2. In the Settings panel select Code Box
  3. Panaya analysis is based on custom objects extracted from your system. In most cases, there are differences between objects in the development system and the production system. Because we are extracting the custom developed objects only from one instance, please choose the system that best represents your needs for analysis.

    Should you require assistance defining from which system in your landscape you should extract the custom code, our support team will be happy to answer any questions you may have. Please contact our support team at:
  4. Before you continue, check that the relevant System appears on the top left corner of the screen

  5. Select your current ERP version
  6. Download the ABAP code

    If you are having trouble downloading the code, use the View option to copy and paste the code to your system.
    The extracted code  is dynamically updated for improvements and according to your system needs and project's progress. To avoid delays and for better results you are required to download a new version of the extractor code before every new extraction.

Step B - Create an Executable Program

This step explains how to install Panaya’s ABAP code extraction program on your SAP system. The ABAP extraction program reads the repository objects locally and extracts customer developed objects from the system it runs on. The program also uses RFC connections to extract data from the production and other systems.
  1. Create an executable program named ZPANAYA_EXTRACT_PROG_LIB and import or paste the ABAP code.
  2. Save the program in a change request, should you need to execute it on other systems like QA or Production.

To learn how to install an ABAP program, click here

Step C - Define User Authorizations for RFC connections

Before you continue to the next step, please identify a user for the RFC. 
It is critical that the RFC users have the required authorizations as described here.

Step D - Defining RFC Connections

In this step you will define 3 RFC connections for Production, Solution Manager and BW systems.

A Production RFC connection is required in order to extract usage information.
Use a production RFC connection when running Panaya’s code extraction program on any system instance other than production (such as sandbox, development, QA etc.).
By default, if no value is providued for the production RFC destination, the usage will be retrieved from the system where the extraction program is executed
A Solution Manager RFC connection is used to extract a list of additional external systems that may be impacted as a result of the changing ERP landscape.
A BW RFC is an optional connection that can be used to extract data from the BW system and used by Panaya to show the impact on the BW system as a result of the change to the ERP system.
When defining the RFC to BW, you should select the BW production system that is connected to the ERP Production system.
If the data sources in BW do not correlate with the production system, the following warning will appear: “No BW DataSources available with source system: <system name> with RFC to BW system: PANAYA_BW"
  1. Start transaction SM59 (configuration of RFC connection)
  2. In the new window fill the following values according to the RFC connection target system
  3. Press the create button in the upper tool bar to create RFC connections with the following values    
    Value/Field RFC Destination Connection Type Description 1
    Production  PANAYA_PRD 3 (ABAP connection) PANAYA_PRD
    Solution Manager  PANAYA_SM 3 (ABAP connection) PANAYA_SM
    PANAYA_BW 3 (ABAP connection) PANAYA_BW

    In the Technical Settings tab:
    For Target Host -  type your target system host name or number 
    For System Number - type your target system number

    In the Logon & Security tab:
    For Language - English (EN)
    For Client Type - your target system client number
    For User & Password - your target system username and password

    Click here for Required User Authorizations

  4. Click the Connection Test button to validate your connection

  5. Click the Remote Logon button and validate your user

  6. Repeat steps 3-7 for all each RFC connection defined in step 3.

Did you know?
You can manually configure the extraction program parameters to define what data and usage should be extracted by Panaya
Click here to learn more

Step E - Execute the Extraction Program

  1. Login to the relevant SAP system
  2. Start transaction SE38
  3. Type the program name ZPANAYA_EXTRACT_PROG_LIB and press the execute button (F8)
  4. The system will automatically perform a version validation check. If the automatic validation cannot be performed, a validate extraction button will appear. In this case, run the validation to avoid extraction failure.
  5. Under Execution mode, select Background and enter the Background Directory path (e.g. \tmp) on the SAP application server.

  6. For Target system for Roles and Usage extraction, under RFC destination, type - PANAYA_PRD
  7. If Systems' Roles in the Landscape section is available, follow the steps as described here.
  8. For Solution Manager target system for Systems extraction, under RFC destination, type - PANAYA_SM
    (not applicable for SCM systems)
  9. For BW target system for BW extraction, under RFC destination, type - PANAYA_BW
  10. Do not check the Usage Only checkbox. Checking this box will result in an extraction with usage information only.
    To learn how to extract usage statistics only, click here
  11. If migrating to HANA, under HANA SAP Code Inspector execution mode select between options A, B or C as described below.
    Note that Option A and B are highly recommended. 

    Option A (Recommended)
    Select Choose from previously executed list if you want to use existing data from previous SAP code inspector runs. You can perform those runs by following the instructions in this article. Then fill in the values for the FUNCTIONAL_DB, FUNCTIONAL_DB_ADDITION and PERFORMANCE_DB field from the previously executed Code Inspector.

    Option B 
    Select Choose from excel files if you wish to run the Panaya Code Extractor before migrating your system to HANA and still receive a HANA Impact Analysis. To learn more about how to export these XLS files, click here.

    Click Upload

    When selecting options A or B, verify that you are using the most recent output of the HANA extraction. 
    Using older versions for a current custom code extraction may cause HANA analysis discrepancies. 
    Run HANA SAP Code Inspector in offline mode
    Export HANA Code Inspector using Excel

    Option C 
    Select Execute  to run the SAP Code Inspector with HANA relevant variants during extractor execution

    - If you are having trouble extracting your custom code for HANA migration, click here
    - If you receive Warnings or Errors in the Code Inspector Results, click here

  12. From the Program drop down menu, select Execute in Background
    - In case the Execute in Background option is disabled, double click on the Background Directory field
  13. Select to create immediate job (you can review the job processed in SM37)
  14. Once completed, please check to see that an XML file was created in the defined path.
    If you cannot locate the file, click here for assistance.
The program normally runs between 45 minutes to two hours, depending on the extent of custom objects developed in your system and usage information, although in some cases may take longer.

Step F - Upload Your Custom Code

  1. Locate the extraction file. Click here to learn how
  2. Before you upload your code to Panaya's Code Box, you will need to compress the XML file into Zip archive using a standard archiving software like Gzip. You can download Gzip here. RAR file type is not supported.
  3. Select the relevant System and ERP version
  4. Drop the ZIP file back to Panaya Code Box, or click to browse and select it.
  5. 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)
  6. Once uploaded, you should receive a confirmation email regarding your custom code upload.
  7. User 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
All information uploaded to Panaya via the website is encrypted using SSL technology Read more.