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

Similar Messages

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

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

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

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

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.

Sharepoint 2013 Active Directory Import- Manager field not updating

Hi,
SharePoint 2013 Active directory import -Manager field not updating
Concern/Issue-
We are using SharePoint and configured the Active Directory Import .First import it seems everything is working fine and OOB Organization chart built using User profile data is coming out right.
Now the user is moved from one Organization Unit to Another.
Now our Manager field is not Updating .There is change in AD manager attribute but not reflecting in the SharePoint User profile.
Manger field is mapped to "manager" attribute in SharePoint.
We tried removing the user and Re-Import using Incremental import but no luck.
Thanks for help in advance
Sachin

Moving a user from one OU to another in AD won't normally change the Manager attribute in AD. You would need to edit the user's organization settings to change the manager value in AD. I've also seen these changes not be picked up unless something
other than just the manager field in AD changing. Try changing something like Office location and see if the manager change is picked up by AD Import.
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

Import Manager and Display Fields

I've been using SRM-MDM 3.0 for a couple of months and 1 fundamental MDM design has always bothered me and I was hoping to get some resolve on this.
The purpose of Display Field is 2 folds:
1. Display the field in the Catalog Search UI for a lookup table: i.e. if both Supplier Name and ID are Display Fields, then in the Search UI, both fields are displayed to the end-user. If only Supplier ID was the display field, then in the UI only the ID is displayed.
- From a usability pov, tables such as Supplier and Product Group should have the name or description fields displayed in the Search UI as the numeric values are meaningless to the end-users.
2. Display field ALSO affect what is the key used to import data into a table. So if Supplier ID is the display field for Supplier table, then in Import Manager, the Supplier ID values are displayed and must be mapped to the source values.
- From an importing pov, mapping values should always be an index-like field, such as Supplier ID or Product Group ID, or ISO, and usually never the actual name or description field.
But SAP has tied the two together. So in order to display the name/description to the end-user, we must enable the name/description field as a Display Field. But we also want to map based on the index/ID field, so we also enable the index/ID field as a Display Field. Now in Import Manager, we have two Display Fields for a table (i.e. Supplier ID and Supplier Name for Supplier table) and I've noticed some issues with this:
1. You import file must have BOTH values (index/ID and the name/description fields) in the source, in order to Automap. If your source file only has 1 field, like in MECCM when extracting ECC contract, ONLY the Supplier ID, or Category ID is extracted, Automap is not possible. What is funny is that standard SAP extract program only extracts the ID fields, BUT the standard SAP repository has the name/description fields as the Display Field. Automap is a must for tables like Product Group where hundreds of lines can make manual mapping a pain.
2. I also noticed you cannot Add values to a table that has 2 Display Fields, you can only map to existing values. The Add button is grayed out.
With all that said, when you're replication ECC Contract Data using MECCM, for tables like Supplier and Product Group, what fields should be set as Display Fields, and if there are multiple Display Fields, what special setting needs to be done in Import Manager to enable automapping? Even standard SAP Import Map (_MDMContractDataTransmission_ProductID) throws errors when multiple fields are set as Display Fields.
I'm not familiar with the partitioning function, and I've seen PDF's about it, but don't really see how it could be helpful. I've also read someone suggesting changing the DF's before import, which I think is unacceptable, as this requires unloading/loading repositories everytime an import happens.
Thanks for reading my paragraph and any input is greatly appreciated.
Edited by: Derek Xu on Apr 30, 2009 6:50 PM

Hi Derek,
Thanks for writing your thoughts. I would like to provide some information on one of your points where in you have mentioned that :
You import file must have BOTH values (index/ID and the name/description fields) in the source, in order to Automap. If your source file only has 1 field, like in MECCM when extracting ECC contract, ONLY the Supplier ID, or Category ID is extracted, Automap is not possible.
I completely agree that if you have 2 fields in MDM repository and you are only importing only one of them, then you cannot use the Automap feature of Import Manager. So in your case, the description is not getting importing, so you cannot use Automap in that case.
I had a very similar requirement in one of my project and we went with creation of a Import Value template. We created a template with all the possible values for all the look up tables in that and mapped it once in the Map. Hence, next time, the Map was used to automatically Map the source and Destination values for all the look up tables.
SAP-MDM Automatic Import Requirement u2013 Creation of a Value Mapping Template:
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/80ad0cff-19ef-2b10-54b7-d4c7eb4390dd
Please read the above article and hope its useful. You can go for this approach in your case if suitable.
I have mentioned examples of descriptions and their respective fields in the article.
Hope it helps.
Thanks and Regards
Nitin jain

Date field conversion in Import Manager

Hi,
I am getting the source Date field as 'Text' type and want to convert it to Date type.
Is it possible in import Manager?
What are the best way to manage the issue.
Appreciate your reply
regards,
reo

Hi Reo,
The data types of source data values are automatically
converted within the Source Values grid based on the data type of the
destination field to which the source field is mapped, even when stored
in the source data as text values.
Original source values appear with their original data type in the Value
column, and the converted values appear in the Converted Value
column with the data type of the mapped destination field and the
proper grid cell type for editing (e.g. text, numeric, measurement,
currency, date, time, Boolean). If necessary, individual values can then
be manually edited to override errors or omissions in the source data.
Regards
Neethu Joy.

Field Type in Import Manager

Dear all,
I am importing Vendors in MDM SP4 that I extracted from BI. In Import manager my Vendor and GN_Vendor fields appears with numeric type but I created them in the Console with text type. I also cheched the xls input file but they are in text format. Can you please tell me where to change the field type from numeric to text.
Because I can only import Vendors who have numeric name.
In advance thank you for your kind help,
Aklilu

Hi Aklilu,
As Far as I understand,
the problem is with your source and not the destination.
The source field type from BI, is numerical and this has to be changed to text in the source
The destination field is a text field and hence no need to change the field type in MDM.
Hope this helps you solve the problem.
Let me know the result.
Thanks and Regards,
Rashmi Jadhav

How to import data usin Import manager if one of the field is of type LOOKUP[FLAT].

Consider a scenario:
Where I created a Main table named STUDENT and it has 4 fields,
a) Among which 2 fields are OF DATA TYPE TEXT[50] and
b) Remaining two are of DATA TYPE LOOKUP[FLAT] and corresponding look up table also created in the repository.
When I tried to create a file with certain input records and tried to import the values into the Main table using MDM IMPORT Manager, I am getting error at the IMPORT STATUS tab with the action item message: MAP 'FILED NAME OF LOOKUP[FLAT] TABLE' FIELD VALUE(S).
Do I need to do any special action to import record if the field is of data type LOOKUP[FLAT].
Please advice.

Hi,
Since you need to import value into a field which is referred by a flat look table, you need to map the values of that field to the values maintain in flat look up table.
You can do the mapping from "Map Fields/Values" Tab.
You have probably Mapped Source fields with destination fields, but in case of importing values in lookup fields you need to map Source Value with destination value.
Keep the cursor on the required lookup field in Source field section, below that section you will be able to see Source Value section perform the mapping in that section too and it will resolve your issue.
Regards,

Matching records in Import Manager

Dear experts,
I'm using SRM-MDM Catalog 3.0 and I need to create different catalogs using the same records, distinguished only by some fields like Catalog name, Category and supplier.
But because Iu2019m using same product ID, when I try to import the new records I can only update or replace the fields, which was not the idea.
Does anyone know if this scenario is possible?
Thanks in advance.
Best regards,
Andreia Nascimento

Hi Andreia,
For importing new records with same Product ID. In Import Manager under Match Records tab Your Matching fields: should be combination of Product ID, Catalog Name, Category and Supplier rather than Product ID only. This will result in importing new records rather than update or replace the fields.
Regards,
Mandeep Saini

Combine fields in Import manager

Similar Messages

Maybe you are looking for