Qualified field merge

Hello,
This is the scenario.
We have phones qualified table where we have phone type as Non qualifier which can have values Work or phone and we have phone number as qualifier.All records have Phone type=Work but only few records have Phone type =Work as well as Phone type=FAX (multivalued qualified).
now at the time of syndication client need output format as flat file and they dont need 2 records with different phone types.i.e when you syndicate qualified data it becomes cartesian product that is if record 1 has Phone type as Work and Fax ,2 records will be syndicated
Record 1, phone type=Work ,Phone number= xxx
Record 1 ,phone type=FAX,Phone Number=YYY.
but we want that it should only go as
Record 1 ,phone Type=Work,Phone Number=XXX,Phone Type=Fax,Phone Number=YYY
Is it possible?
Thanks
Bindi

Hi Bindi,
If its Flat File then unfortunately that is not possible.
U will get separate record for each record in Qualified Table.
If ur output structure is XML then u can get something like this depending on ur XSD:
<Product>
<Record>1</Record>
<Phones>
<Phone Type> Work</Phone Type>
<Phone Number> XXX</Phone Number>
</Phones>
<Phones>
<Phone Type> Fax </Phone Type>
<Phone Number> YYY</Phone Number>
</Phones>
</Products>
Thanks,
Maheshwari
Edited by: Maheshwari Morbale on Jan 8, 2009 8:01 AM

Similar Messages

  • Matching and Merging Qualified fields

    Hi,
    I want to match and merge fields in a qualified table.
    Eg: Have to match the Street, City(Yes Qualifier) in the Qualified table Address.
    Have created the transformation, rule and startegy on these fields.
    When I execute the strategy, i'm able to see the scores and class.
    But in the "Merge" tab only fields of Main table are visible. I'm not able to see the required Address table fields and hence not able to make the decision on which field should be merged.
    How do i execute this scenario?

    Hi ketan,
      Basically you can perform matching and merging only on Main table and not on qualified tables; and if you have to match any qualified lookup field in the main table then it should be an qualifier field(i.e. the qualified option should be YES),
      And while matching the records of a qualifier field when the values matches it shows only the display fields of the qualified table not the qualifier fields as already they have the same value you don't require them again.
      I couldn't understand the structure you gave above, but i will take this example
    Qualified table(Price)
           field_Name          Displayfiled       Qualifiedfield
             Price                      Yes                 No
             Quantity                 Yes                  No
             Currency               No                     YES
    Main table(Products)
              field_Name         Type            
              Product               Text
               Price                Look-up(Price)
    now the values in main table
       Product          Price
      cream            05 | 10 | Rs
      Cloth             10 | 05 | $
      Pen               20 | 02 | Rs
      Pencil            02 | 02 | Rs
    now you write a rule using the price lookup qualifier field.
    it will show  cream , pen and pencil as matching.
    you can now merge as
    ___________       cream                 Pen         Pencil
    ___________        05 | 10               20 | 02      02 | 02 
    now you can select the product any one of those there and price any one of those three but as the currency qualifier field is same for all; its not displayed nor is it showed over here.
    If the scenario is different form this which you require; please let me know, but the common scenario is the same.
    Regards,
    CHARAN

  • Populating data of a No Qualifier Field

    Hi All,
           I have 3-4 fields as Yes Qualifiers in my Qualified Table. I want to merge the data of these fields into a single No Qualifier field of the same table so that I can see that data in Matching Mode while merging of two records as I can not see the data of Yes qualifiers in matching mode.

    hi,
    1. in the console, in the qualified table, create one ( NO qualifier multivalued) filed.
    2. When you are importing qualified table, use partitions to concatenate required YES qualifiers, it will create one concatenated multivalued field. Those concatenated fields separated by delimeters.
    3. Map source multivalued field to the Destination No qualifier multivalued field.
    4.Do the import, and you can see the concatenated fields in the match mode, when ever you are doing merging of two records.
    hope this may help you,
    Regards
    Srinivas

  • Field Merge in Subject Line - Increasing the Hard Bounce Rate?

    Hey All,
    We did a little A/B test recently. By "little" I mean two different tests, 250 recipients in each test). We wanted to test the option to insert Field Merge in the Subject Line. We took 10% of 2 specific groups of costumers and sent the two options:
    1. Salutation LastName, Register Now and Secure a Tuition Scholarship
    VS.
    2. Register Now and Secure a Tuition Scholarship
    As said above, we did the same test twice to 2 different groups.
    The results was, unsurprisingly, in favour of the Subject Line with the Field Merge BUT - - - - - We saw that not only the Open Rates or Clickthroughs were higher, but also Hard Bounce rates were higher (3 Hard Bounces when we used Field Merge vs. 0 when we sent a plain text SL)
    Do you think that the usage of Field Merge in the Subject Line could be the reason for the higher Hard Bounces rates?
    Thank you,
    Ziv

    You should be able to get some more precise information from your Xorg logs, but I would bet it is related to the evdev driver. Some of the options in your xorg.conf no longer work with the latest version. For now you should be able to either map your mouse directly to the appropriate /dev/event* entry or change to the standard mouse driver, both of those methods should be in the wiki.
    You are supposed to be able to use the evdev driver without the input section of your xorg.conf by using dbus/hal autodetection, but AFAIK at the moment the xorg-server package still isn't compiled with hal support, so you would have to patch and rebuild the package.

  • Error while inserting value Qualified field in the main table

    Hello,
    I am trying to populate Qualified field in the main table when a new record is inserted in the Products Repository.
    The field is Reference Price and its a qualified lookup field. I am using the below code to create qualified lookup value and create qualified link values.
    QualifiedLookupValue qlvRefPrice = new QualifiedLookupValue();
    TableId qltabid = repSchema.getTableId("ReferencePrices");
    FieldId qlfieldid = repSchema.getFieldId("ReferencePrices","RP_ReferncePrices");
    RecordId rdRefPrice = getRecordId(connPool,session,"RP",qlfieldid,qltabid);
    HashMap map = new HashMap();
    map.put(repSchema.getFieldId("ReferencePrices","StartDate_ReferencePrice"),new DateTimeValue(cal));
    map.put(repSchema.getFieldId("ReferencePrices","EndDate_ReferencePrice"),new DateTimeValue(cal));
    map.put(repSchema.getFieldId("ReferencePrices","ListPrice"),new FloatValue(Float.parseFloat("123.3")));
    map.put(repSchema.getFieldId("ReferencePrices","Currency"),new LookupValue(getLookupRecordId(connPool,session,"Currencies","Currency_Currencies","EUR")));
    QualifiedLinkValue qlvLinkValue = MdmValueFactory.createQualifiedLinkValue(rdRefPrice,map);
    qlvRefPrice.addValue(qlvLinkValue);
    emptyRecord.setFieldValue(fieldIdRefPriceHistory,qlvRefPrice);
    However when the createrecord command is executed I get the following error.
    java.lang.RuntimeException: No matching validation Id 97. at com.sap.mdm.internal.validation.ValidationInfoHelper.retrieveValidations(ValidationInfoHelper.java:71) at com.sap.mdm.data.commands.CreateRecordCommand.execute(CreateRecordCommand.java:246) at com.alcatel_lucent.productdetail.ProductItemDetail_Comp.createProduct(ProductItemDetail_Comp.java:2927) at com.alcatel_lucent.productdetail.wdp.InternalProductItemDetail_Comp.createProduct(InternalProductItemDetail_Comp.java:656) at com.alcatel_lucent.productdetail.ProductItemAddView.onActionSave(ProductItemAddView.java:971) at com.alcatel_lucent.productdetail.wdp.InternalProductItemAddView.wdInvokeEventHandler(InternalProductItemAddView.java:662) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132) at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:332) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253) at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149) at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73) at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:869) at com.sap.tc.webdynpro.portal.pb.impl.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:77) at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1356) at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:327) at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:869) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136) at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:332) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253) at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(AccessController.java:219) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)      
    I spoke to my MDM team and they say there is no validation which they have put for Reference Price field. I have tried inserting values in another field of type qualified lookup in the same main table and that works without any issue.
    The code is as below:
    QualifiedLookupValue qlvRating = new QualifiedLookupValue();
    TableId qlvtable = repSchema.getTableId("ProductRatings");
    FieldId qlvratinglink = repSchema.getFieldId("ProductRatings","RatingLink");                    
    RecordId rdidPR = getRecordId(connPool,session,"CI",qlvratinglink,qlvtable);
    wdComponentAPI.getMessageManager().reportSuccess("rdidPR "+rdidPR);
    HashMap mapPR = new HashMap();
    mapPR.put(repSchema.getFieldId("ProductRatings","AvailRating"),new LookupValue(getLookupRecordId(connPool,session,"AvailabilityRatings","AvailabilityRating_AvailabilityRatings","CI")));
    mapPR.put(repSchema.getFieldId("ProductRatings","EffectiveDate"),new DateTimeValue(cal));
    mapPR.put(repSchema.getFieldId("ProductRatings","FERAIndic"),new LookupValue(getLookupRecordId(connPool,session,"ReplacementIndicators","Code","FE")));
    mapPR.put(repSchema.getFieldId("ProductRatings","FERAOrdItem"),new LookupValue(getLookupRecordId(connPool,session,"ReplProducts","ProdID","100008200")));
    QualifiedLinkValue qlvLink = MdmValueFactory.createQualifiedLinkValue(rdidPR,mapPR);
    qlvRating.addValue(qlvLink);
    emptyRecord.setFieldValue(fieldIdRatingHistory,qlvRating);     
    I would really appreciate if someone can help in solving the issue.
    Thanks in advance,
    Aamod

    Hi Aamod,
    Sees that some validation/assignments are getting triggered as soon as you make changes to the record in MDM. Please check once after removing validations/workflow that you may have. This way you may debug the issue.
    Hope this helps!!
    Cheers,
    Arafat

  • How to search for a qualifier field?

    Hello Experts,
    I have a field of type Lookup[qualified flat] in the MDM main table. The lookup table has 5-6 fields, some are qualifier and some are non-qualifier. I want to perform a search which is combination of qualifier as well as non-qualifier fields of the lookup table.
    For non-qualifier I have used FieldSearchDimension for non-qualifier field and QualifierSearchDimension for qualifier filed. But I am not getting the expected result. Could you please help.
    Pictorially the scenarion is like:
    MDM Main Table-> Field X(lookup[qualified flat])
    Field X - Sub Field X1[qualifier - no]
                - Sub Field X2[qualifier - yes]
    Search criteria : Combination of Sub field X1 and sub field X2.
    Thanks in anticipation!
    Rakesh

    Hi Rakesh,
    Adopt a drill down mechanism while using a Qualified lookup search.
    In Datamanager, search parameters for a qualified lookup table appear as 3 distinct boxes - one below the other -
    Box 1 : Look ups in Non qualifiers and their values
    Box 2 : Qualified field : Displays all the valid Qualified field values that exist for a main table record.
    Box 3: Qualifiers and their Values.
    In your case, Sub Field X1( Non Qualifier) will appear in Box 1 ; Sub Field X2 (qualifier) will appear in Box3.
    To achieve the expected search you want follw the below steps in seq :
    1. Select Sub Field X1( Non Qualifier)  in Box 1 and then select its lookup value.
    2. Select Sub Field X2 (qualifier) in Box3 and then select its lookup value.
    You will have your combination search results visible. To cross check the selection you have made, select 'Search Selections' tab and verify.
    Regards,
    Vinay

  • Field level trigger on qualifier field

    Hello,
    Here is my scenario.
    I have a qualified field : ACTIVE FLAG  in address qualified table.
    What i want to do is if the value of this field changes to N (possible values of this field : Blank,Y and N),i want my workflow to trigger.
    I know its possible with field trigger option where you create one time stamp field and will give the field you want to comare
    but in case of qualified tables you can not select qualifier as a selected field for timestamp field.you can only select non qualifiers.
    is there any other way this can be achieved?
    thanks
    Bindi

    SharePoint doesn't provide field level permissions.  Fellow MVP Dan Holme has a good article that recommends some approaches on this here:
    http://sharepointpromag.com/blog/3-approaches-restricting-access-sharepoint-columns-and-metadata
    Another approach you could take is to make the form an InfoPath form from in an InfoPath LIBRARY instead.  This way you can control the form fields and prevent users from directly editing fields.  It also plays really well with workflow.
    I trust that answers your question...
    Thanks
    C
    |
    RSS |
    http://crayveon.com/blog |
    SharePoint Scripts | Twitter |
    Google+ | LinkedIn |
    Facebook | Quix Utilities for SharePoint
    thanks for your reply , seems that creating two lists will work for me better. but can you provide some useful links that talks about how to create two lists and link them , and specify different permissions for each list using web-parts...

  • Error in importing qualified field values

    Hi,
    I have a query related to importing qualified tables. At the source side, the main fields and qualified table fields are given in 2 different sheets of Excel, joined by the product ID. While importing the qualified tables, I am only able to import non qualified field values in data manager and rests of the qualified field values are not getting imported. Following are the steps I have followed:
      Map Non Qualified fields (Source: Qualified table;   Destination: Qualified table)
      Import Non Qualified fields
      Map Non Qualified fields (Source: Qualified table; Destination: Main Table)
      Create compound key and map with the destination field.
      Map qualified fields (Source: Qualified table; Destination: Main table)
    o Match records and Import. (No fields are coming up in the Match records pane  (Error))
    Pls let me know the solution to rectify the error.

    Hi Vishal,
    You cannot have your Qualified table (Non -qualifier and Qualifier)details in a separate excel sheet and the Main table fields in a separate sheet.As the Qualifiers are part of the main record only and besides whenever you import data in the qualified tabel itself by selecting the qualified table as the destination table ,you will be able to map only the non-qulaifiers as the Qualifiers are only visible under the main table destination.
    So you can create your source in two ways
    - All the non-qualifiers of the qualified table in a separate excel and all the main table fields along with the Qualifiers in a separate sheet.
    - All the fields in a single sheet ,as you can select the same source when you want to import the qualified table as well as the main table.
    You can import the Qualified tabel records either before or after the main table importing as mentioned in the above post.
    kindly follow the below link to understand qualified table importing:
    Taming the animal - Qualified Tables
    - When you are importing data (non qualifiers) in the qualified table you can select any one or combination of the non qualifiers as the matching fields
    - When you are importing the main table you need to map the qualifiers as well as the main table fields.You need to select the primary key field of the main table as the matching field.
    - The link is established between the qualifiers and the non qualifiers in the main table mapping.
    - You will able to see the same in the qualified tab in data manager
    Hope it helped
    Thanks & Regards
    Simona

  • PDF in qualifier fields ?

    Hi, all
    I have a PDF lookup field in qualified table as a qualifier. When I select it and click 'View PDF..." system doesn't react and when i click 'Edit externally' or 'Save PDF' I get errors like
    'Data Table Not Found, Version SP5 (5.5.42.65)' and 'Failed to load image'.
    Everything works fine in case of simple lookup PDF field in main table.
    Has anyone experiened such behaviour with lookup to PDF table in qualifier field?
    Regards,
    Vadim Kalabin

    Hi Vadim,
    It is expected sometimes that one could need to export some or all of the records of an MDM repository, for example, so that you can distribute subsets of your master data for review and/or editing by different audiences who are not users of the MDM system.
    The *Exportcommand* in Record mode allows you to output table records into several different, industry-standard file formats, as summarized in the following table.
    For more info visit this URL [http://help.sap.com/saphelp_mdm550/helpdata/en/43/de22db05666195e10000000a1553f7/content.htm]
    Now, a qualified table in MDM stores a set of lookup records, and also supports qualifiers, “subfields” that apply not to the qualified table record by itself, but rather to each association of a qualified table record with a main table record. MDM supports multiple simultaneous qualified tables.
    For value mapping from PDF as qualifier you can find some relevent information on this URL [http://help.sap.com/saphelp_mdm550/helpdata/en/43/2a977eec3d0b1fe10000000a1553f6/content.htm]
    Beat Regards,
    Krutarth

  • 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

  • Fully Qualified Field

    I have a question about JDBC drivers. I am trying to access a field from a query row using the fully qualified field name. That is, I'm tring to use the <table-name>.<field-name> naming convention. For example:
      SELECT EMPLOYEE.NAME FROM EMPLOYEE ;
    The fully qualified name would be EMPLOYEE.NAME. Most SQL servers understand this. I've found that there are JDBC drivers out there that cannot retrieve the field using this fully qualified name:
      rs.getString("EMPLOYEE.NAME") ;
    The above statement may throw an exception on one driver and return null for another. I've modified a driver to allow this naming convention, but I'm worried that it's not part of the actual JDBC specification. Is this true?
    On the other hand, field alias seems to work:
      SELECT EMPLOYEE.NAME EMPLOYEE_NAME FROM EMPLOYEE ;
      rs.getString("EMPLOYEE_NAME") ;
    Most drivers allow this. Although I have seen a few that don't. I can live with having to give a field alias. Should I leave it at that?
    Anthony

    The issue is the the column name in the returned resultset is not the fully qualified column name. The resultset only returns the column name without the tablename prefix. Even if you have a statment like the following:
    select Request.RequestID, RequestStatus.RequestID from Request, RequestStatus
    The resultset returned will have two columns named RequestID.
    An alternative is to retrieve the resultset using the column number from the resultset( ie. var = rset.getString(1)).

  • Qualifier Field Not Shown in Qualified Table

    Hi All,
    Can anybody tell me why the values of qualifier fields are not shown in the qualified tables? And where are those qualifier values stored, in the main table or in the qualified table itself?
    Best Regards
    Jerome

    Hi Jerome,
    Before starting, I am assuming there is no confusion relating to Qualifiers & Non-Qualifiers.
    Non-Qualifiers --> Decidors/Fields whose value changes
    Qualifiers --> Fields which get decided/whose value changes based on the Non-Qualifers.
    You said - "<i>Can anybody tell me why the values of qualifier fields are not shown in the qualified tables?</i> "
    <b>1. )</b>What I understood from your question is that; when you select your Qualified Table in the Record Mode of the Data Manager, the qualifiers appear to be locked/non-editable. Is that right?
    All the qualifiers are locked because <b>they have no context in the Qualified table.</b>
    For e.g.: If your Qualified table is "Addresses" consisting of
    Non-Qualifiers --> Address Type(say Home(can be more than 1), Office,etc)
    Qualifiers --> HouseNo,Street, City, Country,etc.
    What would it mean if we put the street name "XYZ Street" for the record selected. Nothing -- the street must be connected to a main table record, a Customer(Cust_Id)  and and an address-type(Home) to have meaning.
    <b>2.)</b> If the above interpretation of your Q is not correct, then 2nd case could be --> when you select your main table in DM (Record Mode)and try to add a Qualified Lookup value to a record you are unable to see the qualifiers. Right?
    In the main table Double-click on the quailfied lookup field. An screen pops-up. Here we see the available lookup records -- these are in fact the records we saw when we switched to view the Addresses qualified lookup fields, which means these are the values stored in the non-qualifiers. You have to select & add them (Selected Lookup Records). The qualifiers become enabled. Now you an add values to them.
    You can either use an existing Address type or add a record to the Qualified-Lookup Table from here.  We can add and remove types of addresses -- a main table record may have any number of any type of address. When we add a type, for example "Favourite Restaurant Address"(say), we can enter information for the qualifiers, those field which make sense only when connected to a main table record and a non-qualifier. If we add two "Home" addresses each can have it's own values for the City, Street, Country, State and Postal Code qualifier fields
    To answer 2nd part of your Q - "<i>And where are those qualifier values stored, in the main table or in the qualified table itself?</i>"
    Qualifiers are database “subfields” that apply not to the qualified table record by itself, but <b>rather to each association of a qualified table record with a main table record.</b>
    Hope this helped your cause. Please mark helpful answers.
    Regards,
    Siddharth Sharma.

  • Field merge via Excel upload?

    I decided to create a new string for this question, though I had found a related article where I initially made a posting (I can't now edit or delete my original posting - "actions" menu doesn't open for me, PC and Mac, Chrome and FF):
    Using Field Merge to Dynamically Display an Image
    The post above outlines pretty much exactly what I want to do, but I'm missing something -
    Here is what I'd like to do: I have some customer information that I want to merge to an email; the information is not something I want to necessarily retain with my contacts.
    We're using Excel to upload lists, as these are contacts not currently in our database. I created a new field merge, and inserted the merge into my email. Creating the field merge requires linking the merge to either Contacts, Accounts, Events/Event Sessions, or CDOs. My original assumption was that I'd need to create a CDO, which I did. So I created the field merge, tied it to my CDO, and inserted the field into the email.
    When I then go to test the email, I upload my test segment. In matching fields, I can't match the additional customer data fields from Excel to fields in Eloqua - I had thought maybe the CDO fields would appear as options for matching.
    So, my question is, how do I get the Excel data to match up to my merge field in Eloqua?
    Thanks for any help you can give!
    Colin

    Here was the outcome:
    You can't perform a merge via Excel upload (ie - trying to create a new segment via upload that contains data to be merged) - I was on the right track, that this needs to be done via CDO.
    1. Create your CDO, upload your Excel file, and map contacts to the data card
         - Create a new CDO, adding the extra fields you want to capture
         - Specify "Email Address" in the Display name, Unique ID and Email Address fields. I also set the Group By field to Email Address, and the Entity type as Contacts with field again set to Email Address.
         - When uploading your Excel file with the records you want to merge, make sure to map the uploaded contacts to the data card (Custom Object > Upload Custom Object Records). In the resulting wizard, in step 4 - Upload Actions, be sure that the Map data card checkbox is checked. Not real sure why you'd ever not want this - it seems to me you can't do much without it.
    2. Create your field merges Email Field Merges
         - map these to your CDO fields
    3. Insert the field merges into your email
    That's about it - if anyone has additional info or corrections on the above, let me know. Hope this helps -
    Colin

  • Regd. Qualifier Fields in Segments

    I wanted to know was the usage of qualifiers in IDOCS.
    Some segments have these qualifier fields, but what exactly could be the significance of them. Could anyone tell me about them.
    Regards,
    Vijay

    Qualifiers are basically differentiating the subsequent data in that segment. By that what I mean is let us say in a segment you have a qualifier and a material number field. Now in the Idoc type, if you have a need to send more than one material number, but they refer to different things like customer material number, vendor material number, your material number etc, you will use the qualifier to identify and differentiate them.

  • Field Merging in ALV

    Hi,
         How to merge the repetitive entries of field, while displaying in ALV.
    For example:
       In my internal table ITAB has 3 fields, VBELN, POSNR, AMOUNT.  If ITAB contains 1 record say 100 with 4 line items 10, 20, 30 & 40. I need to display it as
    VBELN    POSNR    AMT
    100            10          2500  
                      20         1500
                      30          2600
                      40          5680
    I do want to display VBELN value only once, since it is same.
    I tried using sort option in ALV and also populated the cell_merge value in layout with value 'X'. But it is not working as desired.
    I am using the FM 'Reuse_alv_grid_display. Can anyone help me out.
    PS: In the ITAB, VBELN is the second field. First is the indicator field (MARK).
    With Regards,
    NL

    i dont know if you comment spos whether it will work or not ?
    otherwise format your itab like that
    data : v_vbeln like vbap-vbeln.
    sort itab by vbeln.
    loop at itab.
    on change of itab-vbeln.
    v_vbeln = itab-vbeln.
    endon.
    itab-vbeln = v_vbeln.
    modify itab.
    clear v_vbeln.
    endloop.
    regards
    shiba dutta

Maybe you are looking for

  • Open new browser window

    it also opens in the parent window at the same time. For instance, I have a home page and when you click on a link I want it to open up in a new browser window. so i set the behavior to do this and it works. However, the first window also changes to

  • Sending an email with attachment!??!

    Hi everybody. I'm currently having this kind of trouble: I dynamically create a PDF file which the user should be able to download. But he should also get the chance of sending it to some place via email. So I have to create, send and attach a file t

  • Instrument I/O Assistant blank

    I have been having problems getting a code to work. So, I purchased LabVIEW for Everyone (a book) to see if I could figure out how to get the code to run right.  (here is a link to that thread ) I just redownloaded and installed NI-Visa. The book say

  • SQL JDBC Timestamp

    Hello all, How to convert java.Sql. timestamp yyyy-mm-dd HH:MM:SS.nanosec to yyyy-mm-dd HH:MM:SS format. Thanks

  • Domain local groups with members from other (same forest) domains?

    I'm confused about granting access to a share via a domain local group that contains members from other domains. Consider this scenario: Joe Smith logs into his own domain (DALLAS.CORP.COM) and his token gets the DALLAS\sales global group. A share (n