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

Explain the structure of a bdc sessions?

1048


What is the different between template and a table?

1201


Explain what is the significance of hide?

1168


Explain the different types of mode (run code) in call transaction method?

1139


What is the use of the statement leave to list-processing?

1044


What is bdc? : abap bdc

1069


What is an Open Item in SAP? How will you find an Open Item in SAP?

1121


Explain the use of table maintenance allowed?

1058


What is the Process to transfer IDOC from Outbound System to Inbound system.

2206


SAP Script for Billing in which Billing document number was displayed as header, Bill Type, Bill Category, Bill Item, Cost, Base Unit of Measurement and Material number were categorically displayed for each billing document number. plz mention the detail coding Tahnks, Rahul

2567


What is meant by stacked list?

1048


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

1109


Difference between /N and /BEND?

1324


What are the parameters in bdc_insert? : abap bdc

1347


How is conversion of data types done between abap/4 & external level?

1081