Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Maintaining client field in a cross client table

Hi everyone,

I am struggling with this dictionnary issue.

My goal is to create a cross client transactional table that would allow me to create entries in SM30 and manually enter the client number. I do not want to transport the data in an OT.

My fields are like this :




When I perform the table maintenance generator the MANDT field does not appear as a column in SM30 and it is either populated automaticaly or not populated at all depending on which setup I choose.

I tried different solutions but I am not able to find the right combination. I also looked at solutions from other discussions but none of them seems to be solving my issue.

I tried the following:

- Delivery Class : A, C and E

- Data Class : APPL0, APPL1 and APPL2

- One step and Two step maintenance screens in the Maintenance Generator

- Difining MANDT has a key field and not a key field

- I also tried to modify the overview screen generated by the maintenance generator to add the MANDT column

If I maintain table T000 in SM30, I get the result I want since the MANDT field appears in the overview screen and you can create new entries and specify manually the client value. I tried to copy the T000 table in a Z table but I do not obtain the same possibility in SM30.

Can someone give me the right combination for my table and maintenance generator?

Thank you very much for your support,


Former Member replied

I tried using a predefined type to refer CLNT and size 3 and it worked(Even the field name as MANDT is accepted). Then I tried using a custom data element with a pre-defined type CLNT and Size 3 it worked too.

I re-generated the TMG on each occasion after making changes.

It seems as long as you refer MANDT as data element or domain SAP TMG will not have this field as the TMG generation program has got a hardcoded check ( Except table T000 obviously ).

Not sure why you need Client as non-key field. But this could be a workaround.


0 View this answer in context

Helpful Answer

Not what you were looking for? View more on this topic or Ask a question