ORACLE APPLICATIONS ARCHIVES

Topicwise collection of
Postings on Mail Lists
ON
ORACLE APPLICATION FORMS

Zoom - Passing Parameters to - Query 2

From: Kossmann, Bill [mailto:BKossmann@mail.dthr.ab.ca]
Sent: Monday, October 18, 1999 10:01 AM
To: Multiple recipients of list
Subject: Passing parameters with Zooms

Hello, Zoom gurus:

I'm trying to set up a Zoom in 10.7NCA such that when the user presses the Zoom icon while in the GL journal entry form, a hard copy of the journal entry is printed. My intention is to transport the user to the Standard Report Submission form where the report name and parameters would automatically be filled in; the user simply presses the Submit button and the report would process and print.

I'm having a bit of difficulty in passing the parameters. The Zoom correctly brings up the form, but the report name field is blank. I presume that solving the problem with the report name field will then lead me to successfully passing the report parameters. My questions, then, are:

1) Is calling the 'Journals - General(132 Char)' report the best way to go?
2) What am I missing? Why doesn't the report name get passed to FNDRSRUN?

The relevant code block is at the bottom of this message. Thanks for any assistance you can offer!

Regards, Bill
Bill Kossmann, CGA
Business Analyst
David Thompson Health Region
ph 403 343 4463
fx 403 343 4697

snip

begin
if (event_name = 'ZOOM') then
if (form_name = 'GLXJEENT') and
((block_name = 'HEADER') or (block_name = 'LINES')) then
fnd_function.execute(FUNCTION_NAME='FND_FNDRSRUN',
OPEN_FLAG='Y',
SESSION_FLAG='Y',
OTHER_PARAMS='Journals - General(132 Char)');

/* OTHER_PARAMS='Request'||'Journals - General(132 Char)'); didn't work either */
/* OTHER_PARAMS='P'||'Journals - General(132 Char)'); didn't work either */
end if;

snip

Date: Mon, 18 Oct 1999 12:57:41 -0500
From: "Carver, Elizabeth" ecarver@MarkAndy.com
To: "'oraapps-l@cpa.qc.ca'" oraapps-l@cpa.qc.ca
Subject: RE: Passing parameters with Zooms

If you view the submit requests form (FNDRSRUN) through Forms Designer you will be able to see the parameters you can pass into the form. That is probably why yours does not work. You can only pass valid parameters into the form You must populate one of these parameters with the report name. Then in create a when-new-form-instance event (just like the zoom event) and then populate the report name field with the parameter value. See changes to code

IF (event = 'ZOOM') and
form_name = 'GL form' and block_name = 'block_name') then
-- parm_to_pass, 2, 3 are declared variables parm_to_pass := put report name here etc

OTHER_PARAMS='Journals - General(132 Char)="'||parm_to_pass||'"
type="'||parm_to_pass2||'"
P="'||parm_to_pass3||'"');

if (event = 'WHEN-NEW-FORM-INSTANCE')
and (form_name = FNDRSRUN)
and name_in('parameter.REPORT_NAME') is not null then
copy('request', 'report.report_type');
copy('PARAMETER.REPORT_NAME', 'REPORT.REPORT_NAME);
copy('1', 'report.number_of_copies');

I am not sure what you want to do about printers I would probably just copy values into report type field and number of copies field assuming they would always be request and 1 copy since it would never change I am guessing at block and field names you must put the valid field and block names in the reference to report.report_name is the block and field name. You must check to see if the parameter is null (or not null) so it only copies the value of the parameter into the form field when it is zoomed to and not when opened from the navigator.

x-------------x

Date: Mon, 18 Oct 1999 16:35:10 -0600
From: "Kossmann, Bill" BKossmann@mail.dthr.ab.ca
To: "'oraapps-l@cpa.qc.ca'" oraapps-l@cpa.qc.ca
Subject: RE: Passing parameters with Zooms

Elizabeth,

Thanks for the information. Can I impose upon your good nature one more time? I think that I have a problem with variable scoping; the parameters params_to_pass[1|2|3] appear to be null when they get passed to the report. Note that the report is a home-grown report (SQL*Plus). At one time, I gave the variables meaningful names (e.g. p_report, p_je_name, p_period) but in my desperation I resorted to the format used in the CUSTOM.pll shell.

I think I'm on the right track, as the literals are passed correctly to FNDRSRUN. Can you (or anyone) spot what I'm doing wrong here?

Thanks again for your help!
Regards,
Bill

For the Code please click here

Date: Tue, 19 Oct 1999 08:52:00 -0500
From: "Carver, Elizabeth" ecarver@MarkAndy.com
Subject: RE: Passing parameters with Zooms

See changes below to when-new-form-instance. To check to see if the parameters have been populated into FNDRSRUN. Do Help Tools examine block parameters and then type in the parameter name.

Code snippet follows:
----------------------------------------------------------------------

form_name varchar2(30) := name_in('system.current_form');
block_name varchar2(30) := name_in('system.cursor_block');
param_to_pass1 varchar2(50);
param_to_pass2 varchar2(100);
param_to_pass3 varchar2(25);
--
begin
if (event_name = 'ZOOM') then
if (form_name = 'GLXJEENT') and
((block_name = 'HEADER') or (block_name = 'LINES')) then
param_to_pass1 := 'DTHR Journal Entry Report';
param_to_pass2 := name_in('HEADER.NAME');
param_to_pass3 := name_in('HEADER.PERIOD_NAME');
fnd_function.execute(FUNCTION_NAME='FND_FNDRSRUN',
OPEN_FLAG='Y',
SESSION_FLAG='Y',

OTHER_PARAMS='CONCURRENT_PROGRAM_NAME="'||param_to_pass1||'"
xyz="'||param_to_pass2||'"
abc="'||param_to_pass3||'"');
end if;
else
null;
end if;

=====
You would have to pass the param_to_pass2 and 3 into the zoom to form. Again xyz and abc must be valid parameters. I have passed values into the form parameters that don't match the usage of the parameter. Ex. It looks like you are trying to pass the set of books name. Is there another parameter that you can use? I would not think that there is parameter in FNDRSRUN for the set of books but again is there another parameter that you can pass the value into? When you do this or pass values into any parameter make sure that you are being careful as to what you are populating and what you are populating it with. Ex. The FNDRSRUN has a parameter called REQUEST_GROUP (or something like that) It determines which group of reports appear in the report name field. I would not pass values into this parameter.

Custom Objects - avoid overwriting on upgradation

From: Bartoletti, Mike [mailto:BartolMi@rf.suny.edu]
Sent: Tuesday, October 19, 1999 10:21 AM
To: Multiple recipients of list
Subject: DEV: Custom Objects

I think I am an idiot, but here goes anyways. In the release 11 Extend Oracle Apps class, it states that custom tables, indexes, and sequences are created under the custom oracle user name we create. Packages, views, procdures, functions, and triggers are created under the APPS schema. How do we protect ourselve from patches and upgrades from overwriting the stuff that is there? We will have our code version contolled, but we all know something could be in development and the latest version in production is not really identifiable in the version cntrol software. Any help is great as usual.

Michael Bartoletti
Applications Development Project Leader
Research Foundation of SUNY
(518)434-7204

Date: Tue, 19 Oct 1999 15:08:26 -0700
From: Karen Blackwell KBlackwell@rockshox.com
To: "'oraapps-l@cpa.qc.ca'" oraapps-l@cpa.qc.ca
Subject: RE: Custom Objects

We are in process of upgrading from 10.7NCA to 11.0.3 (in fact, dev is up and users are testing).

On page 2-17 of the "Oracle Applications Installation Release 11 for UNIX" manual, step 25 states:
" If you are upgrading from a previous release, AutoInstall automatically runs a script ... which drops database objects in Applications schemas that match standard Oracle prefixes. For example, if you have a stored procedure named GL_CUSTOM in the schema for General Ledger, it will be dropped during the upgrade. An object named XXGL_CUSTOM would not be affected."

If I understand your question appropriately, this should clear it up. It goes on to say ...
" If you wish to preserve these database objects, you should relocate them to another schema or rename them to a name that does not use the Oracle standard prefixes. "

They also recommend that at least four characters be used for your product short name, followed by an underscore.

HTH

Date: Wed, 20 Oct 1999 18:35:18 +0200
From: "Gilad A." gilade@rafael.co.il
To: oraapps-l@cpa.qc.ca
Subject: Re: Custom Objects

Pay attenetion to the concept of how Oracle is managed in APPS 11: Data is stored in the application scheme ( HR, GL , INV ... ) Programs are stored in APPS scheme.

Tables ( and indexes and constraints attached to ), Sequences are Data. If you define your new scheme XXGL , Oracle shouldnt recognize this scheme, therefore - will not touch your data during any patch or upgrade. But, all your Program Customizations ( as well as Oracle's ) Packages, Procedures, Triggers, Views need to be recognized by the whole Oracle Vanilla, therefore, defined in APPS, and might be spoiled after an upgrade.

If you save your all your Programs ( Packages, Triggers, Views ) in scripts, and manage them properly ( Separately in DEV, TEST, PROD ), it is really not a big deal to run them all after an upgrade in the right DEV/TEST/PROD installation, they are just DDL's.

Hope this helps,
Gilad.

Motif version of Forms45 on unix

From: Manjula Muthukumar [mailto:m_manjula@oracleassist.com]
Sent: Wednesday, October 20, 1999 7:52 AM
To: Multiple recipients of list
Subject: Forms45 motif version

Hi All,

Can anyone please let me know how to invoke forms45 motif version on unix.

Thanks,
Manju.

Date: Wed, 20 Oct 1999 10:21:14 -0500
From: Bharat Patel bpatel@DOMINOAMJET.com
To: "'oraapps-l@cpa.qc.ca'" oraapps-l@cpa.qc.ca
Subject: RE: Forms45 motif version

f45desm
before that you have to user . ./.profile

hope this helps.

Bharat Patel
D.B.A.

Special Menu - invoking

From: oraapps-l@cpa.qc.ca [mailto:oraapps-l@cpa.qc.ca]On Behalf Of Kossmann, Bill
Sent: Tuesday, October 26, 1999 11:35 AM
To: Multiple recipients of list
Subject: AOL: Special menu

Hi everyone:

I'm trying to set up a "special menu" item using CUSTOM.pll without success. In the following code snippet, I'm trying to enable the special menu:

if (event_name = 'WHEN-NEW-BLOCK-INSTANCE') then
/* Where is the user now? */
if ((form_name = 'GLXJEENT') and (block_name = 'HEADER')) then

/* Is this *&@%$#&! thing working? */
FND_MESSAGE.SET_NAME('FND', 'Hello, world!');
FND_MESSAGE.SHOW;

/* Enable the special menu */
set_menu_item_property('SPECIAL.SPECIAL15', LABEL, '&Oh so special');
set_menu_item_property('SPECIAL.SPECIAL15', DISPLAYED, PROPERTY_TRUE);
set_menu_item_property('SPECIAL.SPECIAL15', ENABLED, PROPERTY_TRUE);
else
null;
end if;
else
null;
end if;

The code results in a "hello world" message when I arrive at the proper block, but does not enable the special menu. Can anyone tell me what I'm missing?

Thanks in advance for any advice you can offer!
Regards,
Bill
Bill Kossmann, CGA
Business Analyst
David Thompson Health Region
ph 403 343 4463
fx 403 343 4697

Date: Tue, 26 Oct 1999 13:45:54 -0700
From: "Prasad Sanikommu" prasad.sanikommu@sentrol.com
To: oraapps-l@cpa.qc.ca
Subject: RE: Special menu

Hi,

You have to use the apps built in app_special.instantiate and app_special.enable. The first call should be in the pre-form trigger. The arguments are option_name(special1 to special15,hint(menu item label),icon(only for the first three),initially_enabled(default true).

The second call is used to enable and disable menu items for particular blocks.it shpuld be called in the pre-block trigger.

HTH
Prasad