Import server

Hi All,
Can anyone please send me he link or document on how to get started with Import server.
I even tried in search forum but there are many outcomes and it is bit difficult to find the documents
It will be really helpful if anyone send the link or document
Thanks in advance
Nitin
Edited by: nitin shanbhag on Jul 20, 2011 8:04 AM

Hi Nitin,
As you are aware MDIS is used to automate import.
The help.sap.com provides beautifully arranged information regarding the same including exception handing and troubleshooting too:
http://help.sap.com/saphelp_mdm550/helpdata/en/19/d4301589b54841af17e7c42b4cee49/frameset.htm
The following thread talks about mdis.ini configuration :
mdis.ini
These threads can also be useful:
differ between import manager and import server
MDM Import Server, Automating the Port/Ready
Hope this helps!
Thanks,
Ravi

Similar Messages

Strange Errors from Import Server on Schema-based maps for repeating nodes

I have already posted one thread about this, but perhaps some more in-depth information is required:
We have uploaded our schema into the console, and have mapped the following multi-node file to it:
CUSTOMER <repeating node>
MDM_CUST (new Customer number returned)
CUSTOMER(mapped back from XI for RECORD MATCHING)
CREATE_DATE (text field)
CONTACT<repeating node>
    CONTACT_NO (RECORD MATCHING : NON-QUALIFIER)
    CONTACT_SAP_NO (QUALIFIER)
     [NOTE: There are other qualifers for CONTACT, but only this one
qualifier is being returned and is the only field that would and should be updated.
The other fields should be left alone. However, it appears to overwrite EVERYthing
with NULL other than these two fields. The CONTACT_NO is the sole qualifer on
the table. It is a calculated field that equals the Auto-ID that is also produced on
the table - but obviously not mapped.]
PARTNER<repeating node>
    CUSTOMER_NO (RECORD MATCHING : NON-QUALIFER)
    PARTNER_FUNC (NON-QUALIFIER - Code given to lookup from PARTNER_FUNCTION table which has Code and Desc)
    PARTNER_NO     (NON-QUALIFIER)
    DEFAULT_PARTNER_FLAG (QUALIFIER)
<CLOSE CUSTOMER NODE>
In the Customer main table, all records are matched on CUSTOMER. The CONTACT_NO non-qualifer is matched to the CONTACT qualified lookup table directly since it is the only available non-qualifier. For the PARTNER table, the three qualifiers are mapped and then a compound field is created to map to the PARTNER table entry.
We have the Configurations set at:
Default Multi-Valued Update: Replace
Default Qualified Update: Replace
Default Matching Qualifiers: None
Our record matching is: Create / Update(ALL MAPPED FIELDS) / Update(ALL MAPPED FIELDS)
When the map is reused, the repeating nodes are all recognized, be it one node or many. However, when the map is reused, it does not automatically map the values for many of the Partner fields (nor the compound field) though the fields are correctly mapped.
Also, when we attempt to use Import Server to automate the mapping, we use the mdis.ini set to
Automap Unmapped Value=True
Unmapped Value Handling=Add
Always Use Unmapped Value Handling=False
We get a very strange error saying that :
[code]Encountered a pre-SP4 map. The map needs to be upgraded to SP4.
Solution: Please, Launch the Import Manager GUI using the same source file and simply save the map.[code]
Could it be that our MDM 5.5 SP4 is not compatible with schemas generated with XI v.7 SP9?
All of our MDM is 5.5 SP4. It makes no sense that we would get THIS kind of error. Also, I am questioning our combination of these and other configurations since it doesn't always seem to do what it should

Hi Donald,
this sounds good so far. Just a short hint: you've set "Default Qualified Update: Replace". This explains why Import server "appears to overwrite EVERYthing
with NULL other than these two fields.". The reason is the replace. A replace means that the old values are completely deleted and only the new incoming ones are stored. I'd suggest to use any of the Update possibilities.
Note: the definitions you set in in the record matching step are mainly for the new records in the main table! Records in qualified look ups are handled differently! If you open your map in Import Manager, switch to tab "Map Fields/Values". Select a field that is your non qualifier. Right-Click on it and choose "Set qualified update" from the context menu. Now you can define which qualifiers can be used for the qualified look up matching. And you can define as well what should happen with new and/or existing records.
Regarding the value mapping: do you use keymapping? Or do you use simple values only? Do you save the map everytime you add a new value mapping?
Regarding the issue "Encountered a pre-SP4 map. The map needs to be upgraded to SP4. Solution: Please, Launch the Import Manager GUI using the same source file and simply save the map". This sounds very likely like a bug in MDIS and should be reported to SAP!
Hope that helps
Michael

Value Exception in Import server

Hi Experts,
My requirement is i have 100 files in the ready folder while processing first file through import server, it got value exception which i fixed manually through import manager port option and saved map as update. But even after the files which are having records with same values also moving to Value exception. Can you please me help me out to fix it.
Thanks
Narendra

Hi Mullapudi Narendra,
Value exception only come when any new value occurs in you lookup table so avoid this in importmanager configuration setting require to set MDIS parameter
in MDIS Add / Map / fail and ignore detail as follows
Add : value at destination side doesn't exist then this value get added to your lookup table as well as update this value at record. add new value at lookup subtable and update record at main table
Map : value will only map which are exist at destination side. update records at main table
Fail : if any new value occurs which is not exist at destination will not allowed to import this record as well as lookup field value.
entire record will get fail and doesnot import lookup subtable and maintable
Ignore : if any new value occurs which is not exist at destination will ignore this value and remaining data will get import except lookup field which contain new value .only value will ingore at lookup subtable and maintable for respective field, other field data of file will import
Thanks,
Jignesh Patel

Import Server not picking up the file

Hello,
I have 2 repositories running on the same server. Import server picks up file for one repository, but not for the other. What could be the reason? Also, for the repository, import server not picking up the file, workflow also does not send an email notification.
Please help
Subhash

Hi Subhash,
Hope you are not using the same Import Server for both the MDM Servers. If yes then you need to mention the MDM Sevrer name in the MDM Server parameter of MDIS.ini. Check the parameter list of MDIS.ini file.
If your repository has password for Admin user then you need to specify the same in MDIS.ini file under your repository section for User = Admin and Passowrd = [Admin password]. Remove the E from the PAsswordE and give the password for Admin user. Once done restart the Import Server and check again, parameter Password would have converted to PasswordE.
For Email Notification two things you need to check:
1. You should have specified the mail server address in MDS.ini file under your repository section for parameter Mail Server.
2. Workflow owner should have entry in Email address field of the user. Check this in Console under Admin -> Users.
Regards,
Jitesh Talreja

Map including spliting operation dosen't work in MDM Import Server

Hi All,
I met a problem with MDM Import Server when using a map file with spliting operation in it, although I can use it in MDM import manager to load data successfully. The error in log file is like this:
Record Matching...
Importing Lookup...
One or more attribute values are invalid.
One or more attribute values are invalid.
One or more attribute values are invalid.
One or more attribute values are invalid.
Import Failed!
The spliting in my map is: I split field "Category" into category1 and category2 with space " ". e.g. value "Trousers M" is splitted into "Trousers" and "M" . Then I map category1 to category and category2 to size.
I tried to delete this spliting and just map "Category" to "Category" then it works well for Import Server.
Is it the bug of MDM import server? can anyone give me a explaination?
Thanks! Bin

Under Configuration Options of the Import Manager,
check the values for
<b>Default Batch Handling</b>
AutoMap Unmapped Values = Yes
Unmapped value Handling = Add/Ignore/Fail.
Set the values according to your needs.
Make sure that the data source is updatable as well.

Import Server issues with SP4 maps

While using the Import Server, I have a newly created map using Import Mgr 5.5 SP4. (I used a schema created by XI v.7 SP9). When it runs, it throw and exception with the following error message:
<b>"Encountered a pre-SP4 map. The map needs to be upgraded to SP4.
Solution: Please, Launch the Import Manager GUI using the same source file and simply save the map"</b>
It appears to not like new entries on the Partners table and balks at auto-mapping values for the compound field for the qualified lookup table at the Customer main level. The input record is outlined below. I have set the CONFIGURATIONS to "Replace/Replace/None" and "Automap values in batch" and in the map they are set to "Create/Update (ALL MAPPED)/Update (ALL MAPPED)".
Thanks in advance. Don
<?xml version="1.0" encoding="UTF-8" ?>
- <ns1:CustomerCreateResponseTest xmlns:ns1="urn:bp:xi:up:re:cust_mdm:cmdm:pr5:100">
- <CUSTOMER>
- <item>
     <CUSTOMERNO>0099999989</CUSTOMERNO>
     <MDMCUSTOMER>4539</MDMCUSTOMER>
     <CREATE_DATE>16/01/2007,09:39:30</CREATE_DATE>
   - <RETURN>
      <TYPE>E</TYPE>
      <MESSAGE>F2381 MESSAGE</MESSAGE>
     </RETURN>
   - <PT_CONTPART_RETURN>                    qualified lookup table
    - <item>
        <MDM_CONTACT>0000000002</MDM_CONTACT>           non-qualifier
        <CONTACT>0002111119</CONTACT>                qualifier
      </item>
     </PT_CONTPART_RETURN>
   - <PARTNERS>                              qualified lookup table
    - <item>
       <CUSTOMERNO>0099999989</CUSTOMERNO>           non-qualifer
       <PARTNER_FUNCTION>RE</PARTNER_FUNCTION>          non-qualifer
       <PARTNER_NUMBER>0090098989</PARTNER_NUMBER>      non-qualifer
       <DEFAULT_PARTNER>X</DEFAULT_PARTNER>           qualifier
      </item>
     </PARTNERS>
    </item>
   </CUSTOMER>
</ns1:CustomerCreateResponseTest>

For all watching this thread:
We were running MDM 5.5 SP4. We applied Patch 2 (not patch 3) to our 32-bit system and we no longer get this error. We now get an error that the "Source File does not conform to the XML Schema", an entirely new issue. I will open a new question regarding that.
Thank you. Don

MDM Import Server after error in import file

We setup Import Server and it processed a few files. then we tested what happens when there is an error. it logged a file to LOG folder. but would not start picking up new files we dropped in the READY folder. We removed the file with an error but still nothing; we fixed the error and put the file back and still nothing; we stopped and restarted the server, reposititory and import server but still nothing. Any ideas how we "reset" import server so it will start to process files again ? thanks

Hi Jay
I have faced the similar problem; have done some turn around to make things work, it may not be permanent solution. I have cleared the folders LOG,EXCEPTION(StructuralX), STATUS by copying the files to someother location for future reference and it worked.
Please feel free to revert to me for further clarifications.
thanks
Alexander
Note:Please mark the helpful answers.

Import Server - Error in connecting Import Server

hi Team,
One of our business application integrated with MDM getting error as "Error in connection Import Server".
As i checked all the repositories and they are all active/online.
Please advise what all the place/items to cross very and take necessary actions accordingly.
Thanks
Sekhar

Hi Sekhar,
Go to Services.msc in the system where your MDM servers are installed and restart the MDM Import server service.
Then try connecting again.
Your error message basiaclly points out that you are using Automatic import but as your MDIS server is not up and running the importing cannot be performed.
So make sure your MDIS is functioning properly and you have made the necessary settings in your MDIS.ini file and port property in console for correct importing.
You can check the mdis settings needed in the below path:
http://help.sap.com/saphelp_mdm550/helpdata/en/43/12036df94c3e92e10000000a1553f6/frameset.htm
(Automatic importing MDIS - Import manager ref guide>MDM import server(MDIS)>MDIS Consfiguration)
The port in MDM Console must have processing type as Automatic and the correct map attached.
Hope It Helped
Thanks & Regards
Simona Pinto

Import server - Structural exception

Hi All,
I configured all the necessary setting required for Import server.I manually placed the file in Ready folder.The file gets processed but goes and sit in exception folder under structural folder.
I tried the same file using Import manager and and dot loaded in DM without any error.I checked all the fields and structure but unable to find the solution.
I am getting the following error showing some timestamp.There are no fields in may main table using timestamp .our design has only literal date and time in tuple.Is this something to do with this?
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <File>
<ExceptionSubFolder>E:\usr\sap\MD1\MDS00\exe\Distributions\HYDHTC100401D_MSQL\Sachin\Inbound\MDM\MRH2_MAP_AUTO\Exception\StructuralX\</ExceptionSubFolder>
<Name>20110721084955_S_MRH2_Customer_Master_Data.xls</Name>
<ExceptionType>StructuralX</ExceptionType>
<TimeStamp>20110721084955_S</TimeStamp>
</File>
Can any one help me in this ?
Thanks and Regards
Nitin

Hi,
Thanks for the help.
I clicked on the below link.But please clarify which one to download from below.Which one from below contains xsd.exe
What is xsd.exe used for.Is it some kind of tool to create xml files.Please need some information.Because if it is a tool i am using Altova XML spy for the same
Download .NET Framework 2.0 SDK x86 version (354 MB)
Download .NET Framework 2.0 SP2 (52 MB )
Thanks and Regards
Nitin
Edited by: nitin shanbhag on Jul 25, 2011 5:23 AM

Import Server not working

Hi ,
I have a scenario where PI is sending data to MDM inbound port which is automaticaly getting imported to MDM .
Now problem is PI is succesfully sending data but file is not coming to Inbond port.
PI side all the configuration is fine .
Through Import amanger its working fine.
Kindly help me out .
Thanks in advance.
Regards,
Neethu Joy

Hi Neethu,
it seems problem at PI level because as you said file not coming in MDM inbound port.
To check MDM import server working or not just put file in MDM inbound port manually and check wether file processing automatically or not.
if PI sending file to to inbound port then you need to check port in MDM console and configuration parameter such as remote system, map , file format, processing time, file aggregation count etc.
Kindly check and revert back.
Thanks,
Jignesh Patel

Configuration of the Import Manager in order to use the Import Server

Hi all,
Firstly thanks a lot for all. The question is: I need to set all the properties neccesary to use the Import Server, so would be very positive to know how to set all the default import action in the import manager. when I try to make that all default import action under the Records Option in the main menu are disable.
Can someone help me with that?.
Thanks in Advance and Best Regards.

Hi Devashish Bharti
All that you have told is configured, instead of this configuration, the default import action: none/none;single/exact is disable in the "Records" main menu. Do you know what happen?
Best Regards.

Question about parsing delimiter file using import server

I am using import server to load comma delimiter file; but some fields contain comma covered by ", like "1GB, 200HZ", import server parses it into "1GB and 200HZ" two fields and it caused whole import process failed.
The same map and same file works in Import manager. I specified , in delimiter field in port table.
Any idea to solve this issue? Thanks.

hi
Try setting the policy for ur applet
All the Best
Kumar.R

"Source file does not conform to XML Schema!" error at Import Server

Dear SDN,
When I run Import Server the import job stopped with the error "Source file does not conform to XML Schema!" in Log file. I used MDM SP05 Patch01 and HF1.
Both of 2 Import Server have same problems. Of course it works in Import Manager.
What do I have to check?
Regards,
Eric

Hi Eric
Just confirm this...
One needs to load XML schema file in MDM and can be done by specifying this file in Port .
Refer this link.
http://help.sap.com/saphelp_mdm550/helpdata/en/fa/69b20ae0ae4b158a3f6d025b3d3847/content.htm
Just make sure that corresponding XSD file is specified in the port
Regards

Import server: Undefined elements exception

Hi,
I do have a problem with the import server. I get ,'save-update map' structural exceptions in the import server. It complains about undefined elements, and if saved the update it works for one single XML file but other still fail with similar (other element though) error. Mapping the files in the import manager just works. We are using version 5.5.41.70 here of all components. I noticed a thread which explains about sp5 patch 01, hotfix 1, which fixes this, but we're having that one already.
I did validate the xml already against the xsd used, the xml is valid.
Error from logfile is:
"Some portions of this import map are out of date.<LF/>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.<LF/> Parent hierarchy: <E1MARAM>.<LF/> Undefined element: <EKWSL>. ".
Thanks,
Wim

Hi Wim,
it looks like that your Import Map does not have all IDoc fields mapped to the corresponding repository fields. If you map the fields in Import Manager and choose the Save->Update option, IM adds the new mapping to the old existing one. But of course it is still possible that there are other unmapped IDoc elements which need to be mapped once manually before the Import Server can process the file automatically. The best way to solve this is creating a "Dummy" IDoc file that contains a value for each and every field. Then use this "Dummy" IDoc in Import Manager, load the Map and check the mappings. You can add/delete mappings according to your expected real data. Save->Update once again and you should not into the issue any longer.
Best regards
Michael

Import Server - Workflow related value exceptions

Hi,
Our Import Server is importing multiple records, one record per file. The inbound port is configured with a file threshold of 5, 50000 chunks and 5 parallel chunks.
We are using a workflow on import to assign values to 2 different fields. In the start step of the workflow the records do not get checked out.
When importing 1000+ records it works great, but a couple of times it runs into value exceptions.
In the log files I can find the following error:
Import failed. Cannot import record with workflow because the record is already checked out
Import action: Update (All Mapped Fields)
Source record no: 16
All MDM components have version 5.5.42.92.
I saw a similar issue in a different thread. Is this fixed in 5.5.42.98?
Thanks & Best Regards,
Ingo

Dear Saurabh,
The record is not checked out in Data Manager at the time the error occurs.
Nobody is checking out records prior and during the whole test run.
5.5.42.98 - I tried this out and get the same errors.
In our project we are still on 5.5.42.92 and won't upgrade until we know that another version is doing better.
There are some functionalities in MDM5.5 SP06 patch 1 that are not working well, for example try out the qualified update (update (new links create, existing links update (all mapped fields), that you can set on field level and you will get some unexpected results. We won't go for SP06 until we are really sure that all issues we experience are fixed.
What else could be the cause for this error?
Thanks & Best Regards,
Ingo

Import Server Error - Value Transformation

Hi,
I have two questions on import server and import map.
1. My source xml does not have company code segment (customer repository), when I opened my xml thru import manager using my import map, I dont see any source fields belong to company code segment, which I think is right. But the same xml when it runs thru import server it throws "Value Transformation" error on fields that belong to company code segment which is not present in the source xml. Any help on this issue is appreciated.
2. In import maps, any new field mapping is saved using "Save update" option, but when I unmap any field, "save update" option does not save it, but "save as" option does save it, but the downside it just saves the current mapping. Any help on this is also appreciated.
Thanks
Job.
Edited by: Job Daniel on Jul 21, 2008 8:44 PM

Hi Sekhar,
Go to Services.msc in the system where your MDM servers are installed and restart the MDM Import server service.
Then try connecting again.
Your error message basiaclly points out that you are using Automatic import but as your MDIS server is not up and running the importing cannot be performed.
So make sure your MDIS is functioning properly and you have made the necessary settings in your MDIS.ini file and port property in console for correct importing.
You can check the mdis settings needed in the below path:
http://help.sap.com/saphelp_mdm550/helpdata/en/43/12036df94c3e92e10000000a1553f6/frameset.htm
(Automatic importing MDIS - Import manager ref guide>MDM import server(MDIS)>MDIS Consfiguration)
The port in MDM Console must have processing type as Automatic and the correct map attached.
Hope It Helped
Thanks & Regards
Simona Pinto

Import server

Similar Messages

Maybe you are looking for