"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 SELECT-OPTIONS to have Upper and Lower Case
SELECT-OPTIONS by default displays all characters in UPPER CASE. This happens once the user hits the ENTER Key. If you wish to force Lower Case on the field values entered in the SELECT-OPTIONS fields use the addition LOWER CASE.
The Syntax is as follows.
SELECT-OPTIONS: s_ernam for vbak-ernam LOWER CASE.
The code is as follows.
REPORT ZEX_SELECTOPTIONS.
Tables: VBAK, VBAP.
Data: int_vbak type vbak occurs 0 with header line.
Select-options: s_vbeln for vbak-vbeln , s_auart for vbak-auart, s_ernam for vbak-ernam LOWER CASE.
Select * INTO int_VBAK from VBAK where VBELN in s_vbeln. APPEND int_VBAK. CLEAR int_VBAK. ENDSELECT.
loop at int_vbak. Write:/ int_vbak-vbeln, int_vbak-AUART. endloop.
write:/ s_vbeln-low, s_auart-low, s_ernam-low.
In the above example, s_ernam has the addition of LOWER CASE where as s_auart does not have the addition. Once you execute the program the output will show auart in upper case where as ernam in the case that has been entered by the user as it is.
Not: If TYPE addition is used to refer data types from the ABAP dictionary, then you cannot use the LOWER CASE addition. If you enter the following data
Sales Order 4969 Order Type or Created By JohN
Then the Output would be as follows.
Select Options in SAP ABAP 4969 OR 4969 OR JohN
This is because s_ernam has the LOWER CASE addition where as s_auart does not have the addition.
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