• Exporting/Importing More Than One Parameters To/From Memory ID

    To export more than one parameters (internal table, variable, structures) to Memory ID, please use the following code:

    EXPORT
    lt_tab1 FROM lt_table1
    lt_tab2 FROM lt_table2
    lv_var1 FROM lv_variable1
    TO MEMORY ID \'MEMORY_ID\'.

    To import more than one parameters (internal table, variable, structures) from Memory ID, please use the following code:

    IMPORT
    lt_tab1 TO lt_table1
    lt_tab2 TO lt_table2
    lv_var1 TO lv_variable1
    FROM MEMORY ID lc_memo_id1.

    Please note that it is not necessary to declare \’lt_tab1, lt_tab2 and lv_var1\’, this is used just as a reference from the importing program. Using this technique, the name of the importing table does not need to have the same name of the exporting table.

  • SAP Signature Theme With Colors in SAP Logon 7.30

    The new version of SAP Logon 7.30 is out which comes with a new modern SAP Signature Theme. The new modern SAP Signature theme comes with a palette of different colours, allowing users to change the theme colour in different environment. This option was not available in the previous version of the signature theme.

    \"SAP

     

     

     

     

     

    [dt_gap height=\”5\” /]

    Some features of SAP 7.30:

    • Corbu Design: New SAP GUI design,
    • Signature Color Theme: Different colours for different system, easier to differentiate between production environment and development environment,
    • Branding Area: Company logo can be added to the top right corner of the SAP screen,
    • Floating Docking Containers: Containers can be position individually,
    • Personalised Tab Order: Easily personalise the order of TAB

    Download SAP Logon 7.30:             Download Link

    SAP GUI 7.30 Installation Guide:     View Guide

    Please note that the SAP GUI for Windows 7.20 will be out of support as from 9th April 2013, make sure your SAP logon is up-to-date to be able to enjoy these new features. 🙂

  • How To Rename An Enhancement Spot

    Step 1:Go to transaction code \’SE19\’, that is the Badi Builder,

    Step 2:Enter the enhancement spot which we want to rename

    \"12-11-2013

    Step 3:Click on the button Rename

    \"12-11-2013

    Step 4: Finally, enter the new name of the enhancement spot and click on the button \’Rename\’.

    \"12-11-2013

    Voila! 🙂

  • Finding Transport Request By Description in SE03

    Step 1: Go to SE03 and double click on ‘Find Requests’.

    \"ABAP

    Step 2: Click on the icon shown in the screenshot below.

    \"ABAP

    Step 3: Enter the TR description in the field ‘Short description’.

    \"ABAP

    Step 4: Execute the program and voila you will find the related TR.

    \"ABAP

  • Displaying the standard menu buttons (SET PF-STATUS)

    Step 1: Go to transaction SE90.

    Step 2: Navigate to the directory shown in the screenshot below:

    \"image\"

    Step 3: Double click and on the next screen enter the standard program \’SAPLKKBL\’ as shown in the picture below and click execute. Please note that in this case we will copy the standard menu buttons from the standard \’SAPLKKBL\’.

    \"image\"

    Step 4: Once execute, select the standard program shown in the picture below.

    \"image\"

    Step 5: Finally click on the menu bar GUI status > Copy

    \"image\"

    Enter the name of the program to insert the PF Status and the name of the PF-Status.

    Step 6: Done, the PF-Status should appears in the program. Go in the program to view the PF-Status:

    \"image\"

    Step 7: Call the PF-Status using the following code below:

    								
    *----------------------------------------------------------------------*								
    * Setting up of the pf status of                                       *								
    * the ALV form.                                                        *								
    *----------------------------------------------------------------------*								
    FORM f_set_pf_status USING pi_extab TYPE slis_t_extab.								
    *----------------------------------------------------------------------*								
    
      SET PF-STATUS \'ZKUNGFU_DODO2\'.								
    
    *----------------------------------------------------------------------*								
    ENDFORM.                    \" F_SET_PF_STATUS

    Please Note: In case the buttons are not working on the PF-STATUS, please refer to the following fix.

  • Creating Routine Using VOFM in SAP

    1. Go to the transaction code VOFM.

    2. In the menu bar, choose between Table > Display or Table > Maintain

    3. The screenshot shows an example when modifying subroutine in VOFM responsible for the Data Transfer > Billing Documents.

    \"image\"

    4. Below is a list of all the sub routines in this specific VOFM (Data Transfer > Billing Documents)

    \"image\"

    5. Here, I will modify the sub routine 913 or 917.

    6. To modify a specified sub routine, double click on the sub routine to modify.

    Please Note: That you will required an ACCESS KEY in order to be able to make any modifications to the routine. ACCESS KEY is independent for each sub routine.

    Important: After transporting modify VOFM subroutines to other environments, please execute the program \’\’RV80HGEN\’  in SE38 to activate all subroutines. If this action is not carried out, the following exception (VOFM Error) will be raised:

    The exception, which is assigned to class \'CX_SY_DYN_CALL_ILLEGAL_FORM\', was
    not caught in							
    procedure \"VBRK_VBRP_DATENTRANSPORT\" \"(FORM)\", nor was it propagated by a							
    RAISING clause.							
    Since the caller of the procedure could not have anticipated that the							
    exception would occur, the current program is terminated.							
    The reason for the exception is:							
    The program \"SAPLV60A\" is meant to execute an external PERFORM,							
    namely the routine \"DATEN_KOPIEREN_601\" of the program \"SAPFV60C\", but							
    this routine does not exist.
  • Importance of field MANDT in Custom SAP Table

    It is important to use the field \’MANDT\’ when creating table because all information available in the table will only available in the specify MANDT only.

    But the rule specify above is not applicable for cross clients tables, that is tables where we want the content to be available in all available clients. For example, the transaction code \’FILE\’ which uses a cross client table does not need the field \’MANDT\’ because the data must be available in all the clients.

    Information:

    If we need to retrieve data from another MANDT, we should specified the option \’CLIENT SPECIFIED\’ in the select statement.

    REPORT demo_client_specified.
    
    DATA wa TYPE scarr.
    
    DATA name(10) TYPE c VALUE \'SCARR\'.
    
      SELECT  *
      INTO  wa
      FROM  (name) CLIENT SPECIFIED
      WHERE mandt = \'400\'. \'We are retrieving data from the client(MANDT)\"400\".
    
      WRITE: / wa-carrid, wa-carrname.
    
    ENDSELECT.
  • Converting Smart Forms to PDF format in SAP

    If you want to convert an SAP Smart Forms to PDF format directly, please follows the following steps:

    Step 1:

    When the smartform is in print preview mode, enter the command \’PDF!\’ in the command bar and press \’Enter\’.

    \"image\"

    Step 2:

    If adobe acrobat reader is installed correctly on the machine, a PDF version of the smartforms will be generated.

    Hope it helps. 😉