Skipped items in import manager

Hi,
If i have around 10000 masterdata and in that i impoted around 8000 through import manager and 2000 i skipped as duplicates, Is there a way to check that this 2000 records will there be any way to track this as below,
10000 record recd in import manager
8000 records created
2000 skiped.
Thanks,
Suresh

Import stats are displayed in the Import Status tab of the Import Manager.
Here's what I\ve found at the end of the report:
Import Actions Action # of Source Records
Skip 2000
Create 8000
Update (NULL Fields Only) 0
Update (All Mapped Fields) 0
Replace 0
Delete [destination] 0
Is that what you want?

Similar Messages

Import Substitute and Related Item relationship via Import Manager

Hi! I have been able to import parent/child relationship (captured in an Excel spreadsheet) via the Import Manager. I have tested with BOM and Sales Packages and it worked fine.
However, I now also want to be able to import relationship such as substitutes and related items and found out that this feature is not available in Import Manager. I cannot do this via matching in Data Manager as there is a similarity in the part number used. However, I guess it may be possible if I introduce a new field to somehow link them together.
Has anyone tried to do a mass load of relationships like these before? If so, would appreciate if you can share your experience in this.
Cheers!
SF

Have to import via Data Manager using a text file. It is important to note that there should be no blanks after the last header field and data line.

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.

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

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

Import Manager Join Tables not working

Hi Experts,
for combining tables in the Import Manager i tried to use the join and lookup function.
My easy example is:
Table1
Product ID
Organsation ID
Table2
Organisation ID
Plant
Now I'm joining using the field Organisation ID which contains the same items and make a lookup on the field Plant. In the Source Preview I can see the looked up field but without any values and it is with a grey background.
Any suggestions?
Thanks
Andy

Hi,
I tried this at my end. It seems like a Bug. I am using MDM 7.1 SP3.
Facing same issue, I mean Grey background (not editable) in source preview, when we look-up field Plant from Table1 to Table2.
This field values are seen mapped in Map Fields/Values tab, but when i import data. Fields get populated for Product ID and Organization ID only but Plant field is not getting populated into MDM data Manager.
So, i am quite sure it seems like a Bug and I would Suggest you to Raise OSS note for the same.
Temporarily, You can import data in below manner.
I mean when you select Source table as Table1, you can import Product ID and Organization ID.
After importing Table1, select your Source table as Table2 map both fields Organization Id and Plant.
Import data by selecting Matching Field as Organization ID and Default Import Action as Update (All Mapped Fields).
So, in this way you can have your complete data in your MDM but obviously just because of bug which you can do in Single Step, Now going to be done in two Steps.
Note: For one of Client i did this on MDM 5.5 SP6, that time it was working perfectly.
Thanks and Regards,
Mandeep Saini

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

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

Import Manager problem

Hi All
I would like to ask to help me with very strange problem, I tried to google it but no success.
When I use Importa Manager (ver 7,1 SP5) to import ~ 150 records there is a problem. I choose to upload all record to create, but only one is created. I tried few times to upload and each time it create only one record. I am uploading from Excel.
That is strange, because normally to others repositories I can ulpad a lot more records with no problem.
I never had that problems before.
Thank you for help.
BR
Rafal

1. check the preview tab in the import managerand see how many are shown in there compared to the excel
2. is it showing the correct number of items (in the create / matching ) view of the import manager ??
3. check in data manager if you are opening any named search / mask views to see only 1 record .
click the reset search at the top to see again ?
4.if alls correct , this seems to be some exception which is not thrown - hence raise an OSS with SAP with the archive file and excel uploaded
hth
thanks
-Adrivit

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

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,

Import Manager - Import Parent Child Relationships

I have a parent child relationship set up in console.
Kits / Parts.
Has Required = No
Has Quantity = No
I am trying to import the data for the relationship links using Import Manager.
The source is a Excel file.
Item Number <Kits> Item Number<Parts>
ACC-123 ACC-1234
ACC-123 ACC-555
I mapped the Item Number Kits and Item Number Parts.
When I import, I am getting the following error
Import failed. Failed to find the aggregation record from its field values.
Source record no: 1
I am able to import the same record using Data Manager if the file format is Text.
Any help is appreciated.
Helpful answers will be duly rewarded

The key field that you use to load the relationship must be defined as:
Unique................Yes
Display...............Yes
Multilingual..........No
My problem was that I had defined Model Number as multiligual. When I changed this setting and loaded with Update Indices the load worked.
I have not found anywhere in the literature that talks about this restriction. You can create the relationship in the Console. You can load this type of relationship in Data Manager. You can not however load them in Import Manager.

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

Key Mapping activates Versus Import Manager

Hello,
I have Key mapping activated in the console and Supress Unchaged Records activated in my syndication map.
Case : I import files (suppliers catalogs) to MDM via Import Manager manually. I am not sure about it, but since I activated Key mapping property,
I noticed that for each supplier ID in the Supplier table, a lot of remote keys were created. Previously I only had one remote key for each supplier and now I have a list of other supplier's ID. ( Existent or nonexistent supplier IDs). This becomes an issue for my import, because when I try to import a file where the supplier id does not exist in the MDM ( this scenario used to block my import and this is what a expect, as supplier is a key in my mapping), the system automatically maps that nonexistent supplier to other supplier.
Can you help me to understand if this is caused for the key mapping property ? Any Idea ?
Thank you very much
Luciana.

Hello Stanley,
The remote keys are form the same remote system.
My story is : When I am importing a file , suppose my file has an invalid supplier ID. ( this means this supplier is not in the lookup table Suppliers)
1)The import manager will give me a message such as : Map Supplier ID Values. This behavior was expected.
2)I decided to test the automap. The invalid supplier was not mapped to a different value. I am ok with that.
3)If the user ( dont ask me the reason ;-)) decides to map that invalid supplier ID to a different one, he/she is allowed to do so. I remember when the key mapping was not activated this option did not exist. The map and automap button was deactivated.
What I am trying to make sure is : a remote key will be created for invalid suppliers ONLY if I choose to map it with a different supplier ID.
Do you have any comments about it ?
Thank you very much
Luciana.

Partial match for Value Mapping in Import Manager

Hello Experts,
We have a import map which is used to do mass insert of data into the main table. This is done as & when required by the end user.
We have a qualified lookup field which has a flat lookup filed as the Non-Qualifier. This flat lookup field is refering to a Lookup Flat table, which has mulitple dispay fields like Code,Name, Status etc. (14 fields in total) where as only the Code is the unique field.
We have only the unique field in our source file which we use for the import. Since we have only a part of the display fields in the source, the automap functionality in the Value maping section doesn't work. It becomes very tedious for the user to manually map all the values for this field.
Is there any way by which we can convert the source or target values in the import map, so that we can map the values using the Automap feature?
Your help & suggestion for alternate approach is highly appreciated.
Thanks in advance.
Regards,
Uday
P.S. We are using SAP MDM 5.5 SP6.

Hi Uday,
No need to enable remote key mapping for QLT. Please execute the below steps(stated with an example) -
1. Among all the fields in the referenced lookup table, identify the lookup fields and the tables they are looking up .
For eg.If you have a lookup field as 'Country' as one of the fields, look up table will be 'Countries'
2.For the identified lookup tables, set 'key mapping =Yes' in Console.
For eg, For Country Lookup table ,set Key mapping to 'Yes'
3.Import values into Lookup table (Import manager)/ Remote key update -
In import manager, select source (local file) and destination as Countries flat table.This Table will be haing 2fields - Code and description.Clone the 'Code'field and map it to Remote key field in destination hierarchy.Map code and description to equivalent destination fields. Select 'Code' as matching field > Perform import into lookup table.
Check if the records in countries table are updated with remote keys(in Data manager> right click on a record> select 'Edit key mappings' > view key mapping for the record)
3.Import to Qualified table/Auto value mapping -
Now, in the import map for qualified import , map the source field and destination field (of lookup type), all the values of this field will automatically map.
Similarly, refresh remote keys mappings for all the lookup tables first and then you can see auto mappings of values happening for the lookup fields.
Regards,
Vinay M.S

Skipped items in import manager

Similar Messages

Maybe you are looking for