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

Similar Messages

Import Server - Multiple Qualified Table - Map Crash

Hello,
Requirement: I need to update multiple qualified table using single source file.
Preparation: I have created a map where mapping to multiple qualified table fields maually.
Have created a Inbound Port using the above map.
Problem: Import server throws an exception; while opening the Import Manager using the Port Option and corresponding Exception; Lot of fields were un-mapped. Looks like Import map crashed.
Please feel free to throw some light reg the same!
Thanks
Alexander

Hi Alexander,
If you are performing multiple qualifier table mapping and importing then you will hav eto create differnt map for each table importing.In that case you will rrquire multiple inbound ports and in each ports deatils you will give the map name pertaining to which qualified lookup table you wish to import.
Actually using automatic importing for lookups is not desirable as the lookups always need to be prepopulated before your main table importing.
The exception taht you are receiving could be due to the reason that the map you are saving is using only one table mapping and so most of the fields are left unmapped.
try not to use automatic importing for Lookup qualifier tables and use manual importing and see if the the exception still comes.
Hope it helps
Kindly reaward points if found useful
Thanks
Simona

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 - 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 - 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

Complex XML - Import Server

Hi,
I have an XML structure as follows:
<Root>
<PartnerNum>123</PartnerNum>
<FName>D</FName>
<Lname>B</LName>
<Address>
<Add1>Address line 111</Add1>
<Add2>Address Line 222</Add2>
<PostCode>Po 1</PostCode>
</Address>
<Address>
<Add1>Address line 333</Add1>
<Add2>Address line 444</Add2>
<PostCode>Po 2</PostCode>
</Address>
</Root>
When I use import manager I can succesfully importby forming Joins (_ID field) between different XML structures... However when I use Import Server exception comes that I cannot use complex structures.
How do I import these kind of structures using Import server?
Regards,
Dev.

Simona,
I am using similar approach - using joins to club multiple segments into one and then using this main one as the source table.
Michael,
Here is the schema as requested:
<?xml version="1.0" encoding="utf-8"?>

<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
 <xs:element name="BusinessPartner">
 <xs:complexType>
 <xs:sequence>
 <xs:element minOccurs="0" maxOccurs="unbounded" name="Partner">
 <xs:complexType>
 <xs:sequence>
 <xs:element minOccurs="0" name="FirstName" type="xs:string" />
 <xs:element minOccurs="0" name="LastName" type="xs:string" />
 <xs:element minOccurs="0" name="PartnerNumber" type="xs:string" />
 <xs:element minOccurs="0" maxOccurs="unbounded" name="Address">
 <xs:complexType>
 <xs:sequence>
 <xs:element minOccurs="0" name="AddressLine1" type="xs:string" />
 <xs:element minOccurs="0" name="AddressLine2" type="xs:string" />
 <xs:element minOccurs="0" name="AddressLine3" type="xs:string" />
 <xs:element minOccurs="0" name="AddressLine4" type="xs:string" />
 <xs:element minOccurs="0" name="PostCode" type="xs:string" />
 <xs:element minOccurs="0" name="DPS" type="xs:string" />
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 <xs:element minOccurs="0" maxOccurs="unbounded" name="ContactDetails">
 <xs:complexType>
 <xs:sequence>
 <xs:element minOccurs="0" name="ContactType" type="xs:string" />
 <xs:element minOccurs="0" name="ContactInfo" type="xs:string" />
 <xs:element minOccurs="0" name="ContactValidFrom" type="xs:string" />
 <xs:element minOccurs="0" name="ContactValidTo" type="xs:string" />
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 <xs:element minOccurs="0" maxOccurs="unbounded" name="EmailAddresses">
 <xs:complexType>
 <xs:sequence>
 <xs:element minOccurs="0" name="EmailType" type="xs:string" />
 <xs:element minOccurs="0" name="EmailAddress" type="xs:string" />
 <xs:element minOccurs="0" name="EmailValidFrom" type="xs:string" />
 <xs:element minOccurs="0" name="EmailValidTo" type="xs:string" />
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
</xs:schema>

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:
"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"
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 Query

Hi All,
If we use Import Server on the Port of a repository, we need to specify a map that can be run on the Port in Console.
But can I run multiple maps on the same file using the Import Server? If yes, how can it be done?
How can we raise an event whenever a file is dumped into a directory? I am using Import Manager batch and I want to schedule the batch process whenever a file gets dumped to a particular folder.
Thanks in advance.
Pooja.

Hi Subbu,
Thanks for providing me the code. But I am still facing a problem. I have modified my code as below -
import java.io.File;
import java.lang.*;
public class DirMonitor
 static final String DIR_PATH = "<Valid path>";
 static final int PING_PERIOD = 3000;
 public static void main(String[] args) throws Exception
 File dir = new File(DIR_PATH);
 while (true)
 String[] filelist = dir.list();
 if(filelist!=null)
 System.out.println("No.of Files found are:" + filelist.length);
 Runtime rt = Runtime.getRuntime();
 Process p = rt.exec("<Complete path to the batch file>");
 System.out.println("Check");
 p.waitFor();
 System.out.println("Next Check");
 try
 System.out.println("Waiting.....");
 Thread.sleep(PING_PERIOD);
 System.out.println("Waiting Complete...");
 catch (Exception e) {}
As soon as I am running this program, It runs well till System.out.println("Check");.
But it stops to process further on "p.waitFor()" statement.
Looks like the process does not terminate. I don't know why?
I doubt wheteher the batch file is running or not, as I don't see the batch file running on the command prompt.
Note: My batch file is running fine when I am trying to run it manually.
Can you please suggest what could be the problem?
Regards,
Pooja

Problem with import server automation(MDIS)...........

When i am importing the delimiter text data file manually with import manager(by both port method & delimiter file), 1116 records are getting imported, but when i do import server automation with same file & Map only 130 records are getting imported in to repository.
Details of server.
SAP MDM 7.1.04.122 (SP4)
Observations
1. In sap MDM console when i see port details, the status of port is : HAS exception.
2. In Exception folder log is created in ImportX subfolder.
3.in log folder, in files i could see most of lines as
<Failure ts="2010/04/01 12:43:26.084 GMT" tid="4184" entry-no="39" operation="Import" import-action="Create" row="1">One or more field values are invalid</Failure>
Did anyone faced the similar issue, or did i do any mistake or missed any step...

Hi Srinivas,
As you said that status of your import Exception is Empty once you delete all the records from Exception folders.
But when you again import records through MDIS all records are not getting imported. right?
I feel that it could be also possible that saved map which you are using into Port may have missed field/values.
So, I would suggest please go for this step by step and let me know if you face any issue.
1st step: Open this file using Import manager Type = Delimited text, select your Remote System and Delimiter as per your requirement. Map all your Fields and Values. Make sure that all your desired fields and their values are mapped correctly.
Now in the last come to import status and check that Action items: Ready to import . Don't import records here but save this map File-->Save As->Give Map name say MAP1 and then close your import manager.
2nd Step: Put this file into Ready folder and make sure that you MDIS services is stopped so that you can open this same file using MDM Import Manager Type = Port and select you required Remote system which you defined in MDM Console while defining Port and make sure that this port in console also contain the same map MAP1. Also make sure that you put same Delimiter Correctly in port as you put during mdm import manager.
check the status of Import into Import status Tab as Action items: Ready to import or not. It should have Action Items: Ready to import if not then map the missing values/fields and then Go to File-->Save.
Now Run your MDIS Services, and put this same file into your ready folder. This should import all of your records into MDM and i feel this will solve your Problem with MDIS.
Revert with result.
Regards,
Mandeep Saini

Import Server problem

Hello,
in the last days we experience some strange phenomena with the Import Server. For example, I created an XML import mapping for the standard repository "Material", created a port in the console and used the mapping there. Manual execution of the mapping worked fine. I dumped the file in the correspondent Ready-folder and the Import Server swallowed the file and progressed it.
So far so good.
I did this again, no problem. I tried a different file and got error messages, because the file format didn't match. But the Import Server still swallowed the file. Then I tried a larger file like the first one (the first one was just a 10-records-test), but no reaction. The Import Server did not swallow the file.
I read this thread: , stopped and started the MDM Server and the Import Server several times and then dumped files again - same result, even with the file with which it worked before.
I created a new mapping on Repository "Vendor" like the one on "Material", for the same file, no reaction. The Import Server seems to be sleeping.
Anyone faced a similar situation before? Any suggestions what I could do to resolve the problem?
Best regards,
Jörg
Message was edited by: Jörg Thiesmann

Some additional information on my problem:
The second file read the following error once for each record I wanted to read:
So there IS only one root element. The test file with which it worked before has exactly the same start/end.
This was the last logfile.
Message was edited by: Jörg Thiesmann

Help on import server

Hi friends,
please provide full configuration file for mds.ini(server), mdis.ini(import server) and
mdss.ini (syndication server)
[email protected]
Thank you
S Naidu
shankar

Hi Shankar,
You can refer the following format for the configurations:
_mds.ini_
[MDM Server]
XCS Ini Version=1
MDS Ini Version=1
Accelerator Dir=C:\Program Files\SAP MDM 5.5\Server\Accelerators
Lexicon Dir=C:\Program Files\SAP MDM 5.5\Server\Lexicons
Extra DBConnection Validation=False
Log SQL Errors=True
RELEASE\UseAssert=False
String Resource Dir=C:\Program Files\SAP MDM 5.5\Server\LangStrings\
Stemmer Install Dir=C:\Program Files\SAP MDM 5.5\Server
Log Dir=C:\PROGRA2\SAPMDM1.5\Server\Logs\
MDS Scone=
Autostart=0
Log Protocol Transactions=False
Modifications Dir=C:\PROGRA2\SAPMDM1.5\Server\Modifications\
Report Dir=C:\PROGRA2\SAPMDM1.5\Server\Reports\
Archive Dir=C:\PROGRA2\SAPMDM1.5\Server\Archives\
Distribution Root Dir=C:\PROGRA2\SAPMDM1.5\Server\Distributions\
CPU Count=1
SLD Registration=False
Log SQL Modifications=False
Maximum DBMS Bind Count=256
Max Initial MB to Retain=4
Max Send Failure MB to Retain=4
Oracle\Dll=OCI.DLL
Default Interface Language Code=eng
Default Interface Country Code=US
Allow Console to Retrieve Files=True
Oracle Tablespace Files=1
Oracle DBA Username=sapmdm
Oracle Best Block Size=2048
Client Ping Timeout Minutes=0
Inactive Client Timeout Minutes=30
Value Retrieval Threshold=0
TrexDllPath=
LOG_REC_MATCH_PERF=0
LOG_IMPORT_RECS_PERF=0
Import Slice Size=2048
Allow Console to Delete Files=True
Protect Family Nodes With Locked Data=False
BULK_IMPORT_SILO_LEVEL=3
Disable Log Retrieval=False
Max Large Text Length=50000
Number of Rows Per Fetch=100
Logged-In Role Maintenance=True
DBMS Reconnection Attempts=10
Workflow Detailed Report=False
[MDM Server\Databases\CUSTOMERMDVORCL_15_3_4_3]
Port=3249
Login=sapmdm
Password+=19TL68AMP7LARMAHS9QLUB2QV3
Block Ports On Structural Exceptions=True
Valid Keyword Chars=abcdefghijklmnopqrstuvwxyz0123456789
Mail Server=
mdis.ini
[GLOBAL]
Version=5540
Interval=60
Server=Hostname
Verbose=0x0000
String Resource Dir=C:\PROGRA2\SAPMDM1.5\IMPORT~1\LangStrings\
Log Dir=C:\PROGRA2\SAPMDM1.5\IMPORT~1\Logs
SLD Registration=False
[CUSTOMERMDVORCL_15_3_4_3]
Chunk Size=50000
No. Of Chunks Proccessed In Parallel=5
Login=mdis
Password=import
Log Protocol Transactions=False
Inter-Chunk Delay MS=10000
mdss.ini
[GLOBAL]
MDM Server Name=hostname
Auto Syndication Task Enabled=True
Auto Syndication Task Delay (seconds)=10
Default Interface Language Code=eng
Default Interface Country Code=US
String Resource Dir=C:\Program Files\SAP MDM 5.5\Syndication Server\LangStrings\
Log Dir=C:\Program Files\SAP MDM 5.5\Syndication Server\Logs
SLD Registration=False
[CUSTOMERMDVORCL_15_3_4_3]
User=Admin
Password=PWD
These all are there if you have only one repository "CUSTOMER" on your server. Make the entries for each repository following this customer and the [Global] wntries will appear only once.
Hope this is helpful to you.
Regards,
Dheeraj.

Steps to configure Import Server and Syndication server

Hi,
Can some one help me to work on Import Server and Syndication server. I know there are few forums availabe on this topic but they are not very basic. I need to know the basic step(From installation to automatic transfer of data.) to work on Import Server and Syndication Server.
Regards,
Ron
Message was edited by:
Ron

Hi Ron,
The MDM Import Server is a background process (service), which separates the core processing of master data imports from the front-end processing. MDM Import Server allows you to load master data records periodically from various
client systems to various MDM Servers and repositories based on the port concept.
Once the data is delivered by SAP XI on a specific port, it will automatically get picked within a configurable time interval and queued up for import processing.
MDM Import Server creates log files of the entire load process, which are stored
in the port folder Log and can be displayed in MDM Console.
If an error occurs in the automated import, the MDM Import Server stops and
drops the XML in the Exception folder of the port. You can import the XML
interactively using the MDM Import Manager and correct the error (for example
complete the import map).
Hope this might help....
thanks
Alexander
P.S. Kindly reward the points, if found helpful.

Differ between import manager and import server

Hi to all,
Can any one explain difference between import server and import manager and how the data will be imported to the same.
Regards
MM

Hi reddy,
Can any one explain difference between import server and import manager and how the data will be imported to the same
Please follow the text below, which has been taken from the help.sap.com
Both MDIS and the MDM Import Manager can import data from a source file into an MDM repository. However, each has unique capabilities that distinguish it from the other. When each is used to its advantage, the result is an import strategy which provides the most efficient importing of data possible.
The strength of the Import Manager is its connection to the source data, which enables its interactive map-making capabilities. When the Import Manager connects to a source it preloads the entire source file, giving it knowledge of every field and every value in the source data. This u201Ctotal awarenessu201D is crucial for preparing a complete import map. To help ensure a map is complete, the Import Manageru2019s Import Status tab alerts users to any discrepancies between source data values and the current map. The user can fix these problems interactively within the Import Manager and save the corrected map before any data is imported.
Preloading an entire source file comes at a price, however. It consumes memory on the computer running the Import Manager and very large source files may exhaust the computeru2019s available memory.
By contrast, MDISu2019s strengths are its scalability and automation.
For scalability, instead of preloading the entire source file into the host machineu2019s memory as the Import Manager does, MDIS processes records in a stream by loading a record at a time into memory.
This streaming technique enables MDIS to process much larger source files than the Import Manager, as the demand for memory on the host machine is not affected by the size of the import file.
In addition to file size, file quantity poses a second scalability challenge. For example, a real-time transactional environment may produce a staggering number of files, each containing only one or two records. To import these files individually through Import Manager would be extremely inefficient. MDIS tackles this problem with a file aggregation feature that processes files systematically in batches rather than as individual files, resulting in faster, more efficient import of data.
As it relates to automation, MDIS requires no user intervention to import files to an MDM repository. Instead, it relies on maps created previously within the Import Manager. Once an import file is placed in the appropriate folder, its data is imported automatically into the MDM repository using the rules of the pre-defined import map. Once a file is processed, MDIS scans the repository for the next file to import. This process continues 24 hours a day, seven days a week, until either MDIS or MDM Server are stopped.
The trade-off for this scalability and automation is that if discrepancies between the source data and the import map arise, MDIS cannot u201Cfixu201D these problems by itself. Instead, the u201Cproblem casesu201D can be fixed manually at a later time using the interactive capabilities of the Import Manager. Unlike the Import Manager, however, MDIS can set aside problem records or files and continue importing.
These conceptual and operational differences between the Import Manager and MDIS are summarized in the table below.
Item
Import Manager
MDIS
Source file location
Anywhere
Automatic inbound port
Import process
Interactive
Automatic
Import map state
Editable
Read-only
Object loaded in memory
Entire import file
Individual records
Streaming import support
No
Yes
File aggregation support
No
Yes
Maximum import file size
Limited (50,000 records)
Unlimited
Status location
Import Status Tab
MDM Console/Report file
Error correction prior to import
Yes
No
Exception handling during import
No
Yes
For additional info, kindly refer the link below:
http://help.sap.com/saphelp_mdm550/helpdata/en/43/12036df94c3e92e10000000a1553f6/frameset.htm
GO to-> MDM import Server
Hope it helps.
Thanks and Regards
Nitin Jain

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

Import server: Undefined elements exception

Similar Messages

Maybe you are looking for