SAP GET_KONV Function Module for NOTRANSL: Gets KONV
GET_KONV is a standard get konv 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: Gets KONV 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 get konv FM, simply by entering the name GET_KONV into the relevant SAP transaction such as SE37 or SE38.
Function Group: REF_ARC_VBRK
Program Name: SAPLREF_ARC_VBRK
Main Program: SAPLREF_ARC_VBRK
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function GET_KONV 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 'GET_KONV'"NOTRANSL: Gets KONV.
EXPORTING
I_VBELN = "Sales and Distribution Document Number
I_POSNR = "Condition Item Number
CHANGING
CH_KOMV = "Pricing: Communications Condition Record
IMPORTING Parameters details for GET_KONV
I_VBELN - Sales and Distribution Document Number
Data type: VBELNOptional: No
Call by Reference: No ( called with pass by value option)
I_POSNR - Condition Item Number
Data type: KPOSNOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for GET_KONV
CH_KOMV - Pricing: Communications Condition Record
Data type: KOMV_TABOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for GET_KONV 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_ch_komv | TYPE KOMV_TAB, " | |||
| lv_i_vbeln | TYPE VBELN, " | |||
| lv_i_posnr | TYPE KPOSN. " |
|   CALL FUNCTION 'GET_KONV' "NOTRANSL: Gets KONV |
| EXPORTING | ||
| I_VBELN | = lv_i_vbeln | |
| I_POSNR | = lv_i_posnr | |
| CHANGING | ||
| CH_KOMV | = lv_ch_komv | |
| . " GET_KONV | ||
ABAP code using 7.40 inline data declarations to call FM GET_KONV
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.Search for further information about these or an SAP related objects