Learning OAF is not a big deal
but debugging the errors while learning phase will make you feel sick and urge
you dropping the plan of learning. I started learning and dropped it twice. At
last I succeeded now. It took around 4 complete days to run my first oaf
project.
The foremost thing to look at
before learning OAF is choosing the correct version of jdeveloper. There are
too many versions of jdeveloper and patches available in internet. We should
make sure to select the correct version of jdeveloper.
Set the correct database
connection, in this step we can test the connection in the connection create
window itself. Get the correct DBC file from the DB administrator and add it in
the application property.
Get the correct application name
and the corresponding responsibility key which is active for set up. Below is
the query to find the responsibility key and application short name and other information’s
related.
SELECT
r.responsibility_name,r.responsibility_key, fa.APPLICATION_SHORT_NAME,
r.version, u.user_name, u.description, r.start_date,
r.end_date
FROM
apps_fnd.fnd_user_v u,
apps_fnd.fnd_user_resp_groups ur,
fnd_responsibility_vl r,
fnd_application_tl a,
fnd_application fa
ur .responsibility_id = r.responsibility_id
AND
u.user_id = ur.user_id
AND
fa.APPLICATION_ID = a.APPLICATION_ID
AND
r.application_id = a.application_id
In Tools menu, select
“preferences Embedded OC4J”, try to use "Default Local IP Address"
option.
Lastly, take care of the naming
of the package we create. The naming convention for the package we create
should starts with the company name, oracle, apps and the application name.
Usually the OC4J components will be stored in the package like
XXX.oracle.apps.fnd.projName.Schema.Server. The User interface will be stored
in the package XXX.oracle.apps.fnd.projName.Schema.webui.
These
are some of the issues I faced while learning OAF. There might be lot more
errors. But these are the areas where most of the mistakes happens while
learning.