Calling transaction issue

Hi ,
HRASR_EXEC_TX_PASR_W is a calling Tcode for PA30, PASR, & START_REPORT with Check Indicator as "blank" in SE97.
My understanding is when the user is authorized for HRASR_EXEC_TX_PASR_W, he should be having access for PA30, PASR, & START_REPORT.But its not working.
What can be the issue here?
Peeyush

Hi
Is your question answered or not if not please correct me if i am wrong :
Statement by you :HRASR_EXEC_TX_PASR_W is a calling Tcode for PA30, PASR, & START_REPORT
You are asking if user tries to run Transaction  PA30, PASR, & START_REPORT he should be allowed.
As per my understanding system will not allow to execute these transactions directly as they are called in program.
the intial check will fail at the time of execution of transaction as these Tcode  will not be part of Object S_Tcode.
Please check this object in ur role , i think you will get the answer.
Mayank Gupta

Similar Messages

  • Stumped on BDC Call Transaction issue

    Hi,
    When I do a:
                call transaction 'VGM2' using bdcdata
                   messages into itab.
    It doesn't work.
    If I debug the transaction, there is is a row of data in itab.
    I would like to use this data to figure out what's going wrong, but I can't find any documentation on what the fields in the table refer to.
    Does anyone know where BDCMSGCOLL is documented along with the error numbers that get returned?
    Thx.
    Andy Jacobs

    Hi Andy,
    help.sap.com gives very good documentation.  Just plug in
    BDCMSGCOLL and look at the segment on Call Transaction Using.
    For example:The MESSAGES specification indicates that all system messages issued during a CALL TRANSACTION USING are written into the internal table <MESSTAB> . The internal table must have the structure BDCMSGCOLL .
    Meaning of the fields:
    System fields:
    SY-MSGID Message-ID
    SY-MSGTY Message type (E,I,W,S,A,X)
    SY-MSGNO Message number
    SY-MSGV1 Message variable 1
    SY-MSGV2 Message variable 2
    SY-MSGV3 Message variable 3
    SY-MSGV4 Message variable 4
    These messages are in message classes.
    For your transaction VGM2 the message class is VL.
    You can see this by doing a System->Status on the screen and looking at the message-id of the report line.
    Each of the messages are self-documented in the message class.  Go to transaction SE91 and view the messages of VL.
    You can handle incorrect transactions by using update mode S (synchronous updating) and checking the return code from CALL TRANSACTION USING. If the return code is anything other than 0, then you should do the following:
    write out or save the message table
    use the BDCDATA table that you generated for the CALL TRANSACTION USING to generate a batch input session for the faulty transaction. You can then analyze the faulty transaction and correct the error using the tools provided in the batch input management facility.
    regards,
    Marilyn Pratt

  • Issue in background job for call transaction

    Dear All,
    I am facing a strange issue with call transaction. I need to add some Purchase requisitons in the APO using Call transactionmethod. It is working fine In All screen mode and No Screen Mode. But when I schedule the program in BAckground processing it is not wokring fine. It is not creating any Purchase requisitioins. When I debug the background Job it is creating Purchase requisitions.
    Please find the code below
        DATA: l_wa_params TYPE ctu_params.
        l_wa_params-dismode = l_c_mode.
        l_wa_params-updmode = 'A'.
        l_wa_params-defsize = 'X'.
        l_wa_params-racommit = 'X'.
        CALL TRANSACTION '/SAPAPO/RRP3' USING fp_i_bdcdata OPTIONS FROM l_wa_params
                                            MESSAGES INTO l_i_bdcmsgcoll.

    Hi,
    I have exactly the same problem with transaction /SAPAPO/RRP5.
    Thanks in advance for your help,
    Yannick CAREL

  • Issue with using call transaction CJ9F and F.M  BAPI_PROJECT_MAINTAIN

    Hello All,
    In my custom program for a given project in selection screen we are getting all the related data as shown in CJ20N, in this screen I first created the WBS element and during save we used F.M BAPI_PROJECT_MAINTAIN to update the data, and next called transaction CJ9F to update BLC, after this we are comming back to selection screen 1000.
    Now from selection screen if i enter again into that project details screen and try to create a new WBS it is showing below information msg.
    Changing the contents of the field is not permitted
    Message no. CJ727
    If i remove the call transaction CJ9F part during save i am not getting the above error msg.
    I think i am getting this error when we call the function module BAPI_PROJECT_MAINTAIN twice in the program.
    Please help me to resolve this issue, as this msg is not allowing to save or create anything. 
    But i found that if i come totally out of my custom transaction and enter once again into that Z transaction it is working fine with out that message
    Please help me to resolve this issue.

    Hi,
    Not sure, but if it is possible, complete your project update using the custom transaction and do the CJ9F afterwards seperately.
    Regards
    Sreekanth

  • 2 issues with call transaction to LS24

    Hello All,
    There are 2 issues with call transaction to LS24.
    <b>1) It doesn't take batch value and displays stock for all batches.
    2) When you go back, it doesn't go back to the calling program.</b>
    Any thoughts ?
    <u>Here is my code:</u>
    PARAMETERS: p_lgnum TYPE lgnum,
                p_matnr TYPE matnr,
                p_werks TYPE werks_d,
                p_lgort TYPE lgort_d,
                p_charg TYPE charg_d.
    START-OF-SELECTION.
    END-OF-SELECTION.
      PERFORM display_stock_per_batch.
    *&      Form  DISPLAY_STOCK_PER_BATCH
    FORM display_stock_per_batch .
      SET PARAMETER ID 'LGN' FIELD p_lgnum.
      SET PARAMETER ID 'MAT' FIELD p_matnr.
      SET PARAMETER ID 'WRK' FIELD p_werks.
      SET PARAMETER ID 'LAG' FIELD p_lgort.
      SET PARAMETER ID 'CHA' FIELD p_charg.
      CALL TRANSACTION 'LS24' AND SKIP FIRST SCREEN.
    ENDFORM.                    " DISPLAY_STOCK_PER_BATCH

    hello
    use this code
    perform bdc_dynpro      using 'SAPML01S' '0209'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'RL01S-CHARG'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '/00'.
    perform bdc_field       using 'RL01S-LGNUM'
                                  p_lgnum.
    perform bdc_field       using 'RL01S-MATNR'
                                  p_matnr.
    perform bdc_field       using 'RL01S-WERKS'
                                  p_werks.
    perform bdc_field       using 'RL01S-LGORT'
                                  p_lgort.
    perform bdc_field       using 'RL01S-BESTQ'
    perform bdc_field       using 'RL01S-SOBKZ'
    perform bdc_field       using 'RL01S-CHARG'
                                  p_charg.
    perform bdc_dynpro      using 'SAPML01S' '0209'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '/EBACK'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'RL01S-LGNUM'.
    perform bdc_transaction using 'LS24'.
    may be it will help u

  • Doubt in uploading using call transaction method

    hi all
    i am uploading f-29 in call transaction method .. i have a problem in currency field, the currency field is not picking up it shows a error that input field is longer than screen field .. i have declared currency field as type BSEG-WRBTR(same as screen field ...how to go about
    thanks
    lokesh

    Hi,
    When you use the database value directly in your BDC, you will have this issue. It is always advisable to use character fields when doing BDC. so change it to charecter field and try it..
    Regards
    Sudheer

  • CALL TRANSACTION AND SKIP FIRST SCREEN to specified tab in TCODE 'IW32'

    Hi,
    I am using CALL TRANSACTION AND SKIP FIRST SCREEN in ALV Grid Report to call IW32 tcode and it goes to tcode skipping the first screen. But it goes to the default header tab in the tab control. Whereas I wish to go to the specified tab 'OPERATIONS'.
    Can any one help me, as to how to resolve this issue ?
    Thanks in advance.

    Sridher,
    I have the similar requirement. but in my case its COSTS tab. Could you please provide the code you have used for this to work?
    I used standard "call transaction with mode 'E' ". This seems to be working but I am not pleased by my effort. Is there any proper way that you might have followed ?
    Greatly appreciated your help.
    Regards,
    Reddy

  • Call Transaction and skip first screen in SE37

    Hi All,
    I want call transaction SE37 and skip first screen of it. Is it possible through the statemen Call transaction 'SE37' and skip first screen ?.
    Of course I have populated the parameter id 'LIB' before this statement but it is not working. Though I have found several posts with this solution but it's not working for me. Could anyone please let me know if this can be done using this statement or there are any other additions required along with this statement or it is not at all possible to achieve this functionality.
    Thanks in advance !!.

    Solved! without a solution? very funny.
    In somewhere of second screen related bdcdata, intensionlly make a mistake to force the system throws the error and the call the trasnaction with mode 'E'. This will solve the issue.
    perform bdc_field       using 'BDC_CURSO'                   " I removed letter R in 'BDC_CURSO'
                                                 'ISEG-ERFMG(01)'.
    CALL TRANSACTION 'XXXX' USING BDCDATA MODE 'E'.
    Thanks.
    Suresh Yerra.

  • CALL TRANSACTION VK13 AND SKIP FIRST SCREEN

    Hi,
    I'm using ALV report and i want to call the the Tcode VK13 from alv and skip the screens.
    I have declared form user_command and calling from the "REUSE_ALV_LIST_DISPLAY".
    The actual issue is how to select the radio button in the pop up window and also skip the next screen to go the condition records screen when calling tcode VK13 by passing parameters.
    CALL TRANSACTION VK13 .
    Help is highly appreciated.
    Thanks,
    Kash

    Hello,
        As per the requirement I understood that you have to skip more than one screen in VK13 transaction.
    For this purpose, write a BDC (Upto the screen you want ) and use it in a call transaction .
    You have to do a partial BDC to the transaction VK13, providing all the data that is required to get to the screen you want and use the statement
    Call transaction 'VA03' using it_bdcdata mode 'E'...
    (IT_BDCDATA should have the information that is necessary to fill in the screens of VA03.)
    Eg:
    DATA: bdcdata_wa  TYPE bdcdata,
              bdcdata_tab TYPE TABLE OF bdcdata.
    CLEAR bdcdata_wa.
    bdcdata_wa-program  = 'SAPLSEOD'.        "Pass pgm name
    bdcdata_wa-dynpro   = '1000'.                    "Pass your screen you want to call
    bdcdata_wa-dynbegin = 'X'.
    APPEND bdcdata_wa TO bdcdata_tab.
    CLEAR bdcdata_wa.                                         "Optional
    bdcdata_wa-fnam = 'BDC_CURSOR'.                  "Optional
    bdcdata_wa-fval = 'SEOCLASS-CLSNAME'.        "Optional
    APPEND bdcdata_wa TO bdcdata_tab.              "Optional
    CALL TRANSACTION 'VK13' USING bdcdata_tab
                                MODE 'E'
                                UPDATE 'A'
                                MESSAGES INTO g_t_bdcmsgcoll.
    Regards,
    Lijo

  • CALL TRANSACTION 'MIR6' AND SKIP FIRST SCREEN .

    Hi all,
    i hope there is someone that can help me.
    My problem is: in an ABAP custom report in a FORM user-command my code is
      CASE ls_selfield-sel_tab_field.
        WHEN 'ITAB-BELNR'.
          IF NOT ls_selfield-value IS INITIAL.
            SET PARAMETER ID 'RBN' FIELD ls_selfield-value.
            CALL TRANSACTION 'MIR6' AND SKIP FIRST SCREEN .
      ENDCASE.
    When i click on output field of my report, not skip first screen but only call MIR6!!!
    How can i solve this problem? 
    Regards.

    Hi,
    First of all Please don't use all Caps for Subject Line
    Test Following Sample Code it will solve out your problem,
    DATA: it_bdcdata TYPE TABLE OF bdcdata,
          wa_it_bdcdata LIKE LINE OF it_bdcdata,
          belnr(10).
    belnr = '100'. " Give Document Number here
    DATA opt TYPE ctu_params.
    CLEAR wa_it_bdcdata.
    wa_it_bdcdata-program  = 'SAPMM08N'.
    wa_it_bdcdata-dynpro   = '100'.
    wa_it_bdcdata-dynbegin = 'X'.
    APPEND wa_it_bdcdata TO it_bdcdata.
    CLEAR wa_it_bdcdata.
    wa_it_bdcdata-fnam = 'BDC_CURSOR'.
    wa_it_bdcdata-fval = 'SO_BELNR-LOW'.
    APPEND wa_it_bdcdata TO it_bdcdata.
    CLEAR wa_it_bdcdata.
    wa_it_bdcdata-fnam = 'SO_BELNR-LOW'.
    wa_it_bdcdata-fval = BELNR.
    APPEND wa_it_bdcdata TO it_bdcdata.
    CLEAR wa_it_bdcdata.
    wa_it_bdcdata-fnam = 'BDC_OKCODE'.
    wa_it_bdcdata-fval = '=CRET'.
    APPEND wa_it_bdcdata TO it_bdcdata.
    opt-dismode = 'E'.
    CALL TRANSACTION 'MIR6' USING it_bdcdata OPTIONS FROM opt.
    Please Reply if any Issue,
    Best Regards,
    Faisal

  • What are the parameters in Call transaction method?

    Hi ABAPER'S,
        Please give me what are the parameters in call transaction method?
    Thanks,
    Prakash

    Processing batch input data with CALL TRANSACTION USING is the faster of the two recommended data transfer methods. In this method, legacy data is processed inline in your data transfer program.
    Syntax:
    CALL TRANSACTION <tcode>
    USING <bdc_tab>
    MODE  <mode>
    UPDATE  <update>
    <tcode> : Transaction code
    <bdc_tab> : Internal table of structure BDCDATA.
    <mode> : Display mode:
    A
    Display all
    E
    Display errors only
    N
    No display
    <update> : Update mode:
    S
    Synchronous
    A
    Asynchronous
    L
    Local update
    A program that uses CALL TRANSACTION USING to process legacy data should execute the following steps:
    Prepare a BDCDATA structure for the transaction that you wish to run.
    With a CALL TRANSACTION USING statement, call the transaction and prepare the BDCDATA structure. For example:
    CALL TRANSACTION 'TFCA' USING BDCDATA
    MODE 'A'
    UPDATE 'S'.
    MESSAGES INTO MESSTAB.
    IF SY-SUBRC <> 0.
    <Error_handling>.
    ENDIF.
    The MODE Parameter
    You can use the MODE parameter to specify whether data transfer processing should be displayed as it happens. You can choose between three modes:
    A Display all. All screens and the data that goes in them appear when you run your program.
    N No display. All screens are processed invisibly, regardless of whether there are errors or not. Control returns to your program as soon as transaction processing is finished.
    E Display errors only. The transaction goes into display mode as soon as an error in one of the screens is detected. You can then correct the error.
    The display modes are the same as those that are available for processing batch input sessions.
    The UPDATE Parameter
    You use the UPDATE parameter to specify how updates produced by a transaction should be processed. You can select between these modes:
    A Asynchronous updating. In this mode, the called transaction does not wait for any updates it produces to be completed. It simply passes the updates to the SAP update service. Asynchronous processing therefore usually results in faster execution of your data transfer program.
    Asynchronous processing is NOT recommended for processing any larger amount of data. This is because the called transaction receives no completion message from the update module in asynchronous updating. The calling data transfer program, in turn, cannot determine whether a called transaction ended with a successful update of the database or not.
    If you use asynchronous updating, then you will need to use the update management facility (Transaction SM12) to check whether updates have been terminated abnormally during session processing. Error analysis and recovery is less convenient than with synchronous updating.
    S Synchronous updating. In this mode, the called transaction waits for any updates that it produces to be completed. Execution is slower than with asynchronous updating because called transactions wait for updating to be completed. However, the called transaction is able to return any update error message that occurs to your program. It is much easier for you to analyze and recover from errors.
    L Local updating. If you update data locally, the update of the database will not be processed in a separate process, but in the process of the calling program. (See the ABAP keyword documentation on SET UPDATE TASK LOCAL for more information.)
    The MESSAGES Parameter
    The MESSAGES specification indicates that all system messages issued during a CALL TRANSACTION USING are written into the internal table <MESSTAB> . The internal table must have the structure BDCMSGCOLL .
    You can record the messages issued by Transaction TFCA in table MESSTAB with the following coding:
    (This example uses a flight connection that does not exist to trigger an error in the transaction.)
    DATA: BEGIN OF BDCDATA OCCURS 100.
    INCLUDE STRUCTURE BDCDATA.
    DATA: END OF BDCDATA.
    DATA: BEGIN OF MESSTAB OCCURS 10.
    INCLUDE STRUCTURE BDCMSGCOLL.
    DATA: END OF MESSTAB.
    BDCDATA-PROGRAM = 'SAPMTFCA'.
    BDCDATA-DYNPRO = '0100'.
    BDCDATA-DYNBEGIN = 'X'.
    APPEND BDCDATA.
    CLEAR BDCDATA.
    BDCDATA-FNAM = 'SFLIGHT-CARRID'.
    BDCDATA-FVAL = 'XX'.
    APPEND BDCDATA.
    BDCDATA-FNAM = 'SFLIGHT-CONNID'.
    BDCDATA-FVAL = '0400'.
    APPEND BDCDATA.
    CALL TRANSACTION 'TFCA' USING BDCDATA MODE 'N'
    MESSAGES INTO MESSTAB.
    LOOP AT MESSTAB.
    WRITE: / MESSTAB-TCODE,
    MESSTAB-DYNAME,
    MESSTAB-DYNUMB,
    MESSTAB-MSGTYP,
    MESSTAB-MSGSPRA,
    MESSTAB-MSGID,
    MESSTAB-MSGNR.
    ENDLOOP.
    The following figures show the return codes from CALL TRANSACTION USING and the system fields that contain message information from the called transaction. As the return code chart shows, return codes above 1000 are reserved for data transfer. If you use the MESSAGES INTO <table> option, then you do not need to query the system fields shown below; their contents are automatically written into the message table. You can loop over the message table to write out any messages that were entered into it.
    Return codes:
    Value
    Explanation
    0
    Successful
    <=1000
    Error in dialog program
    > 1000
    Batch input error
    System fields:
    Name:
    Explanation:
    SY-MSGID
    Message-ID
    SY-MSGTY
    Message type (E,I,W,S,A,X)
    SY-MSGNO
    Message number
    SY-MSGV1
    Message variable 1
    SY-MSGV2
    Message variable 2
    SY-MSGV3
    Message variable 3
    SY-MSGV4
    Message variable 4
    Error Analysis and Restart Capability
    Unlike batch input methods using sessions, CALL TRANSACTION USING processing does not provide any special handling for incorrect transactions. There is no restart capability for transactions that contain errors or produce update failures.
    You can handle incorrect transactions by using update mode S (synchronous updating) and checking the return code from CALL TRANSACTION USING. If the return code is anything other than 0, then you should do the following:
    write out or save the message table
    use the BDCDATA table that you generated for the CALL TRANSACTION USING to generate a batch input session for the faulty transaction. You can then analyze the faulty transaction and correct the error using the tools provided in the batch input management facility.

  • Error in Call Transaction

    Hi,
    Let me know why this issue is coming.
    I'M doing a bdc using call transaction and want to catch the error messages and throw back as alvoutput.
    my code is 
         PERFORM bdc_dynpro using 'X' 'SAPMV50A' '0101' '' ''.
         PERFORM bdc_dynpro using 'X' 'SAPMV50A' '4004' '' ''.
         PERFORM bdc_dynpro using '' '' '' 'LIKP-VBELN' wa_likp-vbeln.
         PERFORM bdc_dynpro using '' '' '' 'BDC_OKCODE' 'WABU_T'.
         CALL TRANSACTION 'VL02N'
                           USING itab_bdcdata
                            MODE lv_tmpmode
                            UPDATE 'S'
                            MESSAGES INTO itab_messages.
         IF sy-subrc NE 0.
            PERFORM messages.
         ENDIF.
    what the message that i'm getting in itab_messages is "
    Start screen does not exist in batch input data".
    please let me know why this error is coming.
    --sudha

    Hi,
    no need to call the screen num  101.
    4004 is the first screen number of the transaction code  vl02n.
    regards.
    sriram.

  • Initial Load Error - No generation performed. Call transaction GN_START

    Hi Folks,
    We are doing middleware configuration for data migration between R3->CRM.Have followed "Best Practies" configuration Guide.
    System Using; CRM 2007 and ECC6.0
    Issue
    While performing initial load, system is throwing the error as
    001- No generation performed. Call transaction GN_START
    002-Due to system errors the Load is prohibited (check transaction MW_CHECK)!
    After calling the transaction GN_START system asks for job scheduling,whereas I have already scheduled it.
    A job is already scheduled periodically.
    Clicking on 'Continue' will create another job
    that starts immediately.
    After checking(MW_CHECK),message is displayed as
    No generation performed. Call transaction GN_START.
    If anybody has encountered the similar issue and has resolved it,their guidence will be greatly appriciated.
    Thanks in Advance
    VEERA B

    Veera,
    We also faced the same problem when we have done the upgrade from CRM 4.0 to CRM 2007.
    For that you go to SMWP where you can see all the errors related to Middleware with the error message so try to remove the error,
    Also pls check in RZ20 and activate the middleware trace tree.
    Regards
    Vinod

  • Call Transaction in Web dynpro

    Hi friends ,
    how to call the sap transaction in web dynpro abap.
    I am using the function module
      CALL FUNCTION 'ABAP4_CALL_TRANSACTION '
        EXPORTING
          tcode                         =  'VA01'
    in web dynpro abap
    but i am getting error like  fill all the required filed
    please give suggestion.
    Regards ,
    krishnan R.

    Hi Krishnan,
    You cannot call a transaction from WebDynpro ABAP. You can instead create an transactional iView in the portal. Go through this link for further information.
    [http://help.sap.com/SAPHELP_NW04S/helpdata/EN/18/f96f4132f15c58e10000000a1550b0/frameset.htm|http://help.sap.com/SAPHELP_NW04S/helpdata/EN/18/f96f4132f15c58e10000000a1550b0/frameset.htm]
    There are already many similar threads over the issue of calling a transaction from WebDynpro ABAP. Please try run a search in the previous forum threads. Below are a few such threads:
    [https://forums.sdn.sap.com/click.jspa?searchID=18250003&messageID=5345700|https://forums.sdn.sap.com/click.jspa?searchID=18250003&messageID=5345700]
    [call Transaction thru WB4A.|call Transaction thru WB4A.]
    Regards,
    Uday

  • Call Transaction (BAPI) in ABAP Web Dynpro

    I'm developing a ABAP WD application which make use of a RFC BAPI. The BAPI will then use call transaction to perform certain operation on R3. 
    <b>CALL TRANSACTION 'IQS12' USING bdcdata MODE 'P'
      MESSAGES INTO itab.</b>
    It works fine when I tested it using TCode SE37. When the call transaction fails all error message is trapped inside the internal table.
    However when I run it using ABAP WD, it does not return the internal table but an error page on the portal. The error message was displayed on the portal page. I would like to handle the error message by my own. Is there any way doing this?
    Appreciate if anyone can sort this out for me. Thanks in advance.
    Ricky

    Hi,
    It's okie now. I have found out that this is a known issue and there's a SAP notes (935725) for that.
    According to the notes, call transaction with message type E will fail if the BAPI is executed through http.
    Thanks for replying. Appreciate that.
    Ricky

Maybe you are looking for