SAP MS_ACCEPTANCE_POPUP Function Module for Dialog Box: Acceptance Document Header Data
MS_ACCEPTANCE_POPUP is a standard ms acceptance popup SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Dialog Box: Acceptance Document Header Data processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for ms acceptance popup FM, simply by entering the name MS_ACCEPTANCE_POPUP into the relevant SAP transaction such as SE37 or SE38.
Function Group: MLSR
Program Name: SAPLMLSR
Main Program: SAPLMLSR
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MS_ACCEPTANCE_POPUP pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'MS_ACCEPTANCE_POPUP'"Dialog Box: Acceptance Document Header Data.
EXPORTING
I_EKKO_BUKRS = "
IMPORTING
E_IMKPF = "Header Data: Acceptance Document
EXCEPTIONS
NO_DATA = 1
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLMLSR_001 User Exit: Control of Service Entry Mode
EXIT_SAPLMLSR_010 Set Entry Sheet Header Data
EXIT_SAPLMLSR_020 Transfer of Data to Entry Sheet User Screen
EXIT_SAPLMLSR_021 Adoption of Data from Entry Sheet User Screen
IMPORTING Parameters details for MS_ACCEPTANCE_POPUP
I_EKKO_BUKRS -
Data type: EKKO-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for MS_ACCEPTANCE_POPUP
E_IMKPF - Header Data: Acceptance Document
Data type: IMKPFOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_DATA -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MS_ACCEPTANCE_POPUP Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_e_imkpf | TYPE IMKPF, " | |||
| lv_no_data | TYPE IMKPF, " | |||
| lv_i_ekko_bukrs | TYPE EKKO-BUKRS. " |
|   CALL FUNCTION 'MS_ACCEPTANCE_POPUP' "Dialog Box: Acceptance Document Header Data |
| EXPORTING | ||
| I_EKKO_BUKRS | = lv_i_ekko_bukrs | |
| IMPORTING | ||
| E_IMKPF | = lv_e_imkpf | |
| EXCEPTIONS | ||
| NO_DATA = 1 | ||
| . " MS_ACCEPTANCE_POPUP | ||
ABAP code using 7.40 inline data declarations to call FM MS_ACCEPTANCE_POPUP
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.| "SELECT single BUKRS FROM EKKO INTO @DATA(ld_i_ekko_bukrs). | ||||
Search for further information about these or an SAP related objects