SAP CNV_INT_STATE_INITIALIZE Function Module for
CNV_INT_STATE_INITIALIZE is a standard cnv int state initialize 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 initialize FM, simply by entering the name CNV_INT_STATE_INITIALIZE 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_INITIALIZE 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_INITIALIZE'".
EXPORTING
* RUNMODE = "Conversion: Type of program run
* TABNAME = "Table Name
* PROGNAME = "ABAP Program Name
IMPORTING
RERUNARG = "
CLUFIELDS = "
EXCEPTIONS
NO_PACKAGE_ACTIVE = 1 PROGRAM_NOT_FOUND = 2 WRONG_STATE = 3 PRECURSOR_NOT_OK = 4 ENQUEUE_ERROR = 5
IMPORTING Parameters details for CNV_INT_STATE_INITIALIZE
RUNMODE - Conversion: Type of program run
Data type: CNVSTATE-RUNMODEOptional: Yes
Call by Reference: No ( called with pass by value option)
TABNAME - Table Name
Data type: CNVSTATE-TABNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
PROGNAME - ABAP Program Name
Data type: CNVSTATE-PROGNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CNV_INT_STATE_INITIALIZE
RERUNARG -
Data type: CNVSTATE-RERUNARGOptional: No
Call by Reference: No ( called with pass by value option)
CLUFIELDS -
Data type: CNVCLUSTEROptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_PACKAGE_ACTIVE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PROGRAM_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WRONG_STATE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PRECURSOR_NOT_OK -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ENQUEUE_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CNV_INT_STATE_INITIALIZE 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_runmode | TYPE CNVSTATE-RUNMODE, " | |||
| lv_rerunarg | TYPE CNVSTATE-RERUNARG, " | |||
| lv_no_package_active | TYPE CNVSTATE, " | |||
| lv_tabname | TYPE CNVSTATE-TABNAME, " | |||
| lv_clufields | TYPE CNVCLUSTER, " | |||
| lv_program_not_found | TYPE CNVCLUSTER, " | |||
| lv_progname | TYPE CNVSTATE-PROGNAME, " | |||
| lv_wrong_state | TYPE CNVSTATE, " | |||
| lv_precursor_not_ok | TYPE CNVSTATE, " | |||
| lv_enqueue_error | TYPE CNVSTATE. " |
|   CALL FUNCTION 'CNV_INT_STATE_INITIALIZE' " |
| EXPORTING | ||
| RUNMODE | = lv_runmode | |
| TABNAME | = lv_tabname | |
| PROGNAME | = lv_progname | |
| IMPORTING | ||
| RERUNARG | = lv_rerunarg | |
| CLUFIELDS | = lv_clufields | |
| EXCEPTIONS | ||
| NO_PACKAGE_ACTIVE = 1 | ||
| PROGRAM_NOT_FOUND = 2 | ||
| WRONG_STATE = 3 | ||
| PRECURSOR_NOT_OK = 4 | ||
| ENQUEUE_ERROR = 5 | ||
| . " CNV_INT_STATE_INITIALIZE | ||
ABAP code using 7.40 inline data declarations to call FM CNV_INT_STATE_INITIALIZE
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 RUNMODE FROM CNVSTATE INTO @DATA(ld_runmode). | ||||
| "SELECT single RERUNARG FROM CNVSTATE INTO @DATA(ld_rerunarg). | ||||
| "SELECT single TABNAME FROM CNVSTATE INTO @DATA(ld_tabname). | ||||
| "SELECT single PROGNAME FROM CNVSTATE INTO @DATA(ld_progname). | ||||
Search for further information about these or an SAP related objects