Unique Field as Non-Qualifier in Qualified Flat Table

Hi experts,
I have the      requirement to store the customer data regarding company code in the qualified flat:
customer have different data related on company code. It's important that this company code have to be unique in this qualified flat. (e. g. one customer have data with company code 3850, 3860 and 3870, its not allowed to store further data with the same company code 3850).
In the console I set the company code as unique and non-qualifierer field. But afterwards I was able to put two records with the same company code in this lookup qualified flat table.
What did I wrong? ( I use MDM 5.5 SP 6 Patch 3).
Best regards,
Nico

Hello,
the behaviour depend of the settings for qualified upadate.
(Set Qualified Update sub-menu when define mapping in import manager)
Settings can be:
- Append
- Replace
- Update
In your, case looks to be "Update". be sure the Set Matching Qualifier is righly set for the qualifier which indentify the relation to the flat data. (sometimes have to clean this point)
Check New links are : Create and Existing Links are : Update (All Mapped Qualifiers)
Hope helps you
best regards
Vincent

Similar Messages

  • Read Only Field in Qualified Flat Table

    Hi Guys.
    After upgrading MDM 5.5 SP4 to MDM 5.5 SP6, fields of the qualified flat table appear as read only in Standard IView Item Details.
    Any ideas ?
    Thanks in advance
    Luciano

    Hi Luciano,
    Have you made sure to upgrade your portal content as well when you upgraded your MDM ?
    As portal SCA files are MDM server version and patch dependent.
    So if you have upgraded to SP06 from SP04 then accordingly you will have to deploy the SP06 version sca files on WAS.
    This will also cause you to recreate your Iviews and pages again as once you undeploy your older version of Sca file from EP their Iview contents and configurations will also be lost.Unless you have used some way of reusing the created iViews.
    So test for these two changes,they could be the possible cause of the qualified fields behaviour.
    Also make sure you upload the rep with update indices and Update repository if you are using an archived version of it from the SP04 version to the SP06 version.
    Hope It Helped
    Thanks & Regards
    Simona Pinto

  • Lookup Flat Table and Lookup Qualifier Table

    Hi,
    Can any body confirm that if I will change the type of lookup-flat type field to lookup-qualifier type field. But the structure of Lookup Flat table and Lookup Qualifier table will be the same then the Java code written to populate the lookup-flat type field will work without any changes with its new type (lookup-qualifier).
    Right now when I run the code after the above said changes, no error comes but no values is assigned to that field.
    Another way to ask this question, can a simple Qualifier Lookup table(without having any qualifier type field) be used as like Lookup flat table.
    I would appreciate if any body can help me in this regard ASAP.
    Regards
    Shahid Nadeem

    Hi Alok,
    I think this Qualifier importing after main table import is quite trickier that you estimate.
    1)Map all the fields of qualified table with source fields whther they are qualifiers or non-qulaifiers.
    - we will only be able to view the Non Qualifier field in the qualified table.
    2)Now the main step is when you finish all field and value mapping there will be also a Target field name on your qualified table with values of display field. this field must be mapped to a source field to import qualified table. do value mapping also.
    - This target field is the linkup field you are talking abot i feel, and it is viewed only in the main table and, as i have only on one non- qualifier this will not be a combination of any display fields.
    3)I am not abl eto see the Non -Qualifier in my main table
    So how do i proceed.
    Kindly guide
    Thanks
    Simona

  • Flat vs Qualified Flat

    Hi,
    What's the difference between Flat & Qualified Flat table?
    Thanks

    Hi Rokie,
      What's the difference between Flat & Qualified Flat table?    
        Genarally to avoid the redundancy of data, both  Lookup[Flat] and Qualified Flat will be used.
        But  What's the difference between Flat & Qualified Flat table?
        Lookup[Flat] contains some set of legal values which can be shared by main table .But in some cases
        we may have the data in some fields changes frequently based on other fields in that table.
        Suppose Price of a particular product changes based on region.Here what we need to understand is
        there are multiple values for each main table product.Obvisouly it increases redundancy of data.
        Qualifer table contains qualifier and non-qualifier fields.
        Data which is frequently changes based on other fields considered as Qualifier fields.
        Non-Qualifier fields contains the data which is responsible of changes in qualifier fields.
         I am giving differences between Lookup[Flat] and Qualified lookup.
         1) Lookup[Flat] contains predefined set of records (Ex: List of manufactures for particular product)
            whereas Qualified lookup contains conditional set of records (Ex: Pricing based on manufaturer and
             region)
       2) Lookup within lookup is possible whereas qualified lookup is possible only on main table
       3) Lookup table record need to be maintained  before main table record  whereas qualified record is
          maintained  after main table gets created.
      4) Lookup[Flat] contains relatively small no of records when compared to main table whereas qualified
         lookup contains large no of records when compared to main table.
        For better understanding, go through the above blogs given by others.
       Hope it helps,
       Reward points,if found useful.
       Thanks,
       Narendra.M

  • Sorting the Non qualifier values.. Is it Possible!!

    Hi Experts,
    I have a qualified table.
    week day -> Non qualifier
    Time In -> Qualifier
    Time out -> Qualifier
    The Week day Field is fileed with all 7 days of the week.
    Monday, Tuesday,wednesday,Th..... sunday
    Wehave 2 issues here..
    1) In DM qualified lookup selection for a record, i can see it is autiomaticallyy sorted Based on Alphabetical order..
    that is Friday, Monday, Saturday, Sunday, thursday, Tuesday, Wednesday.
    we require this to be in Monday to Sunday order..
    2) Also i selected Monday first and gave timein time out values, and for the same record when i ALSO select Friday and provided Time in and Time out values and once i Hit save, then i can see that Friday is seen first and Monday is seen Next to it.
    Which means it is also saving the Entries for Qualified table in a Non qualifier Alphabetical sorting order.
    Can we get rid of this??
    User should see the Qualifid Lookup selection box in Monday to sunday order
    Once user selects the any of the values in non qualifiers they should be seen in Monday to Sunday order once they save.
    Note: Sort Type option at Non qualifier Field level did not help.
    did anyone face similar issue??
    KR
    John

    Hi,
    I used a Integer field called Code.
    which has 1-7 numbers.
    Name                 :     Code
    Monday                     1
    Tuesday                   2
    Wednesday              3
    thursday                   4
    Friday                       5
    Saturday                   6
    Sunday                     7
    These 2 fields are Non qualifiers, But in Portal we have hidden the Code field.
    This way the sorting worked.
    Closing thread.
    KR
    John

  • When to use qualified lookup table?

    Hi all,
    I am confused with the qualified lookup table and lookup table, for the situation that a company has more than one contact person, I created a table "contact person", which has following fields: first name, last name, phone number, email address.
    Questions:
    1. should I set "contact person" as a lookup table or qualified lookup table?
    2. if to be set as qualified lookup table, which field should be qualifier field? what is the difference between qualifier field and non-qualifier field?
    your reply will be very appreciable
    Bin

    At times data is stored in such a way that duplication is unavoidable due to the storing mechanism and other factors. It may also happen that the data is sparse. The efficient way of storing data in such scenarios is the use of Qualified tables as it reduces the size of the main table and removes the unnecessarily created duplicates.
    Check the foll links
    /people/pooja.khandelwal2/blog/2006/03/29/taming-the-animal--qualified-tables
    /people/avi.rokach/blog/2006/11/14/using-mdm-55-for-data-quality-analysis
    MDM data modelling guide
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5d4211fa-0301-0010-9fb1-ef1fd91719b6
    How to import Qualified tables.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/abe914fa-0301-0010-7bb1-d25c2a4bb655
    Also this one.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/792f57b7-0a01-0010-f3b6-881269136a83
    Please reward for the same.

  • Qualified Lookup Table in Webdynpro Content Generator

    I am trying to build a user interface with the webynpro component generators from the business content deployed on the portal.  The problem I face is with qualified lookup tables.  From the main table, there is an embedded table which contains the qualified lookup table.  I can press the "edit" button to open a pop-up window which shows the details of the qualified link.  Unfortunately, on MDM 7.1 SP05, the pop-up window contains a table at the top of the screen that forces the entire window to span the width of the table, which will go on quite far because I have about 20 fields in my qualified lookup table.  Below I can enter the values for the individual fields, but it is difficult to use because you have to scroll all the way to the right to select drop down values.  Is there a way to remove the summary table from the pop-up window for qualified lookup tables?  I havent seen an option in the UI config.

    Apparently you can configure the fields that are shown in the pop-up window, but it also limits the fields that are displayed on the iView of the main table.

  • MDM ABAP API - Retrieval of Qualified Flat lookup fields

    Hi,
    I am having trouble retrieving the records using MDM ABAP API when the fields that are being retrieved includes a Qualified Flat lookup field. An exception is being thrown with the error message <b>Value with type id 0 is not supported</b>. I don't see any problem when I am trying to retrieve other fields of types String or Real. The type of the Qualified Flat lookup field is set to MDM_QUALIFIED_LINK_TABLE as per the How to guides given by SAP. Any ideas on why the exception is occuring?
    Thanks
    Suman

    Hi Suman,
    Please check if the How to guide (#13) in SMP -operations is of help https://websmp204.sap-ag.de/nw04operation
    Regards,
    Anita

  • Qualifier and non qualifier fields

    Hi,
    What is the diff b/w Qualifier and non qualifier fields
    Regards,
    Ganga

    Hi,
    You can get a lot of information on Qualifier & Non- Qualifiers.
    Please follow the link below for info:
    http://help.sap.com/saphelp_mdm550/helpdata/en/8e/9f9c427055c66ae10000000a155106/frameset.htm
    Go to->Repository Maintenence->Designing an MDM Repository-> Qualified Tables.
    How to Consolidate Data in Qualified Tables (NW7.0) :
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30380d0e-2f23-2a10-8f9d-da55511adbd8
    SAP Network Blog: Taming the animal - Qualified Tables:
    Taming the animal - Qualified Tables
    Here is a link to the thread where you can understand the concept to Qualified tables:
    Qualified table concept
    After basic understanding, you can follow the links below for importing the data into Qualified Tables:
    Importing Qualified Tables in MDM:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00a15239-684e-2b10-b8ae-b936b7d1c1fe
    Importing Qualified Tables and Main Table Data in a Single Step:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c03240fa-cc3e-2b10-aa9a-a5798e319a6e
    Hope this info helps.
    Thanks and Regards
    Nitin jain

  • Values of Non-Qualifiers (lookups) not auto-converting.

    We've been trying to use Import Server to automatically import records (XML) that had data for qualified lookup tables. Apparently there is an issue with namespaces in both the schema that we mapped to and the source field.
    After removing the namespaces, we now have an issue with the non-qualifier that uses a lookup table not automapping it's values and thus retaining the compound field at the Customer main level.
    First, the Partner Function is mapped to the Partner Function flat lookup table. At this level, the value auto-converts and the green dot is visible to the left. 
    Second, at the Customer Partner qualified lookup, the Partner Function is again mapped to the Partner Function lookup. This time, however, the values do not automatically convert and the "AUTOMAP" button must be manually pushed for them to map. The other non-qualifiers (CustomerID, PartnerNum, PartnerSAP_ID) are also mapped and their values auto-convert (green dot).
    Finally, at the Customer main level, all of the non-qualified field from the Customer Partner table are mapped and all auto-convert except for the Partner Function field. This requires us to manually push "Automap". Then, and only then, does it allow us to right click on one of the fields and create the compound field to map to the Customer Partner field. Again, the value mapping is not automatic but must be done manually.
    This map is then saved and ImpMgr closed. When the IM is reopened with the same map, the compound field is not recreated due to the fact that the Partner Function values did not convert. Once these are redone manually, then and only then can the compound field be recreated and value mapped.
    When this same map is used in the Import Server, the error is that the qualified fields cannot be mapped. This brings us back to the lookup fields not value mapping. Likewise, if this same file is opened in Import Manager mannually, and the map applied, it STILL does not convert the values and the Compound Field for the Qualified L/Up table is dropped. 
    We are using MDM 5.5 SP4 Patch 3.

    Hello Christiane,
    Yes, this is a very important point and I should have noted it in my original post. Yes, my Default Batch Handling settings are:
      Yes - Automap unmapped values
      Add - Unmapped Value Handling
    Plus:
      Replace - Default multi-valued update
      Append - Deault qualified update
      None - Default matching qualifiers
    Also, in my mdis.ini file, my settings are:
      Automap Unmapped Value = True
      Unmapped Value Handling = Add
      Always Use Unmapped Value Handling = True
    It used to work when we were in SP4, Patch 2, but have since upgraded to Patch 3, Hotfix 2(?) and can't get it to work.
    Thanks for helping!
    Don

  • Force one unique record in a qualified table in data manager

    Our main table is Customers. We have a qualified table that stores Company Code information. We need to ensure that each customer in the main table has only one record per company code in the Company Code qualifeid table.
    Company ABC can be linked to Company Code 1, Company Code 2, Company 3 (three records in the Company Code qualified table)
    Company ABC cannot be linked to Company Code 1, Company Code 2, Company 2 (three records in the Company Code qualified table where two are duplicates)
    Company code is a the only Non-Qualifer field in the Company Code qualifeid table. I have set field as Unique in the console but i can still add duplicate records

    Tammi,
    Choosing Qualified table is wise option, when we really want to maintain possible duplicate data!
    otherwise Normal Lookup table would be ideal option.
    befor we proceed further, cud u pls explain me the unique factor to choose qualified in ur Business requirement?
    thanks
    Alexander

  • Non-qualifier Auto Id

    Hello
    we have a qulaified lookup table with all fields set as Qualified except one which is an AutoId field.
    How do we handle the mapping of the qulaified lookup field in the the main table for the auto id seeing as we will not have a source field?
    Do we need to map all the Qualified fields or just the qualified fields that are display field?
    We keep getting the following error on import:
    Import failed. Cannot import qualifiers because the qualified lookup field is not mapped.
    Import action: Create
    Source record no: 1
    Kind Regards
    C

    Hello
    The senario is as follows:
    Main table record Customer has a field of type qualifed lookup called Search key id. The qualified table is used to maintain a list of search keys per customer.
    Lookup table is as follows:
    Id        AutoID   Non-Qualifier
    Key     Text      Qualifier
    Status Text      Qualifer.
    We recieve on import:
    Customer Number  and map to Customer Number (main table)
    Key Value and map to Key (qualified lookup table)
    Status Value and map to Status (qualified lookup table)
    We add a field "search Key" on import and map to search key (main table)
    The question is how do we handle the AutoId field? E.g. If we import 3 search keys
    for a customer autoid runs from 1 to 3 the qulaified lookup table
    We keep getting an error when we try this. (see org. message)
    Kind Regards
    Con

  • Validation of non-qualifier

    Hello experts
    I have a validation problem on my qualified table.
    From the main table, containing customers I have a qualifier called Customer Numbers. It only has one non-qualifier called organization. It represents the internal organisation at the company and a customer can have different customer numbers depending on the organization.
    Organizations can be: Org A, Org B etc.
    Customer number is a text field.
    Other qualifiers exist but they are not important for the validation.
    I need to make sure that all customer numbers that are created have a text field that is not blank.
    I can get it to work if there is only one qualified link but if I have several I'm not able to get a consistent satisfactory result.
    This is an ok example:
    Organization   Customer Number    Other data
    Org A          12345              XYZ
    Org B          67890              XYZ
    Org A          67890              XYZ
    This is not allowed since the customer number for org B is blank:
    Organization   Customer Number    Other data
    Org A          12345              XYZ
    Org B                             XYZ
    Org A          67890              XYZ
    I have looked at [this thread|Validation Help; without luck.
    I have also tried the HAS_ANY_VALUES() function but it doesn't seem to work with IS_NOT_NULL. Any help would be appreciated.
    BR
    /Alexander

    >
    Udya Jisna wrote:
    > IF(IS_NULL(<qualifier:customer_number>), NOT(IS_NOT_NULL(<qualifier:customer_number>)), TRUE)
    One thing to consider here is that the semantics of IS_NULL and IS_NOT_NULL have changed in MDM 5.5 SP06 (see page 4 of the release notes: https://service.sap.com/~sapidb/011000358700001124542007E ). Therefore, the correct implementation depends on the MDM version you're using. If it's below SP06, you'll have to keep in mind to change the validation expression during an upgrade. If you're using SP06 (or already MDM 7.1), Udya's advice to use IS_NULL resp. IS_NOT_NULL should be the better way to go.
    Best regards,
    Dennis

  • Fetching Non Qualifier value frm main table

    Hi All,
           I have a requirement where I need to get 3  Non-Qualifier value present in the Main table .
           These 3 Non-Qualifier values are present in 1 Qualified Table.
            Kindly send me some sample code for this scenario
    awaiting for your reply
    Regards

    Hi Sudheendra,
                  Get the record result set by serching one particular column(other than field of type qualified) of the main table.
    then follow the steps.
    QualifiedLookupValue LVAL =(QualifiedLookupValue) temprs.getRecords()[0].getFieldValue(repoSchemacmd.getRepositorySchema().getTableSchema("mainTableName").getField("MaintableFieldName").getId());
    QualifiedLinkValue[] qlinks = LVAL.getQualifiedLinks();
    for (int k = 0; k < qlinks.length; k++) {
       //check whether qualifiercolumn is Display field or not.
       if(displayField){
       RecordId RID[] = new RecordId[1];
       RID[0] = qlinks[k].getLookupId();
            ResultDefinition rd =new ResultDefinition(repoSchema.getTable("qualifertableName").getId());
            rd.setSelectFields(repoSchemacmd.getRepositorySchema().getTableSchema("qualifertableName").getDisplayFieldIds());
            RetrieveRecordsByIdCommand retrievedRecords =new RetrieveRecordsByIdCommand(conAccessor);
           retrievedRecords.setSession(userSessionID);
           retrievedRecords.setIds(RID);
           retrievedRecords.setResultDefinition(rd);
              try {
                   retrievedRecords.execute();
                  } catch (CommandException e) {
              Record[] rec = retrievedRecords.getRecords().getRecords();
                     for (int m = 0; m < rec.length; m++) {
                         //if the field value is String.
                        String Value = qlinks[k].getQualifierValue(repoSchemacmd.getRepositorySchema().getFieldId(tableName,column)).toString();
      else{
           //if columt type in qualifier table is StringValue.
           String value1 =qlinks[k].getQualifierValue(repoSchemacmd.getRepositorySchema().getFieldId("qualifertableName","qualifiercolumn")).toString();
    Regards,
    Sandeep.

  • What is the need to combine non qualifiers during IMPORT

    Hi Experts,
    I want to know the need to combine the non qualifiers during import in the match records field.
    what is the significance of it?
    Thanks in advance.
    Sandhya.

    Hi Alex,
    Thanks for the reply.
    i need a small clarification about the same. as per my understanding the NON QUALIFIERS are text fields so how do they effect the value in the qualified fields? or should the NON Qualifiers be lookup fileds (in your example company code and Plant)
    Case 1 - if the Non qualifiers are of type lookup:
    Then based on the combination of the qualifiers how can we define the valid values in the qualifier fields
    Eg: if company code is 2000 (where company code is Non qualifiers of type lookup) then the available dropdown value for plant field should only be P001 and P002 (Whare plant field is qualifier)
    Case 2: If the Non qualifiers are of type lookup :
    Then how does the value in the Non qualifier decide the available values in the Qualifiers. 
    Please help me understand the above two scenerios
    Regards,
    SS

Maybe you are looking for