SAVE push button

[Former Member]

Hi all,

The requirement is that 'SAVE' button should be on the application tool bar instead of the standard tool bar & should save the following fields : serial number , material,delivery date, status included & plant for report RIEQUI21.

[Former Member]

Hi,

Set the user GUI ststus using SET PF-STATUS. The standard 'SAVE' will be disabled.

Then in ur user defined GUI status create a button with 'SAVE' function code.

After that in report in the event 'AT USER-COMMAND' write the what ever code u want for 'SAVE' button...

Sreedhar

[Former Member]

This is the logic iam following

SELECTION-SCREEN: FUNCTION KEY 1,

FUNCTION KEY 2.

INITIALIZATION.

sscrfields-functxt_01 = 'SAVE'.

sscrfields-functxt_02 = 'EXIT'.

AT SELECTION-SCREEN.

CASE sscrfields-ucomm.

WHEN'FC01'.

CODE....

WHEN 'FC02'.

CODE.....

ENDCASE.

[dani_mn]

Hi,

Open your GUI status with SE41 and create your 'SAVE' button in 'APPLICATION TOOL BAR'. assign a code to it and also icon.

Disable the standard save button.

Activate the status again.

And write your Logic in 'PAI' module for saving.

CASE ok_code.

WHEN 'SAVE'.

do saving.

ENDCASE.

Regards,

Wasim Ahmed

[Former Member]

Hi,

In GUI status(SE41) disable standard SAVE button & create your 'SAVE' button in 'APPLICATION TOOL BAR'. assign a code to it and also icon.

And write your Logic in 'PAI' module for saving.

CASE ok_code.

WHEN 'SAVE'.

ENDCASE.

Regards

Abhishek

[Former Member]

The report RIEQUI21 has one selection screen

[Former Member]

Hi AS,

When you create SETPFSTAUS and double click on it than on application tool bar it may be possible that your SAVE function code is not generated That may be the problem that you write 'save' instead of 'SAVE' when your AT-USSER-COMMAND is triggered that take save not SAVE.

Regards.

Ankur Garg.

[Former Member]

Try this code as a example....

TABLES SSCRFIELDS.

DATA FLAG.

SELECTION-SCREEN BEGIN OF SCREEN 500 AS WINDOW TITLE TIT.

SELECTION-SCREEN FUNCTION KEY 1.

SELECTION-SCREEN FUNCTION KEY 2.

SELECTION-SCREEN END OF SCREEN 500.

AT SELECTION-SCREEN.

CASE SY-DYNNR.

WHEN '0500'.

IF SSCRFIELDS-UCOMM = 'FC01'.

FLAG = '1'.

ELSEIF SSCRFIELDS-UCOMM = 'FC02'.

FLAG = '2'.

ENDIF.

ENDCASE.

START-OF-SELECTION.

SSCRFIELDS-FUNCTXT_01 = 'Button 1'.

SSCRFIELDS-FUNCTXT_02 = 'Button 2'.

TIT = 'Buttons'.

CALL SELECTION-SCREEN 500 STARTING AT 10 10

ENDING AT 10 11.

IF FLAG = '1'.

WRITE / 'Button 1 was clicked'.

ELSEIF FLAG = '2'.

WRITE / 'Button 2 was clicked'.

ENDIF.

Regards

Abhishek

[Former Member]

Hi AS,

Unless the standard PF status is not over written by user defined GUI status, u can't do this...

Aa i said earlier craete one GUI ststus

AND TRY THIS,

INITIALIZATION.

SET PF-STATUS < name >.

Sreedhar

[Former Member]

hi,

use menu painter to create pushbuttons on application tool bar,to create menu bar,to create function keys,etc,

SET PF-STATUS 'ZMATERIAL'.

check out this in the PBO event of a transaction,

best of luck,

regards,

kcc