MDM_CUST_USER_INTERFACE_KNB1 SAP Function module

MDM_CUST_USER_INTERFACE_KNB1 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 MDM_CUST_USER_INTERFACE_KNB1 into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM MDM_CUST_USER_INTERFACE_KNB1 - MDM CUST USER INTERFACE KNB1

CALL FUNCTION 'MDM_CUST_USER_INTERFACE_KNB1' "
  EXPORTING
    ip_message_type =           " tbdme-mestyp
    ip_segment_name =           " edidd-segnam
    is_knb1 =                   " knb1
  TABLES
    et_idoc_data =              " edidd
  CHANGING
    cp_cimtype =                " edidc-cimtyp
    .  "  MDM_CUST_USER_INTERFACE_KNB1

ABAP code example for Function Module MDM_CUST_USER_INTERFACE_KNB1

The ABAP code below is a full code listing to execute function module MDM_CUST_USER_INTERFACE_KNB1 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:
it_et_idoc_data  
 
 TYPE STANDARD TABLE OF EDIDD,"TABLES PARAM
wa_et_idoc_data
 
 LIKE LINE OF it_et_idoc_data
.

 

SELECT single CIMTYP 
  FROM EDIDC 
  INTO @DATA(ld_cp_cimtype).

 

SELECT single MESTYP 
  FROM TBDME 
  INTO @DATA(ld_ip_message_type).



DATA(ld_ip_segment_name) = some text here

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

"populate fields of struture and append to itab
append wa_et_idoc_data to it_et_idoc_data.
.

CALL FUNCTION 'MDM_CUST_USER_INTERFACE_KNB1'
  EXPORTING
    ip_message_type =            ld_ip_message_type
    ip_segment_name =            ld_ip_segment_name
    is_knb1 =                    ld_is_knb1
  TABLES
    et_idoc_data =               it_et_idoc_data
  CHANGING
    cp_cimtype =                 ld_cp_cimtype
    .  "  MDM_CUST_USER_INTERFACE_KNB1

IF SY-SUBRC EQ 0.
  "All OK
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_cp_cimtype
 
 TYPE EDIDC-CIMTYP ,
ld_ip_message_type
 
 TYPE TBDME-MESTYP ,
it_et_idoc_data
 
 TYPE STANDARD TABLE OF EDIDD ,
wa_et_idoc_data
 
 LIKE LINE OF it_et_idoc_data,
ld_ip_segment_name
 
 TYPE EDIDD-SEGNAM ,
ld_is_knb1
 
 TYPE KNB1 .



SELECT single CIMTYP 
  FROM EDIDC 
  INTO ld_cp_cimtype.


SELECT single MESTYP 
  FROM TBDME 
  INTO ld_ip_message_type.
 

"populate fields of struture and append to itab
append wa_et_idoc_data to it_et_idoc_data.

ld_ip_segment_name = some text here
ld_is_knb1 = 'Check type of data required'.