cancel
Showing results for 
Search instead for 
Did you mean: 

SAP Screen Personas 3.0 SP02 to SP03 - scripts: no update by Flavor export in other System?

former_member193127
Participant
0 Kudos

Hello,

there is a grave scripting issue:

we have a System with SAP Screen Personas 3.0 SP02 on a System with SAP Basis 702, Kernel 722 (Early Access Programm) and recorded scripts with Transaction MIGO.

The address of the movement type dropdown is:

session.findById("wnd[0]/usr/ssubSUB_MAIN_CARRIER:SAPLMIGO:0003/subSUB_FIRSTLINE:SAPLMIGO:0011/cmbGODYNPRO-ACTION").key = "A01";

Now we imported this flavor in a System with Version 3.0 SP03, SAP Basis 740, Kernel 745 and the scripts do not work. If I recorded they in this system, the address is:

session.findById("wnd[0]/usr/ssubSUB_MAIN_CARRIER:SAPLMIGO:*/subSUB_FIRSTLINE:SAPLMIGO:0010/cmbGODYNPRO-ACTION").key = "A01";

We updated the Flavor, there is no changing in the script.

Is there any way to avoid the correction of every possible wrong address by exporting flavors in a other SAP Releases? Whats about Systemupgrades?

Thanks for helping

Accepted Solutions (1)

Accepted Solutions (1)

tamas_hoznek
Product and Topic Expert
Product and Topic Expert
0 Kudos

Looks like this is caused by a missing control ID overwrite entry in SP02. In SP03, there is such an entry (hence the * in the ID instead of 0003). Your flavor includes the customization for the ID with 0003 so the same won't be applied to the ID with *.

If that's the case, you should be able to fix such problems by running the control ID conversion routine in the Admin transaction.

Since we don't know what the exact situation is, it'd be best if you create an OSS incident and provide access to the systems so we can determine what is different between your SP02 and SP03 environment and how to fix the issue.

Answers (0)