Regarding Basic settings for Table layout in Persona 2.0 SP03

[former_member193190]

Hi Experts,

We are facing the below problem related to table layout in Personas in many of the transactions for which we have created flavors in Personas.

Personas uses the backend ECC table layout basic settings for the table controls for example in ME51N, MIGO etc. the problem what is happening here is we are developing Personas flavors for end user to make the screen simple, so the requirement here is to display may be 10 columns out of 60 columns which is available for that table control, 2 problems are happening in this:

1. As Personas uses the same basic settings of table layout in ECC, so if the functional people or super users changes the basic setting in the ECC the same thing is reflecting in the Personas flavors for the end users.
2. When we hide columns in Personas in a table control, we know that Personas only understand the sequence number of the columns and not the columns name, so when the basic setting is getting changed  or dynamically columns are appearing based on the data entered in the ECC, the columns shown in the Personas flavors all are getting affected due to this because the sequencing of the columns are getting changed.

So the solution what we think here is can we segregate the table settings for the back-end functional/super user and for the Persona user, is there way to implement this?

[Former Member]

Hi,

I am working on ME51N too and am being bothered bu similar issues. More UI issues due to this can been seen:

1. The 3 expandable icons status are also affacted by the backend users. My solution is to use script to expand all 3 icons (hidden) always when personas starts. Similar for the "side panel" due to dicument overview btn. Dynamic UI is so complex!

2. For hiding columsn of table, I am having issues that after I hide some columns, and I enter 'V' in Account Assignmemnt column, Personas UI is sending request constantly to backend, so UI is "dead".

One my idea is to make all UI controls by Personas and upon Save, all data will be copied to the table. BUT, since the data in SAP objects have certain logics from the backend data, we cannot have the logic check after entering data - this causes issue that users have enter all data, after press Save, it conplains a lot data that are not correct - headache!

If you find solution for this, pls share, appreciate! 🙂

Dong Zhu

[former_member105930]

Hi Dong,

Have you perhaps thought for your second issue, to have say on the main smen page different script buttons to select the different account assignments. These then default the account assignment through scripting. you have seperate flavors per account assignments with all the relative columns showing for that specific assignment?

Ian

[Former Member]

HI Ian,

Thanks for the new idea. I will investigate it.
Our cases is also a bit more complex that there are other key factors like "Plant" that have impact on other elements.

In general we want to make unified app for multiple nusiness units. And they want to have everything on one page. If we optimise the original SAP objects, we haev the data logic, but the dropdown list, eg, plant, has too much and is to complex. I have made a simple dropdown for solving that problem, but I con't know how to hide the original F4 key for that column. The main issue in this post is that if the backend only control the master data and data relationship, it will be OK for frontend app. But now the backend also impacts the frontend UI layout, which is not so good architecture.
It would be nice if it were made as MVC structure - namely changing data model should not affect UI view.

Br,

Dong