How to add push button in function module

I want to add Push button( yes/no) in same screen. I used POPUP_TO_CONFIRM,
but this popup is coming on next screen when I click on cancel button.

There is no scope to create a push button in application tool bar. Instead of that we can add in a menu bar.

Similar Messages

How to add push buttons in out put screen of ALV

Hai,
How to add push buttons in out put screen of ALV (tool bar) with out using classes or methods .I want to know using normal ALV .
Thanks in advance .
kiran

Hi Kiran,
Here is the sample code.If you are using reuse_alv_grid_display, no need to write code in PBO.
Just double click the 'TEST' which is written in code.Then create a GUI Status.In Application toolbar,type the name of the button you want(say BUTTON).Then double click that name.Then enter the ICON name and function text.Activate it.This itself will work.If you want all the functionalities,then try to do as Vinod told.
TYPE-POOLS: slis.
DATA: i_qmel LIKE qmel OCCURS 0.
data v_repid type repid.
SELECT * FROM qmel INTO TABLE i_qmel.
v_repid = sy-repid.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
 I_CALLBACK_PROGRAM = v_repid
 I_CALLBACK_PF_STATUS_SET = 'SET_PF_STATUS'
 I_CALLBACK_USER_COMMAND = 'USER_COMMAND'
 i_structure_name = 'QMEL'
TABLES
 t_outtab = i_qmel
EXCEPTIONS
 program_error = 1
 OTHERS = 2.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
form set_pf_status using rt_extab type slis_t_extab.
set pf-status 'TEST'.
endform.
FORM user_command USING ucomm LIKE sy-ucomm
 selfield TYPE slis_selfield.
data lv_ucomm type sy-ucomm.
lv_ucomm
= sy-ucomm.
CASE lv_ucomm.
 WHEN 'BUTTON'. "Double Click line Item
 call transaction 'MM01'.
endcase.
endform.

How to Add Push Button On Selection Screen

Hi Experts,
How to add Push button on Selection Screen.
Points will b rewarded for useful help.
Bohra.

Hi,
To create a pushbutton on the selection screen, you use:
SELECTION SCREEN PUSHBUTTON [/]<pos(len)> <push>
USER-COMMAND <ucom> [MODIF ID <key>].
The [/]<pos(len)> parameters and the MODIF IF addition have the same function as for the formatting options for underlines and comments.
<push> determines the pushbutton text. For <push>, you can specify a text symbol or a field name with a maximum length of eight characters. This character field must not be declared with the DATA statement, but is generated automatically with length <len>. The field must be filled before the selection screen is called.
For <ucom>, you must specify a code of up to four characters. When the user clicks the pushbutton on the selection screen, <ucom> is entered in the UCOMM of the SSCRFIELDS interface work area. You must use the TABLES statement to declare the SSCRFIELDS structure. The contents of the SSCRFIELDS-UCOMM field can be processed during the AT SELECTION-SCREENevent.
Ex.
REPORT DEMO.
TABLES SSCRFIELDS.
DATA FLAG.
SELECTION-SCREEN:
BEGIN OF SCREEN 500 AS WINDOW TITLE TIT,
BEGIN OF LINE,
PUSHBUTTON 2(10) BUT1 USER-COMMAND CLI1,
PUSHBUTTON 12(10) TEXT-020 USER-COMMAND CLI2,
END OF LINE,
BEGIN OF LINE,
PUSHBUTTON 2(10) BUT3 USER-COMMAND CLI3,
PUSHBUTTON 12(10) TEXT-040 USER-COMMAND CLI4,
END OF LINE,
END OF SCREEN 500.
AT SELECTION-SCREEN.
CASE SSCRFIELDS.
WHEN 'CLI1'.
FLAG = '1'.
WHEN 'CLI2'.
FLAG = '2'.
WHEN 'CLI3'.
FLAG = '3'.
WHEN 'CLI4'.
FLAG = '4'.
ENDCASE.
START-OF-SELECTION.
TIT = 'Four Buttons'.
BUT1 = 'Button 1'.
BUT3 = 'Button 3'.
CALL SELECTION-SCREEN 500 STARTING AT 10 10.
CASE FLAG.
WHEN '1'.
WRITE / 'Button 1 was clicked'.
WHEN '2'.
WRITE / 'Button 2 was clicked'.
WHEN '3'.
WRITE / 'Button 3 was clicked'.
WHEN '4'.
WRITE / 'Button 4 was clicked'.
WHEN OTHERS.
WRITE / 'No Button was clicked'.
ENDCASE.
This example defines four pushbuttons on a selection screen that is displayed as a
dialog box. The selection screen is defined in a statement chain for keyword
SELECTION-SCREEN.
If the text symbols TEXT-020 and TEXT-040 are defined as 'Button 2' and 'Button 4',
the four pushbuttons appear as follows on the selection screen displayed as a dialog box.
Regards,
Bhaskar

How to add push button in application tool bar in SAP transaction VA01

How to add push button in application tool bar in SAP standard transaction VA01 and how to implement the code for that function code.

There is no scope to create a push button in application tool bar. Instead of that we can add in a menu bar.

How to add push button in alv display with out class or method

Hai,
How to add push buttons in out put screen of ALV (tool bar) with out using classes or methods .I want to know using normal ALV .
Thanks in advance .
kiran

You should post your question in the ABAP forum.
ABAP Development

How to add push button in report.

Hi,
how to add a push button in the standard list report and on clicking which the line-size of the screen should reduce from 300 to 100.
how to proceed.
Can anyone help me.
Regards
Guhapriyan

Hii Guhapriyam,
You can ceate PUSHBUTTON in selection-screen like Below
SELECTION-SCREEN PUSHBUTTON 2(10) text-004 USER-COMMAND CL1.
Create a variable to hold the processed PUSHBUTTON value like
DATA v_flag TYPE flag.
The PUSHBUTTON will be processed at the event AT SELECTION-SCREEN. So write your code like below
AT SELECTION-SCREEN.
   IF sy-ucomm EQ 'CL1'.
     v_flag = 1.          "Buttob clicked
   ENDIF.
START-OF-SELECTION.
IF v_flag EQ 1.
     NEW-PAGE LINE-SIZE 100.
ENDIF.
OR
The best way of doing this by setting PF-STATUS like
START-OF-SELCTION.
SET PF-STATUS 'ZSTATUS'. "Double click on this and set the pushButton in standard toolbar option and in function key specify the BACK, EXIT and CANCEL button .
Then write your logic at the event AT USER-COMMAND.
AT USER-COMMAND.
   CASE sy-ucomm.
     WHEN 'RED'.
       NEW-PAGE LINE-SIZE 100.
     WHEN 'BACK' OR 'CANCEL' OR 'EXIT'.
       LEAVE SCREEN.
     WHEN OTHERS.
   ENDCASE.
regards
Syed

How to add push button on UI?

Hi,
I would like to add a push button 'PROCESS' on one assignment block. When user selects the pushbutton I would like to execute some custom functionality. How do I achieve this?
Regards,
Akash

Hi,
Please add the below code in the htm page of your view
<thtmlb: button id = Search
on Click = Search
text = Search
tooltip = Search />
Regards,
Lakshmi.Y
Edited by: Lakshmi Soujanya on Jun 7, 2011 11:09 AM
Edited by: Lakshmi Soujanya on Jun 7, 2011 11:11 AM

How to add Image in "SX_OBJECT_CONVERT_OTF_PDF" Function module

Hi,
We have scenario to add a BMP image from report to PDF format ,they are using the SX_OBJECT_CONVERT_OTF_PDF function module to generate the report in PDF ,so we want to know how to add a image(BMP) for this function module or is there any other function module to get the image in PDF format.
Replies would be appreciated.
Regards
Raghava

Hi Brad Bohn ,
We have the scenario were in we have two tabs (If click first tab output is displayed in excel with image using OLE functionality) for second tab output is displayed in PDF by using SX_OBJECT_CONVERT_OTF_PDF-Function module without the image(*.bmp).
Our requirement is to get image in PDF.
Please let us know which is the way to approach this scenario.
Regards,
Raghava

How to add a created Z function module to the existing list in WE21

Hi all,
There is some existing function modules ( like EDI_PATH_CREATE_CLIENT_DOCNUM ) in WE21 in the function module field.
here, i need to create one Z function module as per user requirement & want to add to that list. is it possible???
actually, i want the file name format is like
" Document Number_YYYYMMDDHHMMSS.xml ". but existing function modules are not giving this format.do anybody give any idea.
correct answers will be rewarded.
Thanks & Regards

HI Pabitra,
Yes, can always change the existing fm and add it with message type as follows pls note step 7 and step 8. (for inbound it is we42 and for outbound it is we41 )
Basic IDOCs have supplied by SAP with standard structure. (Segments). You can extend them with your own segments.
IDOCs does have unique number. They contain control, data, and status records.
Useful Transaction Codes:
WEDI : IDoc Menu
WE02 : IDoc List (can enter IDoc number to select on)
WE05 : IDoc List
WE19 : Transaction WE19 can be used to test the IDoc
WE30 : IDoc Type Development: Initial Screen
WE31: Development Segments: Initial Screen
WE60 : Documentation for IDoc Types. This allows you to view the IDoc you have created.
WE81 : Display View EDI: Logical Message Types: Overview
WE82: Display View Message Types and Assignment to IDoc Types: Overview
WE21 - Creation of POrt
WE20 - Partner Profile creation
SALE - ALE (Application Linking and Enabling) settings
For Outbound ALE Configurations: (Example)
IDoc definitions and necessary ALE configurations settings for the outbound .
Create Idoc segments Transaction WE31.
Create Idoc type Transaction WE30.
Create Message Type Transaction WE81.
Assign Message Type to Idoc type Transaction WE82.
Create a distribution Model - Transaction BD64
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
for creating a IDOC
see the below steps for outbound processing IDOCS..
2.1 Outbound Interface
PROCESS DIAGRAM
Outbound Interface
1. Analyse Hierarchy Levels
2. Create New segment
3. Create New IDoc Type
4. Create New Message Type
5. Link Message with IDoc Type
6. Create an entry in EDP13 via transactions WE20 and BD64
7. Populate the Custom IDoc via ABAP Program
7b Error Handling
7c. Send Status Email
8. Test the Population of the Custom IDoc
Step 1 Analyse Hierarchy Levels:
Analyse the data relationships being processed in the interface. Define the appropriate hierarchical Parent-to-Child relationships.
Navigate to transaction code WEDI
Transaction WEDI displays the IDOC main menu. This allows navigation around the various development and control areas to create a customised IDOC.
Step 2 Create a new segment:
via wedi : Development - IDOC Segments or Transaction code WE31.
Enter segment name and click on Create.
The? name of the segment type must start with Z1 , and have a maximum of eight characters.
Enter description and enter the relevant field names and data elements.
The segment should represent a structure in the program so for? each field in the segment a field name and a data element must be defined.
Save the segment and enter Person Responsible and Processing Person .
Go to Edit and Set Release.
Repeat this procedure for each new Segment in the IDOC.
Step 3 Create a new IDOC Type
via wedi Development - IDOC Types or Transaction WE30.
Enter segment name (starting with Z), click on Basic Type and then Create.
Create as new, enter Person Responsible and Processing Person and enter description.
On Create Basic Type screen decide where segments should be inserted and go to Edit/Create Segment.
Complete relevant fields in the Maintain Attributes screen:
From the relevant segments created in Step 2 enter the Segment type and if mandatory segment.
The Minimum and Maximum number of segments to be allowed in the sequence. (One minimum and one maximum if segment is mandatory).
The Parent Segment and Hierarchy Level will be automatically created depending on where in the IDOC tree you decided to create that particular segment.
Repeat this process for each segment needed in the IDOC type, deciding whether to add the next segments at the same level or as a Child.
When IDOC created return to initial screen. Go to Edit and Set Release.
Go to Transaction WE60 to view the IDoc Type you have created.
Step 4 Create new Message Type
via wedi Development - Message Types or Transaction WE81.
Display/Change and click on New Entries
Create a new Message Type and Save.
Step 5 Link Message Type to IDOC Type
via wedi Development - IDOC Type/Message or Transaction WE82.
Display/Change and then click on New Entries.
Enter Message Type, Basic Type (IDOC Type) and Release (46C) and Save.
Step 6 Create an entry in EDP13 via transactions WE20 and BD64.
The partner profile for the Idoc must be set up and generated in the transaction BD64 and transaction WE20.
WE20 Add Message Type to appropriate Partner Type, Enter Message Type, Receiver Port and Idoc Type and Save.
BD64 Create a Model View, Enter Sender and Receiver Ports, Attach Message Type. Go to Environment on Menu and click on Generate Partner Profiles and generate (not save) profile.
Step 7 Populate the custom IDOC via ABAP Program
See Test Program ZOUTBD_IDOC_TEMPLATE, Appendix IV.
Create an Internal Table for each segment type, this should be exactly the same structure as the segment type.
The control record is filled into a structure like EDIDC. The message type and the Idoc type for the Idoc must be populated into the eddic structure.
- PERFORM populate_Control_structure USING c_mestyp
c_SEGMENT_type1.
The data segments are filled into a structure like edidd-sdata; sdata and the segment name are populated into the edidd structure.
- PERFORM transfer_Parent_data_to_seg.
The standard SAP function module MASTER_IDOC_DISTRIBUTE is called to pass the populated IDOC to the ALE Layer.
- PERFORM master_idoc_distribute.
NOTE: This function module is only called for stand alone programs and Shared Master Data programs (SMD). It is not called when using extensions or output determination.
The ALE Layer handles the sending of the IDOC to the receiving system.
Error Handling (see Step 7b).
Commit work.
Project SpecificStep 7b Error Handling
Analyse which fields in the interface are mandatory for the receiving system and who needs to receive error notification.
Declare a structure of type MCMAILOBJ for sending instructions.
Enter values for the internal table based on structure MCMAILOBJ
For selection processes, on SY-SUBRC checks and where fields are mandatory for the receiving system; insert Function Module MC_SEND_MAIL.
Enter values in the following parameters: -
MS_MAIL_SENDMODE = B (Batch Mode)
MS_MAIL_TITLE = 'Mail Title'
MS_MAIL_DESCRIPTION = Error description (e.g. MATNR not given)
MS_MAIL_RECEIVER = Name of Receiver (To be determined)
MS_MAIL_EXPRESS = E (Express Delivery)
MS_MAIL_DLINAME = Leave Blank
MS_MAIL_LANGU = 'E' (Language)
MS_MAIL_FUNKOBJ_NAME = Leave Blank
TABLES
MS_MAIL_CONT = I_MCMAILOBJ
Note:
It has to be determined separately for each interface how these errors and mail notifications are to be grouped dependant upon the number of errors that are potentially likely. One possible approach is to send an email for each reason for rejection and include all the records that failed for that reason in the mail notification. Another possible approach is to send an email for every failure.
When error checking for mandatory fields it is common SAP practice to reject a record on its first failure (irrespective of subsequent errors in that record)
Step 7
(Transaction WE57)
Assign the custom function module to the IDoc type and the message type.
Set function module to type F and direction 2 for inbound.
Step 8
(Transaction WE42)
Create a new process code and assign it to the function module. The process code determines how the incoming IDoc is to be processed in SAP.
Step 9
(Transaction BD67)
Assign the function module to the process code created above. Got to New Entries and enter the process code and the function module name.
Step 10
(Transaction WE20 and Transaction BD64)
Create a partner profile for your message and ensure that in transaction WE20 the process code is the one that points to your function module. (See step 6 of creating Outbound Idocs).
Step 11
Ensure that error handling functionality is present.
If u still have doubt, i can send u the print screen doc - hope this helps u
Reward pts if found usefull :)
regards
Sathish

How to add push button in alv list

Dear all,
     I am doing ALV report, in that i have some requirements as mentioned below
6.     In the main report screen, each row should have a selection button at the left end. The entire row should be selectable by clicking on this button. By clicking on the button a second time the row gets deselected. The user should be able to select only one row at a time (i.e. he should not be able to select multiple rows simultaneously).
7.     All Report screens should have standard SAP Navigation buttons.
8.     The main Report Screen should have a Refresh Button. When the user clicks on this Refresh button the program should remember and re-execute (i.e. refresh) the last selection of the user in the Selection Screen above and the Main Report Screen should be re-displayed accordingly.
pleae help on me,
Regards ,
Sudhakar.

hi
good
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e8a1d690-0201-0010-b7ad-d9719a415907
http://www.sap-img.com/abap/what-are-the-events-in-alv.htm
reward point if helpful.
thanks
mrutyun^

Radio buttons in function module.

Hi,
I have developed a function module which internally calls abap report with SUBMIT command. However, the abap report has radio buttons on selecton screen. So I would like to know how to define radio buttons in function module or is there any alternative to overcome this problem?
ABAP code in function module :
submit zodmr_report    with p_vkorg = bukrs
                         with s_off in vkbur
                         with s_vtweg in vtweg
                         with s_spart in spart
                         with s_dsa in dsa
                         with s_ext in allocation_id
                         with p_yyyymm = year_month
                         and return.
( ABAP report "ZODMR_REPORT" has two radio buttons)
Regards,
Santosh

Hi,
To the best of my knowledge you need to create an IMPORT parameter of type SY-DYNNY And pass your selection screen to the FM. If this will not serve your purpose, then Instead of Standard Selection Screen with number 1000, use custom defined Screen number.
Cheers
Ram

How to find out the inbound function module in the extended idoc

Hi,
how to find out the inbound function module in the extended idocs
Thanks .

through we41/we42 you can find the inbound function module.......
or
thorough we19(idoc test tool) ....
give the input as message type or basic idoc..
press exec...
then you can find th button on application tool bar as inbound funtion module....
from here also you can find..........
<REMOVED BY MODERATOR>
Khasimsa
Edited by: Alvaro Tejada Galindo on Apr 14, 2008 1:34 PM

How to add a button to the grouped data in an AdvancedDataGrid?

Hi,
Can anyone please suggest how to add a button to the grouped data in the AdvancedDataGrid?
I have tried extending the AdvancedDataGridGroupItemRenderer and using it as the groupItemRenderer but its not reflecting.
For the leaf node the itemRenderer property works just fine.
Please help!

HI ,
I want to add a push button on the ALV list out put which is comming as a pop up and I want this using classes and methods.
I have got a method IF_SREL_BROWSER_COMMANDS~ADD_BUTTONS from class cl_gos_attachment_list but still I am unable to get any additional button on the output ALV popup.
Please help.
Regards,
Kavya.

How to ijntroduce PUSH Button in KD_GET_FILENAME_ON_F4

Dear Experts,
I am new to ABAP.
I know how to use push button in Sel-Screen. But my requirement is:
1)How can I use a push button in "KD_GET_FILENAME_ON_F4" so that on hitting the push button a PopUp screen appears.
2) This Pop up screen should be a file directory screen from which I can select a file.
3) This file on one click should get considered as "file_name" of the call function "KD_GET_FILENAME_ON_F4."
Looking forward for advise from experts.
Regards
Chandan Kumar

Dear Mr Klaus,
Thanks for your reply. The method suggested by you will definitely help the user to directly open a file dialogue box. But I want the code to make it more simpler for the user. After I execute the code The use should get a Push Button. On hitting this push button a POP UP screen should appear. This pop up screen should lear us to the target folder.
In your suggestion it was possible to open a folder path pop up screen. just I want to intriduce a PUSH button there. Also I want multi selection to be possible. In your suggestion above when I wrote the code as:
DATA: file_str1 type string.
data: it_tab TYPE STANDARD TABLE OF file_table,
 lw_file LIKE LINE OF it_tab,
 gd_subrc TYPE i.
SELECTION-SCREEN begin of block blk with frame title text-100.
SELECTION-SCREEN SKIP 2.
parameters : p_file like rlgrap-filename .
SELECTION-SCREEN end of block blk.
*F4 input file
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
CALL METHOD cl_gui_frontend_services=>file_open_dialog
EXPORTING
window_title = 'Select only Text File'
default_filename = '.azt'
multiselection = 'X'
CHANGING
file_table = it_tab
rc = gd_subrc.
READ TABLE it_tab INTO lw_file INDEX 1.
p_file = lw_file-FILENAME.
Start-of-Selection.
file_str1 = P_file.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
 filename = file_str1
* filename = '\\10.10.1.92\Volume_1\_projekte\Zeiterfassung-SAP\test.azt'
tables
 data_tab = it_string
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
In the above code when I use Multiselection = 'X' then in the folder pop up multiselection is possible but the multiselection deosn't
gets selected for upload.
Looking forward for your suggestions.
That is my requirement.
Regards,
Chandan

Add push button tp Micro-controller

Hi All,
I appreciate if you read my problem and answer me:).
I am using CSMB12 micro controller, which has port S as a SCI. 2 pins of this port is TXT and 2 pins are RXT. Right now i used one pair of these pins for both Bluetooth and LCD. now I need to add push button to my system, whenever I click on the push button, my micro start working and calculating the program, and whenever i click it again, it stops calculating and show the value on the LCD, and use another button for sending data by Bluetooth.
my problem is:
1-I used one SCI for both LCD and Bluetooth, how can I separate them?
2-Do you have a y sample codes for adding push button switch?
If you need my code, i can upload it.
really thank you.
Regards,
Sb

Just create the the UINavigationController wherever you need to show its root view controller. With no storyboard segue you would typically use something like this. I initiated from a UIButton action for this example. Instead of a generic UITableViewController, use the custom view controller class of your root view controller (PauseMenuTableViewController?). If you are using old-school nib/xib, replace initWithStyle with initWithNibName.
- (IBAction)showWhateverViewButtonClick:(id)sender {
    // create whatever view controller type will be the root of the navigation controller
    UIViewController *rootViewController = [[UITableViewController alloc] initWithStyle:UITableViewStylePlain];
    // create a navigation controller using that view controller for the root
    UINavigationController *navigationController = [[UINavigationController alloc] initWithRootViewController:rootViewController];
    // show the navigation controller (modal)
    [self presentViewController:navigationController animated:YES completion:NULL];

How to add push button in function module

Similar Messages

Maybe you are looking for