SAP ABAP Program (Update control) is using • • • • • • • # Object Type Object Name Object Description Note 1 Table/Structure Field - Group of SAP instances 2 Table/Structure Field - SAP Instance Name 3 Table/Structure Field - Name of a DB instance 4 Table/Structure Field - Group of SAP instances 5 Table/Structure Field - Documentation Object 6 Table/Structure Field - Status of documentation module 7 Table/Structure Field - Module Title 8 Table/Structure Field - Application Server Instance SOURCE MODULE SERVER_LIST. Affinities: © Copyright 2014 - 2019,, The Best Online SAP Object Repository SAP Datasheet web site and its affinity sites content is based on our knowledge of SAP system, and it is constantly reviewed to avoid errors; well we cannot warrant full correctness of all content.

While using this site, you agree to have read and accepted our terms of use, cookie and privacy policy. Use the information and content on this web site at your own risk. SAP and the SAP logo are registered trademarks of. This web site is not sponsored by, affiliated with, or approved. This web site is validated by as.

Debugging SAP events By Saurabh Asthana, Infosys Technologies Overview: This document explains how receiver Function module can be used as a Substitute of BAPIs and Exits in particular cases and how to debug those events, as general debugging method can not be used for them. This document is categorized into: • events • About receiver FM • o debug related event INTRODUCTION OF EVENTS: § Events indicate the occurrence of a status change of a Business objects. § Events always belong to an object and are therefore described as definition components in the object type § Events can have parameters & exceptions like methods § These events have listeners (outside the BO). E.g., workflow § We can create our own events also. Procedure to create Events: a) Position the cursor on the entry Events. And then press create b) Now enter the following texts for the event to be created C) Give Event, Name, Short description § Irrespective of whether you use uppercase and lowercase in the event name, the name is always entered in uppercase letters in the event receiver linkage table by the system. § The event has now been created and is available in the Business Object Repository.

Yesudas ayyappa songs in telugu. Sep 8, 2011 - *Termination occurred in the ABAP program 'RV13A004' - in 'DB_UPDATE'.* *The main program was 'RSM13000 '.* *In the source code.

§ You can now use this event in the other definition tools in SAP Business Workflow. Position the cursor on the new event and choose Edit → Change release status → Object component → to implement.

§ The object type must first be generated so that it can be instantiated and tested. About Receiver FM: § If we have a requirement like insertion of an entry in a table when material is changed in a sales order or we want some functionality to happen when a purchase order or sales order is created, generally in such cases we look for BADIs and exist, these are called after the save events are triggered and we place our logic there.

But we can also have a separate approach in which we link the event to a function module through Transaction SWETYPV and the logic are written in the FM to satisfy the requirement. § Now if we want to Debug that code, just by putting the break point there, we cannot reach their directly So for this purpose below mentioned method should be followed, this procedure is very useful and can be utilized wherever we want to debug the events.