topic Re: problem with call transaction in Application Development and Automation Discussions

problem with call transaction

Former Member — Fri, 24 Jul 2009 07:11:26 GMT

Dear all,

i am using call transaction function and use skip first screen but the first screen will not spiked.

i am using this one transaction code SU01.

and

 CALL TRANSACTION  'SU01'  AND SKIP FIRST SCREEN.

please solve this problem.

thanks,

Abhilash

Re: problem with call transaction

Former Member — Fri, 24 Jul 2009 07:15:41 GMT

Hello


set parameter id 'XUS' field 'USER_NAME'. <= set user name here
call transaction 'SU01' and skip first screen.

Re: problem with call transaction

Former Member — Fri, 24 Jul 2009 07:18:01 GMT

HI,

The first screen will be skipped only if you specify some username to it.

SET the parameter id XUS with a particular username. Then only you will be able to skip teh first screen.

Else do a recording and use CALL TRANSACTION with the BDCDATA table and run in N mode till you reach the second screen.

Regards,

Ankur Parab

Re: problem with call transaction

Former Member — Fri, 24 Jul 2009 07:18:46 GMT

ya already i put this one code



DATA: F_SUBRC LIKE SY-SUBRC,
        S_DATA LIKE IT_DATA.

  READ TABLE IT_DATA INDEX P_SELFIELD-TABINDEX INTO S_DATA.


  CASE P_UCOMM.
    WHEN '&IC1'.
      CASE P_SELFIELD-SEL_TAB_FIELD.

        WHEN 'IT_DATA-BNAME'.
          IF S_DATA-BNAME NE ''.
            SET PARAMETER ID 'XUS' FIELD S_DATA-BNAME.
            CALL TRANSACTION  'SU01'  AND SKIP FIRST SCREEN.
          ENDIF.
      ENDCASE.
  ENDCASE.

but the first screen is not skipped.

Edited by: Abhilash on Jul 24, 2009 9:20 AM

Re: problem with call transaction

Former Member — Fri, 24 Jul 2009 07:19:00 GMT

Hi Abhilas,

use this.

SET PARAMETER ID 'XUS' FIELD p_user.

CALL TRANSACTION 'SU01' AND SKIP FIRST SCREEN.

Regards,

Vijay

Re: problem with call transaction

Former Member — Fri, 24 Jul 2009 07:25:27 GMT

actually i am using this one in my report.

so i want to link with report.

Re: problem with call transaction

Maciej_DomagaBa — Fri, 24 Jul 2009 07:55:41 GMT

I think the first screen is not skipped in this case because transaction SU01 expects choosing one of the functions it offers (triggered by buttons available on the first screen) - so it does not "know" which of them you mean: creating, changing, viewing etc. None of those functions is default - if you run SU01 manually, type a username and hit Enter - nothing happens too, ie. the screen does not disappear - so the same happens when SU01 is called by your code.

You can prepare batch-input data and perform "call transaction 'SU01' using ..."

regards

Re: problem with call transaction

Former Member — Sat, 19 Dec 2009 03:46:52 GMT

solved