Trigger Firing in Form6i

Hi all
ill explain detail my situation
In my forms
my menu contain icons like new(+),save,e.t.c.
when I click on new(+) icon one additional record comes for inserting
But i don't want it. I tried to know the trigger fired for adding record to disabling the trigger action.
ex;
icons: new ,save,cut and so.on
My form records are like this e.g.
A
B
C
If I click on NEW icon, one record was added like this for inserting
A
B
C
My requirement is even if I click on NEW icon, no action will be performed. Can you Plz give me the idea?
Thanks
RangaReddy

Instead of breaking the WHEN-BUTTON-PRESSED trigger that fires for that button, you should disable the button. Otherwise, a user may think the form is "broken."
set_item_property ('ADD', ENABLED, PROPERTY_FALSE);Replace "ADD" with whatever your button is named.

Similar Messages

Sequence of trigger firing in forms 6i

hai,
please reply soon ..
i need full details about sequence of trigger firing when form initiate,
query mode,modify mode,delete mode and insert mode in forms 6i .
regards,
B.prakash

please look into the forms 6i online help manuals. There are the trigger flows of all events

Sequence of trigger firing in Forms

hi all,
can any one tell me sequence of trigger firing in forms
regards,
Ajay

Sorry boss,
the actual link is:-
Forms trigger Firing Sequence

Is it possible to change trigger firing sequence by program?

Hi,
I would like to know if there is a command like set_item_property or set_block_property or set_lov_property which can allow to change by program a trigger firing sequence. I do not find any, so i think i have to do it manually in property palette of the trigger. Thanks for your answer.

Thx
To change Execution Hierarchy of a trigger, we go into Property palette of that trigger to change this property, i want to know if it is possible to change this property by program without need to go into Property palette of that trigger, EXECUTE_TRIGGER executes an indicated trigger but how to change Execution Hierarchy (for example set_lov_property sets the given LOV property for the given LOV, we use set_lov_property in the program and do not need to go into property palette of this lov), hope you understand what i would like to do. thanks for your help.
Edited by: Tabit7 on Mar 20, 2011 4:40 AM

Oracle Forms Trigger firing hierarchy flowchart

Greetings,
In 1994, there was a "Oracle Forms Processing Manual" (Oracle part# A11990-2).
This book contained the visual representation of Oracle Forms processes showing where each trigger fires.
Where is this "flow-chart" in documentation available today?
I need to know the explicit chronological sequence of each trigger firing....
Pre-Form trigger fires first...then the When-New-Form-Instance....etc
Thank you for your support!

Sorry.
Let me clarify.
Need to know where it is defined about which trigger fires before or after which other trigger….
The whole sequence…every trigger…
Example:
Document must show stuff like ON-COMMIT fires before(or after) POST-DELETE.
So I am certain that when a delete is initiated by the user, the ON-COMMIT fires before(or after), and so data in the database record is still available(or not available) to the code in the ON_COMMIT trigger.
This helps me know for certain what really happens, step-by-step, when Forms deletes a record.
So the document must show a visual representation of the DELETE EVENT.
This visual representation must explicitly show the ON-COMMIT trigger and the PRE-DELETE trigger and the ON-DELETE trigger and the POST-DELETE trigger…
Thank you!

Forms trigger Firing Sequence

Does anyone know where I can find details on firing sequence of each type of triggers on Item, Block and Form levels?
Can I set the Debugger to trace the actual sequence of firing of triggers at run-time?
Message was edited by:
wyfwong

i hope that the document may help!
(V45) Trigger Execution Sequence in Forms 4.5
=============================================
Introduction
This document lists the order in which triggers fire in Oracle Forms 4.5:
o The first column, Action, describes the function to be performed
(e.g. deleting a record).
o The second column, Trigger Firing Order, describes the order
in which triggers fire after a function is performed.
o The third column, Level, describes the level (form, block, item)
at which the trigger fires. This was accomplished by creating a form
with all the triggers invoked. If a trigger could fire at all levels,
it was included at all levels. Such a trigger fires at the lowest level
at which it is defined.
Key triggers and triggers which fire via buttons or check boxes are
not included.
This bulletin does not cover every contingency and covers only the
most commonly used actions.
Action Trigger Firing Order Level
Runform 1. Pre-Logon Form
2. On-Logon Form
3. Post-Logon Form
4. Pre-Form Form
5. When-Create-Record Block
6. Pre-Block Block
7. Pre-Record Block
8. Pre-Text-Item Item
9. When-New-Form-Instance Form
10. When-New-Block-Instance Block
11. When-New-Record-Instance Block
12. When-New-Item-Instance Item
Enter Query 1. Post-Text-Item Item
2. Post-Record Block
3. When-Clear-Block Block
4. When-New-Record-Instance Block
5. When-New-Item-Instance Item
Note: If you define the Key-ENTQRY trigger, this is the only trigger
which fires in an Enter Query situation.
Execute Query
After Enter Query 1. Pre-Query Block
2. Pre-Select Block
3. On-Select Block
4. When-Clear-Block Block
5. Post-Select Block
6. On-Fetch Block
7. On-Close Form
8. When-Clear-Block Block
Note: If you define the Key-EXEQRY trigger, this is the only trigger
which fires in an Execute Query situation.
Execute Query
Without Enter
Query 1. Post-Text-Item Block
2. Pre-Query Block
3. Pre-Select Block
4. On-Select Block
5. Post-Select Block
6. On-Fetch Block
7. On-Close Form
8. When_Create_Record Block
9. Pre-Record Block
10. Pre-Text-Item Item
11. When-New-Record-Instance Block
12. When-New-Item-Instance Item
Exit 1. Post-Text-Item Item
2. Post-Record Block
3. Post-Block Block
4. Post-Form Form
5. On-Rollback Form
6. Pre-Logout Form
7. On-Logout Form
8. Post-Logout Form
Next Field and
Previous field 1. When-New-Item-Instance Item
Next Record and
Previous Record 1. When-New-Record-Instance Block
2. When-New-Item-Instance Item
Next Block and
Previous Block 1. Post-Text-Item Item
2. Post-Record Block
3. Post-Block Block
4. When-Create-Record Block
5. Pre-Block Block
6. Pre-Record Block
7. Pre-Text-Item Block
8. When-New-Block-Instance Block
9. When-New-Record-Instance Block
10. When-New-Item-Instance Form
Records Are Queried 1. Post-Query Block
2. Post-Change Block
3. Post-Change Item
4. Post-Change Block
5. Post-Change Block
Go back to Post-Query
NOTE: This cycle is repeated for each record retrieved.
No Records Are Queried 1. When-New-Record-Instance Block
2. When-New-Item-Instance Item
NOTE: To observe this Trigger Firing Order:
a. Enter a query.
b. Enter a nonexistent record.
c. Execute the query.
The two triggers listed above, the Enter Query triggers, and
the Execute Query triggers fire.
Create Record 1. Post-Change Block
2. When-Validate-Item Block
3. Post-Text-Item Block
4. When-Validate-Record Block
5. Post-Record Block
6. Post-Block Block
7. On-Savepoint Form
8. Pre-Commit Form
9. Pre-Insert Block
10. On-Insert Form
11. Post-Insert Block
12. Post-Forms-Commit Form
13. On-Commit Form
14. Post-Database-Commit Form
15. Pre-Block Block
16. Pre-Record Block
17. Pre-Text-Item Block
18. When-New-Item-Instance Form
Update Record 1. When-Database-Record Block
2. Post-Change Block
3. When-Validate-Item Block
4. Post-Text-Item Block
5. When-Validate-Record Block
6. Post-Record Block
7. Post-Block Block
8. On-Savepoint Form
9. Pre-Commit Form
10. Pre-Update Block
11. On-Update Block
12. Post-Update Block
13. Post-Forms-Commit Form
14. On-Commit Form
Here the transaction is complete and one record added.
15. Post-Database-Commit Form
16. Pre-Text-Item Block
17. When-New-Item-Instance Form
NOTE: To observe this Trigger Firing Order:
a. Execute a query.
b. Change a value.
c. Choose Action->Save from the menu.
d. Record the triggers from that point.
Delete Record 1. On-Lock Block
2. When-Remove-Record Block
3. Post-Change Block
4. Post-Change Block
5. Post-Change Block
6. Post-Change Block
7. Post-Change Block
8. Post-Change Block
9. Post-Change Item
10. Post-Query Block
11. Post-Text-Item Block
12. Post-Record Block
13. Pre-Record Block
14. Pre-Text-Item Block
15. When-New-Record-Instance Block
16. When-New-Item-Instance Form
NOTE: To observe this Trigger Firing Order, delete a detail record.

How can I get/Catch the information about Trigger firing?

How can I get/Catch the information about Trigger firing?

I am running one application (backend is Oracle) and have written one trigger, which will insert one row in two tables depending on user event (After Update Trigger).
I want know last fired Trigger Information.
Thanks

Pre-query trigger firing twice

I have a pre-query trigger on a block in a form to set the "default where" as
SET_BLOCK_PROPERTY (BLOCK_ID, default_where,where_clause);
but when I look at the current query for the session the where clause looks like
WHERE screening_group_num = :1 AND (screening_group_num = :2)
Why is this firing twice?
I checked this thread : Re: pre-query firing twice but I dont have any calls to execute_query in the form.

I am setting the where_clause in the pre_query trigger for that block.
and the copy value is not set for the screening_group_num item or for that matter any other item in the block. For all other items, it dosent really matter if the comparison is done twice (as the values will be same) , but when I have text (string) items, then its a problem. For example:
Where
(event_description LIKE '%test%') --- this is from the pre_query trigger where I am doing a string_comparison using 'Like and %%'
AND (event_description = :1) --i suppose this is from the default where clause of the block

Issue with When Validate Trigger firing multiple times

Hi guys,
I have Designed a Form Personalization on a Form which Fires a concurrent Program (built in:execute Procedure) when a Record is Saved.
Below are the issues I am facing:
1.Concurrent Program is Firing Multiple Times after Saving the Record.
2.2 input Values to Concurrent Program are passed as NULL though I have Data but they are in Different Block of Form.
Note :I have When Validate trigger on 1 Block but i am trying to pass 2 Values on Another Block as input parameters for Concurrent program.But those values are getting as null when program fires.
Thanks.

If EBS then post in {forum:id=475}

After update trigger firing on after insert

Hi All,
I am using oracle database version 8i.
I have one database trigger
create or replace trigger mna_post_update
after update
on mobile_number_actions
for each row
when (new.mna_status = 'P'
and new.mna_type in ('I','C','R','D','M','T','A','N','O'))
begin
insert into test1234 values (:new.mna_mcp_serial_no,:old.mna_mcp_serial_no);
end;
The problem is that it is giving the same value for :new.mna_mcp_serial_no and :old.mna_mcp_serial_no. And also in my table insertion is taken place not updates I have no idea why this trigger is firing on insert?
Could any one please tell me how is this possible?
Please help !!

Are you sure you don't have a similar trigger that is firing on inserts (perhaps you were debugging this code and inadvertently created one that fired on inserts or on inserts & updates)?
Assuming you are updating MNS_MCP_SERIAL_NO, you should be getting different values in test1234. If you are not, can you post a brief test case (including DDL to create the objects) that shows the problem(s) you're seeing?
Justin

Database Trigger firing order

If I implement THREE after insert triggers on the same table using unique trigger names but with different coding, how can I know which set of code is fired.
create trigger mytrigger1
after insert on mytable
for each row
-- coding 1
create trigger mytrigger2
after insert on mytable
for each row
-- coding 2
create trigger mytrigger3
after insert on mytable
for each row
-- coding 3
Is it a general practice to combine code into ONE trigger for the same trigger condition?
create trigger mytrigger
after insert on mytable
for each row
-- coding 1
-- coding 2
-- coding 3

If you have multiple triggers of the same type on a table, Oracle fires the triggers arbitrarily. If you want the triggered actions to occur in a specific order, you should consolidate them into one trigger.

Trigger firing more than once

Can any one help me i am having the problem with trigger . The trigger fires more than once. I want the trigger to be fired for every COMMIT and not for each row.
The pl/sql used for populating the table in given below
CREATE OR REPLACE TRIGGER REFRESH_MV_TRIGGER
AFTER INSERT OR UPDATE ON CONTACT_HISTORY
DECLARE
cnt NUMBER;
BEGIN
IF ( INSERTING ) THEN
dbms_output.put_line('INSERTING');
END IF;
IF ( UPDATING ) THEN
dbms_output.put_line('UPDATING');
END IF;
END;
DECLARE
BEGIN
FOR i IN 1..2 LOOP
INSERT INTO CONTACT_HISTORY(TARGET_ID,CAMPCODE,COMMSTAGE,CUSTOMER_KEY,solicit_dt)
VALUES(i,'CAMP4','COMM1',i,SYSDATE);
END LOOP;
COMMIT;
END;
sql> output when i run pl/sql block
INSERTING
INSERTING

I am not shure what you need exactly but maybe this might help:
CREATE TABLE dept (
deptno NUMBER(2) PRIMARY KEY,
dname VARCHAR2(14),
loc    VARCHAR2(13)
CREATE TABLE dept_history (
deptno NUMBER(2),
dname VARCHAR2(14),
loc    VARCHAR2(13)
CREATE MATERIALIZED VIEW dept_mv
BUILD IMMEDIATE
REFRESH ON COMMIT
AS SELECT * FROM dept
CREATE OR REPLACE TRIGGER bir_dept_mv
BEFORE INSERT ON dept_mv
FOR EACH ROW
BEGIN
INSERT INTO dept_history VALUES (:NEW.deptno, :NEW.dname, :NEW.loc);
END;
INSERT INTO DEPT (deptno, dname, loc) VALUES (1, 'D1', 'L1');
1 row created.
INSERT INTO DEPT (deptno, dname, loc) VALUES (2, 'D2', 'L2');
1 row created.
SELECT * FROM dept;
    DEPTNO DNAME          LOC
         1 D1             L1
         2 D2             L2
SELECT * FROM dept_history;
no rows selected
SELECT * FROM dept_mv;
no rows selected
COMMIT;
Commit complete.
SELECT * FROM dept_history;
    DEPTNO DNAME          LOC
         1 D1             L1
         2 D2             L2
SELECT * FROM dept_mv;
    DEPTNO DNAME          LOC
         1 D1             L1
         2 D2             L2Regards,
Zlatko Sirotic

Trigger firing on destination db

Can I use the same technique(from Adv Rep) to stop trigger from refiring at destination db by using following to allow otherwise not fired?
BEGIN
IF DBMS_REPUTIL.FROM_REMOTE = FALSE
THEN

In fact, le trigger WILL NOT FIRE at the destination database unless you want it. See the response i made on the "Execution of Row level trigger in Oracle Streams.
" topic on the next page
Claudine.

DB Trigger firing issue in case of oracle forms session crash

Hi All,
Oracle DB version: Oracle Database 10g Release 10.2.0.2.0 - Production
Oracle Forms version: (Oracle Developer Suite 10g) 10.1.2.0.2 Production
I am entering some data in the oracle forms and committed the data to database. This form is still open.
By some reasons i get a error as "FRM-92101: There is error during forms server startup" and the forms session gets crashed.
When this event happens i wanted to update the records which are inserted before this error occurred. For this purpose i created a BEFORE LOGOFF ON DATABASE trigger (in SYS user) and declared that transaction as autonomous and performed update and then commit.
But when i get this error in forms runtime session, this trigger doesn't fire and also the records don't get updated.
If i query to v$session view, the session entry is gone because the forms session is crashed.
Can anyone please tell me why this trigger don't get fire when oracle forms session gets crashed? Or is there is any other way to run update statement as soon as the forms session gets crashes?
Thanks.

Hi,
please check java runtime console for more issue information.
Windows:
SystemControl->Java Plugin Ver XXXX -> Standard -> Check "Show Java Console"
In Systray, check the console for information about errors in java after the form error.
Attackwave

Forms 6.0 Trigger firing order

Hi, I have a master-detail form where I "execute_query" during new_form_instance. I display 5 master records and for the current master all detail records with one detail being current. The cursor focus is in the master block.
I'm looking for the last trigger to fire before the user has access to
form.
I need to do two things:
1. Go to a specific detail record i.e go_record(3) if a condition is meet.
2. I need to set a detail item property that is valid only for the current detail. enable or disable a button.
I use a post_query and when_new_record_instance trigger to change the item property for the current detail block. This only works if the user enters and scrolls through the detail block. BUT I need to change the item while the user scrolls through the master block.
Ideas?
Is there a trigger that that fires after all data has been queried and the form is about to display where I can check a condition and set properties?
Thanks, Dave
null

Maybe this help:
You can try to modify On-Populate-Details
and On-Clear-Details triggers.
Helena

Trigger Firing in Form6i

Similar Messages

Maybe you are looking for