Skip to Content
avatar image
Former Member

Customizing changes with Workbench Transport Request

Hello gurus,

I do not understand why customizing changes, despite having client field in their tables, sometimes, require a Workbench Transport Request instead of a Customizing one.

For instance: View 'V_T045T' has got 'MANDT' field. Its table can be modified in SPRO -> Financial Accounting -> Bank Accounting -> Business Transactions -> Bill of Exchange Transactions -> Bill of exchange Receivable -> Present Bill of Exchange Receivable at Bank -> Define DME User IDs.

Delivery class of this view is 'C', and its only involved table too.

I always thought that Workbench TRs could not have 'MANDT' field in their table records.

Can anyone explain me what am I missing? Which trigger causes to force user to create a Workbench instead of a Customizing?

Thanks a lot!,


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Feb 07, 2017 at 02:34 PM

    Check object definition with transaction SOBJ, is the flag "client specific" set (for info on my systems it creates a Customizing request)


    Add comment
    10|10000 characters needed characters exceeded

    • It's probably useful for many little things. My 2 cents:

      • Organization (for instance: displaying only transport requests containing repository objects)
      • Authorization (S_TRANSPRT object; for instance: developers should not be allowed to create customizing requests)