SAP CNV_CMIS_A_20_GET_SYS_PROP Function Module for Get system properties from landscape









CNV_CMIS_A_20_GET_SYS_PROP is a standard cnv cmis a 20 get sys prop SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get system properties from landscape 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 a 20 get sys prop FM, simply by entering the name CNV_CMIS_A_20_GET_SYS_PROP into the relevant SAP transaction such as SE37 or SE38.

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



Function CNV_CMIS_A_20_GET_SYS_PROP 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_A_20_GET_SYS_PROP'"Get system properties from landscape
  EXPORTING
   PACKID =  "Package Number to Specify CMIS and TDMS Packages
*  VERSION = '001' "Version number
   EXEC_TARGET =  "Specifies The Target System the Activity is Executed in

 IMPORTING
   DESTINATION_ID =  "SAPOSCOL destination
   EXEC_DESCR =  "
   SYSTEM_ID =  "R/3 System, name of R/3 System
   CLIENT =  "R/3 System, client number from logon

EXCEPTIONS
   NO_PACKID = 1    INVALID_EXEC_TARGET = 2    EXEC_TARGET_NOT_FOUND = 3    OTHERS = 4
.



IMPORTING Parameters details for CNV_CMIS_A_20_GET_SYS_PROP

PACKID - Package Number to Specify CMIS and TDMS Packages

Data type: CNV_MBT_PACKID
Optional: No
Call by Reference: No ( called with pass by value option)

VERSION - Version number

Data type: CNVCMIS_A_20_VERSN
Default: '001'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXEC_TARGET - Specifies The Target System the Activity is Executed in

Data type: CNV_MBT_EXEC_TARGET
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for CNV_CMIS_A_20_GET_SYS_PROP

DESTINATION_ID - SAPOSCOL destination

Data type: RFC_DEST
Optional: No
Call by Reference: No ( called with pass by value option)

EXEC_DESCR -

Data type: CNVCMIS_A_20_DESCR
Optional: No
Call by Reference: No ( called with pass by value option)

SYSTEM_ID - R/3 System, name of R/3 System

Data type: SYSYSID
Optional: No
Call by Reference: No ( called with pass by value option)

CLIENT - R/3 System, client number from logon

Data type: SYMANDT
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

NO_PACKID - No value for PackID passed

Data type:
Optional: No
Call by Reference: Yes

INVALID_EXEC_TARGET - Invalid or not supported system type

Data type:
Optional: No
Call by Reference: Yes

EXEC_TARGET_NOT_FOUND - System type not found in landscape

Data type:
Optional: No
Call by Reference: Yes

OTHERS - Others

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CNV_CMIS_A_20_GET_SYS_PROP 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 CNV_MBT_PACKID, "   
lv_no_packid  TYPE CNV_MBT_PACKID, "   
lv_destination_id  TYPE RFC_DEST, "   
lv_version  TYPE CNVCMIS_A_20_VERSN, "   '001'
lv_exec_descr  TYPE CNVCMIS_A_20_DESCR, "   
lv_invalid_exec_target  TYPE CNVCMIS_A_20_DESCR, "   
lv_system_id  TYPE SYSYSID, "   
lv_exec_target  TYPE CNV_MBT_EXEC_TARGET, "   
lv_exec_target_not_found  TYPE CNV_MBT_EXEC_TARGET, "   
lv_client  TYPE SYMANDT, "   
lv_others  TYPE SYMANDT. "   

  CALL FUNCTION 'CNV_CMIS_A_20_GET_SYS_PROP'  "Get system properties from landscape
    EXPORTING
         PACKID = lv_packid
         VERSION = lv_version
         EXEC_TARGET = lv_exec_target
    IMPORTING
         DESTINATION_ID = lv_destination_id
         EXEC_DESCR = lv_exec_descr
         SYSTEM_ID = lv_system_id
         CLIENT = lv_client
    EXCEPTIONS
        NO_PACKID = 1
        INVALID_EXEC_TARGET = 2
        EXEC_TARGET_NOT_FOUND = 3
        OTHERS = 4
. " CNV_CMIS_A_20_GET_SYS_PROP




ABAP code using 7.40 inline data declarations to call FM CNV_CMIS_A_20_GET_SYS_PROP

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.

 
 
 
DATA(ld_version) = '001'.
 
 
 
 
 
 
 
 


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!