"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."
"Radio Frequency Identification Devices are responsible for electronically capturing the data related to Materials. Once the data is captured, it is transmitted via Radio waves to the SAP server. The main use of RFID devices is in Warehouses where the data is physically moved from one location to another. It is very convenient for the warehouse personnel to make use of RFID so that all the material movement is captured automatically and the information is transferred to the SAP server. SAP Auto-ID Infrastructure is the component in SAP Netweaver that provides gateway to the RFID Data."
SAP ABAP Using the ABAP inbuilt functionality to add Sates.
The easiest way to add or subtract days from any date filed in ABAP is shown below. Basically ABAP has an inbuilt functionality with the help of which you can add or subtract dates from the date field.
See the example given below.
REPORT ZEX_DATEADD .
*Using the ABAP inbuilt functionality to add dates. * Data Declaration Parameters: P_DATE1 TYPE D.
Data: D_DATE1 TYPE D.
* 15 Days after the input date D_Date1 = P_DATE1 + 15. Write:/ 'Input Date', P_DATE1, '15 Days after the input date.'. WRITE / D_DATE1. SKIP. * 50 Days after the input date D_Date1 = P_DATE1 + 50. Write:/ 'Input Date', P_DATE1, '50 Days after the input date.'. WRITE / D_DATE1. SKIP. * 500 Days after the input date D_Date1 = P_DATE1 + 500. Write:/ 'Input Date', P_DATE1, '500 Days after the input date.'. WRITE / D_DATE1. SKIP.
Write:/ 'Going Back in Time'. SKIP.
* 15 Days before the input date D_Date1 = P_DATE1 - 15. Write:/ 'Input Date', P_DATE1, '15 Days before the input date.'. WRITE / D_DATE1. SKIP. * 50 Days before the input date D_Date1 = P_DATE1 - 50. Write:/ 'Input Date', P_DATE1, '50 Days before the input date.'. WRITE / D_DATE1. SKIP. * 500 Days before the input date D_Date1 = P_DATE1 - 500. Write:/ 'Input Date', P_DATE1, '500 Days before the input date.'.
If you input the following date
01012000
Then the output would be as follows.
Adding Date
Input Date 01012000 15 Days after the input date. 01162000
Input Date 01012000 50 Days after the input date. 02202000
Input Date 01012000 500 Days after the input date. 05152001
Going Back in Time
Input Date 01012000 15 Days before the input date. 12171999
Input Date 01012000 50 Days before the input date. 11121999
Input Date 01012000 500 Days before the input date. 08191998
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.
