" 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."
"SAP has provided two different types of methods for BDC to do its work. Among these the first one is called the classical method. This method is also called as the session method. Through this method the data can be read by the BDC program from a sequential dataset file. This sequential dataset file is stored in batch-input sessions. In order to run the transaction in this session, What you need is to execute the session. For this follow these few steps. YOu an start and subsequently monitor the sessions firstly from System----> Service---->Batch input or have the sessions run in the background."
Wednesday, February 6, 2008
Creating a Function Module in SAP ABAP. DownLoad PDF Function modules are very important in SAP ABAP. Once you create a function module then it can be called from any program. You just need to pass some parameters to this function module and once the function module runs it passes back the desired result in the form of a variable. SAP has provided a transaction to create a function module. Execute transaction SE37 and create a function group as shown in the figure below.
Give the desired function group name and a short text.
Once the function group is created type the desired function module name as shown below. And click on create.
Enter the function group name created earlier and the desired short text for function module. and click on save.
Save the function module as a $tmp object.
Now the following screen will be presented to you, here you need to enter the import and export parameters. These are nothing but the variables that you would be passing to the function module and the returned values from the function module.
The following screen shot shows the returned values from the function module.
Type the following code in the source code area.
Active the function module and the related code.
Call the above created function module from an ABAP Report. The following screen shot shows the details to insert the code.
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.
