Value Exceptions - Import Map Update

Hello MDM Gurus,
We have the requirement to update the existing import map by unmapping two of the fields that we no longer required.
When we try unmapping the required fields and save as another map name, export, reimporting it and overwriting the existing map with the same name. But the problem is we are loosing all value mappings. we are facing issue getting loads of value exceptions as all value mappings are gone.
Please we need experts advices to resolve this since we no longer need that two fields getting imported in to the repository.
We need a solution to unmap that two fields and keep all existing value mappings.
Save Update not works for filed mappings, it only works for value mappings.
Thank you very much in advance for the suggestions and inputs.
Example :
Field1 and Field2 Unmapped, We saved the Map by Save -> we are loosing all value exceptions ( As it stores only present config)
Field1 and Field2 Unmapped, We saved the Map by Save Update -> When reimport the map again, we are seeing this field1 and field2 still mapped.
Field1 and Field2 Unmapped, We saved the map by Save As -> Still it does like First Scenario.
Please Advice.

Hi Smartsoft,
Just try this below procedure and revert with result.
1. Open the existing map.
2. Remove all the fields from matching field under Match Records tab.
3. Now unmap these two not required fields under Map Field/Value tab.
4. Afterwards, set again all the matching fields like earlier under Match records tab. Now make sure that under your Import Status tab Action Item: Ready to Import. Once it is done.
5. Now try with Save As option as a new map in order you have had existing correct map as a reference for future.
If it work properly then you can overwrite this new map name with existing map. Kindly revert.
Regards,
Mandeep Saini

Similar Messages

Issue facing : Deletion of Qualified Look up field value : Using Import Map

Hi All,
We are having qualified multi-valued look up field in the main table. Using import map for the main table record update, we are trying to delete the qualified look up field value. But it is not working.
Please guide on how you have achieved this.
One approach is to supply NULL value, though I am not sure or have tried this.
Regards,
Ganga

Hi Ganga,
I assume that you are trying to delete the Qualifier values for the Qualified look up table. The only possibility is to pass the Null values to the already Existing records in the Main table. Please note that if you are passing one Null value only one record will get deleted. So you will have to pass the Null values equivalent to the number of values for the Multi Valued Qualified table.
Kind Regards,
Thamizharasi N

Value Exception in Import server

Hi Experts,
My requirement is i have 100 files in the ready folder while processing first file through import server, it got value exception which i fixed manually through import manager port option and saved map as update. But even after the files which are having records with same values also moving to Value exception. Can you please me help me out to fix it.
Thanks
Narendra

Hi Mullapudi Narendra,
Value exception only come when any new value occurs in you lookup table so avoid this in importmanager configuration setting require to set MDIS parameter
in MDIS Add / Map / fail and ignore detail as follows
Add : value at destination side doesn't exist then this value get added to your lookup table as well as update this value at record. add new value at lookup subtable and update record at main table
Map : value will only map which are exist at destination side. update records at main table
Fail : if any new value occurs which is not exist at destination will not allowed to import this record as well as lookup field value.
entire record will get fail and doesnot import lookup subtable and maintable
Ignore : if any new value occurs which is not exist at destination will ignore this value and remaining data will get import except lookup field which contain new value .only value will ingore at lookup subtable and maintable for respective field, other field data of file will import
Thanks,
Jignesh Patel

Import Server - Workflow related value exceptions

Hi,
Our Import Server is importing multiple records, one record per file. The inbound port is configured with a file threshold of 5, 50000 chunks and 5 parallel chunks.
We are using a workflow on import to assign values to 2 different fields. In the start step of the workflow the records do not get checked out.
When importing 1000+ records it works great, but a couple of times it runs into value exceptions.
In the log files I can find the following error:
Import failed. Cannot import record with workflow because the record is already checked out
Import action: Update (All Mapped Fields)
Source record no: 16
All MDM components have version 5.5.42.92.
I saw a similar issue in a different thread. Is this fixed in 5.5.42.98?
Thanks & Best Regards,
Ingo

Dear Saurabh,
The record is not checked out in Data Manager at the time the error occurs.
Nobody is checking out records prior and during the whole test run.
5.5.42.98 - I tried this out and get the same errors.
In our project we are still on 5.5.42.92 and won't upgrade until we know that another version is doing better.
There are some functionalities in MDM5.5 SP06 patch 1 that are not working well, for example try out the qualified update (update (new links create, existing links update (all mapped fields), that you can set on field level and you will get some unexpected results. We won't go for SP06 until we are really sure that all issues we experience are fixed.
What else could be the cause for this error?
Thanks & Best Regards,
Ingo

Qualified Updated Selections not Saved in Import Map

Hello,
I create a new Import Map and Set the Qualified Update setting on a qualified table. When I reopen the map, the Qualified Update option is saved but not the selections for the qualified update. The defaults are saved: all fields are selected as matching qualifers. Create = blank, Existing = blank.
I have tried to recreate a new map and get the same results. Any ideas?
thanks
Tammi

Hi Tammi,
could you pls elaborate on the exact issue a bit more?
Reg,'
Bis

How do i update & test import maps and syndication maps?

HI,
Can anyone guide me/ let me know the steps - how do i update & test import maps & syndication maps during upgrade in development system>
Regards,
Harmony

Hello Harmony
Different service packs SAP MDM 7.1 supprot the same Syndication and Import map format.
For Import map is updating you can use Import manager
For syndication map is updating - Syndicator
If your syndication and import map have been saved into repository just archive repository from your source landscape and unarchive it in destination.
If your syndication and import map haven't been saved in repository.
Exporting your maps to xml(syndication maps from syndicator and import maps from Import Manager) before migration and importing it to new repository.
According updating(modification) repository structure:
For Import map is updating you can use Import manager
For syndication map is updating - Syndicator
Another way(very exotic) - make changes in exported xml maps.
That's all
Regards
Kanstantsin Chernichenka

Update MDM Import Map

Hello...
I am a PI consultant who inherited MDM recently.
MDM 5.5, SP06
My issue is that I have an existing map that works fine, but the source schema is changing to add a few new fields. I need to map the new fields to my existing catalog repository.
I had to import the revised schema under a unique name (v2 suffix). Then I assumed I could just change the source schema in my existing map, but that does not look possible. What is the best way to make such a change? I am hoping to at least copy the current mapping as nothing is changing there...just adding a few new mappings.
Thanks!
Keith
Edited by: Keith Wendel on Jun 4, 2009 10:30 AM

HI Keith
Are you talking of syndication maps?
In import maps we never put the schema. Just connect to the source file and open your old map. on top of this you can do the mappings for the delta fields and save the map with a new name.
thanks
Ravi

Source Data for Import Map

I inherited some MDM work from a consultant who rolled off our SRM project. He did not leave any source input files to use when making changes to maps, and I read in the SAP MDM Guides that you should always revert back to your original source file when making map changes so you don't lose any mappings (if the newer source file does not contain every segment that the original did, etc).
Am I off base? Is there a safe way to make map changes without having the original source file?
Thank you in advance,
Keith

Hi Keith,
You are absolutely right. This is a common problem which is being faced while subsequent loads into MDM. The problem is that generally the Map is created in Import manager and then if more values come in for value mapping or more fields are mapped due to a new business requirement, then the map sometimes throws a problem of Map being out of date.
The solution that we came out for this was a creation of Value mapping template ( you can also include the field mapping). This would have the complete list of fields and values in one map. Also if some new value is getting added, then firstly add in the template and then Map it in the original Map.
Now in your case, you can either go and create a Template or else, use the SAVE UPDATE option present in Import Manager everytime you face an exception via MDIS. SAVE UPDATE will help you update the additional mapping onto the original map and then if a similar file comes in again, it will processed successfully via MDIS.
You can refer to my Article on this:
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/80ad0cff-19ef-2b10-54b7-d4c7eb4390dd
Hope it helps.
Thanks and Regards
Nitin Jain

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

Block port on Value Exception

Hi,
Whenever there is a Value or Import exception,port is not blocked but now customer wants to block the port in case of Value Exception as there can be scenario where a record is updated in the source system but due to some issue it failed under value exception. A different user updates the same record in source system and it pass through MDM correctly. Now some one will check the value exception and process the record manually which will overwrite the changes .
Kindly suggest if there is some method to block port in case of value and import exception.
Thanks and Regards,
Neethu Joy

Hi Neethu
As rightly explained blocking the port for Value and Import exceptions is not possible.
Now coming to the initial requirement- *there can be scenario where a record is updated in the source system but due to some issue it failed under value exception. A different user updates the same record in source system and it pass through MDM correctly. Now some one will check the value exception and process the record manually which will overwrite the changes .
Why should this happen- For the lookup values how are you refreshing MDM from the source system? If this is not automated the above makes a scenario for automatically refreshing the lookup values from the source system to MDM.
Also if the User1 is wrongly editing a record in source system MDM by design is not allowing to import that record. User2 edits(corrects) the record in source system again which is reflected in MDM correctly. Here if the client needs to see the changes made at record level (by user1/all incorrect updates) then the change tracking or logs should be seen/developed in the source system itself- since MDM has been designed to filter correct records flow only.
Hope this helps-Ravi

Import action Update vs Replace in workflow

Hi! Is it true that we should be using import action Update (all mapped fields) when processing data updates via import manager?
I found that if I set the impact action to Replace and when I run my workflow which does a check on old and new value (for price), the validation will fail. This is because the old and new value will be the same. However, if I use Update action, then the system will retain the old value. I find it strange that on checking out that the system is not retaining the old value of the data (regardless of whether I am using Replace or Update action).
Can someone please clarify?
Thanks!
SF

Hi SF,
Replace Import action will Replace the old value with the new Value so their is no information of the Old value as the old value is now replaced with the new value.
In case of Update All mapped fields the system will Update the old values with the new values as per the new source file and so not all the records field values will change .Only the incoming records which have updated values in the source file will update all the mapped fields with new values.
In any of the case only the lates value will be saved under that particular field for the records so tracing the old and new values is not possible.
Even the workflow is always triggered after the record is already updated/Replaced in MDM and after the record is created they get checked out.
Note: In case you are using MDM 5.5 , Excel source file cannot be used with the Replace Import Action.
Hope it helps
Thanks & Regards
Simona Pinto

R/3 u2013 XI u2013 MDM integration scenario - Standard import Maps problem

Hi Data Masters,
We are working on R/3 u2013 XI u2013 MDM integration scenario for Vendor Object. We have extracted main table Data using u201CMDM_CLNT_EXTRu201D program. Now while importing the data in MDM we want to use u201CStandard business content i.e. Standard Import Maps (Name u2013 cremdm - 03 u201D but this maps are not mapping all the fields. So do we need to extend this maps..??
OK. Second, To create own maps we are facing following problems,
1) In source section many fields are reflecting twice means in two segments i.e. LFA1 and ADRMAS like Name, City, Street, country etcu2026 whereas in Target section we have one field for the same so how to maps this fields.
2) In source, There are few fields like ADRNR which have values but in target we donot have any fields to map for the same, so how to handle thisu2026
Helpful answers will be rewarded,
Cheers
RC

closed

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

Import map issue one record at a time

Hello Experts,
I built an import map to run it manually with import manager, but when I click on Ready to Import, the import manager is doing one record at a time. I have to go back to the match tab and refresh in order to import the rest.
Any idea where to setup a setting to import all records at once?
Thank you very much for your help,
Claudia Hardeman

Hi Claudia,
Please check if your matching criteria results in fewer records,what is the matching criteria you are setting?
Do you see a total of 300 under "Create" Match Action?
No of records to be imported is governed by Match action which tell the MDS which are distinct records,Match Action tells MDS what is to be done with this number of records which have this Match type.
Please check if you have "SKIP" as match action,if yes use a appropriate action for match type.
Do a "Save Update" of the map.
Please revert with results.
Thanks,
Ravi

Exception during mapping Execution

Hi Experts
an Matmas05 xml is coming from MDM system. & it should be posted as Matmas05 in R/3.
i imported the MDM content in IR. but the fields order in coming Matmas05 xml file and the fields order in
Matmas05 Idoc are Not same.
while Executing Mapping it throws 'Exception during mapping execution'
so pls give solution How can i solve...this error
pls ....urgent.
thanks & regards
swapna

HI swapna,
The XMl coming from MDM have the different sequence than the original Matmas05 IDOC that you have imported in IR,.
Lets take it this way as the Original Matmas IDOC structre is not matched up with the sender side Structure.
You can change the sequence of IDOC XSD file with some tools like Altova xmlSpy and make it same as sender side. Then import the modified XSD file as external defination and use it on sender side.
On Receiver side your Matmas05 structre sequence should have to be original one.
Now map the corresponding fields and execute the scenario.
thanks
Swarup

Value Exceptions - Import Map Update

Similar Messages

Maybe you are looking for