Frequent/periodic import with Import Server

Hi everyone,
I just read that the MDM "Import Server" allows for doing frequent/periodic imports. It was also stated that this frequent/period import only works with importing files. And furthermore, that the reason for this restriction lies in MDM's link to SAP XI.
So what if I frequently/periodically want to import from an MS SQL server? Could I do this by working with SAP XI? (I haven't worked with XI yet)
Best regards, Daniel

hi,
So what if I frequently/periodically want to import from an MS SQL server? Could I do this by working with SAP XI? (I haven't worked with XI yet)
yes you can do the frequent/periodic import with import server.
follow the link:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/8973bcaf-0801-0010-b7a7-f6af6b1df00e
hope this may help you,
Regards,
Srinivas

Similar Messages

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

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

Updating record with check out in Workflow by Import Server

Hi,
I have a Workflow starting with "Checkout". During the Workflow, a syndicate is executed, a WebService is called and the response is processed by Import Server.
The record is not updated because it's u201Ccheckoutedu201D.
The user that executes the Import Server is the Admin, which have all roles and the u201CAuto-Join checked out recordsu201D parameter is u201Cyesu201D.
Can I update a record with check out by Import Server? The MDM version is 5.5.64.71
Thank you,
Evandro

Lets start with this....
1. Auto-Join checkout records -->Yes ; should join the record which is already checkedout as well as in workflow.
2. Check the [owner] assigned to workflow record that might stop you to AUTO-JOIN this record to exisiting.
please feel free to revert.
thanks
Alexander

DM 3.1.1 with SQL Server 2008 . Extended Properties not imported .

Hi
I am using Data Modeler 3.1.1 with SQL Server 2008.
I have a database where I have Extended Properties (MS_Description) for the tables and columns.
I use the Import Data Dictionary option (database type SQL 2005) , and the extended properties are not being imported to the model.
Is there anything else that I should do to have the descriptions imported?
Regards,
Jorge

Hi Fernando
That is what I need to do.
Create a Model from an existing SQL Server database with the Import data Dictionary option , be able to modify tables structures, extended properties in the model, and then sync those changes with the database.
So far I can't import the extended properties with DM 3.1.1. If you find a way , please let me know.
Thanks,
Jorge

Imported email synced with IMAP server?

Hey guys,
I'm about to import a couple of emails into an email account on a machine and wanted to know if these email are being synced with the server and appear on all devices?
Thanks in advance
Constantin

Anything on an IMAP server should appear on all clients that connect to the same account.

ODC Import Server - Working with emailed read only files

When running the ODC import server as a service or as an application we sometimes get users that send us emails with "read only" attachements. ODC will get stuck on these emails becasue excel will prompt to open the read only file.
Is there a way we can easily get around this problem? Is there an ODC setting or an Excel setting that I can use to always open all excel documents?
Data_Bitz

You are missing an indexing step, which can't be done automatically without the Recognition server (or manual indexing). ODC manual explains briefly on the 34th page:
Import Server, which imports images and other electronic documents directly into Capture from sources such as email, FTP sites, network folders, list files, and fax providers. As images and electronic documents are imported, they are converted into Capture batches where they can be indexed using Index or Recognition Server and then committed.
I use import server only for importing network folder scans and assigning them to the appropriate batch for manual indexing, so can't give you an elaborated advice.
Regards,
Boris
Edited by: tombo on 2011.09.14 01:21

Sharing Import Server with MDM

Is it feasible to have a shared import server used for both MDM and SRM-MDM Catalog?
The SRM-MDM sizing guide recommends an independent server just for the MDIS (for production). I am wondering if I could just use the server we have for our MDM system.

Hi,
You can use same Import Server but it depends on how often and how many items are going to import in MDM scenario side.
Regards,
Masa

Issues with Import Server

I have set up the MDM import server and it seems to be pulling the files from the port directory (/Ready directory) and creating a log that says successful, but the materials are not being created in the data manager. Any clues as to why this may be happening, or if there is another peice that I need to configure?

In one of the log files I found the following:
<Trace ts="2006/11/21 16:25:32.883 GMT" tid="3" entry-no="1">[MDS=sd4p1v7 Repos=Material AgencyID=7]: MS Excel not supported in this release. RC: 0x80000001<LINE-FEED/></Trace>
Does anyone know if possibly Excel format (.xls) is not supported by the import server? I have tried importing manually and it works fine....

Import server Process consuming maximum time at Parsing and Importing steps

We are using Import server to Import files and most of the time looks like is spent on Impoting and Parsing, the whole load took little more than an hour and these two steps (see the log below) took almost 50 mins.
1543 2008/09/29 17:23:07.041 [MDS=usil0d32 Repos=ZCustomer11_Q ClientSystem=R3_ERP Port=IMPORT_MAIN]: xImporter: Thread started.
772 2008/09/29 18:12:20.231 [MDS=usil0d32 Repos=ZCustomer11_Q ClientSystem=R3_ERP Port=IMPORT_MAIN]: xSaxParser: Thread finished; Start -> End: 2612.191168000 seconds.
So I wonder how can we reduce the time taken for these two steps?
Same thing on Import Manager takes 10 mins max to open up and I assume Import manager opening up an XML is equivalent to Importer & Parser thread of Import server ?

It is Queued parallel Processing, you will not see a true parallel processing here, just like a pipelined CPU architecture.
Say Chunk 1 is at stage 1 preparing import records
Then Nothing else happens parallelly
Now is Chunk 1 moved to stage 2 Filter/Merge
Then Chunk 2 can move to stage 1 preparing import records
Now Chunk 1 moves to stage 3 MDS
Then Chunk 2 moves to stage 2 Filter/Merge
And Chunk 3 moves to stage 1 preparing import records
so on ......and so forth......
So if you prepare a Gantt chart with all these tasks in swim lanes then over a period of time you will observe that actually 'n' number of tasks will be running on various chunks and this 'n' is the what you set in No.of Chunks parameter.
try observing, when the stage 1 task started on Chunk 2 , see if it kinda overlaps stage 2 of chunk 1. Try posting all the logs , very interesting observation !
Size of Chunk is like preparing the packet, in any communication protocol, the more records you have in chunk , the less overhead/record but more wait time. The less the no.of records you have in your chunk the more the overhead/record but less the wait time. So yeah this can be tweaked according to your memory.
-Sudhir.

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

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.

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

Frequent/periodic import with Import Server

Similar Messages

Maybe you are looking for