SAP CNV_INT_STATE_SET Function Module for









CNV_INT_STATE_SET is a standard cnv int state set SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 int state set FM, simply by entering the name CNV_INT_STATE_SET into the relevant SAP transaction such as SE37 or SE38.

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



Function CNV_INT_STATE_SET 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_INT_STATE_SET'"
EXPORTING
PACKID = "
PHASE = "
PROGNAME = "
* RUNCOUNT = "
* STATE = "
* ROWSTOTAL = "
.



IMPORTING Parameters details for CNV_INT_STATE_SET

PACKID -

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

PHASE -

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

PROGNAME -

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

RUNCOUNT -

Data type: CNVSTATE-TASKID
Optional: Yes
Call by Reference: No ( called with pass by value option)

STATE -

Data type: CNVSTATE-STATE_LOG
Optional: Yes
Call by Reference: No ( called with pass by value option)

ROWSTOTAL -

Data type: CNVSTATE-RECTOTAL
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for CNV_INT_STATE_SET 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 CNVSTATE-PACKID, "   
lv_phase  TYPE CNVSTATE-PHASE, "   
lv_progname  TYPE CNVSTATE-PROGNAME, "   
lv_runcount  TYPE CNVSTATE-TASKID, "   
lv_state  TYPE CNVSTATE-STATE_LOG, "   
lv_rowstotal  TYPE CNVSTATE-RECTOTAL. "   

  CALL FUNCTION 'CNV_INT_STATE_SET'  "
    EXPORTING
         PACKID = lv_packid
         PHASE = lv_phase
         PROGNAME = lv_progname
         RUNCOUNT = lv_runcount
         STATE = lv_state
         ROWSTOTAL = lv_rowstotal
. " CNV_INT_STATE_SET




ABAP code using 7.40 inline data declarations to call FM CNV_INT_STATE_SET

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 CNVSTATE INTO @DATA(ld_packid).
 
"SELECT single PHASE FROM CNVSTATE INTO @DATA(ld_phase).
 
"SELECT single PROGNAME FROM CNVSTATE INTO @DATA(ld_progname).
 
"SELECT single TASKID FROM CNVSTATE INTO @DATA(ld_runcount).
 
"SELECT single STATE_LOG FROM CNVSTATE INTO @DATA(ld_state).
 
"SELECT single RECTOTAL FROM CNVSTATE INTO @DATA(ld_rowstotal).
 


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!