Best way to to prevent cancelling report?

[jdesmm]

I've designed an application for data entry. When the user clicks the OK button, the application is programmed to call a report which performs additional processing and uploads the data to a "final" table. When it calls the report, the standard JDE printer selection screen is displayed. My concern is that a user could accidentally click "cancel" and prevent the report from running.

The CNC Admin tells me there is nothing that can be done about this from a settings or security perspective (i.e. preventing the printer selection form from appearing or disabling the cancel button). I'm wondering what, if any, options I have. It appears that setting the report to a subsystem job might be one (can that be done at the version level only instead of at the report level?). Any others?

 

[Diana_Maas]

If you put the UBE interconnect into a business function then the defaults
will be used and no 'printer screen' presented.

-
Diana L. Maas
URS Corporation
Information Technology
P.O. Box 201088
Austin, TX 78720-1080
512.419.6407

E-mail: [email protected]


This e-mail and any attachments are confidential. If you receive this
message in error or are not the intended recipient, you should not retain,
distribute, disclose or use any of this information and you should destroy
the e-mail and any attachments or copies.









jdesmm
<[email protected]
m> To
Sent by: [email protected]
jdeowdev-bounces@ cc
jdelist.com
Subject
Best way to to prevent cancelling
10/20/2005 02:28 report?
PM


Please respond to
JD Edwards®
EnterpriseOne
Developers
<jdeowdev@jdelist
.com>






I've designed an application for data entry. When the user clicks the OK
button, the application is programmed to call a report which performs
additional processing and uploads the data to a "final" table. When it
calls the report, the standard JDE printer selection screen is displayed.
My concern is that a user could accidentally click "cancel" and prevent the
report from running.

The CNC Admin tells me there is nothing that can be done about this from a
settings or security perspective (i.e. preventing the printer selection
form from appearing or disabling the cancel button). I'm wondering what, if
any, options I have. It appears that setting the report to a subsystem job
might be one (can that be done at the version level only instead of at the
report level?). Any others?


Shelley M. Maas Development Manager Apio, Inc.

 

[MPDev]

Hi, Shelley

One way to prevent any interruption is to call the Report from inside a Business Function (NER) instead of the regular Report Interconnect from APPL.

Regards,

 

[jdesmm]

I spoke too soon... I found the Launch Batch Application business function, but the problem is that the function does not give me the ability to pass parameters the way the Call UBE system function does. I looked for other business functions that might do this but didn't find any. I need the report to run only for the specific record that the users has just entered...

 

[Zoltan_Gyimesi]

Hi Shelley,

I have already made applications, where I use Launch Batch Application and I pass parameters to the UBE thru a custom table.

If the UBE runs locally and one user can run only one instance of the UBE in the same time on the same machine, then enough to place the Machine Key (MKEY) and User ID (USER) in the primary key. In other cases, we can figure out other primary key to fit to the requirements.

Regards,

Zoltán