SAP COM_PME_CLASS_CREATE Function Module for
COM_PME_CLASS_CREATE is a standard com pme class create 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 pme class create FM, simply by entering the name COM_PME_CLASS_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: COM_PME_SV
Program Name: SAPLCOM_PME_SV
Main Program: SAPLCOM_PME_SV
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function COM_PME_CLASS_CREATE 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_PME_CLASS_CREATE'".
EXPORTING
CRM_HIERARCHY_GUID = "
* CONFIGURABLE = "
CRM_OBJECT_GUID = "
CRM_OBJECT_NAME = "
CRM_OBJECT_TYPE = "
* PARENT_GUID = "
* PARENT_TYPE = CO_CATEGORY_TYPE "
PR_ORG_TYPE = "Sales Organization
* PR_ORG_ID = "Distribution Channel
LOG_SYS = "R/3 System, Client Number from Logon
IMPORTING
PME_CRM_MAP_KEY = "
LOCKING_USER = "SAP System, User Logon Name
ES_LOG_MSG = "Application Log: Message Data
TABLES
* CLASS_DESCR = "
* CSTICS = "
EXCEPTIONS
NO_ACTIVE_SESSION = 1 CLASS_ALREADY_EXISTS = 2 FOREIGN_LOCK = 3 INVALID_PARAM = 4 API_ERROR = 5 SYSTEM_ERROR = 6 NO_PARENTS_FOUND = 7
IMPORTING Parameters details for COM_PME_CLASS_CREATE
CRM_HIERARCHY_GUID -
Data type: COMT_PME_CRM_GUIDOptional: No
Call by Reference: Yes
CONFIGURABLE -
Data type: COptional: Yes
Call by Reference: Yes
CRM_OBJECT_GUID -
Data type: COMT_PME_CRM_GUIDOptional: No
Call by Reference: Yes
CRM_OBJECT_NAME -
Data type: COMT_PRODUCT_IDOptional: No
Call by Reference: Yes
CRM_OBJECT_TYPE -
Data type: COMT_PME_CLASS_TYPEOptional: No
Call by Reference: Yes
PARENT_GUID -
Data type: COMT_PME_CRM_GUIDOptional: Yes
Call by Reference: Yes
PARENT_TYPE -
Data type: COMT_PME_CLASS_TYPEDefault: CO_CATEGORY_TYPE
Optional: Yes
Call by Reference: Yes
PR_ORG_TYPE - Sales Organization
Data type: COMT_PR_ORG_TYPEOptional: No
Call by Reference: Yes
PR_ORG_ID - Distribution Channel
Data type: COMT_PR_ORG_IDOptional: Yes
Call by Reference: Yes
LOG_SYS - R/3 System, Client Number from Logon
Data type: LOGSYSOptional: No
Call by Reference: Yes
EXPORTING Parameters details for COM_PME_CLASS_CREATE
PME_CRM_MAP_KEY -
Data type: COMT_PME_CRM_MAP_KEYOptional: No
Call by Reference: Yes
LOCKING_USER - SAP System, User Logon Name
Data type: SY-UNAMEOptional: No
Call by Reference: Yes
ES_LOG_MSG - Application Log: Message Data
Data type: BAL_S_MSGOptional: No
Call by Reference: Yes
TABLES Parameters details for COM_PME_CLASS_CREATE
CLASS_DESCR -
Data type: COMT_PME_CLASS_DESCR_TABLEOptional: Yes
Call by Reference: Yes
CSTICS -
Data type: COMT_PME_CSTIC_TABLEOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
NO_ACTIVE_SESSION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CLASS_ALREADY_EXISTS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FOREIGN_LOCK -
Data type:Optional: No
Call by Reference: Yes
INVALID_PARAM - Invalid parameter
Data type:Optional: No
Call by Reference: Yes
API_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SYSTEM_ERROR -
Data type:Optional: No
Call by Reference: Yes
NO_PARENTS_FOUND -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for COM_PME_CLASS_CREATE 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_class_descr | TYPE STANDARD TABLE OF COMT_PME_CLASS_DESCR_TABLE, " | |||
| lv_pme_crm_map_key | TYPE COMT_PME_CRM_MAP_KEY, " | |||
| lv_no_active_session | TYPE COMT_PME_CRM_MAP_KEY, " | |||
| lv_crm_hierarchy_guid | TYPE COMT_PME_CRM_GUID, " | |||
| lv_configurable | TYPE C, " | |||
| lt_cstics | TYPE STANDARD TABLE OF COMT_PME_CSTIC_TABLE, " | |||
| lv_locking_user | TYPE SY-UNAME, " | |||
| lv_crm_object_guid | TYPE COMT_PME_CRM_GUID, " | |||
| lv_class_already_exists | TYPE COMT_PME_CRM_GUID, " | |||
| lv_es_log_msg | TYPE BAL_S_MSG, " | |||
| lv_foreign_lock | TYPE BAL_S_MSG, " | |||
| lv_crm_object_name | TYPE COMT_PRODUCT_ID, " | |||
| lv_invalid_param | TYPE COMT_PRODUCT_ID, " | |||
| lv_crm_object_type | TYPE COMT_PME_CLASS_TYPE, " | |||
| lv_api_error | TYPE COMT_PME_CLASS_TYPE, " | |||
| lv_parent_guid | TYPE COMT_PME_CRM_GUID, " | |||
| lv_parent_type | TYPE COMT_PME_CLASS_TYPE, " CO_CATEGORY_TYPE | |||
| lv_system_error | TYPE COMT_PME_CLASS_TYPE, " | |||
| lv_pr_org_type | TYPE COMT_PR_ORG_TYPE, " | |||
| lv_no_parents_found | TYPE COMT_PR_ORG_TYPE, " | |||
| lv_pr_org_id | TYPE COMT_PR_ORG_ID, " | |||
| lv_log_sys | TYPE LOGSYS. " |
|   CALL FUNCTION 'COM_PME_CLASS_CREATE' " |
| EXPORTING | ||
| CRM_HIERARCHY_GUID | = lv_crm_hierarchy_guid | |
| CONFIGURABLE | = lv_configurable | |
| CRM_OBJECT_GUID | = lv_crm_object_guid | |
| CRM_OBJECT_NAME | = lv_crm_object_name | |
| CRM_OBJECT_TYPE | = lv_crm_object_type | |
| PARENT_GUID | = lv_parent_guid | |
| PARENT_TYPE | = lv_parent_type | |
| PR_ORG_TYPE | = lv_pr_org_type | |
| PR_ORG_ID | = lv_pr_org_id | |
| LOG_SYS | = lv_log_sys | |
| IMPORTING | ||
| PME_CRM_MAP_KEY | = lv_pme_crm_map_key | |
| LOCKING_USER | = lv_locking_user | |
| ES_LOG_MSG | = lv_es_log_msg | |
| TABLES | ||
| CLASS_DESCR | = lt_class_descr | |
| CSTICS | = lt_cstics | |
| EXCEPTIONS | ||
| NO_ACTIVE_SESSION = 1 | ||
| CLASS_ALREADY_EXISTS = 2 | ||
| FOREIGN_LOCK = 3 | ||
| INVALID_PARAM = 4 | ||
| API_ERROR = 5 | ||
| SYSTEM_ERROR = 6 | ||
| NO_PARENTS_FOUND = 7 | ||
| . " COM_PME_CLASS_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM COM_PME_CLASS_CREATE
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.| "SELECT single UNAME FROM SY INTO @DATA(ld_locking_user). | ||||
| DATA(ld_parent_type) | = CO_CATEGORY_TYPE. | |||
Search for further information about these or an SAP related objects