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. Code Correction Priority is based on the likelihood of system failure.
Activity Type | Priority Level | Complexity Level |
3rd Party Components | High | Complex |
Function API | High | Simple |
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 |
Obsolete Functions | Medium | Complex
If Panaya is not able to provide a suitable replacement.
Simple
If a replacement suggestion is provided by Panaya |
Batch Input | High
If screens or fields that are in use by the batch input are removed in the upgrade process and/or when the batch input includes transactions that became obsolete in the upgrade
Low
When the analysis determines the called transaction is impacted by delivered notes and/or a field name/type was changed in the batch input.
| Complex
A field or screen is deleted in ECC6, or if Panaya didn’t identify which of the screens are used in the Batch input
Simple
Everything else |
Syntax Error | High
HANA Migration Activities Complexity and Priority
| Medium |
Deleted SAP Table (Structure) or Field | High | Complex
If there is a select statement from that table/field
Simple
The field is used to describe another field (“Like”) without a selection |
Fix RFC call in external system | High | Simple |
Validate Inactive User Exit | Medium | Simple |
Replace Removed User Exit | High | Complex |
Fix User Exit Calls to Removed Parameters | High | Complex |
Replace Use of Obsolete Table | High | Medium - If Panaya provides a replacement suggestion Complex - If Panaya is not able to provide a suitable replacement |
Replace call to deleted SAP report | High | Complex |
Replace call to removed transaction | High | Complex |
Replace call to obsolete transaction | Medium
If the change occurred after the current version Low
If the transaction was already obsolete in the previous or current version | Complex |
Replace removed transaction | High | Complex |
Replace obsolete transaction | Medium
If the change occurred at the current version Low
If the transaction was already obsolete in the previous version | Complex |
Form API | High | Simple |
Implement Side Effect Note (SPS/EHP/HR only) | High
If the SAP note has priority of ‘HotNews’ or ‘high’
Medium
If the SAP note has priority of ‘medium’, ‘low’ or ‘Recommendations/additional info’
| Medium |
Validate Classic BAdI | Medium | High
2 or more implementations are required
Medium
1 implementation required |
Validate BAdI | Medium | High
2 or more implementations are required
Medium
1 implementation required |
Validate Enhancement Point | Medium | High
2 or more implementations are required
Medium
1 implementation required |
Validate Enhancement Point | Medium | High
2 or more implementations are required
Medium
1 implementation required |