SAP EXIT_SAPMM06E_010 Function Module for Export of Service RFQ Data
EXIT_SAPMM06E_010 is a standard exit sapmm06e 010 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Export of Service RFQ 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 exit sapmm06e 010 FM, simply by entering the name EXIT_SAPMM06E_010 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XMLU
Program Name: SAPLXMLU
Main Program:
Appliation area: M
Release date: 22-Oct-1996
Mode(Normal, Remote etc): Normal Function Module
Update:
Function EXIT_SAPMM06E_010 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_010'"Export of Service RFQ Data.
EXPORTING
I_EBELN = "RFQ Number
IMPORTING
E_CODING_EXIST = "Indicator: Whether Coding Exists
IMPORTING Parameters details for EXIT_SAPMM06E_010
I_EBELN - RFQ Number
Data type: EKKO-EBELNOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for EXIT_SAPMM06E_010
E_CODING_EXIST - Indicator: Whether Coding Exists
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EXIT_SAPMM06E_010 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_ebeln | TYPE EKKO-EBELN, " | |||
lv_e_coding_exist | TYPE EKKO. " |
  CALL FUNCTION 'EXIT_SAPMM06E_010' "Export of Service RFQ Data |
EXPORTING | ||
I_EBELN | = lv_i_ebeln | |
IMPORTING | ||
E_CODING_EXIST | = lv_e_coding_exist | |
. " EXIT_SAPMM06E_010 |
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPMM06E_010
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 EBELN FROM EKKO INTO @DATA(ld_i_ebeln). | ||||
Search for further information about these or an SAP related objects