SAP CNVA_GET_MSG_DOCU Function Module for Get documentation
CNVA_GET_MSG_DOCU is a standard cnva get msg docu SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get documentation 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 cnva get msg docu FM, simply by entering the name CNVA_GET_MSG_DOCU into the relevant SAP transaction such as SE37 or SE38.
Function Group: CNVA_ANALYSIS_FUGR
Program Name: SAPLCNVA_ANALYSIS_FUGR
Main Program: SAPLCNVA_ANALYSIS_FUGR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CNVA_GET_MSG_DOCU 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 'CNVA_GET_MSG_DOCU'"Get documentation.
EXPORTING
IV_MSGCLS = "Application Area
IV_MSGNR = "Message number
IV_LANGU = "Language Key
IMPORTING
EV_TEXT = "
EXCEPTIONS
EX_NO_MSG_FOUND = 1
IMPORTING Parameters details for CNVA_GET_MSG_DOCU
IV_MSGCLS - Application Area
Data type: ARBGBOptional: No
Call by Reference: Yes
IV_MSGNR - Message number
Data type: MSGNROptional: No
Call by Reference: Yes
IV_LANGU - Language Key
Data type: SPRASOptional: No
Call by Reference: Yes
EXPORTING Parameters details for CNVA_GET_MSG_DOCU
EV_TEXT -
Data type: STRINGOptional: No
Call by Reference: Yes
EXCEPTIONS details
EX_NO_MSG_FOUND - Message class / number does not exist.
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CNVA_GET_MSG_DOCU 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_ev_text | TYPE STRING, " | |||
| lv_iv_msgcls | TYPE ARBGB, " | |||
| lv_ex_no_msg_found | TYPE ARBGB, " | |||
| lv_iv_msgnr | TYPE MSGNR, " | |||
| lv_iv_langu | TYPE SPRAS. " |
|   CALL FUNCTION 'CNVA_GET_MSG_DOCU' "Get documentation |
| EXPORTING | ||
| IV_MSGCLS | = lv_iv_msgcls | |
| IV_MSGNR | = lv_iv_msgnr | |
| IV_LANGU | = lv_iv_langu | |
| IMPORTING | ||
| EV_TEXT | = lv_ev_text | |
| EXCEPTIONS | ||
| EX_NO_MSG_FOUND = 1 | ||
| . " CNVA_GET_MSG_DOCU | ||
ABAP code using 7.40 inline data declarations to call FM CNVA_GET_MSG_DOCU
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