Import Manager Batch

Hi,
actually I've already asked this question in a different post, but i want to reopen a new one to show the urgency of this topic and to be able to reward the answers.
The question or problem concerns the Import Manger Batch. Since I cannot find any documentation on the batch mode, i have to try and aks questions.
I use SP02 5.5.24.06
I want to load XML files into my repository.
When I start the Import Manager I use
Type: XML Schema
Client System: A defined Inbound/Outbound system e.g. R/3
XML Schema: CREMDM03
File: some xml files
After I've done the suffiecient mappings and saved the mapping I run the job and the Import works. I have the data without any problems in my reporitory.
But now I'd like to do exactly the same job with the Import Manager Batch.
I tried a few things and got many different error messages.
I've done a batch job with EXCEL files before and it worked.
How do I have to define my INI file?
Type: XML Schema
doesn't work.
Type: XML
doesn't work
Do I have to define a Port (with CREMDM and XML Schema) in the Console? But then how do I start this via the Import Manager Batch?
Thank you for help in advance
Regards
Nico

Hi Richard,
no still same problem. When I look at the log file I would say that there is a mapping problem. But the error only occurs when I put several files after each other in the "ready" folder.
If I stop and restart the server between every file import then it works perfectly fine.
Error log:
ts="2005/11/30 09:03:08.263 GMT" tid="2652" entry-no="52">Converting values: 'SORT1' field --> 'Search Term 1' field.<LINE-FEED/></Trace>
          <Trace ts="2005/11/30 09:03:08.263 GMT" tid="2652" entry-no="53">Converting values: 'STREET' field --> 'Street' field.<LINE-FEED/></Trace>
          <Trace ts="2005/11/30 09:03:08.263 GMT" tid="2652" entry-no="54">Record Matching...<LINE-FEED/></Trace>
          <Trace ts="2005/11/30 09:03:08.313 GMT" tid="2652" entry-no="55">Importing Lookup...<LINE-FEED/></Trace>
          <Failure ts="2005/11/30 09:03:08.313 GMT" tid="2652" entry-no="56" operation="Import" import-action="Create" row="1">Unable to find value map index for '10465' in 'POSTL_COD1' field</Failure>
          <Trace ts="2005/11/30 09:03:08.313 GMT" tid="2652" entry-no="57">     ImportManagerBatch failed</Trace>
          <Trace ts="2005/11/30 09:03:08.313 GMT" tid="2652" entry-no="58">Import Server job finished</Trace>
     </Open>
</MDM_Log>
Since there is no docu on the import manager batch I just try and error. How can I solve this problem?
edit:I tried it again and aigan with different files. The Import Server imports only one file per service start. Then I have to stop the service manually and restart it again. Then it takes the next file and so on. But this was the service doesn't make any sense.
Regards
Nico
Message was edited by: Nicolas Fink

Similar Messages

MDM Import Manager Batch

Hi everyone,
We are using the MDM Import Manager Batch to import data automatically. Can we write in our ImportBatch.ini the file name with * at the end : CREMDM.CREMDM04*.xml
because the file name comes with time stamp (CREMDM.CREMDM0420061129-103959-602.xml)
[Source]
Type=XML Schema
XML Schema=CREMDM04
File name= \...\... CREMDM.CREMDM04*.xml
DSN=
DBMS Server=
Database=
User=admin
In advance thanks,
Aklilu

Hi Aklilu,
the names of the XML files don't matter. MDIS tries to process everthing that is put into the ready folder. The ready folder is processed in a "first comes, first served" way. So there's no need to change the names. Is the time stamp in the file name really a problem? If yes, why?
> We are trying to parameter the mdis.ini and until now it does not work.
Could you specify this? In addition, I've got a few hints:
MDIS has to have the same build version as the MDM Server. In addition, MDIS has to be running (in Windows, you can check this in the Services Screen). Furthermore you should have a look at the Console's port definition (select your repository, go to Admin -> Ports in the menu tree). The port has to be configured correctly (XML Scheme, which map to be used, and so on). Very important: you have to set the port to automatic processing.
Here's a sample for the MDIS.ini:
[GLOBAL]
Version=5540
Server=WDFD00146633A
Interval=30
Automap Unmapped Value=True
Unmapped Value Handling=Add
Always Use Unmapped Value Handling=False
VXR_MAX=25000
Verbose=0xFFFF
-- Verbose OFF:     0x0000
-- Verbose ON:      0xFFFF
-- FI Verbose:     0x0001
-- XML Verbose:     0x0002
-- MAP Verbose:     0x0004
-- THRD Verbose:    0x0008
-- PARSER Verbose: 0x0010
-- STRUCTX Verbose: 0x0020
-- VALUEX Verbose: 0x0040
-- IMPORTX Verbose: 0x0080
String Resource Dir=C:PROGRA~1SAPMDM~1.5IMPORT~2LangStrings
Log Dir=Logs
SLD Registration=False
[SP04_BUSINESS_PARTNERWDFD00143366AMSQL_21_13_4_3]
Login=Admin
Password=
Chunk Size=50000
No. Of Chunks Proccessed In Parallel=5
Using the Verbose parameter you can define which errors, issues, messages and so on should be written into the MDIS log. You can find the logs directly in the port's log folder and in the log folder of your MDIS installation directory. If MDIS is not working or the import fails, these files contain some helpful information.
Kind regards
Michael

Problem with Import Manager Batch

Hi All
I am facing problem when I am running my Import manager batch. When I am executing my batch file after doing all required configurations its executing without doing anything. When i see the log file for the same its saying -
7796 2007/03/15 18:07:21.006 GMT Import Server job started
7796 2007/03/15 18:07:21.006 GMT Command line parsed
7796 2007/03/15 18:07:21.006 GMT OLE and socket initialized
7796 2007/03/15 18:07:34.568 GMT Cannot connect to server: '"10.30.107.4"' failed.
7796 2007/03/15 18:07:34.584 GMT ImportManager Batch End
I dont know why it could not connect to server as I am able to ping it using command prompt.
Any pointers? Please suggest!!
Regards
Tony

Hello Enc:
This is what I get from my import.ini file:
[Batch Import Default Option]
//possible values are: Yes or No
Automap Batch Unmapped Value=Yes
//possible values are: Add or Ignore
Batch Unmapped Value Handling=Add
//possible values are: Yes or No
Always Use Batch Unmapped Value Handling=YES
If you have a value, but is not mapped yet, you must put YES on the above settings. This will auto-add the missing values.
Greetings
Alejandro

AUTOMATION OF IMPORTING USING BATCH FILES...!

Hello Everyone!
I want your help on this matter. Actually I am trying to get data( in the form of XML) from BI into MDM SP04.
I want to automate the import process. i have saved the map and defined a port in the console and given the map name for the port.
now i configured the INI file present in the import manager batch.
I read somewhere that to run the importmanagerbatch.exe file i need to create a batch file having info about the INI file and then run the batch file which will execute the .EXE file.
But after doing this still data is not cmg in the repository.
Can anybody list me down all the required steps to automate importing. N can more than 1 map be taken care of in the console? or probably for every map we will have to create new ports for them?
I am totally confused....... please help me out.
Thanks and Regards.
Nitin jain.

Hi, Nitin,
The Import Batch can handle any number of maps in one batch process. It does have a limitation that the batch ini file will only reference 1 import file. But that file can contain any number of records and different table data.
I have used the Import Batch (only useable on Windows) for importing multiple check table data into the repository. In the dat file, I used the following code for each map. This is the code for the Partner Function.
:: IMPORT MAPS
cd "C:Program FilesSAP MDM 5.5Import Manager Batch"
@echo . STARTED Map: "Partner Functions" %DATE% %TIME% >> "C:MDMImportReport.log"
@echo Executing Map: Partner Functions
ImportManagerBatch.exe /INI "C:MDMMdmImportCheckTables.ini" /CLIENTSYSTEM "R/3 4.7" /MAP "Partner Functions"
            /LANGUAGE "English [US]" >> "C:MDMImportReport.log"
IF errorlevel 0 (echo . Completed successfully. >> "C:MDMImportReport.log")
           ELSE (echo . FAILED with error code %errorlevel% >> "C:MDMImportReport.log")
IF errorlevel 0 (echo Completed successfully - %TIME%) ELSE (echo FAILED with error code %errorlevel%)
@echo . Ended Mapping: "Partner Functions" %DATE% %TIME% >> "C:MDMImportReport.log"
@echo .   >> "C:MDMImportReport.log"
I then repeated this code in the batch.dat file for each map used. In total I had 93 maps.
Kristin

Batch Import and Batch Syndication

Hi Guys,
Please help me how Batch import takes place in windows environment and Linux environment (shell script also) and how to mention the timing in the scheduler a complete walk thru of this scenario ..........
Thanks in Advance............
********points will be rewarded*****************

Hi Dear,
Did you unzipped the installion of MDM.
You can find Import Manager Batch and Syndicator Batch alsong with other GUI.
Do not try to find seperate install for batches as its part of full installation.
https://websmp107.sap-ag.de/swdc
Entry by Application Group
Installations and Upgrades" SAP NetWeaver" SAP MDM" SAP MDM 5.5
The following objects are available for download:
File Type Download Object Title Info File File Size [kb] Last Changed
ZIP 51032724 SAP Master Data Management 5.5 SP5 Info 1108673 06.06.2007
Hope this help,
- An

Reuse of MAP in Import Manager

I am trying to reuse a MAP created to load KNA1 table in Import Manager in the same server. The Source file name and file type (.xls) is the same, as well as the original worksheet name. While the Import Manager is matching records, it is abending w/ following msg - Error sig:
AppName: importmanager.exe; Appver 1.0.0.1; ModName: importmanager.exe; ModVer: 1.0.0.1; Offset: 004e9c90
Thanks

Sure, this is possible. Remember that map/syn files are useful when you know in advance nothing has changed, that is, when automating the process (via batch/server processing).
One example might be if MDM is expecting numeric value, whereas in the past you used a text value. You might not be changing the source data, but you have made the MDM Repository more restricted.
Perhaps you should review which changes have taken place, something might be escaping your sigh
I hope this helps
Regards
Alejandro

Import Manager vs LSMW

Hello,
Since I started to learn SAP I've been seeing many different solutions to the same problems, but always with some added value in the newer of them. The question is: is MDM import manager supposed to be a replacement to LSMW? if not when should the late be used?
Best regards,
Younos Aboulnaga

Hi Younus
There is significant difference between LSMW and Import Manager. Although both follow the same concept of "Importing" data.
LSMW -
1. The full form of this is Legacy System Migration Workbench
2. The transaction code is LSMW and is executed in the SAP ERP system.
2. This is used to import - Master and Transaction data from legacy systems (in text format) into the SAP ERP systems (like ECC, etc).
3. This is a "workbench" that consolidates 4 methods of importing (master and transaction) data as mentioned below:
    a) Direct Input - Uses SAP provided standard programs for importing data.
        The data is imported in the SAP tables directly and hence is the fastest method.
        This must be the most preferred mode of importing data provided SAP has given standard programs.
    b) BDC - You need to create Batch import programs for specific SAP transactions to import the data.
    c) BAPI - Uses SAP provided standard BAPIs to import data.
    d) ALE/IDOCs - Use the ALE mechanism to import data via IDOCs.
MDM Import Manager -
1. This is a component in the SAP MDM suite of components used to import "master data" into the MDM repository.
2. There is no transaction code for the SAP MDM components (Console, Import Manager, Data Manager, Syndicator).
     Infact there are different applications (executable programs).
2. The import files can be XML or Text.
    It's possible to "push" data into the MDM repository using APIs and completely eliminate the middleware (NOT recommended).
Commonality in concept between the two are:
a) Both "import" data in the respective systems.
b) Source structure - Destination structure mapping
c) Field mapping
d) Value transformation & mapping
Hope this clarifies.
Regards
Neelesh

Import dtw batches

Hi,
I am a newbie (first implementation) and I need to implement a SKU reader in the warehouse. The SKU reader can provide me with a file that will be on a computer. I will need to read the file and process an import for PO and AR.
What are the basic fields for a batch import linked to a PO or an AR ( We manage batches in inventory on every transaction). Can I call the DTW via command line with params? Where do I find doc on DTW.
Are there better alternatives to the method described above (ie other ways to track batches then DTW).
Thanks

hi,
Check both dtw notes
814215 How can I assign serial/batch numbers to initial quantities
923719 How to import batch numbers correctly via the DTW
Jeyakanthan

Import large batches of WMA slow... Smaller batches, faster. What gives?

If I try to import more than like 20-30 unprotected WMAs into iTunes, the conversion is god awful slow. If I do them in smaller batches, it flies.
What's the deal? Bug in iTunes?

Hi VijayaKumar.
Import Server(MDIS) is best for importing Mass or Bulk Data. Please verify this on Page 246/403 of MDM Console Reference Guide. Table 63. Conceptual Differences Between Import Manager and MDIS
http://help.sap.com/saphelp_nwmdm71/helpdata/en/4b/71608566ae3260e10000000a42189b/MDMConsole71.pdf
Maximum import file size Limited (50,000 records) for IM Unlimited for MDIS
I think you need to make use of Import sleep time and Import Slice Size parameters for MDM Optimized Performance.
How to configure these Parameters for this Please refer below thread:
how to configure import slice and import sleep time in MDIS ?
Also please refer, Table 59. Optional MDM Server Parameters of MDM Console Reference Guide:
parameters like: Bulk Import Silo Page 226-227/403
Hope it helps..
Regards,
Mandeep Saini

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

Key Mapping activates Versus Import Manager

Hello,
I have Key mapping activated in the console and Supress Unchaged Records activated in my syndication map.
Case : I import files (suppliers catalogs) to MDM via Import Manager manually. I am not sure about it, but since I activated Key mapping property,
I noticed that for each supplier ID in the Supplier table, a lot of remote keys were created. Previously I only had one remote key for each supplier and now I have a list of other supplier's ID. ( Existent or nonexistent supplier IDs). This becomes an issue for my import, because when I try to import a file where the supplier id does not exist in the MDM ( this scenario used to block my import and this is what a expect, as supplier is a key in my mapping), the system automatically maps that nonexistent supplier to other supplier.
Can you help me to understand if this is caused for the key mapping property ? Any Idea ?
Thank you very much
Luciana.

Hello Stanley,
The remote keys are form the same remote system.
My story is : When I am importing a file , suppose my file has an invalid supplier ID. ( this means this supplier is not in the lookup table Suppliers)
1)The import manager will give me a message such as : Map Supplier ID Values. This behavior was expected.
2)I decided to test the automap. The invalid supplier was not mapped to a different value. I am ok with that.
3)If the user ( dont ask me the reason ;-)) decides to map that invalid supplier ID to a different one, he/she is allowed to do so. I remember when the key mapping was not activated this option did not exist. The map and automap button was deactivated.
What I am trying to make sure is : a remote key will be created for invalid suppliers ONLY if I choose to map it with a different supplier ID.
Do you have any comments about it ?
Thank you very much
Luciana.

How to add hyperlinks in Import Manager

Dear MDM-gurus!
I really tried hard to find the solution, but couldn't find it here or in OSS.
We already have a repository with more than 50.000 items.
What I'd like to do is to add hyperlinks to PDF-files in the internet to each item.
For this we got an excel-file from the supplier with the supplier part number in one column, the PDF-link in another column and the .
In Data Manager I was able to add links manually or also with importing entries of the excel-file. Importing from excel takes a LOT of time. I don' t know why:
- Fields to import: Hyperlinks
- Key fields: Supplier part number.
--> Action: Update all single matches.
How can I import hyperlinks in Import Manager, make the mapping and then update the records faster? E.g. I could not find the field "URL <Hyperlink> [Qual]" in Import Manager
Thanks for your help and best regards,
Henning

Resolved!
I accidently oversaw the URL fields in Import Manager in table catalog items.

Partial match for Value Mapping in Import Manager

Hello Experts,
We have a import map which is used to do mass insert of data into the main table. This is done as & when required by the end user.
We have a qualified lookup field which has a flat lookup filed as the Non-Qualifier. This flat lookup field is refering to a Lookup Flat table, which has mulitple dispay fields like Code,Name, Status etc. (14 fields in total) where as only the Code is the unique field.
We have only the unique field in our source file which we use for the import. Since we have only a part of the display fields in the source, the automap functionality in the Value maping section doesn't work. It becomes very tedious for the user to manually map all the values for this field.
Is there any way by which we can convert the source or target values in the import map, so that we can map the values using the Automap feature?
Your help & suggestion for alternate approach is highly appreciated.
Thanks in advance.
Regards,
Uday
P.S. We are using SAP MDM 5.5 SP6.

Hi Uday,
No need to enable remote key mapping for QLT. Please execute the below steps(stated with an example) -
1. Among all the fields in the referenced lookup table, identify the lookup fields and the tables they are looking up .
For eg.If you have a lookup field as 'Country' as one of the fields, look up table will be 'Countries'
2.For the identified lookup tables, set 'key mapping =Yes' in Console.
For eg, For Country Lookup table ,set Key mapping to 'Yes'
3.Import values into Lookup table (Import manager)/ Remote key update -
In import manager, select source (local file) and destination as Countries flat table.This Table will be haing 2fields - Code and description.Clone the 'Code'field and map it to Remote key field in destination hierarchy.Map code and description to equivalent destination fields. Select 'Code' as matching field > Perform import into lookup table.
Check if the records in countries table are updated with remote keys(in Data manager> right click on a record> select 'Edit key mappings' > view key mapping for the record)
3.Import to Qualified table/Auto value mapping -
Now, in the import map for qualified import , map the source field and destination field (of lookup type), all the values of this field will automatically map.
Similarly, refresh remote keys mappings for all the lookup tables first and then you can see auto mappings of values happening for the lookup fields.
Regards,
Vinay M.S

Sharepoint 2013 Active Directory Import- Manager field not updating

Hi,
SharePoint 2013 Active directory import -Manager field not updating
Concern/Issue-
We are using SharePoint and configured the Active Directory Import .First import it seems everything is working fine and OOB Organization chart built using User profile data is coming out right.
Now the user is moved from one Organization Unit to Another.
Now our Manager field is not Updating .There is change in AD manager attribute but not reflecting in the SharePoint User profile.
Manger field is mapped to "manager" attribute in SharePoint.
We tried removing the user and Re-Import using Incremental import but no luck.
Thanks for help in advance
Sachin

Moving a user from one OU to another in AD won't normally change the Manager attribute in AD. You would need to edit the user's organization settings to change the manager value in AD. I've also seen these changes not be picked up unless something
other than just the manager field in AD changing. Try changing something like Office location and see if the manager change is picked up by AD Import.
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

MDM Import Manager - remove multiple values from a multi valued fiedl

Hi,
We have this multi-valued field and we would like to clean the values from it.
How can we do this using MDM Import Manager?
Example:
Article A
Field XPTO has values Z, T and P.
We want this field XPTO with no values. How can we do a mass actualization to clean the field for some articles?
Thanks and regards,
Maria

*We have this multi-valued field and we would like to clean the values from it.
How can we do this using MDM Import Manager?
Example:
Article A
Field XPTO has values Z, T and P.
We want this field XPTO with no values. How can we do a mass actualization to clean the field for some articles?*
Hi Maria,
There can be multiple ways to achieve this -
1.After doing field mapping for XPTO you can set conversion filter for each of the values.
2.Value map with NULL.
3.Trigger a Workflow on import/record add,run assignment and make that field NULL.
4.Run mass update for conditional assignment based on that value of XPTO.
There can be more ways,whichever suits you best you can go ahead with that.
Hope it helped
Regards,
Ravi

Import Manager Batch

Similar Messages

Maybe you are looking for