Subject: Trouble in Multi-Select LOV. Does not populate records in Base Pag

Hi Friends,
I am trying to use multi-select LOV for the first time. But the base page table does not get populated after the rows are selected in the LOV. I am initializing the Base Page VO like below. And all fields are mapped between both the VO's, Can you please help as to what else could be the problem.
if("UPDATE".equals(s1))
vo.setMaxFetchSize(-1);
vo.executeQuery();
} else
if("CREATE".equals(s1))
vo.setMaxFetchSize(0);
vo.setPreparedForExecution(true);
}

Is there any other piece of code you have used?
Try my suggestion and follow the Dev guide once step by step to implement the multi select LOV. They have a nice sample and then you can compare where you went wrong. I feel like you are missing something part of setup.
--Shiv

Similar Messages

Multi-select LOV does not work in forms

the multi select LOV does not work in the form.
the LOV works individually but in the form it does not work. it does not allow multiple selection from the list.
is there a workaround for this or is this a bug ...?
any ideas ...?
thanx a lot.
null

Right, we cannot store more than one value in a single column in a table :), we were getting a lot of requests to support multiple select LOVs but requirements were contradictory if not mutually exclusive.
The only sense it makes is when used together with user-defined object types (nested tables for example) but the current [application building]infrastructure we have does not support this. However, we are looking into this and this feature maybe implemented in a future release.

Group Used as LOV does not return records

Have:
1. A header table called Claims
2. A detail table called ClaimLines
3. The Claims Table has a foreign key called emp_no which refers to an employee table ( Claims for an employee)
4. The ClaimLines table has a foreign key called mem_id which refers to an employee family members table that also has emp_no as a foreign key (family members for an employee)
5. A JHS group for Claims that shows the employee name and employee id. An LOV populates the employee name and employee id
6. A details group fro CalimLines that shows family member name. An LOV populates the member name and member id. (The idea is to pull family members for the employee selected in the header section in 5 above.
Problem:
The calims LOV populates the employee name and employee id correctly.
When I move to the calimlines (details), the members who should be restricted to the employee selected in the Claims group does not return any records.
The LOV for the members is based on a VO called DependentsofEmpolyee that has a where clause emp_no=:p_emp_id (:p_emp_id is a bind parameter)
The LOV group for the members has an EL expression in the Query Bind Parameters
p_emp_id=#{bindings.ClaimsEmpId.inputValue}. The expression is to restrict the members to those who belong to the employee selected in the Claims section of the page.
Debug gives the following information:
-ViewObject DependentsOfEmployee1: bind parameter values have not changed, NO Requery performed.
It seems that the p_emp_id is not being populated with the emp_id from the header section(Claims)
The same EL expression works if applied to a dynamic LOV. The drawback of the dynamic LOV is that is only populates two fields, the value attribute and the meaning attribute. In our case we need to populate more than one attribute.

Thanks for the input.
I tried the following
1. Create a managed bean in faces-config.xml.
<managed-bean>
<managed-bean-name>FamiliyLovContext</managed-bean-name>
<managed-bean-class>FamiliyLovContext</managed-bean-class>
<managed-bean-scope>session</managed-bean-scope>
</managed-bean>
2. Updated the skeleton class FamilyLovContext.java to:
public class FamiliyLovContext {
Number empId;
public void setEmpId(Number empId) {
this.empId = empId;
public Number getEmpId() {
return empId;
3. Copied tableLovItem to tableLovItemFamily and added the following to the section
<af:selectInputText
<af:setActionListener from="#{bindings.ClaimsEmpId.inputValue}"
to="#{FamilyLovContext.empId}"/>
4. Used the the new template for the lov item in the claimlines group.
5. set the query bind parameters of the lov group to #{FamilyLovContext.empId}
I gor the following error
16:38:08 ERROR (ApplyRequestValuesPhase) -java.lang.IllegalArgumentException: argument type mismatch
javax.faces.el.EvaluationException: java.lang.IllegalArgumentException: argument type mismatch
     at com.sun.faces.el.ValueBindingImpl.setValue(ValueBindingImpl.java:248)
     at oracle.adfinternal.view.faces.taglib.listener.SetActionListener.processAction(SetActionListener.java:50)
     at javax.faces.event.ActionEvent.processListener(ActionEvent.java:77)
     at oracle.adf.view.faces.component.UIXComponentBase.broadcast(UIXComponentBase.java:548)
     at oracle.adf.view.faces.component.UIXEditableValue.broadcast(UIXEditableValue.java:243)
     at oracle.adf.view.faces.component.UIXSelectInput.broadcast(UIXSelectInput.java:170)
The ClaimsEmpId attribute is Number(4,0)

Processing Multi Select LOV Results in Portal Forms

Hi,
I want to be able to create a portal form where i can use a multi-select LOV to create multiple records on a seperate table. How does one 'capture' all selected items so that one can do a seperate insert into a child table containing the items? When querying the form how can one programmatically set the items so that they appear as selected.
Thanks

Hi,
Were you able to fix this up? If so, can you please provide me some directions?
Thanks
Kamlesh

Problem with Headstart Multi-Select LOV

Hi,
I'm working on a few forms which should include a Multi-Select
LOV. Now here's the problem: One MSEL doesn't close; you can
select record(s), the LOV returns them, but doesn't disappear.
Clicking Cancel doesn't help.
Another MSEL-problem in another form: if you click Select All,
this selection isn't visible in the MSEL. He returns all of the
records, but it looks like he only selected one. Working with
CTRL to select more than one record doesn't work either. This
one closes fine.
As you know I have to include module component
QMS_MSEL_LOV_BUTTONS (which includes all button-functionality),
and then it should work, but it doesn't.
We've checked all the properties and they seem to be correct. It
isn't the first time we encountered these problems. We always
rebuilt the MSEL LOV, but it doesn't help this time.
Has anyone got an idea what's causing this problem.
P.S. There are also MSEL LOV's which operate just fine, without
any problems; only these two are doing strange things.
Thx,
Wouter

Workaround provided by Lauri Boyd seems to have worked:
A bug (#1985903) was introduced in Forms 6.0.8.13.0 and later which affected Headstart. This was fixed in Headstart patch 6.5.2.1 which is available through the Supplement Option.
Description
===========
1. When using a multi-select LOV (which is displayed in a modal dialog
window), you select the records you want, press OK, and the application exits.
2. When using a shuttle control to move records from left to right or vice
versa, you select the records you want, press '>' to move them, and the
application exits.
This occurs in Forms 6.0.8.13.0 and 6.0.8.14.1. It did NOT occur in prior
releases. This is some kind of forms bug.
Workaround
==========
For some reason the call to procedure renumber in qms$msel.process_records
causes the application to exit. If you copy the code from renumber to all the
places from which it is called, it works fine.
- open qmslib65.pll in Form Builder
- open package body qms$msel
- find procedure process_records and define a local variable l_recno of type
number.
- find local procedure renumber and copy the body of this procedure
(everything
after 'begin' and before 'exception').
- replace each call to 'renumber;' with the copied code.
Regards,
Lauri

Multi Select LOV Gives CDI-21600

Have discovered that the Multi Select LOV facility is causing error CDI-21600 in some circumstances.
We have 2 tables -
Instance_Type_Owners
ito_int_id
ito_owner_org_id
ito_owner_ort_id
ito_created_by
ito_created_date
pk is the first 3 columns
Instance_Type_Relations
itr_ito_int_id1
itr_ito_owner_org_id1
itr_ito_owner_ort_id1
itr_ito_int_id2
itr_ito_owner_org_id2
itr_ito_owner_ort_id2
pk is all 6 columns, with 2 fk's pointing back to Instance_Type_Owners.
I'm creating a 2 block form, master block has base table of Instance_Type_Owners, detail block has base table of Instance_Type_Relations, using a key link based on the fk pointing back to id1's. I also want a multi-select LOV using the fk pointing back to id2's. This is giving me CDI-21600; the error goes away if I take the Template/Library Object qmsso$msel_lov_item off the leading element of the fk used by the LOV (i.e. itr_ito_int_id2).
I've double-checked everything about the definitions of these tables/pks/fks, & everything looks ok. I've successfully used multi-select LOV on other tables with a similar fk structure (ie relationship tables, with 2 fks pointing back to the same master table), & with multi-column fks, so it's not being caused by any of these reasons.
Any ideas on what may be causing this?

Thanks for the response. I have seen the checklists for causes of this problem, & have checked all tables/fks/pks involved in the form. I can successfully generate forms which maintain these tables, or with lookups to these tables. The problem only happens when I use the Headstart multi-select LOV facility. As I said, the problem goes away immediately I remove the 'qmsso$msel_lov_item' template/library object from the leading element of the fk in the base table.
If I go to Designer support & tell them this, I'm pretty sure they'll say it's a Headstart problem, since it only happens when Headstart facilities are involved.

Multi-select LOV bug and Developer6i R2 Patch7

Has anyone verified that Patch7 corrects the problem with multi-
select LOV bug (see below). The Headstart6i Report Launch form
(QMS0012F) exhibits this bug (when using the demo reports for
example) and we were unsuccessful applying the workaround (see
below). We will upgrade to Patch7 if this bug is fixed or we
could use a little help from the HeadStart team correcting the
Report Launch form to get around this bug. Thanks, Keith
We have found one odd quirk with Headstart 6i and Forms
6i versions 6.0.13 and higher.
Description ===========
1. When using a multi-select LOV (which is displayed in a modal
dialog window), you select the records you want, press OK, and
the application exits.
2. When using a shuttle control to move records from left to
right or vice versa, you select the records you want, press '>'
to move them, and the application exits. This occurs in Forms
6.0.8.13.0 and higher. It did NOT occur in prior releases. This
is some kind of forms bug.
Workaround ==========
For some reason the call to procedure 'renumber' in
qms$msel.process_records in qmslib65.pll causes the application
to exit. If you copy the code from renumber to all the places
from which it is called, it works fine.

So far as I know, this bug has not yet been corrected.
You will have to apply the fix as described in your email
message.
Regards, Lauri

Multi-Select LOV for Report Parameters

I have a LOV defined in Oracle Portal as a Multi-Select LOV. When I assign this to an optional report parameter when defining a reports definiton file and run the parameter screen, it comes up as a combo box. Is a combo box the only type of LOV I can use for an Oracle Reports Parameter.
Thanks
Jody

With whatever i could make out is you are trying to change a discovere report to xml; publisher report isnt it?
To answe to your question, directly it is not possible to have In clause but you could use some smart logic like lexical parameters etc to achieve similar things.I guess you cannot do in in EBS Reports too.

Error : Selected user does not exist

I m trying to send the alert messages. And for this I am using message object of DIAPI and sending alert to usercode 'manager' of SAP B1. But i m facing the error that 'Selected user does not exist' and it is present in the OUSR table for the user related details.

Hi, Amit Jadon!
If you send a code snippet, it will be more helpfull for us to solve a problem.
It's my "sending for yourself" example. Log in with a "problem" user and try it:
public void SendMess(string Mess, string Subj)
int errn;
string mes;
SAPbobsCOM.Messages msg;
msg = (SAPbobsCOM.Messages) pCmp.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oMessages); //pCmp - company obj
msg.MessageText = Mess;
msg.Subject = Subj;
msg.Recipients.Add();
msg.Recipients.SetCurrentLine(0);
msg.Recipients.UserCode = pCmp.UserName;
msg.Recipients.NameTo = pCmp.UserName;
msg.Recipients.SendInternal = SAPbobsCOM.BoYesNoEnum.tYES;
msg.Add();
pCmp.GetLastError(out errn, out mes);
if (0 != errn)
    SBOApp.MessageBox("Error in msg.Add(); " + errn + ", " + mes, 1, "Ok", null, null);
HTH,
Alexey

Multi-select LOV's hang form and use 100% CPU power

Hello,
We are using Designer 6i (6.5.52.1.0) and Headstart 6.5
In one of our forms we are using 6 Multi-select LOV's.
When we click the Cancel or Ok button (included through QMS_MSEL_LOV_BUTTONS), or hit Enter query in one of the ML_... blocks the form hangs and starts using all the CPU-power. I've tested this locally (c/s) and through the web (iAS), same result...
I already rebuilt the LOV's but the problem isn't solved.
We've got other forms with one or two multi-select LOV's, and these work fine.
Has anyone experienced this behaviour before, and what is the cure?
Thanks in advance!
Wouter

Wouter,
If you are running against Solaris, you could be running into the following:
Headstart applications that run via webforms on a Sun Solaris application server, suffer again from bug 1985903. This bug was spotted and solved a time ago and seemed to be solved at next
releases of Forms 6i. Now, on Solaris the bug is introduced again.
Description
===========
1. When using a multi-select LOV (which is displayed in a modal dialog
window), you select the records you want, press OK, and the application exits.
2. When using a shuttle control to move records from left to right or vice
versa, you select the records you want, press '>' to move them, and the
application exits.
This occurs in Forms 6.0.8.13.0 and 6.0.8.14.1. It did NOT occur in prior
releases. This is some kind of forms bug.
Workaround
==========
For some reason the call to procedure renumber in qms$msel.process_records
causes the application to exit. If you copy the code from renumber to all the
places from which it is called, it works fine.
- open qmslib65.pll in Form Builder
- open package body qms$msel
- find procedure process_records and define a local variable l_recno of type
number.
- find local procedure renumber and copy the body of this procedure
(everything
after 'begin' and before 'exception').
- replace each call to 'renumber;' with the copied code.
A new version of qms$msel package body is available on iXchange for download.
See Headstart Oracle Designer 6i, Bugs and Fixes.
Hope this helps,
Marc Vahsen
Headstart Team
Oracle NL

Is it possible to Add to Multi-Select Lov through Customization?

Hi All,
I have a Oracle Seeded page( Oracle Training Administrator).
Clients wants a new field with Multi-Select LOV on that.
Is is possible to create Multi-Select LOV through Customization or changing the page in JDeveloper?
As per OAF Developer guide, Multi-Select Lov on single field in not possible and their is topic on 'Multi-Select on Advance Table'.
Please guide me, is it possible? If Yes, steps to achieve this will be great help for me.

That is correct you can only add a normal LOv through personalization and not a multi select LOV.

Multi-select LOV return into single row

I have a multi-select lov setup on a column in a table layout. I want to be able to select the lov, select multiple rows in the lov and then when I press the select button in the lov window to have those lov records select return to the same column. Currently, the lov returns the multi lov records into multiple records on my table layout.

IN JHeadstart 10.1.3, we will add the option to return multiple selected values as a comma-separated list into the same field. With 10.1.2 this is not possible. You can implement this yourself by overriding method JhsDataAction.onLovSelect.
Steven Davelaar,
JHeadstart Team.

LOV does not return value to the base page sometimes

Hi,
I have created messageLOV type items. These LOVs do return value to the base page usually. We have a user in Uruguay who is trying to use the page which has the LOVs. He says the LOV takes a long time to return to the main page after he clicks on quick select and also the value does not get populated in the main page.
We have not been facing any such problem here in India. The LOV has been tested rigorously with no issues as such.
Can you please suggest a reason why such a problem is occuring? Expecting your replies soon
Thanks,
Priya

Thiyaga, did you read the devguide or the tutorial ?
Can you please give me the inputs about the creation of LOV and it requires how many lov mappings as mandatory?
This is there in the devguideHow to identify the mapping fields of an LOV which is already existing in the base page to reproduce in a similar way and need to do a customization on top of it ?
Open the page XML and you can find the LOV mappings.Tapash

I am having trouble printing I have a connection to my printer wirelessly but does not print out the correct page I want.When I do print I get a bunch of pages more than is needed and also get a code and symbols please help I am jammed at work

I am having trouble printing I have a connection to my printer wirelessly but does not print out the correct page I want.When I do print I get a bunch of pages more than is needed and also get a code and symbols please help I am jammed at work

This can be the result of selecting the wrong driver. An older, unsupported laser printer will sometimes work with the generic Postscript driver.

Error: Selected disk does not exist (21) Module-SRE-700

Already tried everything that the recovery cisco commands, anyone have idea how to solve the problem of the print shown in print?
Initializing memory #2. Please wait...
This may take a minute....
Serial ATA Port 0 : Hitachi HTE545050B9A300
DDR Memory 4096 MB detected
Intel(R) Core(TM)2 Solo CPU    L3400 @ 1.86GHz
BIOS SM 3.52.8, BIOS Build date: 02/08/2011
System now booting...
Please wait...
Please press P to select Primary Boot Loader ...
          or S to select Secondary Boot Loader ...
          or wait to boot from default configuration ...
Now booting from primary boot loader....
Authenticating boot loader....
Primary Boot Loader Authenticated - booting....
ServicesEngine boot-loader> install_key waas-accelerator-4.4.5c.4-k9.bin
Keyfile Size 202814577 over limit 32768 will not burn into flash
ServicesEngine boot-loader> verify
Loading disk:/bzImage ... Unable to load image
Error: Selected disk does not exist (21)
Unable to boot image
Unrecognized command
ServicesEngine boot-loader>
#service-module sm 1/0 session
Trying 172.20.245.1, 2067 ... Open
Please wait...
Please press P to select Primary Boot Loader ...
          or S to select Secondary Boot Loader ...
          or wait to boot from default configuration ...
Now booting from primary boot loader....
Authenticating boot loader....
Primary Boot Loader Authenticated - booting....
Please enter '***' to change boot configuration:
Trying to reset Service Module SM1/0.
May 7 11:27:33.055: %SRE_SM-6-STATE_CHANGE: SM1/0 changing state from SERVICE_MODULE_STATE_ERRQ to SERVICE_MODULE_STATE_SHDN
Initializing memory #1. Please wait...
Initializing memory #2. Please wait...
This may take a minute....
Serial ATA Port 0 : Hitachi HTE545050B9A300
DDR Memory 4096 MB detected
Intel(R) Core(TM)2 Solo CPU    L3400 @ 1.86GHz
BIOS SM 3.52.8, BIOS Build date: 02/08/2011
System now booting...
Please wait...
Please press P to select Primary Boot Loader ...
          or S to select Secondary Boot Loader ...
          or wait to boot from default configuration ...
Now booting from primary boot loader....
Authenticating boot loader....
Primary Boot Loader Authenticated - booting....
Please enter '***' to change boot configuration:
Detect and Initialize network device
Backup current platform configurations....
SRE step 1 - SM registration...
Finding (hd1,3)/296e03bc-3236-4a68-a178-688e56400a1e, failed
Local install not supported
Response - no installation needed (len: 422)
SRE Installation Not Needed
Restoring orignial configuration...
Updating flash with bootloader configuration.
Please wait ................... done.
May 7 11:29:03.331: %SM_INSTALL-6-INST_RBIP: SM1/0 received msg: RBIP Registration RequestLoading disk:/bzImage ... Unable to load image
Error: Selected disk does not exist (21)
Unable to boot image
þ
Initializing memory #1. Please wait...
Initializing memory #2. Please wait...
This may take a minute....
Serial ATA Port 0 : Hitachi HTE545050B9A300
DDR Memory 4096 MB detected
Intel(R) Core(TM)2 Solo CPU    L3400 @ 1.86GHz
BIOS SM 3.52.8, BIOS Build date: 02/08/2011
System now booting...
Please wait...
Please press P to select Primary Boot Loader ...
          or S to select Secondary Boot Loader ...
          or wait to boot from default configuration ...
Now booting from primary boot loader....
Authenticating boot loader....
Primary Boot Loader Authenticated - booting....
Please enter '***' to change boot configuration:
Detect and Initialize network device
Backup current platform configurations....
SRE step 1 - SM registration...
Finding (hd1,3)/296e03bc-3236-4a68-a178-688e56400a1e, failed
Local install not supported
Response - no installation needed (len: 422)
SRE Installation Not Needed
Restoring orignial configuration...
Updating flash with bootloader configuration.
Please wait ................... done.
May 7 11:30:31.339: %SM_INSTALL-6-INST_RBIP: SM1/0 received msg: RBIP Registration RequestLoading disk:/bzImage ... Unable to load image
Error: Selected disk does not exist (21)
Unable to boot image
ú
Initializing memory #1. Please wait...
Initializing memory #2. Please wait...
This may take a minute....
Serial ATA Port 0 : Hitachi HTE545050B9A300
DDR Memory 4096 MB detected
Intel(R) Core(TM)2 Solo CPU    L3400 @ 1.86GHz
BIOS SM 3.52.8, BIOS Build date: 02/08/2011
System now booting...
Please wait...
Please press P to select Primary Boot Loader ...
          or S to select Secondary Boot Loader ...
          or wait to boot from default configuration ...

Hi,
Opened a tac and managed to get the resolution of the problem. For those with the same problem reported by me above just follow the procedure below:
1. uninstall existing SRE-V software
http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/sre_v/1.5/user/guide/software.html#wp1055364
2. run sm-hw-util to set sata mode to IDE
http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/sre_v/1.5/user/guide/software.html#wp1091438
3. configure a static, 32bit route to point the service module IP address to the SM slot/0 interface
ip route 255.255.255.255 SM slot/0
4. install WAAS:
http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v421/module/installation/guide/wssmcfg.html#wp47040
http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/sre_v/1.5/user/guide/software.html#wp1091438

Subject: Trouble in Multi-Select LOV. Does not populate records in Base Pag

Similar Messages

Maybe you are looking for