The Oracle Forms Builder is an Integrated Development Environment (IDE)
included in the Oracle Developer Suite package. It is intended for Rapid
Application Deployment (RAD) using PL/SQL.
What are the steps you have to follow to register a
Form?
·
We will down load template.fmb from AU_TOP ($AU_TOP/forms/US) resource folder. Then we will delete
block name from window, datablock, canvas.
·
Change the property class for window,
canvas and data block.
·
Change the name of form.
·
Go to pre_form
trigger at form level. Give the window name in set window position function.
We change action History like date and author name (optional).
·
Go to when
_new_form instance at form level give the form name in template.fmb place
·
Go to program
units select app_custom package
body in the following function.
If (wnd = 'window name') then app_window.close_first_window;
·
Compile the form and save. It will create FMB and
create the fmx by following option.
File => administration
=> compile file.
·
move the fmb to au_top=>11.5.0=>forms=>us
·
move the fmx to the corresponding to PO => 11.5
=> forms => us
·
Select
the responsibility called application developer
First create the form by using following navigation
application => form
give the name of fmx in form field. Give the application
name where the fmx is stored. We can give our own user form name select the
user form name goto function we will create the function, user function name
select properties tab and choose the type as form And goto form tab give
the user form name in the form field
·
Go to menu option will attach the function to the
menu
·
We will attach the menu to the resp through
sysadmin.
How
do you generate Apps Forms modules or FMB files?
Oftentimes as part of
upgrading Forms or modifying a Form module or applying a patch modifying a Form
module, you would encounter an issue that would necessitate manually
regenerating the Forms module executable or FMX file. To do this you issue the
following command: f60gen module=form_name.fmb userid=apps/apps output_file=form_name.fmx
module_type=form batch=yes compile_all=special
How
do you generate Apps Forms library modules or PLL files?
To do this you issue
the following command: f60gen module=library_name.pll
userid=apps/apps module_type=library batch=yes compile_all=special
Write the Abbreviation for the
following File Extension?
1. FMB – Form Module Binary
1. FMB – Form Module Binary
2. MMB
-- Menu Module Binary
3.
PLL—PL/SQL Library Module Binary
What is ZOOM? How it works?
Zoom is a
function provided by apps which can be used to call another form from a form.
For making zoom available for your form u have to customize the
custom.pll. We have to add a branch
stating if form name (specify form name) and blockname (specify blockname) then
make zoom available.
What are the standard libraries available in
template form?
·
FNDSQF(Routines for handling Message Dictionary, flexfields,
profiles, concurrent processing, multicurrency, WHO)
·
APPCORE
·
APPCORE2
·
APPDAYPK(Controls the Application Calendar)
·
CUSTOM
What is who column and how you set the values?
CREATED_BY,
CREATION_DATE,
LAST_UPDATED_BY,
LAST_UPDATED_DATE,
LAST_UPDATE_LOGIN
The
custom form requires a pre-insert trigger at the block level containing the
FND_STANDARD.SET_WHO function. This
trigger/function enables the 'About This Record' info and displays the info for
the User when requested.
Name the directory having the FORMS source
codes (FMB files)?
The
FORMS source codes having the directory $AU_TOP/forms/US
Can we change the profile value? How?
Fnd_profile
API can be used to set the profile value
fnd_profile.put
(name in varchar2, value in varchar2).
What are the steps you have to follow to register a custom
application?
·
Register custom application in AOl
·
create a physical director structure under
APPL_TOP
·
modify the environment file to include
custom schema path
·
in the backend register the custom schema
as user
·
register the user with AOl
·
add the custom schema to standard data
group
·
register all the custom table with the
application
·
create synonyms in apps schema for custom
objects
What is event handler package?
An event
handler is a PL/SQL procedure that encapsulate all the code that act upon an
event. Usually we will use to satisfy the requirement of Oracle forms or oracle
application interface standard for form base product.
Can we modify all the triggers?
No.
There are some triggers which should not be modified. Here are the form triggers
that must not be changed
CLOSE_THIS_WINDOW,
CLOSE_WINDOW,
EXPORT,
FOLDER_ACTION,
KEY–COMMIT,
KEY–EDIT,
KEY–EXIT,
KEY–HELP,
LASTRECORD,
MENU_TO_APPCORE,
STANDARD_ATTACHMENTS,
WHEN–WINDOW–CLOSED,
WHEN–FORM–NAVIGATE,
ZOOM
When you are moving a cursor on a form what are the
possible triggers that are going to be fired?
If you are
moving from an item of first block to the item of another block in a form then
following trigger will be fired.
post-text
pre-text
when-validate-item
(fired only when the status of the text item has been changed)
post-block
pre-block
when-new-block-instance
when-new-item-instance
If you are
moving from an item to another item in same form then following trigger will be fired.
Post-text
when-validate-item
(fired only when the status of the text item has been changed)
pre-text
when-new-item-instance
No comments:
Post a Comment