SAP EXIT_SAPMM06E_016 Function Module for Export Data to Customer Subscreen for Purchasing Document Item (PBO)
EXIT_SAPMM06E_016 is a standard exit sapmm06e 016 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 Data to Customer Subscreen for Purchasing Document Item (PBO) 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 016 FM, simply by entering the name EXIT_SAPMM06E_016 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XM06
Program Name: SAPLXM06
Main Program: SAPLXM06
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function EXIT_SAPMM06E_016 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_016'"Export Data to Customer Subscreen for Purchasing Document Item (PBO).
EXPORTING
I_EKPO = "Purchasing Document Item
* I_KEKPO = "Contract Item, Release Order (Create)
* I_AEKPO = "Reference RFQ Item (Create)
* I_REBAN = "Reference Purchase Requisition (Create)
* I_MT06E = "Material Master Data (Create)
* I_EINA = "Info Record: General Data
* I_EINE = "Info Record: Purchasing Organization Data
* I_EKPO_OLD = "Old Status: Purchasing Document Item
* I_KOMP = "Transfer Structure for Conditions
* I_ENJ_CALL = "Enjoy Transaction
I_AKTYP = "Create, Change, Display
I_CI_EKPO = "Customer Fields for Purchasing Document Item
I_BSTYP = "Document Category (Purchase Order, RFQ, ...)
I_NO_SCREEN = "No Screen Input Possible
I_LFA1 = "Vendor: General Data
I_LFM1 = "Vendor: Purchasing Organization Data
I_EKKO = "Purchasing Document Header
* I_REKPO = "Reference Document Item (Create)
TABLES
* TEKPO = "All Items of Purchasing Document
* TEKET = "All Delivery Schedule Lines of Purchasing Document
* TEKKN = "All Account Assignments of Purchasing Document
* TKOMV = "All Conditions of Purchasing Document
IMPORTING Parameters details for EXIT_SAPMM06E_016
I_EKPO - Purchasing Document Item
Data type: EKPOOptional: No
Call by Reference: No ( called with pass by value option)
I_KEKPO - Contract Item, Release Order (Create)
Data type: EKPOOptional: Yes
Call by Reference: No ( called with pass by value option)
I_AEKPO - Reference RFQ Item (Create)
Data type: EKPOOptional: Yes
Call by Reference: No ( called with pass by value option)
I_REBAN - Reference Purchase Requisition (Create)
Data type: EBANOptional: Yes
Call by Reference: No ( called with pass by value option)
I_MT06E - Material Master Data (Create)
Data type: MT06EOptional: Yes
Call by Reference: No ( called with pass by value option)
I_EINA - Info Record: General Data
Data type: EINAOptional: Yes
Call by Reference: No ( called with pass by value option)
I_EINE - Info Record: Purchasing Organization Data
Data type: EINEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_EKPO_OLD - Old Status: Purchasing Document Item
Data type: EKPOOptional: Yes
Call by Reference: No ( called with pass by value option)
I_KOMP - Transfer Structure for Conditions
Data type: KOMPOptional: Yes
Call by Reference: No ( called with pass by value option)
I_ENJ_CALL - Enjoy Transaction
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
I_AKTYP - Create, Change, Display
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
I_CI_EKPO - Customer Fields for Purchasing Document Item
Data type: EKPO_CIOptional: No
Call by Reference: No ( called with pass by value option)
I_BSTYP - Document Category (Purchase Order, RFQ, ...)
Data type: EKKO-BSTYPOptional: No
Call by Reference: No ( called with pass by value option)
I_NO_SCREEN - No Screen Input Possible
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
I_LFA1 - Vendor: General Data
Data type: LFA1Optional: No
Call by Reference: No ( called with pass by value option)
I_LFM1 - Vendor: Purchasing Organization Data
Data type: LFM1Optional: No
Call by Reference: No ( called with pass by value option)
I_EKKO - Purchasing Document Header
Data type: EKKOOptional: No
Call by Reference: No ( called with pass by value option)
I_REKPO - Reference Document Item (Create)
Data type: EKPOOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for EXIT_SAPMM06E_016
TEKPO - All Items of Purchasing Document
Data type: BEKPOOptional: Yes
Call by Reference: No ( called with pass by value option)
TEKET - All Delivery Schedule Lines of Purchasing Document
Data type: BEKETOptional: Yes
Call by Reference: No ( called with pass by value option)
TEKKN - All Account Assignments of Purchasing Document
Data type: EKKNUOptional: Yes
Call by Reference: No ( called with pass by value option)
TKOMV - All Conditions of Purchasing Document
Data type: KOMVOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EXIT_SAPMM06E_016 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: | ||||
lt_tekpo | TYPE STANDARD TABLE OF BEKPO, " | |||
lv_i_ekpo | TYPE EKPO, " | |||
lv_i_kekpo | TYPE EKPO, " | |||
lv_i_aekpo | TYPE EKPO, " | |||
lv_i_reban | TYPE EBAN, " | |||
lv_i_mt06e | TYPE MT06E, " | |||
lv_i_eina | TYPE EINA, " | |||
lv_i_eine | TYPE EINE, " | |||
lv_i_ekpo_old | TYPE EKPO, " | |||
lv_i_komp | TYPE KOMP, " | |||
lv_i_enj_call | TYPE KOMP, " | |||
lt_teket | TYPE STANDARD TABLE OF BEKET, " | |||
lv_i_aktyp | TYPE BEKET, " | |||
lt_tekkn | TYPE STANDARD TABLE OF EKKNU, " | |||
lv_i_ci_ekpo | TYPE EKPO_CI, " | |||
lt_tkomv | TYPE STANDARD TABLE OF KOMV, " | |||
lv_i_bstyp | TYPE EKKO-BSTYP, " | |||
lv_i_no_screen | TYPE EKKO, " | |||
lv_i_lfa1 | TYPE LFA1, " | |||
lv_i_lfm1 | TYPE LFM1, " | |||
lv_i_ekko | TYPE EKKO, " | |||
lv_i_rekpo | TYPE EKPO. " |
  CALL FUNCTION 'EXIT_SAPMM06E_016' "Export Data to Customer Subscreen for Purchasing Document Item (PBO) |
EXPORTING | ||
I_EKPO | = lv_i_ekpo | |
I_KEKPO | = lv_i_kekpo | |
I_AEKPO | = lv_i_aekpo | |
I_REBAN | = lv_i_reban | |
I_MT06E | = lv_i_mt06e | |
I_EINA | = lv_i_eina | |
I_EINE | = lv_i_eine | |
I_EKPO_OLD | = lv_i_ekpo_old | |
I_KOMP | = lv_i_komp | |
I_ENJ_CALL | = lv_i_enj_call | |
I_AKTYP | = lv_i_aktyp | |
I_CI_EKPO | = lv_i_ci_ekpo | |
I_BSTYP | = lv_i_bstyp | |
I_NO_SCREEN | = lv_i_no_screen | |
I_LFA1 | = lv_i_lfa1 | |
I_LFM1 | = lv_i_lfm1 | |
I_EKKO | = lv_i_ekko | |
I_REKPO | = lv_i_rekpo | |
TABLES | ||
TEKPO | = lt_tekpo | |
TEKET | = lt_teket | |
TEKKN | = lt_tekkn | |
TKOMV | = lt_tkomv | |
. " EXIT_SAPMM06E_016 |
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPMM06E_016
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 BSTYP FROM EKKO INTO @DATA(ld_i_bstyp). | ||||
Search for further information about these or an SAP related objects