Tests and Recommended Unit Tests Priority & Complexity

Depending on the type of project, the activity  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.

 

Activity Type

Priority Level

Complexity Level
Recommended Unit Test Activities – SPS/EHP Upgrade
(Generated by Panaya)

High
If the transaction has associated code corrections (not including a problem in user exits)


Medium
Transaction is impacted directly by SAP notes OR calls an active user exit
AND
No
associated code correction

Low
No associated code correction found AND the transaction is impacted indirectly by SAP notes
OR 
Only an active User Exit code correction found AND the User Exit is called by a transaction that is not impacted by SAP delivered notes.

Note
If a Unit Test is only related to Authorization Adjustments, the priority will be set based on the highest related Authorization Adjustment priority


 

Complex
If there are at least two code-correction predecessors

Medium
If there is exactly one code correction predecessor

Simple
No code correction predecessors
 
Recommended Unit Test Activities – BW, SPS/EHP Upgrade (Generated by Panaya)

High
If the transaction has code corrections

Medium
No code correction problems and the transaction is impacted directly by SAP notes

 

 

 

Complex
More than 1 Code Correction

Simple
No code corrections, no notes, no Active User Exits

Medium
All the rest
 

Recommended Unit Tests Activities - 
S/4HANA Conversion Project (Generated by Panaya)

High

With at least one associated correction in high priority
(Related Modifications are not considered)

Medium

  • With at least one associated correction in low or medium priority. (Related Modifications are not considered)
  • No associated corrections, but the Transaction has active users exits

Low
Everything else

 

 

 
Recommended Progression Tests Activities - 
S/4HANA Conversion Project (Generated by Panaya)

For Transactions - 
 

  • High
    With at least one associated correction in high priority
    (Related Modifications are not considered)
  • Medium
    • With at least one associated correction in low or medium priority. (Related Modifications are not considered)
    • No associated corrections, but the Transaction has active users exits
  • Low
    Everything else

 

For Fiori
According to replaced transaction usage and impact level -

Impact Level / Usage Frequently Normally Rarely Unused Unknown
Deleted High High Medium - -
Obsolete High Medium Low - -
Enhanced by Fiori Medium Low Low - -

 

 

 
Test Activities in an EHP/SPS and S/4Convert projects (User Generated)
If Transactions are identified by Panaya and an associated Unit Test was generated with steps using these transactions, the Test priority is determined according to the highest priority transaction correction

If the transaction is not specified -
  • Low - For all other Tests

 

 
Test Activities in a Testing project (User Generated)

High