SAP MM_ARRANG_COND_REC_EVALUATION Function Module for NOTRANSL: Konditionssatz auswerten (nachtr. Abrechnung Einkauf)
MM_ARRANG_COND_REC_EVALUATION is a standard mm arrang cond rec evaluation 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: Konditionssatz auswerten (nachtr. Abrechnung Einkauf) 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 cond rec evaluation FM, simply by entering the name MM_ARRANG_COND_REC_EVALUATION into the relevant SAP transaction such as SE37 or SE38.
Function Group: WN01
Program Name: SAPLWN01
Main Program: SAPLWN01
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MM_ARRANG_COND_REC_EVALUATION 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_COND_REC_EVALUATION'"NOTRANSL: Konditionssatz auswerten (nachtr. Abrechnung Einkauf).
EXPORTING
I_ARRANGEMENT = "Rebate Arrangement
I_SETTLEMENT_VALUES = "Settlement accounting data
I_SETTLEMENT_BUKRS = "
* I_T6B1 = "
* I_T685A = "
* I_T001 = "Company Code (Optional)
* I_NO_SCALE_DETERMINATION = ' ' "
* I_ERR_MSGNO_NO_BUKRS = '145' "
IMPORTING
E_SETTLEMENT_VALUES = "Settlement accounting data
E_READ_SUBRC = "
TABLES
T_VARIABLE_KEY = "Variable Key
T_CONDITION_RECORD = "Condition Records
T_CONDITION_SCALE = "Scale data
T_ERROR_MESSAGES = "Notifications
* T_EVALUATION_DATA = "
EXCEPTIONS
INVALID_CONDSCALE = 1 ERROR_MSG_USER_EXIT = 2 FATAL_ERROR_MSG_USER_EXIT = 3
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLWN01_001 Business Volume Data (Scale/Condition Basis) Before Calculation of Income
EXIT_SAPLWN01_002 Calculation of the Income of a Condition Record
EXIT_SAPLWN01_003 Change Settlement Data Before Creation of Settlement Doc.
IMPORTING Parameters details for MM_ARRANG_COND_REC_EVALUATION
I_ARRANGEMENT - Rebate Arrangement
Data type: KONAOptional: No
Call by Reference: No ( called with pass by value option)
I_SETTLEMENT_VALUES - Settlement accounting data
Data type: ARRANG_VALOptional: No
Call by Reference: No ( called with pass by value option)
I_SETTLEMENT_BUKRS -
Data type: T001-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
I_T6B1 -
Data type: T6B1Optional: Yes
Call by Reference: No ( called with pass by value option)
I_T685A -
Data type: T685AOptional: Yes
Call by Reference: No ( called with pass by value option)
I_T001 - Company Code (Optional)
Data type: T001Optional: Yes
Call by Reference: No ( called with pass by value option)
I_NO_SCALE_DETERMINATION -
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_ERR_MSGNO_NO_BUKRS -
Data type: SY-MSGNODefault: '145'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for MM_ARRANG_COND_REC_EVALUATION
E_SETTLEMENT_VALUES - Settlement accounting data
Data type: ARRANG_VALOptional: No
Call by Reference: No ( called with pass by value option)
E_READ_SUBRC -
Data type: SY-SUBRCOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for MM_ARRANG_COND_REC_EVALUATION
T_VARIABLE_KEY - Variable Key
Data type: VAKEOptional: No
Call by Reference: No ( called with pass by value option)
T_CONDITION_RECORD - Condition Records
Data type: KONPOptional: No
Call by Reference: No ( called with pass by value option)
T_CONDITION_SCALE - Scale data
Data type: CONDSCALEOptional: No
Call by Reference: No ( called with pass by value option)
T_ERROR_MESSAGES - Notifications
Data type: ARRANG_ERROptional: No
Call by Reference: No ( called with pass by value option)
T_EVALUATION_DATA -
Data type: GRADDATAOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INVALID_CONDSCALE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERROR_MSG_USER_EXIT -
Data type:Optional: No
Call by Reference: Yes
FATAL_ERROR_MSG_USER_EXIT -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for MM_ARRANG_COND_REC_EVALUATION 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_arrangement | TYPE KONA, " | |||
| lt_t_variable_key | TYPE STANDARD TABLE OF VAKE, " | |||
| lv_invalid_condscale | TYPE VAKE, " | |||
| lv_e_settlement_values | TYPE ARRANG_VAL, " | |||
| lv_e_read_subrc | TYPE SY-SUBRC, " | |||
| lt_t_condition_record | TYPE STANDARD TABLE OF KONP, " | |||
| lv_error_msg_user_exit | TYPE KONP, " | |||
| lv_i_settlement_values | TYPE ARRANG_VAL, " | |||
| lt_t_condition_scale | TYPE STANDARD TABLE OF CONDSCALE, " | |||
| lv_i_settlement_bukrs | TYPE T001-BUKRS, " | |||
| lv_fatal_error_msg_user_exit | TYPE T001, " | |||
| lv_i_t6b1 | TYPE T6B1, " | |||
| lt_t_error_messages | TYPE STANDARD TABLE OF ARRANG_ERR, " | |||
| lv_i_t685a | TYPE T685A, " | |||
| lt_t_evaluation_data | TYPE STANDARD TABLE OF GRADDATA, " | |||
| lv_i_t001 | TYPE T001, " | |||
| lv_i_no_scale_determination | TYPE C, " SPACE | |||
| lv_i_err_msgno_no_bukrs | TYPE SY-MSGNO. " '145' |
|   CALL FUNCTION 'MM_ARRANG_COND_REC_EVALUATION' "NOTRANSL: Konditionssatz auswerten (nachtr. Abrechnung Einkauf) |
| EXPORTING | ||
| I_ARRANGEMENT | = lv_i_arrangement | |
| I_SETTLEMENT_VALUES | = lv_i_settlement_values | |
| I_SETTLEMENT_BUKRS | = lv_i_settlement_bukrs | |
| I_T6B1 | = lv_i_t6b1 | |
| I_T685A | = lv_i_t685a | |
| I_T001 | = lv_i_t001 | |
| I_NO_SCALE_DETERMINATION | = lv_i_no_scale_determination | |
| I_ERR_MSGNO_NO_BUKRS | = lv_i_err_msgno_no_bukrs | |
| IMPORTING | ||
| E_SETTLEMENT_VALUES | = lv_e_settlement_values | |
| E_READ_SUBRC | = lv_e_read_subrc | |
| TABLES | ||
| T_VARIABLE_KEY | = lt_t_variable_key | |
| T_CONDITION_RECORD | = lt_t_condition_record | |
| T_CONDITION_SCALE | = lt_t_condition_scale | |
| T_ERROR_MESSAGES | = lt_t_error_messages | |
| T_EVALUATION_DATA | = lt_t_evaluation_data | |
| EXCEPTIONS | ||
| INVALID_CONDSCALE = 1 | ||
| ERROR_MSG_USER_EXIT = 2 | ||
| FATAL_ERROR_MSG_USER_EXIT = 3 | ||
| . " MM_ARRANG_COND_REC_EVALUATION | ||
ABAP code using 7.40 inline data declarations to call FM MM_ARRANG_COND_REC_EVALUATION
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 SUBRC FROM SY INTO @DATA(ld_e_read_subrc). | ||||
| "SELECT single BUKRS FROM T001 INTO @DATA(ld_i_settlement_bukrs). | ||||
| DATA(ld_i_no_scale_determination) | = ' '. | |||
| "SELECT single MSGNO FROM SY INTO @DATA(ld_i_err_msgno_no_bukrs). | ||||
| DATA(ld_i_err_msgno_no_bukrs) | = '145'. | |||
Search for further information about these or an SAP related objects