" The role of the update work process is very important since it is responsible for recording the changes in the database. The process performs its functions when the ABAP applications are programmed with the statements in the UPDATE TASK. This type of updating is asynchronously performed, ie. The programs leave update records in a queue to be processed and then continue to the update process. Normally, it runs without any intervention from the SAP R/3 management, still R/3 includes utilities to monitor check and perform management operations on the updation processes. In case any updating error takes place, the system places a message to the user regarding the error and an alert is triggered in the CCMS monitor. For the update functions go to Administration menu bar option --> Monitor option ---> Update option. An initial update screen showing various functions appears. The initial update screen is used to display the system update records with error status or the records which have not yet been processed, activate and deactivate the updating in the whole SAP system. It is also useful to display the update statistics, to display the data on the erroneous update records and reprocess them, either in real or in test mode and to send waiting update records for processing after a deactivation/activations of the updating and delete update records. Many work processes of the type R/3 system update the database. A database interface is included by the dialog and background work processes, which can directly update the database. However, the update work processes ca also be used for updating the physical database in asynchronous way. If it is asynchronous updating, according to which the transactions are programmed in the ABAP business applications, then in the database commit phase, the transactions pass the update records to the update work processes."
"The flow of a program is determined by a sequence of screens in a dialog transaction. The screens that are called within a transaction, must belong to a single ABAP program, usually a module pool (Type M). You have to use the transaction maintenance transaction (SE93) to create a dialog transaction. Once you have entered a transaction code and a short description, chose transaction type program and screen. Then enter data on the next screen as required. The transaction code in a dialog program must be linked to the number of its initial screen. Finally enter this number in the screen number field."
If you are on a particular screen and wish to check the current transaction in SAP then you can follow the menu path given below. System----->Status. Please refer the diagram shown below.
Once you click on Status you will see the screen shown below.
In the above screen you can see the complete SAP system information.
SAP OWN DATA
In the SAP System if you want to set defaults or want to give your own preferences then you can follow the menu path given below.
SYSTEM -------- USER PROFILE -------- OWN DATA.
Please refer the screen shown below.
For example you can change the way system date is displayed. (mm.dd.yyyy) or (dd.mm.yyyy)
Hold Data and Set Data
Suppose you want to create multiple Sale Orders or Purchase Orders with similar data. Then you need not type in all the fields again and again. This can be done by using the Hold Data and Set Data functionality.
To check this functionality pleas run transaction VA01 ---- SAP Sales Order Create. Type in the required fields like
Ship-to Party Sold-to Party Purchase Order Number Material No Quantity
and then click on HOLD Data (Menu Path >>>>>>>>> System ---------- User Profile ------- Hold Data)
Please refer the figure below.
The fields that contain data will be held even after saving the sales Order and will remain when the next VA01 screen appears. Now you can make changes in the data and Save the Order.
Similarly you can use Set Data. By using Set Data the values remain on the screen but are not available for editing. Set Data can be used if you are sure that you would be creating multiple objects in same with exactly the same data values.
Always specify your conditions in the Where-clause instead of checking
them yourself with check statements. The database system can then use an index
(if possible) and the network load is considerably less.
Always use Pretty Printer and Extended Program Check before releasing the code.
Do not leave unused code in the program. Comment the code thoroughly. Align the comments and the Code. Follow the SAP Standards and SAP Best Practices guidelines. It’s a good practice to take a dump of the code on your local drive.
