Enhancing User Experience: Adding F1 Help Documentation to SAP Screens

 

Process on Help Request :-

  • This event calls when we click F1( technical information ) on a field of a screen.
  • We create technical information through SE61 transaction code.
  • Then we call that technical information at our required location.
  • We generally use HELP_OBJECT_SHOW function module to call the created technical information.

Requirement :-

  • In out previous part we have created a F4 help using Process on Value Request event in module pool.



  • Now, Customer wants that there should be some documentation present for Order number, when we press F1 on the field.

Solution :-

  • Step 1 :- Go to SE61 transaction code.



  • Step 2 :- Press F4 on Document class and select the respective format that you want to use.



  • Step 3 :- Give a name to the text and click on create button and then provide the details as shown below.



  • Step 4 :- Save the text.



  • Step 5 :- Now Open the Module Pool Program that we have used in the previous part → Click on object list display to navigate to SE80.



  • Step 6 :- Go to flow logic of screen 100 and write the below code.



  • Step 7 :- Double click on the module and create a master program.



  • Step 8 :- Write the required logic in the above module.

  • Step 9 :- Call the function module HELP_OBJECT_SHOW.



Execute the Program :-



  • Press F1 on the field order number.


  • We can see the same text that we have written while creating the document.

Important Questions and Answers :-

1. What is the significance of leave to screen 0 ?

Ans :- Go to the previous stacked screen.

2. What is the difference between CALL SCREEN <screen no> and LEAVE TO SCREEN <screen no>?

Ans :- CALL SCREEN <screen no> calls the specified screen by adding the specified screen to the stack, whereas LEAVE TO SCREEN <screen no> calls the specified screen by replacing the last stacked screen.

Comments

Post a Comment

Popular posts from this blog

Understanding Different Types of SAP Function Modules: Normal, RFC, and Update

Image
  1. Normal/Regular Function Module :- It can be called inside the system. Here Pass by value + Pass by reference both is fine. 2. RFC Function Modules :- You can call from same system or from another possible. In RFC function module you can only have pass by value. In the same system if you are going to add the DESTINATION NONE’ while calling the RFC then it’ll be called in separate session. 3. UPDATE Function Modules :- This is generally used to update the database record. Update Function Module can be called from the same system. ( Background RFC / trfc / grfc ) This is used to achieve generally the SAP LUW. Some time we use from performance perspective also. When COMMIT WORK gets executed then Update starts getting executed. Important Questions on Update Function Modules :- When Update function Module gets Triggered ? ON COMMIT WORK IF a update function module gets failed, under which transaction we can see that ? OR What is the T-Code for moni
Read more

Unlocking SAP ABAP Secrets: Interactive Classical Reports with GET CURSOR, At User Command, and a Comparison of HIDE Statements

Image
 Welcome back everyone, We were discussing about the interactive classical reports, so let’s continue it. Interactive Classical Reports- GET CURSOR :- In Interactive Classical Reports, GET CURSOR statement is used to create secondary list according to cursor position. The parameter FIELD provides the name of an output field. The parameter VALUE provide the output value. Syntax : GET CURSOR FIELD <lv_field> VALUE <lv_value>. In the above syntax - the field name and field value will be returned in to variables lv_field and lv_value respectively. Requirement :- If you remember, In our last two blog, We have been displaying the order header table in a basic list and order item table in the secondary list. We have used SY-LISEL and HIDE statements to achieve the requirement. Now, we have to use the get CURSOR to achieve the same to same requirement. Code :- ************************************************************* *Start of Program *Declaring Strcutrure
Read more

Mastering ABAP: A Step-by-Step Guide to Function Modules and Groups for Modularized Programming

Image
  Function Modules :- It is a modularization technique. The transaction code to create a function module is SE37. To create a function module, we need to create a function group. Function Group :- Function group is a container for the function modules. The transaction code to create a function group is SE80. A function group can store up to 99 function modules. Requirement :- let’s create a function module for sum of two numbers. 1. Creation of function group :- Step 1 :- Go to SE80 transaction code → Object Navigator. Step 2 :- From the drop down select function group. Step 3 :- Give a name of function group. Step 4 :- press enter. Step 5 :- Click on yes a popup screen will appear. Step 6 :- Give short description → press enter → Assign package and transaction request and press enter. Step 7 :- Right click on function group and click on activate to activate the function group. Step 8 :- You will see two includes, will be added after ac
Read more