- 3 Minutes to read
- Print
- DarkLight
- PDF
SAP S/4HANA Corrections Complexity and Priority
- 3 Minutes to read
- Print
- DarkLight
- PDF
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.
Correction Category | Correction Type | Priority | Complexity |
Simplification Item Checks | Consistency Checks Consistency Checks - exemption possible | High Medium | Complex Simple Bottom ~20% with the lowest number of issues Medium |
| 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 Medium | According to the number of objects found per role Simple Medium Complex |
Adjust Master Roles | Based on the number of users High Medium | According to the number of objects found per role Simple Medium Complex | |
Modifications | Assisted Notes with Manually Imp. Objects Assisted Notes Unassisted Notes | High | According to the number of notes found per transport Simple Medium Complex |
Modification Adjustments | High | Complex Medium | |
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 | for S/4Convert Projects - High When the maximum issue severity is 'error' Medium When the maximum issue severity is 'warning' Low When the maximum issue severity is 'info' for S/4Accelerate Projects - High At least one issue is with severity = error and 'target only' = Yes / Blank Medium When the maximum issue severity is 'warning' or Max issue severity is 'error,' but all 'error' severity issues are with 'target only' = No. Low When the maximum 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 |
Implement Side Effect Note | High Medium | Medium | |
Related Notes | Correction of legal function Note | High For notes of high priority Medium For notes of medium priority Low For notes of low priority | Medium Low Legal Change Notes and Correction of legal function Notes that are associated with a support pack. |
Problem Note How to Note | Medium For notes of normal priority Low If the note exists in the source version | High |