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

Similar Messages

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.

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

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

MDM Import manager data sources

Hi experts,
As far as I know MDM has ETL capabilities with MDM Import/syndicator tools that allows to load and extract data to and from MDM using files and relational databases as source/target.
What different kind of data sources supports MDM Import manager?
When should we work with SAP XI/PI?
When sould we work with ETL (Data Services as Data Integrator)?
Thanks in advance,
Abby
Edited by: Abigail Beurmann on Nov 23, 2011 11:38 AM

Hi Abigail,
So, Could you please tell me if it's a common practice to import data in MDM using files?
for example as you said, We want to import data from R/3 to MDM using XML files that XI/PI generates?
Yes its a common practice to import data in MDM in files.Most common mode of data exchange is xml which has many advantages namely it is accepted open standard,allows to clearly separate content from form (appearance), is text-oriented,is Secure, is extensible,is self-describing, is universal; meaning internationalization is no problem and XML is a future-oriented technology.
In our business scenario, We have a SAP CRM with SQL server 2005 as a source. Could MDM automatically import data directly from SQL Server or it's a better practice to generate XML files with PI using the Import Port/folder?
One should always use a interface as business rules can possibly change and making a later change could be huge ask.
So PI can act a interface between MDM and CRM.
CRM supports Bdoc and PI can integrate with CRM with help of ABAP Proxies.
The following thread provides you in depth information on integration of the 2 systems:
CRM-MDM Integration via XI
To help you understand more about webservice and PI integration with MDM for CRM integration please go though this thread:
SAP PI and Webservices
To know more about PI vs DS please go though this guide:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10fbac70-c381-2d10-afbe-c3902a694eaf?QuickLink=index&overridelayout=true
About Integration with PI:
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/8035bf61-d6b5-2e10-5fa6-e5e00b9e6174&overridelayout=true
A guide which takes you through the entire process of CRM PI MDM integration,although for SAP MDM 5.5 version but valid for most part:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/405a73cc-9068-2c10-859e-c13f81922e7c?QuickLink=index&overridelayout=true
Hope this helps.
Thanks,
Ravi

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

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,

Normalisation of text string on import through import manager

Hi There, we have just uncovered an issue with our workflows where a submitted file that contains 'special' characters in a description field (text string) will cause the jobs to fail. Is there a way i can tweak the normalisation feature in the import manager to remove these special characters, while leaving 'normal' characters (such as spaces, commas and other punctuation) in tact?

Hi Adam,
The failure is happening at the import stage and not the workflow stage ,As your import of records are triggering the workflow action(Trigger action being record Import).The records may not be getting imported rightly and so the workflow failing.
But as far as i know the Text data type in MDM allows special characters entry without much problem.
Try the following:
- Check to see if the charater length of this special characters holding field is sufficiently large it could be the problem that the length of the incoming charaters are more than the length mentioned in the console settings and so truncation of charaters are causing the failure of import.
- Check to see if values of all other fields especially the date and numeric fields if any are holding correct data .
- Lastly if you find out that the special charaters are the only cause of the failure then you will have to perform the normalization of the values and save the settings in the map and then use this saved map.Try to accomodate all the possible charaters faults.You can normalize the Field by right clicking on it and say value conversion filter >Normalize.If your values are lesser you can normalize them at the value level itself using the right click.
Hope It Helped
Thanks & Regards
Simona Pinto

Setting up Custom Priorities for Taxonomy Attributes through Import Manager

Hi,
I want to set priority for "n" number of characteristics through Import Manager.
I know Import manager allows us to set priority to one of the following : "Highest" "High" "Normal" "Low" "Lowest". But I have a requirement to set custom priority for each of the attribute through Import manager so as to avoid manual intervention.
Has anybody worked on this before?
Regards,
Amol.

Hi,
Which special properties you are talking about ?
I will just brief you the concepts of Hierarchy and Taxonomy
Hierarchy
Node1
-    Node11
-   Node12
Node2
-    Node21
--         Node211
Only leaf nodes can be assigned at the time of record creation.
Taxonomy
Used when particular hierarchy nodes needs some extra fields.
Example: If your hierarchy is like
Cars
    - Fiat
    - Maruti
Bikes
    - Hero Honda
    - Bajaj
Now for Cars, i want to store its Price but for Bikes i am not interested in Price but I want the Colour info. Now if you create the Price and Colour as fields of the repository then for all the records whose category is Cars will have NULL value for Colour and reverse in case of Bikes. Hence the concept of Taxonomy is introduced so that you can assign the fields (known as attributes) to the Nodes of the hierarchy.
For Taxonomy Import, refer the below links
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30aa1447-80a1-2a10-e483-a76087bcb12f
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/6090d0bd-1da7-2a10-468f-bdd17badb396
Regards,
Jitesh Talreja

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

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.

MDM Import Manager - remove multiple values from a multi valued fiedl

Hi,
We have this multi-valued field and we would like to clean the values from it.
How can we do this using MDM Import Manager?
Example:
Article A
Field XPTO has values Z, T and P.
We want this field XPTO with no values. How can we do a mass actualization to clean the field for some articles?
Thanks and regards,
Maria

*We have this multi-valued field and we would like to clean the values from it.
How can we do this using MDM Import Manager?
Example:
Article A
Field XPTO has values Z, T and P.
We want this field XPTO with no values. How can we do a mass actualization to clean the field for some articles?*
Hi Maria,
There can be multiple ways to achieve this -
1.After doing field mapping for XPTO you can set conversion filter for each of the values.
2.Value map with NULL.
3.Trigger a Workflow on import/record add,run assignment and make that field NULL.
4.Run mass update for conditional assignment based on that value of XPTO.
There can be more ways,whichever suits you best you can go ahead with that.
Hope it helped
Regards,
Ravi

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.

Special Charecter acceptable in Import manager?

Similar Messages

Maybe you are looking for