What are the available Correction categories and types?

Under the corrections tab, activities are classified by category:

Code Correction Custom code fixes required for the system to run correctly in the new version
HANA Migratioײ Activities to be performed as part of you HANA migration project
Authorization Adjustments For all roles that require an adjustment based on new checks in the target version, an Authorization Adjustment activity is generated
Modification Adjustments For changes that are made to SAP standard code, a modification activity is generated
Functional Corrections These are corrections that impact the ordinary behavior of the system
Code Quality Activities Security & Compliance, Performance, Robustness and Maintainability activities
Learn more
Back to Standard Activities Panaya recommends to perform these activities for your custom code cleansing project

Code Corrections

Adjust Cloned Program
A cloned program is a program that was created by copying a standard SAP program. These programs are usually slightly adjusted compared to the original programs, to meet with business requirements.
Panaya identifies cloned programs by performing a code comparison between all custom programs and all standard SAP programs. Matching pairs are classified as clones.
 
Adjust Cloned Program activities are generated when the following apply to cloned programs:
  • The standard SAP program was also changed by SAP in the target version
  • The cloned program is identical to the standard SAP program in both the source and target versions
Using the code comparison provided, you should review the changes made by SAP to the standard program in the target version and decide whether you should implement them in your cloned program. If you decide not to perform the recommended implementation, it does not necessarily mean that it would fail.
 
Fix code due to Deleted SAP Table (Structure) or Field
Panaya identifies SAP standard data dictionary tables, structures and fields that are used in your custom code but have been deleted in the target version. The reference to the deleted table or field from your custom code should be removed or replaced with an existing data dictionary object
 
Fix Code due to Obsolete Functions
Obsolete functions are functions that are not supported by SAP in the target version forward. Panaya identifies calls to these functions within your custom code. The functions may still be available and work properly after the upgrade, but they will not be supported by SAP and therefore it is recommended that the calls to these functions will be replaced.
 
The call to the obsolete functions from your custom code should be replaced using the replacement function Panaya suggests or by finding an up-to-date function that behaves exactly as the original functions did. If you decide not to perform the recommended replacement, it does not necessarily mean that it would fail.
 
Fix Code due to SAP Form API Change
Panaya identifies calls to ABAP forms when the form API undergoes an incompatible change in the target version.
The change can be the result of adding a new parameter or removing an existing parameter, or the form may have been deleted and no longer exists in the target version.

Adjust the call to the ABAP form within your custom code or replace the call to reference another ABAP form in case the original form had been removed.
 
Fix Code due to Syntax Error
Panaya generates syntax error activities based on existing errors on the system. Panaya also generates Unicode-related syntax errors that fail to compile, if Unicode is enabled on your SAP system. For Panaya to generate Unicode-related activities, Unicode should be enabled on your SAP system and UCCHECK should be run.
 
Fix RFC Call in External System
Panaya simulates all Remote Function Calls from outside your SAP system, on the target version. Defective calls are found even if they are not coded in ABAP. Defective calls can result from changes to the RFC API, such as adding a new mandatory parameter or removing an existing parameter. Panaya identifies all RFC calls to your SAP R/3 system based on the usage statistics information extracted from your production system.
 
The call from the external system to your SAP system should be adjusted in the external system to support the new RFC API or by replacing the call if the function was deleted. The focus should be on calls from systems that are not going to be upgraded or from non-SAP systems containing non-ABAP code such as Java. 
 
Fix User Exit Calls to Removed Parameters
Panaya identifies cases where parameters that do not exist in the target version are used in the implementation of the user exit.
The user exit implementation uses removed parameters. The user exit implementation should be fixed by locating alternatives to the removed parameters.
 
Implement Side Effect Note
When upgrading to the target version, many notes are being implemented. Some of these notes cause issues. Side effect notes are the notes that will fix these issues. Panaya provides Side Effect Notes on an on-going basis for you to implement and fix upgrade related issues.
 
Replace Call to Deleted SAP Report
Panaya identifies calls to reports deleted in the target version.
The call to the report from your custom code should be adjusted by replacing the call.
 
Replace Call to Obsolete Transaction
Panaya identifies calls to transactions that became obsolete in the target version or before.
The call to the transaction from your custom code should be adjusted by replacing the call.
 
Replace Call to Removed Transaction
Panaya identifies calls to transactions deleted in the target version.
The call to the transaction from your custom code should be adjusted by replacing the call.
 
Replace Removed User Exit
Panaya identifies cases where an active user exit does not exist in the target version.
The removed user exit should be replaced by an alternative enhancement technique that behaves exactly as the user exit did.
 
Replace Use of Obsolete Table
Obsolete tables are tables that SAP announced they will not be supporting in the target version and forward.

Data in these tables will not be maintained anymore. Panaya identifies calls to those tables and suggest a replacement table.

The call to the obsolete tables from your custom code should be replaced using the replacement table Panaya suggests.

Upgrade 3rd Party Component
Panaya generates an activity for each 3rd party component installed on your SAP system. You should verify that all third-party components are compatible with the target version. If not, these should be upgraded.

To address 3rd party components, check with your software vendor whether there are any updates required or if the existing release is compatible with your target SAP version.
 
Validate Batch Input Program
Batch input is a screen-based technology that mimics an end user interaction with a transaction. Panaya generates activities for all batch inputs that exist in your system and identifies programs using batch inputs and call transactions that may fail after the upgrade.

The batch inputs should be fixed by finding alternative screens or fields for the deleted objects and then rewriting the BDC input sequence or by finding a BAPI that replaces a particular batch input.

Validate Inactive User Exit

Panaya provides you with a list of all inactive user exits. There will be one activity listing all inactive user exits in your system.
Review the list of all inactive user exits to check whether they are relevant to your system.
 
Validate Classic BAdI
Your system has one or more implementations of BAdI. Panaya has found impact within the BAdI flow.
It is advised to validate the expected logic / behavior of the implementations to address the found impact.
 
Validate BAdI
Your system has one or more implementations of BAdI. Panaya has found impact within the BAdI flow.
It is advised to validate the expected logic / behavior of the implementations to address the found impact.
 
Validate Enhancement Point 
Your system has one or more Enhancement Point implementations. Panaya has found impact on the Enhancement Point within the include. It is advised to verify the behavior of the implementations due to the impact found.
 
Validate Enhancement Spot
Your system has one or more Enhancement Spot implementations. Panaya has found impact on the Enhancement Spot. It is advised to verify behavior of the implementations due to the found impact.

HANA Migration

DB Table adjustment for HANA
Panaya generates an activity for each table/program that requires adjustments after HANA migration. The activity lists all related issues for a specific object.
The analysis covers issues such as errors when using native SQL, index issues, ABAP Database Connectivity, settings in DDIC tables and more.

Functional correctness adjustments for HANA
Panaya generates an activity for each table/program that requires adjustments after HANA migration. The activity lists all related issues for a specific object.
The analysis covers issues such as errors when using native SQL, index issues, ABAP Database Connectivity, settings in DDIC tables and more.

Performance Adjustments for HANA
Panaya generates performance checks for database access. The analysis covers issues such as analysis of the WHERE condition for SELECT, unsecure use of FOR ALL ENTRIES, search DB Operations and more. 

Authorization Adjustments

Adjust Basic Role
Basic role is a stand-alone role that is assigned to users and transactions are connected to it.
Basic roles grant access to transactions and activities within transactions.
Panaya finds the additional authorizations required for each basic role.
 
Adjust Master Role
Master roles are templates used for efficiently maintaining multiple roles that grant similar authorizations for different organizational entities. For master roles, Panaya lists all the derived roles that will be adjusted.
 
Assisted Note
Assisted Notes are notes that were implemented prior to the project using the note assistant (transaction SNOTE). 
Once the system is upgraded, these notes need to be handled – by approving or resetting them.
 
Assisted Note with Manually Implemented Objects
Contain modifications that cannot be done automatically by SNOTE and are implemented manually.
 
Modification Adjustment
Modifications are changes to SAP standard code.
Modification activities are generated by Panaya to help adjust the modified program(s) following the upgrade.
 
Unassisted Notes
Notes implemented manually, not by using transaction SNOTE.
 
ā€‹Replace Obsolete Transaction
Panaya identifies usage to transactions that became obsolete in the target version or before.
The use of these transactions should be changed to supported transactions (if the obsolete transaction still exists, customers may keep on using it). Panaya provides replacement suggestions.

Replace Removed Transaction
Panaya identifies the use of transactions deleted in the target version.
The use of these transactions should be changed to supported transactions.