SAP CNV_CMIS_30_EXPORT Function Module for Export the internal tables to the database









CNV_CMIS_30_EXPORT is a standard cnv cmis 30 export SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Export the internal tables to the database 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 cmis 30 export FM, simply by entering the name CNV_CMIS_30_EXPORT into the relevant SAP transaction such as SE37 or SE38.

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



Function CNV_CMIS_30_EXPORT 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_CMIS_30_EXPORT'"Export the internal tables to the database
  EXPORTING
   IS_KEY =  "CMIS system Comparision stuct for the key
   IT_SDACCSEQ =  "Table Type of CNVCMIS_A_30_SDACCSEQ
   IT_SDDICINFO =  "CMIS: Structure to store Table and Fields details
   IT_GTINFO =  "Table of type CNVCMIS_A_30_GTINFO
   IT_GTCOMPTAB =  "Table of type SPAM_CVERS
   IT_GTLANG =  "Table of type  CNVCMIS_A_30_GTLANG
   IS_CODEPAGE =  "Code page details for CMIS System Analysis
   IT_PRODHS_USED =  "CMIS system analysis structure for prod heirarchy usage info
   IT_PRODHS =  "Cmis system analysis structure for prod hierarchy info
   IT_LISCURRENCY =  "Table type for cnvcmis_a_30_liscurr
   IT_LISDICINFO =  "Table type for SD tables Dictionary information

EXCEPTIONS
   EXPORT_UNSUCCESSFUL = 1
.



IMPORTING Parameters details for CNV_CMIS_30_EXPORT

IS_KEY - CMIS system Comparision stuct for the key

Data type: CNVCMIS_A_30_KEY_STRUC
Optional: No
Call by Reference: Yes

IT_SDACCSEQ - Table Type of CNVCMIS_A_30_SDACCSEQ

Data type: CNVCMIS_A_30_TAB_SDACCSEQ
Optional: No
Call by Reference: Yes

IT_SDDICINFO - CMIS: Structure to store Table and Fields details

Data type: CNVCMIS_A_30_TAB_DIC
Optional: No
Call by Reference: Yes

IT_GTINFO - Table of type CNVCMIS_A_30_GTINFO

Data type: CNVCMIS_A_30_TAB_GTINFO
Optional: No
Call by Reference: Yes

IT_GTCOMPTAB - Table of type SPAM_CVERS

Data type: CNVCMIS_A_30_TAB_SPAM_CVERS
Optional: No
Call by Reference: Yes

IT_GTLANG - Table of type CNVCMIS_A_30_GTLANG

Data type: CNVCMIS_A_30_TAB_GTLANG
Optional: No
Call by Reference: Yes

IS_CODEPAGE - Code page details for CMIS System Analysis

Data type: CNVCMIS_A_30_CODEPAGE
Optional: No
Call by Reference: Yes

IT_PRODHS_USED - CMIS system analysis structure for prod heirarchy usage info

Data type: CNVCMIS_A_30_TAB_PRODHSINFO
Optional: No
Call by Reference: Yes

IT_PRODHS - Cmis system analysis structure for prod hierarchy info

Data type: CNVCMIS_A_30_TAB_PRODHS
Optional: No
Call by Reference: Yes

IT_LISCURRENCY - Table type for cnvcmis_a_30_liscurr

Data type: CNVCMIS_A_30_TAB_LISCURRENCY
Optional: No
Call by Reference: Yes

IT_LISDICINFO - Table type for SD tables Dictionary information

Data type: CNVCMIS_A_30_TAB_DIC
Optional: No
Call by Reference: Yes

EXCEPTIONS details

EXPORT_UNSUCCESSFUL - INTERNAL TABLES COULD NOT BE EXPORTED

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CNV_CMIS_30_EXPORT 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_is_key  TYPE CNVCMIS_A_30_KEY_STRUC, "   
lv_export_unsuccessful  TYPE CNVCMIS_A_30_KEY_STRUC, "   
lv_it_sdaccseq  TYPE CNVCMIS_A_30_TAB_SDACCSEQ, "   
lv_it_sddicinfo  TYPE CNVCMIS_A_30_TAB_DIC, "   
lv_it_gtinfo  TYPE CNVCMIS_A_30_TAB_GTINFO, "   
lv_it_gtcomptab  TYPE CNVCMIS_A_30_TAB_SPAM_CVERS, "   
lv_it_gtlang  TYPE CNVCMIS_A_30_TAB_GTLANG, "   
lv_is_codepage  TYPE CNVCMIS_A_30_CODEPAGE, "   
lv_it_prodhs_used  TYPE CNVCMIS_A_30_TAB_PRODHSINFO, "   
lv_it_prodhs  TYPE CNVCMIS_A_30_TAB_PRODHS, "   
lv_it_liscurrency  TYPE CNVCMIS_A_30_TAB_LISCURRENCY, "   
lv_it_lisdicinfo  TYPE CNVCMIS_A_30_TAB_DIC. "   

  CALL FUNCTION 'CNV_CMIS_30_EXPORT'  "Export the internal tables to the database
    EXPORTING
         IS_KEY = lv_is_key
         IT_SDACCSEQ = lv_it_sdaccseq
         IT_SDDICINFO = lv_it_sddicinfo
         IT_GTINFO = lv_it_gtinfo
         IT_GTCOMPTAB = lv_it_gtcomptab
         IT_GTLANG = lv_it_gtlang
         IS_CODEPAGE = lv_is_codepage
         IT_PRODHS_USED = lv_it_prodhs_used
         IT_PRODHS = lv_it_prodhs
         IT_LISCURRENCY = lv_it_liscurrency
         IT_LISDICINFO = lv_it_lisdicinfo
    EXCEPTIONS
        EXPORT_UNSUCCESSFUL = 1
. " CNV_CMIS_30_EXPORT




ABAP code using 7.40 inline data declarations to call FM CNV_CMIS_30_EXPORT

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



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!