Screen Personas 2.0 SP03 - Tab merge Problems

[Former Member]

Hello,

I want to merge tabs in transaction IW51.

I change the position a ALV-table (original tab "tasks" - new tab "Additional Data 2").

Everything is working fine. If I enter a wrong userID in the tasks-table, the hidden tab "tasks" will be displayed.

I can't correct the UserID, because the ALV-table is no longer be part of this tab.

Switch to tab "Additional Data 2" is impossible.

At the moment I don't create a entry for the elementId-overwrite-rules (Admin-Tcode).

Is that neccessary in this case? I check the SAP Note #1999747 but I don't understand, how I have to set the overwrite rules for this element.

Any idea how I can solve this problem?

Matthias

[praseo]

Can you please confirm the behavior in basic view.
After entering invalid UserID, are you able to switch to the tab 'Additional Data 2'?
If tab switching is not possible, then that means tab merging will fail in such a use case.

Always check basic view behavior before deciding on tab merging.
In cases where tab switching is blocked by validation error, tab caching cannot succeed.

Regarding the Screen / Control ID overwrite rules.

1. Add the following in SPRO -> Cross Application components -> SAP Screen Personas -> Maintain Screen ID Overwrite Rules    

Transaction : IW51

Original Program Name : SAPLIQS0

Original Screen Number : 7200

New Program name :

New Screen Number : 720X

Transaction : IW51

Original Program Name : SAPLIQS0

Original Screen Number : 7204

New Program Name :

New Screen Number : 720X

This information is available in SAP Note 1999747 for transaction IW21.

and

2.  In /PERSOS/ADMIN_UI -> General Actions -> Control ID Overwrite Rules Maintenance

Transaction : IW51

Program Name : SAPLCOIH

Screen Number : 3000

Overwrite Rule Pattern : ^ses\[0\]/wnd\[0\]/usrUSRAREA/subcntSUB_ALLSAPLCOIH3001/subcntSUB_LEVELSAPLCOIH\w+$

Overwrite Rule Replacement : ses[0]/wnd[0]/usrUSRAREA/subcntSUB_ALLSAPLCOIH3001/subcntSUB_LEVELSAPLCOIH

This information is available in SAP Note 1999747.

Regards,
Pradeep