SAP CNV_TDMS_08_GET_EXEC_NUM_P Function Module for
CNV_TDMS_08_GET_EXEC_NUM_P is a standard cnv tdms 08 get exec num p 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 tdms 08 get exec num p FM, simply by entering the name CNV_TDMS_08_GET_EXEC_NUM_P into the relevant SAP transaction such as SE37 or SE38.
Function Group: CNV_TDMS_08_P
Program Name: SAPLCNV_TDMS_08_P
Main Program: SAPLCNV_TDMS_08_P
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function CNV_TDMS_08_GET_EXEC_NUM_P 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_TDMS_08_GET_EXEC_NUM_P'".
EXPORTING
GD_PACKID = "
GD_PHASE = "
GD_ACT_ID = "
TABLES
LT_STATE = "
IMPORTING Parameters details for CNV_TDMS_08_GET_EXEC_NUM_P
GD_PACKID -
Data type: CNV_MBT_PACKIDOptional: No
Call by Reference: No ( called with pass by value option)
GD_PHASE -
Data type: CNV_MBT_PHASEOptional: No
Call by Reference: No ( called with pass by value option)
GD_ACT_ID -
Data type: CNV_MBT_ACTIVITYOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CNV_TDMS_08_GET_EXEC_NUM_P
LT_STATE -
Data type: CNVMBTSTATEOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CNV_TDMS_08_GET_EXEC_NUM_P 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_lt_state | TYPE STANDARD TABLE OF CNVMBTSTATE, " | |||
lv_gd_packid | TYPE CNV_MBT_PACKID, " | |||
lv_gd_phase | TYPE CNV_MBT_PHASE, " | |||
lv_gd_act_id | TYPE CNV_MBT_ACTIVITY. " |
  CALL FUNCTION 'CNV_TDMS_08_GET_EXEC_NUM_P' " |
EXPORTING | ||
GD_PACKID | = lv_gd_packid | |
GD_PHASE | = lv_gd_phase | |
GD_ACT_ID | = lv_gd_act_id | |
TABLES | ||
LT_STATE | = lt_lt_state | |
. " CNV_TDMS_08_GET_EXEC_NUM_P |
ABAP code using 7.40 inline data declarations to call FM CNV_TDMS_08_GET_EXEC_NUM_P
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