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.

Similar Messages

How to create multiple rows in a child table from the multi select Lov

Hi
We have Departments and EmployDept and Persons tables and each employee can associate multiple departments and vice versa.While creating a Department page there should be a Multi Select LOV(values from Persons table) with search option for the Persons.From the search panel we can select multiple persons for that department.Suppose we have selected 5 persons and click on submit, then it should create 5 rows in the EmployDept table for 5 persons with that department id.
Any inputs on how to implement this scenario please..

Maybe you can get some ideas from here -
http://adfdeveloper.blogspot.com/2011/07/simple-implementation-of-af.html

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.

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

APEX - passing values from LOV's or multi-select LOV's to another APEX form

I am new APEX development and I need to take the values from LOV's and multi-select LOV's and pass them to another APEX form. I want to take those passed values and use them in the where clause of the base-table in the called form. Any assistance would be greately appreciated.

Hi,
Refer this example
http://www.talkapex.com/2009/07/apex-how-to-pass-multiselect-list.html
Example: http://apex.oracle.com/pls/otn/f?p=20195:2100
Regards,
Kartik Patel
http://patelkartik.blogspot.com/
http://apex.oracle.com/pls/apex/f?p=9904351712:1

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.

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

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

Multi-Select LOV doesn't work where 1

I have a form with 1 master & 2 detail blocks. Each of the detail blocks has an LOV, & I'd like both to use the multi-select LOV facility within Headstart. However, this doesn't work if there's > 1 multi-select LOV within the form, for these reasons -
1. If there's > 1 multi-select LOV, you have to include reusable module component qms_msel_lov_buttons for each. As this is reusable, you can't edit the name. Therefore you have duplicate block names, therefore generator discards the names specified in Des2K & uses default block names of MC0, MC1 etc.
2. Headstart code in qms$init_application sets the lov block prefix to ML_. At runtime, the form fails with FRM-40104: No such block: ML_MC1.
I can't see any way of influencing Des2k's choice of block name, short of copying the reusable component into a specific component. Is there any workaround in Headstart you can suggest, to make this facility work?

Cheryl,
You are correct, you must make a specific copy of the reusable module component to work around this. I will record this as an enhancement request for future releases. Thanks for the info.
Regards,
Lauri

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.

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.

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

SEARCH item in MULTI-SELECT LOV (Hierachical Tree)

I have created a multi-select LOV using a hierarchical tree; providing the query for the tree in the Functional/Data Query property.
The Multi-Select LOV works fine. As you would suspect some LOV's have long lists that one must scroll through.
I would like to implement a SEARCH field (as seen in Forms standard LOV functionality) that will search through my Tree Node values and highlight the item searched (again as the standard LOV functionality works). Thus, allowing the user to quickly find the values in the list.
How do I go about referencing the Tree Node values to the value in the search (field) item?

Hello,
Search, through the FTree package's functions, those that allows to navigate through the leaves.
http://www.oracle.com/webapps/online-help/forms/10g/state?navSetId=_&navId=3&vtTopicFile=designing_forms/objects/manip_ht_runtime.html&vtTopicId=
Francois

Multiple Default Values in a Multi-Select LOV Parameter?

Hi,
I have a report in BI Publisher standalone version 10.1.3.4. The report has a list of values called org_lov. This lov is attached to a multi-selection p_org_code parameter from which it is desirable to also have multiple default values.
For example, if org_lov has the following values:
100
101
102
103
104
105
106
I would like to have 3 default values and have 100, 101,105 as the defaults if the user doesn't specifically select anything from the LOV. So far my testing has only allowed a single default value.
Here are my settings:
Data type = string
Multiple Selection = checked
Can select All = checked (all values passed)
On the Default Value field, I have tried the following:
1. 100, 101,105
2. [100, 101,105]
3. '100', '101','105'
4. (100, 101,105)
5. ['100', '101','105']
6. ('100', '101','105')
I don't need these default values highlighted in the LOV, I just need it passed correctly to the query (a data template).
Thank you in advance for any input.

Hi,
Sorry for the delayed reply. I tried what you suggested but the problem is that by having the "Multiple Selection" property of the parameter unchecked, the result is that it allows the user to only have a single value passed. The user wants the option to select multiple values AND also have the multiple default values.
Thanks anyway.

Multi Select LOV Gives CDI-21600

Similar Messages

Maybe you are looking for