COM_PROD_CATEGORY_MAINTAIN_API SAP Function module

COM_PROD_CATEGORY_MAINTAIN_API is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name COM_PROD_CATEGORY_MAINTAIN_API into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: COM_PRCAT_API
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM COM_PROD_CATEGORY_MAINTAIN_API - COM PROD CATEGORY MAINTAIN API

CALL FUNCTION 'COM_PROD_CATEGORY_MAINTAIN_API' "
  EXPORTING
    is_prod_category =          " comt_pr_category_maintain_gen
*   iv_maintain_comm_category = 'X'  " comt_boolean
    iv_hierarchy_exist_in_pme =   " comt_boolean
*   iv_application_log =        " balloghndl
  IMPORTING
    ev_category_guid =          " comt_category_guid
  EXCEPTIONS
    WRONG_CALL = 1              "
    ERROR = 2                   "
    .  "  COM_PROD_CATEGORY_MAINTAIN_API

ABAP code example for Function Module COM_PROD_CATEGORY_MAINTAIN_API

The ABAP code below is a full code listing to execute function module COM_PROD_CATEGORY_MAINTAIN_API including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_ev_category_guid  
 
 TYPE COMT_CATEGORY_GUID
.


DATA(ld_is_prod_category) = 'Check type of data required'.

DATA(ld_iv_maintain_comm_category) = 'Check type of data required'.

DATA(ld_iv_hierarchy_exist_in_pme) = 'Check type of data required'.

DATA(ld_iv_application_log) = 'Check type of data required'.
.

CALL FUNCTION 'COM_PROD_CATEGORY_MAINTAIN_API'
  EXPORTING
    is_prod_category =           ld_is_prod_category
*   iv_maintain_comm_category =    ld_iv_maintain_comm_category
    iv_hierarchy_exist_in_pme =    ld_iv_hierarchy_exist_in_pme
*   iv_application_log =         ld_iv_application_log
  IMPORTING
    ev_category_guid =           ld_ev_category_guid
  EXCEPTIONS
    WRONG_CALL =                 1
    ERROR =                      2
    .  "  COM_PROD_CATEGORY_MAINTAIN_API

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_ev_category_guid
 
 TYPE COMT_CATEGORY_GUID ,
ld_is_prod_category
 
 TYPE COMT_PR_CATEGORY_MAINTAIN_GEN ,
ld_iv_maintain_comm_category
 
 TYPE COMT_BOOLEAN ,
ld_iv_hierarchy_exist_in_pme
 
 TYPE COMT_BOOLEAN ,
ld_iv_application_log
 
 TYPE BALLOGHNDL .


ld_is_prod_category = 'Check type of data required'.
ld_iv_maintain_comm_category = 'Check type of data required'.
ld_iv_hierarchy_exist_in_pme = 'Check type of data required'.
ld_iv_application_log = 'Check type of data required'.