SAP MDM_CUST_USER_INTERFACE_KNEX Function Module for NOTRANSL: Aufruf der Benutzerschnittstellen für KNEX ALE-Ausgang Kundensta









MDM_CUST_USER_INTERFACE_KNEX is a standard mdm cust user interface knex SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Aufruf der Benutzerschnittstellen für KNEX ALE-Ausgang Kundensta 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 mdm cust user interface knex FM, simply by entering the name MDM_CUST_USER_INTERFACE_KNEX into the relevant SAP transaction such as SE37 or SE38.

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



Function MDM_CUST_USER_INTERFACE_KNEX 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 'MDM_CUST_USER_INTERFACE_KNEX'"NOTRANSL: Aufruf der Benutzerschnittstellen für KNEX ALE-Ausgang Kundensta
  EXPORTING
   IP_MESSAGE_TYPE =  "Message Type
   IP_SEGMENT_NAME =  "DE-EN-LANG-SWITCH-NO-TRANSLATION
   IS_KNEX =  "DE-EN-LANG-SWITCH-NO-TRANSLATION

CHANGING
   CP_CIMTYPE =  "Extension Type

TABLES
   ET_IDOC_DATA =  "DE-EN-LANG-SWITCH-NO-TRANSLATION
.



IMPORTING Parameters details for MDM_CUST_USER_INTERFACE_KNEX

IP_MESSAGE_TYPE - Message Type

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

IP_SEGMENT_NAME - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

IS_KNEX - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

CHANGING Parameters details for MDM_CUST_USER_INTERFACE_KNEX

CP_CIMTYPE - Extension Type

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

TABLES Parameters details for MDM_CUST_USER_INTERFACE_KNEX

ET_IDOC_DATA - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

Copy and paste ABAP code example for MDM_CUST_USER_INTERFACE_KNEX 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_cp_cimtype  TYPE EDIDC-CIMTYP, "   
lt_et_idoc_data  TYPE STANDARD TABLE OF EDIDD, "   
lv_ip_message_type  TYPE TBDME-MESTYP, "   
lv_ip_segment_name  TYPE EDIDD-SEGNAM, "   
lv_is_knex  TYPE KNEX. "   

  CALL FUNCTION 'MDM_CUST_USER_INTERFACE_KNEX'  "NOTRANSL: Aufruf der Benutzerschnittstellen für KNEX ALE-Ausgang Kundensta
    EXPORTING
         IP_MESSAGE_TYPE = lv_ip_message_type
         IP_SEGMENT_NAME = lv_ip_segment_name
         IS_KNEX = lv_is_knex
    CHANGING
         CP_CIMTYPE = lv_cp_cimtype
    TABLES
         ET_IDOC_DATA = lt_et_idoc_data
. " MDM_CUST_USER_INTERFACE_KNEX




ABAP code using 7.40 inline data declarations to call FM MDM_CUST_USER_INTERFACE_KNEX

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 CIMTYP FROM EDIDC INTO @DATA(ld_cp_cimtype).
 
 
"SELECT single MESTYP FROM TBDME INTO @DATA(ld_ip_message_type).
 
"SELECT single SEGNAM FROM EDIDD INTO @DATA(ld_ip_segment_name).
 
 


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!