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

Similar Messages

  • 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

  • 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

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

  • 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

  • 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

  • FA Account Generator: Non Qualified Segment

    Hi,
    Currently we have a requirement of customizing the account generator to accommodate the following requirement.
    COA structure: Company-Branch-CostCenter-NaturalAccount-Product-Future1
    The account generator should generate the Account based on the Branch and the CostCenter that owns the asset.
    I understand that we can get Cost Center segment value in FA account generator.(by using the Cost center qualifier)
    Currently i need to derive the non qualifier segment BRANCH also.
    Can someone throw some light on this, like how can this be acheived?
    Regards,
    Senthil
    Edited by: Senthil Velavan J R on Oct 8, 2009 2:59 PM

    Accounting Segments that are not qualifiers will have to be derived programmatically.

  • 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

  • Auto Id as Non-Qualifer

    Hi Guys
    I already open a thread on this topic but maybe I was not so clear on the issue.
    Can some please tell us how we can use a Auto Id filed as the Non-Qualifier field in a Qualified lookup table?
    All other fields in the same lookup table we want as Qualifiers.
    How do we map to the Non-Qualifer, Auto Id field on import seeing as we will not have a corresponding value in the source data
    All help is greatly appricated
    Rgs
    C

    You create a new table of type FLAT.
    Create two fields for this table.
    One of them is a AutoId type field. Make this the display field. Another field could be description field or something like that.
    Create a Qualified table. Make the non-qualifier field as type look up to the Flat table you created above.
    Add all the qualifers you need.
    This way you can look up the autoids of the lookup table as NON Qualifiers.
    Hope this helps.

  • How to map qualifiers?

    Hello,
    I am new in MDM and have (hopefully) a basic question:
    I have issues in the import manager.
    My target table is the table “Products” (source is an Excel file). I am facing issues to import the price data. The sub table price is a qualified look up table that looks like this (it’s just an example):
    Lower Bound (integer – Non Qualifier - DF)
    Price (integer – Qualifier - DF)
    Year (text50 – Non Qualifier –DF)
    UOM (text50 – Qualifier )
    As soon as I map a Qualifier field (either Price or UOM) the import manager tells me:
    “Map 'Price' field to import qualifier(s).”
    I think he wants me to map the target field “Price <Year; Lower Bound>”
    What I tried is to create a Partition of the source fields year and Lower Bound and map it to the target field “Price <Year; Lower Bound>”.
    During the value mapping I can not choose the option “Add” it is grayed out. There is only “Map” and “Auto Map” available. But what I like is that these values will be created if they not yet exist…..So the only option I have is to map it to the existing <Null> value…
    Can anyone help me? I am sure it is just a problem of understanding….
    How does the process look like to map qualifiers?

    Hi ,
    What about mapping i ncase of e-mail ,phone and fax fields in the standard business content. In this case the main table is the customer table and it has the e-mail/phone/fax field as a multi-valued qualified lookup.
    The lookup table has the country field as a display -non qualifier and other fields like e-mail, address type ,home flag as the qualifiers.
    The issue is that with only country as the non qual display field, the mapping is not possible. None of the other fields can act as non-qualifiers, as they are mainly flags.
    Ideally, the e-mail address has to appear in the main table as a display field. If this field is created as a DF and qualifier, the compound field does not get created.
    If it is created as a DF ,non qualifier, it is wrong, as each customer would have a different e-mai land we cannot upload lookup values for it.
    What is the best way to tackle this issue ?
    Thanks for all your suggestions.
    Regards,
    Anita

  • Qualified table, MDIS

    Hi All,
    for a qualified table, we have a different approach of loading the data using import manager...... like first mapping and loading the qualifiers and then mapping and loading the non-qualifiers .
    My question is that ..... I want to load a qualified table automatically from the port using MDIS........ can anyone pls explain me how to handle this auto task.
    regards,
    verma.

    Adrivit,
    I have to place these files in a port to import automatically.
    for this i need MDIS to pick up the no qualifiers first
    and then the qualifiers.
    Once the file if imported it will be moved to archived folder right.
    then how do i handle this.
    pls dont mind..little stuck ....... can you pls elabrate
    example:
    mat01 desc type Bu1 ht1 wt1
                               Bu1 ht2  wt2
                               Bu1 ht3 wt3
    say Bu1 is the no qualifier
    rgds,
    verma

  • ASR (Auto Service Request) version 3.1 now available

    ASR (Auto Service Request) version 3.1 has been released to production.
    You can access the ASR 3.1 download and documentation via the link at the bottom of http://oracle.com/asr.
    Changes in ASR 3.1:
    ASR Manager installable on any Solaris 10 or OEL (Oracle Enterprise Linux) operating environment
    Supports the ability to install the ASR Manager on a non-qualified, non-entitled server. This means the ASR Manager can be installed in a Solaris local zone or LDOM, in virtual environments such as VirtualBox and VMWare, and on M-Series domains and Blade servers.
    Changes in the customer email notifications.
    The updated user documentation includes examples of the new email messages.
    Our customers and Partners are advised to use My Oracle Support to manage their ASR assets, as well as the ASR Manager "list_asset" command.
    The "asr report" command is now disabled.
    See the "What's new" section of Installation and Operations guide for more info on ASR 3.1 changes.
    Note that the ASR download is now hosted by My Oracle Support and is no longer on the Sun Download Center.
    Best Regards,
    Wayne Seltzer
    ASR Product Manager
    Oracle Global Customer Services

    Hi
    I have wls 10.3.1 installed on my local machine. I installed it as part of configuring FMW 11g. I am trying to add
    OSB component to it by running : osb1031_wls103_win32.exe.
    But I am receiving the following error message:
    The product maintenance level of the current installer ( wls 10.3.0.0) is not compatible with the maintenace
    level of the product installed on your system (wls 10.3.1.0). Please obtain a compatibile installer or perform
    maintenance on your current system to achieve the desired level.
    So my guess from the above message is that "osb1031_wls103_win32.exe" is for wls 10.3 and not for wls 10.3.1.
    Where can I get the OSB installer for wls 10.3.1? or how can I fix the above error?

  • Get Qualifier value from Qualified table

    Hi,
    I am trying to get all the qualifier value for a qualified table. What is the best way to do it. Can I use QualifierSearchDimension to search for all the qualifier value.
    Re: Lookup [Qualified Flat] type field how to use as a query condition? link gives us a way to do this , but it talk about getting the non - qualifiers only , so How can we get the qualifier values.
    The link Search Qualifier Fields : MDM Java APIs gives us a way to this , but it is using old Java API , does anyone know how to do it using MDM API SP06.
    Thanks and Regards,
    Subhasis

    Hi Subhasis,
    The Search API's will only search for a particular value in the qualified tables. In order to read all the qualifier and non qualifier for a record, please follow the below mentioned steps.
    Assuming 'rec' is the variable that holds the reference for the current record.
    MdmValue lookUpVal = rec.getFieldValuel(<Field Id of the field>);
    com.sap.mdm.valuetypes.QualifiedLookupValue val = (com.sap.mdm.valuetypes.QualifiedLookupValue) lookUpVal;
    // Get the total number of qualified records present for that field
    int size = val.getValuesCount();
    // Iterate through each qualified record to fetch the details
    for(int i=0;i<size;i++){
        MdmValue nqVal = val.getValue(i);
       if(nqVal != null){
             MdmValue incVal = val.getQualifierFieldValue(i,<Field Id of the qualifier field value>);
    Regards,
    Ponraj M
    Edited by: Ponraj M on Jul 10, 2009 10:12 AM

  • Error while trying to modify a Qualified Lookup Value.

    Hello,
    I have the following structure:
    Vendor <-- Main Table
    vendorName
    vendorType
    BankDetails <-- Qualified Table
    BankDetails (Table)
    Country   (non-qualifier value)
    bankKeyCode (cualifier value)
    Country
    code
    name
    I am trying to modify the BankDetails for a specific Vendor, I am getting a Record from Country table and then create a Link for the QualifiedLookupValue
    qualifiedLookupValue = (QualifiedLookupValue) mainRecord.getFieldValue(bankDetailFieldId);
    int index = qualifiedLookupValue.createQualifiedLink(countryRecord.getId());
    qualifiedLookupValue.setQualifierFieldValue(index, bankKeyFieldId, new LookupValue(bankKeyRecord.getId()));
    mainRecord.setFieldValue(bankDetailFieldId, qualifiedLookupValue);
    And then I modify the main Record (Vendor).
    I am getting the error: com.sap.mdm.commands.CommandException: com.sap.mdm.internal.protocol.manual.ServerException: Server error (0xffaa6000)
    What I have found in the forum is that this error is related to "Record Not Found". However, I am actually getting a correct Country from the Country table.
    Any Idea?.
    Many thanks in advance.
    Best Regards,
    Baez

    Hi Baez,
    You have to create a record with country record id in BankDetails table or get record id if country record id is already existed in BankDetails table  and use this record id to create qualified link .
    1. get Country record id
    2. search in Bankdetails table with Country Record id,
    3 . if exist in Bank details table, get record id in Bank details table and pass it to createQualifiedLink()method
                    or
    3. if Country record does not exist in BankDetails table, then  create new record in bankdetails table with Country record id, pass record id of new record to createQualifiedLink()method
    I hope this helps you......
    Cheers,
    Veeru

Maybe you are looking for