Creation of Execution Variants.
An execution variant is a set of predefined values that can be used to influence the behavior of a program or report. These variants allow a program to be executed with different configurations without modifying the source code.
These execution variants prove highly beneficial for end-users during the execution of transactions in the productive environment. They are also invaluable for ABAP consultants and functional consultants to test transactions during the testing phase.
Creation of a variant:
- At execution moment, in the selection screen, select the wanted options to be configured as default in the variant and click on "Save". Then, choose the name for this Variant and provide a description to clearly understand what it will display. This way, we can execute a "Shortcut" for the parameters previusly selected.
Creation of transactions associated with reports
For end-users to use the programs we create in the productive environment, we need to create transaction codes associated with the programs. Since users don't have direct access to execute programs through transactions like SE38 or any other development transaction such as SE80, we use the standard transaction SE93 to create these transactions. We can create and update transactions named Z and view standard transactions.
Steps to create a Z transaction via transaction SE93:
- Start searching for SE93 transaction.
- Enter the "Code" of the new transaction and click Create. (Remember start with Z)
- A dialog window appears, where you provide a brief "Description" and select the "Transaction Type". Click "Continue".
- On the next screen, enter:
-
Program name
-
Selection Screen (screen 1000 is the default for reports)
-
In the Start With Variant field, add the name of a variant for the transaction to execute.
-
In the Authorization Object field, you can add the name of an authorization object for the transaction.
-
Leave the Transaction Classification option selected as Professional User Transaction, as it comes by default.
-
In the GUI Support field, check all three available options: SAP GUI for HTML, SAP GUI for Java, and SAP GUI for Windows.
- After completing the above, "Save".
- To execute the new transaction, type it in the Command Field and press Enter to display it on the screen.
Transaction Types
-
Dialog or Dynpro: Transactions linked to a series/sequence of screens.
-
Report: Calls an ABAP report. It maps to the selection screen of an executable program and usually executes a submit to the executable program.
-
Object-Oriented: Linked to a method of a local or global class.
-
Variant: Existing transactions with a predefined variant.
Utilizing Colors in Reports
To choose colors when printing on-screen in interactive and classic reports, execute the statement FORMAT COLOR before the WRITE statement, like this:
FORMAT COLOR COL_GROUP INTENSIFIED ON.
WRITE: 'Entry Date is: ', p_date.
FORMAT COLOR 1.
WRITE: 'Entry Date is: ', p_date.
To see the options, press F1 on the FORMAT COLOR statement, and details will expand.
Syntax of the color Value in COL Color
| Syntax of color |
Value in col |
Color |
| { COL_BACKGROUND } |
0 |
GUI-dependent |
| { 1 | COL_HEADING } |
1 |
Gray-blue |
| { 2 | COL_NORMAL } |
2 |
Light gray |
| { 3 | COL_TOTAL } |
3 |
Yellow |
| { 4 | COL_KEY } |
4 |
Blue-green |
| { 5 | COL_POSITIVE } |
5 |
Green |
| { 6 | COL_NEGATIVE } |
6 |
Red |
| { 7 | COL_GROUP } |
7 |
Purple |
E.g
DATA col TYPE i VALUE 0.
DO 8 TIMES.
col = sy-index - 1.
FORMAT COLOR = col.
WRITE: / col COLOR OFF,
'INTENSIFIED ON' INTENSIFIED ON,
'INTENSIFIED OFF' INTENSIFIED OFF,
'INVERSE ON' INVERSE ON.
ENDDO.
