Skip to Content
avatar image
Former Member

Table layout cannot be controlled using Personas 2.0

Scenario1:

While changing the table layout using Personas by hiding some columns, and transporting it to target system the table layout design get change as the basic setting/default setting are differ in source and target system in ECC.

Scenario2:

Based on a default setting we are controlling the table layout in Personas. But if this default setting is changed by the super user, than the table layout customized in Personas is also getting changed.

Is there any way to control the table layout in Personas 2.0 /SP03 and Personas 3.0, so that it will not get affected by the change in the default settings in the ECC?

Please share the document and the information regarding the customization of the table layout in SAP Screen Persona 2.0 SP03 or SAP Screen Persona 3.0.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Dec 11, 2015 at 06:17 PM

    Table variants in the backend cannot be changed by Personas. The flavor will be applied on top of the backend table layout. Therefore it is essential that the table variants match in the source and target systems. You have to make sure that first the matching table variant is selected that was used when the flavor was created.

    Add comment
    10|10000 characters needed characters exceeded

    • Personas 3.0 uses the column name for identification, instead of the sequence index.


      Still, even in this case there are certain transactions where the backend logic assigns dynamic names to columns that can behave like indexes or names are completely different in one system vs. another. That is a tough problem because the flavor only knows the static names of the columns when it was created and the same formatting will not be applicable to the other system's setup.