Validation in Import Manager

Hi Experts,
When I create a level 9 heirarchy code via Import Manager without first creating its level 8 code (level 8 code not included in the upload file), the result will be:
- level 9 code will be successfully created with complete details as in the upload file
- level 8 code will automatically created without any details as it is a prerequisite of the level 9 code
To prevent the creation of codes without any details, I want to add a validation in Import Manager so codes will not be created when its higher node does not exist yet (or not included in the same upload file).
Will this be possible?
Thanks in advance.

Hi All,
We are uploading new hierarchy via XML file in Import Manager. please see sample below for only one level 8 code (441639A56B104C3) with complete details.
<?xml version="1.0" encoding="UTF-8" ?>
- <dataroot xmlns:od="urn:schemas-microsoft-com:officedata" generated="2010-12-23T11:09:08">
- <Hierarchy_x0020_Template>
<PH_x0020_Code>441639A56B104C3</PH_x0020_Code>
<Level>8</Level>
<PH_x0020_Description>Hazeline COOLING ANTI ACNE FACIAL FOAM</PH_x0020_Description>
<Path>4\44\4416\441639\441639A56\441639A56B1\441639A56B104\441639A56B104C3</Path>
</Hierarchy_x0020_Template>
If the higher level - level 7 code 441639A56B104 is not yet existing in data manager and the level 8 code above was uploaded in import manager, the result will be -->
- level 8 code will be successfully created with complete details as per the upload file..
- level 7 code which is not yet existing and not included in the upload file will be automatically created because it is the prerequisite of the level 8 code. but since it is not included in the upload file, it will be created without details (DESCRIPTION, LEVEL NUMBER).
I just want to ask if some validation is possible to be set-up in import manager that will check if the higher level nodes are not yet existing in Data manager or not included in the upload file so it will not proceed loading the lower level nodes.
Please note that if both level 7 and 8 are included in the upload file, they must be created both successfully.
Thanks!

Similar Messages

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

Help using workflow for import manager

hi all,
assumes import server is used for automation creation/update of records,
i need to design a workflow to verify existing record that:
if a validation pass: update all fields + update mapping key
if a validation fail : update mapping key only
can anyone provide good suggestion on how it can be done via workflow?
MDM API is out of scope...
thanks,
Shanti

Hello Shanti
Import manager and import server launch workflow after data loading is finished.
You cannot manage loading rules from workflow.
You can create two inbound ports:
one for keys loading
another one for keys+fileds loading
Regards
Kanstantsin Chernichenka

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 save Vs Save & Update

Hi all,
I am getting this message when I use Import Server .
515 2008/09/03 11:42:30.091 Some portions of this import map are out of date.
Solution: Please, Launch the Import Manager GUI, preferably using the original source file that the map was generated for, otherwise the same source file and Save Update [File->Save Update] the map.
And when I do the action suggested, it does solve the problem.
My question here is why is this even happening, i use Import manager for the same data file, I am using Save rather than save & Update. So is that causing this problem??
Thanks,
really appreciate any thoughts.
Sudhir

Hi Sudhir,
This problem usually occurs because the XML source that gives the structural error when importing, contains an element which had not been part of the original XML that was used for generation of the original map. Since this element is not defined as mandatory in the XSD the Import Manager could open it with no schema conflict. But since the source file contains a new element the Save Update option must be applied to add this new element to the map definition.
There are two ways to overcome this issue:
1. To create an input file which contains all the elements and use this to create the map (you do not need to run the actual import, it is sufficient just to save the map after mapping all the required fields.
2. Open the Import Manager GUI and choose a number of files together (the more files you open, the better your map will be).Map all the required fields and values and then use the "Save Update" option to save your changes. Open Console and update the same map for the ports also. Doing this it wont ask for save update for the this element again
You should now be able to import all of the files as well as other files that do not have new unmapped elements. The XML files are valid against the schema and the Server is looking for the mapping not for correctness of the schema.
I hope I am able to help you
Thanks & Regards
Dilmit Chadha

Automap Lookup values in Import Manager

Hi,
I have lookup field in main table for country code. In import map I can do automap and then can run the import. But when the new data comes in, new valid country code values are not automatically mapped. I have to click on automap again. I have looked at MDIS default unmapped handling options and do find any that will cover this scenario. This is a very basic scenario, I think I missing something here on how to set this automap feature for future imports. Any help would be appreciated.
Regards,
Imran Zafar

Hi Imran,
For automatic Value mapping, you have options in the MDIS.ini
Please refer to the Page no-12 of this link doc:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/8973bcaf-0801-0010-b7a7-f6af6b1df00e
Also, there are few configuration options for Value Automapping in the Import Manager config options. You can go through the Link below
http://help.sap.com/saphelp_mdm550/helpdata/en/43/12036df94c3e92e10000000a1553f6/frameset.htm
Go to MDM Import Server. MDIS Configuration->Trouble Shooting
Now, after doing the basic settings, Also, there can still be problems. I had faced a similar issues while importing a file and the Automap feature did not work fine.
You can use Import Manager-> File->Save Update for an Import Map. This will save all the updates you make to the map.
After save Updates, try importing a file and check whether the values are getting Auto mapped.
Hoep this info helps.
Thanks & 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.

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.

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

Not able to Populate Qualified Table in Import Manager

Hi,
I am performing following steps for populating Bank Detail Qualified table in MDM from R3 but not able to populate the data.
1.Populating all lookup tables like Account_no,Bank-Key.......
2.Mapping all fields in Bank detail table except the 'Collect Auth'
field which is Qualifier
3.In Customer table(Main) mapping Collect auth to Bank Detail field and
customer_no to its corresponding ID.
It is not populating the Bank detail data which are available in lookup tables
Appreciate your suggestion
-regards,
reo

Reo
Matching will be based on the Display field (at least one) of the Main table. This is for example the Customer Number.
You also need to map all the display fields of the qualified lookup table. Then you can set the Qualified Update Action by right clicking on the field in the main that is linked to the qualified lookup.(the Collection_Authorization I think). Set the option that well update/append/replace the qualified data fields of the looked table.
There is two how_to_guides that will help. You can download from SAP Service Market Place. (Otherwise I can email to you)
How To Troubleshoot MDM Import Manager
HowTo_LoadQualifiedFields
Rgs
Con

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

Validation in Import Manager

Similar Messages

Maybe you are looking for