Skip to Content
avatar image
Former Member

User exit in ME52N to disable fields

Hi experts,

does anyone know a user exit where I can do a loop at screen to disable all the fields except 2 on the transaction?

We need to do this because there is 2 users that are allowed to enter this transaction, one can do everything he wants, but the other can only change 2 fileds on the screen, so I'm thinking of doing a user check in a exit, depending on the user, I'll do the loop at screen.

If you have a better idea, please tell me.

Thanks!

Eduardo

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Oct 05, 2007 at 07:08 PM

    Hi

    Hi check this, and you can achieve the requirement with the help of creating the transaction variant.

    we can create Transaction Variants Using SHD0 Transaction.

    Transaction Variants and Screen Variants

    Transaction variants can simplify transaction runs as they allow you to:

    Preassign values to fields

    Hide and change the 'ready for input' status of fields

    Hide and change table control column attributes

    Hide menu functions

    Hide entire screens

    In particular, hiding fields in connection with screen compression, and hiding screens, can result in greater clarity and simplicity.

    Transaction variants are made up of a sequence of screen variants. The field values and field attributes for the individual screens found in transaction variants are stored in screen variants. Each of these variants is assigned to a specific transaction, can, however, also contain values for screens in other transactions if this is required by transaction flow. The transaction that the variant is assigned to serves as initial transaction when the variant is called.

    There are both client-specific and cross-client transaction variants. All screen variants are cross-client, but may be assigned to a client-specific transaction variant.

    A namespace exists for cross-client transaction variants and screen variants and both are automatically attached to the Transport Organizer. Client-specific transaction variants must be transported manually.

    In principle, transaction and screen variants can be created for all dialog and reporting transactions. There are, however, certain Restrictions that apply to certain transactions, depending on their internal structure.

    No transaction variants are possible with transactions already containing preset parameters (parameter transactions and variant transactions).

    Regards

    Anji

    Message was edited by:

    Anji Reddy Vangala

    Add comment
    10|10000 characters needed characters exceeded