PersonasFlavorUpdater utility program is now available for Personas 2.0 SP03 (also Personas 1.0 SP05) which can update the flavor with newly added screen and control id overwrite rules. For more details, please see SAP Screen Personas knowledge base.
We had a lot of questions about Screen Id and Control Id overwrite rules from our customers. So we did a tutorial session in our Practitioner forum session 10. If you missed it, then this blog will help you understand the overwrite rule mechanism.
Screen Id overwrite rules
When you are using SAP Screen Personas to create a flavor on your business transaction, you might sometimes notice that the screen changes in the flavor suddenly disappear or reappear while navigating across tabs or clicking on expand/collapse buttons etc. This is because Personas uses a combination of "transaction code + program name + screen number" to identify screen changes but due to dynamic design of Dynpro screens the program name or screen number can change within the same transaction. So Personas uses a mechanism of Screen Id overwrite rules to neutralize the program name or screen number change to preserve the screen changes in such cases.
For example, if you go to IW23 transaction and click on page like icon at bottom right corner (you can click on black arrow head to expand if you are not seeing the page icon), you will see the screen information as in the below screen and you can select "Dynpro" to see program name (SAPLIQS0 part) and screen number (7200 part)
If you create a new flavor with background colour as green and save the flavor. When you navigate on screen by clicking on the tabs, you will notice that the background colour stays when you are on the first 4 tabs and also the program name and screen number remains same (SAPLIQS0/7200), but the background colour disappears when you click on "Items" tab and also the screen number changes to 7204
To handle such cases, you need to identify the program name and screen number changes for your business case and then add the Screen Id overwrite entries with a neutral screen number such as "720X" in this case for both the entries as shown below under SPRO -> Cross-Application Component -> SAP Screen Personas -> Maintain Screen ID Overwrite Logic
| Transaction Code | Program | Original Screen Number | New Screen Number | New Program |
|---|---|---|---|---|
| IW23 | SAPLIQS0 | 7200 | 720X | |
| IW23 | SAPLIQS0 | 7204 | 720X |
Control Id overwrite rules
Similar to screen id behaviour, you will sometimes see that the changes done for a particular control disappears or reappears when you are navigating across tabs or clicking on expand/collapse button. This is because the ids of some of the control or its containers are generated dynamically based on program or sometimes even system id and client.So Personas uses mechanism of Control Id overwrite rule to neutralize control id of such control and all its sub controls to preserve the screen changes.
Control id can be seen in properties window of Personas editor by selecting the control when you are editing any flavor. You can copy the control id by clicking on it
For example, in ME21n, if you create a flavor with header panel expanded and item overview panel collapsed and set the background colour of item dropdown box to orange and save the flavor. When you navigate on screen by collapsing the header and expanding item overview, you will notice that the item dropdown background colour disappears
when you check the control id of "Item" dropdown with header panel expanded but item overview panel collapsed, it would be
ses[0]/wnd[0]/usrUSRAREA/subcntSUB0SAPLMEGUI0013/subcntSUB3SAPLMEVIEWS1100/subcntSUB2SAPLMEVIEWS1200/subcntSUB1SAPLMEGUI1301/subcntSUB1SAPLMEGUI6000/cmbDYN_6000LIST
and again when you check the control id of same "Item" dropdown with header panel collapsed but item overview panel expanded, it would be
ses[0]/wnd[0]/usrUSRAREA/subcntSUB0SAPLMEGUI0016/subcntSUB3SAPLMEVIEWS1100/subcntSUB2SAPLMEVIEWS1200/subcntSUB1SAPLMEGUI1301/subcntSUB1SAPLMEGUI6000/cmbDYN_6000LIST
You can notice that the values differ above where highlighted in bold.
To handle such cases, you must identify such control id changes for your business case and then add Control Id overwrite entry with neutral control id under /n/persos/admin_ui -> General Actions -> Maintain Control Id Overwrite Logic as shown below. here, using regular expression to define original control id helps Personas to find and replace the control id even for any child controls for that control.
| Transaction | Program | Screen Number | Original Control Id | New Control Id |
|---|---|---|---|---|
| ME21N | SAPLMEGUI | 0014 | ^ses\[0\]/wnd\[0\]/usrUSRAREA/subcntSUB0SAPLMEGUI\w+$ | ses[0]/wnd[0]/usrUSRAREA/subcntSUB0SAPLMEGUI__COMMON__ |
If you notice a similar behaviour for any of your transaction then you can check our note#1999747 for the required overwrite rules. If you don't find a rule for your transaction, then we recommend you to log a message to check with us if new overwrite rules are required for that transaction.
Please note that any new addition or modification of screen id or control id overwrite entries requires re-creation of flavor, so we recommend you to identify and add the required overwrite entries before you start with your flavor creation.
For the SAP Screen Personas team,
Chinthan Yajamaan
12 Comments