31. How to tackle SAP_ABA is in undefined state error during SUM Run ?

Most of the basis peoples who have played with SUM run will definitely experienced this error once.

Subjected error usually occurs if we didn't reset previous SUM Run properly.

Even I have tried SUM run for practice - deleted directory directly without proper reset and faced subjected error while trying to run SUM once again.

Let's have a quick tips.

While we perform SUM Run, UVERS table status will change FROM "+" - "can be upgraded" status TO "U" - "Upgrade running" status.

✨"+" status usually denotes that Previous upgraded completed successfully and system can be upgraded newly further.

Assume that we decided to Stop SUM update. Then, status will be set back to "+" - if we performed reset properly. If not, it stays with "U" status triggering this "Undefined state" error.

Before SUM Run:

(Sample snap)

During SUM Run:

(Sample snap)

Usual resolution would be below ones.

Step 1) If SUM directory backup taken before deletion, Restore SUM directory using backup. Do an proper reset. SUM reset can be done till it reaches downtime phase.

1.1 -  If you already reached Preprocessing/Execution (before SUM Downtime) phase in previous SUM run, then it's necessary to restore SUM directory and do SUM reset which will deal and delete shadow tables, others whichever created during SUM run. If you don't have backup, Step 2&3 might help but there would be some consequences since SUM was not properly reset despite it's reached Preprocessing/Execution phase (before downtime).

Step 2&3 - Mostly valid for Preparation RoadMap Cases - Extraction, Configuration, Checks.

Step 2) If there is no backup,  Reset the table buffer. It will set back to "+" state.

AL12 - Edit - Reset buffer - Table buffer - enter UVERS - click on Invalidate.

Step 3) If table buffer reset doesn't help, just restart SUM instance. It will clear table buffer caches.

Above steps usually resolve in 99% cases.

1% case, It won't work. I have tried above steps multiple times in one of my scenario but it didn't work. (Not sure what happened)

Since I'm confident that I haven't changed anything w.r.t my system operations/updates, I have manually changed PUTSTATUS to "+". I can able to run SUM newly without any issues.

Caution - You can do it on own risk

In general, Before starting SUM run,

Crosscheck whether SPAM/SAINT status is in green status. You can only do SUM operations if SPAM/SAINT is in GREEN 

Crosscheck whether PUTSTATUS is in "+" or not.

Note 1790486 - SAP_ABA is in an undefined state that is not safe to be upgraded vers36

Additional comments on Step 1.1:

SAP set this as mandatory condition in Note 1790486 till vers34. However, Removed in vers35 and made step 2 & 3 as common resolution.

Vers 34:

Vers 36:

✨However, As I stated in Step 1.1, It's best practice and necessary to restore SUM directory and perform SUM reset if previous SUM run already reached Preprocessing or Execution (before downtime phase)

Ever uploaded older package for SPAM/SAINT update and wondered why you have uploaded?

Refer below tick.

18. Doing SPAM/SAINT Import ? Seeking Older version files ?

Thanks for visiting !!!