Import Manager Partitioning/Pivot Question

My source data has two fields (Part Number, Page Number). There are multiple rows for each part number with a single value for page number. I need to combine the page number values for all instances of each part number and import into MDM as a comma delimited value.
For example:
Part Number | Page Number
A1 | 1
A1 | 2
I want to store in destination field "Page Numbers" as "1, 2" for single record where part number is "A1".
I do not understand how to accomplish this with Import Manager.

Hi ,
I tried in one more case also but there was limitaion .In that case you will end up with more no. of delimiters or nulls
You can try with same procedure but just define a clone field for partnumber and create pivot table with the same constraints
just swaaping with newly introduced field.
After this just partiton all the new fields and then combine .
the newly partition field treat as page number and map to destination field and also map source part number with destination field.
This is also an option with limitation of trailng or preceeding null .I think we can ignore that also for that we have to do some setting of ignoring nulls.
Please try this alos but if you are able to add new field than that is the best one.
please revert back with your results.
Thanks,
Sudhanshu

Similar Messages

Import Manager Match Records question

Hi
I am following the below file
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a0a9cee4-9cd1-2a10-62b6-ea2acb06a5a3
Till 5.2 I have done it successfully
while proceeding through the match records
i.e.
In Import Manager, Match Records------> Default Import Action
is not active to create Records
35 of 35 ->None->None--->SKIP (its inactive)
pls check this screen shot
http://www.flickr.com/photos/11212307@N08/2555733854/
why it is inactive , where should I have to check
Any Help pls
Thanks
manian

Hi,
i have got your Problem, you could come to know if you try this
Create an Excel file as below
Category Type Attribute Value
PC Text A 10
PC Text B 11
Now during import this Taxonomy:
First Map your Source Category Field with your Target Name Field when Select Categories as Destination Table
So in MDM Data Manager: when select Categories as destination Table you will GET PC as Value there.
Noe 2nd step Select Categories( Attributes) as your Destination Table here Map Source Attribute and Type Fields with corresponding Target Destination fields.
If you skip this 2nd step and just go for Saelcting Categories(Text Values) as your Destination table , the problem you describe is come into picture.coz that attributes are not available into MDM data Manager.thats why even for Update All Update Options it is showing 0 Record.
Hope it will clear your doubt,
Rewards if useful.....
Mandeep Saini
Edited by: Mandeep Saini on Jun 6, 2008 9:51 AM

Overview of Import Manager

Friends,
Iam new to MDM.Could anybody give an overview of Import Manager.I have very less time to prepare for MDM.I need the basic topics in MDM for presentation.This topics must lead the consultant to work on MDM.
Reward points will be awarded for suitable answers.

Hi,
Import Manager is basically used to import data in the selected repository.
Initially When you launch Import manager it asks you for repository name,language and username & password(can be Admin or one specified in console)
Then next step it asks you for
1.)Type(type of source file i.e excel,access,port(in case of remote system),ODBC,XML).
2)Remote system(MDM For local desktop or ABCfor client system)
3)Filename
Then you select the source file and destination table.
Then source preview tab you can see the source data ,In partition tab you can create combination of fields for say hierarchy.In Map fields you should map corresponding source and destination fields and values .
In Match Records tab you select the field as per the uniqueness of this field records are imported.selected import action as create for first import.
In Import Status if its ready to import execute import.
Other features of Import manager include pivoting ,reverse pivoting,split in hierarchy,split in multiple fields,convert data values etc.
reward points if helpful
Regards
Nisha
Edited by: Nisha Lalwani on Feb 14, 2008 2:20 PM

How to use Destination partitions in Import Manager ..?

Hello everybody,
I am trying to implement example given in latest MDM Import manager reference guide (page no 177). Wherein i have in source file category as
Source___________________Destination
Category_________________Category___Printer type__DPI
300 DPI Laser Printers_______Printers____Laser_______300
300 DPI Inkjet Printers_______Printers____Inkjet_______ 300
600 DPI Dot Matrix Printers___Printers____Dot Matrix___600
Where in destination printer type & DPI are my attributes for category printers.
How can I make use of partition tab to achieve this????
I m unable to get any attribute for partition under Destination Partition pane..

Hi Anton
Format your GM Time source as YYYY:MM:DD:HH:NN:SS:TTT (e.g. 2010:02:19:14:34:28:000). Deviations from this format seem to confuse the IM.
HTH,
Mark

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

Add button inactive in Match record step in Import manager

Hello,
In the Main table, I want to see the country data as 'US; United States' in country field.
I have made both 'country code' and 'country description' as display fields in the country flat lookup table.
When I load country code and country description from import manager from an excel file, the 'Add' button in Match records step is inactive for both the fields.
How can I do the matching in import manager without sacrificing my requirement of showing country as 'US; United States' in main table ?
Thanks,

answer to this question is already available in forum.

Problem in mapping from import manager to Data manager

hi friend's....I got a problem while mapping the data from import manager to Data manager .The problem is the data in import manager (i.e source hierarchy) will map to single filed in data manager ( i.e target hierarchy)..
Help me it will be great full to me
Regards
Yugandhar

Hi Ana,
If you have a hierarchy in this format:
N1            N2                 N3
A              A1                 A11
A              A2                 A21
A              A3                 A31
B              B1                 B11
Then u have to follow these steps for import.
1. Select source file and destination hierarchy table at top of import manager.
2. Go to Partitions tab (Second tab) Just above the tabs, if u click on the plus sign against your source file, you will see N1, N2 and N3. Cick on N1 and in partition tab, add N2 to right side by double clicking on N2.
3. Now add N3 to right side by double clicking on it.
4. Go to field mapping (Third tab). There you will see a field N1(Partition). Map this field to yourhierarchy field on destination side.
5. In value mapping (Below the field mapping), Expand your source hierarchy. Select all (ctrl + A). Click on "Add" button. Select "Add Branch as child" option.
6. Go to Matching tab (Fourth tab). only one field will be there. take ity on the right side. and select the import action as "Create".
7. Go to last tab. Click on import button.
Your hierarchy has been imported. You can check it in data manager (in hierarchy mode).
Hope this solves your problem.
Regards,
Dheeraj.

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"
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.

Import Manager Usage : Approaches for developing Import file structure and text validations

Hi Experts,
We are having 50+ import maps. We have provided option to users to drop the files for data import. Currently Import Manager(7.1 Sp08) does not have capability of pre-import validation of file data such as
a. file structure - number of columns specific to import map
b. file text validations - special characters, empty lines, empty cells
c. Uniqueness of the records in the file
For this, we are planning to build temporary folder(port specific) in which user drops in the file. We use the custom development to do above mentioned validations and then move the files to actual import ports.
Please let us know if you have worked on similar requirements and how you have fulfilled such requirements.
Regards,
Ganga

Hi Ganga,
Assuming you have a well defined xsd and are getting valid xmls from source in the Inbound Port of MDM. Also,you have a Primary key in form of External ID (say).
So just by making and defining a XSD you get most of what you want in your questions a and b.
Now if you wish to use PI to drop files in the inbound port then you can build all the validations in PI itself and you would not need Staging table.
Otherwise,you can have another table (preferably Main table) in the same repository or other dummy repository where records are created on import based on External ID.
Here you can launch an MDM workflow on import of these records and run assignments to replace unwanted characters and Validations to give error for rejecting some records based on the data quality level desired.Once unwanted characters are removed and data is validated it can be syndicated using a syndication step in the Workflow.So records which fail are not sent and which pass are sent to a outbound port.
From the outbound port PI or some other job can pick the file from this outbound folder and drop to Inbound folder of the same repository which imports to the required Primary Main table.Here again you have the option to leverage validations in PI and further check if data is fine.
Once this activity is done you can delete the records from the staging table.
Thanks,
Ravi

Special Charecter acceptable in Import manager?

Hell Experts,
I have a situation where i need to extract data from syndicator and load the same file into MDM via Import manager.
The extracted file format is '.txt' (Flat File)
When i try to reload the same file, import manager throws error when it spots speacial charecters in teh Flat file (Ex: " )
When i remove " in the Source file i am able to import the file. But i cannot ask the Users to each time they get the flat file to open it and remove the " .
is there any way to load this file via Import manager with out manipulating the data init?
Please Help.
Regards
Eva

Hi Eva,
Kindly find the below threads, which may help to sort your issue.
http://scn.sap.com/thread/1860282
https://www.interspire.com/support/kb/questions/1071/When+importing+contacts+from+a+CSV+file,+special+characters+(e.g.+%E8,+%E9,+%EA...)+are+not+visible
Regards
Rahul

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

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

Using Import manager with XI

Hi,
I am working with Import manager without any connection with XI. So, I have created by myself a XML file and a its corresponding XSD file, and I have put the XSD file into the console using XML Schemas Table.
Finally, I choose into the MDM Import manager the next options:
 - Type: XML Schema.
 - Client System: MDM.
 - XML Schema: the XML Schema declared.
 - File name: the XML file created.
The import manager imports the XML file correctly. But, my question is:
It's the same using XI? I mean, How works MDM Import manager using XI?
For instance, If I want to work with a CRM client system:
 1. XI works with CRM and tranforms its IDocs to XML.
 2. XI puts its XML file into any folder (than doesn't correspond with the ports declared into the MDM Console).
 3. Finally, XML takes the XML file in to that folder (exactly in the same way that I did before)
 4. MDM Import manager then imports the XML file into the repository.
Is that correct or the process is absolutely different using XI?
Thanks in advance,
Marta.

Each time you create a Port in the MDM Console directories are created on the server to hold data being exported and imported via the Import Server and the Syndication Server. If you log into your server you can find these directories in a heirarchy similar to this:
/opt/MDM/Distributions/ServerName/Repository/
So for example, a directory for one of your Ports may be:
/opt/MDM/Distributions/MDM_ORA/Material/Inbound/ECC(clientsystem)/In_ECC(portname)/
In that directory you will find several folders. One of which is the Ready folder. That is where the import server looks to find files to import. You can change the settings for the Import Server in its .ini file. This file is probably located in either your /opt/MDM folder or /opt/MDM/bin depending on how the installation was set up. There you can set how frequently you want the import server to check that port directory. If you are on unix you start the import server by navigating to the /opt/MDM/bin directory and running the command:
./mdis
Then check that it's running via command:
ps -ef | grep mdis
If you are on a Windows server you simply have to right click -> start the service in Services panel. Also make sure to check the /Exceptions folder in the port directory (same location as the Ready folder), because if the import fails, a file will show up there and lock the port from further use until that file is removed from the Exceptions folder.
Good luck
Message was edited by:
 Harrison Holland

Import Manager Partitioning/Pivot Question

Similar Messages

Maybe you are looking for