SAP COM_SETTYPE_EXIST Function Module for

Search SAP Function Modules

COM_SETTYPE_EXIST is a standard com settype exist 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 com settype exist FM, simply by entering the name COM_SETTYPE_EXIST into the relevant SAP transaction such as SE37 or SE38.

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

Function COM_SETTYPE_EXIST 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 'COM_SETTYPE_EXIST'"
  EXPORTING
*  IV_SETTYPE_NAME =  "Set Type's Identification
*  IV_SETTYPE_GUID =  "Set Type's Internal Key
*  IV_BUS_OBJTYPE =  "
*  IV_ORG_UNIT =  "
*  IV_PROD_COMP_TYPE =  "
*  IV_LANGU = SY-LANGU "SAP R/3 System, Current Language

 IMPORTING
   ES_SETTYPE_INFO =  "
   ES_SETTYPE_T_INFO =  "Set Type Text

EXCEPTIONS
   NOTHING_EXISTS = 1    OBJECT_IN_SAP_NAMESPACE = 10    OBJECT_ALREADY_EXISTS = 11    INVALID_PARAMETER = 12    SETTYPE_IN_STATUS_NEW = 2    SETTYPE_IS_NOT_ACTIVE = 3    TABLE_ENTRY_MISSING = 4    DDIC_OBJECT_ALREADY_EXISTS = 5    DDIC_OBJECT_NOT_FOUND = 6    DDIC_OBJECT_NOT_ACTIVE = 7    DDIC_READ_ERROR = 8    OBJECT_IN_CUSTOMER_NAMESPACE = 9 

.

IMPORTING Parameters details for COM_SETTYPE_EXIST

IV_SETTYPE_NAME - Set Type's Identification

Data type: COMT_FRGTYPE_ID
Optional: Yes
Call by Reference: Yes

IV_SETTYPE_GUID - Set Type's Internal Key

Data type: COMT_FRGTYPE_GUID
Optional: Yes
Call by Reference: Yes

IV_BUS_OBJTYPE -

Data type: COMT_BUS_OBJTYPE
Optional: Yes
Call by Reference: Yes

IV_ORG_UNIT -

Data type: COMT_PR_ORG_TYPE
Optional: Yes
Call by Reference: Yes

IV_PROD_COMP_TYPE -

Data type: COMT_PROD_COMP_TYPE
Optional: Yes
Call by Reference: Yes

IV_LANGU - SAP R/3 System, Current Language

Data type: SYLANGU
Default: SY-LANGU
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for COM_SETTYPE_EXIST

ES_SETTYPE_INFO -

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

ES_SETTYPE_T_INFO - Set Type Text

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

EXCEPTIONS details

NOTHING_EXISTS -

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

OBJECT_IN_SAP_NAMESPACE -

Data type:
Optional: No
Call by Reference: Yes

OBJECT_ALREADY_EXISTS -

Data type:
Optional: No
Call by Reference: Yes

INVALID_PARAMETER - Invalid parameter value

Data type:
Optional: No
Call by Reference: Yes

SETTYPE_IN_STATUS_NEW -

Data type:
Optional: No
Call by Reference: Yes

SETTYPE_IS_NOT_ACTIVE -

Data type:
Optional: No
Call by Reference: Yes

TABLE_ENTRY_MISSING -

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

DDIC_OBJECT_ALREADY_EXISTS -

Data type:
Optional: No
Call by Reference: Yes

DDIC_OBJECT_NOT_FOUND -

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

DDIC_OBJECT_NOT_ACTIVE -

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

DDIC_READ_ERROR -

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

OBJECT_IN_CUSTOMER_NAMESPACE -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for COM_SETTYPE_EXIST 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.

ABAP code using 7.40 inline data declarations to call FM COM_SETTYPE_EXIST

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