topic Re: for one module pool program how to create two transactions in Application Development and Automation Discussions

for one module pool program how to create two transactions

Former Member — Tue, 12 Jun 2007 14:37:50 GMT

for one module pool program how to create two transactions.if we execute one transaction , it has to display one application. when we execute second transaction , it has to display the second application

Re: for one module pool program how to create two transactions

Former Member — Tue, 12 Jun 2007 14:40:39 GMT

By using different screen numbers as per the applications.

Re: for one module pool program how to create two transactions

Former Member — Tue, 12 Jun 2007 14:41:21 GMT

Hello,

Inside the report u need to make the changes liike this.


  IF SY-TCODE = 'ZFEHLTEILE' OR
     SY-TCODE = 'ZLIEFERLISTE'.
    LOOP AT SCREEN.
      IF SCREEN-NAME = 'SELPA-LOW'
      OR SCREEN-NAME = '%_SELPA_%_APP_%-VALU_PUSH'.
        SCREEN-INPUT = 0.
        MODIFY SCREEN.
      ENDIF.
    ENDLOOP.
  ENDIF.

  IF SY-TCODE <> 'ZFEHLTEILE_PTA'.
    LOOP AT SCREEN.
      IF SCREEN-GROUP1 = 'LAY'.
        SCREEN-ACTIVE = 0.
        MODIFY SCREEN.
      ENDIF.
    ENDLOOP.
  ENDIF.

  IF SY-TCODE = 'ZLIEFERLISTE' OR " brc1wa2 002
     SY-TCODE = 'ZFEHLTEILE_ATMO3_END'.
    LOOP AT SCREEN.
      IF SCREEN-GROUP1 = 'GR1'.
        SCREEN-ACTIVE  = 0.     " vsm1kor 002
        MODIFY SCREEN.
      ENDIF.
    ENDLOOP.
  ENDIF.

Like this make change in ur report also.

vasanth

Re: for one module pool program how to create two transactions

RichHeilman — Tue, 12 Jun 2007 14:42:11 GMT

All you need to do is tie the transaction codes to different screens with in the module pool program. Your module pool can have a lot of screens, in some cases, taking the user in to two different directions, in these cases, the transaction codes are simply defined with two different start screens.

Regards,

RIch Heilman

Re: for one module pool program how to create two transactions

Former Member — Tue, 12 Jun 2007 14:53:56 GMT

Instead of different screens, you can have multiple transactions calling the same screen and use logic to determine how the screen should be handled (display or change for example).

Rob