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

Similar Messages

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

Hierarchy Loads using Import Manager

Running on 7.1 SP05 using the SAP supplied Vendor Master repostory archive.
Attempting to load the Regions hierarchy table which contains three fields: Country (lookup flat), Region Code (text) and Region Name (text). When defining the map in Import Manager it will only allow me to select Region Name as the matching field. And, as a result, it will not load all of the data in my load file - it loads the first value of Region Name and skips the other records where Region Name is duplicated. This makes sense; however, I need to be able to select both Region Name and Country as my matching fields when defining the map. These two fields are the unique identifier for the load file and all the data would be loaded correctly if I was able to select Country as well. I have tried making Country both a unique field and a display field in Console, but to no avail.
Does anyone know how to get Country to appear in the "Mapped destination fields" so that I can match on both Region Name and Country?

Hi Reinhardt,
I think you can achieve it by setting country field also as Display field (DF) along with existing Region name (DF) in Regions Hierarchy Table of MDM console.
Regards,
Mandeep Saini

Hierarchy loading in Import Manager

Hi,
I have the following scenario to load Hierarchy but Import Manager is throwing an error message ' Duplicate in Clomn-2".
However the same structure I am able to make in Data Manger manually for a 3 level hierarchy which confirm that hierarchy table supports that structure.
Column1   Column-2
(parent)    (Child)
                3M
3M           Abrasive
Abrasive    Roll
3M            Coil
Coil           Copper
GE           Abrasive
SH-Ent     Coil
The data shows Manufacturer 3M and GE both have 'Abrasive' which is very normal but not able to load thru 'create Hierarchy' option after selecting 2 flds in IM.
IM throws a duplicate error , "Duplicate in Column-2: Abrasive"
Hope the example communicates properly.
Appreciate ur help/tips
-reo

Guys,
Found the way to do that.The steps to follow are
1) In partition have to select all mutilevel (for my case 3 levels) individual columns one by one and select all the flds brought to right pane to 'combine' them.
2)Select the combine field in partion, right click and select 'split partion' from context menu.
3)In map , map this partition field of source side to 'Name' fld of destination hierarchy table.
This works excellent
However I have a challenge to convert 220k hierarchy input record.The system is just hanging even if I have splitted the input files to 6/7 sections in MS access.
Any suggestion /tips appreciated.
-reo

Tuple Loads using Import Manager

Running on 7.1 SP05 using the SAP supplied Vendor Master repostory archive.
Attempting to load company code data in the Vendors main table. Company Code Data is set-up as a tuple table in Console.
When defining the map in Import Manager it will only allow me to select Vendor Number as the matching field. And, as a result, it will not load all of the data in my load file - it loads the first value of Vendor Number and skips the other records where Vendor Number is duplicated. This makes sense; however, I need to be able to select both Vendor Number and Company Code as my matching fields when defining the map. These two fields are the unique identifier for the load file and all the data would be loaded correctly if I was able to select Company Code as well.
I read where you can set the tuple update option and I did this by adding Company Code, but for some reason, it is still only using Vendor Number as the matching field and not including Company Code with it.
Does anyone know how to get Company Code to appear in the "Mapped destination fields" so that I can match on both Vendor Number and Company Code? Or do other options exist where I could accurately load the tuple table?

You match on the correct vendor in the Match Records tab. This positions you at the correct vendor.
To match on the correct Company Code you use the update tuple option (as you have done). The Company Code should be the only field that you use to match on the Company Code tuple. So, when the incoming record has the same Company Code the tuple will get updated. If the incoming record has a different Company Code, then you can set the options to either create a new tuple or skip the input record.
You can not match on the Company Code in the Match Records tab.
Edited by: Tom Belcher on Feb 18, 2011 10:13 AM

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

Map Auto ID field in import manager

Hello all
I need to make a quick fix to the data in our repository. A field needs to be updated based on a small formula. To do so I have syndicated the information and imported it to and SQL database where calculated the result. I exported it to a text file.
Now I need to create a map to update the field. However the only common ID is the auto ID field I have set up. I can't map the source to the destination - the map button is grayed out when I select the auto ID field.
Is it not possible to map it or is it because the auto ID field is numeric and my import is text.
BR
/Alexander

Hi Alexander,
It is true that the Auto Id field cannot be imported or syndicated.But as you said you have used only the auto id field as the Primary matching fiel dand you need the Auto id information only so as to import then a workaround i would suggest
- Create a new field in your repository in console say(Auto id1)
- Make this field as calculated field
- In the calculation expression just selct the auto id field from the dropdown
- This will populate the autoid field1 with the values same as the auto id field
- And then try mapping it to this newly craeted field while importing.
- This is just a workaround i am not sure whether it will address your problem directly
Hope It Helped,
Thanks & Regards
Simona Pinto

Cannot find the maps stored in import manager during port creation

Hi All,
I am unable to find any maps that i saved in import manager during port creation ,the maps are not showing in dropdown list during port creation in console.Do i need to store the maps that i have in import manager in specific place under mdm server,so that i can see them during port creation.
All i need to do is assign my import map during inbound port creation,but i cannot find any maps in console.
Could I know whether i am storing my maps some where other than default location.
Thanks
Aravind

Hi Aravind,
First of all check the remote system assigned to ur Port. After that go to import manager. When u logon to the import manager, u get a window "Connect to source". Mention the same remote system over there.Select the file type.Browse the file and map the fields,values,field matching and save the map. then unload the repo and assign the map to the port.
Second way is, u create the port first and give any particular remote system to it. Put the file (u want to use for mapping) in the ready folder of that port and in connect to source window select the type as port, remote system(ame as used port port) and port.then map and save. unload the repo and assign the map to port. Ready folder will be in ur server at location: C drive or D drive->SAP MDM 5.5 ->server->distributions->repo name->inbound->port code->ready. For this option, Ur port type should be manual. After assigning the map u can change it to automatic or keep it manual as per ur requirement.
Hope this solves ur problem.
Regards,
Dheeraj.
Edited by: Dheeraj Kumar on May 6, 2008 9:16 AM

Differ between import manager and import server

Hi to all,
Can any one explain difference between import server and import manager and how the data will be imported to the same.
Regards
MM

Hi reddy,
Can any one explain difference between import server and import manager and how the data will be imported to the same
Please follow the text below, which has been taken from the help.sap.com
Both MDIS and the MDM Import Manager can import data from a source file into an MDM repository. However, each has unique capabilities that distinguish it from the other. When each is used to its advantage, the result is an import strategy which provides the most efficient importing of data possible.
The strength of the Import Manager is its connection to the source data, which enables its interactive map-making capabilities. When the Import Manager connects to a source it preloads the entire source file, giving it knowledge of every field and every value in the source data. This u201Ctotal awarenessu201D is crucial for preparing a complete import map. To help ensure a map is complete, the Import Manageru2019s Import Status tab alerts users to any discrepancies between source data values and the current map. The user can fix these problems interactively within the Import Manager and save the corrected map before any data is imported.
Preloading an entire source file comes at a price, however. It consumes memory on the computer running the Import Manager and very large source files may exhaust the computeru2019s available memory.
By contrast, MDISu2019s strengths are its scalability and automation.
For scalability, instead of preloading the entire source file into the host machineu2019s memory as the Import Manager does, MDIS processes records in a stream by loading a record at a time into memory.
This streaming technique enables MDIS to process much larger source files than the Import Manager, as the demand for memory on the host machine is not affected by the size of the import file.
In addition to file size, file quantity poses a second scalability challenge. For example, a real-time transactional environment may produce a staggering number of files, each containing only one or two records. To import these files individually through Import Manager would be extremely inefficient. MDIS tackles this problem with a file aggregation feature that processes files systematically in batches rather than as individual files, resulting in faster, more efficient import of data.
As it relates to automation, MDIS requires no user intervention to import files to an MDM repository. Instead, it relies on maps created previously within the Import Manager. Once an import file is placed in the appropriate folder, its data is imported automatically into the MDM repository using the rules of the pre-defined import map. Once a file is processed, MDIS scans the repository for the next file to import. This process continues 24 hours a day, seven days a week, until either MDIS or MDM Server are stopped.
The trade-off for this scalability and automation is that if discrepancies between the source data and the import map arise, MDIS cannot u201Cfixu201D these problems by itself. Instead, the u201Cproblem casesu201D can be fixed manually at a later time using the interactive capabilities of the Import Manager. Unlike the Import Manager, however, MDIS can set aside problem records or files and continue importing.
These conceptual and operational differences between the Import Manager and MDIS are summarized in the table below.
Item
Import Manager
MDIS
Source file location
Anywhere
Automatic inbound port
Import process
Interactive
Automatic
Import map state
Editable
Read-only
Object loaded in memory
Entire import file
Individual records
Streaming import support
No
Yes
File aggregation support
No
Yes
Maximum import file size
Limited (50,000 records)
Unlimited
Status location
Import Status Tab
MDM Console/Report file
Error correction prior to import
Yes
No
Exception handling during import
No
Yes
For additional info, kindly refer the link below:
http://help.sap.com/saphelp_mdm550/helpdata/en/43/12036df94c3e92e10000000a1553f6/frameset.htm
GO to-> MDM import Server
Hope it helps.
Thanks and Regards
Nitin Jain

Port disabled in Import Manager

Hi,
I created remote system, port (with map and XML Schema) in Console and tried to import XML file manually in Import Manager using port option. The port I created in console is appearing in the drop down but in grey color and in disabled mode. I could not import data from XML file.
Did I miss anything?
Thanks.

Hi,
In ready folder, whatever XML file you placed then Port for this get enabled, it only after selecting port it checks wheteher your XML content Verifies with your XSD.
it may be due to :
1. Firstly in MDM Console , All port Settings which have you done is correct:
Type = Inbound, Remote System = say ECC, ofcourse your Map = which you saved in import Manager, Format = XML Schema, XML Schema = Select your XML Schema ( which you saved in XML Schemas table), Processing Type =Automatic, file Aggregation count =1 and Block on Structura Exception = Yes , Here in Staus it will show Has Data if your XML file is placed in ready folder otherwise Empty.
Apart from this, During Import Manager, Select your Type = Port, Remote Sytem = ECC which you defined During MDM Console Carefully, if u r selcting any other Remote System Port in MDM Import Manager will not get enabled.
Hope it will Help you,
Rewards if Useful.....
Mandeep Saini

Error Message - Import Manager

Helllo All
I recieve a message when trying to import some records
The Map cannot be loaded because the table "Record" is not a source.
We are "missing" the table "Record" from the dropdown.
Can some one tell me how I can add/fine this table again?
Regards
Con

Hi,
In your case the "Record" disappears whenever you have only one record in your XML file. Instead of displaying nodes under "Record", it displays all fields under its parent node (let us say "Records").This situation occurs specifically whenever you are trying to import an XML file without refering to an XML Schema.
To make things clear further: You created a map with an XML file that has more than one record i.e., with a file that has the "Record" node. So, whenver you try to open the map with another XML file that has only one record it fails as there is no "Record" node.
Solution: Always refer to an XML Schema. This way, you are enforcing the XML structure i.e., "Record" node will be available even if you have only one record in your input XML file.
Please let me know in case you need more details in this regard.
Hope this helps,
Regards,
Rajani

MDM Maps in Import Manager crashes and does not open

I am having problems with some of my maps in the Import Manager. While working in the Import Manager the maps are fine and I am able to import the data, but once I exit out of Import Manager and try to open the same map, it crashes and closes the application. I am not sure what the issue my be. Could it be the fields I am mapping to are creating a conflict somewhere? Has anyone encountered the same problem. Any insight on this issue would be greatly appreciated. Thanks!

This was happening to me as well. Basically, the data I was submitting was much too large for MDM to handle which resulted in a timeout. To resolve this, I copied my data to temp tables to minimize the number of records I was sending it. After my experience with Import Manager, I think it's safe to say that it was not intended for large data loads. In the future I will be using Import Server and translate my data to XML.

SRM-MDM - loading hyperlink field in import manager

Hi forum members,
I am having trouble loading the hyperlinks in for SRM-MDM in import manager.
What fields / values do I need to map to load this please?
I have mapped the hyperlink source field to the hyperlink destination field, but get an error during import executing saying there is an creating lookup table entry.
Is anyone able to provide step-by-step details of which mappings are needed?
Thanks very much,
Nick

Hi Nicholas,
the non-qualifier for the hyperlinks table is the type. Therefore you need to also map this field. Please check note 1077701 (under 11.) on how to use the types.
Let us know whether that helped.
Best regards
Christian

XML file error while loading import manager

Hi all,
I am new to MDM.
I have archive repository(.a2a file),xsd files,import maps and export maps.I have unarchived the repository in console and I am trying to load import manager by selecting the file type as XML schema, client system as MDM, XMl schema name and file name as XML file of given XSD in import manager folder of server.
I am getting error like "failed to parse XML file".
Please help me out regarding this.
Thanks in advance.
Ravi.

Hi ravi,
Is it MSXML 4.0 SP2 parser?
<a href="http://www.microsoft.com/downloads/details.aspx?FamilyID=3144b72b-b4f2-46da-b4b6-c5d7485f2b42&DisplayLang=en">http://www.microsoft.com/downloads/details.aspx?FamilyID=3144b72b-b4f2-46da-b4b6-c5d7485f2b42&DisplayLang=en</a>
Try installing this and let me know.
Thanks and Regards,
<b>Sagar Sonje</b>
Message was edited by:
Sagar Sonje

Reuse of MAP in Import Manager

I am trying to reuse a MAP created to load KNA1 table in Import Manager in the same server. The Source file name and file type (.xls) is the same, as well as the original worksheet name. While the Import Manager is matching records, it is abending w/ following msg - Error sig:
AppName: importmanager.exe; Appver 1.0.0.1; ModName: importmanager.exe; ModVer: 1.0.0.1; Offset: 004e9c90
Thanks

Sure, this is possible. Remember that map/syn files are useful when you know in advance nothing has changed, that is, when automating the process (via batch/server processing).
One example might be if MDM is expecting numeric value, whereas in the past you used a text value. You might not be changing the source data, but you have made the MDM Repository more restricted.
Perhaps you should review which changes have taken place, something might be escaping your sigh
I hope this helps
Regards
Alejandro

Map cannot be loaded in import manager | MDM

Similar Messages

Maybe you are looking for