SAP MAA_EXTRACTOR Function Module for Extractor PO History MAA
MAA_EXTRACTOR is a standard maa extractor SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Extractor PO History MAA 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 maa extractor FM, simply by entering the name MAA_EXTRACTOR into the relevant SAP transaction such as SE37 or SE38.
Function Group: MEMAA_EXT
Program Name: SAPLMEMAA_EXT
Main Program: SAPLMEMAA_EXT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MAA_EXTRACTOR 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 'MAA_EXTRACTOR'"Extractor PO History MAA.
EXPORTING
* I_ISOURCE = "
* I_RLOGSYS = "
I_REQUNR = "
* I_MAXSIZE = 1000 "
* I_INITFLAG = "
* I_DATAPAKID = "
* I_UPDMODE = "
* I_READ_ONLY = 'X' "
TABLES
* I_T_SELECT = "
* I_T_FIELDS = "
* E_T_MAA_EXT_STR_S = "BW: Multiple Acc Assignment(extractor)
EXCEPTIONS
NO_MORE_DATA = 1 ERROR_PASSED_TO_MESS_HANDLER = 2
IMPORTING Parameters details for MAA_EXTRACTOR
I_ISOURCE -
Data type: SBIWA_S_INTERFACE-ISOURCEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_RLOGSYS -
Data type: RSAOT_LOGSYSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_REQUNR -
Data type: SBIWA_S_INTERFACE-REQUNROptional: No
Call by Reference: No ( called with pass by value option)
I_MAXSIZE -
Data type: SBIWA_S_INTERFACE-MAXSIZEDefault: 1000
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_INITFLAG -
Data type: SBIWA_S_INTERFACE-INITFLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
I_DATAPAKID -
Data type: SBIWA_S_INTERFACE-DATAPAKIDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_UPDMODE -
Data type: SBIWA_S_INTERFACE-UPDMODEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_READ_ONLY -
Data type: SBIWA_FLAGDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for MAA_EXTRACTOR
I_T_SELECT -
Data type: SBIWA_T_SELECTOptional: Yes
Call by Reference: Yes
I_T_FIELDS -
Data type: SBIWA_T_FIELDSOptional: Yes
Call by Reference: Yes
E_T_MAA_EXT_STR_S - BW: Multiple Acc Assignment(extractor)
Data type: MAA_EXT_STR_TOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
NO_MORE_DATA -
Data type:Optional: No
Call by Reference: Yes
ERROR_PASSED_TO_MESS_HANDLER -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for MAA_EXTRACTOR 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_isource | TYPE SBIWA_S_INTERFACE-ISOURCE, " | |||
| lt_i_t_select | TYPE STANDARD TABLE OF SBIWA_T_SELECT, " | |||
| lv_no_more_data | TYPE SBIWA_T_SELECT, " | |||
| lv_i_rlogsys | TYPE RSAOT_LOGSYS, " | |||
| lt_i_t_fields | TYPE STANDARD TABLE OF SBIWA_T_FIELDS, " | |||
| lv_error_passed_to_mess_handler | TYPE SBIWA_T_FIELDS, " | |||
| lv_i_requnr | TYPE SBIWA_S_INTERFACE-REQUNR, " | |||
| lt_e_t_maa_ext_str_s | TYPE STANDARD TABLE OF MAA_EXT_STR_T, " | |||
| lv_i_maxsize | TYPE SBIWA_S_INTERFACE-MAXSIZE, " 1000 | |||
| lv_i_initflag | TYPE SBIWA_S_INTERFACE-INITFLAG, " | |||
| lv_i_datapakid | TYPE SBIWA_S_INTERFACE-DATAPAKID, " | |||
| lv_i_updmode | TYPE SBIWA_S_INTERFACE-UPDMODE, " | |||
| lv_i_read_only | TYPE SBIWA_FLAG. " 'X' |
|   CALL FUNCTION 'MAA_EXTRACTOR' "Extractor PO History MAA |
| EXPORTING | ||
| I_ISOURCE | = lv_i_isource | |
| I_RLOGSYS | = lv_i_rlogsys | |
| I_REQUNR | = lv_i_requnr | |
| I_MAXSIZE | = lv_i_maxsize | |
| I_INITFLAG | = lv_i_initflag | |
| I_DATAPAKID | = lv_i_datapakid | |
| I_UPDMODE | = lv_i_updmode | |
| I_READ_ONLY | = lv_i_read_only | |
| TABLES | ||
| I_T_SELECT | = lt_i_t_select | |
| I_T_FIELDS | = lt_i_t_fields | |
| E_T_MAA_EXT_STR_S | = lt_e_t_maa_ext_str_s | |
| EXCEPTIONS | ||
| NO_MORE_DATA = 1 | ||
| ERROR_PASSED_TO_MESS_HANDLER = 2 | ||
| . " MAA_EXTRACTOR | ||
ABAP code using 7.40 inline data declarations to call FM MAA_EXTRACTOR
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 ISOURCE FROM SBIWA_S_INTERFACE INTO @DATA(ld_i_isource). | ||||
| "SELECT single REQUNR FROM SBIWA_S_INTERFACE INTO @DATA(ld_i_requnr). | ||||
| "SELECT single MAXSIZE FROM SBIWA_S_INTERFACE INTO @DATA(ld_i_maxsize). | ||||
| DATA(ld_i_maxsize) | = 1000. | |||
| "SELECT single INITFLAG FROM SBIWA_S_INTERFACE INTO @DATA(ld_i_initflag). | ||||
| "SELECT single DATAPAKID FROM SBIWA_S_INTERFACE INTO @DATA(ld_i_datapakid). | ||||
| "SELECT single UPDMODE FROM SBIWA_S_INTERFACE INTO @DATA(ld_i_updmode). | ||||
| DATA(ld_i_read_only) | = 'X'. | |||
Search for further information about these or an SAP related objects