SAP Personas 3.0 SP03 Combobox Issue after Kernal and SAP BASIS Upgrade

[srini_brahmasani]

Hello Gurus,

We are working on SAP Screen Personas 3.0 SP03, We have an issue with custom combo box and some Script errors in IW31 Flavor after upgrading our SAP BASIS version and Kernel.

Issue 1:

We have a combo box for plant field with two possible inputs (1000 and 2000), When we select any of these values in dropdown we are able to see the value in drop down selection, but the key and text value is not flowing to the properties( Key and Text) properties of Combo box.

In below screen shot we are able to see one of the possible values have been selected

.

In below screen I'm inspecting the value in drop down list and Key field in inspector section is empty, even we have selected a value in drop down list.

Issue2:

We are passing Plant number selected in combo box and order type to IW31 initial screen through the script and the same script attached to on Enter event.

But system is not at all triggering this script after upgrade, if we check the syntax in script editor we are getting a script is valid message.

But we are getting below errors in the console section of debugger.

Note: Before upgrading our Kernel version it was working fine.

Upgraded version:

1).We have Upgraded Kernel Release version 745 Patch level 316 to Version 753 Patch level 213.

2). Also we upgraded SAP BASIS Release version 740 Patch level 0013 to Version 750 Patch level 0011.

Could you please help me on this issues.

Earliest reply on this will be appreciated.

Thank you

[srini_brahmasani]

Hi Tamas

We implemented the notes showing in error status and yellow status(implemented latest version).

Now we are not facing '+' symbol issue any more.

We are good to go live now.

Thank you so much for you great help in resolving these upgrade issues.

BR

Srinivas Brahmasani

[cris_hansen]

Hi Srinivas,

You need to upgrade your Personas to, at very least, SP05.
SP03 and SP04 are already out of support.

I recommend going to SP07, as it includes new features and bug fixes.

Taking that you upgraded your SAP_BASIS and kernel, you could have included the Personas SP in the queue.

Kind regards,
Cris

[srini_brahmasani]

Hi Cris,

Thank you so much for your quick reply.

We will upgrade and let you know.

Thank you once again

BR

Srinivas

[srini_brahmasani]

Hi Cris,

Hope you are doing good!

We planned to upgrade our personas to SP06.

I have one question, as per the SAP below are the compatible kernel versions for Personas 3.0 SP06.

SAP BASIS : 750

Kernel Release: 745 and 749

Now we are into SAP BASIS 750 and Kernel version is 753.

Still will it work for Kernel version 753 as well or we need to down grade own kernel?

Thank you

Regards

Srinivas Brahmasani

[tamas_hoznek]

If you check the SP06 master note 2560666, it mentions that this SP is supported with kernel 753. The minimum patch level is 27.

However, as Cris suggested, it is much wiser at this time to go to SP07. SP06 has a lot more notes to implement, and SP07 offers additional features that SP06 doesn't have.

[srini_brahmasani]

Hi Tamas Hoznek,

Good Morning!

Thank you for helping me on these issues!

As suggested, we upgraded our Screen personas to SP07, The flavors created in older SP(03) are converted to SP07. Now how to transport them.

We have two clients in Development system 100 for development and 200 for testing.

So we converted flavors in client 100 and added them to a transport. Then we imported the objects to 200 client using SCC1 transaction. We are able to see the version of flavors as 307 in 200 client, But the flavor is not working properly.

Could you please suggest on this.

Thank you

BR

Srinivas

[tamas_hoznek]

What does it mean that "the flavor is not working properly"? What's happening?

[srini_brahmasani]

Hi Tamas,

Thank you for your quick reply on this!

We designed a flavor for IW31 Transaction with two screens.

issue-screen.png

Please see the screen attached above.

The Buttons and input fields marked in blue color circle's are from second page. But these are showing in first page and second page as well.

Initially in client 100 also we have same issue, after updated our flavor from 303 to 307, this issue have been resolved.

We added the updated flavor in client 100 to a transport and imported it to client 200 using SCC1 transaction.

I checked flavor version in 200 client after transport import, It is showing flavor version as 307 but the old issue what we have faced before flavor update in client 100 still persist in client 200.

I have one question here, Do we need to update flavors from old version(303) to new version(307) in each system manually Or we can transport from Development systems to QA and PRD?

Thank you

BR

Srinivas

[tamas_hoznek]

If the system is fully up-to-date with all notes for SP07 implemented (Check Notes status is all green), then there is no reason for controls to show on the first screen, which were added to the second screen. I have not heard of such a problem yet.

Updating flavors to SP07 should be performed in the system and client where you are maintaining these flavors (DEV), and then you need to transport the upgraded flavors to QA and PRD.

[srini_brahmasani]

Hi Tamas,

Thank you for guiding us on these issues!

We did health check in QA system. Some notes are not showing green status.

health-check.png

We updated our flavor to 307 manually in QA system, the controls showing in first page issue has gone now. But we are facing two more issues.

1) We did some script changes in DEV system after updated our old flavor to 307 and moved those changes to QA system..

The script changes are moved successfully into QA, But the flavor is still triggering old version of script.

When we see the script in Script editor we are able to see our changes. When we saw flavor execution in debugging, it is still triggering old version of script.

2) We have a long text field in IW31 flavor, when we are saving long text it is adding '+' symbol's in place of spaces.

Example: "This is sample long text"

"This+is+sample+long+text"

Even in Windows GUI also it is showing with '+' symbols, if we save the long text through flavors.

Could you please help us on these two issues.

Thank you

BR

Srinivas

[tamas_hoznek]

For the problem after the transport, clear the flavor cache in the target system. Transaction /PERSONAS/HEALTH -> Health Check -> Cleanup -> Clear Flavor Cache.

The addition of the + signs is odd... is this only happening when a Personas flavor is active? How about when you use the Original Screen?

Also, does this happen perhaps already in webgui? Try using the webgui service and add the following at the end of the URL: &sap-personas-runmode=0

[srini_brahmasani]

Hi Tamas,

Thank you for your quick help!

First issue resolved after clearing flavor cache.

Coming to second (Long text) issue:

Windows GUI: No issue with long text in Windows GUI.

Webgui without Personas runmode parameter: We have long text issue.(Adding '+' symbols in place of spaces)

Webgui with Personas runmode parameter: We have no issue in this case.

Could you please guide us on this issue?

Thank you

BR

Srinivas

[tamas_hoznek]

I have not heard yet about Personas adding the + signs as separators.

If this only happens when Personas is enabled but not in pure webgui, then create a support incident and we will look into the issue.

[srini_brahmasani]

Hi Tamas

We implemented notes showing in red and yellow(Implemented latest version).

Now we do not have any issue with '+' symbol and we are good to go-live.

Thank you so much for your great help in resolving these upgrade issues.

BR

Srinivas