SM30 issue

[Former Member]

Hi,

What would be the reason whenever a table view is different when viewed from SM30 and SE16n?

Here are their differences:

1. Arrangement of columns are different.

2. Key fields in SE16n are not key fields in SM30.

3. Character length of a field in SE16n is 2 while in SM30, it is only limited to 1.

Any help is greatly appreciated.

Moderator message: please use more descriptive subject lines from now on.

Edited by: Thomas Zloch on Jul 12, 2010 1:54 PM

[Former Member]

Hi,

What would be the reason whenever a table view is different when viewed from SM30 and SE16n?

Here are their differences:

1. Arrangement of columns are different.

2. Key fields in SE16n are not key fields in SM30.

3. Character length of a field in SE16n is 2 while in SM30, it is only limited to 1.

Any help is greatly appreciated.

Moderator message: please use more descriptive subject lines from now on.

Edited by: Thomas Zloch on Jul 12, 2010 1:54 PM

[kesavadas_thekkillath]

1)Arrangement of columns are different.

This is because there will be a maintenance view created for a table and then the maintenance would be generated, we can change the position of the fields in maintenance view, it can also done by changing the table control in the generated flow logic.

2. Key fields in SE16n are not key fields in SM30.

This cannot happen at all.

3.Character length of a field in SE16n is 2 while in SM30, it is only limited to

This can be done by modifying the screen attributes after generating the maintanance.

For point 2 will you please provide the example.

[Former Member]

Thanks so much for the response, for #2, let's say I have a custom table ZTAB with key fields f1, f2 in se11, however, when viewed using SM30, only f1 shows as key.

[kesavadas_thekkillath]

Hi,

May be the field is set to no display mode in maintanance view and populated im maintance generator using events.

Check the maintanaace view of the table.

[Former Member]

Thank you so much for these Keshav, it clarified everything for me.