"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."
"The flow of a program is determined by a sequence of screens in a dialog transaction. The screens that are called within a transaction, must belong to a single ABAP program, usually a module pool (Type M). You have to use the transaction maintenance transaction (SE93) to create a dialog transaction. Once you have entered a transaction code and a short description, chose transaction type program and screen. Then enter data on the next screen as required. The transaction code in a dialog program must be linked to the number of its initial screen. Finally enter this number in the screen number field."
OLE AUTOMATION PART 3DownLoad PDF In this post we will see the Color code for Excel Cells by using SAP OLE. Color code for ABAP is shown below, please use the numeric value as given in the figure below. For example if you want the interior color of the Excel cell to be of the color Cyan then use the code 8.
DownLoad PDF The following ABAP key words control the applications:
CREATE OBJECT SET PROPERTY GET PROPERTY CALL METHOD FREE OBJECT
The Desktop application serves as the OLE server to the calling ABAP program. For example when the ABAP program makes calls to the OLE application the SAPGUI servers as the client. The create statement generates the object of this class. The following return code values can be encountered.
SY-SUBRC = 0: Object successfully generated.
SY-SUBRC = 1: SAPGUI communication error. SY-SUBRC = 2: SAPGUI function call error. The frontend ports of SAP’s OLE implementation modules are implemented only under Windows and Apple Macintosh. SY-SUBRC = 3: The OLE-API call resulted in an error - possibly a storage space problem. SY-SUBRC = 4: The object is not registered with SAP.
Note that for each OLE object there has to be a variable holding handle data for that object. The type-pool “ole2” defines the handle variable data of the type ole2_object. For all the OLE automation programs “OLE2INCL” include should be used. Please find below some examples of setting the properties of fonts, cell borders and colors. Font Properties. SET PROPERTY OF name_font 'Name' = 'Times New Roman' . SET PROPERTY OF size_font 'Size' = '12' . SET PROPERTY OF bold_font 'Bold' = '0' . "Not bold SET PROPERTY OF Italic_font 'Italic' = '0' . "Not Italic SET PROPERTY OF underline_font 'Underline' = '0' . "Not underlined
Paragraph Formatting SET PROPERTY OF allignment_parformat 'Alignment' = '3' . "Justified
Similarly for EXCEL DATA: d_excel TYPE ole2_object , d_cell1 TYPE ole2_object , d_cell2 TYPE ole2_object , d_cells TYPE ole2_object , d_range TYPE ole2_object , d_font TYPE ole2_object , d_interior TYPE ole2_object , d_columns TYPE ole2_object , d_charts TYPE ole2_object , d_chart TYPE ole2_object , d_charttitle TYPE ole2_object , d_charttitlech TYPE ole2_object , d_chartob TYPE ole2_object . Sample code CREATE OBJECT d_excel 'EXCEL.APPLICATION' . SET PROPERTY OF d_excel 'Visible' = 1 . GET PROPERTY OF d_excel 'Workbooks' = gs_wbooklist . Formatting the Excel Cells GET PROPERTY OF d_cell1 'Font' = d_font . SET PROPERTY OF d_font 'Underline' = 2 . SET PROPERTY OF d_font 'Bold' = 1 . SET PROPERTY OF d_cell1 'HorizontalAlignment' = -4108 . GET PROPERTY OF d_cell1 'Interior' = d_interior . SET PROPERTY OF d_interior 'ColorIndex' = 15 . >>>>>>>>>> Check Ole Automation part 3 SET PROPERTY OF d_interior 'Pattern' = -4124 . SET PROPERTY OF d_interior 'PatternColorIndex' = -4105 . Folor Color Code
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.