SAP CNV_MBT_L_STATE_FINISH Function Module for Disconnect from PCL state management after sending final state









CNV_MBT_L_STATE_FINISH is a standard cnv mbt l state finish SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Disconnect from PCL state management after sending final state 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 l state finish FM, simply by entering the name CNV_MBT_L_STATE_FINISH into the relevant SAP transaction such as SE37 or SE38.

Function Group: CNV_MBT_L_STATE
Program Name: SAPLCNV_MBT_L_STATE
Main Program: SAPLCNV_MBT_L_STATE
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function CNV_MBT_L_STATE_FINISH 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_L_STATE_FINISH'"Disconnect from PCL state management after sending final state
EXPORTING
PACKID = "
PHASE = "
ACTIVITY_ID = "
* IR_LOGGER = "ULV Logger

EXCEPTIONS
UPDATE_FAILED = 1
.



IMPORTING Parameters details for CNV_MBT_L_STATE_FINISH

PACKID -

Data type: CNVMBTACTIVE-PACKID
Optional: No
Call by Reference: No ( called with pass by value option)

PHASE -

Data type: CNVMBTACTIVE-PHASE
Optional: No
Call by Reference: No ( called with pass by value option)

ACTIVITY_ID -

Data type: CNVMBTACTIVITY-ACTIVITY_ID
Optional: No
Call by Reference: No ( called with pass by value option)

IR_LOGGER - ULV Logger

Data type: CL_CNV_MBT_ULV_LOGGER
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

UPDATE_FAILED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for CNV_MBT_L_STATE_FINISH 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_update_failed  TYPE CNVMBTACTIVE, "   
lv_phase  TYPE CNVMBTACTIVE-PHASE, "   
lv_activity_id  TYPE CNVMBTACTIVITY-ACTIVITY_ID, "   
lv_ir_logger  TYPE CL_CNV_MBT_ULV_LOGGER. "   

  CALL FUNCTION 'CNV_MBT_L_STATE_FINISH'  "Disconnect from PCL state management after sending final state
    EXPORTING
         PACKID = lv_packid
         PHASE = lv_phase
         ACTIVITY_ID = lv_activity_id
         IR_LOGGER = lv_ir_logger
    EXCEPTIONS
        UPDATE_FAILED = 1
. " CNV_MBT_L_STATE_FINISH




ABAP code using 7.40 inline data declarations to call FM CNV_MBT_L_STATE_FINISH

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 PHASE FROM CNVMBTACTIVE INTO @DATA(ld_phase).
 
"SELECT single ACTIVITY_ID FROM CNVMBTACTIVITY INTO @DATA(ld_activity_id).
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!