"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."
"A subset of Standard SQL that is fully integrated in ABAP is Open SQL statements. Their role is to help you by giving permission to access data irrespective of the database system, which the R/3 installation is using. The Data Manipulation Language (DML) part of the Standard SQL is present in the Open SQL. In other words, it gives you the permission to read (SELECT) and change (INSERT, UPDATE, DELETE) data. In the R/3 system, the tasks of the Data Definition Language (DDL) and Data Control Language (DCL) parts of the Standard SQL are performed by the ABAP dictionary and the authorization system."
SAP ABAP Function Module to add Days Months and Years to a Date
Consider a scenario where you want to add days, months and years to the date field. You can either write custom code to achieve the desired result or use a standard function module provided by SAP. It is always a best practice to use a standard function module as it save time and effort. Also the standard function modules have already been tested by SAP and they give you the desired result. The resulting code is easier to maintain.
The following function module can be used to achieve the desired result.
RP_CALC_DATE_IN_INTERVAL
Please see the code given below
REPORT ZEX_ADDDAYSMONTHSYEARS .
Parameters: p_date like P0001-BEGDA, p_days like T5A4A-DLYDY, p_mons like T5A4A-DLYMO, p_yrs like T5A4A-DLYYR, p_date1 like P0001-BEGDA.
CALL FUNCTION 'RP_CALC_DATE_IN_INTERVAL' EXPORTING DATE = p_date DAYS = p_days MONTHS = p_mons SIGNUM = '+' YEARS = p_yrs IMPORTING CALC_DATE = p_date1 .
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.
No comments:
Post a Comment