Property Tree Update data with green active check when saving Specifcation

[rohan_somji]

Dear SAP Experts,

Recently we upgraded our SAP system ECC 6.0 EHP8/SPS02 to "SPS18".

After the upgrade we noticed that when we create a new value instance with some data and click save the green active check doesn't appear. Instead we have to now and click refresh button manually. As soon as we click the refresh button we end up right at the top of the property tree. But now the green check is active.

We then understood SAP has a environment parameter 'SP_WB_DATA_REFRESH_AT_SAVE'. If this parameter is blank then the behaviour is as I mentioned above.

If we add value as 'X' in the environment Parameter then green active check appears immediately when we create a new value instance with some data and click save but at the same time we end up going to the top of the property tree.

As per SAP we will improve the performance of our system if we do not carry out the update in the env. parameter.

But then again we have to look at this from our end user perspective. Since we were on SP02 the users were used to see the green check and staying on the same property tree after save. Now after upgrade we initially kept the parameter as Blank and they noticed the green check does not appear. So then we added value as 'X' in the Env. Parameter. Now when they click save the property tree is auto refreshed and it goes right to the top. This becomes a little irritating specially when we have multiple folders and a lot of VATs in some folder and now you click save and you end up right at the top of the property tree. If you want to check the VAT again you then have to scroll all the way down to find the VAT again.

Can you please tell me if your client / company also had a similar experience when you upgraded the system? If yes then how did you deal with this.

Regards,

Rohan

[christoph_bergemann · Accepted solution]

Dear Rohan

this is not the only surprise if you do update/upgrade. I believe we have a different SP (lower) and therefore: now i know what will come up. In out SP i just reallized that the specification header get "updates" (whole specification is updated) do to a OSS Note released 2021... To explain this (and your story) is no easy.

In our last upgrade we have had "a lot of fun" with such not very well documented changes in the software (RFC Connection was not working as assumed).

So sorry: even if you implement "only" a SP.. there are surprises possible. If you "upgrade": there is a "guarantee" for some "surprise" according to last year experienceses in doing so.

Even if you do good testing... sometimes only after go live you will detect such changes. Ten yeas (or more) ago: there was "only" a SP change. ANYBODY tested really intensive. The issue was the detected "after go live" (change of an "authorization check". I am sorry to say: Even if you do only an "SP" change.. ther can be a surprise.

C.B.

[rohan_somji · Accepted solution]

Thanks for the response Christoph. Yes we also had few suprises during our testing and even after our golive. But the business wanted to understand how did you deal with this change. After the SP upgrade, was this a gradual acceptance by users for your company? In my case the users were particularly not fond of this change. So they asked me to check how did other companies adapted to this? Was there any specific activity done by the IT support team like training, documentation etc? If you can let me know this would help. I know there is nothing we can do at this point and my users will eventually adapt.

Regards,

Rohan