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.

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

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

  • 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

  • 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                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • How to convert single column into single row

    I need to convert single column into single row having n no.of.values in a column. without using case or decode. I need a query to display as below.
    emp_id
    100
    101
    102
    102
    103
    200
    I need output like 100,101,102,103,104.........200.

    I assume you want to convert 200 rows with one column into one row with 200 columns. If so, this is called pivot. If you know number of rows (max possible number of rows) and you are on 11G you can use PIVOT operator (on lower versions GROUP BY + CASE). Otherwise, if row number isn't known, you can use dynamic SQL or assemble select on clent side. Below is example emp_id = 1,2,..5 (to give you idea) and you are on 11G:
    with emp as (
                 select  level emp_id
                   from  dual
                   connect by level <= 5
    select  *
      from  emp
      pivot(
            max(emp_id) for emp_id in (1 emp_id1,2 emp_id2,3 emp_id3,4 emp_id4,5 emp_id5)
       EMP_ID1    EMP_ID2    EMP_ID3    EMP_ID4    EMP_ID5
             1          2          3          4          5
    SQL>
    SY.

  • Convert  multiple rows into single rows for the respective index name

    Dear Experts,
                             I want to convert  multiple rows into single rows for the respective index name,
                            Here is my query.
    SELECT user_tables.table_name, user_indexes.index_name, user_ind_columns.column_name
    FROM user_tables
    JOIN user_indexes on user_indexes.table_name = user_tables.table_name
    join USER_IND_COLUMNS on USER_INDEXES.INDEX_NAME = USER_IND_COLUMNS.INDEX_NAME
    where user_indexes.index_name not like '%PK%' AND user_ind_columns.column_name NOT LIKE '%SYS%'
    ORDER BY user_tables.table_name,user_indexes.index_name;
    Result of previous query
    TABLE_NAME
    INDEX_NAME
    COLUMN_NAME
    T1
    IDX_ACCNTYPCFG1
    ENABLE_SERVICE
    T1
    IDX_ACCTTYPCFG1
    ACC_CODE
    T1
    IDX_ACCTTYPCFG1
    ACCTYPE
    T2
    IDX_ACCTTYPCFGAPP1
    ACCTYPE
    T3
    IDX_ACTLG1
    MOBILE_NO
    T3
    IDX_ACTLG1
    ID
    Desired output required is
    TABLE_NAME
    INDEX_NAME
    COLUMN_NAME
    T1
    IDX_ACCNTYPCFG1
    ENABLE_SERVICE,ACC_CODE,ACCTYPE
    T2
    IDX_ACCTTYPCFGAPP1
    ACCTYPE
    T3
    IDX_ACTLG1
    ACCTYPE,MOBILE_NO
    please help.

    Maybe
    with
    user_tables as
    (select 'T1' table_name,'IDX_ACCNTYPCFG1' index_name,'ENABLE_SERVICE' column_name from dual union all
    select 'T1','IDX_ACCTTYPCFG1','ACC_CODE' from dual union all
    select 'T1','IDX_ACCTTYPCFG1','ACCTYPE' from dual union all
    select 'T2','IDX_ACCTTYPCFGAPP1','ACCTYPE' from dual union all
    select 'T3','IDX_ACTLG1','MOBILE_NO' from dual union all
    select 'T3','IDX_ACTLG1','ID' from dual
    select table_name,
           case index_name when 'IDX_ACCNTYPCFG1' then 'IDX_ACCTTYPCFG1' else index_name end index_name,
           listagg(case column_name when 'ID' then 'ACCTYPE' else column_name end,',') within group (order by null) column_name
      from user_tables
    group by table_name,case index_name when 'IDX_ACCNTYPCFG1' then 'IDX_ACCTTYPCFG1' else index_name end
    TABLE_NAME
    INDEX_NAME
    COLUMN_NAME
    T1
    IDX_ACCTTYPCFG1
    ACCTYPE,ACC_CODE,ENABLE_SERVICE
    T2
    IDX_ACCTTYPCFGAPP1
    ACCTYPE
    T3
    IDX_ACTLG1
    ACCTYPE,MOBILE_NO
    Regards
    Etbin

  • Combining Multiple Rows into single row with multple columns

    Hi Experts,
    I have the following requirement, kindly help me.
    I have data in my table like below.
    ID NAME DEPT
    1 Sam 10
    1 Sam 20
    2 alex     30
    2 alex 40
    2 alex 50
    3 vinod 60
    3 vinod 70
    I want to show the same data into single row with dynamically generating columns for DEPT. I want show like below.
    ID NAME DEPT1 DEPT2 DEPT3
    1 Sam 10 20
    2 alex 30 40 50
    3 vinod 60 70
    It's urgent requirement, kindly help me.
    Thanks in advance.

    Right I've had my drink, so what was this "urgent" question then?
    798616 wrote:
    I have data in my table like below.
    ID NAME DEPT
    1 Sam 10
    1 Sam 20
    2 alex     30
    2 alex 40
    2 alex 50
    3 vinod 60
    3 vinod 70
    I want to show the same data into single row with dynamically generating columns for DEPT. I want show like below.Dynamic numbers of columns eh! Tricky.
    If you understand how SQL statements are executed it's along these lines...
    1. Open Cursor
    2. Parse SQL statement and determine columns
    3. Bind in any input values
    4. Fetch data
    5. Bind out values to columns
    6. Repeat step 3 until no more data
    7. Close cursor
    Now, you're expecting that you can determine the columns (step 2) from the fetched data (step 4 onwards). You can't. The SQL engine needs to know the expected columns before any data is fetched so, it can't base the number of columns on the data itself.
    If you need that requirement, you would need to query the data first and build up a dynamic query based on the data and then execute that dynamically built query to fetch the data and pivot it into those columns, which means that you have queried the data twice. Not good practice and not good (or simple) coding.
    What you're talking of doing is something that should be handled at the presentation/interface layer, not as part of the data fetch.
    Typically these sorts of things are handled most easily in report generation/writer tools such as Oracle Reports, Business Objects etc. where they fetch the data from the database and then process it to format it on the display, pivoting the results as required.
    It's not something that lends itself to be easily achieved in SQL. Yes, SQL can do pivoting of data quite easily, but NOT with a dynamic number of columns.
    If you were to specify that there is a maximum number of columns that you could get (rather than wanting it dynamic), then you can do it simply in SQL with the max-decode method...
    SQL> ed
    Wrote file afiedt.buf
      1  with t as (select deptno, ename, row_number() over (partition by deptno order by ename) as rn from emp)
      2  --
      3  select deptno
      4        ,max(decode(rn,1,ename)) as ename1
      5        ,max(decode(rn,2,ename)) as ename2
      6        ,max(decode(rn,3,ename)) as ename3
      7        ,max(decode(rn,4,ename)) as ename4
      8        ,max(decode(rn,5,ename)) as ename5
      9        ,max(decode(rn,6,ename)) as ename6
    10        ,max(decode(rn,7,ename)) as ename7
    11        ,max(decode(rn,8,ename)) as ename8
    12        ,max(decode(rn,9,ename)) as ename9
    13        ,max(decode(rn,10,ename)) as ename10
    14  from t
    15  group by deptno
    16* order by deptno
    SQL> /
        DEPTNO ENAME1     ENAME2     ENAME3     ENAME4     ENAME5     ENAME6     ENAME7     ENAME8     ENAME9     ENAME10
            10 CLARK      KING       MILLER
            20 ADAMS      FORD       JONES      SCOTT      SMITH
            30 ALLEN      BLAKE      JAMES      MARTIN     TURNER     WARD
    SQL>

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

  • How to convert select-options table into single field internal table

    Hi,
    My requirement is to convert select-options table into single internal table which has one field.
    e.g. select-options: s_matnr for mara-matnr.
           select-options table can have options  'BT',"EQ", "NE", "GE", "GT", "LE", "LT", "CP" etc. select-options table
           have   Sign:I ,Option:BT, Low: 1, High.10.The new internal table records should be 1,2,3,4,5,6,7,8,9,10.
    Please suggest any function module available for this scenario in SAP.
    Thanks,
    Somi.
    Edited by: somi reddy satti on Sep 15, 2009 3:18 PM

    Hi Sowmya,
    Here is the answer if I understand well of your question.
    Data: begin of gt_mon OCCURS 0,
                  mon(2)             TYPE n,
             end of gt_mon.
    Data: begin of gt_year OCCURS 0,
                  year(4)             TYPE n,
             end of gt_year.
    Select-options: s_period       FOR ptdw_pws_db-kmonth NO-EXTENSION
                                                                                    DEFAULT sy-datum(6)
                                                                                    TO sy-datum(6).
    For example according to above statement period is 201110 is 201201.
    Period field does n't exists in SAP for selection. If your selection is on date based on period which is given on the selection-screen then you need to convert the period to date by concatenating ( or using FM to convert )01 at the end of each period . You need to declare one range table for date to select the data from table.
    loop at s_period.
    gr_date-sign   = s_period-sign.
    gr_date-option = s_period-option.
    COncatenate s_period-low
                          '01'
    into gr_date-high.
    COncatenate s_period-high                   
                           '01'
    into gr_date-low
    append gr_date.                      
    ENDloop.
    Thanks,
    Satheesh

  • 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

Maybe you are looking for