7.1 Message Flow
You extract master data from SAP ERP remote systems using the generic master data extractor MDM_CLNT_EXTR (see MDM CLNT_EXTR Documentation for details). The import requires a correct setup of the SAP remote systems and PI. Refer to the IT Scenario Configuration Guide available on SAP Service Market Place and chapter MDM Vendor PI Content of this note for details.
The (recommended) message flow between SAP ERP remote systems and MDM is realized with the CREMDM IDoc type. MDM_CLNT_EXTR is able to collect ERP vendor records into this IDoc. The IDoc is transferred via the IDoc Adapter from ERP to PI. PI is responsible for the transformation of the IDoc into a XML format (see Interface (XSLT) Mapping) and the correct routing to MDM. The transfer from PI to MDM is either done via FTP or the MDM PI Adapter.
7.2 Interface (XSLT) Mappings
The Vendor repository is able to import XMLs having the same structure as the CREMDM IDoc. The Interface (XSLT) Mappings provided by the Vendor PI content do not perform any changes regarding the message structure.
Nevertheless the mapping is mandatory as some segment specific values mappings are happening on PI.
International Address Versions of the segments <E1BPAD1VL> (address data) and <E1BPAD_REM>
(address notes) are filtered on PI.
The value for the Payment Methods in segment <E1LFB1M/ZWELS> needs to be re-formatted so that Import Manager respectively MDIS is able to import the data into the multi-valued hierarchy lookup table. The data in the IDoc is a single string consisting of the remote keys of the payment methods.
The required format is a coma-separated string including the related company code for each payment method.
Example
A record for Company Code 0001 in ERP has four payment methods 1, 7, A, and C. The
<BUKRS> element in the company code data segment <E1KNB1M> carries the value 0001. The payment method element <ZWELS> in the same segment carries the value 17AC. The XSLT mapping on PI transforms the <ZWELS> value into the required format 00011, 00017, 0001A, 0001C. Import Manager respectively MDIS are now able to map the single field to the corresponding entries of the hierarchy lookup table.
7.3 Field Mappings
Field mappings are generally listed in the attached Excel file Field Mapping and Check Tables Vendor.xls. In a few cases the Vendor Import Map uses partitions and/or cloned fields to concatenate and/or duplicate some values:
Dest. Table / Tuple Destination Field Source Field(s)
Vendors Remote Key Clone: <E1LFA1M> LIFNR
Region Partition: <E1BPAD1VL> COUNTRY <Clone> + REGION
Dest. Table / Tuple Destination Field Source Field(s)
Region for PO Box Partition: <E1BPAD1VL> POBOX_CTRY + PO_BOX_REG
Regional Structure Additional City
Partition: <E1BPAD1VL> COUNTRY <Clone> (4) +
<E1BPAD1VL1> HOMECITYNO
Regional Structure City Partition: <E1BPAD1VL> COUNTRY <Clone> (3) + CITY_NO
Regional Structure District
Partition: <E1BPAD1VL> COUNTRY <Clone> (5) + CITY_NO + DISTRICT_NO
Regional Structure PPO Box City
Partition: <E1BPAD1VL> POBOX_CTRY <Clone>
(2) + PBOXCIT_NO Regional Structure
Street
Partition: <E1BPAD1VL> COUNTRY <Clone> (6) + STREET_NO
Transportation Zone Partition: <E1BPAD1VL> COUNTRY <Clone> (2) + TRANSPZONE
Bank Details Bank Partition: <E1LFBKM> BANKS + BANKL
Company Code Data Accounting Clerk Partition: <E1LFB1M> BUKRS <Clone> (2) + BUSAB House Bank Partition: <E1LFB1M> BUKRS <Clone> (4) + HBKID Recipient Type Partition: <E1LFB1M> BUKRS <Clone> (6) +
<E1LFB1M> QSREC
Reconciliation Account Partition: <E1LFB1M> BUKRS <Clone> + AKONT Tolerance Group
(Business Partner)
Partition: <E1LFB1M> BUKRS <Clone> (3) + TOGRU
Tolerance Group (Invoice)
Partition: <E1LFB1M> BUKRS <Clone> (3) + TOGRR
Withholding Tax Code Partition: <E1LFB1M> BUKRS <Clone> (7) +
<E1LFB1M> QSSKZ
Withholding Tax Country Partition: <E1LFB1M> BUKRS <Clone> (8) +
<E1LFB1M> QLAND
Dunning Data Dunning Area Partition: <E1LFB5M> BUKRS <Clone> +
<E1LFB5M> MABER
Dunning Clerk Partition: <E1LFB5M> BUKRS <Clone> (2) +
<E1LFB5M> BUSAB Purchasing
Organization Data
Mode of Transport for Foreign Trade
Partition: <E1LFA1M> LAND1 <Clone> (4) +
<E1LFM1M> EXPVZ Office of Exit or Entry for
Foreign Trade
Partition: <E1LFA1M> LAND1 <Clone> (5) +
<E1LFM1M> ZOLLA
Planning Calendar Partition: <E1LFA1M> WERKS <Clone> +
<E1LFM1M> MRPPP
Planning Cycle Partition: <E1LFA1M> WERKS <Clone> (2) +
<E1LFM1M> LFHRY
Dest. Table / Tuple Destination Field Source Field(s)
Rounding Profile Partition: <E1LFA1M> WERKS <Clone> (3) +
<E1LFM1M> RDPRF
7.4 Value Mappings
The Import Maps for Vendor records do not contain any value mapping. The reason is that
customizing values can differ for each remote system. It hardly possible to predict all values that might occur in your systems. It is your task to enrich the Import Maps with the correct value mappings.
You can use MDM Import Manager to have a full control about the value mapping. Depending on the Import Map configuration, Import Manager tries to map the values automatically.
Note
In general field values will only be mapped automatically if:
a) there is value mapping information stored in the import map
b) the source value is NULL and the Import Map configuration option Automatically map NULL values is set to yes
c) the destination field has the type lookup table with key mapping and the source values are the keys
If MDM Import Manager is not able to map all values automatically, you have to map the missing values manually.
Tip
If you know all of your customizing values that occur in your records, you could think about creating a dummy XML file containing all possible values. Then use this dummy file once to update the Import Map with all value mappings. As soon as you have saved the map with all value mappings, you could automate the import.
MDIS is able to handle unmapped values, too. This depends on the configuration options of the Import Map. The screenshot below shows the default settings used by the predefined Import Map.
Figure: MDIS Value Mapping
7.5 Import of Lookup Main Relationships
General information about the import of lookup main relationships is available in the MDM Import Manager Reference Guide. The following chapters below list some special cases within the Vendor repository.
7.5.1 Bank Details
The Bank Details tuple is part of the Vendors main table. The tuple includes a lookup to the secondary Banks main table. To enable a successful link between a Bank Details tuple record to its related
Banks master record, only the remote keys of the Banks main table are mapped within the Vendor import map. This remote key is a concatenation of the source field BANKS (Bank Country) and BANKL (Bank Key) that is mapped to the destination field Bank of the Bank Details tuple. All further mapped fields (like BANKN (Bank Account Number), BKREF (Reference Details), and so on) specify the Bank Details tuple record only. They do not change the related Banks master record itself.
Recommendation
To ensure that the import of Bank Details works smoothly, ensure that all required Banks master records already exist in your repository.
7.5.2 Main Table Vendors
Fields Alternative Payee, Fiscal Address and Tax Office of the Vendors main table are all lookup main fields that relate to a different record of the Vendors main table.
Fields Alternative Payee and Head Office of the Company Code Data tuple are all lookup main fields that relate to a different record of the Vendors main table.
Field Dunning Recipient of the Dunning Data tuple is a lookup main field that relates to a record of the Vendors main table.
CAUTION
Remember that a lookup to a main table record can only be imported if the lookup record already exists in the repository. It is not possible to import a new main table record and use the very same record as a lookup main record for a different record in a single message. MDM Import Manager respectively MDIS are not able to identify the new record as a valid lookup main record in this case. If you are facing a similar situation for your master data records, you have to execute the import of the message twice. The first import creates all main table records without the lookup main relationships. The second import updated the now existing records with the missing lookup main relationship information.
7.6 Import of Tuples
Tuples can be understood as sub-records of your main record. The import of tuples requires a specific logic to decide if a tuple record should be added, updated, and so on. This setting can be specified either generally for all tuples using the Import Map Configuration Options, or specifically for each tuple being part of your repository.
The default setting as defined in the delivered Import Map is shown in the screenshot below.
Figure: Default Tuple Import Configuration
Depending on the data you’re going to import, you have to decide if the default settings are useable for you, or if you have to redefine some or all properties. Matching tuple fields defines those fields that MDM Import Manager respectively MDIS use to identify if the source values should be used to create a new tuple record or update an existing one.
Recommendation
As mentioned above, you can define the tuple import for each tuple of the repository independently. Therefore switch to the Map Fields/Values tab in MDM Import Manager.
Locate a tuple in the Destination Fields pane. Right-click on it and choose Set Tuple Update… from the context menu.
Figure: Specific Tuple Import Configuration (I)
MDM Import Manager shows a pop-up window where you can define the matching fields and import actions specifically for this tuple.
Figure: Specific Tuple Import Configuration (II) Note
Additionally the handling of NULL values differs for tuples. The property Set NULL Interpretation (see the screenshot on the previous page) is set to ignore for all tuples and their member fields.
7.7 MDIS usage
Currently the inbound ports for importing MDM Vendor XML messages are defined as manual ports.
This configuration setting has been made for some reasons. All predefined maps do not yet contain any specific value mapping and only a common definition for the tuple import. Both rely strongly on the data you’re going to import. Therefore SAP cannot predefine these settings.
Recommendation
Use MDM Import Manger at least once for having a full control of the value and tuple mapping. As soon as you have saved the Import Map including your specific value and tuple mapping, you can switch to automatic import via MDIS by changing the
corresponding port configuration in MDM Console.