How to use Bespoke transaction in SRM Front end.

Hi All,
I am having a transaction ZPO_REPORT, I want to use this transaction in SRM Front End.
How can I do it?
Please advice.
Regards.
Pras

hi pras,
   sorry to ask once again. as per my understand from your questions.
   execute ur report program by SAP-GUI mode???
thank you,
Regards,
John.

Similar Messages

  • How to use OMJX transaction? Need to add an additional field on MIGO item

    hi guys
    we need to add a new field on the MIGO screen at the item level. We are trying to explore OMJX to add custom fields.
    We have used append structutre to enhance the GOITEM structure but are not clear on how to use OMJX.
    ANy idea how to use the transaction OMJX.
    Thanks in advance

    With the Business Add-In (BAdI) MB_MIGO_BADI, you can extend the              
    interface of the goods movements transaction (MIGO) with additional           
    tabstrip controls for the detailed information (detail tabstrips) and         
    header information (header tabstrips). It is possible for an external         
    application                                                                   
    o  to display an additional detail tabstrip with own subscreen (max. 10       
       lines) in MIGO                                                             
    o  to display an additional header tabstrip with own subscreen (max. 3        
       lines) in MIGO                                                                               
    The program name, screen number and tab page text can be determined           
    dynamically. Different screens can therefore be controlled according to       
    the mode (for example, change mode, display mode, goods receipt, goods        
    issue).                                                                               
    Pushbuttons                                                                   
    It is not possible to implement pushbuttons in the MIGO menu, but you         
    can, however, implement pushbuttons directly on the external subscreen.       
    The OK code from MIGO is forwarded to the external application so it can      
    react.                                                                               
    Cursor Control                                                                
    So that the cursor stays on the same subscreen after you press Continue,      
    if it was positioned there before, the external application in the own        
    PAI must hold the cursor positioning (on the same screen 'yes'/'no'; if       
    'yes', on which field), to set the cursor in PBO again.                                                                               
    Requirements                                                                               
    If you use the BAdI MB_MIGO_BADI in MIGO to update customer-own data, in      
    addition to the material document, to the database, you should note the       
    following:                                                                    
    o  The BAdI MB_MIGO_BADI is only active in transaction MIGO.                  
    o  If you post goods movements with other transactions (for example, with     
       MB01, MB1C, VL02N), you must ensure that customer data is also             
       updated, if necessary.                                                     
       You can do this by using the BAdI MB_DOCUMENT_BADI (Creating a             
       material document) to post the goods movements with the transactions       
       mentioned above.                                                           
    o  Note that otherwise, posting the goods movements will lead to              
       inconsistencies between SAP system data (for example, in stocks,           
       material documents, FI documents) and customer data.

  • ...how to use BATCHMAN transaction in Controlling?

    ...how to use BATCHMAN transaction in Controlling?...
    need to upload statistical keyfigure values from an Excel file, but do not know which should be the header row on Excel file.
    thank you.

    To access the Transfer of External Data function (transaction BATCHMAN), choose:
    Accounting ® Real Estate Management ® Controlling ® Actual Postings ® Transfer of External Data.
    For further information please check the following link:
    http://help.sap.com/saphelp_erp2005/helpdata/en/32/e7ee431feb6d45957a83e0179cbbff/frameset.htm
    regards,
    Lily

  • I Don't know how to use SBO Transaction Notification  procedure

    Hi all
    I don't know how to use SBO Transaction Notification  procedure
    can any body give me description why we use,where we use,how we use some example
    Awaiting soon reply
    Rajkumar G.

    example is for testing, if on delivery is filled ref no of vendor or not
    if @object_type = '20'  and (@transaction_type= 'A' or @transaction_type= 'U')
    begin
         if 1 = (select count(docentry) from opdn with(nolock) where docentry =@list_of_cols_val_tab_del and (numatcard is null or len(numatcard) = 0) )
         begin
              select @error =1
              select @error_message = 'vendor ref no isnt filled'
         end
    end
    next example is for creating BP as vendor and testing, if dont begin for specific sign
    if @object_type = '2' and @transaction_type= 'A'
    begin
    if left(@list_of_cols_val_tab_del, 1) = N'x' or left(@list_of_cols_val_tab_del, 1) = N'X'
         begin
              if 1 = (select count(cardcode) from ocrd where cardcode = @list_of_cols_val_tab_del and cardtype in ('S', N'S') )
                   begin
         select @error =1
              select @error_message = 'Vendor code cannot begin to X sign.'
    end
         end
    end
    is it clear?

  • Using MDMGX transaction in SRM 5.0

    Hi,
    I am not able to use MDMGX transaction in SRM 5.0 wherein says the transaction does not exists.
    The following are my component level.
    SAP_ABA     700     0009     SAPKA70009     Cross-Application Component
    SAP_BASIS     700     0009     SAPKB70009     SAP Basis Component
    PI_BASIS     2005_1_700     0009     SAPKIPYJ79     PI_BASIS 2005_1_700
    ST-PI     2005_1_700     0001     SAPKITLQI1     SAP Solution Tools Plug-In
    SAP_BW     700     0009     SAPKW70009     SAP NetWeaver BI 7.0
    SAP_AP     700     0006     SAPKNA7006     SAP Application Platform
    CCM     200_700     0007     SAPK-27007INCCM     CCM 200_700 : Add-On Installation
    SRM_PLUS     550     0006     SAPKIBK006     SRM_PLUS for mySAP SRM
    SRM_SERVER     550     0006     SAPKIBKT06     SRM_SERVER
    Is there any note application or any patches to upload for making the transaction available?
    Regards,
    Radeesh Velayudhan

    Hello Radeesh
    You will have apply the latest support Package fo r
    PI_BASIS     2005_1_700     0012     SAPKIPYJ7C     PI_BASIS 2005_1_700
    Then you can get this transaction.
    Reward points if this is useful
    Thanks and Regards
    Pushkar

  • How to get name of table from front end

    Hi,
    How to get name of table from front end in EBS 11i?
    thanx
    Ashish

    Hi
    Sandeep is correct. The "Help"/"Record History" will give you the table/view name, but sometimes this particular menu function give me a "Record History is not available here." error message.
    I then use the following menu functions (this will also give you additional information, like column details).
    1) Open Forms
    2) Click on Help/Diagnostics/Examine (*you might have to enter the APPS password at this point)
    3) Change "Block" to "System"
    4) Change "Field" to "Last_query"
    The system will populate the "Value" field with the query that was executed in order to populate the form.
    Regards
    Frank

  • SRM front end details needed

    Hi,
       I am facing issues with SRM front end. Can anyone provide me oSS notes, Help files and documents. Points will be rewarded to replies.
    Regards,
    Munavar

    When I go to through Some of the transaction in the SRM in one of the fields Storage location appears as pull down menu. The values appears in this order
    TR01
    SH10
    SH09
    SH01
    Whereas most of the materials are maintained for SH01. User they don't see this field in urgency. They want this in ascending order rather in descending order.
    Apart from this I need to know some Oss notes or else help files to support front end issues.
    Thanks
    Regards,
    Munavar

  • How to enable Translation icon in forms front end

    Hi All,
    How to enable Translation icon in forms front end (EBusiness) ?
    let me know the steps to follow to enable this icon?
    I want to know exactly what is the purpose of this Translation Icon and how it works? If there are any links Please provide the links?
    will this help to display the items long description in other languages?
    Regards,
    Durga Srinivas

    What is your application release?
    How to enable Translation icon in forms front end (EBusiness) ?
    let me know the steps to follow to enable this icon?
    I want to know exactly what is the purpose of this Translation Icon and how it works? If there are any links Please provide the links?
    will this help to display the items long description in other languages?Please see these docs.
    Customizing Translation in Oracle E-Business Suite - R12 [ID 1382124.1]
    Using Lightweight MLS With Oracle E-Business Suite Release 12.1.3 [ID 1077709.1]
    Oracle Applications 11i Internationalization Guide [ID 333785.1]
    Thanks,
    Hussein

  • R/3 Screen appearing in SRM Front End

    Dear All,
    We are working on SRM 5.00. I have noticed that at times, we face a problem with the SRM front end.
    On logging in through the web and clicking on any button, the screen takes me to the R/3 screen with the button 'Start SAP Easy Access'. On clicking this button, it goes to the SAP menu just like R/3. And all this happens on the web browser.
    Anyone have any idea why this happens?
    Thanks for your help.
    Good day.
    Johnson

    Hi
    Check your  SRMlogical system is correct and make ensure that your logical system is assigned to your client only via scc4.
    I had this issue in sandboxes.
    BR
    Muthu
    Edited by: Muthuraman Govindasamy on Oct 14, 2008 1:12 PM

  • Why can't I use Signal Express as a Front End to my LV application?

    Why not make an API for Signal Express so I can use its
    functionality as a front-end to my LV
    applications.
    It is very powerful and user friendly so why have LV developers recreate
    the wheel? Give an interface to access a SE project via LV
    to get data and pass results into LV
    so we can then use its power to make quicker more user friendly applications.
    SE could run in the background as the analyzer and the LV application call SE to get the portions of
    the data it needs.
    Even an automatic VI compiler on SAVE would be a start so a user
    could edit a project in SE close it and it would compile the VI which the LV program calls.
    LabVIEW developers typically do not have 6-18months to
    design and perfect a powerful user friendly interface and are stuck using MAX
    and its inadequacies which is much less impressive.

    Arron,
    I agree that it would be a good idea to include this functionality and have filed a product suggestion.  To file a suggestion, you can go to www.ni.com/contact and click on the link in the lower left hand corner for product feedback.  Thanks for letting us know!
    Regards,
    Craig D
    Applications Engineer
    National Instruments

  • How to use multiple transactions

    hi experts,
    1.how to handle multiple transactions in call transaction and session method.
    2.is it possible to handle multiple transactions in call transaction method.
    3.can plz send how handle multiple transactions in session method.
    thanks in addvance

    hi,
    Go through this program.
    REPORT zra_gl_cr NO STANDARD PAGE HEADING LINE-SIZE 255.
    TYPE-POOLS: truxs.
    DATA: it_raw TYPE truxs_t_text_data.
    DATA:messtab1 LIKE bdcmsgcoll OCCURS 0 WITH HEADER LINE.
    DATA:messtab LIKE bdcmsgcoll OCCURS 0 WITH HEADER LINE.
    DATA: bdcdata LIKE bdcdata OCCURS 0 WITH HEADER LINE.
    DATA: BEGIN OF i_mess OCCURS 0,
    l_mstring(480),
    msgnr(5),
    msgv1(15),
    END OF i_mess.
    DATA:i_mess1 LIKE i_mess OCCURS 0 WITH HEADER LINE.
    DATA: l_mstring(480),l_mstring1(480).
    DATA: BEGIN OF it_itab OCCURS 0,
    saknr(10), "G/L a/c number.
    bukrs(4), "Company Code.
    ktoks(4), "G/L a/c group.
    xplacct(1), "P&L statement account.
    xbilk(1), "Balance sheet account.
    txt20_ml(20), "G/L a/c short text.
    txt50_ml(50), "G/L a/c long text.
    waers(5), "Account currency.
    MWSKZ(2),
    mitkz(1), "Reconciliation a/c for a/c type.
    xopvw(1), "Open item management
    xkres(1), "Line item display.
    zuawa(3), "Sort Key.
    fstag(4), "Field status group.
    xintb(1), "Post automatically only.
    hbkid(5), "House bank.
    hktid(5), "Account id.
    vzskz(2), "Interest indicator
    END OF it_itab.
    DATA: hdate LIKE sy-datum.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 5(15) text-103. " FOR FIELD P_FILE1.
    SELECTION-SCREEN POSITION 25.
    PARAMETERS : p_file1 LIKE rlgrap-filename.
    SELECTION-SCREEN END OF LINE.
    INITIALIZATION.
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file1.
    Perform file_selection will help to select the location of the file
    PERFORM file_selection.
    START-OF-SELECTION.
    Perform data_upload will help to upload the data from the flat file
    to the internal table.
    PERFORM data_upload.
    PERFORM open_group.
    Peform bdc_upload will help to upload the data from the internal
    table into its respective fields.
    PERFORM bdc_fspo.
    PERFORM bdc_upload.
    PERFORM exp_log.
    PERFORM close_group.
    Perform display_log will prepare a log for the data that has been
    uploaded
    PERFORM display_log.
    END-OF-SELECTION.
    FORM file_selection .
    CALL FUNCTION 'WS_FILENAME_GET'
    EXPORTING
    def_filename = ' '
    def_path = 'C:\'
    mask = ',.txt,.xls.'
    mode = 'O'
    title = 'Open a excel file'
    IMPORTING
    filename = p_file1
    EXCEPTIONS
    inv_winsys = 1
    no_batch = 2
    selection_cancel = 3
    selection_error = 4
    OTHERS = 5.
    ENDFORM. " file_selection
    FORM data_upload .
    CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'
    EXPORTING
    I_FIELD_SEPERATOR =
    i_line_header = 'X'
    i_tab_raw_data = it_raw
    i_filename = p_file1
    TABLES
    i_tab_converted_data = it_itab
    EXCEPTIONS
    conversion_failed = 1
    OTHERS = 2.
    IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
    WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    ENDIF.
    ENDFORM. " data_upload
    FORM bdc_upload .
    LOOP AT it_itab.
    perform bdc_dynpro using 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    perform bdc_field using 'BDC_OKCODE'
    '=ACC_CRE'.
    perform bdc_field using 'BDC_CURSOR'
    'GLACCOUNT_SCREEN_KEY-SAKNR'.
    perform bdc_field using 'GLACCOUNT_SCREEN_KEY-SAKNR'
    it_itab-SAKNR.
    perform bdc_field using 'GLACCOUNT_SCREEN_KEY-BUKRS'
    it_itab-BUKRS.
    perform bdc_dynpro using 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    perform bdc_field using 'BDC_OKCODE'
    '=2102_GROUP'.
    perform bdc_field using 'BDC_CURSOR'
    'GLACCOUNT_SCREEN_COA-KTOKS'.
    perform bdc_field using 'GLACCOUNT_SCREEN_COA-KTOKS'
    it_itab-KTOKS.
    perform bdc_field using 'GLACCOUNT_SCREEN_COA-XPLACCT'
    it_itab-XPLACCT.
    perform bdc_dynpro using 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    perform bdc_field using 'BDC_OKCODE'
    '=2102_BS_PL'.
    perform bdc_field using 'BDC_CURSOR'
    'GLACCOUNT_SCREEN_COA-XBILK'.
    perform bdc_field using 'GLACCOUNT_SCREEN_COA-KTOKS'
    it_itab-KTOKS.
    perform bdc_field using 'GLACCOUNT_SCREEN_COA-XPLACCT'
    it_itab-XPLACCT.
    perform bdc_field using 'GLACCOUNT_SCREEN_COA-XBILK'
    it_itab-XBILK.
    perform bdc_dynpro using 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    perform bdc_field using 'BDC_OKCODE'
    '=ENTER'.
    perform bdc_field using 'GLACCOUNT_SCREEN_COA-KTOKS'
    it_itab-KTOKS.
    perform bdc_field using 'GLACCOUNT_SCREEN_COA-XBILK'
    it_itab-XBILK.
    perform bdc_field using 'GLACCOUNT_SCREEN_COA-TXT20_ML'
    it_itab-TXT20_ML.
    perform bdc_field using 'GLACCOUNT_SCREEN_COA-TXT50_ML'
    it_itab-TXT50_ML.
    perform bdc_field using 'BDC_CURSOR'
    'GLACCOUNT_SCREEN_COA-BILKT'.
    perform bdc_field using 'GLACCOUNT_SCREEN_COA-BILKT'
    it_itab-saknr.
    PERFORM bdc_dynpro USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    PERFORM bdc_field USING 'BDC_OKCODE'
    '=TAB02'.
    PERFORM bdc_field USING 'BDC_CURSOR'
    'GLACCOUNT_SCREEN_COA-KTOKS'.
    PERFORM bdc_field USING 'GLACCOUNT_SCREEN_COA-KTOKS'
    it_itab-ktoks.
    PERFORM bdc_field USING 'GLACCOUNT_SCREEN_COA-TXT20_ML'
    it_itab-txt20_ml.
    PERFORM bdc_field USING 'GLACCOUNT_SCREEN_COA-TXT50_ML'
    it_itab-txt50_ml.
    perform bdc_field using 'BDC_CURSOR'
    'GLACCOUNT_SCREEN_COA-BILKT'.
    perform bdc_field using 'GLACCOUNT_SCREEN_COA-BILKT'
    it_itab-saknr.
    perform bdc_dynpro using 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    perform bdc_field using 'BDC_OKCODE'
    '=TAB02'.
    perform bdc_field using 'BDC_CURSOR'
    'GLACCOUNT_SCREEN_COA-KTOKS'.
    perform bdc_field using 'GLACCOUNT_SCREEN_COA-KTOKS'
    it_itab-KTOKS.
    perform bdc_field using 'BDC_CURSOR'
    'GLACCOUNT_SCREEN_COA-KTOKS'.
    perform bdc_field using 'GLACCOUNT_SCREEN_COA-KTOKS'
    it_itab-KTOKS.
    perform bdc_field using 'GLACCOUNT_SCREEN_COA-XBILK'
    it_itab-XBILK.
    perform bdc_field using 'GLACCOUNT_SCREEN_COA-TXT20_ML'
    it_itab-TXT20_ML.
    perform bdc_field using 'GLACCOUNT_SCREEN_COA-TXT50_ML'
    it_itab-TXT50_ML.
    perform bdc_field using 'GLACCOUNT_SCREEN_COA-BILKT'
    it_itab-saknr.
    perform bdc_dynpro using 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    perform bdc_field using 'BDC_OKCODE'
    '=ENTER'.
    perform bdc_field using 'GLACCOUNT_SCREEN_CCODE-WAERS'
    it_itab-waers.
    perform bdc_field using 'GLACCOUNT_SCREEN_CCODE-MWSKZ'
    it_itab-MWSKZ.
    perform bdc_field using 'GLACCOUNT_SCREEN_CCODE-MITKZ'
    it_itab-mitkz.
    perform bdc_field using 'BDC_CURSOR'
    'GLACCOUNT_SCREEN_CCODE-XOPVW'.
    perform bdc_field using 'GLACCOUNT_SCREEN_CCODE-XOPVW'
    it_itab-XOPVW.
    perform bdc_field using 'GLACCOUNT_SCREEN_CCODE-XKRES'
    it_itab-XKRES.
    perform bdc_field using 'GLACCOUNT_SCREEN_CCODE-ZUAWA'
    it_itab-ZUAWA.
    PERFORM bdc_field USING 'GLACCOUNT_SCREEN_COA-XPLACCT'
    it_itab-xplacct.
    PERFORM bdc_field USING 'GLACCOUNT_SCREEN_COA-XBILK'
    it_itab-xbilk.
    IF it_itab-xbilk = 'X'.
    PERFORM bdc_dynpro USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    PERFORM bdc_field USING 'BDC_OKCODE'
    '=TAB03'.
    PERFORM bdc_field USING 'BDC_CURSOR'
    'GLACCOUNT_SCREEN_CCODE-WAERS'.
    PERFORM bdc_field USING 'GLACCOUNT_SCREEN_CCODE-WAERS'
    it_itab-waers.
    PERFORM bdc_field USING 'GLACCOUNT_SCREEN_CCODE-XOPVW'
    it_itab-xopvw.
    PERFORM bdc_field USING 'GLACCOUNT_SCREEN_CCODE-MITKZ'
    it_itab-mitkz.
    ENDIF.
    PERFORM bdc_field USING 'GLACCOUNT_SCREEN_CCODE-XKRES'
    it_itab-xkres.
    PERFORM bdc_field USING 'GLACCOUNT_SCREEN_CCODE-ZUAWA'
    it_itab-zuawa.
    PERFORM bdc_dynpro USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    PERFORM bdc_field USING 'BDC_OKCODE'
    '=SAVE'.
    PERFORM bdc_field USING 'BDC_CURSOR'
    'GLACCOUNT_SCREEN_CCODE-FSTAG'.
    PERFORM bdc_field USING 'GLACCOUNT_SCREEN_CCODE-FSTAG'
    it_itab-fstag.
    PERFORM bdc_field USING 'GLACCOUNT_SCREEN_CCODE-XINTB'
    it_itab-xintb.
    PERFORM bdc_field USING 'GLACCOUNT_SCREEN_CCODE-HBKID'
    it_itab-hbkid.
    PERFORM bdc_field USING 'GLACCOUNT_SCREEN_CCODE-HKTID'
    it_itab-hktid.
    PERFORM bdc_field USING 'GLACCOUNT_SCREEN_CCODE-VZSKZ'
    it_itab-vzskz.
    perform bdc_dynpro using 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    perform bdc_field using 'BDC_OKCODE'
    '=TAB03'.
    perform bdc_field using 'BDC_CURSOR'
    'GLACCOUNT_SCREEN_CCODE-WAERS'.
    perform bdc_field using 'GLACCOUNT_SCREEN_CCODE-WAERS'
    it_itab-WAERS.
    perform bdc_field using 'GLACCOUNT_SCREEN_CCODE-MWSKZ'
    it_itab-MWSKZ.
    perform bdc_field using 'GLACCOUNT_SCREEN_CCODE-MITKZ'
    it_itab-MITKZ.
    perform bdc_field using 'GLACCOUNT_SCREEN_CCODE-ZUAWA'
    it_itab-ZUAWA.
    perform bdc_dynpro using 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    perform bdc_field using 'BDC_OKCODE'
    '=ENTER'.
    perform bdc_field using 'BDC_CURSOR'
    'GLACCOUNT_SCREEN_CCODE-FSTAG'.
    perform bdc_field using 'GLACCOUNT_SCREEN_CCODE-FSTAG'
    it_itab-FSTAG.
    perform bdc_dynpro using 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    perform bdc_field using 'BDC_OKCODE'
    '=SAVE'.
    perform bdc_field using 'BDC_CURSOR'
    'GLACCOUNT_SCREEN_CCODE-FSTAG'.
    perform bdc_field using 'GLACCOUNT_SCREEN_CCODE-FSTAG'
    it_itab-FSTAG.
    PERFORM bdc_transaction USING 'FS00'.
    CALL TRANSACTION 'FS00' USING bdcdata MODE 'A'
    UPDATE 'S'
    MESSAGES INTO messtab1.
    PERFORM mess1.
    REFRESH bdcdata[].
    ENDLOOP.
    ENDFORM. " bdc_upload
    FORM bdc_fspo .
    LOOP AT it_itab.
    PERFORM bdc_dynpro USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    PERFORM bdc_field USING 'BDC_OKCODE'
    '=ACC_CRE'.
    PERFORM bdc_field USING 'BDC_CURSOR'
    'GLACCOUNT_SCREEN_KEY-SAKNR'.
    PERFORM bdc_field USING 'GLACCOUNT_SCREEN_KEY-SAKNR'
    it_itab-saknr.
    PERFORM bdc_field USING 'GLACCOUNT_SCREEN_KEY-KTOPL'
    '1000'.
    PERFORM bdc_dynpro USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    PERFORM bdc_field USING 'BDC_OKCODE'
    '=2102_GROUP'.
    PERFORM bdc_field USING 'BDC_CURSOR'
    'GLACCOUNT_SCREEN_COA-KTOKS'.
    PERFORM bdc_field USING 'GLACCOUNT_SCREEN_COA-KTOKS'
    it_itab-ktoks.
    PERFORM bdc_field USING 'GLACCOUNT_SCREEN_COA-XPLACCT'
    it_itab-xplacct.
    PERFORM bdc_field USING 'GLACCOUNT_SCREEN_COA-XBILK'
    it_itab-xbilk.
    PERFORM bdc_dynpro USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    PERFORM bdc_field USING 'BDC_OKCODE'
    '=SAVE'.
    PERFORM bdc_field USING 'GLACCOUNT_SCREEN_COA-KTOKS'
    it_itab-ktoks.
    PERFORM bdc_field USING 'GLACCOUNT_SCREEN_COA-XPLACCT'
    it_itab-xplacct.
    PERFORM bdc_field USING 'BDC_CURSOR'
    'GLACCOUNT_SCREEN_COA-TXT50_ML'.
    PERFORM bdc_field USING 'GLACCOUNT_SCREEN_COA-TXT20_ML'
    it_itab-txt20_ml.
    PERFORM bdc_field USING 'GLACCOUNT_SCREEN_COA-TXT50_ML'
    it_itab-txt50_ml.
    *perform bdc_transaction using 'FSP0'.
    CALL TRANSACTION 'FSP0' USING bdcdata MODE 'A'
    UPDATE 'S'
    MESSAGES INTO messtab.
    PERFORM mess.
    REFRESH bdcdata[].
    ENDLOOP.
    ENDFORM. " bdc_fspo
    FORM mess . "fsp0
    LOOP AT messtab.
    CALL FUNCTION 'FORMAT_MESSAGE'
    EXPORTING
    id = messtab-msgid
    lang = messtab-msgspra
    no = messtab-msgnr
    v1 = messtab-msgv1
    v2 = messtab-msgv2
    v3 = messtab-msgv3
    v4 = messtab-msgv4
    IMPORTING
    msg = l_mstring
    EXCEPTIONS
    not_found = 1
    OTHERS = 2.
    CONDENSE l_mstring.
    i_mess1-l_mstring = l_mstring(250).
    i_mess1-msgnr = messtab1-msgnr.
    i_mess1-msgv1 = messtab1-msgv1.
    APPEND i_mess1.
    ENDLOOP.
    ENDFORM. " mess
    FORM mess1 . "fs00
    LOOP AT messtab1.
    CALL FUNCTION 'FORMAT_MESSAGE'
    EXPORTING
    id = messtab1-msgid
    lang = messtab1-msgspra
    no = messtab1-msgnr
    v1 = messtab1-msgv1
    v2 = messtab1-msgv2
    v3 = messtab1-msgv3
    v4 = messtab1-msgv4
    IMPORTING
    msg = l_mstring1
    EXCEPTIONS
    not_found = 1
    OTHERS = 2.
    CONDENSE l_mstring1.
    i_mess-l_mstring = l_mstring1(250).
    i_mess-msgnr = messtab1-msgnr.
    i_mess-msgv1 = messtab1-msgv1.
    APPEND i_mess.
    ENDLOOP.
    ENDFORM. " mess1
    FORM exp_log .
    CALL FUNCTION 'GUI_DOWNLOAD'
    EXPORTING
    filename = 'c:\temp\error_fsp0.txt'
    filetype = 'DAT'
    TABLES
    data_tab = i_mess1.
    CALL FUNCTION 'GUI_DOWNLOAD'
    EXPORTING
    filename = 'c:\temp\error_fs00.txt'
    filetype = 'DAT'
    TABLES
    data_tab = i_mess.
    ENDFORM. " exp_log
    FORM bdc_dynpro USING program dynpro.
    CLEAR bdcdata.
    bdcdata-program = program.
    bdcdata-dynpro = dynpro.
    bdcdata-dynbegin = 'X'.
    APPEND bdcdata.
    ENDFORM. "BDC_DYNPRO
    FORM bdc_field USING fnam fval.
    CLEAR bdcdata.
    bdcdata-fnam = fnam.
    bdcdata-fval = fval.
    APPEND bdcdata.
    ENDFORM. "BDC_Field
    Rewards points.
    Rgds,
    P.Nag

  • How to use Z transaction type while in the Transaction launcher Wizard?

    In SPRO->CRM->Transactions->Basic Settings->Define transaction Types I can see a whole host of Z transaction types.
    These define all sorts of business transaction defaults. Within the Transaction launcher Wizard there is a Transaction Type that can be entered, but I can only see three options, being 'BOR Transaction', 'URL Transaction' and ' M', for some reason. None of the transaction types shown in the above SPRO path are displayed.
    Does anyone know how I can use my Z transation type. These are used by the config behind the Action Boxes for the Winclient IC, but I can not get the Transaction launcher wizard to see or use these. The SAP How-to Guide to tha Transaction Launcher says that only BOR and URL Transactions can be used (unless you have IS-U). If this is true then how does one provide all the information provided by the Transaction type. The whole idea of the transaction type is default this information in one area.
    Anyone.
    Jason

    I think it is possible.
    In CRMC_UI_NBLINKS if you look at the logical links you can see that SRV-ORD-DC has a Parameter of 'SRVO' with a certain Parameter Class.
    If you were to check SPRO->CRM->Transactions_Basic Settings->Transaction Types  you will see that SRVO exists as an entry. This logical ink is therefore using this Transaction type to extract characteristics etc.
    Having said that, I need to call the sales order create with a certain transaction type, so I copied SLS-SLO-CR to a Z copy, added the Parameter of 'Z111' and also used the Parameter class of CL_CRM_UIU_BT_PARAM_CREATE.
    This should now, in theory all work, and show the exact same transaction in the Webclient IC as it does in the Winclient IC as they are both using the same Transaction type. However, the Webclient transaction looks different in terms of fields etc., so I don't think it's working. after all.
    Jason

  • Example on how to use the NI "saving a front panel img to file" on a prog.

    New to the labview program - I'm trying to save the front panel of the displayed output to file. I downloaded "Panel_Image_to_File.zip" from the NI site. But I'm having problem using the code to our program so as to save the image as a jpeg.
    A simple example on how to use the code or any other code that will be able to save the front panel to a specified folder will be great.

    All you should need is an invoke node of VI class and the the method Get Panel Image. Wire the Image Data output to the Write JPEG File on the Graphics & Sound>Graphics Formats palette. The Invoke Node is on the application Control palette. When it's on the diagram, right click and select Class>VI Server>VI. Right click on it again and select Methods>Get Panel Image.
    Attachments:
    Save to jpg.jpg ‏10 KB

  • How to use Call Transaction in AVL ........ for va02

    Hi Experts,
    I am using CALL TRANSACTION in ALV for VA02, but I want to go on item number. The following form i have used and it is working but I want to go on perticular item number in va02. pl. guide me.
    FORM user_command USING r_ucomm LIKE sy-ucomm
                      rs_selfield TYPE slis_selfield.
      CASE r_ucomm.
        WHEN '&IC1'.
        IF rs_selfield-fieldname = 'VBELN'.
          READ TABLE it_out INTO wa_itab INDEX rs_selfield-tabindex.
          SET PARAMETER ID : 'AUN' FIELD wa_itab-vbeln .
                           'APO' FIELD wa_itab-posnr.
          CALL TRANSACTION 'VA02' AND SKIP FIRST SCREEN.
        ENDIF.
      ENDCASE.
    ENDFORM.
    *=====================================
    Yusuf

    Hi,
    use BDC for that....
    check out the BDC part of coding for it.
    REFRESH  itab_bdcdata.
      CLEAR    itab_bdcdata.
    *initial screen
      PERFORM bdc_dynpro      USING 'SAPMV45A'
                                    '0102'.
      PERFORM bdc_field       USING 'BDC_CURSOR'
                                    'VBAK-VBELN'.
      PERFORM bdc_field       USING 'BDC_OKCODE'
                                    '/00'.
      PERFORM bdc_field       USING 'VBAK-VBELN'
                          <b>          g_t_atpma4-vbeln.</b>
    *item overview screen
      PERFORM bdc_dynpro      USING 'SAPMV45A'
                                    '4001'.
      PERFORM bdc_field       USING 'BDC_OKCODE'
                                    '=POPO'.
      PERFORM bdc_field       USING 'BDC_CURSOR'
                                    'RV45A-MABNR(04)'.
    *popup screen (move item to top)
      PERFORM bdc_dynpro      USING 'SAPMV45A'
                                    '0251'.
      PERFORM bdc_field       USING 'BDC_CURSOR'
                                    'RV45A-POSNR'.
      PERFORM bdc_field       USING 'BDC_OKCODE'
                                    '=POSI'.
      PERFORM bdc_field       USING 'RV45A-POSNR'
                                    <b>g_t_atpma4-posnr.</b>
    *item overview screen
      PERFORM bdc_dynpro      USING 'SAPMV45A'
                                    '4001'.
      PERFORM bdc_field       USING 'BDC_OKCODE'
                                    '/00'.
      PERFORM bdc_field       USING 'BDC_CURSOR'
                                    'VBAP-POSNR(01)'.
      PERFORM bdc_field       USING 'RV45A-VBAP_SELKZ(01)'
                                    'X'.
    *Call transaction VA02
      CALL TRANSACTION 'VA02'  USING itab_bdcdata
                               MODE 'E'
                               UPDATE 'A'
                               MESSAGES INTO itab_bdcmsg.
    Patil

  • How to use call transaction 'XD03' in abap.

    Hi Experts,
    I am  use call transaction xd03 in programme but when i click on any customer number the transaction xd03 is called and it show only one customer details. i.e 1 st  in row . other customer details not show. so please write code to solved my problems

    Hi
    It's not clear where you set the USER_COMMAND routine and where you set the OK_CODE for doubleclick.
    I suppose you set the routine in the importing parameter I_CALLBACK_USER_COMMAND (?) becasue you aren't use the parameter for the event, but for OK_CODE?
    Remember the OK_CODE should be upper case:
    FORM USER_COMMAND USING R_UCOMM LIKE SY-UCOMM
    RS_SELFIELD TYPE SLIS_SELFIELD.
    CASE R_UCOMM.
    "WHEN 'kunnr'.   <--------------- UPPER CASE
      WHEN 'KUNNR'.
    See my sample:
    TYPE-POOLS SLIS.
    DATA: BEGIN OF GT_FINAL OCCURS 0,
            KUNNR LIKE KNA1-KUNNR,
            NAME1 LIKE KNA1-NAME1,
          END OF GT_FINAL.
    * ALV
    DATA: GT_FIELDCAT   TYPE SLIS_T_FIELDCAT_ALV,
          GT_LAYOUT     TYPE SLIS_LAYOUT_ALV,
          GT_REPID    LIKE SY-REPID.
    START-OF-SELECTION.
      SELECT KUNNR NAME1 INTO TABLE GT_FINAL
         UP TO 20 ROWS
           FROM KNA1.
      GT_REPID = SY-REPID.
      CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
        EXPORTING
          I_PROGRAM_NAME     = GT_REPID
          I_INTERNAL_TABNAME = 'GT_FINAL'
          I_INCLNAME         = GT_REPID
        CHANGING
          CT_FIELDCAT        = GT_FIELDCAT[].
      GT_LAYOUT-F2CODE = 'KUNNR'.
      CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
        EXPORTING
          I_CALLBACK_PROGRAM      = GT_REPID
          I_CALLBACK_USER_COMMAND = 'USER_COMMAND'
          IS_LAYOUT               = GT_LAYOUT
          IT_FIELDCAT             = GT_FIELDCAT
        TABLES
          T_OUTTAB                = GT_FINAL.
    FORM USER_COMMAND USING R_UCOMM LIKE SY-UCOMM
                            RS_SELFIELD TYPE SLIS_SELFIELD.
      DATA: GWA_FINAL LIKE GT_FINAL.
      CASE R_UCOMM.
        WHEN 'KUNNR'.
          READ TABLE GT_FINAL INTO GWA_FINAL INDEX RS_SELFIELD-TABINDEX.
          IF SY-SUBRC = 0.
            SET PARAMETER ID 'KUN' FIELD GWA_FINAL-KUNNR.
            CALL TRANSACTION 'XD03' AND SKIP FIRST SCREEN.
          ENDIF.
      ENDCASE.
    ENDFORM.TYPE-POOLS SLIS.
    DATA: BEGIN OF GT_FINAL OCCURS 0,
            KUNNR LIKE KNA1-KUNNR,
            NAME1 LIKE KNA1-NAME1,
          END OF GT_FINAL.
    * ALV
    DATA: GT_FIELDCAT   TYPE SLIS_T_FIELDCAT_ALV,
          GT_LAYOUT     TYPE SLIS_LAYOUT_ALV,
          GT_REPID    LIKE SY-REPID.
    DATA: FL_INPUT_OFF.
    START-OF-SELECTION.
      SELECT KUNNR NAME1 INTO TABLE GT_FINAL
         UP TO 20 ROWS
           FROM KNA1.
      GT_REPID = SY-REPID.
      CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
        EXPORTING
          I_PROGRAM_NAME     = GT_REPID
          I_INTERNAL_TABNAME = 'GT_FINAL'
          I_INCLNAME         = GT_REPID
        CHANGING
          CT_FIELDCAT        = GT_FIELDCAT[].
      GT_LAYOUT-F2CODE = 'KUNNR'.
      CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
        EXPORTING
          I_CALLBACK_PROGRAM      = GT_REPID
          I_CALLBACK_USER_COMMAND = 'USER_COMMAND'
          IS_LAYOUT               = GT_LAYOUT
          IT_FIELDCAT             = GT_FIELDCAT
        TABLES
          T_OUTTAB                = GT_FINAL.
    FORM USER_COMMAND USING R_UCOMM LIKE SY-UCOMM
                            RS_SELFIELD TYPE SLIS_SELFIELD.
      DATA: GWA_FINAL LIKE GT_FINAL.
      CASE R_UCOMM.
        WHEN 'KUNNR'.
          READ TABLE GT_FINAL INTO GWA_FINAL INDEX RS_SELFIELD-TABINDEX.
          IF SY-SUBRC = 0.
            SET PARAMETER ID 'KUN' FIELD GWA_FINAL-KUNNR.
            CALL TRANSACTION 'XD03' AND SKIP FIRST SCREEN.
          ENDIF.
      ENDCASE.
    ENDFORM.  TYPE-POOLS SLIS.
    DATA: BEGIN OF GT_FINAL OCCURS 0,
            KUNNR LIKE KNA1-KUNNR,
            NAME1 LIKE KNA1-NAME1,
          END OF GT_FINAL.
    * ALV
    DATA: GT_FIELDCAT   TYPE SLIS_T_FIELDCAT_ALV,
          GT_LAYOUT     TYPE SLIS_LAYOUT_ALV,
          GT_REPID    LIKE SY-REPID.
    DATA: FL_INPUT_OFF.
    START-OF-SELECTION.
      SELECT KUNNR NAME1 INTO TABLE GT_FINAL
         UP TO 20 ROWS
           FROM KNA1.
      GT_REPID = SY-REPID.
      CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
        EXPORTING
          I_PROGRAM_NAME     = GT_REPID
          I_INTERNAL_TABNAME = 'GT_FINAL'
          I_INCLNAME         = GT_REPID
        CHANGING
          CT_FIELDCAT        = GT_FIELDCAT[].
      GT_LAYOUT-F2CODE = 'KUNNR'.
      CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
        EXPORTING
          I_CALLBACK_PROGRAM      = GT_REPID
          I_CALLBACK_USER_COMMAND = 'USER_COMMAND'
          IS_LAYOUT               = GT_LAYOUT
          IT_FIELDCAT             = GT_FIELDCAT
        TABLES
          T_OUTTAB                = GT_FINAL.
    FORM USER_COMMAND USING R_UCOMM LIKE SY-UCOMM
                            RS_SELFIELD TYPE SLIS_SELFIELD.
      DATA: GWA_FINAL LIKE GT_FINAL.
      CASE R_UCOMM.
        WHEN 'KUNNR'.
          READ TABLE GT_FINAL INTO GWA_FINAL INDEX RS_SELFIELD-TABINDEX.
          IF SY-SUBRC = 0.
            SET PARAMETER ID 'KUN' FIELD GWA_FINAL-KUNNR.
            CALL TRANSACTION 'XD03' AND SKIP FIRST SCREEN.
          ENDIF.
      ENDCASE.
    ENDFORM.
    Max

Maybe you are looking for