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

Similar Messages

  • 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

  • Updating Qualifiers using import manager

    I am having difficulties with updating my data in qualified lookup tables. I have a qualified lookup table Produkt Market Data with market as a display field (hierarchical lookup).
    All other fields in this table are qualifiers, most of them multi valued. I have loaded the non multi value fields in the table first, so there is an entry for eg product 4711, market Health Care.
    When i try to update a field text (multi valued flat lookup) using the import manager, the record 4711-Health Care is not updated but a lot of entries 4711-Health Care are created extra, each of them containing one line of text. I used the option update all mapped fields (and have mapped only product, market and text). When I choose the option update Null fields only, nothing happens: only the lookup table for the text is updated.
    can anyone tell me what i am doing wrong. It should be possible to update qualified fields using the import manager instead of creating new entries shouldn't it??
    Regards,
    Bert

    Hi,
    See the below example.
    HeirarchyT [Hierrachy Table]
    Name Text[5]
    Data in Hierarchy Table
    Hier1
    -H1
    --H3
    -H2
      --H4
    MainT[Main Table]
    Field1[Text5]
    QField1[Lookup Qualified multivaled]
    LT1 [ Flat Table 1]
    NameLT1 Text[100]
    CodeLT1 Text[2]
    Data in this Table
    LT1Val1  LT1Code1
    LT1Val2      LT1Code2
    LT1Val3  LT1Code3
    LT1Val4  LT1Code4
    LT2 [ Flat Table 2]
    NameLT2 Text[100]
    CodeLT2 Text[2]
    Data in this Table
    LT2Val1  LT2Code1
    LT2Val2      LT2Code2
    LT2Val3  LT2Code3
    LT2Val4  LT2Code4
    QualTable[Qualified Table]
    QH1 Lookup[hierarchy]
    No(Qualifier) Yes(DisplayField)
    QMLV1 Lookup[Flat]
    Yes(qualifier) LookupTable[LT1]
    Yes(Multivalue)
    QMLV2 Lookup[Flat]
    Yes(qualifier) LookupTable[LT2]
    Yes(Multivalue)
    Intial data in the repository:
    Record 1: N1
    Qualified Data:
    QH1 : H3
    QMLV1: LT1Val1,LT1Val3
    QMLV2: LT2Val2,LT2Val4
    Record 2: N2
    Qualified Data:
    QH1 : H4
    QMLV1: LT1Val2,LT1Val4
    QMLV2: LT2Val1,LT2Val3
    Lets say u have source data in Excel sheet like below.
    N1     H4     LT1Val2,LT1Val4          LT2Val1,LT2Val3
    N2     H3     LT1Val3,LT1Val1          LT2Val2,LT2Val4
    Follow the instructions given by Rajani till step 5.
    In the Step 6 selct The default import action as <b>"Replace".</b>
    I hope this helps.
    Thanks and Regards
    Subbu

  • 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

  • Create key mapping using import manager for lookup table FROM EXCEL file

    hello,
    i would like create key mapping while importing the values via excel file.
    the source file containing the key, but how do i map it to the lookup table?
    the properties of the table has enable the creation of mapping key. but during the mapping in import manager, i cant find any way to map the key mapping..
    eg
    lookup table contains:
    Material Group
    Code
    excel file contain
    MatGroup1  Code   System
    Thanks!
    Shanti

    Hi Shanti,
    Assuming you have already defined below listed points
    1)  Key Mapping "Yes" to your lookup table in MDM Console
    2) Created a New Remote System in MDM console
    3) proper rights for your account for updating the remote key values in to data manager through import manager.
    Your sample file can have Material Group and Code alone which can be exported from Data Manager by File-> Export To -> Excel, if you have  data already in Data Manager.
    Open your sample file through Import Manager by selecting  the remote system for which you want to import the Key mapping.
    (Do Not select MDM as Remote System, which do not allows you to maintain key mapping values) and also the file type as Excel
    Now select your Soruce and Destination tables, under the destination fields you will be seeing a new field called [Remote Key]
    Map you source and destination fields correspondingly and Clone your source field code by right clicking on code in the source hierarchy and map it to Remote Key if you want the code to be in the remote key values.
    And in the matching criteria select destination field code as a Matching field and change the default import action to Update NULL fields or UPDATED MAPPED FIELDS as required,
    After sucessfull import you can check the Remote Key values in Data Manager.
    Hope this helps
    Thanks
    Sowseel

  • Error in Import Manager if Constraints are assigned to lookup table

    Hi Folks,
    I am using the Repository SRM-MDM Catalog...and in the Console,
    For a Role, if I assign a Constraint for the lookup-table Product Groups, System shoots the error message in Import Manager when I try to Map the file.
    Scenario: Say I have Product Group from LOC1-LOC5, and for a Z-Catalog Manager Role(Manager1) if I assign the Constraint-LOC1.....and if I Import a file in the Import Manager, system shoots the error message "Unable to retrieve Unique values for Product Groups".

    Hi Mohan,
    Are you updating any Qualified table.Please explain what table and also some more details.
    Thanks
    Ganesh Kotti

  • How to import data usin Import manager if one of the field is of type LOOKUP[FLAT].

    Consider a scenario:
    Where I created a Main table named STUDENT and it has 4 fields,
    a) Among which 2 fields are OF DATA TYPE TEXT[50] and
    b) Remaining two are of DATA TYPE LOOKUP[FLAT] and corresponding look up table also created in the repository.
    When I tried to create a file with certain input records and tried to import the values into the Main table using MDM IMPORT Manager, I am getting error at the IMPORT STATUS tab with the action item message: MAP 'FILED NAME OF LOOKUP[FLAT] TABLE' FIELD VALUE(S).
    Do I need to do any special action to import record if the field is of data type LOOKUP[FLAT].
    Please advice.

    Hi,
    Since you need to import value into a field which is referred by a flat look table, you need to map the values of that field to the values maintain in flat look up table.
    You can do the mapping from "Map Fields/Values" Tab.
    You have probably Mapped Source fields with destination fields, but in case of importing values in lookup fields you need to map Source Value with destination value.
    Keep the cursor on the required lookup field in Source field section, below that section you will be able to see Source Value section perform the mapping in that section too and it will resolve your issue.
    Regards,

  • 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

  • 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

  • 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 <b><i>Conversion Filters</i></b> 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 <i>Apply Conversion Filter</i>. You can these choose an appropriate filter like <i><b>Replace</b> and eliminate/replace source field value with/by blank space</i> followed by <i><b>Apply Operator --> Prepend</b> and then specify your fixed value 'XXXX'</i>.
    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

  • 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

  • Lookup query to get Manager ID value on object form

    Hi ,
    I have created a Manager ID field on object form which is of type lookup field.
    Can any one please tell me that how can i write Lookup query to get Manager ID value on object form.
    Thanks in Advance

    I was looking for something like this today too.
    Here's what I came up with:
    SELECT fu.user_id, fu.employee_id, fu.user_guid, pe1.full_name, pe2.full_name SUPERVISOR, pe2.employee_id
    FROM fnd_user fu
    JOIN per_employees_x pe1 on pe1.employee_id = fu.employee_id
    JOIN per_employees_x pe2 on pe2.employee_id = pe1.supervisor_id
    WHERE fu.user_id = $(user_id)
    Edited by: user12232265 on Feb 24, 2010 3:20 PM

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

  • Import Manager and Display Fields

    I've been using SRM-MDM 3.0 for a couple of months and 1 fundamental MDM design has always bothered me and I was hoping to get some resolve on this.
    The purpose of Display Field is 2 folds:
    1. Display the field in the Catalog Search UI for a lookup table: i.e. if both Supplier Name and ID are Display Fields, then in the Search UI, both fields are displayed to the end-user. If only Supplier ID was the display field, then in the UI only the ID is displayed.
    - From a usability pov, tables such as Supplier and Product Group should have the name or description fields displayed in the Search UI as the numeric values are meaningless to the end-users. 
    2. Display field ALSO affect what is the key used to import data into a table.  So if Supplier ID is the display field for Supplier table, then in Import Manager, the Supplier ID values are displayed and must be mapped to the source values.
    - From an importing pov, mapping values should always be an index-like field, such as Supplier ID or Product Group ID, or ISO, and usually never the actual name or description field.
    But SAP has tied the two together. So in order to display the name/description to the end-user, we must enable the name/description field as a Display Field.  But we also want to map based on the index/ID field, so we also enable the index/ID field as a Display Field.  Now in Import Manager, we have two Display Fields for a table (i.e. Supplier ID and Supplier Name for Supplier table) and I've noticed some issues with this:
    1. You import file must have BOTH values (index/ID and the name/description fields) in the source, in order to Automap.  If your source file only has 1 field, like in MECCM when extracting  ECC contract, ONLY the Supplier ID, or Category ID is extracted, Automap is not possible.  What is funny is that standard SAP extract program only extracts the ID fields, BUT the standard SAP repository has the name/description fields as the Display Field.  Automap is a must for tables like Product Group where hundreds of lines can make manual mapping a pain.
    2. I also noticed you cannot Add values to a table that has 2 Display Fields, you can only map to existing values.  The Add button is grayed out.
    With all that said, when you're replication ECC Contract Data using MECCM, for tables like Supplier and Product Group, what fields should be set as Display Fields, and if there are multiple Display Fields, what special setting needs to be done in Import Manager to enable automapping?  Even standard SAP Import Map (_MDMContractDataTransmission_ProductID) throws errors when multiple fields are set as Display Fields.
    I'm not familiar with the partitioning function, and I've seen PDF's about it, but don't really see how it could be helpful. I've also read someone suggesting changing the DF's before import, which I think is unacceptable, as this requires unloading/loading repositories everytime an import happens.
    Thanks for reading my paragraph and any input is greatly appreciated.
    Edited by: Derek Xu on Apr 30, 2009 6:50 PM

    Hi Derek,
    Thanks for writing your thoughts. I would like to provide some information on one of your points where in you have mentioned that :
    You import file must have BOTH values (index/ID and the name/description fields) in the source, in order to Automap. If your source file only has 1 field, like in MECCM when extracting ECC contract, ONLY the Supplier ID, or Category ID is extracted, Automap is not possible.
    I completely agree that if you have 2 fields in MDM repository and you are only importing only one of them, then you cannot use the Automap feature of Import Manager. So in your case, the description is not getting importing, so you cannot use Automap in that case.
    I had a very similar requirement in one of my project and we went with creation of a Import Value template. We created a template with all the possible values for all the look up tables in that and mapped it once in the Map. Hence, next time, the Map was used to automatically Map the source and Destination values for all the look up tables.
    SAP-MDM Automatic Import Requirement u2013 Creation of a Value Mapping Template:
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/80ad0cff-19ef-2b10-54b7-d4c7eb4390dd
    Please read the above article and hope its useful. You can go for this approach in your case if suitable.
    I have mentioned examples of descriptions and their respective fields in the article.
    Hope it helps.
    Thanks and Regards
    Nitin jain

Maybe you are looking for

  • How to copy a PDF converter file to my android phone ?

    I have an android phone , and I want to copy a PDF file to my phone , is there someone who knows how to do it ?

  • NLS patch failure and afterwards...?

    Currently, System is running with R12.1.1 on RHEL 5.7 Patch 8576725 applied for language performance as pre-requisite, and 4 languages are merged to be applied. Language license activated in OAM, and Maintain Multi-lingual Tables ran successfully. Th

  • Where is my Search Discussion Field?

    Hi guys, Sorry if I am not at the right place to ask this, but I am really lost. I can't search anything in the Discussions: the Search Discussions Field seems to have disappeared. I feel like a lost soul... Keep up the good work, RTP

  • SLD in DEV

    Hi, We have just one SLD for DEV, QAS & PRD. The SLD is installed on DEV. Are there any risks to have it installed there ? Thx

  • How do I cancel auto debiy on my account?

    How do I cancel auto debit on my account? Website shows no way to do it, even though it says it can be deleted easily.