loader
  • Useful System Fields

    It may be helpful to have the generally available system fields.   They are helpful to have in your back pocket when you’re floundering around looking for extra information in a user exit.   Check in debug to see if they hold the information you’re looking for.

    SY-SUBRC

    SY-INDEX

    SY-TABIX

    SY-DBCNT

    SY-FDPOS

    SY-LSIND

    SY-PAGNO

    SY-LINNO

    SY-COLNO

    SY-PFKEY

    SY-UCOMM

    SY-TITLE

    SY-MSGTY

    SY-MSGID

    SY-MSGNO

    SY-MSGV1

    SY-MSGV2

    SY-MSGV3

    SY-MSGV4

    SY-MODNO

    SY-DATUM

    SY-UZEIT

    SY-XPROG

    SY-XFORM

    Thanks to Robyn for submitting this trick through the contact page.

  • ABAP Runtime Errors Short Dump Actions

    What to do when you get a short-dump or ABAP runtime error.

    I do the following – you may find this useful in your day to day analysis:

    • As soon as possible I check ST22.
    • Knowing that entries in ST22 only stay 3 days before being purged.
    • From ST22 take careful note of the Server name. (You may need this for SM21).
      • Generally from ST22 you may be able to locate the source of the problem under the section called “Error analysis”.
      • If possible, depending on the transaction, press F7 and go into the ABAP editor where the problem exists. Set a breakpoint. Re-execute the logic and watch the variables.
      • If the problem is from memory whilst in debug mode, select the menu path: GotoàSystem AreasàSAP Memory (You will now be in a mode which shows Area = SMEM) This also shows the values in memory, including user parameters.
    • On some occasions you may wish to see more information on the system message log using SM21. If you do this ensure you use the menu path: System LogàChooseàRemote System Log to select the server on which the error occurred. (This opens up the instance as a selection variable on the selection parameters.)
    • It is possible the ABAP runtime error may have resulted in a terminated update, You can view these in SM13.
  • Welcome to the new SAP Tricks layout

    SAP Tricks has now been updated to help you get SAP Information faster by:

    • Being made totally responsive on any mobile device. This means the site content will automatically adapt to your screen, making the content easier to use.
    • Using a cleaner clearer font. This means the text is now easier to read.
    • Removal of unnecessary graphics. No distractions on the content.
    • Improved search facility. Powerful new search engine helping you locate SAP tricks.
    • Addition of a contact form. Feel free to submit SAP Tips Tricks or just get in touch.
    • New Social buttons. Join the SAP Tricks community on LinkedIn.

    We wish you all the best in your SAP career.

  • IMG values and table display values not consistent

    Picture the scenario, you check a configuration value in the IMG and it has a value for example 1,00. You then check its technical table and field name (By going F1 for help and then selecting the “Technical Information” icon  you then go to SE16 and check the value and whoops, its 240.000.  Confused? No need to be.

    SAP has a conversion routine on the domain of the data element of the field name. To check use a real world example:

    Use SE11 and check table and field TVRO-TDVZTD, this field uses Data element TDVZTD, select the Data Type tab an double click on the Domain TSTRDURAG, check the definition tab and see the Conversion routine TSTRG. If you double click on the conversion routine you will find the Function Modules used to change the output display: CONVERSION_EXIT_TSTRG_OUTPUT.

    You can now test by using SE37 and the FM – CONVERSION_EXIT_TSTRG_OUTPUT with an input parameter of 240000, which will provide you the output value of 1,00.

    TIP – You can also use SE16N with table TVRO (as opposed to SE16) – double click on the output line – which will provide you with the screen output display value of 1,00 as well as the internal database value of 240000.

  • Pricing Condition Records Change Report

    Did you know that there is a pricing conditions change report in SAP?

    This report gives you the ability to check the before and after values for condition records for a condition type, promotion, sales deal or agreement. You can limit the selection criteria to be table specific if required, in addition to using a date range. You are also able to select changes made by a specific user ID, or even changes made when a specific transaction code was executed.

    Simply run report – RV16ACHD from SE38 or SA38.