What are the available Correction categories and types for SAP S/4HANA?

For your S/4HANA Conversion or Upgrade Projects, you will find the below available Corrections, automatically generated for you by Panaya.

See also

Simplification Item Checks Corrections are defined per each SAP Simplification Item relevant to your system. SAP Simplification Items identifies data inconsistencies or missing mandatory preparation activities which could cause the system conversion to fail.
Deleted Transactions* Corrections are defined per deleted transactions that are not available anymore in S/4HANA and transactions which became obsolete in S/4HANA
* Conversion Projects Only
Custom Code Preparations Corrections related to customization of many forms and types which were done to the SAP code
HANA 2.0 Migration Corrections required in order to migrate from any database to HANA 2.0 database locating ABAP code that potentially relies on specific properties of the predecessor database and that might need to be modified
HANA 2.0 Performance Tunings Recommended corrections for optimizing the HANA 2.0 performance
Roles & Authorizations An Authorization Adjustment correction is generated for all roles that require an adjustment based on new checks in the target version    
Modifications A post-conversion modification correction is generated for changes that are made to SAP standard code
Business Function Preparations Corrections for Business Functions activation state changes due to S/4HANA system conversion
Add-Ons Compatibility Checks Corrections for Add-ons which exist in the current system and are not compatible with the S/4HANA target version.    
BW Extractor Impacts* Corrections are being created for BW Extractors in use. Each correction includes the required action due to S/4HANA data source modifications.

Note
An RFC to a BW system is not required for BW Extractor Impact

* Conversion Projects Only

Accounting Data Conversion*

Accounting data conversion corrections provide guidance on programs that should be run before the conversion, in order to detect inconsistent financial data.

* Conversion Projects Only

 


 

 

Simplification Item Checks

Consistency Checks
The S/4HANA system conversion relies on consistent data in the system in order for the conversion to happen automatically. Consistency Check corrections are SAP Simplification Items which has data consistency issues that needs to be fixed grouped by Sub-ID.

Consistency Checks - exemption possible
S/4HANA Simplification items corrections which can be exempted. An Exempted simplification item is a relevant to your system simplification item which will not fail the SUM conversion process and can be handled after the SUM conversion.

Consistency Checks - runtime failures
Critical error (error code 12) reported while running the Simplifications Items Consistency Check.
This runtime error requires fixing, in order to run consistency checks successfully.

Manual Guided Activities
Simplification Item corrections which are highly application specific and require manual activity. in order to solve the manual guided activity correction, you should read the relevant business impact note of the corresponding Simplification Item and act accordingly.    

Manual Guided Activities with Custom Code Adaptations    
Simplification Item corrections which require manual activity and custom code corrections correlation was found. By looking at the related corrections you will find all the custom code corrections related to this simplification item.    

 


 

 

Deleted Transactions    

Deleted Transactions - Simplification Item source
Deleted and obsolete transactions corrections which Panaya found a correlation to a simplification item. Each correction is grouped by all deleted transactions related to a specific simplification item.    

Deleted Transactions - Note source
Deleted and obsolete transactions corrections which Panaya found a correlation to a generic SAP note which is not related to a simplification item. Each correction is grouped by all deleted transactions related to a specific application component.

Deleted Transactions - Other source
Deleted and obsolete transactions corrections which are Panaya specific and cannot be correlated to any note or simplification item. Each correction is grouped by all deleted transactions related to a specific application component.

 


 

 

Custom Code Preparations    

Adjust Cloned Programs    
Panaya compares your custom code with the SAP vanilla code. The identification of a cloned program is done based on the comparison of the relevant lines of code. A minimum similarity of 20% is required in order to classify the program as a cloned program. A correction is defined per cloned program.

Fix Code due to Obsolete Functions    
Panaya identifies calls to functions which are obsolete in the target SAP version 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.

Validate Batch Input Programs    
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.

Fix Code due to SAP Form API Changes    
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 S/4HANA 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 Errors
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 Systems    
Panaya simulates all Remote Function Calls from outside your SAP system, on the target S/4HANA 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 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. 

Validate Inactive User Exits    
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.

Replace Removed User Exits    
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.

Fix User Exit Calls with Removed Parameter    
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 should be fixed by locating alternatives to the removed parameters.

Replace Use of Obsolete Tables    
Obsolete tables are tables that SAP announced they will not be supporting in the target version.
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.

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 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 Enhancement Points    
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 Spots    
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.    

ATC related types
The following correction types are corrections which are derived from the SAP ABAP Test Cockpit (ATC) static code checks data which is uploaded to the Panaya system. The custom code fixes are grouped into corrections by program name and correction type.

Field Length Extensions
Correction is being made for changes in field length. E.g. MATNR domain is now 40 characters long instead of 18 characters.

ABAP Dictionary Enhancements
Correction is being made for creation of append structures to tables or standard views which are “simplified” in S/4HANA.

Database Operations
Correction is being made for SQL statements  (like INSERT or MODIFY) which are executed on old tables which S/4HANA replaced by views

Usage of Simplified Objects
Correction is being made for usage of objects such as dictionary or repository which are no longer available on S/4HANA.

Base Tables of ABAP Dictionary Views
Correction is being made for usage of simplified standard tables within custom views.

 


 

 

HANA 2.0 Migration

Native SQL Statements
For native SQL, you must check whether the SQL code can run on SAP HANA and whether it needs to be adapted.

ADBC Interfaces
ABAP Database Connectivity (ADBC) is an API for the Native SQL interface that is based on ABAP Objects. You should treat this correction same as the Native SQL correction,

DB Operations in Pool/Cluster Tables
Check the location of accesses to technical pools/clusters of a pooled/cluster table. As part of an SAP HANA migration, most pooled and cluster tables are converted to transparent tables of the same name.  

Problematic statements for query result without ORDER BY
An "order by" clause must be specified for select statements explicitly for all tables if you want a sort sequence

Illegal function calls
Get rid of analysis of technical DB index information using function modules 'DB_EXISTS_INDEX‘, 'DD_INDEX_NAME’ since most indices are no longer needed and therefore not created in HANA. therefore these two functions are unreliable and should not be used. Most indices are no longer needed and therefore not created in HANA.

Analysis of WHERE Condition for SELECT
This correction is created to examine the WHERE condition of the SELECT statement for accesses to non-buffered tables according to the below criteria-

SELECT statement does not contain any WHERE conditions
WHERE condition does not contain any fields of a table index
WHERE condition does not contain the first field of a table index
Despite the addition CLIENT SPECIFIED, no client field in the WHERE condition
Table does not exist or does not have a nametab entry

Analysis of WHERE Condition in UPDATE and DELETE
This correction is created to examine WHERE condition of the UPDATE and DELETE statements according to the below criteria -

UPDATE / DELETE statement without WHERE condition
WHERE condition does not contain any fields of a table index
WHERE condition does not contain the first field of a table index Despite the addition CLIENT SPECIFIED, no client field in the WHERE condition

Table Attributes Check
Examines the technical settings (transport attributes, buffering) and the secondary index of database tables.

Unsecure use of FOR ALL ENTRIES
Checking SQL operations with the addition FOR ALL ENTRIES IN <itab>, whereby in the code itself it is not ensured that the internal table < itab> is always filled.

 


 

 

HANA 2.0 Performance Tunings    

SELECT Statements That Bypass the Table Buffer
When reading data, SAP table buffering (the buffering of database tables on the application server) has a major performance advantage over accessing the database. Therefore, you should not bypass the buffer for buffered tables.

Search problematic SELECT * statements
This correction searches for SELECT * FROM dbtab statements where less than a specified percentage of the fields are effectively used. The default value for the percentage is 20 percent. If less than 20 percent of the fields are used it is more adequate to select only the used fields.

Search SELECT ... FOR ALL ENTRIES-clauses to be transformed
This correction searches for SELECT ... FOR ALL ENTRIES where the input for all entries table is the result of another SELECT statement. In this case the two statements can be joined into one statement with an improved performance.

Search SELECT statements with DELETE statement
Corrections for SELECT .. INTO TABLE tab statements which are followed by a DELETE statement for the result table tab

Search DB Operations in loops across modularization units
This correction searches for database operations that are nested inside any kind of loop (e.g. LOOP-loop, DO-loop, ...). If in the loop there is a call to a modularization unit (PERFORM, CALL FUNCTION, CALL METHOD), then this call is tracked and it will be analyzed, whether there is a database operation in the called unit. This way, several levels of the call-stack are analyzed.

EXIT or no statement in SELECT...ENDSELECT loops
Correction to check whether there is an EXIT statement or RETURN statement in a SELECT...ENDSELECT loop or whether a SELECT...ENDSELECT loop contains any statements at all.

SELECT Statements with Subsequent CHECK
Corrections for CHECK statements that follow directly after the SELECT statement. All selection conditions must be specified in the WHERE clause. You should not select data and then discard it using CHECK.

Search DB Operations
This correction searches for database statements in the ABAP code

 


 

 

Roles & Authorizations    

Adjust Basic Roles    
Basic role is a stand-alone role that is assigned to users and transactions which 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 Roles    
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.  

 


 

 

Modifications     

Assisted Notes with Manually Imp. Objects
Contain modifications that cannot be done automatically by SNOTE and are implemented manually.

Assisted Notes
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.

Unassisted Notes
Notes implemented manually, not by using transaction SNOTE.

Modification Adjustments    
Modification adjustment activities are generated by Panaya to help adjust the modified program(s) following the upgrade.    

 


 

 

Business Function Preparations    

Business Functions are always ON    
Business Functions which are turned OFF in your current system that are turned ON by SAP automatically during the conversion process. You should check what is the influence on your SAP operations due to the new business function activation    

Business Functions Deactivation Prerequisites for Conversion    
Business Functions that are turned ON in your current system and you must turn OFF prior to the conversion to avoid errors which will fail the conversion.     

Business Functions Always-OFF Prerequisites for Conversion
Business Functions that are turned ON in current system and the user must deactivate to avoid errors in the conversion    

 


 

 

Add-Ons Compatibility Checks  

Validate Add-Ons    
Add-ons developed by either SAP or SAP partners which are supported by the target SAP version but require validation since the add-on version on the current system is not supported by the target SAP version. You should update your add-on to the add-on version which is supported by the SAP target version.  

Incompatible Add-ons    
Add-ons developed by either SAP or SAP partners which are NOT supported by the target SAP version. You should either contact SAP support or the partner support, or find an alternative solution for this add-on.    

 


 

 

BW Extractor Impacts    

BW Extractor Regeneration - validate    
The Data Source is working. Due to data model changes, it is recommended to check the upward data flow.    

BW Extractor - Future deprecation    
The Data Source is working but planned to be deprecated. Follow the relevant SAP note in order to avoid future BW extractor problems.    

BW Extractor with Restrictions    
The Data Source is available at S/4HANA but works with restrictions; e.g. not all fields are available. Relevant SAP Note is provided.    

BW Extractor Deleted - Replacement Planned    
The Data Source is not working at S/4HANA. Equivalent Data Source is available in the S/4HANA future release roadmap    

BW Extractor Obsolete    
Legacy obsolete Data Sources which are not available at S/4HANA.    

BW Extractor Deleted - no Replacement    
The Data Source is not working at S/4HANA. No alternative exists.    

BW Extractor Deleted - Replacement Exists    
The Data Source is not working at S/4HANA. There is an alternative which should be used instead.

Validate BW Embedded Extractors
 

 


 

 

Accounting Data Conversion

Accounting - Configuration data consistency checks
Configuration data that should be verified before the installation    

Accounting - Transactions data consistency checks
Transactions data that should be verified before the installation    

 


 

 

See also