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

Function CNV_MBT_STATE_GET 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_STATE_GET'"Determine central PCL state of activity.
EXPORTING
PACKID = "
PHASE = "
ACTIVITY_ID = "
* EXEC_NUM = "
* ALL_AS_TABLE = "flag
IMPORTING
STATE_TEC = "
STATE_LOG = "
ABORTED = "
LAST_EXEC_NUM = "
TABLES
* T_EX_CNVMBTSTATE = "
EXCEPTIONS
ENTRY_DOES_NOT_EXIST = 1
IMPORTING Parameters details for CNV_MBT_STATE_GET
PACKID -
Data type: CNVMBTACTIVE-PACKIDOptional: No
Call by Reference: No ( called with pass by value option)
PHASE -
Data type: CNVMBTACTIVE-PHASEOptional: No
Call by Reference: No ( called with pass by value option)
ACTIVITY_ID -
Data type: CNVMBTACTIVITY-ACTIVITY_IDOptional: No
Call by Reference: No ( called with pass by value option)
EXEC_NUM -
Data type: CNVMBTSTATE-EXEC_NUMOptional: Yes
Call by Reference: No ( called with pass by value option)
ALL_AS_TABLE - flag
Data type: CNVMBTRETSTR-AND_RETURNOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CNV_MBT_STATE_GET
STATE_TEC -
Data type: CNVMBTSTATE-STATE_TECOptional: No
Call by Reference: No ( called with pass by value option)
STATE_LOG -
Data type: CNVMBTSTATE-STATE_LOGOptional: No
Call by Reference: No ( called with pass by value option)
ABORTED -
Data type: CNVMBTSTATE-ABORTEDOptional: No
Call by Reference: No ( called with pass by value option)
LAST_EXEC_NUM -
Data type: CNVMBTSTATE-EXEC_NUMOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CNV_MBT_STATE_GET
T_EX_CNVMBTSTATE -
Data type: CNVMBTSTATEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ENTRY_DOES_NOT_EXIST -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CNV_MBT_STATE_GET 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_packid | TYPE CNVMBTACTIVE-PACKID, " | |||
| lv_state_tec | TYPE CNVMBTSTATE-STATE_TEC, " | |||
| lt_t_ex_cnvmbtstate | TYPE STANDARD TABLE OF CNVMBTSTATE, " | |||
| lv_entry_does_not_exist | TYPE CNVMBTSTATE, " | |||
| lv_phase | TYPE CNVMBTACTIVE-PHASE, " | |||
| lv_state_log | TYPE CNVMBTSTATE-STATE_LOG, " | |||
| lv_aborted | TYPE CNVMBTSTATE-ABORTED, " | |||
| lv_activity_id | TYPE CNVMBTACTIVITY-ACTIVITY_ID, " | |||
| lv_exec_num | TYPE CNVMBTSTATE-EXEC_NUM, " | |||
| lv_last_exec_num | TYPE CNVMBTSTATE-EXEC_NUM, " | |||
| lv_all_as_table | TYPE CNVMBTRETSTR-AND_RETURN. " |
|   CALL FUNCTION 'CNV_MBT_STATE_GET' "Determine central PCL state of activity |
| EXPORTING | ||
| PACKID | = lv_packid | |
| PHASE | = lv_phase | |
| ACTIVITY_ID | = lv_activity_id | |
| EXEC_NUM | = lv_exec_num | |
| ALL_AS_TABLE | = lv_all_as_table | |
| IMPORTING | ||
| STATE_TEC | = lv_state_tec | |
| STATE_LOG | = lv_state_log | |
| ABORTED | = lv_aborted | |
| LAST_EXEC_NUM | = lv_last_exec_num | |
| TABLES | ||
| T_EX_CNVMBTSTATE | = lt_t_ex_cnvmbtstate | |
| EXCEPTIONS | ||
| ENTRY_DOES_NOT_EXIST = 1 | ||
| . " CNV_MBT_STATE_GET | ||
ABAP code using 7.40 inline data declarations to call FM CNV_MBT_STATE_GET
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 PACKID FROM CNVMBTACTIVE INTO @DATA(ld_packid). | ||||
| "SELECT single STATE_TEC FROM CNVMBTSTATE INTO @DATA(ld_state_tec). | ||||
| "SELECT single PHASE FROM CNVMBTACTIVE INTO @DATA(ld_phase). | ||||
| "SELECT single STATE_LOG FROM CNVMBTSTATE INTO @DATA(ld_state_log). | ||||
| "SELECT single ABORTED FROM CNVMBTSTATE INTO @DATA(ld_aborted). | ||||
| "SELECT single ACTIVITY_ID FROM CNVMBTACTIVITY INTO @DATA(ld_activity_id). | ||||
| "SELECT single EXEC_NUM FROM CNVMBTSTATE INTO @DATA(ld_exec_num). | ||||
| "SELECT single EXEC_NUM FROM CNVMBTSTATE INTO @DATA(ld_last_exec_num). | ||||
| "SELECT single AND_RETURN FROM CNVMBTRETSTR INTO @DATA(ld_all_as_table). | ||||
Search for further information about these or an SAP related objects