SAP MM_ARRANG_READ_KONA_FROM_KNUMH Function Module for NOTRANSL: Lesen der Absprachedaten über eine Konditionssatznummer
MM_ARRANG_READ_KONA_FROM_KNUMH is a standard mm arrang read kona from knumh 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: Lesen der Absprachedaten über eine Konditionssatznummer 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 kona from knumh FM, simply by entering the name MM_ARRANG_READ_KONA_FROM_KNUMH into the relevant SAP transaction such as SE37 or SE38.
Function Group: WN05
Program Name: SAPLWN05
Main Program: SAPLWN05
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MM_ARRANG_READ_KONA_FROM_KNUMH 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_KONA_FROM_KNUMH'"NOTRANSL: Lesen der Absprachedaten über eine Konditionssatznummer.
EXPORTING
CONDITION_NUMBER = "Condition Record Number
* CONDITION_KOPOS = '01' "
* ARRANGEMENT = "
* HEADER_READ = ' ' "
* SCALE_READ = ' ' "
* RESET_INTERNAL_BUFFERS = ' ' "
IMPORTING
ARRANGEMENT = "
TABLES
* VARIABLE_KEY = "
* CONDITION_HEADER = "
* CONDITION_RECORD = "
* CONDSCALE = "
EXCEPTIONS
ARRANGEMENT_NOT_FOUND = 1 CONDITION_RECORD_NOT_FOUND = 2 ARRANGEMENT_DATA_INVALID = 3
IMPORTING Parameters details for MM_ARRANG_READ_KONA_FROM_KNUMH
CONDITION_NUMBER - Condition Record Number
Data type: KONP-KNUMHOptional: No
Call by Reference: No ( called with pass by value option)
CONDITION_KOPOS -
Data type: KONP-KOPOSDefault: '01'
Optional: Yes
Call by Reference: No ( called with pass by value option)
ARRANGEMENT -
Data type: KONAOptional: Yes
Call by Reference: No ( called with pass by value option)
HEADER_READ -
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
SCALE_READ -
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
RESET_INTERNAL_BUFFERS -
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for MM_ARRANG_READ_KONA_FROM_KNUMH
ARRANGEMENT -
Data type: KONAOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for MM_ARRANG_READ_KONA_FROM_KNUMH
VARIABLE_KEY -
Data type: VAKEOptional: Yes
Call by Reference: No ( called with pass by value option)
CONDITION_HEADER -
Data type: KONHOptional: Yes
Call by Reference: No ( called with pass by value option)
CONDITION_RECORD -
Data type: KONPOptional: Yes
Call by Reference: No ( called with pass by value option)
CONDSCALE -
Data type: CONDSCALEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ARRANGEMENT_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CONDITION_RECORD_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ARRANGEMENT_DATA_INVALID -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MM_ARRANG_READ_KONA_FROM_KNUMH 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_arrangement | TYPE KONA, " | |||
| lt_variable_key | TYPE STANDARD TABLE OF VAKE, " | |||
| lv_condition_number | TYPE KONP-KNUMH, " | |||
| lv_arrangement_not_found | TYPE KONP, " | |||
| lv_condition_kopos | TYPE KONP-KOPOS, " '01' | |||
| lt_condition_header | TYPE STANDARD TABLE OF KONH, " | |||
| lv_condition_record_not_found | TYPE KONH, " | |||
| lv_arrangement | TYPE KONA, " | |||
| lt_condition_record | TYPE STANDARD TABLE OF KONP, " | |||
| lv_arrangement_data_invalid | TYPE KONP, " | |||
| lt_condscale | TYPE STANDARD TABLE OF CONDSCALE, " | |||
| lv_header_read | TYPE C, " SPACE | |||
| lv_scale_read | TYPE C, " SPACE | |||
| lv_reset_internal_buffers | TYPE C. " SPACE |
|   CALL FUNCTION 'MM_ARRANG_READ_KONA_FROM_KNUMH' "NOTRANSL: Lesen der Absprachedaten über eine Konditionssatznummer |
| EXPORTING | ||
| CONDITION_NUMBER | = lv_condition_number | |
| CONDITION_KOPOS | = lv_condition_kopos | |
| ARRANGEMENT | = lv_arrangement | |
| HEADER_READ | = lv_header_read | |
| SCALE_READ | = lv_scale_read | |
| RESET_INTERNAL_BUFFERS | = lv_reset_internal_buffers | |
| IMPORTING | ||
| ARRANGEMENT | = lv_arrangement | |
| TABLES | ||
| VARIABLE_KEY | = lt_variable_key | |
| CONDITION_HEADER | = lt_condition_header | |
| CONDITION_RECORD | = lt_condition_record | |
| CONDSCALE | = lt_condscale | |
| EXCEPTIONS | ||
| ARRANGEMENT_NOT_FOUND = 1 | ||
| CONDITION_RECORD_NOT_FOUND = 2 | ||
| ARRANGEMENT_DATA_INVALID = 3 | ||
| . " MM_ARRANG_READ_KONA_FROM_KNUMH | ||
ABAP code using 7.40 inline data declarations to call FM MM_ARRANG_READ_KONA_FROM_KNUMH
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_condition_number). | ||||
| "SELECT single KOPOS FROM KONP INTO @DATA(ld_condition_kopos). | ||||
| DATA(ld_condition_kopos) | = '01'. | |||
| DATA(ld_header_read) | = ' '. | |||
| DATA(ld_scale_read) | = ' '. | |||
| DATA(ld_reset_internal_buffers) | = ' '. | |||
Search for further information about these or an SAP related objects