Buttons can either be textual or iconic; that is, they display either words or a picture.
Buttons should be items in the block they act upon or appear to be part of (not in a control block). For example, create an "Accept" button as a non-database object in the block on which it performs the accept. If you navigate to a LINES block from a HEADER block using a "Lines" button, make the button part of the HEADER block.
For information about the look and feel of buttons, see the Oracle Applications User Interface Standards for Forms-Based Products.
Textual buttons use the BUTTON property class. Iconic buttons use the BUTTON_ICONIC property class and typically appear only in the toolbar or in folder forms.
Warning: Never override the height specified by the BUTTON property class.
Single record block buttons are Keyboard Navigable Yes. Multi-record block buttons are Keyboard Navigable No. The exception is Clear buttons, which should always use Keyboard Navigable No. This is to prevent users from accidentally clearing records when they expect to fire the default button.
All buttons are Mouse Navigate No.
Iconic buttons cannot be operated from the keyboard. If your form is intended to used for heads-down data entry (keyboard only), this implies the functionality they add must either be non-essential or have a secondary invocation method, such as the menu.
Most buttons do not apply in Enter-Query mode. Users cannot leave the current record while in this mode. You do not need to explicitly disable a button while in Enter-Query mode; instead set the trigger property "Fire in Enter-Query mode" for the WHEN-BUTTON- PRESSED trigger to No.
Buttons should call APP_STANDARD.APP_VALIDATE and pass a scope before performing their action. This ensures that your records are valid before performing an action, and that the button acts on the expected block.