Syndicating Selected Qualified Lookup Entries

Hello all!
Here is an issue we are working on. We would like to syndicate entries from a qualified lookup table for a particular customer, but only those where a certain qualifier has a specific value. For example:
Qual Table:
Non-Qual1; Non-Qual2; Qualifier.
Entries:
"AA", "123", "Yes"
"BB", "123", "No"
"CC", "456", "Yes"
So, when I syndicate this customer record, I would only like to syndicate those entries where the Qualifer = "Yes".
"Supress Unchanged Records" only works on the whole customer record and if the Search Criteria is set for "Qualifer = "YES", then it chooses the record (correctly), but syndicates all entries from the table.
Thanks in advance!
Don

Try using
<b>Filter Qualified Links</b> in the <b>Map Properties</b> of the Syndicator.
If activated, syndication results contain only the data selected in the Selection Pane.
Tick the check box under the Value Column for that property. By default that check box is not selected. You have to check it.
This works similar to the 'Filter' check box of the MDM Data Manger.
Limitation as of SP04
- One Global setting per map for qualified links plus one global setting per map for multi-valued lookups.

Similar Messages

How to remove qualified lookup entries

Hi All,
My scenario is as explained below:
Main table: Customers
Qualifeid lookup table: Customer_Brands
Qualifer: Form_action (this is a Lookup field and the lookup table is Form_Action)
Form Action table has an entries called "CR" and "MO"
What I need to do:- There is a set of customers with form action value as CR. I need to remove this value (essentially make it null) for all those customers using MDM Java API.
So the question in short is how to remove qualified lookup entries?
NB: I am able to replace CR with MO and vice versa since these entries are in Form_Action table, but unable to remove these entries.
Please give some inputs on this. Sample codes are appreciated.
-Thanks,
Padmarajan.

Hi Adhappan,
My code snippet to set the value is as below:
A2iFields formFields = new A2iFields();
A2iField intField = new A2iField("Form_Action");
Value val = new Value(ValueType.ValueNull);
intField.SetValue(vall);
formFields.Add(intField);
But the ValueType.ValueNull returns an integer (in my case 17) and the form action field of the customer gets set with the value at that row of the form action table once I execute a modify query.
Please advice as to how to code it correctly.
-Thanks,
Padmarajan.

Qualified lookup table

Hi Guys,
Can you tell me the steps to be followed for importing and syndicating qualified lookup table .
Thanks,
MS Reddy

Hi,
1. Import all the lookup tables used in Qualified table.
2. Import qualified table data along with main table data only. For more than one qualified table record you should have repeated main table record.
E.g.
Qualified Table - Price Information
Lower Bound
Purchasing Info Record ID
Purchasing Organization
Amount
Currency
First three fields are the non-qualifiers amongst which Purchasing Organization is the lookup field. So you need to first populate this field.
Now your main table record is
Supplier     Supplier Part Number     Short Description     Product ID     Service Item     Lower Bound Purchasing Info Record ID     Purchasing Organization     Currency     Amount
AGENCY01          1000               metal processing     IBG-100               False     1     5300000018     Mumbai Purchase Org     Indian Rupee     100.00
1. Map all the main table fields
2. Identify the Display fields of your Qualified table, if your qualified table has more than one Display field then map the fields with the fields marked as D in destination structure e.g. in above given table all the three non-qualifiers are the display fields then mark Lower Bound with the D   Lower Bound field, similarly map the other display fields
3. Select all the Display fields at source side, right click and select Create Compound field. This will combine your input fields and automatically map them with Qualified field.
4. Map the qualifiers
5. Select the unique fields in Matching fields tab and execute the import.
When you syndicate data containing qualified links, it will create the number of output records depending on the number of qualified links.
Regards,
Jitesh Talreja

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.

Select for all entries

Hi,
      I am new in abap reports. Now i want to know why we should use select for all entries in query. We can do retrieve directly by accessing the table in database dictionary.
      Experts please give me the reasons I want to know the concepts behind it.It will be better if you kindly explain this with help of code.
     With regards,
       Abir.

HI
GOOD
SELECT
Basic form
SELECT result [target] FROM source [where] [GROUP BY fields] [ORDER BY order].
Effect
Retrieves an extract and/or a set of data from a database table or view (see Relational database ). SELECT belongs to the OPEN SQL command set.
Each SELECT command consists of a series of clauses specifying different tasks:
The SELECT result clause specifies
whether the result of the selection is a table or a single record,
which columns the result is meant to have and
whether the result is allowed to include identical lines.
The INTO target clause specifies the target area into which the selected data is to be read. If the target area is an internal table, the INTO clause specifies
whether the selected data is to overwrite the contents of the internal table or
whether the selected data is to be appended to the contents and
whether the selected data is to be placed in the internal table all at once or in several packets.
The INTO clause can also follow the FROM clause.
You can omit the INTO clause. The system then makes the data available in the table work area (see TABLES ) dbtab . If the SELECT clause includes a "*", the command is processed like the identical SELECT * INTO dbtab FROM dbtab statement. If the SELECT clause contains a list a1 ... an , the command is executed like SELECT a1 ... an INTO CORRESPONDING FIELDS OF dbtab FROM dbtab .
If the result of the selection is meant to be a table, the data is usually (for further information, see INTO -Klausel ) read line by line within a processing loop introduced by SELECT and concluded by ENDSELECT . For each line read, the processing passes through the loop once. If the result of the selection is meant to be a single record, the closing ENDSELECT is omitted.
The FROM source clause the source (database table or view ) from which the data is to be selected. It also determines
the type of client handling,
the behavior for buffered tables and
the maximum number of lines to be read.
The WHERE where clause specifies the conditions which the result of the selection must satisfy. It thus determines the lines of the result table. Normally - i.e. unless a client field is specified in the WHERE clause - only data of the current client is selected. If you want to select across other clients, the FROM clause must include the addition ... CLIENT SPECIFIED .
The GROUP-BY fields clause combines groups of lines together into single lines. A group is a set of lines which contain the same value for every database field in the GROUP BY clause.
The ORDER-BY order clause stipulates how the lines of the result table are to be ordered.
Each time the SELECT statement is executed, the system field SY-DBCNT contains the number of lines read so far. After ENDSELECT , SY-DBCNT contains the total number of lines read.
The return code value is set as follows:
SY-SUBRC = 0 At least one line was read.
SY_SUBRC = 4 No lines were read.
SY-SUBRC = 8 The search key was not fully qualified.
(nur bei SELECT SINGLE ). The returned single record is any line of the solution set.
Example
Output the passenger list for the Lufthansa flight 0400 on 28.02.1995:
TABLES SBOOK.
SELECT * FROM SBOOK
WHERE
    CARRID   = 'LH '      AND
    CONNID   = '0400'     AND
    FLDATE   = '19950228'
ORDER BY PRIMARY KEY.
WRITE: / SBOOK-BOOKID, SBOOK-CUSTOMID,   SBOOK-CUSTTYPE,
           SBOOK-SMOKER, SBOOK-LUGGWEIGHT, SBOOK-WUNIT,
           SBOOK-INVOICE.
ENDSELECT.
Note
Performance
In client/server environments, storing database tables in local buffers (see SAP buffering ) can save considerable amounts of time because the time required to make an access via the network is much more than that needed to access a locally buffered table.
Notes
A SELECT command on a table for which SAP buffering is defined in the ABAP/4 Dictionary is normally satisfied from the SAP buffer by bypassing the database. This does not apply with
- SELECT SINGLE FOR UPDATE
- SELECT DISTINCT in the SELECT clause ,
- BYPASSING BUFFER in the FROM clause ,
- ORDER BY f1 ... fn in the ORDER-BY clause ,
- aggregate functions in the SELECT clause ,
- when using IS [NOT] NULL WHERE condition ,
or if the generic key part is not qualified in the WHERE-Bedingung for a generically buffered table.
Authorization checks are not supported by the SELECT statement, so you must program these yourself.
In dialog systems, the database system locking mechanism cannot always guarantee to synchronize the simultaneous access of several users to the same dataset. In many cases, it is therefore advisable to use the SAP locking mechanism .
Changes to data in a database are only finalized after a database commit (see LUW ). Prior to this, any database update can be reversed by a database rollback (see Programming transactions ). At the lowest isolation level (see the section on the "uncommitted read" under Locking mechanism ), this can result in the dataset selected by the SELECT command not really being written to the database. While a program is selecting data, a second program can add, change or delete lines at the same time. Then, the changes made by the second program are reversed by rolling back the database system. The selection of the first program thus reflects only a very temporary state of the database. If such "phantom data" is not acceptable for a program, you must either use the SAP locking mechanism or at least set the isolation level of the database system to "committed read" (see Locking mechanism ).
In a SELECT-ENDSELECT loop, the CONTINUE statement terminates the current loop pass prematurely and starts the next.
If one of the statements in a SELECT ... ENDSELECT loop results in a database commit, the cursor belonging to the SELECT ... ENDSELECT loop is lost and the processing terminates with a runtime error. Since each screen change automatically generates a database commit, statements such as CALL SCREEN , CALL DIALOG , CALL TRANSACTION or MESSAGE are not allowed within a SELECT ... ENDSELECT loop.
Related OPEN CURSOR , FETCH und CLOSE CURSOR
GO THROUGH THIS LINK
http://www.geocities.com/SiliconValley/Campus/6345/select.htm
THANKS
MRUTYUN

Problem with Qualified lookup field

Hi all
I have one qualified lookup field in main table of the repository. when i created the iview for ItemDetails then i selected all the fields of the main table which includes the qualified look up field . but when i see the preview then i am not able to see the field of qualified lookup field in the preview. it is not displaying but i selected the same field.
please help me out on Can we enter the data in the qualified table field which is part of main table in the repository while creating the record??
but i am able to edit the qualified lookup field which is part of main table. but the only problem while creating the record it is not displaying me the qualified lookup field. please help on this........
Thanks
Regards
Sunil

Hi Sunil,
It will not allow you to add the qualified lookup value in the main table record directly.
As the qualified lookup field in the mai table links the main table record with the qualified table fileds.
You will only be able to view the non-qualifier field values in the main table but the qualifier value for that particular record will be visible in the qualifier table only.
So as to populate the lookup qualifier you need to create the main rec then you can establish the link and populate the qualified table fields.
Hope it helps
Kindly reward points if found useful
Thanks
Simona

Select FOR ALL ENTRIES statement cannot get duplicates entries

Hi all,
t_yxapy_fields consist of
inty field
0001 kostl
0002 perid
0008 ansal
0008 preas
0008 trfst
The following is the code for me to transfer the contents of t_yxapy_fields into t_pa_fields.
SELECT dbtab
      FROM t777d
      INTO TABLE t_pa_fields
      FOR ALL ENTRIES IN t_yxapy_fields
      WHERE infty = t_yxapy_fields-infty.
And t_pa_fields just ended up with
field   infty
pa0001
pa0002
pa0008
Question:The first table have 3 similar infotype 0008 but the result table only have one pa0008. I need to filled up acordingly as what table 1 have. I need another 2 pa0008 in my 2nd table. What is wrng with my Select for all entries statement here?
Edited by: Siong Chao on Mar 27, 2010 10:35 AM

This has nothing to do with duplicates in t777d.
Correct, I failed to recognize that table t777d has only infty as key as pointed out by Aby. Thus in your particular case my comment was misleading. In general though FOR ALL ENTRIES removes all duplicate rows from your result set.
If you want the other 2 values just loop t_yxapy_fields this table and read t_pa_fields and if record found add the other values to t_pa_fields table. --> will trigger performance tuning issue
I'm pretty sure if you'd code this, you won't run into any performance issues, so follow Aby's recipe. To be more concrete, here's what I'd do: Define a mapping table t777d_tab, which holds the translation from infty to dbtab:
types:
begin of T_T777D_VIEW,
    INFTY type T777D-INFTY,
    DBTAB type T777D-DBTAB,
end of T_T777D_VIEW.
data:
T777D_TAB type hashed table of T_T777D_VIEW with unique key INFTY.
Fill table t_pa_fields, typed using t_t777d_tab from above, from table t777d. Then loop over your table t_yxapy_fields (I'd use [LOOP AT ... ASSIGNING|http://help.sap.com/abapdocu_70/en/ABAPLOOP_AT_ITAB_RESULT.htm] instead of LOOP AT ... INTO) and for each entry get the corresponding DBTAB value from t777d_tab (again use the [READ TABLE ... ASSIGNING|http://help.sap.com/abapdocu_70/en/ABAPREAD_TABLE_OUTDESC.htm] variant) and build your result table t_pa_fields.
Anyhow, I suspect that even with less optimal coding (e.g. using just standard table for lookup of DBTAB values) you'd not see much of an performance impact, because it seems that your internal tables are most likely rather small...
Cheers, harald

Syndiacting Qualified lookup in new XML

Hi Gurus,
Requiremnet is to syndicate qualified look up data into different XML
.to be specific ..We have created Vendor specific data as Qualified lookup table and are mapping this table in Syndication to INFREC idoc.
But while syndicating it back..the XML file just pulls out the vendor name .Requiremnent was that the XML should pull out MAterial -Vendor specific data.
Questions:
1Is this possible?
2.If yes please help me with this regards..I think i might be missing some setting..
Regards,
Vikrant M Kelkar

Hi Vikrant,
As per my understanding of your requirement you wnat to syndicate the qualified table data in the form of XML.
If this is the case then it is possible.
- In the syndicator the source structure is your repository structure and your destination structure should be an XML schema containing the idoc structure.
- You need to map your qualified table fileds with the corresponding idoc fields.
- If you do not intend to syndicate any other fields you need not map them.
Note:
You need to note the following things while performing Qualifier syndication
1) While syndicating qualified table fields you need to map the lookup field to the corresponding segment.Else it will not allow you to map the fields inside the qualified table
2) You need to make that particular segemnt as Repeatable XML node in the map properties.
3) Once these settings are done you can map the qualified field syou want and they will be syndicated in the form of .XML
4) Also note to map the Root node.At the beginning of the structure.
Hope it helped
Kindly reward points if found useful
Thanks
Simona

Restrict the user should not allow to select No Excise entry tab in MIGO

Hi
how to restrict the user should not allow to select No Excise entry tab in MIGO
if the material Excisable user can bale to select the No Excise entry tab in MIGO . my requirement .... if the Pop come Please enter Excise Invoice number and Excise Invoice Date user should not change the No Excise how to restrict pls advise me
@sakhi

These are the options provided by SAP keeping in mind Indian Scenario. Sometimes, vendor forget to send excise invoice copy with the material, in such case, you can select 'Only Part I'.
Even if you have maintain vendor excise details & material excise details (By mistake) in J1ID, system will throw an error message, excise invoice value is zero. In such case, we can select option 'No excise entry'.
Your requirement can't be fulfilled in standard way. Even if you go for any Z- developement, you will lose the option.

Dynamic select for all entries?

Hi!
Is it possible to do a dynamic SELECT FOR ALL ENTRIES IN... command?
sg. like:
DATA:
    select_text TYPE string,
    from_text TYPE string,
    where_text TYPE string.
SELECT FOR ALL ENTRIES IN <gt_table1> (select_text)
into corresponding fields of table <gt_table2>
FROM (from_text)
WHERE (where_text).
Thanks and Best Regards,
Tamas

Hi,
you can use the Dynamic Selects for FOR ALL ENTRIES, but i think you may need to use the correct Internal table to match the tabel structure
Regards
Sudheer

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

Dynamic Select One Lookup List restricted to a subset of values

I'm working with JDeveloper 10.1.3. trying to put an application together that needs two Lookup List the first is a Manufacturer Name and the second is items manufactured based on the selection of the first Lookup List choice (Manufacturer Name). I have two tables that make a nice master-detail relationship also I have a view that has the manufacturer name and what they manufacture but I just can't get a handle on how to set up the second lookup list to provide the subset of manufactured items based on the selection made in the first list. So the basic question is how do you restrict a Dynamic Select One Lookup List to a subset of values from the table based on a value stored in the application (on the page or in a bean). This has me stumped and any help would be greatly appreaicated.

I am not sure if you have tried using the partial trigger on your second lookup list.
Here's an overview of how you can do it @
1.) Create a binding on the page to keep the selected value from your first LOV.
2.) Set autoSubmit = true on your first LOV ) [ so that your binding in the first step gets populated upon selection]
3.) Set up an ID value for the first LOV component.
4.) Set up the partial trigger property on your second LOV to the ID of your first LOV.
5.) In your page definition, use the value from the binding in step1 to assign value to any where clause parameters on the view object for your second LOV.
HTH,
Shishir
donnellypl wrote:
I'm working with JDeveloper 10.1.3. trying to put an application together that needs two Lookup List the first is a Manufacturer Name and the second is items manufactured based on the selection of the first Lookup List choice (Manufacturer Name). I have two tables that make a nice master-detail relationship also I have a view that has the manufacturer name and what they manufacture but I just can't get a handle on how to set up the second lookup list to provide the subset of manufactured items based on the selection made in the first list. So the basic question is how do you restrict a Dynamic Select One Lookup List to a subset of values from the table based on a value stored in the application (on the page or in a bean). This has me stumped and any help would be greatly appreaicated.

Qualifier values are not part of a qualified lookup record

Hi
     I am getting the exception "Qualifier values are not part of a qualified lookup record" when I serach for a record in the Qualified table. The Table has both Qualfier and non-Qualifier fields, but all are of type display fields.
My question is If the filed is of type Qualifier then is it mandatory that it should be non-display Field?
if not can any one suggest me to get the record.
If we make Qualifier fields as NON-Dispaly fields in repository then it is working fine.
Here with I am providing the code
               Search serarch = new Search(repoSchemaCmd.getRepositorySchema().getTable("QT_NOTES").getId());
               serarch.addSearchItem(new FieldSearchDimension(repoSchemaCmd.getRepositorySchema().getFieldId("QT_NOTES","USER_PMF_ID")),new TextSearchConstraint("test", TextSearchConstraint.EQUALS));
               ResultDefinition rd =new ResultDefinition(repoSchemaCmd.getRepositorySchema().getTable("QT_NOTES").getId());
               //Returns the array of IDs for all display fields associated with the table
               rd.setSelectFields(repoSchemaCmd.getRepositorySchema().getTableSchema("QT_NOTES").getDisplayFieldIds());
               RetrieveLimitedRecordsCommand retrievedRecords =new RetrieveLimitedRecordsCommand(conn);
               retrievedRecords.setSession(userSessionID);
               retrievedRecords.setSearch(serarch);
               //retrievedRecords.setIds(RID);
               retrievedRecords.setResultDefinition(rd);
               try {
                    retrievedRecords.execute();
               } catch (CommandException e) {
                    throw new CommandException(e);
Regards,
Sandeep.

Hi Sandeep
I have a similar problem, would like to know what is the resolution to this issue.
Regards
Dilip

Workaround on all the limitations of Qualified Lookups, Multivalued Tuples.

Dear Experts,
As we all know, there are lots of limitations on Qualified Lookups in MDM 5.5 and also in MDM 7.1....
1) Can't write Assignments...
2) Failed validation won't specify which qualified link has failed.
3) Compare records won't show link wise comparison of qualified links.
4) Can't start qualified link level workflows.
5) Role level constraints not applicable for Qualified lookup and tables referencing from QL directly or indirectly.
6) Qualified link level check-in check-out operations are not possible.
7) Qualified link level unique constraints are not possible (this becomes pain if links get duplicated by mistake)
8) Duplication of QL link is not allowed in data manager (for copying Qualifier values in new Qualified link).
9) Tuple is replacement for qualified lookup, but its more restrictive than QL (validation are not allowed on multivalued tuple).
10) ....... many more (which might have discovered by you all)
What if we make all the qualified lookups as main table and link those table to actual main table using Lookup [ Main] field type?
Well it will restrict the data analysis objective which is one of goal of Master Data Management...
But this will solve all the problems and limitations due to Qualified Lookup or Multivalued Tuple!
I think its feasible and technically possible (But only in MDM 7.1 onward)
How is the IDEA !!!
Thanks & Regards,
- Shailesh.

Dear Michael,
Thanks for your valuable replay...
Well out of 9 pain points I listed above...
Some of them may be fixed in future releases...
But there are some points which (I feel) may not be on the feature list of future releases like....
2) Failed validation won't specify which qualified link has failed.
3) Compare records won't show link wise comparison of qualified links.
4) Can't start qualified link level workflows.
6) Qualified link level check-in check-out operations are not possible.
(all these points are applicable for tuples also)
Above points can be ignored at the time of fresh implementation
But its become blocker in new scenarios which are taken-up after go-live! (i.e expansion of already live repository)
Most of the people in MDM might not be aware of that import works on a single main table at a time.
Well you are an expert, what you said is something new and useful... Thanks for that !
Thanks & Regards,
Shaailesh.

Insert a record in Qualified Lookup Table

Hello everyone,
I need code to insert a record in Qualified Lookup Table where the non-qualifier is a record of type Country. Other fields are qualifiers.
I tried using QualifiedLookupValue.createQualifiedLink(). However, this only helps to insert in the qualifier values, how can I insert the non-qualifier (Country) value?
Any idea?
Many thanks in advance,
Baez

Hi guys,
Maybe the answer comes late but i'm recently working on this and the API works for me to create and update qualifier values.
Suppose recordMain is the main record, fldQFT is the qualified lookup field in main table, fldQualifier is the qualifier field in QFT table.
To add qualifier value you can use:
QualifiedLookupValue qualifiedLookupValue = new QualifiedLookupValue();
int index = qualifiedLookupValue.createQualifiedLink(recordMain.getId());
qualifiedLookupValue.setQualifierFieldValue(index, fldQualifier, MdmValue);
recordMain.setFieldValue(fldQFT, qualifiedLookupValue);
To update qualifier value, use:
QualifiedLookupValue qualifiedLookupValue = (QualifiedLookupValue) recordMain.getFieldValue(fldQFT);
qualifiedLookupValue.setQualifierFieldValue(index, fldQualifier, MdmValue);
recordMain.setFieldValue(fldQFT, qualifiedLookupValue);
Regards,
James

Syndicating Selected Qualified Lookup Entries

Similar Messages

Maybe you are looking for