SAP EXIT_SAPMM06E_024 Function Module for Reference Dates Set in PO Generation
EXIT_SAPMM06E_024 is a standard exit sapmm06e 024 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Reference Dates Set in PO Generation 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 exit sapmm06e 024 FM, simply by entering the name EXIT_SAPMM06E_024 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XEXPEX
Program Name: SAPLXEXPEX
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function EXIT_SAPMM06E_024 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 'EXIT_SAPMM06E_024'"Reference Dates Set in PO Generation.
EXPORTING
I_EKET = "Scheduling Agreement Delivery Schedules
I_EKPO = "Purchasing Document Item
I_EKKO = "Purchasing Document Header
I_EVENT = "Expediting Event
I_BASELINE = "User Exit Baseline is Active
I_CURRENT = "User Exit Plan is Active
I_FORECAST = "User Exit Forecast is Active
I_ACTUAL = "Actual User Exit is Active
IMPORTING
E_XBASELINE = "Baseline Date
E_XCURRENT = "Planned Date
E_XFORECAST = "Forecast Date
E_XACTUAL = "Actual date
E_EXP_PRIO = "Event Priority
IMPORTING Parameters details for EXIT_SAPMM06E_024
I_EKET - Scheduling Agreement Delivery Schedules
Data type: EKETOptional: No
Call by Reference: Yes
I_EKPO - Purchasing Document Item
Data type: EKPOOptional: No
Call by Reference: Yes
I_EKKO - Purchasing Document Header
Data type: EKKOOptional: No
Call by Reference: Yes
I_EVENT - Expediting Event
Data type: TXPDAT-EVENTOptional: No
Call by Reference: Yes
I_BASELINE - User Exit Baseline is Active
Data type: TSTDEV-USX_BASOptional: No
Call by Reference: Yes
I_CURRENT - User Exit Plan is Active
Data type: TSTDEV-USX_CUROptional: No
Call by Reference: Yes
I_FORECAST - User Exit Forecast is Active
Data type: TSTDEV-USX_FOROptional: No
Call by Reference: Yes
I_ACTUAL - Actual User Exit is Active
Data type: TSTDEV-USX_ACTOptional: No
Call by Reference: Yes
EXPORTING Parameters details for EXIT_SAPMM06E_024
E_XBASELINE - Baseline Date
Data type: TXPDAT-XBASELINEOptional: No
Call by Reference: Yes
E_XCURRENT - Planned Date
Data type: TXPDAT-XCURRENTOptional: No
Call by Reference: Yes
E_XFORECAST - Forecast Date
Data type: TXPDAT-XFORECASTOptional: No
Call by Reference: Yes
E_XACTUAL - Actual date
Data type: TXPDAT-XACTUALOptional: No
Call by Reference: Yes
E_EXP_PRIO - Event Priority
Data type: TXPDAT-EXP_PRIOOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for EXIT_SAPMM06E_024 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_i_eket | TYPE EKET, " | |||
lv_e_xbaseline | TYPE TXPDAT-XBASELINE, " | |||
lv_i_ekpo | TYPE EKPO, " | |||
lv_e_xcurrent | TYPE TXPDAT-XCURRENT, " | |||
lv_i_ekko | TYPE EKKO, " | |||
lv_e_xforecast | TYPE TXPDAT-XFORECAST, " | |||
lv_i_event | TYPE TXPDAT-EVENT, " | |||
lv_e_xactual | TYPE TXPDAT-XACTUAL, " | |||
lv_e_exp_prio | TYPE TXPDAT-EXP_PRIO, " | |||
lv_i_baseline | TYPE TSTDEV-USX_BAS, " | |||
lv_i_current | TYPE TSTDEV-USX_CUR, " | |||
lv_i_forecast | TYPE TSTDEV-USX_FOR, " | |||
lv_i_actual | TYPE TSTDEV-USX_ACT. " |
  CALL FUNCTION 'EXIT_SAPMM06E_024' "Reference Dates Set in PO Generation |
EXPORTING | ||
I_EKET | = lv_i_eket | |
I_EKPO | = lv_i_ekpo | |
I_EKKO | = lv_i_ekko | |
I_EVENT | = lv_i_event | |
I_BASELINE | = lv_i_baseline | |
I_CURRENT | = lv_i_current | |
I_FORECAST | = lv_i_forecast | |
I_ACTUAL | = lv_i_actual | |
IMPORTING | ||
E_XBASELINE | = lv_e_xbaseline | |
E_XCURRENT | = lv_e_xcurrent | |
E_XFORECAST | = lv_e_xforecast | |
E_XACTUAL | = lv_e_xactual | |
E_EXP_PRIO | = lv_e_exp_prio | |
. " EXIT_SAPMM06E_024 |
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPMM06E_024
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 XBASELINE FROM TXPDAT INTO @DATA(ld_e_xbaseline). | ||||
"SELECT single XCURRENT FROM TXPDAT INTO @DATA(ld_e_xcurrent). | ||||
"SELECT single XFORECAST FROM TXPDAT INTO @DATA(ld_e_xforecast). | ||||
"SELECT single EVENT FROM TXPDAT INTO @DATA(ld_i_event). | ||||
"SELECT single XACTUAL FROM TXPDAT INTO @DATA(ld_e_xactual). | ||||
"SELECT single EXP_PRIO FROM TXPDAT INTO @DATA(ld_e_exp_prio). | ||||
"SELECT single USX_BAS FROM TSTDEV INTO @DATA(ld_i_baseline). | ||||
"SELECT single USX_CUR FROM TSTDEV INTO @DATA(ld_i_current). | ||||
"SELECT single USX_FOR FROM TSTDEV INTO @DATA(ld_i_forecast). | ||||
"SELECT single USX_ACT FROM TSTDEV INTO @DATA(ld_i_actual). | ||||
Search for further information about these or an SAP related objects