Home| Forums | Join Google Group | Join Yahoo Group | Jobs

Earn Money
Trading Forex Online
  Paramount Airways
  Free Data Recovery
Cargo
Job Portal
  HSBC Investment
Management
Cheap Web Hosting
  Make Trip
  Cheap Air Travel
Leisure Hotel
  Free Air Travel
  Mutual Fund Informations
Cheapest Cellular Plan
Free Sexy Indians
  Call Center Software
  Hot Indian

Programming Help | Homework Help | Counseling
Astrology Advice | Tarot Advice | Parenting
Dating Advice | Love Advice | Divorce Advice
Legal Advice | Debt Advice | Career Advice
What is LUW or Database LUW or Database Transaction ? A "LUW" ( logical unit of work ) is the span of time during which any database updates must be performed in an "all or nothing" manner. Either they are all performed ( committed ) , or they are all thrown away ( rolled back ). In the ABAP/4 world, LUWs and transactions can have several meanings: LUW ( or "database LUW" or "database transaction" ) This is the set of updates terminated by a database commit. A LUW lasts, at most, from one screen change to the next ( because the SAP system triggers database commits automatically at every screen change ). What is SAP LUW or Update Transaction ? Update transaction ( or "SAP LUW") This is a set of updates terminated by an ABAP/4 commit. A SAP LUW may last much longer than a database LUW, since most update processing extends over multiple transaction screens.The programmer terminates an update transaction by issuing a COMMIT WORK statement. What happens if only one of the commands SET SCREEN and LEAVE SCREEN is used without using the other? If we use SET SCREEN without LEAVE SCREEN, the program finishes processing for the current screen before branching to <scr no>. If we use LEAVE SCREEN without a SET SCREEN before it, the current screen process will be terminated and branch directly to the screen specified as the default next-screen in the screen attributes. What is significance of the screen number `0' ? In "calling mode", the special screen number 0 (LEAVE TO SCREEN 0) causes the system to jump back to the previous call level. That is, if you have called a screen sequence with CALL SCREEN leaving to screen 0 terminates the sequence and returns to the calling screen. If you have not called a screen sequence, LEAVE TO SCREEN 0 terminates the transaction. What does the command `SUPPRESS DIALOG' do ? Suppressing of entire screens is possible with this command. This command allows us to perform screen processing "in the background". Suppresing screens is useful when we are branching to list-mode from a transaction dialog step. What is the significance of the memory table `SCREEN' ? At runtime, attributes for each screen field are stored in the memory table called `SCREEN'. We need not declare this table in our program. The system maintains the table for us internally and updates it with every screen change. What are the fields in the memory table `SCREEN' ? - Name Length Description Why grouping of fields is required ? What is the maximum number of modification groups for each field ? - If the same attributes need to be changed for several fields at the same time these fields can be grouped together. We can specify up to four modification groups for each field.