Fixed value population in Import Manager

Hi
I want to populate a fixed value say 'XXXX' to a destination field while loading data thru import manager.
Can I get some tips how to accomplish that.
Appreciate your help
-Reo

Hi Reo,
You can probably make use of Conversion Filters to accomplish this.
In the Map Fields/Values tab of the Import Manager, when you map your source field to the corresponding destination field; you can apply a conversion filter on your source field.
In field mapping sub-pane, right-click on the source field and select Apply Conversion Filter. You can these choose an appropriate filter like Replace and eliminate/replace source field value with/by blank space followed by Apply Operator --> Prepend and then specify your fixed value 'XXXX'.
As a result your source field will always contain the value 'XXXX' and the same will be imported into your destination field. You can preview the converted source field value in the Converted Value column of the Value Mapping sub-pane(Source side).
This could be a possible solution to your problem.
Let me know if this helped your cause.
Regards,
Siddharth

Similar Messages

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

Value Mapping in Import Manager

Hi All,
I have Probelm while loading data to MAIN TABLE through Import manager,I am getting XML file from Legacy System in which legacy sends State Code like NM (for New Mexico) .In my region table I made Name and Code as display field .Created my Import map ,when ever new value comes for region value mapping is not working ,I tried changing my region table with code only display field it works ,but I want Name also display field .
Note : all my lookup table Remote key mapping Enabled
Is there any way we can acheive this or am I missing some thing here .
Thanks,
Madhu

Hi Madhu,
to achive this:
1. First go to the table where you are maintaining the region codes.
2. Enter the region code there and then go to the import manager by connecting to the source file.
3. go the region field map by opening the map.
4. go to value mapping pane and select unmap.
5. then select Automap and check the that your region code added manually is mapped with the source file.
6. You may see some unmapped source values, map it to Null values at destination.
7. Save the map.
8. This shoul enable the import for you.
if you want to avoid the manual mapping everytime, you should be getting all the region codes once and import/update it in the data manager as a one time job.
Then you avoid steps 1 to 3 everytime and carry out the remaining steps to import the records.
Hope this helps resolve the issue.
Thanks
Rahul

Importing text file (delimited, fixed width) with MDM Import Manager?

Hello all,
According to the overview section of the import manager reference guide, it is possible to import from delimited text files (e.g. CSV).
But when it comes to the details, text files are not mentioned anymore. I also found no option in the Import Manager.
Could you tell me whether this is possible and - if it is - how?
Thanks in advance!
Kind regards,
Dennis

Hi Dennis,
In order to import flat files into MDM do the following. This solution is specific to MS Windows:
I. Set up ODBC for *.txt or *.csv files
1. Open Data Sources (ODBC) interface:
Start> Settings> Control Panel--> Administrative Tools -->Data Sources (ODBC).
2. Select System DSN Tab in Data Sources (ODBC) interface.
3. Click on [Add]. Select the Microsoft Text Driver. Click Finish.
4. Write a Data Source Name
5. Uncheck Use Current Directory to enable the [Select Directory] button.
6. Click on [Select directory] to determine the source directory.
7. Select the source file.
8. Click [OK] and return to the ODBC Text Setup screen.
9. Click [OK].
10. Return to the ODBC Data Source Administrator dialog and click [OK].
II. Importing from Flat file
1. Run MDM Import Manager.
2. Select ODBC from the Type drop-down field of the Connect To Source dialog.
3. Enter the DSN name from the Setup ODBC Connection dialog above.
4. Select the file name with extension (.csv or .txt) in the Tables panel of MDM Import Manager and the file content in the Records panel.
Hope this solved your problem.Please mark helpful answers
Regards,
Santosh.

How to Modify Hierarchy Filed Values by using Import Manager

Hi All,
I have some lookup table values in my source file in 1st attempt I have updated successfully. But, after cross checks the same i found that hierarchy level are incorrect at the destination side.
Source Hierarchy lookup values
Item1
Item 2
Item 3
Item4
Destination Hierarchy lookup values
Item1
Item 2
Item 3
Item4
Note: After Adding the Source filed hierarchy structure by selecting the Add Branch as child opting in the value mapping area
I am getting unique constraint Violated error message while importing the values.
So, how can I update the Source Hierarchy fields structure to Destination Hierarchy Field structure?
Thanks in Advance.
Mahesh

Hi Mahesh,
While importing the values if you get the error unique constraint Violated, that means that the same value has been mapped twice.
when you try to map the values of the hierarchy, NULL would have been automatically mapped.
When you select all the records and do add branch as child, the same NULL would have been added and mapped again.
If not with NULL, this could be the case with some other value.
Just check if some value is added and mapped twice in your value mapping.
This should solve your issue.
Try and let me know the result.
Regards,
Sravan

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

Truncate / Trim and Convert the values while importing in Import Manager

Hi,
I am facing the following issues while importing the values in Import Manager.
1) The incoming value is a 4 character text value (e.g. D004) and i need to truncate the 1st two characters so that i get the output as "04" and map it to the destination numeric 2 character field.
Can any1 help me on this as to how can i truncate the 1st two characters?
2) My incoming value is a numeric field which is coming from ECC. this value can be negative as well. the ECC sends this value as (78.00-) ie the minus sign is suffixed to the value but in MDM i need it as (-78.00) ie minus sign prefixed to the value.
Is there any setting in Import manager where i can set the minus sign as a prefix?
Useful answers will be rewarded with points.
Regards,
Roshani

Hi Roshani,
Can any1 help me on this as to how can i truncate the 1st two characters?
As suggested by everyone, none of these options will work. Since your field has alphanumeric Value i.e. D004. Use Option Replace.
After mapping your source field with target field which must be of Type TEXT, Right click on your source field>Set Value Conversion filter>Replace..-->a pop up window will come Replace write Find What: D0 and Replace with: keep it blank(dont write anything) and then Press Ok, you will see all your Source values D0XX converted to XX and then can save in Import Map which will give you the desired result.
If you set your target field of type INTEGER, you cant have option Replace. And the TRUNCATE option as suggested by everyone will not work as Operand 2: you can set as Numeric values only, you would not able to write D.
Is there any setting in Import manager where i can set the minus sign as a prefix?
I dont think this is possible alone with Import Manager, you need MDM workflow for this where your workflow trigger action = Record Import in Data Manager, and need to select the same workflow in configuration options of Import Manager>Import>checkout/workflow = select the workflow name from drop-down which you set in Data Manager and then need to save this in your Import Map. So in this manner whenever record comes through import Manager, these records automatically will go through this Workflow and will give you the desired result.
START(CHECKOUT)>Assign>STOP(CHECKIN)
Assign step where you give assignment on this field and write assignment expression as:
IF(FIND(XXX, "-"), "-"&LEFT(XXX, (LEN(XXX)-1)), XXX)
where XXX = Field name which you defined in MDM repository.
Regards,
Mandeep Saini

Automap Lookup values in Import Manager

Hi,
I have lookup field in main table for country code. In import map I can do automap and then can run the import. But when the new data comes in, new valid country code values are not automatically mapped. I have to click on automap again. I have looked at MDIS default unmapped handling options and do find any that will cover this scenario. This is a very basic scenario, I think I missing something here on how to set this automap feature for future imports. Any help would be appreciated.
Regards,
Imran Zafar

Hi Imran,
For automatic Value mapping, you have options in the MDIS.ini
Please refer to the Page no-12 of this link doc:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/8973bcaf-0801-0010-b7a7-f6af6b1df00e
Also, there are few configuration options for Value Automapping in the Import Manager config options. You can go through the Link below
http://help.sap.com/saphelp_mdm550/helpdata/en/43/12036df94c3e92e10000000a1553f6/frameset.htm
Go to MDM Import Server. MDIS Configuration->Trouble Shooting
Now, after doing the basic settings, Also, there can still be problems. I had faced a similar issues while importing a file and the Automap feature did not work fine.
You can use Import Manager-> File->Save Update for an Import Map. This will save all the updates you make to the map.
After save Updates, try importing a file and check whether the values are getting Auto mapped.
Hoep this info helps.
Thanks & Regards
Nitin Jain

Creating Value Conversion Filters in Import Manager

Hello.
I am trying to create some Value Conversion Filters that change street suffixes to abbreviations. Such as Lane to Ln.
How would I go about doing this? Am I supposed to use the find/replace Conversion Filter?
Points awarded to any helpful answers / helpful guides (besides the Import Manager Guide) <--- I have this already
Thanks,
Nichole

Hi,
Yes u can use the Find/Replace Conversion filter property in Import manager.
In this u can write the word u want to change and then write the req format.
But the conversions are permanent while if u do this in MDM data manager under transformations they are temporary.i.e they will not be syndicated.
Hope this may help u.
Rgds]
Ankit
Edited by: ankit jain on Aug 6, 2008 5:06 AM

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

Table lookup instead of fixed value mapping

Hi Folks,
My current scenario is that I have used fixed value mapping to map a single target field. These details are actually maintained in the TP_Code table in R3 (a sample table).
TradingPartner:SAP:Short Text
PA:PA:Package
PL:PAL:Pallet
The table contains 20 entries.
I am thinking that fixed value mapping is not a good option since there might have future changes in the TP_Code table.
Is rfc lookup a good option? But I am not sure which rfc to use and if there is any udf availble to be used in parsing the xml payload.
Please advise.
Thanks a ton!

Thanks so much for the links!
I managed to use and run the RFC lookup to an R3 table using JCo. However, I am not getting the right result.
I am getting the result in this format -> 800,PA,PAC,Package
The correct output is PAC which is the third node. Could this only be achieved by using java tokenizer?
The code that I have used is as follows:
Import com.sap.mw.jco.*;
//write your code here
String DBTABLE = a;
String WHERE_CLAUSE = b" = ""'"c"'" ;
String sapClient = "xxx";
String hostName = "nnnxxx";
String systemNumber = "xx";
String userName = "nnnnn";
String password = "******";
String language = "EN";
JCO.Repository mRepository;
JCO.Client mConnection = JCO.createClient(
               sapClient,
               userName,
               password,
               language,
               hostName,
               systemNumber );
// connect to SAP
mConnection.connect();
// create repository
mRepository = new JCO.Repository( "SAPLookup", mConnection );
// Create function
JCO.Function function = null;
IFunctionTemplate ft = mRepository.getFunctionTemplate("RFC_READ_TABLE");
function = ft.getFunction();
// Obtain parameter list for function
JCO.ParameterList input = function.getImportParameterList();
// Pass function parameters
input.setValue( DBTABLE, "QUERY_TABLE");
input.setValue( "," , "DELIMITER");
//Fill the where clause of the table
JCO.ParameterList tabInput = function.getTableParameterList();
JCO.Table inputTable = tabInput.getTable("OPTIONS");
inputTable.appendRow();
inputTable.setValue(WHERE_CLAUSE,"TEXT");
mConnection.execute( function );
JCO.Table valueSet = function.getTableParameterList().getTable("DATA");
String resultSet = valueSet.getString("WA");
mConnection.disconnect();
return resultSet;

What is meant by criteria of Updateability in MDM Import manager

Hi,
What is meant by criteria of Updateability in MDM Import manager? i read some information, but i could understand, it says original data source be updateble. what is meant by Original data source.?
what is the use of option "Read-only" in Import manager logon screen.
Thanks

Hello Ankam,
You can check the Read-only option to prevent MDM from updating your data source.
Kindly see the below information on "DATA SOURCE UPDATES"
DATA SOURCE UPDATES
Some MDM Import Manager operations require that the original data source be updateable, thereby allowing new fields and/or entire new tables u2013 and the corresponding data values for each record u2013 to be automatically added to the data source before further processing.
Other operations simply create virtual fields in the MDM Import Manageru2019s workspace, although if the data source happens to be updateable, some of these operations instead add the new fields to the original data source as well.
NOTE ►► Updating the data source when possible allows you to
perform additional operations on the new fields as if they were part of
the original source data, and also use them as record matching fields.
NOTE ►► Fields that are added only if the data source is updateable
can be deleted automatically by the MDM Import Manager when you
exit or switch data sources based on the setting of the Delete Created
Fields on Exit configuration option.
Updateable Data Sources
Whether or not a data source is updateable depends upon the following:
u2022 Source type. The source Type must permit the MDM Import Manager to update its schema and insert the additional fields of data; some supported types are updateable and some are not.
u2022 Media. The media on which the data source resides must itself be updateable. If the media on which the data source resides is readonly, such as a CD-ROM, the data source cannot be updated.
u2022 Permissions. You must have the proper file system permissions to update the file, or the proper DBMS permissions to update the schema of the database.
u2022 Read-only option. You cannot have checked the Read-Only option, which prevents MDM from updating the data source even if the other conditions would otherwise permit it.
NOTE ►► The Read-Only option is: (1) enabled for source types that
can be updated (Access, Oracle, SQL Server, and XML); (2) disabled
and unchecked for those that use Access as an updateable staging
area (Delimited Text and Fixed Text); and (3) disabled and checked for
those that cannot be updated (Excel and ODBC).
NOTE ►► When the data source is SQL Server, the table names in
the database must not contain spaces; otherwise any operation that
would update the data source will fail.
Hope this helps.
Regards,
Vikas

Import Manager Join Tables not working

Hi Experts,
for combining tables in the Import Manager i tried to use the join and lookup function.
My easy example is:
Table1
Product ID
Organsation ID
Table2
Organisation ID
Plant
Now I'm joining using the field Organisation ID which contains the same items and make a lookup on the field Plant. In the Source Preview I can see the looked up field but without any values and it is with a grey background.
Any suggestions?
Thanks
Andy

Hi,
I tried this at my end. It seems like a Bug. I am using MDM 7.1 SP3.
Facing same issue, I mean Grey background (not editable) in source preview, when we look-up field Plant from Table1 to Table2.
This field values are seen mapped in Map Fields/Values tab, but when i import data. Fields get populated for Product ID and Organization ID only but Plant field is not getting populated into MDM data Manager.
So, i am quite sure it seems like a Bug and I would Suggest you to Raise OSS note for the same.
Temporarily, You can import data in below manner.
I mean when you select Source table as Table1, you can import Product ID and Organization ID.
After importing Table1, select your Source table as Table2 map both fields Organization Id and Plant.
Import data by selecting Matching Field as Organization ID and Default Import Action as Update (All Mapped Fields).
So, in this way you can have your complete data in your MDM but obviously just because of bug which you can do in Single Step, Now going to be done in two Steps.
Note: For one of Client i did this on MDM 5.5 SP6, that time it was working perfectly.
Thanks and Regards,
Mandeep Saini

Import Manager Crash

Hello
We are importing data from CSV files (odbc) and the import manager keeps crashing with the error.
"the system cannot find the file specified. Windows Sockets Error Code 2.
How can we fix/avoid this.
We are running MDM 5.5 SP4 patch 02. All help is appreciated.
Regards
Con

My take on this is : when you have a large import happening thru import manager - it sucks up a lot of memory and at the same time if you open data manager - and if it sucks up more memory than the threshold memory - there might be a disconnect between the clients [import manager & data manger ] to the MDM server. This is when the import manager or data manager "crash".
Techinically its not a crash - its more of a disconnect. When this happens you will get Windows Sockets Errors .
Solution : - increase memory on the system, or use import server instead to load, or open data manager after the import manager is closed.
[ threshold memory is no fixed value which can be defined - it will depend on server hardware and the amount of memory used by the import manager and data manager]
-Vinay

Import manager error, when using Standard maps

Hi,
I am trying to import data using Import manager statndard Maps.
For certain maps I am getting the following error message.
"Unable to retrieve unique values for field 'Key <Clone>'."
And also after getting this error if I close the current statndard map and open another standard map, import manager crashes.
I am using MDM Version 5.5 SP2(5.5.24.04).
Thanks
Subbu

Hi Subbu,
I encountered this issue around inability around unique values for cloned fields too, although in custom maps, not standard ones.
1. When reported, this was fixed in 5.5.24.05. So, try usin 5.5.24.06 and see if you still face it.
2. The other option or workaround to be precise is to uncheck the Read-only box in bottom left hand corner of the second screen. This should work too.
As a last note, even in 5.5.24.06, I still encounter this issue when importing into nested look up tables. This is up for future fixes.
I use the uncheck read-only as work around for now.
Good luck!
Savi

Fixed value population in Import Manager

Similar Messages

Maybe you are looking for