Concatenation in Import manager(MDM)

Hi ALL ,
I want to concat or merge my 3 fields of my Qualified table during Import manager and then map it to one field in my destination table .Please help me in that .
Ex.Name /Country/City into a destination field Info
Thanks and Regards.
Ankit Jain

Hi ankit,
The requirement that you have to merge three fields together in the Import manager can be done by methods.
1)Compound field creation
2)Partioning
1)Compound field:
A compound field will only be created if you map all the exsisting fields in the source side with the fields in the destination side.
For qualified table mapping this is the requirement that if you want to create a compound field you must make sure that all the fields are mapped in the source side.Then when you right click on the non qualifier it will create a compound field and automatically map it with the required field.
2)Partitioning:
You can also use partitioning to merge three fields together.
just click the desired field in the source hierarchy and click the partioning button in that dialog box select all the fields that you want to club under one field.
Regards
Simona

Similar Messages

Map cannot be loaded in import manager | MDM

Hi ,
I am trying to upload some data in customer repository (I am on MDM 5.5 SP05) . I have a few XML files (IDOCS) from customer master in an ECC system ,which I am providing as a source for the import manager . In the source preview I can see the following tables
- DEBMAS06
- E1KNVIM
- E1KNVPM
Now when I try to open the import map 00_DEBMDM06_R3.map (standard map provided by SAP) it gives me an error message "the map cannot be loaded because table E1KNA1M is not a source" .
What do I need to get this file uploaded to the import manager ?
Regards
Deepak Singh

Hi Maheshwari/Harrison ,
I tried giving the type as XML schema as you guys suggested but now the the import manager won't open at all and I get the following error " The element DEBMAS06 is used but not declared in the DTD/Schema " .
In the console inside the customer repository > Admin > XML schemas i have made sure that the schema name DEBMDM06 points to DEBMDM.DEBMDM06.xsd that is provided in the business content with the customer repository . Infact for all the schemas( lookup tables , bank check tables , customer check tables ) i have made sure they point to the right XSD's provided in the business content for the customer repository .
Now what do you guys think is the problem ?
Regards
Deepak Singh

Import Manager MDM 3.0 Updating old Maps

Dear MDM Catalog gurus,
After having upgraded from MDM 2.0 to MDM 3.0 the maps have to be
updated in Import Manager.
1.
When trying to update MDM import Maps in the new "SAP Import Manager" messages
like
- "There are multiple roots for the XML Schema. Please select the correct one" or
- "There are multiple path for Table "ARTICLE". Please select the correct one"
come up.
What exactly do we have to do? What is the root of an XML-Schema? Can
I find that in Console or by looking into "old" Maps with the old Import Manager?
I saved the old Schema files from Console before upgrading to MDM 3.0.
Now when I open this old XML-Schema file with an editor, where can I
find e.g. the "old" root node.
2.
What happens if I say "No" I don't want to update the old Import Maps
when starting Import Manager.
Then all old Maps are gone and I have to recreate them. But does this
have an effect on the further upgrading process to MDM 3.0? Will the
old repositories work under MDM 3.0 after having sais NO?
Any idea?
Thanks a lot for your help in advance.
Best regards,
Henning

Hi there,
thanks for that hints, but this does not really help.
I already read a lot of sap links, but don't really get a solution where I can find information about where to find the rood node (or what it is) or information to former paths.
Is there perhaps anybody how also made an upgrade from MDM Catalog 2.0 to 3.0 with similar experience?
Thanks in advance,
best regards,
Henning

MDM Import Manager - remove multiple values from a multi valued fiedl

Hi,
We have this multi-valued field and we would like to clean the values from it.
How can we do this using MDM Import Manager?
Example:
Article A
Field XPTO has values Z, T and P.
We want this field XPTO with no values. How can we do a mass actualization to clean the field for some articles?
Thanks and regards,
Maria

*We have this multi-valued field and we would like to clean the values from it.
How can we do this using MDM Import Manager?
Example:
Article A
Field XPTO has values Z, T and P.
We want this field XPTO with no values. How can we do a mass actualization to clean the field for some articles?*
Hi Maria,
There can be multiple ways to achieve this -
1.After doing field mapping for XPTO you can set conversion filter for each of the values.
2.Value map with NULL.
3.Trigger a Workflow on import/record add,run assignment and make that field NULL.
4.Run mass update for conditional assignment based on that value of XPTO.
There can be more ways,whichever suits you best you can go ahead with that.
Hope it helped
Regards,
Ravi

Importing text file (delimited, fixed width) with MDM Import Manager?

Hello all,
According to the overview section of the import manager reference guide, it is possible to import from delimited text files (e.g. CSV).
But when it comes to the details, text files are not mentioned anymore. I also found no option in the Import Manager.
Could you tell me whether this is possible and - if it is - how?
Thanks in advance!
Kind regards,
Dennis

Hi Dennis,
In order to import flat files into MDM do the following. This solution is specific to MS Windows:
I. Set up ODBC for *.txt or *.csv files
1. Open Data Sources (ODBC) interface:
Start> Settings> Control Panel--> Administrative Tools -->Data Sources (ODBC).
2. Select System DSN Tab in Data Sources (ODBC) interface.
3. Click on [Add]. Select the Microsoft Text Driver. Click Finish.
4. Write a Data Source Name
5. Uncheck Use Current Directory to enable the [Select Directory] button.
6. Click on [Select directory] to determine the source directory.
7. Select the source file.
8. Click [OK] and return to the ODBC Text Setup screen.
9. Click [OK].
10. Return to the ODBC Data Source Administrator dialog and click [OK].
II. Importing from Flat file
1. Run MDM Import Manager.
2. Select ODBC from the Type drop-down field of the Connect To Source dialog.
3. Enter the DSN name from the Setup ODBC Connection dialog above.
4. Select the file name with extension (.csv or .txt) in the Tables panel of MDM Import Manager and the file content in the Records panel.
Hope this solved your problem.Please mark helpful answers
Regards,
Santosh.

Retreive Next Source File in MDM Import Manager

Hi all,
I am curious about the above feature in the MDM Import Manager. It can be found under File menu but I found that it is always greyed out even if I have selected multiple files. When I select multiple files, the system is clever enough to take all the records in the file so it doesn't seem to be used to move from one file to another. I couldn't find any information on the Import Manager guide so am trying this forum. Note that I have also searched on the forum before posting.
Appreciate if anyone can share their insight into this feature.
Cheers!
SF

Hi SF,
Yes I too did not come accross any document about this.
However,I guess this is something which helps you in exception handling.
When you handle exception of a port and there are multiple files,then you need "connect to source" again and again.
It takes you to next exception file.
Hope this helps!
Thanks,
Ravi

Error while using Import Manager in MDM 7.1 SP7

Hi,
We are using MDM 7.1 SP7. I am trying to import a Tab delimited flat file through import manager. When I try to connect the source file, I get the following error * Logon Error: Found non-complaint CSV format in input stream [Encoding:UTF16].96*
If I try to import through an excel there is not problem. Can someone help to solve this error while importing in Tab delimited flat file through import manager.
Best Regards
Manoj

Hello Mandip,
I had tried doing it before posting my question. I saved it in UTF8 and then tried importing. Saving in UTF8 format made the import manager accept characters like Ä and the original error was solved, but when then a new error came which called for UTF16 format. When I digged into it I found that it is due to the double quotes(" ") in the flat file. When I removed the quote import manager accepted it.
So the conclusion is there should be a way to save the flat file in UTF16 format or the workaround is importing it in excel but again excel has limitation of importing 100000 records in one file.
Can you suggest how to save the flat file in UTF16.
Best Regards
Manoj

Identifing duplicate master data records using the MDM Import Manager

hi all
I read the Topis "How to identify duplicate master data records using the MDM Import Manager</b>"
i tried to create import maps and to set rules. but when i import them it creates the new vendor records for each rule with rest of the fields blank.
when i import vendor data all the three fields i.e Match rate , match type and match group are blank.
My Question is :
I am getting vendor data from SAP R/3.
In which source (in lookup xml file or data xml file) do i have to include these above three fields and how all the rules will be reflected in repository?

Hi Sheetal
Here we go when do you Import any data (vendor master) please follow the following steps;
1. First of all apply the map to the source data
2. In the Match Record tab there are 3 possiblities
   a.[Remote Key] : Checks the current source rec with
     repository along with all the fields - This is
     default
   b.Remove [Remote key] - by double click the same; and
     choose any single fields like Vendor Number or
     name - Then the current record will be matched
     with the repository based on the field.
   c.Instead of single field you can choose combination
     also.
3. Based on the Match results, match class will be set
   automatically;
   a. None
   b. Single
   c. Multiple
4. Then Match Type
    a.Exact-All the individual value matches are Equal.
    b.Partial-At least one value match is Equal and at least one Undefined; no value matches are Not Equal.
    c.Conflict-At least one value match is Equal and at least one value match is Not Equal.
5. then chek the Import status and Execute the import.
Hope this helps you.
cheers
Alexander
Note: Pls dont forget reward points.

SAP MDM Import Manager connect to Oracle Database.

Hi expert,
I try to connect to Oracle DB with SAP MDM Import Manager but I cant.
I entered property in "Connect to Sorce" window.
============================================
Type : Oracle
Remote system : MDM
DBMS server : <DBMS host>:<listener port>
Database : Oracle_SID
User : Oracle database user
Password : Oracle database user password
============================================
then error ocurred.
"Unable to connect to source"
I aleady checked to connect to the Oracle database with Oracle client.
It is connected well.
How can I connect ??
thanks and regards
jun

Hi all,
thank you for your replies.
I tried to connect oracle DB except "< and >" symbol but It did not work.
I installed windowXP 32bit , Oracle client 32bit and SAP MDM Import manager 32bit in My local PC.
Also I connect to MDM DB using sqlplus in My local PC.
I wonder that TNSNAME.ORA is used DB connection using SAP MDM Import manager ??
I think TNSNAME.ORA is not used when I connect to DB using SAP MDM Import manager because I enter parameters are properties of TNSNAME.ORA.
I don`t know why don`t connect to DB.
regards,
jun

MDM Import Manager Ports Disabled

Hi,
I created remote system in Console and tried to import XML file using Import Manager using port option. The port I created in console is appearing in the drop down butis greyed out
Can anyone help please.
I have the XML File in the Ready Folder
Thanks.

Hi Harsha,
Are you using an XML schema to import the XMl file into MDM?
With higher versions of MDM, you need to import the XML file using a related XML schema which you have to upload in Console and also choose in the Port setting.
This completes the linking of the XML schema with the port and when you place an XML in the port, it automatically chooses the XML schema mentioned and imports the file.
You need to choose the XML schema in the Format property of the Port. And then mention the XML schema in the XML schema property of the Port. You will find all these properties under the Port table under the Admin Node in the Console.
I guess, you are not using the XML schema and hence the port might be disabled. Please check it out. Also after doing this, doing this, place the file in the inbound port ready folder.
Hope this info help.
Thanks and Regards
Nitin jain

MDM Import manager data sources

Hi experts,
As far as I know MDM has ETL capabilities with MDM Import/syndicator tools that allows to load and extract data to and from MDM using files and relational databases as source/target.
What different kind of data sources supports MDM Import manager?
When should we work with SAP XI/PI?
When sould we work with ETL (Data Services as Data Integrator)?
Thanks in advance,
Abby
Edited by: Abigail Beurmann on Nov 23, 2011 11:38 AM

Hi Abigail,
So, Could you please tell me if it's a common practice to import data in MDM using files?
for example as you said, We want to import data from R/3 to MDM using XML files that XI/PI generates?
Yes its a common practice to import data in MDM in files.Most common mode of data exchange is xml which has many advantages namely it is accepted open standard,allows to clearly separate content from form (appearance), is text-oriented,is Secure, is extensible,is self-describing, is universal; meaning internationalization is no problem and XML is a future-oriented technology.
In our business scenario, We have a SAP CRM with SQL server 2005 as a source. Could MDM automatically import data directly from SQL Server or it's a better practice to generate XML files with PI using the Import Port/folder?
One should always use a interface as business rules can possibly change and making a later change could be huge ask.
So PI can act a interface between MDM and CRM.
CRM supports Bdoc and PI can integrate with CRM with help of ABAP Proxies.
The following thread provides you in depth information on integration of the 2 systems:
CRM-MDM Integration via XI
To help you understand more about webservice and PI integration with MDM for CRM integration please go though this thread:
SAP PI and Webservices
To know more about PI vs DS please go though this guide:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10fbac70-c381-2d10-afbe-c3902a694eaf?QuickLink=index&overridelayout=true
About Integration with PI:
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/8035bf61-d6b5-2e10-5fa6-e5e00b9e6174&overridelayout=true
A guide which takes you through the entire process of CRM PI MDM integration,although for SAP MDM 5.5 version but valid for most part:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/405a73cc-9068-2c10-859e-c13f81922e7c?QuickLink=index&overridelayout=true
Hope this helps.
Thanks,
Ravi

MDM Import Manager Batch

Hi everyone,
We are using the MDM Import Manager Batch to import data automatically. Can we write in our ImportBatch.ini the file name with * at the end : CREMDM.CREMDM04*.xml
because the file name comes with time stamp (CREMDM.CREMDM0420061129-103959-602.xml)
[Source]
Type=XML Schema
XML Schema=CREMDM04
File name= \...\... CREMDM.CREMDM04*.xml
DSN=
DBMS Server=
Database=
User=admin
In advance thanks,
Aklilu

Hi Aklilu,
the names of the XML files don't matter. MDIS tries to process everthing that is put into the ready folder. The ready folder is processed in a "first comes, first served" way. So there's no need to change the names. Is the time stamp in the file name really a problem? If yes, why?
> We are trying to parameter the mdis.ini and until now it does not work.
Could you specify this? In addition, I've got a few hints:
MDIS has to have the same build version as the MDM Server. In addition, MDIS has to be running (in Windows, you can check this in the Services Screen). Furthermore you should have a look at the Console's port definition (select your repository, go to Admin -> Ports in the menu tree). The port has to be configured correctly (XML Scheme, which map to be used, and so on). Very important: you have to set the port to automatic processing.
Here's a sample for the MDIS.ini:
[GLOBAL]
Version=5540
Server=WDFD00146633A
Interval=30
Automap Unmapped Value=True
Unmapped Value Handling=Add
Always Use Unmapped Value Handling=False
VXR_MAX=25000
Verbose=0xFFFF
-- Verbose OFF:     0x0000
-- Verbose ON:      0xFFFF
-- FI Verbose:     0x0001
-- XML Verbose:     0x0002
-- MAP Verbose:     0x0004
-- THRD Verbose:    0x0008
-- PARSER Verbose: 0x0010
-- STRUCTX Verbose: 0x0020
-- VALUEX Verbose: 0x0040
-- IMPORTX Verbose: 0x0080
String Resource Dir=C:PROGRA~1SAPMDM~1.5IMPORT~2LangStrings
Log Dir=Logs
SLD Registration=False
[SP04_BUSINESS_PARTNERWDFD00143366AMSQL_21_13_4_3]
Login=Admin
Password=
Chunk Size=50000
No. Of Chunks Proccessed In Parallel=5
Using the Verbose parameter you can define which errors, issues, messages and so on should be written into the MDIS log. You can find the logs directly in the port's log folder and in the log folder of your MDIS installation directory. If MDIS is not working or the import fails, these files contain some helpful information.
Kind regards
Michael

MDM - Import Manager

In the import Manager, I am unable to connect to any source database - Oracle, SQL Server. It gives me error message that the database is unavailable. But I can ping the databases and connect to them externally. I tried creating creating connections and ports in MDM console. I do not find any place where I can give details of database etc.

Hi Jay,
Please refer to the following link:
Import using Oracle
Also, make sure that Oracle client is installed on the server for MDM.
If you connect to source that is Oracle, then you must install Oracle client on the machine that is running the IM, for this source "file" - IM is connecting directly to that Oracle database (not thru MDM server).
I hope this helps,
Silpa

What is meant by criteria of Updateability in MDM Import manager

Hi,
What is meant by criteria of Updateability in MDM Import manager? i read some information, but i could understand, it says original data source be updateble. what is meant by Original data source.?
what is the use of option "Read-only" in Import manager logon screen.
Thanks

Hello Ankam,
You can check the Read-only option to prevent MDM from updating your data source.
Kindly see the below information on "DATA SOURCE UPDATES"
DATA SOURCE UPDATES
Some MDM Import Manager operations require that the original data source be updateable, thereby allowing new fields and/or entire new tables u2013 and the corresponding data values for each record u2013 to be automatically added to the data source before further processing.
Other operations simply create virtual fields in the MDM Import Manageru2019s workspace, although if the data source happens to be updateable, some of these operations instead add the new fields to the original data source as well.
NOTE ►► Updating the data source when possible allows you to
perform additional operations on the new fields as if they were part of
the original source data, and also use them as record matching fields.
NOTE ►► Fields that are added only if the data source is updateable
can be deleted automatically by the MDM Import Manager when you
exit or switch data sources based on the setting of the Delete Created
Fields on Exit configuration option.
Updateable Data Sources
Whether or not a data source is updateable depends upon the following:
u2022 Source type. The source Type must permit the MDM Import Manager to update its schema and insert the additional fields of data; some supported types are updateable and some are not.
u2022 Media. The media on which the data source resides must itself be updateable. If the media on which the data source resides is readonly, such as a CD-ROM, the data source cannot be updated.
u2022 Permissions. You must have the proper file system permissions to update the file, or the proper DBMS permissions to update the schema of the database.
u2022 Read-only option. You cannot have checked the Read-Only option, which prevents MDM from updating the data source even if the other conditions would otherwise permit it.
NOTE ►► The Read-Only option is: (1) enabled for source types that
can be updated (Access, Oracle, SQL Server, and XML); (2) disabled
and unchecked for those that use Access as an updateable staging
area (Delimited Text and Fixed Text); and (3) disabled and checked for
those that cannot be updated (Excel and ODBC).
NOTE ►► When the data source is SQL Server, the table names in
the database must not contain spaces; otherwise any operation that
would update the data source will fail.
Hope this helps.
Regards,
Vikas

How to save the setting in MDM import manager?

How to save the setting in MDM import manager? After I configure all things in MDM import manager, I try to save the setting, let's say, saved map name is " Test002", and then I export this map into desktop. After that, I logon Import manager again, and import this map file, system show me the same thing that I have to configure it again, because nothing was changed, what I configured before, were all disappeared.

Hi Alfred ,
are You not saving this map in Import Manager ? Import Manager itslef saves the map and remember it . Exporting map is only for backup .
Pls make changes and save the map . Exit and relogin . then see the map . It should be there . Pls let us know the result .
- An

Concatenation in Import manager(MDM)

Similar Messages

Maybe you are looking for