In release 6.10 a new exception concept has been introduced. Please find below a basic syntax of how
to code the new error-handling concept.

The following function module is used to return the text in a readable
format. Pass in the message ID, number and parameters and receive
the text in MESSAGE_TEXT_OUTPUT. 

      CALL FUNCTION 'MESSAGE_TEXT_BUILD'
           EXPORTING
                msgid               = messtab-msgid
                msgnr               = messtab-msgnr
                msgv1               = messtab-msgv1
                msgv2               = messtab-msgv2
                msgv3               = messtab-msgv3
                msgv4               = messtab-msgv4
           IMPORTING
                message_text_output = w_textout.

ALV report to find the list of infotypes configured in a SAP System

Choose a transaction and write a Batch Input program with 'Call Transaction'. Do not use the Message tab feature of 'Call Transaction'. In this case the last error message will be at the SY-MSG* system fields. Recreate the complete error message from table T100! (This example is also used by the demonstration of SY-MSG* system  fields)

You use the HIDE technique while creating a list level to store line-specific information for later use. To do so, use the HIDE statement as follows:

HIDE <f>.

List the first 100 purchase requsitions at the plant 'PL01' (table EBAN). Then make it possible to change the purchase requisition itself from the list by clicking twice on the row or by using a push-button.

While doing call transaction, if an error occurs in updation, we declare bdcmsgcoll and store our messages in it, but how to retreive error message from it.

Ever received that dreaded message "Time limit exceeded"? 

When you need to run a report that will go over the Basis timeout setting this is what you need to do....