You can of course define a popup-type dynpro (modal dialog box) but the classic BAdI ME_PROCESS_REQ_CUST might (will) disallow such call in POST method during the commit processing (as dynpro interaction will trigger some implicit dB commit) so you should execute the pop-up in the overall CHECK method (always executed before SAVE) and save the data in the POST method or perform on commit (using a call function in update task)
But is not this pop-up a solution and not a requirement? Could you consider to add those fields in the transaction customer subscreen (e.g. with Enhancement MEREQ001) and save those in POST method
any of this below function can help you:
C14A_POPUP_ASK_ADDINF
C14A_POPUP_ASK_DATA_OVERWRITE
C14A_POPUP_ASK_FILE_OVERWRITE
C14A_POPUP_ASK_IMPORT
C14A_POPUP_ASK_OBJID_OVERWRITE
C14A_POPUP_ASK_TO_CONTINUE
C14A_POPUP_ASK_TO_CONTINUE_F4
C14A_POPUP_CANCEL
C14A_POPUP_CONFIRM_AVGEN_START
POPUP_FOR_INFORMATION
POPUP_TO_DECIDE_WM
POPUP_TO_FETCH_ONE_VALUE
POPUP_WITH_2_BUTTONS_TO_CHOOSE
POPUP_WITH_3_BUTTONS_TO_CHOOSE
POPUP_TO_DISPLAY_ADD_FIELDS
POPUP_TO_DISPLAY_VALUE
POPUP_GET_VALUES
POPUP_TO_FILL_COMMAND_LINE allows ONE line of user input.
"I guess, I need to create a new screen for popup in SE51 and call it on SAVE hitting"
Yes.
Look into the documentation of classical dynpros to find out more.
Add comment