Screenvariant vs Transactionvariant in TA SHDS

[Former Member]

hi,

i am in module pool, and via TA SHDS, i can set up screen/transactionvariants for my dynpro screen 100.

in fact u set up an screenvar for a transaction in SHDS.

normally, when entering SHDS you get two parameterfields (transaction + variant).

Now i am facing a weird situation: Sometimes, when calling SHDS i get 4 input fields (the actual TA Code from system status is also not SHDS but 'SHD0_MANDT')

so i get fields: transaction, screenvariant, program, dynpro.

Why is that? As I try to fill the fields via batch-input, i need to know, when to expect which input fields.

thanx for help,

matthias

ps: i noticed, that i get only 2 inputs, when entering the

TA SHDS newly, without having saved a screenvariant).

But once I managed to save a screenvariant, I always get 4 input fields.

Message was edited by: matthias kasig

[Former Member · Accepted solution]

Hi,

Try with =BABA or =BACK OK_CODES.

Thanks

Eswar

[Former Member · Accepted solution]

thank you eswar =BACK worked out fine - although i already thought about the right screw, which to turn, i did not check different ok codes, because i believed the batch input recorder. Never the less: <b>10 points for Eswar Kanakanti,</b>

regards, matthias

[Former Member · Accepted solution]

Thank you......

[Former Member]

You can set up through SHd0 also. Try with this.

Thanks

Eswar

[Former Member]

hi Eswar and Phani,

thanx for your help so far. I'm almost done...

the only problem I am still facing is the transaction SHD0 or SHDS itself. I don't get really back to my calling program...

what i am doing is, during pai of my dynpro 100:

      DATA il_bdcdata TYPE TABLE OF bdcdata.
      DATA wl_bdcdata TYPE bdcdata.
      wl_bdcdata-program = 'SAPMSHD0'.
*      wl_bdcdata-dynpro  = '0500'.
      wl_bdcdata-dynpro  = '2000'.
      wl_bdcdata-dynbegin = 'X'.
      APPEND wl_bdcdata TO il_bdcdata.
      CLEAR wl_bdcdata.

      wl_bdcdata-fnam = 'BDC_OKCODE'.
      wl_bdcdata-fval  = '/ETVBK'.
      APPEND wl_bdcdata TO il_bdcdata.
      CLEAR wl_bdcdata.

      wl_bdcdata-fnam = 'BDC_CURSOR'.
      wl_bdcdata-fval  = 'SHDTV-TCODE'.
      APPEND wl_bdcdata TO il_bdcdata.
      CLEAR wl_bdcdata.

      wl_bdcdata-fnam = 'SHDTV-TCODE'. "SHDTV-TCODE
      wl_bdcdata-fval  = 'ZSEL_03'.
      APPEND wl_bdcdata TO il_bdcdata.
      CLEAR wl_bdcdata.

*      CALL TRANSACTION 'SHD0_MANDT' USING il_bdcdata.
      CALL TRANSACTION 'SHD0' USING il_bdcdata.

So I performed a batch-input recording and putthe values collected manually in place.

Now the point is, SHD0 won't allow my program to get back control...

In SHD0 after setting up transaction- and screenvariants and saving all I return to my program (and see the actual saved variant). But when I produce a new ok_code, like F8 or simple F3, the save-variant-screen comes up again... this is very annoying.

<b>Is that maybe anything to do with the 'BDC_OKCODE' in my batch-input recording?</b>

help appreciated once more,

regards matthias

[Former Member]

Hi,

For some more details on this,Click on the 'I' help icon,it will tell you every thing.

[Former Member]

Hi,

In the SHDS transaction ,there are 2 things ie Transaction variant & screen variant.

For Transaction Variant input is only 2 parameters (transaction + variant).

But in Screen Variant it has 4 parameters(transaction, screenvariant, program, dynpro).

You can check that while going to GOTO in the menu path & check the first path(if the initial screen has Transaction Variant then you will have Screen Variant there & vice versa).

So use then accordingly to your needs.