Skip to Content
Author's profile photo Former Member

MDM_CLNT_EXTR :ECC Configurations

Author: Ankush Bhardwaj

Company: Infosys Technologies Limited

Date written: 18/07/2012

Author Bio: Ankush Bhardwaj is currently working as an MDM Consultant in Infosys Technologies Limited

Target readers: Sap MDM consultant, SAP PI Consultants, SAP ECC Consultants and Data Migration Teams

Keywords: SAP MDM, SAP, Master Data Extraction, MDM_CLNT_EXTR


This document caters to the Business Scenario where Master Date is residing in ECC system and is required to be distributed to various target systems like SAP MDM or SAP or Non-SAP systems. It uses SAP PI system as intermediate systems that will accept the data from Sender system and convert the data in required format for destination system and then sends data to target system. This Document talks about the Landscape Description of the Master Data Extraction of Material Master Data from the SAP ERP System to Target systems. This document will provide all the minute configuration details of the SAP ECC system. This document will only deal with the Extraction procedure of Material Master Data from Backend SAP ECC System.

Table Of Contents:


  1. Creating a New Logical System for Receiver PI System (Some old system can also be used if we have created one earlier)
  2. Creating the Logical System for Sender R3 System & Assigning the Client
  3. Configuration of RFC Destination Pointing to PI System
  4. Configuration of Communication Port (Transactional Port to be mapped with RFC Destination)
  5. Configuration of Partner Profile (For Outbound messages)
  6. Creation of ALE distribution Model/Customer Distribution Model



ALE – The technology for setting up and operating distributed applications.

Application Link Enabling (ALE) facilitates the distributed, but integrated, installation of SAP systems. This involves business-driven message exchange using consistent data across loosely linked SAP applications. Applications are integrated using synchronous and asynchronous communication – not by using a central database.

ALE consists of the following layers:

Application services

Distribution services

Communication services

Delta Mode – The Delta Mode is a specific distribution mode for an extraction run. A delta extraction run uses the system’s change pointers to extract and distribute only those master data objects that have been changed since the last extraction run. In delta mode, the extraction framework performs some mandatory checks. As the delta modes reuses the selection and transfer criteria of an initial extraction run for a master data object, it is mandatory that this object has at least been initially extracted once. Otherwise the object will be excluded from the delta extraction run. In addition, you cannot define selection and transfer criteria in the delta mode.

Extraction Object – An Extraction Object is a valid implementation of an object specific extractor. It consists of the extraction logic how to read the master data from the system storage according to the defined selection criteria and the system/object specific implementation of the communication technology used for sending the master data to the receiver system. As a common rule, the SAP delivered object extractors for R/3 & ERP systems use ALE IDoc technology, whereas object extractors for CRM and SRM systems use the ABAP Proxy XML Message technology.

Distribution Mode – The distribution mode defines how the data is extracted from the SAP system and sent to the target receiving system. The extraction framework is able to support multiple, different distribution modes as the mode to be used is part of the extraction variant object configuration. The actual implementation of a distribution mode has to be done specifically by the extraction object – this implementation is not part of the generic extraction framework. The framework supports implementing an Initial and a Delta Mode only, including the generic handling of selection and transfer criteria for these modes.

Extraction Run – An Extraction Run is the execution of a maintained Extraction Variant. It retrieves the selected master data objects from the system and sends it to the chosen target system. An Extraction Run can either be executed in Initial or Delta Mode.

Extraction Variant – An Extraction Variant is the prerequisite to start an Extraction Run. The Extraction Variant consists of a name and description, the extraction object, the selection and transfer criteria, the extraction mode, the target receiving system and the resulting message size. It is the configuration of the master data extraction. Extraction Variants can be stored in the system.

Initial Mode – The Initial Mode is a specific distribution mode for an extraction run. Initial Mode executes the first, complete extraction and distribution of the chosen master data object. The objects are extracted from the system’s storage according to the given selection criteria, independent from change pointers. The scope of the distributed object is sized according to the given transfer criteria. An extraction run in initial mode is a prerequisite for extraction runs in delta mode.

Steps of ALE Configurations:

1. Creating a New Logical System for Receiver PI System

For the ALE Configuration the first step is the creation of a Logical System for Receiver PI system.

Configuration Steps:

  • Go to Transaction SALE/BD54: Create New Logical System for receiver PI system.


Figure 1: Initial Screen for t-code “SALE”


  • Click New Entries on below screen to create new logical system.
  • Press SAVE button to save new creation.


Figure 2: Screen to create new Logical Systems

  • New Logical System created.


2. Creating the Logical System for Sender R3 System & Assigning the Client

Configuration Steps:

Go to Transaction SCC4: Linking Sender System to Client

  1. BASIS team generally has access to SCC4 as it is administration related tCode.
  2. Logical System name for the given R/3 or ECC system needs to be checked and link to required Client if necessary.
  3. This Logical System name should be used as Sender ECC LS.

3.Configuration of RFC Destination Pointing to PI System

A RFC Destination is to be created with the exact same name as the LS name for the Receiver PI System. This RFC Destination will point to the receiver PI System which would be used in the integration Landscape.

Configuration Steps:

  • T-Code is SM59/SALE.


Figure 3: Initial Screen of SM59 for RFC Configurations

  • Click on ABAP Connections and press Create icon. Below screen pops up:


Figure 4: Initial Screen to create RFC Destination

  • Enter values as shown below:


Figure 5: Technical Settings for RFC Destination

  1. Target Host could be entered as IP Address. Once you save it, it will appear as name automatically.
  2. RFCDES is the table that was referred for entering IP address and System.


Figure 6: Logon & Security Settings for RFC Destination

  1. This user should be some existing user of this Destination System and not the current system that is being used now. For other tabs, default settings will be used.
  2. Save RFC Destination.

4. Configuration of Communication Port (Transactional Port to be mapped with RFC Destination)

A Transactional RFC Communication Port is to be created which is used for R/3 systems. Then the port needs to be mapped with the RFC Destination.

Configuration Steps:

  • T-Code is WE21:

Figure 7: Initial Screen for creating Port

  • Click on Transactional RFC and press Create icon. Give name of Port and press ‘Enter’.

  • Fill in required fields and save the Port.

Figure 8: Technical Settings for Port

5. Configuration of Partner Profile (For Outbound messages)

Partner Profile needs to be configured for Outbound Message types for Material Master that is MATMAS05 and MDMRECEIPT.

Configuration Steps:

  • T-Code is WE20: Select Partner Type LS and press Create icon.

Figure 9: Initial Screen for Creating Partner Profiles

  • Enter Details as below:

Figure 10: Outbound Parameters and other settings

  • For maintaining Outbound Parameters, press highlighted icon and below screen will appear:
  • Enter data as shown in the screenshot:

Figure 11: Screen for Outbound Parameter settings of Partner Profile

  • Similarly add MDMRECEIPT Message Type as well in the Partner Profile Outbound Parameters.
  • MDMRECEIPT is an old message type that was used in MDM 2.0 and MDM 3.0. As T-Code MDM_CLNT_EXTR still has to support the old MDM releases, so we have to configure this IDoc type in ALE, although it is not used in standard MDM 5.5 and 7.1 scenarios. In case we do not configure MDMRECEIPT, then extraction can fail with below error message:

        “BI 003 – Could not determine recipients for message type MDMRECEIPT”.

6. Creation of ALE distribution Model/Customer Distribution Model

This step needs to be performed for creating communication channel from Sender system to receiver system.

A customer distribution model needs to be created with a Model Name & then the MATMAS & MDMRECEIPT Message Type should be added there under the Sender PI System & Receiver R3 System.

Configuration Steps:

  • T-Code is BD64: Go to Change Mode and Click “Create Model View”

Figure 12: Initial Screen for Creating Distribution Model view

Figure 13: Pop-up screen for Creating Distribution Model

  • Select Model View and Click “Add Message Type”

Figure 14: Pop-up screen for Assigning Message Types to Model view

  • Similarly add MDMRECEIPT Message Type as well.
  • After all these steps, it will appear like this in Model View:

Figure 15: Complete Distribution Model

  • Generate Partner Profile for this Distribution Model:

Figure 16: Path for Generating Partner Profile for Distribution Model

  • Below Screen appears then click Execute:

Figure 17: Selection screen for generation of Partner Profile

  • Log will be displayed as shown below:

  • Save Model View and Then Distribute the Model to Target System:

Figure 18: Path for distributing model to target system

  • Select Destination System
  • Log is displayed as follows:

7. Create Variant for Initial Extraction(Selection Criteria and Transfer segments are defined)

The Master Extractor needs to be configured by setting the variants & using the LS name of the ALE settings done above.

The Variant Name is according to Material Master Data & a short description is also given. The Extraction Object is given according to the Message type of the Master which is to be exported. In the Target system the Logical System Name of the Receiver PI system is given. The Mode is kept Initial if it is a first time Extraction. The Block size is selected on the basis of how many records are to be bundled together in one IDOC.

Customizing Steps:

  1. T-Code is MDM_CLNT_EXTR:

  1. Enter name of Variant, Description.
  2. Material_Extract is the Extraction Object for extracting data for Materials.
  3. Target System would be Receiver PI System.
  4. Distribution Mode decides if you want to extract Initial Load Data or Delta Extraction.
  5. Block size decides the number of records to be combined in single MATMAS Idoc.
  6. After entering these values, Press Enter.

Figure 20: Initial Screen for MDM_CLNT_EXTR

  1. Field Groups will appear. Here you can decide Selection Criteria as well as Transfer Criteria:

Figure 21: Screen for entering Selection criteria and transfer selection

  • Double Click on this selection segment E1MARAM and below screen will appear:

  • Mention Selection Criteria for Extraction Program.

Note: In case you are entering some value range for Numeric Type, then you need to enter the value including Leading Zeroes for the concerned field. If this is not done, then extraction will start but message will be generated saying “No Data Found”. For Example, we need to maintain Material Number – MATNR as 000000000070000000 (total 18characters) and not only 70000000 (8 characters).

  • By selecting the checkbox under heading “Transfer” will ensure that given segment is included during the extraction and idoc creation.
  • Then SAVE variant and click “Start Extraction”.
  • Background Job would be scheduled to extract data.


  • Click on “Display Jobs” and all related jobs will be displayed at the screen:

Figure 22: Batch Jobs executed for MDM_CLNT_EXTR

  • Select Job and see Job Log and it would appear like this:

Figure 23: Log display for Batch Job

  • We can go to WE02 and see idocs posted after Extraction.

Figure 24: Idoc display for extracted idocs

Software Check:

  • We need to ensure that Extraction Framework and Extraction Object Software Packages are installed in the system. Without which Extraction will not happen.

  • With this, all the configuration settings needed to be done for extraction of Material Master are complete. Further Settings in PI and MDM system needs to be done to automate the process completely.


Assigned Tags

      1 Comment
      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      Excellent .

      If we need to trigger an IDOC based on KNA1-AUFSD changes alone to PI(No initial load via extractor from SAP ECC) , Is it possible to trigger DEBMDM06 using the customer extractor  or we need to go for DEBMAS06 IDOC trigger via ABAP programs ?