SAP MM_ARRANG_READ_FROM_BUFFER Function Module for NOTRANSL: Absprachedaten lesen mit Pufferung
MM_ARRANG_READ_FROM_BUFFER is a standard mm arrang read from buffer SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Absprachedaten lesen mit Pufferung 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 mm arrang read from buffer FM, simply by entering the name MM_ARRANG_READ_FROM_BUFFER into the relevant SAP transaction such as SE37 or SE38.
Function Group: WN27
Program Name: SAPLWN27
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MM_ARRANG_READ_FROM_BUFFER 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 'MM_ARRANG_READ_FROM_BUFFER'"NOTRANSL: Absprachedaten lesen mit Pufferung.
EXPORTING
I_CONDITION_NUMBER = "Condition Record Number
I_CONDITION_KOPOS = "Sequential number of the condition
IMPORTING
E_ARRANGEMENT = "Rebate Arrangements
P_RESET_INTERNAL_BUFFERS = "DE-EN-LANG-SWITCH-NO-TRANSLATION
TABLES
* T_VARIABLE_KEY = "Sample Structure for the Variable Key
* T_CONDITION_RECORD = "Conditions (Item)
EXCEPTIONS
MISSING_PARAMETER = 1 ERROR_READING_ARRANG_DATA = 2 ARRANGEMENT_DATA_INVALID = 3 CONDITION_RECORD_NOT_FOUND = 4
IMPORTING Parameters details for MM_ARRANG_READ_FROM_BUFFER
I_CONDITION_NUMBER - Condition Record Number
Data type: KONP-KNUMHOptional: No
Call by Reference: No ( called with pass by value option)
I_CONDITION_KOPOS - Sequential number of the condition
Data type: KONP-KOPOSOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for MM_ARRANG_READ_FROM_BUFFER
E_ARRANGEMENT - Rebate Arrangements
Data type: KONAOptional: No
Call by Reference: Yes
P_RESET_INTERNAL_BUFFERS - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: COptional: No
Call by Reference: Yes
TABLES Parameters details for MM_ARRANG_READ_FROM_BUFFER
T_VARIABLE_KEY - Sample Structure for the Variable Key
Data type: VAKEOptional: Yes
Call by Reference: Yes
T_CONDITION_RECORD - Conditions (Item)
Data type: KONPOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
MISSING_PARAMETER - Parameter Missing
Data type:Optional: No
Call by Reference: Yes
ERROR_READING_ARRANG_DATA - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
ARRANGEMENT_DATA_INVALID - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
CONDITION_RECORD_NOT_FOUND - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for MM_ARRANG_READ_FROM_BUFFER 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_e_arrangement | TYPE KONA, " | |||
| lt_t_variable_key | TYPE STANDARD TABLE OF VAKE, " | |||
| lv_missing_parameter | TYPE VAKE, " | |||
| lv_i_condition_number | TYPE KONP-KNUMH, " | |||
| lv_i_condition_kopos | TYPE KONP-KOPOS, " | |||
| lt_t_condition_record | TYPE STANDARD TABLE OF KONP, " | |||
| lv_p_reset_internal_buffers | TYPE C, " | |||
| lv_error_reading_arrang_data | TYPE C, " | |||
| lv_arrangement_data_invalid | TYPE C, " | |||
| lv_condition_record_not_found | TYPE C. " |
|   CALL FUNCTION 'MM_ARRANG_READ_FROM_BUFFER' "NOTRANSL: Absprachedaten lesen mit Pufferung |
| EXPORTING | ||
| I_CONDITION_NUMBER | = lv_i_condition_number | |
| I_CONDITION_KOPOS | = lv_i_condition_kopos | |
| IMPORTING | ||
| E_ARRANGEMENT | = lv_e_arrangement | |
| P_RESET_INTERNAL_BUFFERS | = lv_p_reset_internal_buffers | |
| TABLES | ||
| T_VARIABLE_KEY | = lt_t_variable_key | |
| T_CONDITION_RECORD | = lt_t_condition_record | |
| EXCEPTIONS | ||
| MISSING_PARAMETER = 1 | ||
| ERROR_READING_ARRANG_DATA = 2 | ||
| ARRANGEMENT_DATA_INVALID = 3 | ||
| CONDITION_RECORD_NOT_FOUND = 4 | ||
| . " MM_ARRANG_READ_FROM_BUFFER | ||
ABAP code using 7.40 inline data declarations to call FM MM_ARRANG_READ_FROM_BUFFER
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 KNUMH FROM KONP INTO @DATA(ld_i_condition_number). | ||||
| "SELECT single KOPOS FROM KONP INTO @DATA(ld_i_condition_kopos). | ||||
Search for further information about these or an SAP related objects