Flip-flop explanation

1. ACCEPT
App_standard. EVENT (' ACCEPT ');
This trigger handles the call to save and Proceed (save and Continue) action on the menu or toolbar. It performs the save and moves to the block specified as the first navigation block. Replace the code in this trigger, or create a block-level trigger and specify the execution type as ' Override '.
2. Folder_return_action
Null
This trigger allows you to specify custom folder events to be replaced with code that requires the handling of folder actions.
3. Key_duprec
App_standard. EVENT (' Key-duprec ');
This trigger disables the default duplicate record functionality for Oracle forms.
4. Key-clrfrm
App_standard. EVENT (' key-clrfrm ');
This trigger validates the record before attempting to empty the form, adds additional code after the original code, usually you should add go_block if there are multiple areas in the form, use Go_block to repopulate the control menu after calling the empty from operation
5. Key_menu
App_standard. EVENT (' Key-menu ');
This trigger disables the Block Menu command for Oracle Froms. In order to enable the substitution of blocks from a specific block through the keyboard, then write block-level key_menu and set the execution type to ' override ' this trigger will open a pop-up menu with the same lov
6. Key_listval
App_standard. EVENT (' Key-listval ');
This trigger performs an elastic domain operation or reference lov
Create a block or item-level trigger and set the execution type to ' Override ' to use the calendar or dynamic execution of the elastic field
7. On-error
App_standard. EVENT (' On-error ');
This trigger handles all errors of the server or client, called using the message dictionary. To catch processing of the specified error, check the specified error before calling App_standard

Declareoriginal_messvarchar2( the);beginIFMessage_code= <Your message Number>  Thenoriginal_mess:=Message_type||’–’||To_char (Message_code)||’: ’||message_text;–––your code handling the error goes heremessage (original_mess);ELSEApp_standard. EVENT (' On_error ');END IFEnd;

8. Pre-form

Fnd_standard. Form_info (' $Revision:< Number>$ ', '<Form Name>', '<Application ShortName>', ' $Date:<Yy/Mm/DD HH24:MI:SS>$ ', ' $Author:<Developer Name>$ '); App_standard. EVENT (' Pre–form '); App_window. Set_window_position (' Blockname ', ' First_window ');

This trigger initializes the internal values and menus for the Oracle app. The values entered here will be seen in the Oracle Application Menu ' Help on Oracle Applications '.
You must edit the short name of the application, and the app's short name controls which app's online help document will be called when the user chooses the ' Assist ' button. If you set the short name of the app to FND, your users will not see any help because Oracle applications will not be able to establish available help targets. The name of the
form is the user form name (form title).
Oracle Corporation uses the source control system, which automatically updates values beginning with "$", and if you do not use this source control system you can edit these values according to your development information.
You must edit the Blockname in App_window as your own block. Do not edit First_window
9. Query_find
App_standard. EVENT (' Query_find ');
This trigger will set the display string ' Query Find is not available '
to replace the code in this trigger when you create a window or Row_lov in your form to create a block-level trigger and set the execution type to ' Override '
Ten. When-new-form-instance

 fdrcsid (' $Header: ... $ '); App_standard. EVENT ('   -- app_folder.event (' VERIFY ');  

Call App_standard. The EVENT is intended to be lowered with fnd_function in query-only mode. EXECUTE, called Fndrcsid, is the source control system for the Oracle application. App_folder is called only for internal Oracle applications. The custom form does not require FDRCSID or app_folder calls, but it has no effect if you leave them in the trigger.
Add additional code before the existing code.
When-new-record-instance.
App_standard. EVENT (' when-new-record-instance ');
This trigger manages the Oracle Application menu and toolbars
Create a block-level trigger and set the execution type to ' before '.
When-new-item-instance.
App_standard. EVENT (' when-new-item-instance ');
This trigger manages the menus and toolbars for Oracle Applications
If you add an elastic domain method call, you should add it to the App_standard. Call before the EVENT call, usually you should not add any code in this trigger, such code will affect the speed of your form and affect each item
Post-form.
App_standard. EVENT (' Post-form ');
This trigger is reserved for later use, adding additional code after the original code.

The following are triggers that cannot be modified
Modified form-level triggers are not supported by Oracle applications.
1. Close_this_window
Invokes trigger App_custom from the menu action->close. Close_window.
2. Close_window
App_custom. Close_window (: SYSTEM. Event_window);
This departs the event that it handles all closed windows. The event written to handle the closing window must be written in App_custom. Close_window in Bag
3. EXPORT
App_standard.event (' EXPORT ');
This trigger is a selection from the "Action,export" menu.
4. Folder_action
App_folder.event (: global.folder_action);
5. Key-commit
App_standard.event (' Key-commit ');
This trigger handles a normal commit or a form call
6. Key-edit
App_standard.event (' Key-edit ');
This trigger handles an elastic field or Calendar, editor action.
7. Key-exit
App_standard.event (' Key-exit ');
This trigger handles the shutdown event and exits the Enter-query state
8. Key-help
App_standard.event (' key-help ');
This trigger invokes the window's Help system.
9. LastRecord
App_standard. EVENT (' LastRecord ');
This trigger handles the menu (Go->last RECORD) event
Ten. Menu_to_appcore
App_standard.event (: Global.menu_to_appcore);
This trigger supports the special menu
standard_attachments.
Atchmt_api.invoke;
This trigger handles the invocation of the Attachment menu or tool button
When-window-close.
Execute_trigger (' Close_window ');
This trigger sets the closing event of a form
when-form-navigate.
You cannot modify this trigger, it contains the standard behavior, normalize the form when the minimized form is navigated to.
ZOOM
Appcore_custom.event (' ZOOM ');
This trigger handles the menu or toolbar button ' Action,zoom ' event.

Flip-flop explanation