Issue creating qualified tables in MDM 5.5 SP04 Console

Try the following:
1) Make sure you are using SP04 Patch 1 (Build 5.5.33.13)
2) Unarchieve one of the supplied business content repositories (Eg. Customer, Material, etc).
3) Create a flat lookup table
4) Create a qualified table with only one field: Field type lookup flat referencing the flat lookup table created in step 3, non-qualifier, display field.
5) Create a new field in main table, type qualified multi-value, referencing the qualified table created in step 4.
6) Load the repository
7) Login to repository with data manager
8) Create 1 entry in lookup table created in step 3
9) Create 1 entry in main table, also creating 1 sub-entry in qualified table, save the record with SHIFT-ENTER
10) Make sure the record was saved, including qualified table entry
11) Close data manager
12) Open data manager again
13) Select your record and try to go in to the qualified sub-entry
In my case this produces data manager to crash.
This does not happen for qualified tables created in SP03 and updated to SP04, only for tables created directly in the SP04 console.
Please let me know if everybody is having the same problem.

Hi, Jorge,
I have MDM5.5 SP4 P1 HF1 and followed your steps (except in step 4 (THANK YOU for numbering them), I have more than one field.) At step 13, I selected my record and to my amazement the record was there but my qualified table data was gone. And I then performed your step 14, and opened the qualified lookup table, and again to my amazement the console crashed.
This definitely appears to be a bug and you should report it. I will also see if I can ask around for other solutions.
Kristin

Similar Messages

  • How To create Taxonomy Tables in MDM

    Hi all,
    I am new to MDM and want to know how to create Taxonomy Tables in MDM data manager for the various available categories and attributes.
    Regards,
    Gavin.

    Hi Gavin,
    Here's a solution.
    1. Create a calculated field of type boolean - you can name it On-Site or something similar.
    2. Enter the following as the calculation expression
    IF(HAS_ANY(COUNTRY_FIELD_NAME, "country 1", "country 2", "country n"), TRUE, FALSE) - where country 1...country n are the countries that are on considered On-Site. 
    All Vendors from countries you have listed in the expression will have the value TRUE for the field On-Site.  All other Vendors will have the value False.  This way you can separate the 2 groups of Vendors by searching on the field On-Site.
    Hope this helps,
    Richard

  • Mapping issue with Qualifier table

    Hi,
    1. I have an issue after mapping all 3  non-qual flds of a qualifier table in main table getting the compound fld enabled but selecting it , not mapping automatically to the appropiate compound field in the destination side, but giving an error message
    "unable to retrieve source record".
    2. The second issue is that after mapping some of the fields and qualified table and loading the maintable data, saving the map but subsequently when trying to open the saved map , it is coming out with the usual main error window
    SAP MDM Import Manager
    SAP Import manager has encountered a problem and needs to close.
    We are sorry for the inconvenience.
    Debug                                          Close
    Appreciate your help/suggestion on this issues.
    regards
    -reo

    Answer for Qn2:
    First you have to map all the display fields to individual Source Fields..
    Once you have mapped all the dispaly fields of the Qualified Table, you have to do value mapping for the Fields that require Value Mapping.
    Ex: Source Field A -> Destination Display Field 1
    Source Field B -> Destination Display Field 2
    Source Field C -> Destination Display Field 3
    Now Value Mapping where required should be done.
    Once the value mapping is done, then you can create a Compound Field.
    If you have done the previous steps correclty, then the compound field name is enabled for you to create Compound Field.
    Now map the newly created Compound Field to the Qualified Lookup field of the main table.
    Now you have to click on the Automap for value mapping.
    Hope this helps.
    Please reward if you find this helpful

  • How to add record in Qualified table using MDM Java API

    Hi experts,
    I am trying to add a record into a Table.
    but I am facing the problem in setFieldValue method.
    //Getting Field-ID to pass in setFieldValue() method.
    FieldId[] fields = new FieldId[6];
              fields[0] = repSchema.getFieldId("GTINs", "Description");
              fields[1] = repSchema.getFieldId("GTINs", "Unit_Descriptor");
              fields[2] = repSchema.getFieldId("GTINs", "GTIN");
              fields[3] = repSchema.getFieldId("GTINs", "Alternate_Item_Classifications");
              fields[4] = repSchema.getFieldId("GTINs", "Country_Of_Origin");
              fields[5] = repSchema.getFieldId("GTINs", "Bar_Coded");
    Record rec = RecordFactory.createEmptyRecord(mainTableId);
    rec.setFieldValue(fields, );
    but I am not getting how to assign the value to these fields using MDMvalue Interface.
    Can anyone provide me the code sample or Code flow so that I can do this.
    Plz help me it'll be great help for me.
    Thanks
    Tarun
    Edited by: Tarun Sharma on Feb 4, 2008 11:39 AM
    ==========================================================================================
    Hi Gurus
    I found the way to add the MDMValue in setFieldValue Method.
    we can set like this:
    setFieldValue(<fieldId object like fieldId[], <MdmValue like this> new StringValue("ABC"));
    Now I am facing problem in adding value to lookup flat table.
    According to the setFieldValue method we can assign the loookup like this:
    setFieldValue(<fieldId[0]>, new LookpValue(<here we have to pass the recordID of lookup table>);
    so I want to know how I can pass the recordId of lookup table here.
    Please suggest.
    Thanks
    Tarun Sharma
    Edited by: Tarun Sharma on Feb 4, 2008 3:15 PM
    Edited by: Tarun Sharma on Feb 4, 2008 3:25 PM
    Edited by: Tarun Sharma on Feb 8, 2008 6:58 PM

    Hi Andrea,
    I tried your suggestion but now i am getting Type Mismatch Error.
    Please suggest me what I can do?
    //TableId for Lookup[Flat].
    TableId lookupTableId = repSchema.getTableId("Return_Goods_Policies");
    FieldId[] ReturnGoodsPolicyTableIdFields = new FieldId[1];
    ReturnGoodsPolicyTableIdFields[0] = repSchema.getFieldId("Return_Goods_Policies", "Name");               
    Record recLookup = RecordFactory.createEmptyRecord(lookupTableId);
    try{
    recLookup.setFieldValue(ReturnGoodsPolicyTableIdFields[0], new StringValue("New_Brand"));
    }catch(Exception ex){
    System.out.println(ex);
    //Creating Record in Qualified Table - Request Details
    CreateRecordCommand createLookupcommand = new CreateRecordCommand(simpleConnection);
    createLookupcommand.setSession(session);
    createLookupcommand.setRecord(recLookup);
    createLookupcommand.execute();     
    //Getting the recordId of Lookup record.
    RecordId lookupRecordId = createLookupcommand.getRecord().getId();
    //Table Id for Qualified table.
    TableId  qualifiedTableId = repSchema.getTableId("Ext_Hardlines");
    FieldId[] ExtHardlinesFields = new FieldId[3];
    ExtHardlinesFields[0] = repSchema.getFieldId("Ext_Hardlines", "Name");//Text
    ExtHardlinesFields[1] = repSchema.getFieldId("Ext_Hardlines", "Pieces_Per_Trade_item");//Integer
    ExtHardlinesFields[2] = repSchema.getFieldId("Ext_Hardlines","Return_Goods_Policy");
    Record recQualified = RecordFactory.createEmptyRecord(qualifiedTableId);
    try{
    recQualified.setFieldValue(ExtHardlinesFields[0], new StringValue("Qualified Value"));
    recQualified.setFieldValue(ExtHardlinesFields[1], new StringValue("Qualified Description"));
    recQualified.setFieldValue(ExtHardlinesFields[2], new LookupValue(lookupRecordId));
    }catch(Exception ex){
    System.out.println(ex);
    //Creating Record in Qualified Table - Request Details
    CreateRecordCommand createQualifiedCommand = new CreateRecordCommand(simpleConnection);
    createQualifiedCommand.setSession(session);
    createQualifiedCommand.setRecord(recQualified);
    createQualifiedCommand.execute(); I am getting this Type match here, but i m not getting what mistake i did.     
    RecordId qualifiedRecordId = createQualifiedCommand.getRecord().getId();
    //Adding to Main Table
    TableId  mainTableId = repSchema.getTableId("GTINs");
    FieldId[] gtinsFields = new FieldId[1];
    gtinsFields[0] = repSchema.getFieldId("GTINs","Ext_Hardlines");
    Record recMain = RecordFactory.createEmptyRecord(mainTableId);
    //Adding the new record to Qualifed Lookup value and setting the Yes Qualifiers
    QualifiedLookupValue qualifiedLookupValue = new QualifiedLookupValue();
    qualifiedLookupValue.createQualifiedLink(qualifiedRecordId);
    try{
    recMain.setFieldValue(gtinsFields[0], new QualifiedLookupValue(qualifiedLookupValue));
    }catch(Exception ex){
    System.out.println(ex);
    CreateRecordCommand createCmd = new CreateRecordCommand(simpleConnection);
    createCmd.setSession(session);
    createCmd.setRecord(recMain);
    createCmd.execute();
    Could you help me out?
    Thanks
    Tarun

  • Search on a Qualify Table using MDM Webservices

    Hello
    I´m trying to use the standard MDM 7 webservice to search records in a Qualify Table and I´m having some problems.
    When I try to search records in a non-qualify table, it works perfectly, but when I search on a qualify table, I get the following result:
    repository_3001-Error executing Search Records on repository MY_REPOSITORY, error code , caused by Qualifier values are not part of a qualified lookup record
    I´m filling the following fields:
    parameters/query/criteria/manufacturer/LogicalOperation: AND
    parameters/query/criteria/manufacturer/constraint/element1/value: (blank to return all records)
    parameters/query/criteria/manufacturer/constraint/element1/expression Operation: CONTAINS
    parameters/resultDefinition/fieldListType: ALL
    ..and the repository information...
    Thanks.
    Vitor Zaninotto

    Solved..
    I cannot use parameters/resultDefinition/fieldListType: ALL, I must set the non-qualifier fields only.

  • Issue in Mapping Qualified Table in Import Manager

    Hi Experts
    I have extracted Customer data from R/3 ECC, I could successfully loaded reference data, but when trying to load Main table data (Using DEBMDM06 MAP) I am getting mapping issues with Qualified table (Sales Data and Bank Details).
    Error Messages
    Map 'Sales Data' field to import qualifier(s)
    Map 'Bank Detals' field to import qualifier(s)
    I have checked and found that all the field and value mapping is in place, If i remove mapping for the qualified table fields then the data is ready to import.
    What is the issue, and how do I import Qualified Table data.
    Appreciate your inputs
    Gaurav.

    Hi vickey ,
    Kindly go through the below link it will help you understand better the mapping the workinga nd importing of Qualified tables:
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00a15239-684e-2b10-b8ae-b936b7d1c1fe
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c03240fa-cc3e-2b10-aa9a-a5798e319a6e(Qualified importing with main table)
    Hope It Helped
    Thanks & Regards
    Simona Pinto

  • Unique key for Qualified tables

    Hello Experts,
    We are currently facing an issue with qualified tables. We need to retain existing system keys as below:
    Item (Main table)
    Item_Id, Item_Number
    Item_Price (Qualified Table)
    Item_Price_Id, Item_Id, Price_Type_Id, Price
    E.g.
    1, Pencil
    2, Pen
    3, Notepad
    1, 1, Retail_Price, $10
    2, 1, Wholesale_Price, $5
    3, 2, Retail_Price, $15
    4, 2, Wholesale_Price, $10
    We need to migrate the existing ids (Item_Price_Id) in MDM qualified table and need to maintain the same as max(Item_Price_Id) + 1 for all future records.
    Is there a way we can achieve this?
    Your help is greatly appreciated.
    Thanks in advance,
    Vinay

    Hi Karol,
    The Interface Iprinciple has this function as it:
    Gets the unique identifier which unambiguously identifies the object's <b>principal type and principal's data record</b>(s) in the data store (e.g. a relational database).
    <b>Note: the unique ID is a case sensitive string</b>
    Use this identifier to keep and persist references to principals. As this identifier contains internal information and is usually not readable, it should not be displayed in user interfaces.
    UME implementation guarantees to return Strings which are not longer than 255 characters.
    <b>Returns:</b>
    a non-null String identifying this principal
    I hope this helps you.
    Regards
    Pravesh

  • Not able to Populate Qualified Table in Import Manager

    Hi,
    I am performing following steps for populating Bank Detail Qualified table in MDM from R3 but not able to populate the data.
    1.Populating all lookup tables like Account_no,Bank-Key.......
    2.Mapping all fields in Bank detail table except the 'Collect Auth'
    field which is Qualifier
    3.In Customer table(Main) mapping  Collect auth to Bank Detail field and
    customer_no to its corresponding ID.
    It is not populating the Bank detail data which are available in lookup tables
    Appreciate your suggestion
    -regards,
    reo

    Reo
    Matching will be based on the Display field (at least one) of the Main table.  This is for example the Customer Number.
    You also need to map all the display fields of the qualified lookup table. Then you can set the Qualified Update Action by right clicking on the field in the main that is linked to the qualified lookup.(the Collection_Authorization I think). Set the option that well update/append/replace the qualified data fields of the looked table.
    There is two how_to_guides that will help. You can download from SAP Service Market Place. (Otherwise I can email to you)
    How To Troubleshoot MDM Import Manager
    HowTo_LoadQualifiedFields
    Rgs
    Con

  • Qualified table concept

    Hi,
    I want to discuss, the concept of Qualified table in MDM 5.5.
    Now, in my repository I have main table Business Partner which has a Lookup field Tax Number which is Lookup(Qualified-Flat) (multi-valued).
    There are 2 fields in this table which are both Display field.
    Tax Number is a Qualifier and Tax Number Type is Non-qualifier.
    Now, for a record in Business Partner in Qualified Lookup field Tax Number, there are 4 values.
    Tax Number Type| Tax Number
    Permanent | 840987
    Temporary | 432
    Temporary | 432
    Permanent | 5432
    Now, according to Qualified table concept: For each association of Business Partner Record with Tax Number Type: Permanent or Temporary.
    There should be a Tax Number as Qualifier. But it need not be unique. Then, the significance is, it as an association with the Tax number type.
    Now, if we see from MDM point of view: The non-qualified value need not be duplicate.
    So, my data is wrong but the values are Ok.
    Regards
    Kaushik Banerjee
    Edited by: Kaushik Banerjee on Oct 14, 2008 12:46 PM

    Hi Kaushik,
    Tax Number Type| Tax Number
    Permanent | 840987
    Temporary | 432
    Temporary | 432
    Permanent | 5432
    Two things I would like to share:
    - When you select any data to be fit for saving in a qualifier table,you need to understand it very well.As given in your above example,Tax no type is the non-qualifier determing the Qualifier tax num.As far as i understand this data,it would not be absolutely correct to say that the Tax num type alone can determine the tax num.You can have all tax numbers either Permanent or temporary,but this alone cannot determine the tax number values.what i mean is that by jsut classifying the number as permanaent or temporary you cannot say the num to be so and so.In thsi case if you are saving this kind of data in a qualified table you may need another field to detrrmine the Tax num and the combination of the two of non qualifier field will decide the qualifier for all incoming records.
    - When you import the qualified tabe,you will map the non qualifier.In this case out of your 4 non qualifier values only 2 will enter MDM as the matching field is tax num type and there are only two distinct values in this field.So in that case you will have two unique non qualifier values which will determine the qualifiers accordingly for all main table records
    Hope It Helped
    Thanks & Regards
    Simona Pinto

  • How to create a unique group field in Qualifier table

    Hi,
    I am trying to use a qualified table in Product maintable like "Site items".
    However I would like to have two non-qual field in that like 'Plant' and 'item#' which should be an unique combination.
    I have tried to create a table(X) with the above two fields with display and another table (Y)that uses the table X for lookup (site-item) so as to make it dispaly and unique both. However when i am using this Y table as a lookup for the qualified table(site items) , not able to load data.
    Error message:
    "Import failed. Unable to find source column index for 'Site Item ID' field"
    Another issue also not able to populate data for the qualified flds even if when able to load data without making a group unique field for this qualified table.
    In MDM 5.5 sp4. Thanks in advance for any tips.
    -reo

    Hi Beena,
                    In the above post of mine I suggested you to use STRING data type.
    As you are telling that when creating TABLE MAINTANENCE GENERATOR you are
    getting an error saying that " Datatype STRING is not supported ". I tried this, what you said is right.
                      After your reply I did research on this and I also met my heads,
    The conclusion is <b>IT IS NOT POSSIBLE TO GENERATE TABLE MAINTANENCE</b> for the table which is using STRING type. At last I can give you one suggestion, i.e., In the short text of that field write STANDARD TEXT name.So that whenever you want, go to this standard text, but the problem is you have to maintain it manually.
    <b>Reward all helpful answers.</b>
    Regards,
    V.Raghavender.

  • SRM-MDM Catalogue Search UI - Qualified table search

    Hi,
    We are having the following situation:
    - We have a catalogue of articles
    - We have to tie an article to a location, in addition to a location-specific parameter.
    - Exampe:
    Article A is tied to location A, parameter A
    Article B is tied to location B, parameter B
    Article C is tied to location A, parameter B
    - The way to solve this in MDM is to use the qualified table. I have created one where:
    Location = non-qualifier
    parameter = qualifier
    I want to make this searchable in the SRM-MDM search UI.
    The user should be able to choose one Location, and then one parameter tied to that Location, to view relevant articles.
    This is no problem using SAP Portal with MDM. But how can we realise this using SRM-MDM search UI?
    I have tried, but can only get a drop down or text search on the non-qualifier field.
    Can anyone please help? Is this even possible?
    KR;
    Thomas

    Hi Thomas,
    Is there any possibilities to configure/add code to the search UI, or is this completely locked for customization/altering through code? Unfortunately, I feel it is standard and we can not customize it.
    There is no issue in your design but if your location as well as parameter has certain(limited) number of values only. You can create location field in MDM Main table which is lookup to Locations Flat table and similarly for Parameter field lookup to Parameters table rather than using Qualified table. As you can set lookup/Text field search only, so you can set these two fields in your search criteria. where first you search for Location say US it will search records with US location and when you further give search according to parameter it will further filter(navigate) records based on both Location and parameter, just a thought came which i feel to share with you, try it if it helps you.
    Regards,
    Mandeep Saini

  • Import  issue with Auto-id in Qualifier table

    Hi,
    I am trying to load Customer_contact table in MDM5.5 sp4 from R3.
    Since SAP-Id is generated in R3, initially portal will send all data to R3 w/o SAP-id but with the MDM-Auto-id.
    In return from R3,MDM receives the SAP-id and Contact-id against this MDM-id for update.
    In conversion,I am getting "Error in Look uptable" "Internal Error"  message to load this file in Main table.
    Is there any workaround to map qualifier table with a auto-id in Main table?
    This auto-id needs to be non-qual for portal to create the initial record in MDM.But since this is a non-qual fld and we are not able to map it in main table giving "Internal error" . It is my guess.
    Appreciate your idea and help
    -reo

    The issue was fixed after dropping the calculated fld as Non-qual one which was giving problem since required to be mapped in Main table.

  • Qualified Table getting a blank row in MDM 7.1

    Hi All,
    We are implementing MDM 7.1 and have created custom repository with multiple main table. We have also few qualified tables.
    There is only one non-qualifier in all the qualified tables. The values are u201CAu201D (Active) or u201CIu201D (Inactive).
    For example:
    We have a qualified table called company group, where we store the groups to which a company belongs.
    The import is through import sever and xml file is the input.
    When there are no values for the group at the source system, we will not receive the XML tags for the group and we will receive xml tags for other data. The non-qualifier value u201CAu201D will also be part of the company group values from source.
    The expected functionality is import server should ignore the company group table in total while importing through import server, as there is no xml tags for group.
    We are getting a qualified row with only non-qualifier value u201CAu201D and rest of the values as blank.
    Kindly provide suggestion to resolve this.
    Regards,
    Arul Manickavel

    Hi Arul
    Try using "Update" or "Replace" in the Import Map for the Qualified field mapping's "Set Qualified Update" option.
    Regards
    Varun

  • Qualified table search in MDM

    Hello All,
    I am trying to do drill down search in Data manager on qualified table.
    when in search critieria i am selecting qualified table ,I am not getting all qualifiers in search tab.(we have 6 qualifiers and i am only getting 3 of them )
    and in values as well when i am selecting say for
    qualifier                  Value
    country                  USA
    if i am selecting this combination i am not getting any records whereas there are more than 1000 records of country USA .
    any suggestions.!
    Kunal

    Hi Kunal,
    Check the below statements from MDM Reference Guide and check whether you have designed the repository in the same way or not.
    It permits drilldown search by qualifier lookup values even before you have selected a single qualified table record in the qualified lookup field search tab.
    It permits free-form search by qualifiers (both lookup and non-lookup) when Sort Index is enabled.
    In above statements "It" is nothing but when you enable the Cache property of qualifiers.
    Kindly update us on your issue.
    Regards,
    Jitesh Talreja

  • SRM MDM - Multiple hyperlinks import into qualified table

    Hi,
    I need to create an import map where I can import two hyperlinks (URL2 and URL3) into the Hyperlink qualified table.
    How can I achieve this?
    I have an XML schema where the two hyperlinks are given in separate tags:
        <URL2>http://www.test.net/xxxx</URL2>
        <URL3>http://www.test.net/yyyy</URL3>
    Can anyone provide me with a HOW-TO for how to map these two tags into the qualified table Hyperlink.
    Maybe I should create two sections in the XML?
    <URL2>
    <MIME Type>URL</MIME Type>
    <URL>http://www.test.net/xxxx</URL>
    <URL Description>TEST URL</URL Description>
    </URL2>
    <URL3></URL3>
    KR,
    Thomas

    Thank you very much. This worked fine.
    Now I have another problem someone might be able to help me with.
    The sending system does not wish to send a repeating XML tag with the two hyperlinks. It causes restrictions in the data amount that can be sent.
    We see two possible solutions
    1.
    Building the hyperlinks in MDM, like a calculation.
    <URL2>http://www.test.net/xxxx</URL2>
    <URL3>http://www.test.net/yyyy</URL3>
    xxxx and yyyy are values in fields we have in the MDM structure. Everything before this in the hyperlink is always the same.
    Is it possible to create the hyperlinks based on the value of xxxx and yyyy? If yes, how could we manage this, also filling the fileds: URL Description, Hyperlink Type and MIME Type with correct information?
    2.
    PI can create the URLs during integration.
    Which of these two should we use?
    KR,
    Thomas

Maybe you are looking for

  • Adobe Air install problem

    Hello all,                               I don’t know if anyone can help me with my problem but from what I’ve read on this forum it’s not completely unlike a problem other people have had. . I have tried completely uninstalling and re-installing ado

  • E4x - Variable is not defined

    Hi all, I built an AIR app to store the contact info everyon in my office. The data comes from an XML file and it was all working until I started tinkering and broke it. To trace the problem I built a 20 line test app but still cant get it to work. I

  • Save Data from multiple frames

    Hi to all, I am very new to Java... What I want to do is to save the data entered in textfields and selected in comboboxes from various frames in my application in one single text file. Is that possible? Thanking in advance sotirios

  • How to Mantain Current View

    Hello Experts, I saved the Input Shedule with Year 2011 and version Budget. The problem is that sometimes I open my Input Schedule and the Year and Version changes to other values. Do you know why this appenned? There are any way I can fix the Year a

  • Which pass word is required to boot itv

    have set up apple tv to recognise wirless modem not sure which pass word to use apple id?? or wi fi ----- pass word