Here is the System Class for Establishing the Properties of Characters in ABAP.
The class CL_ABAP_CHAR_UTILITIES provides attributes and methods that concern attributes of individual characters. The components of this class are all static and public, the attributes are write-protected and are initialized in the class constructor.
These are two system classes that handle Conversion of Time Stamps and time formats in ABAP programs.
Here is some System classes and its methods that handle Mathematical Operations in ABAP.
Class CL_ABAP_MATH contains methods and constants for operations with floating point numbers.
Methods and operations with decimal floating point numbers
Class CL_ABAP_RANDOM calls the pseudo random number generator for various numeric types.
Subclasses of the abstract system class CL_ABAP_EXPIMP are used for handling Data clusters in ABAP.using these classes we can access/ delete data clusters in the individual storage media.
These classes offer a range of methods that enable text in text fields or text strings, or binary data in byte fields or byte strings to be compressed or decompressed using GZIP.
These are the list of some the important System fields in ABAP and its details.
| System Fields | Type | System Field details |
| sy-abcde | c(26) | This Transaction code Contains the Latin alphabet. Can be used to access individual letters directly by specifying the offset/length, regardless of the code page. |
| sy-batch | c(1) | This Transaction code Set to “X” in an ABAP program that runs in the background, otherwise initial. |
| sy-binpt | c(1) | This Transaction code Set to “X” during processing of batch input sessions, and in ABAP programs called using CALL TRANSACTION USING. Otherwise initial. |
| sy-calld | c(1) | This Transaction code Contains a blank character in the first program in a call sequence, otherwise contains the value “X”. Is set to “X” after calls using CALL TRANSACTION, CALL DIALOG, or SUBMIT … AND RETURN. Empty if the program was started using LEAVE TO TRANSACTION or a transaction from the screen. A call using SUBMIT (without AND RETURN) assumes the value of the calling program. |
| sy-callr | c(8) | This Transaction code used When printing lists, contains a value that displays where printing was started – for example, NEW-PAGE for program-controlled printing, or RSDBRUNT for printing from the selection screen. |
| sy-colno | i | This Transaction code return Current position during creation of a list in the list buffer. Counting begins at 1. In non- Unicode systems, this position also corresponds to the column in the displayed list. In Unicode systems, this is only guaranteed for the lower and upper output limits applicable to each output, as one character may take up more columns in the list than positions in the list buffer. |
| sy-cpage | i | This Transaction code return Page number of the page displayed at the top of the list for which a list event was triggered. Counting begins at 1. |
| sy-cprog | c(40) | In procedures called externally, the name of the calling program, otherwise the name of the current program. If a procedure called externally calls another external procedure, sy-cprog contains the name of the framework program, and is not set to the name of the framework program of the subsequent calling program. |
| sy-cucol | i | This Transaction code return Horizontal cursor position in the display on a dynpro. Counting begins at column 2. |
| sy-curow | i | This Transaction code return Vertical cursor position on the screen display of a screen. Counting begins at line 1. |
| sy-datar | c(1) | At PAI, contains “X” if at least one input field of a screen has been changed by a user or by further data transfer, otherwise initial. |
| sy-datlo | d | Local date of the user – for example, “19990723″. Can be set using GET TIME. |
| sy-datum | d | This Transaction code return System date (local date of the AS ABAP). Can be set using GET TIME. |
| sy-dayst | c(1) | “X” during summertime, otherwise initial. |
| sy-dbcnt | i | SQL statements set the content of sy-dbcnt to the number of processed table lines. |
| sy-dbnam | c(20) | In executable programs, the linked logical database. |
| sy-dbsys | c(10) | Central database system – for example, “ORACLE”, “INFORMIX”. |
| sy-dyngr | c(4) | Screen group of the current screen. In the Screen Painter, several screens can be assigned to a common screen group, which can be used, for example, for making modifications to all screens in the group at once. |
| sy-dynnr | c(4) | This Transaction code return Number of the current screen. During selection screen processing, this is the current selection screen. During list processing, the number of the subscreen container. During processing of a subscreen dynpro (including in tabstrips), this screen number. |
| sy-fdayw | b | Factory calendar weekday, Monday = 1, …, Friday = 5. |
| sy-fdpos | i | Found location for certain searches in character-like and byte-like data objects. |
| sy-host | c(32) | Network name of the host on which the current application server is instantiated, for example “KSAP0001″, “HS01234″. |
| sy-index | i | This Transaction code return Loop index. In DO and WHILE loops, contains the number of the loop passes including the current pass. |
| sy-langu | c(1) | Single-character language key – for example, “D”, “E”, “F” – for the current text environment. Set according to the logon language of the user or by using the statement SET LOCALE. |
| sy-ldbpg | c(40) | In executable programs, the database program of the linked logical database. |
| sy-lilli | i | This Transaction code return List line for which a list event was triggered. Counting begins at 1 and includes the page header. |
| sy-linct | i | This Transaction code return Page length of the current list during list creation. sy-linct is 0 for a standard list of any length, and has a value that is not 0 for lists with a defined page length. |
| sy-linno | i | This Transaction code return Current list line during list creation. Counting begins at 1 and includes the page header. |
| sy-linsz | i | Line width of the current list in the list buffer during list creation. |
| sy-lisel | c(255) | Content of the list line in the list buffer, on which the cursor was positioned while a list event was triggered (restricted to the first 255 lines). |
| sy-listi | i | List level of the list for which a list event was triggered. |
| sy-loopc | i | Number of lines currently displayed in a table control. |
| sy-lsind | i | List level of the list that is currently being created (basic list: 0, details lists: greater than 0). For every interactive list event, sy-lsind is automatically increased by an increment of 1. sy-lsind can only be changed in ABAP programs for navigating between details lists. |
| sy-macol | i | When printing lists, contains the number of columns on the left edge. |
| sy-mandt | c(3) | Client identifier with which the user has logged on – for example, “401″, “800″. |
| sy-marow | i | When printing lists, contains the number of lines on the top margin. |
| sy-modno | i | Indexing of external sessions. Contains the value 0 in the first session. In new sessions that are opened using the Create Session function or by calling a transaction with /o in the command field of the standard toolbar, this value is increased by 1. |
| sy-msgid | c(20) | After the statement MESSAGE, contains the message class. |
| sy-msgno | n(3) | After the statement MESSAGE, contains the message number. |
| sy-msgty | c(1) | After the statement MESSAGE, contains the message type. |
| sy-msgv1 … sy-msgv4 | c(50) | After the statement MESSAGE, contain the contents of the fields that were used as placeholders in the message. |
| sy-opsys | c(10) | Operating system of the current application server – for example, “SOLARIS”, “HP-UX”. |
| sy-pagno | i | Current page in list creation. |
| sy-pfkey | c(20) | GUI status of the current dynpro. |
| sy-prdsn | c(6) | When printing lists, contains the name of the spool file. |
| sy-repid | c(40) | Name of the current ABAP program. For procedures called externally, name of the framework program of the procedure. If sy-repid is transferred as an actual parameter to an external procedure, the formal parameter is set to the name of the caller. |
| sy-saprl | c(4) | Release status of the AS ABAP, e.g. “46D”, “610″. |
| sy-scols | i | Number of columns of the current screen. |
| sy-slset | c(14) | Variant that was used for filling a selection screen. The associated program name is in sy-cprog. |
| sy-spono | n(10) | When printing lists, contains the name of the spool number. |
| sy-srows | i | Number of lines of the current screen. |
| sy-staco | i | Number of the first column displayed in the list for which a list event has been triggered. Counting begins at 1. |
| sy-staro | i | Number of the list line displayed at the top of the page at the top of the list, for which a list event was triggered. Counting begins at 1 and does not include the page header. |
| sy-stepl | i | Index of the current line in a table control. This is set for every loop pass. |
| sy-subrc | i | Return value that is set by many ABAP statements. In general, the value 0 means that the statement was executed with no problems. Depending on which statement was used to set sy-subrc, the cause of any errors can be derived from the corresponding value. The content of sy-subrc is not defined after statements for which the setting of sy-subrc is not documented explicitly. |
| sy-sysid | c(8) | Name of the AS ABAP, for example “S01″, “K99″.. |
| sy-tabix | i | Line number in the table index of an internal table. Contains the last line accessed with a primary or secondary table index. Is set to 0 when accessed with a hash algorithm. |
| sy-tcode | c(20) | Name of the current transaction code. Initial in background processing unless a transaction was called during background processing. |
| sy-tfill | i | In the statements DESCRIBE TABLE, LOOP AT, and READ TABLE, sy-tfill is filled with the number of lines in the internal table that has been addressed. |
| sy-timlo | t | Local time of the user, for example “152557″. Can be set using GET TIME. |
| sy-title | c(70) | Text that appears in the title bar of the screen. |
| sy-tleng | i | In the statements DESCRIBE TABLE, LOOP AT, and READ TABLE, sy-tleng is filled with the line size of the internal table that is being addressed. |
| sy-tvar0 … sy-tvar9 | c(20) | These system fields can be assigned values in the program. At the event TOP-OF-PAGE, the content of sy-tvar0 to sy-tvar9 replaces the placeholders “&0″ to “&9″ in the list and column headers of the text elements of the program. |
| sy-tzone | i | Time difference to the UTC reference time in seconds – for example, “3600″, “10800″. |
| sy-ucomm | c(70) | Function code that triggered the event PAI. |
| sy-uline | c(255) | Contains a horizontal line of length 255 for displaying in lists. |
| sy-uname | c(12) | User’s logon name – for example, “KELLERH”. |
| sy-uzeit | t | System time (local time of the AS ABAP). Can be set using GET TIME. |
| sy-vline | c(1) | Contains a vertical line (|) for displaying in lists. |
| sy-wtitl | c(1) | In the statements REPORT, PROGRAM, and FUNCTION-POOL, set to “N” if the addition NO STANDARD PAGE HEADING is used, otherwise initial. |
| sy-zonlo | c(6) | Time zone of the user – for example, “CET”, “PST”. |
Today I want to teach you how to call an executable program using ABAP, the function that we will be using is “GUI_RUN”. This function has 2 main parameters, COMMAND and PARAMETER. The COMMAND is used to pass the executable program’s name and the PARAMETER can be used to pass the file name (if any)
If you only supply the COMMAND parameter then it will only call the executable program, but if you want to call a specific file e.g. BOOK1.XLS then you should supply the PARAMETER with the file name.
Here’s the ABAP sample code to call an EXCEL workbook.
01.REPORT Z_Calling_EXE_Program.02. 03.CALL FUNCTION 'GUI_RUN'04. EXPORTING05. COMMAND = 'EXCEL.EXE'06. PARAMETER = 'C:UsersUserDocumentsBOOK1.XLS'.07.* CD = '08.* IMPORTING09.* RETURNCODE = .When you run the program, make sure that you already created the Excel workbook in the destinated folder. You can also change the COMMAND parameter into another type of executable program, e.g. NOTEPAD.EXE, WORD.EXE, etc.
You can also call a web browser, e.g. FIREFOX and immediately open certain website. e.g. www.google.com.
1.CALL FUNCTION 'GUI_RUN'2. EXPORTING3. COMMAND = 'FIREFOX.EXE'4. PARAMETER = 'GOOGLE.COM'.5.* CD = '6.* IMPORTING7.* RETURNCODE = .In today’s tutorial I want to show you how to find User Exits in SD module using SPRO tcode.
1. Execute TCODE SPRO. Click on the “SAP Reference IMG” button.
2. Now expand, Sales and Distribution -> System Modifications -> User Exits. There you will find a list of available user exits for various processes.
3. Click on the Paper icon to show the User Exits list. In this example I want to show all the user exits for Price determination, once I click the “Paper” icon, the pop up window will show you the user exits list.
In this tutorial you will learn how to migrate your existing SmartForms into a PDF-based form in Adobe interactive forms.
Bear in mind, that if you’re using graphics in the SmartForms, be sure to migrate them first into MIME repository.
Now follow these steps to migrate your SmartForms into Adobe Interactive Form.
1. Execute TCODE SmartForms.
2. Select Utilities -> Migration -> Interactive Form -> Export.
3. Enter the name of the SmartForms you want to migrate and the name of the PDF-based target form and also the target interface. By default, the Form target and the interface name are the same but you can change this and use a different name. Press enter to continue.
4. Now you will see the settings dialog box, just leave it as default or change the setting accordingly. You can press F1 on the setting option that you don’t understand to show more detail information. Click continue or enter to proceed.
5. Next you will be prompted with a “Create Object Entry” dialog box, you could include the program into a package and get the tr number and tranport it into the destination client.
Debugging is a daily job for ABAPers, and SAP has an ABAP debugger program that is very easy to use and has a lot of great features to help ABAPer to debug any program.
In this ABAP Debugging Tutorial you will learn how to set a breakpoint on a function module name during run time.
1. Execute any tcode that will run any program, e.g. ZS1234_CCODE
2. Now execute /h tcode, to switch debugger on.
3. Now after execute the program as usual (F8), you will be entering the debugging mode. Now choose Breakpoints > Breakpoint at > Breakpoint at function module
4. Enter the name of the function module you want to debug, click enter to set the breakpoints.
In this tutorial you will learn how to save your internal table data into Excel in run time.
1. Display the Internal table content in debug mode.
2. Right click any where in the content and choose Save to Local file.
3. Choose “Spreadsheet” option and click enter.
4. Choose the folder to save the file.
Here’s a sample code to show / display progress bar using ABAP. We will be using ‘SAPGUI_PROGRESS_INDICATOR’ function module.
01.REPORT Z_PROGRESS_BAR_DISPLAY.02. 03.DATA: progress_txt TYPE c LENGTH 5.04. 05.DO 100 TIMES.06. 07. "Every progress will wait until 0.50 seconds08. 09. WAIT UP TO '0.50' SECONDS.10. 11. progress_txt(3) = sy-index.12. progress_txt+3 = '%'.13. 14. CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'15. EXPORTING16. percentage = sy-index17. text = progress_txt.18. 19.ENDDO.If you need to use variant values as the default values in your selection screen, then you can achieve this by using the “RS_SUPPORT_SELECTIONS” function module.
All you need to do is supply the variant name and it will display the value automatically during the INITIALIZATION event.
Here’s the ABAP SAMPLE CODE.
01.INITIALIZATION.02. 03. data: tp_subrc like sy-subrc.04. data: tp_repid like rsvar-report.05. data: tp_variant like rsvar-variant.06. 07. tp_repid = sy-repid.08. clear tp_variant.09. tp_variant = 'Your Variant Name'.10. 11. "Check if the variant is exist.12. 13. call function 'RS_VARIANT_EXISTS'14. exporting15. report = tp_repid16. variant = tp_variant17. importing18. r_c = tp_subrc19. exceptions20. others = 9.21. 22. if sy-subrc = 0.23. 24. call function 'RS_SUPPORT_SELECTIONS'25. exporting26. report = tp_repid27. variant = tp_variant28. exceptions29. variant_not_existent = 0130. variant_obsolete = 02.31. 32. endif.Once you run the report program (F8) you will see the selection screen are populated by the variant values.
This Idoc Creation Procedure (Step by step Guide) will teach you with all the instructions on creation of Inbound and Outbound IDOC with screen shots for better understanding.
Here is the link to all ABAP Syntaxes.
http://www.sts.tu-harburg.de/teaching/sap_r3/ABAP4/abapindx.htm