OraFAQ Forum: Oracle Fusion Apps & E-Business Suite » How to restrict users from pressing F11 and CTRL-F11 on a form

Home » Applications » Oracle Fusion Apps & E-Business Suite » How to restrict users from pressing F11 and CTRL-F11 on a form (DB version 11.2.0.2 EBS version 12.1.3 Forms 10g )

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

How to restrict users from pressing F11 and CTRL-F11 on a form [message #554099]

Thu, 10 May 2012 07:16

knsreedevi
Messages: 25
Registered: May 2012
Location: Bangalore

Junior Member

Hi,

I am creating a new form which is dependent on the standard form and opened when the zoom is clicked.
In this new form the user is allowed only to update the record or create record. how do i restrict them from pressing F11(enter-query) or CTRL-F11(Query mode).

Report message to a moderator

Re: How to restrict users from pressing F11 and CTRL-F11 on a form [message #554102 is a reply to message #554099]

Thu, 10 May 2012 07:29

Littlefoot
Messages: 21823
Registered: June 2005
Location: Croatia, Europe

Senior Member
Account Moderator

Create KEY-ENTQRY and KEY-EXEQRY triggers which would look exactly the same:

null;

Report message to a moderator

Re: How to restrict users from pressing F11 and CTRL-F11 on a form [message #554110 is a reply to message #554102]

Thu, 10 May 2012 07:42

knsreedevi
Messages: 25
Registered: May 2012
Location: Bangalore

Junior Member

Sorry I didnt follow this.
Can you please explain in detail

Report message to a moderator

Re: How to restrict users from pressing F11 and CTRL-F11 on a form [message #554115 is a reply to message #554110]

Thu, 10 May 2012 07:53

Littlefoot
Messages: 21823
Registered: June 2005
Location: Croatia, Europe

Senior Member
Account Moderator

I'll try.

Sorry if it won't work - I'm not good in answering Forms questions that are related to Oracle Apps.

So, strictly Forms speaking: when you create a form and want to restrict enter query and execute query, you create triggers which do something else - actually, do nothing ("null;"). These can be block-level or even form-level triggers.

In Object Navigator, you'd create these two triggers: KEY-ENTQRY (enter query) and KEY-EXEQRY (execute query). As you don't want to enter query mode and you don't want to execute query, put "null;" as their only code. Alternatively, you might add a MESSAGE to warn users that these functions aren't available.

If Oracle Apps. handle this stuff differently, you'll have to wait until someone who knows that software sees your question and answers it.

Report message to a moderator