Comma Delimited - MDM Import Server

when processing a comma delimited file using Import Server, the data contains commas but enclosed within double quotes ( "test, test"). can Import Server recognize the double quotes and not split the data into multiple fields because of the comma?
regards,
Jarred Alford

If you're using CSV-format, each delimiter sign will also interpreted as a delimiter, putting something in "" doesn't help here. Therefore you've to be very cautious and make sure, these chars are really only used as a delimiter, otherwise your content gets mixed up totally. You can see this pretty good, when calling Import Manager with such a file. in the preview you can see, what the system did with your files.
Best would probably be to choose a different delimiter.
Regards Klaus

Similar Messages

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
Default Batch Handling
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.

SAP MDM Import Server

Hi,
I need to work in SAP MDM Import Server.
I have already worked in SAP MDM Import Manager.
I need to know a more about SAP MDM Import Server.
Is it an application?
Regards
Kaushik Banerjee

Hi Kaushik,
I need to work in SAP MDM Import Server.
I have already worked in SAP MDM Import Manager.
I need to know a more about SAP MDM Import Server.
Is it an application?
The Import Server is a separate MDM application that uses import maps created within the MDM Import Manager to automatically load source data files into a repository.
The MDM Import Server (MDIS) automates the task of importing source data into MDM repositories. It is designed to reduce the processing complexity, resource requirements.
To know more about MDM Import server, which is also called the MDIS, please follow the link below:
http://help.sap.com/saphelp_mdm550/helpdata/en/43/12036df94c3e92e10000000a1553f6/frameset.htm
Go to MDM IMport Server (MDIS).
You will find the complete infomration about it.
You can find the complete process of Automated Import ansd Syndication in the link mentioned below:
Master Data Management Import Server and Master Data Management Syndication Server - Webinar Powerpoint
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/8973bcaf-0801-0010-b7a7-f6af6b1df00e
Hope it helps.
Thanks and Regards
Nitin Jain

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.

Regarding MDM Import and Syndication Server

Hi,
I have earlier worked in MDM Import Server.
Today, I successfully did MDM Syndication by
MDM Syndicator.
Now, the point is I need to do Import and Syndication
by MDM Import Server and MDM Syndication Server.
The MDM Version is 5.5.
Now, the point is under my installed directory:
F:\MDM SERVER\Server
in mds.ini file:
I need to give the following path:
Distribution Root Dir=F:\MDMSER~1\Server\Distributions\
I think other than these I don't have to do any configuration
in mdis.ini or mdss.ini.
Also, I have already inbound and outbound ports made and linked
to inbound and outbound maps.
Is there any more configuration needed?
Regards
Neha Singh

Hi Neha,
There are many configuration needed to complete the Automatic import and syndication using MDIS and MDSS.
Please go through the link below for the same:
Master Data Management Import Server and Master Data Management Syndication Server - Webinar Powerpoint
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/8973bcaf-0801-0010-b7a7-f6af6b1df00e
This will give you the complete steps to perform the same.
Hope it helps.
Thanks and Regards
Nitin Jain

Differences between various source files in mdm import manager

Hi,
Can anyone tell me the differences between the source files(access,xml,xml schema,excel) available in mdm import manager?
Thanks and regards,
Rithesh
Edited by: rithesh_shet on Mar 30, 2010 1:04 PM

Hi Ritesh,
MDM Import Manager provides flexibility to Import Data from different types of Sources into MDM.
You can import data into MDM from below mentioned sources using Import Manager:
1. From Files (Access, Delimited Text, Excel, Fixed Text, XML and XML Schema)
2. Directly from Data base source (SQL server and oracle)
As mentioned by Mandeep, XML Schema is something which you define in MDM console in advance. and then later select the Data source XML file and XML schema from drop down list (it will show all schema defined in console ) to validate XML source file against the XML schema.
For automated Import, Ports are used. Ports are nothing but a logical point of contact with other systems i.e. other systems or middleware will drop file on the port for authomatic import and MDM import server will scan the port directory and if file is present then will import data automatically from file into MDM using a predefine Import Map. (this map needs to be defined manually in import manager and then assigned to port using console).
Please check page no 45 of import manager reference guide for more details about various source properties of Import Manager. (*link for import manager reference guide is already provided on the earlier post)
Also check, page no 53 to 64 for how to import process. Kindly revert if you have any query.
Regards,
Shiv

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

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

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

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.

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

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

SSIS importing comma delimited with double quote text qualifier - Works in VS - SQL Job ignores text qualifier and fails (truncation)

I've created an SSIS package to import a comma delimited file (csv) with double quotes for a text qualifier ("). Some of the fields contain the delimiter inside the qualified text. An example row is:
15,"Doe, John",IS2,Alabama
In SSIS I've specified the text qualifier as ". The sample output in the connection manager looks great. The package runs perfectly from VS and when manually executed on the SSIS server itself. The problem comes when I schedule the package to run via SQL
job. At this point the package ignores the text qualifier, and in doing so pushes half of a field into the next available column. But instead of having too many columns, it concatenates the last 2 columns ignoring the delimiter. For example (pipes are fields):
15|"Doe| John"|IS2,Alabama
So the failure happens when the last half of a field is too large to fit into the next available field. In the case above _John" is 6 characters where the IS2 field is char(3). This would cause a truncation failure, which is the error I receive from the
job history.
To further test this I created a failure flow in my data flow to capture the records failing to be pulled from the source csv. Out of ~5000 records, ~1200 are failing, and every one of the failures has a comma delimiter inside the quoted text with a 'split'
length greater than the next ordinal field. The ones without the comma were inserted as normal and records where the split fit into the next ordinal column where also imported, with the last field being concatenated w/delimiter. Example records when selected
from table:
25|"Allan Percone Trucking"|GI6|California --Imported as intended
36|"Renolds| J."|UI6,Colorado --Field position offset by 1 to right - Last field overloaded
To further ensure this is the problem, I changed the csv file and flat file connection manager to pipe delimited, and sure enough every record makes it in perfectly from the SQL job execution.
I've tried comma delimited on the following set ups. Each set up failed.
SSIS Server 2008 R2 RTM
DB Server 2008 RTM
DB Compat 80
SSIS Server 2008 R2 RTM
DB Server 2008 R2 RTM
DB Compat 80
SSIS Server 2008 R2 RTM
DB Server 2008 RTM
DB Compat 100
SSIS Server 2008 R2 RTM
DB Server 2008 R2 RTM
DB Compat 100
Since a lot of our data comes in via comma delimited flat files, I really need a fix for this. If not I'll have to rebuild all my files when I import them to use pipe delimiters instaed of commas. I'd like to avoid the extra processing overhead if possible.
Also, is this a known bug? If so can someone point me to the posting of said bug?
Edit: I can't ask the vendor to change the format to pipe delimited because it comes from a federal government site.

Just wanted to share my experience of this for anyone else since I wasted a morning on it today.
I encountered the same problem where I could run the package fine on my machine but when I deployed to a server and ran the package via dtexec, the " delimeter was being replaced with _x0022_ and columns all slurped up together and overflowing columns/truncating
data etc.
Since I didn't want to manually hack the DTS XML and can't install updates, the solution I used was to set an expression on the textdelimiter field of the flat file connection with the value "\"" (a double quote). That way, even if the one stored in XML
gets bodged somewhere along the way, it is overridden with the correct value at run time. The package works fine everywhere now.

Comma Delimited - MDM Import Server

Similar Messages

Maybe you are looking for