SAP MDM_BAS_TYP_1_ADRESSE_KUNDE Function Module for NOTRANSL: Aufbau der IDoc-Segmente zu einer Typ-1-Adresse der BAS eines Ku
MDM_BAS_TYP_1_ADRESSE_KUNDE is a standard mdm bas typ 1 adresse kunde 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: Aufbau der IDoc-Segmente zu einer Typ-1-Adresse der BAS eines Ku 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 bas typ 1 adresse kunde FM, simply by entering the name MDM_BAS_TYP_1_ADRESSE_KUNDE 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_BAS_TYP_1_ADRESSE_KUNDE 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_BAS_TYP_1_ADRESSE_KUNDE'"NOTRANSL: Aufbau der IDoc-Segmente zu einer Typ-1-Adresse der BAS eines Ku.
EXPORTING
IP_ADDRNUMBER = "Address number
IP_KUNNR = "Customer Number
TABLES
ET_IDOC_DATA = "DE-EN-LANG-SWITCH-NO-TRANSLATION
IMPORTING Parameters details for MDM_BAS_TYP_1_ADRESSE_KUNDE
IP_ADDRNUMBER - Address number
Data type: ADRC-ADDRNUMBEROptional: No
Call by Reference: No ( called with pass by value option)
IP_KUNNR - Customer Number
Data type: KNA1-KUNNROptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for MDM_BAS_TYP_1_ADRESSE_KUNDE
ET_IDOC_DATA - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: EDIDDOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MDM_BAS_TYP_1_ADRESSE_KUNDE 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_et_idoc_data | TYPE STANDARD TABLE OF EDIDD, " | |||
| lv_ip_addrnumber | TYPE ADRC-ADDRNUMBER, " | |||
| lv_ip_kunnr | TYPE KNA1-KUNNR. " |
|   CALL FUNCTION 'MDM_BAS_TYP_1_ADRESSE_KUNDE' "NOTRANSL: Aufbau der IDoc-Segmente zu einer Typ-1-Adresse der BAS eines Ku |
| EXPORTING | ||
| IP_ADDRNUMBER | = lv_ip_addrnumber | |
| IP_KUNNR | = lv_ip_kunnr | |
| TABLES | ||
| ET_IDOC_DATA | = lt_et_idoc_data | |
| . " MDM_BAS_TYP_1_ADRESSE_KUNDE | ||
ABAP code using 7.40 inline data declarations to call FM MDM_BAS_TYP_1_ADRESSE_KUNDE
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 ADDRNUMBER FROM ADRC INTO @DATA(ld_ip_addrnumber). | ||||
| "SELECT single KUNNR FROM KNA1 INTO @DATA(ld_ip_kunnr). | ||||
Search for further information about these or an SAP related objects