SAP Personas, tab key caching in MM01

[simonpolovina1]

In another thread () it was highlighted that it is difficult to select views in the material master due to the tab key caching in MM01 (and generally difficult with the tab key caching in create mode for example if there is only 1 TAB in MM01).

An initial answer stated that in MM01 in general it's a bit tricky to use tab cache. But with combination of additional action, it works nicely. Also you need to take care of the mandatory fields.

Can anyone elaborate on their experiences with this issue? Thanks, Simon

[iker_espinosa]

Hi,

we are developing some flavors with MM01 but we have the mandatory fields problem.

We use SAP Screen Personas 2.0.

1.- How could we merge tabs using cache and mandatory fields?

2.- Is it possible to merge tabs with mandatory fields?

Thanks.

[tamas_hoznek]

In general, tab caching with mandatory fields in the cached tabs will be a problem because this dictates a certain sequence in which the screen fields must be populated and caching will not be able to handle this due to the required field check kicking in.

The Additional Actions feature in tab caching has a very restricted feature set compared to regular scripting, and thus will likely not help matters here either.

[iker_espinosa]

OK, thanks... as you say Screen Personas does not work well with mandatory fields... but ¿is it possible? ¿how?