SAP CNV_MBT_NOTE_GET_NOTE Function Module for Read all data of the note
CNV_MBT_NOTE_GET_NOTE is a standard cnv mbt note get note SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read all data of the note 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 cnv mbt note get note FM, simply by entering the name CNV_MBT_NOTE_GET_NOTE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CNVMBTNOTES
Program Name: SAPLCNVMBTNOTES
Main Program: SAPLCNVMBTNOTES
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CNV_MBT_NOTE_GET_NOTE 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 'CNV_MBT_NOTE_GET_NOTE'"Read all data of the note.
EXPORTING
IP_PROJECT = "Identification of MBT Project
IP_SUBPROJECT = "Identification of MBT Subproject
IP_PACKID = "Package Number to Specify CMIS and TDMS Packages
IMPORTING
EX_LOCKED = "Information about lock status of the note
TABLES
T_DOKIL = "Index for Documentation Table DOKH
T_DOKHL = "Documentation: Headers
T_DOKTL = "Documentation - text lines
EXCEPTIONS
NOTE_NOT_EXIST = 1 ERR_READ_DOC_HEADER = 2 ERR_READ_TEXT_LINES = 3
IMPORTING Parameters details for CNV_MBT_NOTE_GET_NOTE
IP_PROJECT - Identification of MBT Project
Data type: CNV_MBT_PROJOptional: No
Call by Reference: No ( called with pass by value option)
IP_SUBPROJECT - Identification of MBT Subproject
Data type: CNV_MBT_SUBPROJOptional: No
Call by Reference: No ( called with pass by value option)
IP_PACKID - Package Number to Specify CMIS and TDMS Packages
Data type: CNV_MBT_PACKIDOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CNV_MBT_NOTE_GET_NOTE
EX_LOCKED - Information about lock status of the note
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CNV_MBT_NOTE_GET_NOTE
T_DOKIL - Index for Documentation Table DOKH
Data type: DOKILOptional: No
Call by Reference: Yes
T_DOKHL - Documentation: Headers
Data type: DOKHLOptional: No
Call by Reference: Yes
T_DOKTL - Documentation - text lines
Data type: DOKTLOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOTE_NOT_EXIST - The note does not exist
Data type:Optional: No
Call by Reference: Yes
ERR_READ_DOC_HEADER - Error while reading document header
Data type:Optional: No
Call by Reference: Yes
ERR_READ_TEXT_LINES - Error while reading documentation text lines (DOKTL)
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CNV_MBT_NOTE_GET_NOTE 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: | ||||
| lt_t_dokil | TYPE STANDARD TABLE OF DOKIL, " | |||
| lv_ex_locked | TYPE C, " | |||
| lv_ip_project | TYPE CNV_MBT_PROJ, " | |||
| lv_note_not_exist | TYPE CNV_MBT_PROJ, " | |||
| lt_t_dokhl | TYPE STANDARD TABLE OF DOKHL, " | |||
| lv_ip_subproject | TYPE CNV_MBT_SUBPROJ, " | |||
| lv_err_read_doc_header | TYPE CNV_MBT_SUBPROJ, " | |||
| lt_t_doktl | TYPE STANDARD TABLE OF DOKTL, " | |||
| lv_ip_packid | TYPE CNV_MBT_PACKID, " | |||
| lv_err_read_text_lines | TYPE CNV_MBT_PACKID. " |
|   CALL FUNCTION 'CNV_MBT_NOTE_GET_NOTE' "Read all data of the note |
| EXPORTING | ||
| IP_PROJECT | = lv_ip_project | |
| IP_SUBPROJECT | = lv_ip_subproject | |
| IP_PACKID | = lv_ip_packid | |
| IMPORTING | ||
| EX_LOCKED | = lv_ex_locked | |
| TABLES | ||
| T_DOKIL | = lt_t_dokil | |
| T_DOKHL | = lt_t_dokhl | |
| T_DOKTL | = lt_t_doktl | |
| EXCEPTIONS | ||
| NOTE_NOT_EXIST = 1 | ||
| ERR_READ_DOC_HEADER = 2 | ||
| ERR_READ_TEXT_LINES = 3 | ||
| . " CNV_MBT_NOTE_GET_NOTE | ||
ABAP code using 7.40 inline data declarations to call FM CNV_MBT_NOTE_GET_NOTE
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