SAP AIA_BUFFER_FILL_WORKAREA Function Module for
AIA_BUFFER_FILL_WORKAREA is a standard aia buffer fill workarea SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 aia buffer fill workarea FM, simply by entering the name AIA_BUFFER_FILL_WORKAREA into the relevant SAP transaction such as SE37 or SE38.
Function Group: AIA_BUFFER
Program Name: SAPLAIA_BUFFER
Main Program:
Appliation area: A
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function AIA_BUFFER_FILL_WORKAREA 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 'AIA_BUFFER_FILL_WORKAREA'".
EXPORTING
APPREQ_EXT = "
* I_ACTVT = '01' "
* I_MSG_TYPE = 'E' "
* I_RAISE_EXCEPTION = 'X ' "
* TEST_RUN = 'X' "
IMPORTING
ES_X_IMAK = "
ES_Y_IMAK = "
ES_VKOKRS = "
ES_IMAK_VERW = "
ES_TAIF1 = "
TABLES
ET_X_IMAKT = "
ET_X_IMAV = "
ET_X_IMAVT = "
ET_X_IMAVZ = "
ET_X_IHPA = "
* ET_Y_IMAKT = "
* ET_Y_IMAKA = "
* ET_Y_IMAKPA = "
* ET_Y_IMAKPI = "
* ET_Y_IMAKPU = "
* ET_Y_IMAKPS = "
ET_X_IMAKA = "
* ET_Y_IMAKPW = "
* ET_Y_IMAKZ = "
* ET_Y_IMAKZS = "
* ET_Y_IMAV = "
* ET_Y_IMAVT = "
* ET_Y_IMAVZ = "
* ET_Y_IHPA = "
ET_IMAV_VERW = "
* RETURN = "
ET_X_IMAKPA = "
ET_X_IMAKPI = "
ET_X_IMAKPU = "
ET_X_IMAKPS = "
ET_X_IMAKPW = "
ET_X_IMAKZ = "
ET_X_IMAKZS = "
EXCEPTIONS
NO_APPREQUEST = 1 APPREQUEST_NOT_EXISTS = 2 APPREQUEST_LOCKED = 3 APPREQUEST_DELETED = 4 APPREQUEST_EXISTS = 5 PROJ_DEF_LOCKED = 6 MISSING_KOKRS_DATA = 7
IMPORTING Parameters details for AIA_BUFFER_FILL_WORKAREA
APPREQ_EXT -
Data type: IMAK-POSIDOptional: No
Call by Reference: No ( called with pass by value option)
I_ACTVT -
Data type: AUTHA-IM_ACTVTDefault: '01'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_MSG_TYPE -
Data type: SY-MSGTYDefault: 'E'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_RAISE_EXCEPTION -
Data type: CDefault: 'X '
Optional: Yes
Call by Reference: No ( called with pass by value option)
TEST_RUN -
Data type: CDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for AIA_BUFFER_FILL_WORKAREA
ES_X_IMAK -
Data type: RIMAKOptional: No
Call by Reference: Yes
ES_Y_IMAK -
Data type: RIMAKOptional: No
Call by Reference: Yes
ES_VKOKRS -
Data type: TKA01Optional: No
Call by Reference: Yes
ES_IMAK_VERW -
Data type: IMAD1_VERWOptional: No
Call by Reference: Yes
ES_TAIF1 -
Data type: TAIF1Optional: No
Call by Reference: Yes
TABLES Parameters details for AIA_BUFFER_FILL_WORKAREA
ET_X_IMAKT -
Data type: RIMAKTOptional: No
Call by Reference: Yes
ET_X_IMAV -
Data type: RIMAVOptional: No
Call by Reference: Yes
ET_X_IMAVT -
Data type: RIMAVTOptional: No
Call by Reference: Yes
ET_X_IMAVZ -
Data type: RIMAVZOptional: No
Call by Reference: Yes
ET_X_IHPA -
Data type: RIHPAOptional: No
Call by Reference: Yes
ET_Y_IMAKT -
Data type: RIMAKTOptional: Yes
Call by Reference: Yes
ET_Y_IMAKA -
Data type: RIMAKAOptional: Yes
Call by Reference: Yes
ET_Y_IMAKPA -
Data type: RIMAKPAOptional: Yes
Call by Reference: Yes
ET_Y_IMAKPI -
Data type: RIMAKPIOptional: Yes
Call by Reference: Yes
ET_Y_IMAKPU -
Data type: RIMAKPUOptional: Yes
Call by Reference: Yes
ET_Y_IMAKPS -
Data type: RIMAKPSOptional: Yes
Call by Reference: Yes
ET_X_IMAKA -
Data type: RIMAKAOptional: No
Call by Reference: Yes
ET_Y_IMAKPW -
Data type: RIMAKPWOptional: Yes
Call by Reference: Yes
ET_Y_IMAKZ -
Data type: RIMAKZOptional: Yes
Call by Reference: Yes
ET_Y_IMAKZS -
Data type: RIMAKZSOptional: Yes
Call by Reference: Yes
ET_Y_IMAV -
Data type: RIMAVOptional: Yes
Call by Reference: Yes
ET_Y_IMAVT -
Data type: RIMAVTOptional: Yes
Call by Reference: Yes
ET_Y_IMAVZ -
Data type: RIMAVZOptional: Yes
Call by Reference: Yes
ET_Y_IHPA -
Data type: RIHPAOptional: Yes
Call by Reference: Yes
ET_IMAV_VERW -
Data type: IMAD1_XVERW_VAROptional: No
Call by Reference: Yes
RETURN -
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
ET_X_IMAKPA -
Data type: RIMAKPAOptional: No
Call by Reference: Yes
ET_X_IMAKPI -
Data type: RIMAKPIOptional: No
Call by Reference: Yes
ET_X_IMAKPU -
Data type: RIMAKPUOptional: No
Call by Reference: Yes
ET_X_IMAKPS -
Data type: RIMAKPSOptional: No
Call by Reference: Yes
ET_X_IMAKPW -
Data type: RIMAKPWOptional: No
Call by Reference: Yes
ET_X_IMAKZ -
Data type: RIMAKZOptional: No
Call by Reference: Yes
ET_X_IMAKZS -
Data type: RIMAKZSOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_APPREQUEST -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
APPREQUEST_NOT_EXISTS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
APPREQUEST_LOCKED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
APPREQUEST_DELETED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
APPREQUEST_EXISTS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PROJ_DEF_LOCKED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MISSING_KOKRS_DATA -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for AIA_BUFFER_FILL_WORKAREA 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_es_x_imak | TYPE RIMAK, " | |||
| lv_appreq_ext | TYPE IMAK-POSID, " | |||
| lt_et_x_imakt | TYPE STANDARD TABLE OF RIMAKT, " | |||
| lv_no_apprequest | TYPE RIMAKT, " | |||
| lt_et_x_imav | TYPE STANDARD TABLE OF RIMAV, " | |||
| lt_et_x_imavt | TYPE STANDARD TABLE OF RIMAVT, " | |||
| lt_et_x_imavz | TYPE STANDARD TABLE OF RIMAVZ, " | |||
| lt_et_x_ihpa | TYPE STANDARD TABLE OF RIHPA, " | |||
| lt_et_y_imakt | TYPE STANDARD TABLE OF RIMAKT, " | |||
| lt_et_y_imaka | TYPE STANDARD TABLE OF RIMAKA, " | |||
| lt_et_y_imakpa | TYPE STANDARD TABLE OF RIMAKPA, " | |||
| lt_et_y_imakpi | TYPE STANDARD TABLE OF RIMAKPI, " | |||
| lt_et_y_imakpu | TYPE STANDARD TABLE OF RIMAKPU, " | |||
| lt_et_y_imakps | TYPE STANDARD TABLE OF RIMAKPS, " | |||
| lv_i_actvt | TYPE AUTHA-IM_ACTVT, " '01' | |||
| lv_es_y_imak | TYPE RIMAK, " | |||
| lt_et_x_imaka | TYPE STANDARD TABLE OF RIMAKA, " | |||
| lv_apprequest_not_exists | TYPE RIMAKA, " | |||
| lt_et_y_imakpw | TYPE STANDARD TABLE OF RIMAKPW, " | |||
| lt_et_y_imakz | TYPE STANDARD TABLE OF RIMAKZ, " | |||
| lt_et_y_imakzs | TYPE STANDARD TABLE OF RIMAKZS, " | |||
| lt_et_y_imav | TYPE STANDARD TABLE OF RIMAV, " | |||
| lt_et_y_imavt | TYPE STANDARD TABLE OF RIMAVT, " | |||
| lt_et_y_imavz | TYPE STANDARD TABLE OF RIMAVZ, " | |||
| lt_et_y_ihpa | TYPE STANDARD TABLE OF RIHPA, " | |||
| lt_et_imav_verw | TYPE STANDARD TABLE OF IMAD1_XVERW_VAR, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_es_vkokrs | TYPE TKA01, " | |||
| lv_i_msg_type | TYPE SY-MSGTY, " 'E' | |||
| lt_et_x_imakpa | TYPE STANDARD TABLE OF RIMAKPA, " | |||
| lv_apprequest_locked | TYPE RIMAKPA, " | |||
| lt_et_x_imakpi | TYPE STANDARD TABLE OF RIMAKPI, " | |||
| lv_es_imak_verw | TYPE IMAD1_VERW, " | |||
| lv_i_raise_exception | TYPE C, " 'X ' | |||
| lv_apprequest_deleted | TYPE C, " | |||
| lv_es_taif1 | TYPE TAIF1, " | |||
| lv_test_run | TYPE C, " 'X' | |||
| lt_et_x_imakpu | TYPE STANDARD TABLE OF RIMAKPU, " | |||
| lv_apprequest_exists | TYPE RIMAKPU, " | |||
| lt_et_x_imakps | TYPE STANDARD TABLE OF RIMAKPS, " | |||
| lv_proj_def_locked | TYPE RIMAKPS, " | |||
| lt_et_x_imakpw | TYPE STANDARD TABLE OF RIMAKPW, " | |||
| lv_missing_kokrs_data | TYPE RIMAKPW, " | |||
| lt_et_x_imakz | TYPE STANDARD TABLE OF RIMAKZ, " | |||
| lt_et_x_imakzs | TYPE STANDARD TABLE OF RIMAKZS. " |
|   CALL FUNCTION 'AIA_BUFFER_FILL_WORKAREA' " |
| EXPORTING | ||
| APPREQ_EXT | = lv_appreq_ext | |
| I_ACTVT | = lv_i_actvt | |
| I_MSG_TYPE | = lv_i_msg_type | |
| I_RAISE_EXCEPTION | = lv_i_raise_exception | |
| TEST_RUN | = lv_test_run | |
| IMPORTING | ||
| ES_X_IMAK | = lv_es_x_imak | |
| ES_Y_IMAK | = lv_es_y_imak | |
| ES_VKOKRS | = lv_es_vkokrs | |
| ES_IMAK_VERW | = lv_es_imak_verw | |
| ES_TAIF1 | = lv_es_taif1 | |
| TABLES | ||
| ET_X_IMAKT | = lt_et_x_imakt | |
| ET_X_IMAV | = lt_et_x_imav | |
| ET_X_IMAVT | = lt_et_x_imavt | |
| ET_X_IMAVZ | = lt_et_x_imavz | |
| ET_X_IHPA | = lt_et_x_ihpa | |
| ET_Y_IMAKT | = lt_et_y_imakt | |
| ET_Y_IMAKA | = lt_et_y_imaka | |
| ET_Y_IMAKPA | = lt_et_y_imakpa | |
| ET_Y_IMAKPI | = lt_et_y_imakpi | |
| ET_Y_IMAKPU | = lt_et_y_imakpu | |
| ET_Y_IMAKPS | = lt_et_y_imakps | |
| ET_X_IMAKA | = lt_et_x_imaka | |
| ET_Y_IMAKPW | = lt_et_y_imakpw | |
| ET_Y_IMAKZ | = lt_et_y_imakz | |
| ET_Y_IMAKZS | = lt_et_y_imakzs | |
| ET_Y_IMAV | = lt_et_y_imav | |
| ET_Y_IMAVT | = lt_et_y_imavt | |
| ET_Y_IMAVZ | = lt_et_y_imavz | |
| ET_Y_IHPA | = lt_et_y_ihpa | |
| ET_IMAV_VERW | = lt_et_imav_verw | |
| RETURN | = lt_return | |
| ET_X_IMAKPA | = lt_et_x_imakpa | |
| ET_X_IMAKPI | = lt_et_x_imakpi | |
| ET_X_IMAKPU | = lt_et_x_imakpu | |
| ET_X_IMAKPS | = lt_et_x_imakps | |
| ET_X_IMAKPW | = lt_et_x_imakpw | |
| ET_X_IMAKZ | = lt_et_x_imakz | |
| ET_X_IMAKZS | = lt_et_x_imakzs | |
| EXCEPTIONS | ||
| NO_APPREQUEST = 1 | ||
| APPREQUEST_NOT_EXISTS = 2 | ||
| APPREQUEST_LOCKED = 3 | ||
| APPREQUEST_DELETED = 4 | ||
| APPREQUEST_EXISTS = 5 | ||
| PROJ_DEF_LOCKED = 6 | ||
| MISSING_KOKRS_DATA = 7 | ||
| . " AIA_BUFFER_FILL_WORKAREA | ||
ABAP code using 7.40 inline data declarations to call FM AIA_BUFFER_FILL_WORKAREA
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 POSID FROM IMAK INTO @DATA(ld_appreq_ext). | ||||
| "SELECT single IM_ACTVT FROM AUTHA INTO @DATA(ld_i_actvt). | ||||
| DATA(ld_i_actvt) | = '01'. | |||
| "SELECT single MSGTY FROM SY INTO @DATA(ld_i_msg_type). | ||||
| DATA(ld_i_msg_type) | = 'E'. | |||
| DATA(ld_i_raise_exception) | = 'X '. | |||
| DATA(ld_test_run) | = 'X'. | |||
Search for further information about these or an SAP related objects