Delimiter in Import Manager

We have upgraded to:
MDM Version 5.5 SP6, 5.5.62.33
Before this patch was loaded we used Text delimted with tab delimiter (\t) in the Import Manager for uploading of records.
After the patch update the text delimited file can be used with the tab (\t) as delimiter. When the file is read however it is read without any delimiter and is imported as a string.
I have tried to change to comma delimited ( with no luck ( error).
Anyone that came accross this problem, please advise.
Interesting enough is that the MDIS system still works fine.
Thanks for any imput
CHris

Thanks Jitesh,
I'am having problems adding links, so i resorted to pasting the File.
Its a plain text file, no funnies. copy and paste to notepad.
Let me know if this does not work.
Unique_ID Item_Status Long_Description Short_Description Product_ID Contract_Indicator Catalogue_ID External_Manufacturer Manufacturer_Part_Number Product_Group Original_SAP_Material_Number General_Purpose_ID General_Purpose_XREF UOM Compressed_Part_Number Catalogue_Type Stock_Indicator Price_Unit Currency Price PBQ_UOM SOURCE Source_Status
433174120 ACTIVE SHIM 5 SET SP032.107 BREDEL SP32 SHIM 5 SET SP032.107 BREDEL SP32 433174120 Y N ROTARY PUMP, 433 433174120 each, EA X 1 ZAR 325.55 each, EA 1, SWA0, Supply Chain Bafokeng Rasimone, SWA0 ACTIVE

Similar Messages

Tab delimiter notepad to upload in import manager

Hi,
How to upload a text file which is tab delimited in Import manager in MDM 7.1.Please provide me the steps.Thanks in advance.

Hi Chinnu,
Its nice to know that you could import the data!!
For syndication, since you are sending it to ECC, you need to have a xsd which will define the structure of your destination side.
You need to define the xsd in Console in the table XML Schemas
Connect to syndicator
File -> New
Select the XSD you declared here
Next -.> Map the fields and save the map
Then, syndicate.
You can have the scenario: MDM -> PI-> ECC
Refer this link for step by step procedure: /people/harrison.holland5/blog/2006/11/27/mdm-syndication
Please refer the below links for complete understanding of the scenarios:
http://help.sap.com/saphelp_nwmdm71/helpdata/en/42/c89fc0c84e136ce10000000a1553f7/frameset.htm
http://help.sap.com/saphelp_nwmdm71/helpdata/en/43/1346e6ca856f40e10000000a422035/frameset.htm
http://help.sap.com/saphelp_nwmdm71/helpdata/en/5c/73b2429da4c511e10000000a1550b0/frameset.htm
Thanks,
Priti

Importing text file (delimited, fixed width) with MDM Import Manager?

Hello all,
According to the overview section of the import manager reference guide, it is possible to import from delimited text files (e.g. CSV).
But when it comes to the details, text files are not mentioned anymore. I also found no option in the Import Manager.
Could you tell me whether this is possible and - if it is - how?
Thanks in advance!
Kind regards,
Dennis

Hi Dennis,
In order to import flat files into MDM do the following. This solution is specific to MS Windows:
I. Set up ODBC for *.txt or *.csv files
1. Open Data Sources (ODBC) interface:
Start> Settings> Control Panel--> Administrative Tools -->Data Sources (ODBC).
2. Select System DSN Tab in Data Sources (ODBC) interface.
3. Click on [Add]. Select the Microsoft Text Driver. Click Finish.
4. Write a Data Source Name
5. Uncheck Use Current Directory to enable the [Select Directory] button.
6. Click on [Select directory] to determine the source directory.
7. Select the source file.
8. Click [OK] and return to the ODBC Text Setup screen.
9. Click [OK].
10. Return to the ODBC Data Source Administrator dialog and click [OK].
II. Importing from Flat file
1. Run MDM Import Manager.
2. Select ODBC from the Type drop-down field of the Connect To Source dialog.
3. Enter the DSN name from the Setup ODBC Connection dialog above.
4. Select the file name with extension (.csv or .txt) in the Tables panel of MDM Import Manager and the file content in the Records panel.
Hope this solved your problem.Please mark helpful answers
Regards,
Santosh.

Import Manager Delimiter Issue "|

Hi,
We are facing a issue in during Import...We are loading Pipe Delimited file. Whenever we get "after |(Pipe) MDM is throwing an exception stating that 'Number of field values does not match the field columns'...Please let me know any body faced these kind of issues and solution. The format used here is UTF-8...
Example : |TEST123"EEE|TEST|A| - Here " comes after the Pipe and MDM Import Manager Accepting
|"TEST123 EEE|TEST|A| - MDM Import Manager is throwing an error stating that 'Number of field values does not match the field columns' because " comes immediately after pipe....
Thanks
Ganesh Kotti

Ganesh, please see [Note 1346052 - Connecting to source Import Manager error message|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1346052].
The " has special meanings in import manager and can only be used in pairs. If the first character of a field is a ", then there has to be another one in the same field. Or you can remove it alltogether.

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

What is meant by criteria of Updateability in MDM Import manager

Hi,
What is meant by criteria of Updateability in MDM Import manager? i read some information, but i could understand, it says original data source be updateble. what is meant by Original data source.?
what is the use of option "Read-only" in Import manager logon screen.
Thanks

Hello Ankam,
You can check the Read-only option to prevent MDM from updating your data source.
Kindly see the below information on "DATA SOURCE UPDATES"
DATA SOURCE UPDATES
Some MDM Import Manager operations require that the original data source be updateable, thereby allowing new fields and/or entire new tables u2013 and the corresponding data values for each record u2013 to be automatically added to the data source before further processing.
Other operations simply create virtual fields in the MDM Import Manageru2019s workspace, although if the data source happens to be updateable, some of these operations instead add the new fields to the original data source as well.
NOTE ►► Updating the data source when possible allows you to
perform additional operations on the new fields as if they were part of
the original source data, and also use them as record matching fields.
NOTE ►► Fields that are added only if the data source is updateable
can be deleted automatically by the MDM Import Manager when you
exit or switch data sources based on the setting of the Delete Created
Fields on Exit configuration option.
Updateable Data Sources
Whether or not a data source is updateable depends upon the following:
u2022 Source type. The source Type must permit the MDM Import Manager to update its schema and insert the additional fields of data; some supported types are updateable and some are not.
u2022 Media. The media on which the data source resides must itself be updateable. If the media on which the data source resides is readonly, such as a CD-ROM, the data source cannot be updated.
u2022 Permissions. You must have the proper file system permissions to update the file, or the proper DBMS permissions to update the schema of the database.
u2022 Read-only option. You cannot have checked the Read-Only option, which prevents MDM from updating the data source even if the other conditions would otherwise permit it.
NOTE ►► The Read-Only option is: (1) enabled for source types that
can be updated (Access, Oracle, SQL Server, and XML); (2) disabled
and unchecked for those that use Access as an updateable staging
area (Delimited Text and Fixed Text); and (3) disabled and checked for
those that cannot be updated (Excel and ODBC).
NOTE ►► When the data source is SQL Server, the table names in
the database must not contain spaces; otherwise any operation that
would update the data source will fail.
Hope this helps.
Regards,
Vikas

Differences between various source files in mdm import manager

Hi,
Can anyone tell me the differences between the source files(access,xml,xml schema,excel) available in mdm import manager?
Thanks and regards,
Rithesh
Edited by: rithesh_shet on Mar 30, 2010 1:04 PM

Hi Ritesh,
MDM Import Manager provides flexibility to Import Data from different types of Sources into MDM.
You can import data into MDM from below mentioned sources using Import Manager:
1. From Files (Access, Delimited Text, Excel, Fixed Text, XML and XML Schema)
2. Directly from Data base source (SQL server and oracle)
As mentioned by Mandeep, XML Schema is something which you define in MDM console in advance. and then later select the Data source XML file and XML schema from drop down list (it will show all schema defined in console ) to validate XML source file against the XML schema.
For automated Import, Ports are used. Ports are nothing but a logical point of contact with other systems i.e. other systems or middleware will drop file on the port for authomatic import and MDM import server will scan the port directory and if file is present then will import data automatically from file into MDM using a predefine Import Map. (this map needs to be defined manually in import manager and then assigned to port using console).
Please check page no 45 of import manager reference guide for more details about various source properties of Import Manager. (*link for import manager reference guide is already provided on the earlier post)
Also check, page no 53 to 64 for how to import process. Kindly revert if you have any query.
Regards,
Shiv

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

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

Brief about Console, data manager and Import manager

Hi,
Iam new to MDM we just started installing our MDM components and iam a MM functional guy Can you any one tell me about console, data manager and import manger i need to know the following,
1. what is it
2. How the 3 is interlinked
3. can the data manager be loaded directly without a import
4. is there a std way of creating repository
5. I need to do samples on vendor, customer harmonisation and the spend analysis and matl master harmonisation..
Iam asking too much in this forum but i knw you guys are there to help me out.
Thanks in advance,
Suresh

MDM Console
The MDM Console allows the system manager to administer and monitor the MDM Server, and to create, maintain the structure of, and control access to the MDM repositories themselves. Records are not entered or managed with the MDM Console, but rather with client apps such as the MDM Client.
MDM Client(data manager)
The MDM Client is the primary client of the MDM Server, and is the program most users see on their PCs. It allows users to store, manage and update master data consisting of text, images, and other rich content, and to create taxonomies, families, and relationships. Other clients include the Import Manager, the Image Manager, and the Syndicator.
Import Manager
Allows you to import master data from most types of flat or relational electronic
source files (e.g. Excel, delimited text, SQL, XML, and any ODBC-compliant source),
and to restructure, cleanse, and normalize master data as part of the import process.
2. How the 3 is interlinked
--->
Suppose you are sending vendor information to MDM repository be sending IDOC from R/3. Then the whole process can go as... IDOC will be sent to XI, so XI will generate XML file that contains data. Then import manager can import this file and will so place the data in repository.
Now if you want to send data in MDM repository, the process goes reverse way. Syndicator will generate flat/xml file. This file will be given to XI so that XI will generate IDOC out of it and will send it to XI. This whole process ensures data consistancy
For details refer this link
http://help.sap.com/saphelp_mdm550/helpdata/en/43/D7AED5058201B4E10000000A11466F/frameset.htm

Relationship import | Import manager

Hi ,
I am trying to import relationships through import manager in the material repository . What I do is , there are some existing relationships that I created in the data manager . I export them first [ data manager > relationships > export to a file ] to a file and then make changes to the existing file . I use the same file to import relationships but this time with the import manager . I have the following column names in my ".TXT" file ...
1) material numbe <name of the relationship defined in the console>
2) material number <>
3) quantity
I can successfully map the fields and then when I choose the import action it gives me the following error ...
Import failed. Field not found.
Import action: NoneSource record no: 8
there is no record in my file actually at number 8 . I removed the last "Enter" from the file and then imported it but with same results . I exported the existing relationships to an excel file and then tried to import it through the import manager but with the same result .
To verify if there is a problem with the file I use the same file to import the relationships through data manager [relationships > import from file > name of the relationship defined in the console ] and I am able to successfully import it .
What do you guys think is the problem ??
Regards
Deepak Singh

Hi Deepak,
I had performed the following steps and it worked perfectly fine.
Just go through them once and check that you have did the same.
1. Export Relationship using Data Manager -> Relationships -> Export to File.[There is only Display Field i.e. Material]
2. Imported the same text file with Type="Delimited Text" and Delimiter="\t"
3. Select the Relationship table from the Destination drop down list.
4. Map the Parent Material with the Material[Parent] and Child with Material[Child].Also Quantity with the qualifier Quantity.
5. Execute the import.
Note : Please dont make any changes to the Text file and try importing.
Regards,
Jitesh Talreja
Edited by: Jitesh Talreja on Apr 10, 2008 7:25 AM

Comma Delimited - MDM Import Server

when processing a comma delimited file using Import Server, the data contains commas but enclosed within double quotes ( "test, test"). can Import Server recognize the double quotes and not split the data into multiple fields because of the comma?
regards,
Jarred Alford

If you're using CSV-format, each delimiter sign will also interpreted as a delimiter, putting something in "" doesn't help here. Therefore you've to be very cautious and make sure, these chars are really only used as a delimiter, otherwise your content gets mixed up totally. You can see this pretty good, when calling Import Manager with such a file. in the preview you can see, what the system did with your files.
Best would probably be to choose a different delimiter.
Regards Klaus

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.

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.

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

Delimiter in Import Manager

Similar Messages

Maybe you are looking for