SAP CNV_TDMS_SCR_COPY_INCLUDES Function Module for Copy Includes from Control to Execution System
CNV_TDMS_SCR_COPY_INCLUDES is a standard cnv tdms scr copy includes SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Copy Includes from Control to Execution System 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 tdms scr copy includes FM, simply by entering the name CNV_TDMS_SCR_COPY_INCLUDES into the relevant SAP transaction such as SE37 or SE38.
Function Group: CNV_TDMS_SCR
Program Name: SAPLCNV_TDMS_SCR
Main Program: SAPLCNV_TDMS_SCR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CNV_TDMS_SCR_COPY_INCLUDES 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_SCR_COPY_INCLUDES'"Copy Includes from Control to Execution System.
EXPORTING
IV_PACKID = "Package Number of Transformation / Analysis Package
TABLES
XT_INCL = "Conversion: of includes required by conversion package
EXCEPTIONS
DESTINATION_NOT_FOUND = 1 INCLUDE_READ_ERROR = 10 INCLUDE_LENGTH_EXCEEDS = 11 NO_AUTHORITY = 2 INCLUDE_DOES_NOT_EXIST = 3 ERROR_READING_INCLUDE_SOURCE = 4 ERROR_WRITING_TADIR_ENTRY = 5 INCLUDE_IN_WRONG_NAMESPACE = 6 ERROR_WRITING_TRDIR_ENTRY = 7 INCLUDE_CREATION_ERROR = 8 ERROR_WRITING_INCLUDE_SOURCE = 9
IMPORTING Parameters details for CNV_TDMS_SCR_COPY_INCLUDES
IV_PACKID - Package Number of Transformation / Analysis Package
Data type: CNV_MBT_PACKIDOptional: No
Call by Reference: Yes
TABLES Parameters details for CNV_TDMS_SCR_COPY_INCLUDES
XT_INCL - Conversion: of includes required by conversion package
Data type: CNVTDMSSCR_TT_COPY_INCLOptional: No
Call by Reference: Yes
EXCEPTIONS details
DESTINATION_NOT_FOUND - Destination Not Found
Data type:Optional: No
Call by Reference: Yes
INCLUDE_READ_ERROR - Error Reading Include source
Data type:Optional: No
Call by Reference: Yes
INCLUDE_LENGTH_EXCEEDS - Include Length Exceeds 72 Characters
Data type:Optional: No
Call by Reference: Yes
NO_AUTHORITY - No authority to perform this action
Data type:Optional: No
Call by Reference: Yes
INCLUDE_DOES_NOT_EXIST - Include does not exist on specified destination
Data type:Optional: No
Call by Reference: Yes
ERROR_READING_INCLUDE_SOURCE - Error while reading source of include
Data type:Optional: No
Call by Reference: Yes
ERROR_WRITING_TADIR_ENTRY - Error Writing Tadir Entry
Data type:Optional: No
Call by Reference: Yes
INCLUDE_IN_WRONG_NAMESPACE - Include in wrong Name space
Data type:Optional: No
Call by Reference: Yes
ERROR_WRITING_TRDIR_ENTRY - Error Writing TRDIR entry
Data type:Optional: No
Call by Reference: Yes
INCLUDE_CREATION_ERROR - Include creation error
Data type:Optional: No
Call by Reference: Yes
ERROR_WRITING_INCLUDE_SOURCE - Error Writing Include source
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CNV_TDMS_SCR_COPY_INCLUDES 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_xt_incl | TYPE STANDARD TABLE OF CNVTDMSSCR_TT_COPY_INCL, " | |||
| lv_iv_packid | TYPE CNV_MBT_PACKID, " | |||
| lv_destination_not_found | TYPE CNV_MBT_PACKID, " | |||
| lv_include_read_error | TYPE CNV_MBT_PACKID, " | |||
| lv_include_length_exceeds | TYPE CNV_MBT_PACKID, " | |||
| lv_no_authority | TYPE CNV_MBT_PACKID, " | |||
| lv_include_does_not_exist | TYPE CNV_MBT_PACKID, " | |||
| lv_error_reading_include_source | TYPE CNV_MBT_PACKID, " | |||
| lv_error_writing_tadir_entry | TYPE CNV_MBT_PACKID, " | |||
| lv_include_in_wrong_namespace | TYPE CNV_MBT_PACKID, " | |||
| lv_error_writing_trdir_entry | TYPE CNV_MBT_PACKID, " | |||
| lv_include_creation_error | TYPE CNV_MBT_PACKID, " | |||
| lv_error_writing_include_source | TYPE CNV_MBT_PACKID. " |
| CALL FUNCTION 'CNV_TDMS_SCR_COPY_INCLUDES' "Copy Includes from Control to Execution System |
| EXPORTING | ||
| IV_PACKID | = lv_iv_packid | |
| TABLES | ||
| XT_INCL | = lt_xt_incl | |
| EXCEPTIONS | ||
| DESTINATION_NOT_FOUND = 1 | ||
| INCLUDE_READ_ERROR = 10 | ||
| INCLUDE_LENGTH_EXCEEDS = 11 | ||
| NO_AUTHORITY = 2 | ||
| INCLUDE_DOES_NOT_EXIST = 3 | ||
| ERROR_READING_INCLUDE_SOURCE = 4 | ||
| ERROR_WRITING_TADIR_ENTRY = 5 | ||
| INCLUDE_IN_WRONG_NAMESPACE = 6 | ||
| ERROR_WRITING_TRDIR_ENTRY = 7 | ||
| INCLUDE_CREATION_ERROR = 8 | ||
| ERROR_WRITING_INCLUDE_SOURCE = 9 | ||
| . " CNV_TDMS_SCR_COPY_INCLUDES | ||
ABAP code using 7.40 inline data declarations to call FM CNV_TDMS_SCR_COPY_INCLUDES
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