Date format mask in Enter-Query mode

Hi,
I'm developing a Form which is able to query the masterblock from a detail-item.
The queryable detail-item is a date field and has a datatype: DATETIME. When a new record is entered the values in the date field are stored in the database like "18-10-2002 15:04:02"
When the form is in enter_query mode the user must be able to enter 18-10-2002 (DD-MM-YYYY format mask, so without time mask). When execute the query with this date format the query is not able to find data.
I used a Key-Execute-Query on the detailblock like this:
SELECT 1.COLUMN
, 2.COLUMN
INTO :1.COLUMN
, :2.COLUMN
FROM TABLE.1
, TABLE.2
WHERE 1.COLUMN = 2.COLUMN
AND TO_CHAR(1.COLUMN,'dd-mm-yyyy') = to_date(:avg.datum,'dd-mm-yyyy');
Can anyone please help me?
Regards,
Ronny.

Hi Ronny,
I'm not sure to have got exactly your issue (especially why you have to use that select in master-detail query), but I suggest you to substitute
...AND TO_CHAR(1.COLUMN,'dd-mm-yyyy') = to_date(:avg.datum,'dd-mm-yyyy');
with
...TRUNC(1.COLUMN) = TO_DATE(:avg.datum,'dd-mm-yyyy');
To be fair, I would use it in the where clause, even if you set it dinamically.
Let us know,
Marco

Similar Messages

Suppress the enter-query mode when no-data-found after execute a query.

HI,
Greetings of the day, Can any one suggest me that how to Suppress the enter-query mode when no-data-found after execute a query on the form by a button.
whenever i execute query on form and result is no data found then form :system.mode is still in enter-query mode.
i want that if result is no data found then form comes back it initial state.
i will thank full of him who will help me..
Thanks in Advance..

Put this in your Key-ExeQry trigger:Execute_Query;
If Get_block_property(:System.current_block,query_hits)=0 then
Exit_form; --this cancels the Enter-Query mode; Does not exit the form.
End if;You may want to trap and prevent the "FRM-40353: Query cancelled" message, and change the "FRM-40301: Query caused no records to be retrieved. Re-Enter" message. To do that, you need an On-Message form-level trigger:Declare
Msg_Code Number        := MESSAGE_CODE;
MSG      Varchar2(150) := SUBSTR('   '||MESSAGE_TYPE||'-'
                         ||TO_CHAR(Msg_Code)||': '||MESSAGE_TEXT,1,150);
BEGIN
If Msg_Code=40301 then
     -- 40301: Query caused no records to be retrieved. Re-Enter
    Message(' NO RECORDS FOUND',No_acknowledge);
Elsif Msg_Code=40353 then -- Query cancelled.
    null;
Else
    MESSAGE(MSG,NO_ACKNOWLEDGE);
End if;
End;

[Solved] Problem with LOV and 'enter query' mode

Hi all,
I'm kind of new to Forms and I'm having some problems that I'm not being able to resolve. I already search it on the net, but nothing relevant came up. If anyone could help me I appreciated it.
In my form I have some fields, and in one of them I have a LOV, and almost everything works fine. I inserted data, changed it, deleted it and all it's ok.
But when I change to 'enter query' mode, when I try to search for data on the LOV field it ignores what I write.
That is, for it, it's the same if I make F11 -> write 'aaaa' -> ctrl + F11 or if I make F11 -> '%' -> ctrl + F11.
It behaves the same way, shows me all the records.
Probably I'm missing something basic, but I'm not getting it...
Thanks,
Ana

when you create a lov by wizard the lov and record group have always the same name..
the problem is that the item is NOT based in the tabe.
what kind of query do you execute if you choose something from a love which is not based on the db?
i mean, this item has no influence on the query of the table, so whatever you choose it's like a "select * from table"
i hope i was clear

Problem With Date Format Mask

Hi everyone,
when i set the date format mask in any field..
if i enter any wrong date format messages are coming in to loop
is this is bug of format mask?
how can i avoid this..
thanks in advance
anand mohan

It should not take you into a loop. If the "validation" against the format mask fails, a message is displayed, and the focus is returned to the field which caused the problem. Do you maybe have some method or event associated with the field which could be causing the circular behavior?
-- Brian

Blocking some fields from entering in summary block in enter query mode

Hi ,
I have a data block where in some fileds have to be dynamically allowed to enter and some are not based on
a particular condition. The problem is whenever the forms enters enter query mode, all the fileds in the block are updateble. Even maually I tried to set/unset the property in forms using set_item_property, but the enter query mode was trying to overiride it and making updateble.
Please suggest a solution for this.
Thanks in advance.
Thanks,
Lohith

Try the below code
IF :SYSTEM.MODE='ENTER-QUERY' THEN
SET_BLOCK_PROPERTY('BLOCKNAME',INSERT_ALLOWED,PROPERTY_TRUE);
SET_BLOCK_PROPERTY('BLOCKNAME',UPDATE_ALLOWED,PROPERTY_TRUE);
SET_BLOCK_PROPERTY('BLOCKNAME',DELETE_ALLOWED,PROPERTY_TRUE);
you can set the item here too by using the below code
SET_ITEM_PROPERTY('BLOCK.ITEM_NAME',INSERT_ALLOWED,PROPERTY_TRUE);
SET_ITEM_PROPERTY('BLOCK.ITEM_NAME',UPDATE_ALLOWED,PROPERTY_TRUE);Regards
Moazam
Edited by: Moazam Shareef on Oct 6, 2010 6:10 AM

FRM-40200 and FRM-40501 in Enter-Query-Mode

Some strange behaviour in Enter-Query-Mode:
Although the help states
About Designing Forms for Querying+
+.. To make a "query-only" block, set Query Allowed to Yes and Delete Allowed, Insert Allowed, and Update Allowed to No. ..+
I get FRM-40200: Field is protected against update.
System.Mode says, we are currently in ENTER-QUERY.
Setting insert- and update-allowed to TRUE, I get
FRM-40501: ORACLE error: unable to reserve record for update or delete.
The entered character flashes and is erased immediately.
Any ideas?
Forms 10gR2
Items are base table, all transactional properties aund query_allowed are true, query_length is ok.
2 Things that happen before the initiation of the enter-query-mode:
. data-source is changed to another view; column names are ok.
. all block-items are disabled and not navigable at start-up of form and re-enabled and made navigable before entering the block.
The values of block and item-properties mentioned above are take at WHEN-NEW-ITEM-INSTANCE and no further trigger fire.

I think you are not meaning just the KEY-ENTQRY-Trigger, that to easy
IF INSTR(:SYSTEM.TRIGGER_BLOCK, '_DETAIL') = 0
+ AND :SYSTEM.TRIGGER_BLOCK NOT IN ('VZG_KOPF','KONTROLL','BUTTONS','TEMP')+
THEN
+ ENTER_QUERY;+
END IF;
.. but the rest is a lil bit, let's call it bulky; including pll and db-packageges.
I hoped to get a clue, if somebody has a similar expeience, in what direction to search. It's strange.
And, as I noticed today, it's not a problem of all forms of the app. Not even of all the forms called from the same "environment" (same globals, same menu-form from which they are opened). To me it looks like Enter-Query does not work in the forms where I switch the block-data-source from a view to a globally temporary table. That (this switching) is not a new feature and Enter-Query worked in the past. Althoug we had some changes in the temp tables in the last weeks there are no problems in querying the data in the forms. Recompilation of pll and fmb, no improvement. And either Enter-Query woks in a form or it does not.

LOV button in enter query mode

Hi
How do I show LOV button(Forms 9.0.2) in enter query mode?As of now LOV button is displayed only in the create mode.
Binod.

Hi Andrew,
Thanx for the reply. Actually I have not associated any trigger for this. Here Im refering the LOV button which comes inside the respective field(I mean we change the property lov_button to 'true in the regitry.dat). This button is not getting displayed in the enter query mode.
I hope now you are clear with the query.
Binod.

Calendar in Enter-Query Mode

Dear All ,
i hv posted my problems before.
My. Calendar does not work in Enter-Query Mode.
It says 'Function Key Not Allowed' It's Because of the Code(Go_Block) in Get Date procedure in the date package.
Any Suggestion on this will be highly appreciated.

You will have to change the calendar code to reside in a separate Form and use CALL_FORM to pop it up. This will be valid in Enter-Query mode - You'll then pass the selection back in a Global variable.

Non-Database items in enter-query mode

I have a form with 2 base table blocks, typical master details situation. I wish to allow a field from the detail block to be queryable from the master block. I was considering adding a non-database item to the master block (visible only when in Enter-Query mode). In a pre-query trigger I would amend the DEFAULT-WHERE property of the master block when the appropriate where clause using the non-database item value. My prototype/test version works fine except the non-database item is not enabled while the master block is in enter-query mode.
I think basically forms will enable only field s if they are database items and queryable set to yes. There are no more database items I can use to set the non-database item column name property.
Any suggestions would be appreciated.
Ralph
Oracle Developer - Unisys Australia

Hi Ralph,
we have several Forms using non-database items as query-items which works fine.
What we did is following:
1) create non-database item xy in master-data-block
2) set property database item to no
3) set property query allowed to yes
4) create a pre-query trigger on master-data-block where we change the where-clause (this is forms6i, in 9i we would use the one-time-where-clause)
Peter

Using Enter-Query Mode Programmatically

A question was raised in an earlier thread
QUERY CRITERIA MANAGER
about how to use Enter-Query mode programmatically in a way that doesn't stop
and prompt the user to enter a query after switching from Normal mode to Enter-Query mode.
Since the solution may not be widely known, I thought I'd demonstrate the technique here in a new thread.
Create a simple form with just two blocks. Using the data block wizard, create an EMP block with one
text item for ENAME. Place it on the canvas. Create the other block as a control block and name it CONTROL.
Inside the control block create the following items:
- create a text item named TXT_BOX
(The user will enter their search pattern criteria in this text box while in Normal mode.)
- create a push button item named EXECUTE_QUERY
(This button will switch to Enter-Query mode, execute the query, then return to Normal mode.)
Place both control items on the canvas.
Inside the WHEN-BUTTON-PRESSED trigger for the EXECUTE_QUERY button, enter the following code:
DECLARE
     timer_id TIMER;
BEGIN
     :GLOBAL.search_criteria := :CONTROL.TXT_BOX;
     GO_BLOCK('EMP');
     timer_id := CREATE_TIMER('ENT_QRY', 1500, NO_REPEAT);
     -- 1500 may be a little long, but provides a margin of error
     ENTER_QUERY;
END;
Next, create a WHEN-TIMER-EXPIRED trigger at the form level. Inside this trigger enter the following code:
If GET_APPLICATION_PROPERTY(TIMER_NAME) = 'ENT_QRY' THEN
     :EMP.ENAME := :GLOBAL.search_criteria;
     EXECUTE_QUERY;
     IF :SYSTEM.MODE = 'ENTER-QUERY' THEN
          EXIT_FORM; -- return to Normal mode
     END IF;
END IF;
GO_ITEM('CONTROL.TXT_BOX');
Now, when the user runs the form and logs into the SCOTT schema, he enters a search criteria
such as A% in the TXT_BOX while in Normal mode. Then clicks the EXECUTE_QUERY button.
The form will switch to Enter-Query mode, retrieve all names in ENAME that begin with the letter A,
and then return to Normal mode without pausing for the user to enter a search criteria.
If the query should happen to fail, the form displays the error:
"FRM-40301: Query caused no records to be retrieved. Re-enter."
then switches automatically back to Normal mode so the user can try entering a new criteria.

I'm showing how to do it when switching modes. I'm
not suggesting this is the best way to do a query.We need to look at this in the context of the original probelm in the thread linked to above. For most cases the when-timer-expired etc is just a huge detour around using the pre-query trigger but it's an interesting approach to the specific problem in the earlier thread. The OP there wanted to be able to type '>5000' into a number field in a non-database block, which we can do in a database block in enter-query mode, and use it as a query parameter in the database block. Perhaps if we enter this into a character field in the non-database block and populate the numeric field in the database block whilst in enter-query mode then we can do searches on ranges of data? Unfortunately it doesn't work - you get an ora-06502 error just like you do when using the pre-query trigger. For the situation in the original thread you would have to use a 'default where'.

Enter Query Mode with Block Based on Stored Procedure

How can I get the ENTER QUERY mode to work when the data block is based on a stored procedure?

Thank you for your review.
Because the package is long, I stripped most of it out, but left the basics. After I stripped out the code, I ran the new code under a new user. Under the new user I built I new form, tested it, and I still cannot use the ENTER QUERY mode to retrieve the correct record. Query always returns the first record. I have included table structure and 3 test records.
CREATE TABLE FR_Charge
(      FR_Charge_ID               NUMBER(8),
     FR_Charge_Code               VARCHAR2(8) CONSTRAINT FR_Charge_Code_nn NOT NULL,
     FR_Charge_Code_DESC          VARCHAR2(35),
     FR_Charge_Code_CMT          VARCHAR2(50),
          CONSTRAINT FR_Charge_pk PRIMARY KEY (FR_Charge_ID)
CREATE SEQUENCE FR_Charge_SEQ;
INSERT INTO FR_Charge
VALUES(FR_Charge_SEQ.NEXTVAL,'0.0WS','E-Mail Notification', NULL);
INSERT INTO FR_Charge
VALUES(FR_Charge_SEQ.NEXTVAL,'0.1', 'Shipping', NULL);
INSERT INTO FR_Charge
VALUES(FR_Charge_SEQ.NEXTVAL,'0.12', 'Shipping Charges', NULL);
--Package follows
CREATE OR REPLACE PACKAGE DataCard_Pkg
AUTHID CURRENT_USER
AS
     -- The following records defines the data structure needed by the FR_Card.
     TYPE FR_Charge_Record IS RECORD
     (     FR_Charge_ID                    FR_Charge.FR_Charge_ID%TYPE,
          FR_Charge_Code                    FR_Charge.FR_Charge_Code%TYPE,
          FR_Charge_Code_DESC               FR_Charge.FR_Charge_Code_DESC%TYPE,
          FR_Charge_Code_CMT               FR_Charge.FR_Charge_Code_CMT%TYPE
     -- REF CURSOR definition used by the query procedure.
     TYPE FR_Charge_REFCUR IS REF CURSOR RETURN FR_Charge_Record;
     -- INDEX OF TABLES used for the DML Operation procedures.
     TYPE FR_Charge_Table IS TABLE OF FR_Charge_Record
          INDEX BY BINARY_INTEGER;
     --Define Procedure Specifications
     PROCEDURE FR_Charge_Query (DMLResultSet IN OUT FR_Charge_REFCUR);
     PROCEDURE FR_Charge_Lock (DMLResultSet IN OUT FR_Charge_Table);
     PROCEDURE FR_Charge_Insert (DMLResultSet IN OUT FR_Charge_Table);
     PROCEDURE FR_Charge_Update (DMLResultSet IN OUT FR_Charge_Table);
     PROCEDURE FR_Charge_Delete (DMLResultSet IN OUT FR_Charge_Table);
END DataCard_Pkg;
CREATE OR REPLACE PACKAGE BODY DataCard_Pkg
AS
     PROCEDURE FR_Charge_Query (DMLResultSet IN OUT FR_Charge_REFCUR)
     IS
     BEGIN
          OPEN DMLResultSet FOR
          SELECT FR_CHARGE.FR_Charge_ID,
               FR_CHARGE.FR_Charge_Code,
               FR_CHARGE.FR_Charge_Code_DESC,
               FR_CHARGE.FR_Charge_Code_CMT
     FROM FR_Charge;
     END FR_Charge_Query;
     PROCEDURE FR_Charge_Lock (DMLResultSet IN OUT FR_Charge_Table)
     AS
          x_index NUMBER := 1;
          x_count NUMBER := DMLResultSet.COUNT;
          x_dummy_var VARCHAR2(1);
     BEGIN
          FOR x_index IN 1..x_count LOOP
               SELECT 'X'
               INTO x_dummy_var
               FROM FR_Charge
               WHERE FR_Charge_ID = DMLResultSet(x_index).FR_Charge_ID
               FOR UPDATE NOWAIT;
          END LOOP;
     END FR_Charge_Lock;
     PROCEDURE FR_Charge_Insert (DMLResultSet IN OUT FR_Charge_Table)
     AS
          x_index NUMBER := 1;
          x_count NUMBER := DMLResultSet.COUNT;
     BEGIN
     FOR x_index IN 1..x_count LOOP
          INSERT INTO FR_Charge
          (      FR_Charge_ID,
               FR_Charge_Code,
               FR_Charge_Code_DESC,
               FR_Charge_Code_CMT
          VALUES
          (     FR_Charge_SEQ.NEXTVAL,
               UPPER(DMLResultSet(x_index).FR_Charge_Code),
               DMLResultSet(x_index).FR_Charge_Code_DESC,
               DMLResultSet(x_index).FR_Charge_Code_CMT
          END LOOP;
     END FR_Charge_Insert;
     PROCEDURE FR_Charge_Update (DMLResultSet IN OUT FR_Charge_Table)
     AS
          x_index NUMBER := 1;
          x_count NUMBER := DMLResultSet.Count;
     BEGIN
          FOR x_index IN 1..x_count LOOP
          UPDATE FR_Charge
               SET FR_Charge_Code = UPPER(DMLResultSet(x_index).FR_Charge_Code),
               FR_Charge_Code_DESC = DMLResultSet(x_index).FR_Charge_Code_DESC,
               FR_Charge_Code_CMT = DMLResultSet(x_index).FR_Charge_Code_CMT
          WHERE FR_Charge_ID = DMLResultSet(x_index).FR_Charge_ID;
          END LOOP;
     END FR_Charge_Update;
     PROCEDURE FR_Charge_Delete (DMLResultSet IN OUT FR_Charge_Table)
     AS
          x_index NUMBER := 1;
          x_count NUMBER := DMLResultSet.Count;
     BEGIN
          FOR x_index IN 1..x_count LOOP
               DELETE FROM FR_Charge
               WHERE FR_Charge_ID = DMLResultSet(x_index).FR_Charge_ID;
          END LOOP;
     END FR_Charge_Delete;
END DataCard_Pkg;

Help: Date Format Mask Issue year 0004 instead of 2004

Hi,
I set Date Format Mask as MM/DD/YYYY for a date field. However, when user enter
12/31/04 the result turned out as 12/31/0004
Of course, I'd like user put 12/31/2004, but 12/31/04 leads to 12/31/0004 has to be stopped.
Any suggestions?
Thank you in advance.
Jimmy

Thank you very much Francois and it works for me.
Jimmy

Problem with date format mask 'D'

I am experiencing an extremely thorny problem with the date format mask ‘D’. I am trying to use it to check whether today is a Monday. The variable v_temp_day is set to sysdate. For the last 4 weeks the code has behaved erratically – giving a different result at 02:00 than at 10:30 even though it is only taking account of the date. In desperation I inserted a debug statement formatting the date in a variety of ways – with interesting results. Oracle is somehow managing to tell us that today is simultaneously Monday and Tuesday depending on which format mask you choose. Anyone got any thoughts or suggestions?
PROC_ID TO_CHAR(STAMP_TIM
EVENT_SQLERRM
RRHKP010 17092007 02:00:00
TO_NUMBER( TO_CHAR( v_temp_day, D ) ) = 2. TO_CHAR( v_temp_day, D ) = 2. TO_CHAR( v_temp_day, DY ) = MON. TO_CHAR( v_temp_day, DAY )
= MONDAY . TO_CHAR( v_temp_day, Day DD-MON-YYYY HH24MISS ) = Monday 17-SEP-2007 020000. TO_CHAR( v_temp_day, D ) = 2.
SQL> select to_char( sysdate, 'D' ) from dual ;
T
1

My book says the trunc(d,'iw') will return "same day of the week as Jan 1st of that year"It's bad book.
Please read about [url http://oraclesvca2.oracle.com/docs/cd/B10501_01/server.920/a96540/functions176a.htm#80159]TRUNC & 'IW' Format Model and [url http://oraclesvca2.oracle.com/docs/cd/B10501_01/server.920/a96529/ch3.htm#50331]Database Globalization Support Guide: First Calendar Week of the Year in the manual.

FRM-41361 Cannot navigate out of current form in Enter-Query Mode

Hi All,
I am getting the FRM-41361 error in the bottom message area when opening a form from the function navigator. The issue does not exist when opening the form from the application homepage. The form is loaded in enter-query mode, and the enter_query command is in the WHEN-NEW-FORM-INSTANCE trigger. I have checked all triggers that fire after this point for any type of navigation but do not see any. The interesting thing is, if I put a fnd_message.set_string and fnd_message.show just before the enter_query call to debug, the issue goes away entirely.
Is it possible there are security triggers firing after the form is loaded into enter-query mode that could be causing this and that the fnd_message calls are indeed buying time for those triggers to complete before the enter_query call?
Any help/advice is appreciated. Thanks!
Dan

Yes, when I looked through the triggers I made sure to look for go_block and go_item calls as well as any calls to leave the form.

Error in SQL Date Format Mask

Hi,
I am facing problem in validation data in FDQM.
When I am trying to validate data,I am getting an error as ' An Error occured.Please verify that SQL Date Format Mask is correct'
The current Date Format in our application is YYYYMMDD.
I did not have this problem earlier in validating data.This problem is occuring now only and also this error is coming for few entities only.
Could any one suggest me on how this can be resolved.
Thanks

Hi Kelly,
I checked periods in control tables and there are no duplicates.
The Period Date Format Mask is MMM-YYYY where as the SQL Date Format Mask is YYYYMMDD.
These settings are there since the time I created application.Has it got anything to do with database.
Appreciate your quick response
Regards,
Mrudula

Date format mask in Enter-Query mode

Similar Messages

Maybe you are looking for