"In SAP for logging in to the system you need a user ID and a password. This user ID is created by the system administrator. The first time you login to the SAP system you need to change that password which has been assigned to you while creating the user ID. Every user ID will have certain roles assigned to it. The System Admin (Basis Administrator) is responsible for creating these roles after consulting the Functional team. Each user will typically have several roles assigned to their user ID. The user roles are predefined in the SAP system and each employee would have a combination of several roles which have been predefined in the SAP system. The roles are defined using the activity groups in the SAP system. A proper understating of the activity groups is necessary for creating and assigning Roles in the SAP system. Once a pre-defined user role is assigned to a user the system then automatically displays the appropriate User menu when the user logs on and provides the required authorization. An activity group can contain Transactions, Reports, Files, Web Links. Once the activity group has been assigned it defines the user specific menus. Once the user logs on to SAP a user specific menu is displayed this menu is controlled by the activity group that has been assigned to the user. To display a list of descriptions of the pre-defined user roles, select Tools---- Administration----User Maintenance--'Repository Infosys--' Activity Groups----' List of activity groups according to complex selection criterion---' Selection according to activity group name or call transaction S_BCE_68001418. The pre-defined user roles are delivered as templates and have names beginning with 'SAP_' and suffix _AG. Composite activity groups can be built with individual activity groups. A composite activity group does not contain any authorization."
"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."
Variants can be used when you need to run a Report (Any ABAP Executable program) with different selection criterion. For example if you have a report that needs to be run for Western Region/Easter Region or for different company codes/ Sales Areas. It becomes tedious to enter the selection criterion again and again. Also some reports need to be run in the background. You can schedule to run the report in the back ground with a variant.
To create a variant please follow the steps given below.
Run Transaction SE38 Enter the Report Name Run the Report once the selection screen is displayed click on save.
Click on Save
Enter the Variant name and a short description.
You can create multiple variants for a single report. Once the variants are created you can then choose the variant that you wish to run and then run the report.
In ABAP we can use TRANSLATE statement to change the case of characters. This means that if you want to programatically convert any characters to upper case or to lower case then it can be done using the TRANSLATE statement.
There is another variation of TRANSLATE statement in which you can translate characters in STRING1 as per the rules given in STRING2.
Please see the examples given below.
DATA: d_PH(17) VALUE 'PeAcEaNdHaRmOny', d_Translate LIKE d_PH, RULE(30) VALUE 'PHeEAAcLETaHNYdLHIaVRImNOGn y '.
d_Translate = d_PH. WRITE d_Translate.
TRANSLATE d_Translate TO UPPER CASE. WRITE / d_Translate.
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.
