Golgappa.net | Golgappa.org | BagIndia.net | BodyIndia.Com | CabIndia.net | CarsBikes.net | CarsBikes.org | CashIndia.net | ConsumerIndia.net | CookingIndia.net | DataIndia.net | DealIndia.net | EmailIndia.net | FirstTablet.com | FirstTourist.com | ForsaleIndia.net | IndiaBody.Com | IndiaCab.net | IndiaCash.net | IndiaModel.net | KidForum.net | OfficeIndia.net | PaysIndia.com | RestaurantIndia.net | RestaurantsIndia.net | SaleForum.net | SellForum.net | SoldIndia.com | StarIndia.net | TomatoCab.com | TomatoCabs.com | TownIndia.com
Interested to Buy Any Domain ? << Click Here >> for more details...

What is updated Function Module.

Answer Posted / aditi

It is basically used to bundle distributed updates within different programs spots, to one place (in FM).

Such FM would store all the UPDATE/INSERT/DELETE statements which otherwise you would write in some program place. Now when system reaches CALL FUNCTION 'XXX' IN UDPDATE TASK it doesn't go inside. Instead in registeres this XXX FM in VBLOG table (you can see update tasks in SM13) to be executed later. Now when in program it reaches COMMIT WORK statement, it looks into that table and calls each registered functions.

The aim is to either COMMIT all the changes at once, or ROLLBACK them all. This means that if inside one of any FM these statements are encountered system writes changes to DB permanently. Next it clears VBLOG table (so no FM are registered for change anymore) and continues the program.

This is the most common and safe way to make changes to DB within one [SAP LUW|http://help.sap.com/saphelp_46c/helpdata/en/41/7af4bfa79e11d1950f0000e82de14a/frameset.htm]. There is also other way of doing the same within distributed subroutines which are also described in this document.

But if you are asking yourself what is the reason for use of such bundling techniques. It is because [DB LUW|http://help.sap.com/saphelp_46c/helpdata/en/41/7af4bca79e11d1950f0000e82de14a/frameset.htm] differes from the SAP LUW. It is just a smaller part of the latter and is used to submit changes (permanently) in DB after each UPDATE/INSERT/DELETE. In case of later errors during DB update you could then no longer restore previous state of DB with ROLLBACK. That's why SAP created its own SAP LUW.

Is This Answer Correct ?    0 Yes 0 No



Post New Answer       View All Answers


Please Help Members By Posting Answers For Below Questions

Difference between call by value and call by reference? : abap data dictionary

1026


What is collective search help? : sap abap data dictionary

981


While sorting field groups we cannot use more than one key field. State true or false. : abap modularization

988


Explain what is a foreign key relationship? Explain this with the help of an example.

1011


What is the client concept in sap?

1022


What is synchronous update?

952


Static and instance variable and method with live example. Why and when to use

1361


What is pretty printer?

978


What are the advantages and disadvantages of using views in abap programming ?

1050


What are the three components of a work process?

1051


hi to all abap interview guys please notify this .. first if u have any doubts please go through google search or else please do debugging with some sample programs . but don't post even silly questions too. thanking you.

1923


Why bapi need then bdc ? : abap bdc

1039


What is the purpose of creating symbolic a/c, what is transaction code for same? Can we assign one symbolic a/c to multiple wage types? : sap abap hr

1232


Can we use write statements in screen fields?if not how is data transferred from field data to screen fields?

959


Explain what are the events used in interactive reports?

911