You are on page 1of 22

Form Customization &

Personalization
Guru Prasad

1
Agenda
 CUSTOM Library
 Form Personalization

2 Copyright 2014 Fujitsu India GDC


CUSTOM(.pll) Library
The CUSTOM library is:
 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
products and integrate your code directly with Oracle Applications.
 A supported, upgradeable, user definable, partitioned code repository
for custom code.
In short, the CUSTOM library lets you change properties,
functionality and operation of a form as if you were actually
changing the source code of the form.
 The CUSTOM can be found in $AU_TOP/Resource directory.

3 Copyright 2014 Fujitsu India GDC


CUSTOM(.pll) Library
Common Usages of CUSTOM.pll
 Enabling and disabling the fields
 Hide and Show fields
 Changing the list of values in a LOV field at runtime
 Defaulting values into fields
 Validating additional record level
 Enabling the Special menu
 Zooming and navigating to other screens

4 Copyright 2014 Fujitsu India GDC


CUSTOM(.pll) Library
How the CUSTOM Library Works:
The CUSTOM library works by sending ‘EVENTS’ from each Oracle
Applications form to the CUSTOM library, which is automatically
attached at runtime. User defined custom code, which is in the
CUSTOM library, can then take effect based on these events.

CUSTOM Library
EVENT
(Your Custom
*.fmx
Code) WHEN-NEW-FORM-INSTANCE
WHEN-NEW-BLOCK-INSTANCE
etc.

5 Copyright 2014 Fujitsu India GDC


CUSTOM(.pll) Library
All the standard forms have calls to CUSTOM library through specific
events at runtime.

Listed are the events that invoke CUSTOM library

 WHEN-NEW-FORM-INSTANCE
 WHEN-NEW-BLOCK-INSTANCE
 WHEN-NEW-RECORD-INSTANCE
 WHEN-NEW-ITEM-INSTANCE
 WHEN-VALIDATE-RECORD
 ZOOM

6 Copyright 2014 Fujitsu India GDC


CUSTOM(.pll) Library
 All the forms in Oracle Applications has APPCORE.pll attached to
it. This APPCORE library has APP_STANDARD package which is
called by specific event when form level triggers (i.e. events) are
fired.

 All the form level triggers call APP_STANDARD.EVENT which


internally calls CUSTOM.EVENT via a procedure
CALL_ALL_LIBRARIES.

APP_STANDARD.EVENT(‘<EVENT_NAME>’)
CALL_ALL_LIBRARIES(<EVENT_NAME>)
CUSTOM.EVENT(<EVENT_NAME>).
Microsoft Word
Document

7 Copyright 2014 Fujitsu India GDC


CUSTOM(.pll) Library
 Attach libraries to CUSTOM library: We can attach other libraries to
CUSTOM library but do not attach APPCORE to CUSTOM library
because CUSTOM is already attached to APPCORE. So that it
causes recursive problem.
 It is advisable to attach APPCORE2 to CUSTOM. The APPCORE2
library duplicates most APPCORE routines with the
packages like APP_ITEM_PROPERTY2, APP_DATE2,
APP_SPECIAL2.

 By default FNDSQF library is attached to CUSTOM.

8 Copyright 2014 Fujitsu India GDC


CUSTOM(.pll) Library
 Custom library has the following procedures and functions.
Function ZOOM_AVAILABLE and STYLE
Procedure EVENT.

 When extending the functionality of forms using CUSTOM library it


is important to identify the correct trigger for CUSTOM library in
order to write the extension logic. This can be done by enabling the
show custom events by navigating to Help | Diagnostics | Custom
Code | Show Custom Events.

Microsoft Word
Document

9 Copyright 2014 Fujitsu India GDC


CUSTOM(.pll) Library
 Examples using Custom library:
1. ZOOM: Zoom is the functionality of calling the one form from
another form.
Microsoft Word
Document

2. Hiding fields
3. Enter text in upper case,
4. Making fields mandatory
5. Change field color
6. Changing the filed prompts Microsoft Word
Document

10 Copyright 2014 Fujitsu India GDC


CUSTOM(.pll) Library
 Compiling CUSTOM library: After making necessary changes to
CUSTOM library transfer CUSTOM.pll to $AU_TOP/resource
folder. Ensure that you have the backup of original CUSTOM.pll
file. After that run the command frmcmp_batch to generate
CUSTOM.plx.

 frmcmp_batch module=CUSTOM.pll userid=apps/<appspassword>


output_file= CUSTOM.plx compile_all=special
module_type=LIBRARY batch=yes

11 Copyright 2014 Fujitsu India GDC


CUSTOM(.pll) Library
 Limitations:
1. CUSTOM.pll is single file hence only one developer can make
changes to CUSTOM.pll at a any given point of time.
2. If any thing goes wrong for some reasons, then CUSTOM.pll needs
to be modified.

To overcome these limitations, use forms personalization.

12 Copyright 2014 Fujitsu India GDC


Form Personalization
 Form Personalization : Form personalization is a feature introduced
starting from E-Business Suite version 11.5.10.2 onwards which
allows changing the behavior of form based screens.

 Form personalization is used to achieve


1. Hide, show, enable and disable forms.
2. Display messages.
3. Initialize global variables and assign values to global variables.
4. Make items mandatory.
5. Change the list of values (LOV) properties.
6. Activating special menu.

13 Copyright 2014 Fujitsu India GDC


Form Personalization
 Enable Diagnostics: Use profile options to enable the Help |
Diagnostics | Examine.
Hide Diagnostics menu entry : Yes/No
Set ‘Yes’ to hide Diagnostics menu and ‘No’ to display Diagnostics
menu .
Utilities:Diagnostics : Yes/No
If set to ‘No’, Apps password is required to access Diagnostics
menu. If set to ‘Yes’, Apps password is not required.

 Invoke form personalization: Navigate to Help | Diagnostics |


Custom Code | Personalize to invoke form personalization.

14 Copyright 2014 Fujitsu India GDC


Form Personalization
 Each and every form to be personalized has 4 sections
Rules, Conditions, Context and Actions.
1. Rules: Rules are associated with Sequence and description. These
rules tells us in which sequence the personalization needs to
executed. These rules can be Enabled/Disabled by selecting the
Enable check box which is available for each row.
2. Conditions: Conditions decide that when a rule is to apply. Each
condition has 3 sections, Trigger event, Trigger object and
Condition.
3. Context: Context manages to whom the personalization should
apply. It has 4 levels, Site, Responsibility, User and Industry.
4. Actions: Actions are the operations to be performed when a
condition is evaluated to true. The types of actions available are
Property, Message, Builtin and Menu.
15 Copyright 2014 Fujitsu India GDC
Form Personalization
Object types for each properties:

16 Copyright 2014 Fujitsu India GDC


Form Personalization
 Example using form personalization:
1. Changing the labels/Prompts in the form. Microsoft Word
Document

2. Assign default values to a field. Microsoft Word


Document

3. Hiding and making fields mandatory Microsoft Word


Document

4. Making fields non-updatable. Microsoft Word


Document

5. Attach Menu, ZOOM functionality, Global variables and Display


messages. Microsoft Word
Document

17 Copyright 2014 Fujitsu India GDC


Form Personalization
 Form personalization are stored in FND table.
FND_FORM_CUSTOM_RULES
FND_FORM_CUSTOM_SCOPES
FND_FORM_CUSTOM_ACTIONS
FND_FORM_CUSTOM_PROP_VALUES
FND_FORM_CUSTOM_PROP_LIST

18 Copyright 2014 Fujitsu India GDC


Form Personalization
 Moving Personalization between instances: Since Form
personalization is stored in FND tables, these can be downloaded to a
loader files and can be uploaded to another instance by using this
file.
Use FNDLOAD utility to download and upload the loader files from

one instance to another instance.


Download:
FNDLOAD <userid>/<password> 0 Y DOWNLOAD
$FND_TOP/patch/115/import/affrmcus.lct <filename.ldt> C:\Users\
ummadigu\Desktop\CUST & FORM PER
FND_FORM_CUSTOM_RULES function_name=<function name>

Upload:
FNDLOAD <userid>/<password> 0 Y UPLOAD
$FND_TOP/patch/115/import/affrmcus.lct <filename.ldt>
19 Copyright 2014 Fujitsu India GDC
Form Personalization
Userid , password data base userid and password
Filename.ldt  LDT file name (Suggested any name as per standards)
Function_name  Function short name as seen in the Function
Definition Screen.

20 Copyright 2014 Fujitsu India GDC


Form Personalization
 Advantages of Form Personalization:
1. Changes take place immediately on reopening the form.
2. Personalization are stored in base tables related to Form
Personalization. So, it is very easy to track the information like who
made the changes and when.
3. Can be moved easily through FNDLOAD from one instance to
other.
4. Can be restricted at site/responsibility/user level.
5. Easy to disable/enable with click of a button.

21 Copyright 2014 Fujitsu India GDC


22

You might also like