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

Similar Messages

Set Key Field in Import Manager

Hi All,
I have 2 fields in my source file(name,category) .category(look up Field) is the key field and name(display Field) is the matching field.
I got file like this......
Name                  category
1                           A
1                           B
1                           C
While importing i got an error stating that Import failed. The destination record was referred to by multiple source records. Duplicate source records should be merged before importing them.
Import action: Update (All Mapped Fields)Source record no: 1
But in this case my key field is Category based on category then these 3 records will be 3 different records.
Please let me know the use of Set Key field in the Import Manager and how it works?

Hi,
It's not about set of key field in MDM Import Manager but the reason is that you can not select more than 1 category(Lookup Taxonomy) in maintable for one record. thats why error is coming because for this Property Multi-valued always No.
Even, you can try this in Data Manager manually create three Category A, B and C in taxonomy mode on selecting Sub table Categories, then on selecting main table, when you select category field(which is lookup to categories table)for a particular record you could able to select only one category A, B or C.
i would suggest make a Attribute of type text having three values A, B and C and mark this as Multi-Valued in Attribute Detail and link this Attribute with your category. in this way you can attach three values A, B and C with your Record.
Other thing you can do,make this category field as (Lookup Hierarchy not lookup taxonomy) in main table to Subtable(Hierarchy) then for this field in main table you can set Property Multi-valued = Yes in MDM console and then after Import using MDM Import Manager finally only one record will get created in Data Manager as:
Name Category
1         A;B;C
Hope it will Help you,
Rewards if Useful.....
Mandeep Saini
Edited by: Mandeep Saini on Jun 20, 2008 8:46 AM

Import Manager - Problem with 0..n field in Import Manager

Iu2019m having problems with XMLs that contain multiple or single tags in MDIS process. For example: I did the map using a XML with multiple tags for Address:
<address>
<item>
u2026
</item>
<item>
u2026
</item>
</address>
When I send two address or more Address, the Import Server work fine, but when I send only one Address, the address is not imported.
<address>
<item>
</item>
<item>
</item>
</address>
Opening the xml file with only one Address in Import Manager, I saw that the fields isnu2019t mapped, but when I open a xml file with multiple Address itu2019s open correctly.
The XSD cardinality for the Address\Item is 0..n

Hi Evandro ,
If it is processing the input file correctly through the Manul Import manager process then update your latest Map by using SAVE As option or else save this correct map with a new name altogether and use this new map in the port for automatic importing.
If your file is able to process correctly through the Import manager without showing any errors till the Import step in the Import manager then this map must be correct and shoul automate the importing correctly.
Provided you are using the similar file for automatic importing as well.The file name and the fields as well as the value mapping as saved in this corrected map must not differ with the input file else this saved map will not be able to import correctly.
Check to see if you have made correct setting for automatic importing by refering the below link:
http://help.sap.com/saphelp_mdm550/helpdata/en/43/12036df94c3e92e10000000a1553f6/frameset.htm (Automatic importing MDIS - Import manager ref guide>MDM import server(MDIS)>MDIS Consfiguration)
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/8973bcaf-0801-0010-b7a7-f6af6b1df00e(mdm import and syndication server)
Also check the exception folders if your import is not taking place automatically:
http://help.sap.com/saphelp_mdm550/helpdata/en/43/12036df94c3e92e10000000a1553f6/frameset.htm (Exceptions- MDM Import Manager MDIS-Exception handling)
Hope It Helped
Thanks & Regards
Simona Pinto

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

Combining two source fields in Import Manager

Hi,
I am trying to combine two source fields say fld1 with 5 digit and Fld2 with 3 digit so that combined fld3 of 8 digit can be mapped to a 8 digit field in destination MDM side.
Any suggestion how to do this is highly appreciated
Thanks,
-reo

Hi Reo,
I am just adding details to how to combine fields in the import manager.
To combine two or more existing partitions for a destination node steps are as follows:
1. In the appropriate source hierarchy tree, select the node whose partitions you want to combine.
2. click on the Partition Field/Value tab to make it the active tab.
3. In the appropriate Partition list, select the two or more partition items you want to combine into a single partition.
4. Click on the Combine button, or right-click on one of the items and choose Combine Partitions from the context menu.
5. MDM combines the selected partition items.
6. Now you can map this partition directly to the destination field.
But as ur requirement seems ,u do not need to set delimiter.
Hope it will help you and let me know the results. please remark .
Thanks,
Shiv Prashant Dixit

Combine fields in Import manager

Dear all,
I want to import two related fields to one field in the destinatation. This is linked to a look up table with a combined key.
Now I can combine the two input fields and map it to the destination field (two display fileds).
However the field mapping can not be done by automap, only manual mapping.
Does anyone know how to get an automap?
thanks in advance

Hi
I want to import two related fields to one field in the destinatation. This is linked to a look up table with a combined key.
Now I can combine the two input fields and map it to the destination field (two display fileds).
However the field mapping can not be done by automap, only manual mapping.
In the lookup table suppose we have field1 and field2 as the display fields then for the table define field1+field2 as the unique key in console. Next for the lookup table also enable remote key in console.
Now while importing clone the field1 and field2 and partition field1 using field2 with a delimiter as ;
Next map the combined field as you have already done and also map the partitioned field to the remote key(field1+field2)
Automap will work now..
best regards
Ravi

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

How to Split field into multiple fields in Import Manager without delem

Hi
Is there any method to Split a record in MDM without using delimitter?
I dont want to use any delemitter My field content in Source is PRODLABELPACK and I want to split it into 3 fields in destination Field1= PROD
Field2=LABEL Field3=PACK
I know how to split it if the content is PROD_LABEL_PACK .But we dont want to use delimiter in the firld and want to use some substring function
Regards
Prashant

You Can use below FM SWA_STRING_SPLIT -
First Use READ_TEXT FM.
then loop into
loop at tline.
Here use 'SWA_STRING_SPLIT' -> Pass tdline and append the text into other internal table.
endloop
Thank you
Seshu

Map a field more than once in import manager

Hi experts,
is it possible to map a source field to more than one destination fields in import manager? E.g. I have a source field "client" and I have to map it to a destination field "client" and also to a combined lookup field which consists of a field "client" and "systemname".
Thanks for your answers. Regards, bd

Hi,
Yes you can achieve this , During Import Manager when mapping source field to target field in Map Field/Values tab, just above this on left hand side you can see Source Hierarchy in MDM Import Manger, Right click on field which you want to map more than one Destination field, here you get Clone Field option which make clone field , so you can map this clone field to other second destination field which will serve your purpose.
Hope it will Help you,
Rewards if Useful.....
Mandeep Saini

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

Issue in Mapping Qualified Table in Import Manager

Hi Experts
I have extracted Customer data from R/3 ECC, I could successfully loaded reference data, but when trying to load Main table data (Using DEBMDM06 MAP) I am getting mapping issues with Qualified table (Sales Data and Bank Details).
Error Messages
Map 'Sales Data' field to import qualifier(s)
Map 'Bank Detals' field to import qualifier(s)
I have checked and found that all the field and value mapping is in place, If i remove mapping for the qualified table fields then the data is ready to import.
What is the issue, and how do I import Qualified Table data.
Appreciate your inputs
Gaurav.

Hi vickey ,
Kindly go through the below link it will help you understand better the mapping the workinga nd importing of Qualified tables:
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00a15239-684e-2b10-b8ae-b936b7d1c1fe
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c03240fa-cc3e-2b10-aa9a-a5798e319a6e(Qualified importing with main table)
Hope It Helped
Thanks & Regards
Simona Pinto

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

How to add hyperlinks in Import Manager

Dear MDM-gurus!
I really tried hard to find the solution, but couldn't find it here or in OSS.
We already have a repository with more than 50.000 items.
What I'd like to do is to add hyperlinks to PDF-files in the internet to each item.
For this we got an excel-file from the supplier with the supplier part number in one column, the PDF-link in another column and the .
In Data Manager I was able to add links manually or also with importing entries of the excel-file. Importing from excel takes a LOT of time. I don' t know why:
- Fields to import: Hyperlinks
- Key fields: Supplier part number.
--> Action: Update all single matches.
How can I import hyperlinks in Import Manager, make the mapping and then update the records faster? E.g. I could not find the field "URL <Hyperlink> [Qual]" in Import Manager
Thanks for your help and best regards,
Henning

Resolved!
I accidently oversaw the URL fields in Import Manager in table catalog items.

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

Map Auto ID field in import manager

Similar Messages

Maybe you are looking for