"In ABAP it is very convenient to run a report using a Variant. Basically a report can have several Variants linked to it. If you use a variant then the data entry time is reduced considerably and this also reduces data entry errors. The load on the ABAP processing is also reduced. To create a Variant you may need the necessary authorizations. Most of the times while testing programs you will need to run a report using a variant and hence having the authorization to create a Variant is necessary. To create a Variant go to the main reporting screen, enter the name of the report for which you want to create the variant and select goto Variants option from the menu. The system displays the initial screen for the Variants. For creating a Variant you need to enter all the mandatory fields. Also you need to give a unique name for the Variant. Follow the naming convention rules. You may have to create several Variants for a particular report. Once a Variant is created you ca also schedule to run the report in the background using this Variant. For each variant that you create you need to give a brief description which will help to explain the purpose of the variant and help to distinguish the various Variants that you have created. You may want to protect your Variant by selecting the Protect Variant option. This option enables only the person who has created the Variant to change or delete it. While Running a report directly from the menu you can use the Run with Variant option and then select the desired variant from the dropdown list. Remember that Variants are report dependant. So to create a Variant you need to first create an ABAP report (Executable Program with selection screen). Once you successfully create all the variants for an ABAP report, you will save considerable amount of time which would otherwise have been spent in entering the same data again and again."
"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."
SAP ABAP Transferring Internal Table Contents to a file on the Application Server
In SAP ABAP you can transfer the contents of the internal table to a file. This is required when you wish to extract data from SAP tables into a flat file. This file can then be used to transfer data to another SAP or NON SAP system. This can also be used for an interfacing when you wish to transfer data on a daily or a weekly basis from R/3 to NON R/3 or SAP. The command used to create a file on the application server is as follows.
OPEN DATASET
Please see example code below.
REPORT ZEX_DATATOFILE .
*&---------------------------------------------------------------------* *& ABAPLOVERS: Data Transfer *&---------------------------------------------------------------------*
* Parameters to enter the path PARAMETERS FILENAME(128) DEFAULT '/usr/tmp/testfile.dat' LOWER CASE. * Table Declaration TABLES VBAK.
* Data Declaration DATA D_MSG_TEXT(50).
* Get data for file transfer DATA INT_VBAK LIKE VBAK OCCURS 100 WITH HEADER LINE. SELECT * FROM VBAK INTO TABLE INT_VBAK. SORT INT_VBAK BY VBELN. LOOP AT INT_VBAK. WRITE: / INT_VBAK-VBELN, INT_VBAK-KUNNR. ENDLOOP.
* Opening the File OPEN DATASET FILENAME FOR OUTPUT IN TEXT MODE MESSAGE D_MSG_TEXT. IF SY-SUBRC NE 0. WRITE: 'File cannot be opened. Reason:', D_MSG_TEXT. EXIT. ENDIF. * Transferring Data LOOP AT INT_VBAK. TRANSFER INT_VBAK-VBELN TO FILENAME. ENDLOOP. * Closing the File CLOSE DATASET FILENAME.
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.