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.

Similar Messages

Import Manager Performance Issue

A data load that once took 10 minutes to run is now taking more than 2 hours! What could have happened? This change in run time has occurred in the last week after we've been loading data constantly over the past year! The results are the same whether running the import on a workstation or directly on the server. I've tried the following without changing the results:
1. Rebooted Server (MDM and SQL server on the same machine)
2. Updated Indices
3. Archived repository, deleted repository, rebooted server and unarchived repository. I was hoping that reloading the database would correct an indexing problem.
Here is the system's statistics:
- MDM 5.5 SP3 5.5.28.88
- Repository Size: 8GB
- Contains about 180k products with JPG images
I have opened a Marketplace message on this issue - #337011.
Any suggestions beyond what I've already tried would be appreciated.
Much Thanks!
Travis

Arun,
We are using "Update (All Mapped fields)"
This scenario had 96 mapped fields and 24 rows of data being loaded.
thanks!
Travis

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.

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

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

Import Manager Issue

Hi,
I have a bunch of records which have similarities in the description field of the source file and I need to consolidate all such records and add a separate ID to all such records in a different field. Example data is like this.
1 Rajani Kumar
2 Roman Rytov
3 Rytov Roman
4 Rytov R
5 Kumar Rajani
Here,1&5 represent the same Record for Rajani Kumar
and 2,3 & 4 represent same record for Roman Rytov.
So, I need to give an Id into a different destination field - A for Rajani Kumar(that is for 1&5 records)and B for Roman Rytov (that is for 2,3 &4 records).
Any solutions for this scenario while importing the records using Import Manager? Which is the best method ??
Regards,
RK

The process your are describing is a de-duplication process. For this exercise you need first to define a matching strategy and then implement this in MDM 5.5. This concepts has been demonstrated in a similar scenario identifying duplicate customers. Since this is rather extensive example I will only describe the highlights of what was done.
Based on the customer definition, a set of matching strategies was defined, each representing a specific matching scenario (e.g. one such strategy is: a matching consisting of : VAT number + Street + Name + Postal Code fields is assigned a Match Rage of 100, Match Group = Vat Number and Match Type = Matched.) Each element was initially assumed a weight (e.g. Vat Number = 34 ,street = 14 etc..) and the criteria was set to match results > 60 to be Match, result between 30 and 60 to Dubious and result <30 as Not matched.
For each of the above strategies a specific map was constructed based on the corresponding matching criteria per each strategy. Once these maps configured, the records for the de-duplication process are imported with this import only updating pre-defined fields for each of suspect matched records recording the Match Rate, Match Group and Match Type.
Once completed (all imports run ) you can see the MDM client all the matched records and group/sort them by Match type and grouping finally if you wish , merging the duplicate records while maintain their remote key information.
Kevin

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.

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.

Value Mapping in Import Manager

Hi All,
I have Probelm while loading data to MAIN TABLE through Import manager,I am getting XML file from Legacy System in which legacy sends State Code like NM (for New Mexico) .In my region table I made Name and Code as display field .Created my Import map ,when ever new value comes for region value mapping is not working ,I tried changing my region table with code only display field it works ,but I want Name also display field .
Note : all my lookup table Remote key mapping Enabled
Is there any way we can acheive this or am I missing some thing here .
Thanks,
Madhu

Hi Madhu,
to achive this:
1. First go to the table where you are maintaining the region codes.
2. Enter the region code there and then go to the import manager by connecting to the source file.
3. go the region field map by opening the map.
4. go to value mapping pane and select unmap.
5. then select Automap and check the that your region code added manually is mapped with the source file.
6. You may see some unmapped source values, map it to Null values at destination.
7. Save the map.
8. This shoul enable the import for you.
if you want to avoid the manual mapping everytime, you should be getting all the region codes once and import/update it in the data manager as a one time job.
Then you avoid steps 1 to 3 everytime and carry out the remaining steps to import the records.
Hope this helps resolve the issue.
Thanks
Rahul

How to map Boolean Types in Import Manager

Hi,
I have a issue in Import Manager for mapping Boolean Types.
I have a field which has a single KEY and multilple values(for different languages).
I want to map it to a field in a Tuple.
I can map the Key to field name.
But the values, I am not able to map. Could you help me here please.
Thanks a lot in advance.
Regards,
Rashmi

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

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

Truncate / Trim and Convert the values while importing in Import Manager

Hi,
I am facing the following issues while importing the values in Import Manager.
1) The incoming value is a 4 character text value (e.g. D004) and i need to truncate the 1st two characters so that i get the output as "04" and map it to the destination numeric 2 character field.
Can any1 help me on this as to how can i truncate the 1st two characters?
2) My incoming value is a numeric field which is coming from ECC. this value can be negative as well. the ECC sends this value as (78.00-) ie the minus sign is suffixed to the value but in MDM i need it as (-78.00) ie minus sign prefixed to the value.
Is there any setting in Import manager where i can set the minus sign as a prefix?
Useful answers will be rewarded with points.
Regards,
Roshani

Hi Roshani,
Can any1 help me on this as to how can i truncate the 1st two characters?
As suggested by everyone, none of these options will work. Since your field has alphanumeric Value i.e. D004. Use Option Replace.
After mapping your source field with target field which must be of Type TEXT, Right click on your source field>Set Value Conversion filter>Replace..-->a pop up window will come Replace write Find What: D0 and Replace with: keep it blank(dont write anything) and then Press Ok, you will see all your Source values D0XX converted to XX and then can save in Import Map which will give you the desired result.
If you set your target field of type INTEGER, you cant have option Replace. And the TRUNCATE option as suggested by everyone will not work as Operand 2: you can set as Numeric values only, you would not able to write D.
Is there any setting in Import manager where i can set the minus sign as a prefix?
I dont think this is possible alone with Import Manager, you need MDM workflow for this where your workflow trigger action = Record Import in Data Manager, and need to select the same workflow in configuration options of Import Manager>Import>checkout/workflow = select the workflow name from drop-down which you set in Data Manager and then need to save this in your Import Map. So in this manner whenever record comes through import Manager, these records automatically will go through this Workflow and will give you the desired result.
START(CHECKOUT)>Assign>STOP(CHECKIN)
Assign step where you give assignment on this field and write assignment expression as:
IF(FIND(XXX, "-"), "-"&LEFT(XXX, (LEN(XXX)-1)), XXX)
where XXX = Field name which you defined in MDM repository.
Regards,
Mandeep Saini

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

Letter case in SAP import manager

Hi,
We are facing a strange issue with SAP import manager. we have the value 'n' for a field in XML file. when we tried to open the XML file through import manager, in map/value fields tab, the value is showing up as 'N' for that field where as it is correctly showing up as 'n' for that field in source preview tab. In the XML file, we have the values 'o', 'e', 'n' for that field. The remaining letters are showing up correctly in map/value fields tab and we are facing issue with letter 'n'.
Could you please assist on this. Any help is greatly appreciated.
Thanks & Regards,
Pradeep Kumar

Hi Pradeep,
Can you check whether any value converstion filter (Replace) is set for that particulat field where you are getting this error. if so just choose none for value converstion to source field,save map updates and reload the xml file.
for eg: by using replace command the values can be changed.
Thank you
Rahul

MDM Import Manager Batch

Hi everyone,
We are using the MDM Import Manager Batch to import data automatically. Can we write in our ImportBatch.ini the file name with * at the end : CREMDM.CREMDM04*.xml
because the file name comes with time stamp (CREMDM.CREMDM0420061129-103959-602.xml)
[Source]
Type=XML Schema
XML Schema=CREMDM04
File name= \...\... CREMDM.CREMDM04*.xml
DSN=
DBMS Server=
Database=
User=admin
In advance thanks,
Aklilu

Hi Aklilu,
the names of the XML files don't matter. MDIS tries to process everthing that is put into the ready folder. The ready folder is processed in a "first comes, first served" way. So there's no need to change the names. Is the time stamp in the file name really a problem? If yes, why?
> We are trying to parameter the mdis.ini and until now it does not work.
Could you specify this? In addition, I've got a few hints:
MDIS has to have the same build version as the MDM Server. In addition, MDIS has to be running (in Windows, you can check this in the Services Screen). Furthermore you should have a look at the Console's port definition (select your repository, go to Admin -> Ports in the menu tree). The port has to be configured correctly (XML Scheme, which map to be used, and so on). Very important: you have to set the port to automatic processing.
Here's a sample for the MDIS.ini:
[GLOBAL]
Version=5540
Server=WDFD00146633A
Interval=30
Automap Unmapped Value=True
Unmapped Value Handling=Add
Always Use Unmapped Value Handling=False
VXR_MAX=25000
Verbose=0xFFFF
-- Verbose OFF:     0x0000
-- Verbose ON:      0xFFFF
-- FI Verbose:     0x0001
-- XML Verbose:     0x0002
-- MAP Verbose:     0x0004
-- THRD Verbose:    0x0008
-- PARSER Verbose: 0x0010
-- STRUCTX Verbose: 0x0020
-- VALUEX Verbose: 0x0040
-- IMPORTX Verbose: 0x0080
String Resource Dir=C:PROGRA~1SAPMDM~1.5IMPORT~2LangStrings
Log Dir=Logs
SLD Registration=False
[SP04_BUSINESS_PARTNERWDFD00143366AMSQL_21_13_4_3]
Login=Admin
Password=
Chunk Size=50000
No. Of Chunks Proccessed In Parallel=5
Using the Verbose parameter you can define which errors, issues, messages and so on should be written into the MDIS log. You can find the logs directly in the port's log folder and in the log folder of your MDIS installation directory. If MDIS is not working or the import fails, these files contain some helpful information.
Kind regards
Michael

Import Manager Delimiter Issue "|

Similar Messages

Maybe you are looking for