1.
CUSTOM.PLL
-
A
mechanism that allows extension of Oracle Applications without modification of
Oracle Applications code
-
An
Oracle Forms PL/SQL library that allows you to take full advantage of all of
the capabilities of the Developer 2000 suite of products and integrate your
code directly with Oracle Applications
-
A
supported, upgradeable, user definable, partitioned code repository for custom
code
When
to Use the CUSTOM Library
There
are four main ways to use the CUSTOM library. Each of these must be coded
differently.
1.
Zoom:
A Zoom opens another form and can pass parameters to the opened form.
2. Logic
for generic events: Augment Oracle Applications logic for certain
generic
form
events. such as
WHEN–NEW–FORM–INSTANCE or
WHEN–VALIDATE–RECORD.
3. Logic for
product-specific events: Augment or replace Oracle Applications logic
for
certain
product–specific events that enforce
business
rules.
4.
Custom
entries for the Special menu:
Add
entries to the Special menu for Oracle Applications forms, such
as
an
entry that opens a custom form.
- ZOOM
-
Using
Oracle Forms builder, open /AU_TOP/res/plsql/CUSTOM.pll
-
now
double click on
-now write following code
-
now
compile above code and
-
write
code for event to call form when you click on zoom control
-
compile
above code and save custom.pll and close form builder
TO CHECK ZOOM CONTROL ACTIVATED OR NOT
-
Now
click on ZOOM control following window opens
- CODING FOR GENERIC EVENTS
The CUSTOM library receives two different
kinds of event calls:
1. GENERIC :
Generic events are common for all Forms in Oracle Applications.
2. PRODUCT SPECIFIC.
events are reserved for future use by the applications and
are specific
to individual applications
Generic events:
· WHEN-NEW-FORM-INSTANCE
· WHEN-NEW-BLOCK-INSTANCE
· EXPORT
· WHEN-NEW-RECORD-INSTANCE
· WHEN-NEW-ITEM-INSTANCE
· WHEN-VALIDATE-RECORD
· ZOOM
1. let’s say that your company
insists that vendor names always be entered in
uppercase.
-Now check in suppler entry form in
purchase order module
- To hide description option in
journal enter window use
set_item_property('HEADER.DESCRIPTION',DISPLAYED,
PROPERTY_OFF);
- to disable description in
journal enter window
set_item_property('HEADER.DESCRIPTION',ENABLED,
PROPERTY_OFF);
- To make description as
mandatory
set_item_property('HEADER.DESCRIPTION',REQUIRED,PROPERTY_ON);
FORMS
PERSIONALIZATION
To
Change Journal Label As Enter Journal In The Below Window
-
click
on
-
Now
type
-
now
click on ACTIONS tab
-
Now
click on validate and click on Apply button
-
And
press CTRL+S
-
now
see the changes in the window
2.TO CHANGE ORDER NUMBER TO LABEL TO
CLAIM NUMBER
-
now
click on
-
now
enter password as apps and click on ok
-
now
enter the following details
-
Now
click on actions tab and enter
-
now
click on apply button
-
and
save and close the window
-
now
following change appear in sales order window
3.
TO WARN USER NOT TO ENTER SALES ORDER ON PARTICULAR DAY
-
now
click on
-now enter following details
-
now
click on validate button it should display following message
-
now
press ctrl+S to save the changes
-
now
click on action button
-
click
on validate button and click on ok button
-
now
click on apply now button and press ctrl + s
-
-
and close window
-
now
try to open sales order form on Friday you get following message
4.
TO MOVE CURSOR TO THE PARTICULAR POSITION WHEN YOU OPEN ANY WINDOW
-
now
when you open this window cursor appears in user name
-
now
to make cursor appear in description area then
-
open
personalization window and enter following details
-
click
on apply button and save
-
close
both windows and again open user define window
-
see
the cursor will be at description
- to disable the diagnostics option for the particular
user
-
now click on find button and enter following details
-
now save changes and enter another profile name
-
now click on find button and enter following details
-
-
Now connect to raju user and check in help menu
No comments:
Post a Comment