SAP S/4HANA Activities Complexity and Priority

Priority and its corresponding Complexity are determined based on the specific activity type. This article describes, per activity type, the meaning of the different priority and complexity levels. 

See also

Correction Category

Correction Type

Priority

Complexity

Simplification Item Checks

Consistency Checks

Consistency Checks - exemption possible

High
When max issue severity is 'error'

Medium
When max issue severity is 'warning'

Complex
Top ~20% with the highest number of issues

Simple

Bottom ~20% with the lowest number of issues

Medium
Everything else

 

 

Consistency Checks - runtime failures

High

Medium

 

 

Manual Guided Activities

Based on SAP simplification item categorization

High

When SI Category is

Functionality unavailable - equivalent exists.

Functionality unavailable - no equivalent.

Functionality unavailable - equivalent on roadmap.

Functionality not down-ported

Medium

When SI Category is

Change of existing functionality

Low

When SI Category is

Non-strategic-function - equivalent exists

Non-strategic-function - no equivalent yet

Based on SAP simplification item categorization

Complex

When SI Category is

Functionality unavailable - equivalent exists.

Functionality unavailable - no equivalent.

Functionality unavailable - equivalent on roadmap.

Functionality not down-ported

Medium

When SI Category is

Change of existing functionality

Simple

When SI Category is

Non-strategic-function - equivalent exists

Non-strategic-function - no equivalent yet
 

 

Manual Guided Activities with Custom Code Adaptations

High

Complex




 

Roles & Authorizations

Adjust Basic Roles

Based on the number of users

High
more than 100 users

Medium
0-100 users

According to the number of objects found per role

Simple
less than 5 objects

Medium
more than 5 objects

Complex
more than 20 objects

 

 

Adjust Master Roles

Based on the number of users

High
more than 100 users

Medium
0-100 users

According to the number of objects found per role

Simple
less than 5 objects

Medium
more than 5 objects

Complex
more than 20 objects or if there are derived roles with organization levels that need to be adjusted.

 

Modifications

Assisted Notes with Manually Imp. Objects

Assisted Notes

Unassisted Notes

High

According to the number of notes found per transport

Simple
less than 3 objects

Medium
less than 10 objects

Complex
more than or equal to 10 objects

 

 

Modification Adjustments

High

Complex
For programs

Medium
For classes/ABAP Queries/Function modules/Function groups/Screens

 

HANA 2.0 Migration

Native SQL Statements

ADBC Interfaces

DB Operations in Pool/Cluster Tables

Problematic statements for query result without ORDER BY

Illegal function calls

Analysis of WHERE Condition for SELECT

Analysis of WHERE Condition in UPDATE and DELETE

Table Attributes Check

Unsecure use of FOR ALL ENTRIES
 

High

For S/4Convert projects - When max issue severity is 'error'
 

Medium

For S/4Convert projects - When max issue severity is 'warning'

For S/4Accelerate projects - When max issue severity is 'error' or 'warning'
 

Low

When max issue severity is 'info'

Complex

Top ~20% with the highest number of issues

Simple

Bottom ~20% with the lowest number of issues

Medium

Everything else
 

HANA 2.0 Performance Tunings

SELECT Statements That Bypass the Table Buffer

Search problematic SELECT * statements

Search SELECT ... FOR ALL ENTRIES-clauses to be transformed

Search SELECT statements with DELETE statement

Search DB Operations in loops across modularization units

EXIT or no statement in SELECT...ENDSELECT loops

SELECT Statements with Subsequent CHECK

Search DB Operations
 

Medium

When max issue severity is 'error'

Low

When max issue severity is 'warning'

Complex

Top ~20% with highest number of issues

Simple

Bottom ~20% with lowest number of issues

Medium

Everything else

Deleted Transactions

Deleted Transactions - Simplification Item source

High

If include a 'deleted' transaction

Medium

If all transactions are 'obsolete'

Complex

If include a 'deleted' transaction

Medium

If all transactions are 'obsolete'
 

 

Deleted Transactions - Note source

Deleted Transactions - Other source

High

If include a 'deleted' transaction

Medium

If all transactions are 'obsolete'

Complex

If include a 'deleted' transaction

Medium

If all transactions are 'obsolete'

 

Custom Code Preparations

ATC related types

Field Length Extensions

ABAP Dictionary Enhancements

Database Operations

Usage of Simplified Objects

Base Tables of ABAP Dictionary Views

High

When max issue severity is 'error',
and
the issue exists in the target version only (or version data unknown)

 

Medium

When max issue severity is 'warning',
or max issue severity is 'error',
and all 'error' severity issues exist in the source version

 

Low

When max issue severity is 'info'

Complex

Top ~20% with the highest number of issues

Simple

Bottom ~20% with the lowest number of issues

Medium

Everything else


 

 

Adjust Cloned Programs

High

  • If the cloned program is not identical to the original program, and the original (SAP) program is about to change during the upgrade
  • If the cloned program is identical to the original program and the original (SAP) program is about to change during the upgrade

Low

The original (SAP) program is not about to change during the upgrade

Complex
If the cloned program is not identical to the original program and the original (SAP) program is about to change during the upgrade

Simple

If the cloned program is identical to the original program and the original (SAP) program is about to change during the upgrade



 

 

Fix Code due to Obsolete Functions

Medium

Complex
If Panaya is not able to provide a suitable replacement.

Simple
If a replacement suggestion is provided by Panaya


 

 

Validate Batch Input Programs

High
If screens or fields that are in use by the batch input are removed in the upgrade process

When the batch input includes transactions which became obsolete \ deleted in the upgrade


Low
When the analysis determines there is no change to screens and fields used by the batch input

Complex

When the batch input includes transactions that became obsolete \ deleted in the upgrade.

A field or screen is deleted in S/4HANA or if Panaya didn’t identify which of the screens are used in the Batch input

Simple
Everything else



 

 

Fix Code due to SAP Form API Changes

High

Simple

 

Fix Code due to Syntax Errors

High

Medium

 

Fix RFC Call in External Systems

High

Simple

 

Validate Inactive User Exits

Medium

Simple

 

Replace Removed User Exits

High

Complex

 

Fix User Exit Calls with Removed Parameter

High

Complex

 

Replace Use of Obsolete Tables

High

Medium

If a replacement suggestion is provided by Panaya

Complex

If Panaya is not able to provide a suitable replacement
 

 

Validate BAdI

Medium

Medium

 

Validate Classic BAdI

Medium

Medium

 

Validate Enhancement Points

Medium

Medium

 

Validate Enhancement Spots

Medium

Medium

BW Extractor Impacts

BW Extractor Regeneration - validate

Low

Simple

Business Function Preparations

Business Functions are always ON

Medium

Medium

 

Business Functions Deactivation Prerequisites for Conversion / Upgrade

High

Complex

 

Business Functions Always-OFF Prerequisites for Conversion / Upgrade

High

Complex

Add-Ons Compatibility Checks

Validate Add-Ons

High

Complex

 

Incompatible Add-ons

High

Complex

 

BW Extractor - Future deprecation

Medium

Medium

 

BW Extractor with Restrictions

Medium

Medium

 

BW Extractor Deleted - Replacement Planned

High

Complex

 

BW Extractor Obsolete

High

Complex

 

BW Extractor Deleted - no Replacement

High

Complex

 

BW Extractor Deleted - Replacement Exists

High

Complex

Accounting Data Conversion

Accounting - Configuration data consistency checks

High

 Medium

 

Accounting - Transactions data consistency checks

High

Medium