Steps to create LOV dynamically

Hello All,
I want to create LOV dynamically.in my Oracle Forms 6I
Is there any code which can create LOV dynamically using coding.
I can create Record group dynamically. but I want to create LOV dynamically not from object browser of Form Builder by pressing Add LOV option.
Kindly help me.
Thanks
HARSH SHAH

Forms does not have a Built-in for dynamically creating an LOV; these objects can only be created in the Forms Builder during design time. You can, as numerous people have tried to demonstrate, change the Record Group an LOV uses dynamically. Unless you are changing the Column Mapping Properties of the LOV, using different Record Groups to supply the data for an LOV should work for you. If you need to change the Column Mapping Properties, then you will need to create multiple LOV objects with the different mapping you need and then assign the LOV to your Item dynamically.
Hope this helps,
Craig...

Similar Messages

Steps to create LOV.

Hi All,
Crystal Version 10.
Can someone please help me write the steps to create a LOV? I do not exactly know what is LOV, I have a requirement that is the report should prompt me for the parameters. Now that I only know it is possible using LOV, I do not have access to our BO Server. I need to send them (guys who deploy the reports on the server) the exact steps to do that. Please co-operate and write steps for me.
Thanks
-Azhar

I think you cannot create dynamic LOVs in Crystal 10. It is possible in Crystal XI and latter versions. You can add the database values to the parameter but if any changes done in the database will be updated by manually inserting the database values. Click on default values and select the database field and add all the values from database to default values to show the list while selecting the parameter values. This list will be static and need to re import all the database values again if any changes done in the database. For more details please go through the following SAP note
[https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_erq/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes.do]
Regards,
Raghavendra

Steps to create LOV-form not correct

Hi,
In order tot create an LOV-form we follow the steps from the Headstart 6.5 user guide (we are using Designer 9i).
We come to the conclusion that these steps are not complete/correct for Designer 9i.
First the keys f7 and f8 are not available with qmsso$modal_dialog_window, so we use our own template object which is basically the same but set to document window.
Second the code to invoke the LOV is not generated so we have to manually add this code in Designer.
Can anyone confirm out findings on this matter?
Kind regards,
Pascal

Forms does not have a Built-in for dynamically creating an LOV; these objects can only be created in the Forms Builder during design time. You can, as numerous people have tried to demonstrate, change the Record Group an LOV uses dynamically. Unless you are changing the Column Mapping Properties of the LOV, using different Record Groups to supply the data for an LOV should work for you. If you need to change the Column Mapping Properties, then you will need to create multiple LOV objects with the different mapping you need and then assign the LOV to your Item dynamically.
Hope this helps,
Craig...

Creating a dynamic lov based on a column

Hi,
I want to create a dynamic lov based on a column in a database-table.
Eg. the query
'select code, description from code_table'
is the contents of the column 'lov_query' in the table 'parameters'.
For every parameter there can be a different lov-query, but the result is always
two columns (code and description, number and name, etc.), exactly what you need to use in a lov.
I've written a (dbms_sql) function that takes the parameter-id and returns the lov_query.
create or replace function "GET_PMR_LOV"
(pmr_id in NUMBER)
return VARCHAR2
is
cur INTEGER := DBMS_SQL.OPEN_CURSOR;
fdbk INTEGER;
l_pmr_id NUMBER(9) := pmr_id;
l_stmnt VARCHAR2(2000);
begin
DBMS_SQL.PARSE
(cur, 'select pmr.lov_query from parameters pmr where pmr.ID ' || ' = 'L_PMR_ID', DBMS_SQL.NATIVE);
DBMS_SQL.BIND_VARIABLE (cur, 'L_PMR_ID', l_pmr_id);
DBMS_SQL.DEFINE_COLUMN (cur, 1, l_stmnt, 2000);
fdbk := DBMS_SQL.EXECUTE (cur);
fdbk := DBMS_SQL.FETCH_ROWS (cur);
IF fdbk > 0
THEN
DBMS_SQL.COLUMN_VALUE (cur, 1, l_stmnt);
return (l_stmnt);
ELSE
return null;
END IF;
DBMS_SQL.CLOSE_CURSOR (cur);
END;
But now I'm stuck on how to pass on this statement in HTMLDB
as an dynamic lov, I don't seem to be able to execute this statement
into the two display and return columns. Any ideas?

Hello again,
This lov is on an updatable report-column where the user has to make a choice from an non-named, popup and query-based lov. In the lov-query box I have just put:
"return get_pmr_lov(:p41_param_id)" (without the quotes ;-)
Here's my latest version plus an alternative, which both seem to work fine:
create or replace function "GET_PMR_LOV"
(pmr_id in NUMBER)
return VARCHAR2
is
cur INTEGER := DBMS_SQL.OPEN_CURSOR;
fdbk INTEGER;
l_pmr_id NUMBER(9) := pmr_id;
l_stmnt VARCHAR2(1000);
begin
DBMS_SQL.PARSE (cur, 'select pmr.lov_query from paramaters pmr where pmr.ID ' || '= :L_PMR_ID', DBMS_SQL.NATIVE);
DBMS_SQL.BIND_VARIABLE (cur, 'L_PMR_ID', l_pmr_id);
DBMS_SQL.DEFINE_COLUMN (cur, 1, l_stmnt, 1000);
fdbk := DBMS_SQL.EXECUTE (cur);
fdbk := DBMS_SQL.FETCH_ROWS (cur);
IF fdbk > 0 THEN
DBMS_SQL.COLUMN_VALUE (cur, 1, l_stmnt);
return (l_stmnt);
ELSE
return null;
END IF;
DBMS_SQL.CLOSE_CURSOR (cur);
END;
create or replace function "GET_PMR_LOV2"
(pmr_id in NUMBER)
return VARCHAR2
is
l_pmr_id NUMBER(9) := pmr_id;
l_stmnt VARCHAR2(1000);
BEGIN
EXECUTE IMMEDIATE 'select pmr.lov_query from parameters pmr where pmr.ID = :1'
INTO l_stmnt USING l_pmr_id;
return l_stmnt;
END;
The error-message remains the same, unable to bind :p41_param_id !

Problem - Creating a Dynamic LOV using duplicate value in select statement

I am trying to create a Dynamic LOV by attempting to follow a pattern similar to the following:
select shop_name d, shop_id r
from shops
order by 1
However, I want to use the shop_name twice as in the following because I do not have any other unique identifier available such as a shop_id to associate with the shop name:
select shop_name d, shop_name r
from shops
order by 1
But I get an error where I am not allowed to duplicate the shop_name in the select statement. I read somewhere on this forum where it can be done but I can't find exactly how.
Can someone tell or show me how to accomplish this?
Thanks in anticipation for your answer.
Thanks,
Ric

Ric,
I just tried to do this on APEX 3.0, and it worked just fine with this SQL:
select ename d, ename r from emp order by 1Perhaps you could put an example on apex.oracle.com or specify the error message that you're getting.
So as long as you have uniquely aliased both columns, this should not present a problem.
Thanks,
- Scott -

Creating a Dynamic LOV to pass parameters

I am attempting to create an LOV to pass parameters to my Discoverer report I have on my portal. Any way to make the LOV dynamic? I want a simple sql statement in there to populate it. I used a simple parameter portlet and that wont work...just static list.
Thanks.

I suppse the answer is "No" there is no way to do it....
Anyone found a way to do this?

How can I create a LOV dynamically in UIX?

Jdev10g, ADF BC UIX...
I need to create LOVs for 0 to many columns in my UIX datapage but I don't know the column names nor the tables until I read the LOV_SQL column from the child as they come in. Can you show me the way, please.
Thanks, Stephen.

Stephen,
Check this page out for some elementaries on dynamic pages in UIX. The LOV is essentially just like any other UIX page, with the two differences: it's launched and submitted differently. But these differences don't affect what content is displayed on the page.
Dynamic Structure in ADF UIX Pages:
http://helponline.oracle.com/jdeveloper/help/state/content/navSetId.jdeveloper/navId.4/vtAnchor.ChildData/vtTopicFile.jdeveloper%7Cuixhelp%7Cuixdevguide%7Cdynamic%7Ehtml/

Create lov at run time in oracle form 10g

i want to create a lov and record group dynamically at run time..
i have the code in when-form-instance..
Declare
v_lov lov;
rg_id recordgroup;
gc_id groupcolumn;
tem_num number;
v_rg_id number;
begin
rg_id := find_group('My group');
if id_null(rg_id) then
rg_id := Create_group('My_group');
gc_id := add_group_column(rg_id,'emp_id',number_column);
gc_id := add_group_column(rg_id,'ename',char_column,15);
end if;
v_rg_id := POPULATE_GROUP_WITH_QUERY('My_group','select t.employee_id,t.first_name from employee_mt t where t.employee_id in (103,104,106)');
--tem_num :=populate_group(rg_id);
v_lov := find_lov ('LOV_NAME');
set_lov_property(v_lov,group_name,'My_group');
set_item_property('VEH_SEARCH.TXT_VEH_CODE',lov_name,'lov');
End;
now i have problem...whether i create first a lov and record group at design time or not????
if i create a lov and have the recordgroup column then what is the benefit of dynamically lov...???
thanks

Hi.
It is possible with some restrictions. Let's say you agree there are max 5 columns in your LOV-s. That way you can easily create LOV to RG colums mapping (what Andreas pointed out).
For example :
1. in design time create RG with dummy columns (for example : c1, c2, c3, c4, c5)
2. in design time create 1 LOV with 5 predefind columns (for example : c1, c2, c3, c4, c5)
3. populate that record group with select (selecting 5 columns. If you do not have 5 columns in your table on which LOV is based just select dummy columns for the rest of the columns) aliasing them as c1, c2, c3, c4, c5 (same as in LOV from step 2)
4. asign that RG to the LOV in step 1
5. in LOV show just "non-dummy" rows form step 3
The rest you already figured it out.
The benefit of this approach is questionable as the same can be done creating more RG and LOV-s in design time. So I believe this is the matter of developer preferences. By the way the concept I described we use on daily bases dealing with LOV-s.
Best regards.

Will possible to create lov,recordgroup on runtime?

Hi all,
Is it possible to create lov,recordgroup on runtime. If so, please explain step.
Kanihs

Documentation:
Record Group Type Property
Description
+Specifies the type of record group, either Static or Query: Static Specifies that the record group is constructed of explicitly defined column names and column values.
The values of a static record group are specified at design time and cannot be changed at runtime.
Query Specifies that the record group is associated with a SELECT statement, and thus can be populated dynamically at runtime.
When you select this option, enter the SELECT statement in the multi-line field provided, then choose Apply.+
Francois

How to create a dynamic form with bind variables :schema & :table_name

My application has two LOV's, one to select a schema, and the next to select a table within that schema. I then have a button which passes me to a report which displays the data in that table.schema.
I now want to create a link to a form where I can edit the record based on the rowid of that table.schema, but it doesn't appear that I can create a dynamic form where I pass the schema.table_name and rowid. Is this possible? Can anyone advise how I can do this? The form builder only wants a fixed schema/table name.
Thanks in advance.
Stuart.

Hi Stuart,
In this sort of situation, you will need to be a bit creative.
I would suggest a pipeline function called as if it was a report.
Then you can pipe out the required fields.
Since you will have a variable number of fields, you could use two of the multi row field names for your field names and values.
Then after submit, you can create your own procedure to loop through the fields (stored for you in the Apex package) and update the table as required.
Not very specific I'm afraid, but it should work.
Regards
Michael

Need help with OA Framework. Enable/Disable LOV dynamically

Hello,
I am new to OA Framework. My requirement is as follows;
The page should have a field with parameter org code (LOV). When the user selects an org and click GO button, the page should display all the inactive items (which have no Sales order or work order for last 2 years). In the table region, user selects single record or multiple records by a check box. The selected records should be processed after clicking a submit button in the table region. The process is, calling an API to change the status of the item to Inactive or some other status. The status should be determined by the user by selecting a LOV within the table region. I could create LOV based field for org code and could display the data on the page. I have been trying to display the LOV for item status , I have created a LOV under table region under table components > table actions. I could open the LOV and select a value, but the value is not defaulting to the field on the page. Somebody please help me with a suggestion or if you have the code for a similar kind of requirement please share with me.
Also, need some suggestion on how to enable and disable LOV dynamically. I want to display the 2 LOV's in different regions. I want to enable the LOV for Item Status only after the org code is selected and the page populated after the user clicks GO button.
Thanks in Advance…..

Hi,
I could open the LOV and select a value, but the value is not defaulting to the field on the page.pls check the LOV mapping ,this might be wrong.
to enable/Disable LOV dynamically ,u need to use PPR,please check the lab solution exercise create employee chapter to learn to implement PPR functionality.
Thanks
Pratap

Steps to create tabstrip for subscreen in selection screen

hi,
can let me know the steps taken to create subscreen in selection screen and put in tabstrip?
i need to have 3 screens. 1000 being the tabstrip, 2000 being first subscreen and 3000 being the second subscreen.
i have the abap code but i do not know the steps to create especially 1000 screen.
for 2000 and 3000, once i activated the program, these 2 screens added but i do not know where can i create the 1000 screen.
also, should i use wizard to create tabstrip?
please advise. thanks
SELECTION-SCREEN BEGIN OF SCREEN 2000 AS SUBSCREEN.        SELECTION-SCREEN BEGIN OF BLOCK x WITH FRAME TITLE text-001.
SELECT-OPTIONS: para1 FOR field1 ,
                              para2 FOR field2.
SELECTION-SCREEN END OF BLOCK x.
SELECTION-SCREEN END OF SCREEN 2000.
SELECTION-SCREEN BEGIN OF SCREEN 3000 AS SUBSCREEN.
SELECTION-SCREEN BEGIN OF BLOCK y WITH FRAME TITLE text-002.
SELECT-OPTIONS: para3 FOR field3 ,
                              para4 FOR field4.
SELECTION-SCREEN END OF BLOCK y.
SELECTION-SCREEN:SKIP.
SELECTION-SCREEN END OF SCREEN 3000.

e_l,
See the total doc.. with example.
Assigning a Subscreen Area to a Tab Title
You must assign a subscreen area to each tab title. There are two ways of doing this:
Paging in the SAPgui
You need to assign a separate subscreen area to each tab title, and define the function codes of the tab titles with type P (local GUI function). In the screen flow logic, you call all the subscreens in the PBO event. This means that all of the tab pages reside locally on the SAPgui.
When the user chooses a tab title, paging takes place within the SAPgui. In this respect, the tabstrip control behaves like a single screen. In particular, the PAI event is not triggered when the user chooses a tab title, and no data is transported. While this improves the performance of your tabstrip control, it also has the negative effect that when the user does trigger the PAI event, all of the input checks for all of the subscreens are performed. This means that when the user is working on one tab page, the input checks may jump to an unfilled mandatory field on another page.
Local paging at the SAPgui is therefore most appropriate for screens that display data rather than for input screens.
Paging on the Application Server
One subscreen area is shared by all tab titles and called in the PBO event. You define the function codes of the individual tab titles without a special function type. When the user chooses a tab page, the PAI event is triggered, and you must include a module in your flow logic that activates the appropriate tab page and assigns the correct subscreen to the subscreen area.
Since the PAI event is triggered each time the user chooses a tab title, this method is less economical for the application server, but the input checks that are performed only affect the current tab page.
Procedure in Either Case
You create the subscreen areas within the tabstrip area. You assign the subscreen areas to one or more tab titles in the Screen Painter by selecting one or more titles. You can also assign a subscreen area to a tab title in the tab title attributes by entering the name of the subscreen area in the Reference field attribute.
The procedure for the alphanumeric Screen Painter is described under Creating Tabstrip Controls.
If you are paging at the SAPgui, create a subscreen area for each tab title. If you are paging at the application server, select all tab titles and create a single subscreen area. The subscreen areas may not cover the top line of the tab area. However, within a tab area, more than one subscreen area can overlap.
Programming the Flow Logic
In the flow logic, all you have to do by hand is include the correct subscreens. The screen flow and data transport to the ABAP program is the same as for normal subscreens. There are two ways of programming the screen flow logic, depending on how you have decided to page through the tabstrip control.
Paging in the SAPgui
When you page in the SAPgui, you must include a subscreen for each subscreen area:
PROCESS BEFORE OUTPUT.
CALL SUBSCREEN: <area1> INCLUDING [<prog 1>] <dynp 1>,
                  <area2> INCLUDING [<prog 2>] <dynp 2>,
                  <area3> INCLUDING [<prog 3>] <dynp 3>,
PROCESS AFTER INPUT.
CALL SUBSCREEN: <area1>,
                  <area2>,
                  <area3>,
Paging on the Application Server
When you page on the application server, you only have to include a subscreen for the one subscreen area:
PROCESS BEFORE OUTPUT.
CALL SUBSCREEN <area> INCLUDING [<prog>] <dynp>.
PROCESS AFTER INPUT.
CALL SUBSCREEN <area>.
Handling in the ABAP Program
Before you can use a tabstrip control in your ABAP program, you must create a control for each control in the declaration part of your program using the following statement:
CONTROLS <ctrl> TYPE TABSTRIP.
where <ctrl> is the name of the tabstrip area on a screen in the ABAP program. The control allows the ABAP program to work with the tabstrip control. The statement declares a structure with the name <ctrl> . The only component of this structure that you need in your program is called ACTIVETAB.
Use in the PBO event
Before the screen is displayed, you use the control to set the tab page that is currently active. To do this, assign the function code of the corresponding tab title to the component ACTIVETAB:
<ctrl>-ACTIVETAB = <fcode>.
When you page at the SAPgui, you only need to do this once before the screen is displayed. This initializes the tabstrip control. The default active tab page is the first page. After this, the page activated when the user chooses a tab title is set within SAPgui.
When you page on the application server, you must assign the active page both before the screen is displayed for the first time, and each time the user pages. At the same time, you must set the required subscreen screen.
You can suppress a tab page dynamically by setting the ACTIVE field of table SCREEN to 0 for the corresponding tab title.
Use in the PAI event
In the PAI event, ACTIVETAB contains the function code of the last active tab title on the screen.
When you page in the SAPgui, this allows you to find out the page that the user can currently see. When you page at the application server, the active tab page is controlled by the ABAP program anyway.
The OK_CODE field behaves differently according to the paging method:
Paging in the SAPgui
When you page in the SAPgui, the PAI event is not triggered when the user chooses a tab title, and the OK_CODE field is not filled. The OK_CODE field is only filled by user actions in the GUI status or when the user chooses a pushbutton either outside the tabstrip control or on one of the subscreens.
Paging on the application server
If you are paging at the application server, the PAI event is triggered when the user chooses a tab title, and the OK_CODE field is filled with the corresponding function code.
To page through the tabstrip control, you must assign the function code to the ACTIVETAB component of the control:
<ctrl>-ACTIVETAB = <ok_code>.
This statement overwrites the function code of the last active tab page with that of the new tab title. At the same time, you must ensure that the correct subscreen is inserted in the subscreen area.
Otherwise, tabstrip controls are handled like normal subscrens in ABAP programs, that is, the ABAP program of a subscreen screen must contain the dialog modules called from the flow logic of the subscreen.
Examples
Tabstrip control, paging at SAPgui
REPORT DEMO_DYNPRO_TABSTRIP_LOCAL.
CONTROLS MYTABSTRIP TYPE TABSTRIP.
DATA: OK_CODE TYPE SY-UCOMM,
      SAVE_OK TYPE SY-UCOMM.
MYTABSTRIP-ACTIVETAB = 'PUSH2'.
CALL SCREEN 100.
MODULE STATUS_0100 OUTPUT.
SET PF-STATUS 'SCREEN_100'.
ENDMODULE.
MODULE CANCEL INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE USER_COMMAND INPUT.
SAVE_OK = OK_CODE.
CLEAR OK_CODE.
IF SAVE_OK = 'OK'.
    MESSAGE I888(SABAPDOCU) WITH 'MYTABSTRIP-ACTIVETAB ='
                                  MYTABSTRIP-ACTIVETAB.
ENDIF.
ENDMODULE.
The next screen (statically defined) for screen 100 is itself. It has the following layout:
The screen contains a tabstrip area called MYTABSTRIP with three tab titles PUSH1, PUSH2 and PUSH3. The function codes have the same name, and all have the function type P. One of the subscreen areas SUB1 to SUB3 is assigned to each tab title. The pushbutton has the name BUTTON and the function code OK.
In the same ABAP program, there are three subscreen screens 110 to 130. Each of these fits the subscreen area exactly. The layout is:
The screen flow logic for screen 100 is as follows:
PROCESS BEFORE OUTPUT.
MODULE STATUS_0100.
CALL SUBSCREEN: SUB1 INCLUDING SY-REPID '0110',
                  SUB2 INCLUDING SY-REPID '0120',
                  SUB3 INCLUDING SY-REPID '0130'.
PROCESS AFTER INPUT.
MODULE CANCEL AT EXIT-COMMAND.
CALL SUBSCREEN: SUB1,
                  SUB2,
                  SUB3.
MODULE USER_COMMAND.
The screen flow logic of subscreens 110 to 130 does not contain any module calls.
When you run the program, a screen appears on which the second tab page is active, since the program sets the ACTIVETAB component of the structure MYTABSTRIP to PUSH2 before the screen is displayed. The user can page through the tabstrip control without the PAI event being triggered. One of the three subscreens is included on each tab page.
When the user chooses Continue, the PAI event is triggered, and an information message displays the function code of the tab title of the page that is currently active.
Tabstrip control with paging on the application server.
REPORT DEMO_DYNPRO_TABSTRIP_LOCAL.
CONTROLS MYTABSTRIP TYPE TABSTRIP.
DATA: OK_CODE TYPE SY-UCOMM,
      SAVE_OK TYPE SY-UCOMM.
DATA NUMBER TYPE SY-DYNNR.
MYTABSTRIP-ACTIVETAB = 'PUSH2'.
NUMBER = '0120'.
CALL SCREEN 100.
MODULE STATUS_0100 OUTPUT.
SET PF-STATUS 'SCREEN_100'.
ENDMODULE.
MODULE CANCEL INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE USER_COMMAND INPUT.
SAVE_OK = OK_CODE.
CLEAR OK_CODE.
IF SAVE_OK = 'OK'.
    MESSAGE I888(SABAPDOCU) WITH 'MYTABSTRIP-ACTIVETAB ='
                                  MYTABSTRIP-ACTIVETAB.
ELSE.
    MYTABSTRIP-ACTIVETAB = SAVE_OK.
    CASE SAVE_OK.
      WHEN 'PUSH1'.
        NUMBER = '0110'.
      WHEN 'PUSH2'.
        NUMBER = '0120'.
      WHEN 'PUSH3'.
        NUMBER = '0130'.
    ENDCASE.
ENDIF.
ENDMODULE.
The statically-defined next screen for screen 100 is itself, and its layout is the same as in the above example. However, the function codes of the three tab titles have the function type <blank> and they all share a single subscreen area SUB.
The same subscreen screens 110 to 130 are defined as in the last example.
The screen flow logic for screen 100 is as follows:
PROCESS BEFORE OUTPUT.
MODULE STATUS_0100.
CALL SUBSCREEN SUB INCLUDING SY-REPID NUMBER.
PROCESS AFTER INPUT.
MODULE CANCEL AT EXIT-COMMAND.
CALL SUBSCREEN SUB.
MODULE USER_COMMAND.
In this example, the program includes a subscreen screen in the subscreen area SUB dynamically during the PBO event.
The screen flow logic of subscreens 110 to 130 does not contain any module calls.
This example has the same function as the previous example, but the paging within the tabstrip control is implemented on the application server. Each time the user chooses a tab title, the function code from the OK_CODE field is assigned to the ACTIVETAB component of structure MYTABSTRIP. At the same time, the variable NUMBER is filled with the screen number of the subscreen that has to be displayed in the subscreen area SUB of the tabstrip control
Pls. reward if useful

POPup LOV Dynamic List of values

Hi All,
I need to change the list of values of a popup Lov in my application depending on a checkbox.
Like:
If I the checkbox is checked by the user the list will come from Table A and if the checkbox is unchecked the the list needs to come from Table B.
I need to bind this to the checkbox click event. But I don't know which option should I use to create this Dynamic action.
Please help me out as Its urgent..... I got the deadline today..... :(
Thanks in advance.....

Solved with cascading feature.. Thanks All.

Error creating LOV in Business View Manager - cannot be based on current DF

Hi,
I'm trying to use Business View Manager for the first time. I'm trying to create a dynamic, cascading prompt to be used by Crystal Reports.
I've been able to create:
- data connection
- data foundation - simple one table
- business elements - two columns from the table
- business view
- List of Values
I am now trying to create a parameter in the Business Elements tool. The parameter needs to be a Dynamic, Cascading parameter.
When I try to save the new parameter, I get the follow error:
The List of Values used by this parameter cannot be based on a Business View derived from the current Data Foundation or Business Element.
HELP
Thanks

Hi Chris
If you are trying to create a LOV and use that as a parameter, then you need to create LOV as Dynamic Cascading values. Once created then you can use that LOV in the Crystal Reports.
This is the best way to get dynamic cascading prompts in Crystal reports.
Please refer to Business View Admin guide for more information.
Hope this helps!!
Regards
Sourashree

Creating LOV in Forms Personalization

Hi Friends,
I have the requirement to create LOV for the 'Description' field in Standard Form. That Description field doesn't have LOV. I want to create LOV for that field thru Forms personalisation. Is it possible. Pl. tell me the steps.
I'm using 11.5.10.2.
Thanks
Kavitha

You cannot use Forms Personalization to create a new LOV (you can use Forms Personalization to change what the form run). This is already explained in (Limitations of Forms Personalization [ID 420518.1], Point #1).
To create a new LOV, you will have to customize the form (pay attention to Oracle policy about customizing seeded forms/report) -- See the docs below for details.
Customization in Oracle Applications [ID 743490.1]
Sample CUSTOM Library Code To Customize Applications [ID 744065.1]
Oracle Forms in Applications FAQ [ID 177610.1]
How To Customize Standard Oracle Application Using Custom Library [ID 438920.1]
Oracle Application Developer Guide
http://www.oracle.com/technetwork/documentation/applications-167706.html
Thanks,
Hussein

Steps to create LOV dynamically

Similar Messages

Maybe you are looking for