Have any question?
+2 0100 62 62 837
[email protected]
Register Login

Login with your site account

Lost your password?

Not a member yet? Register now

AppsLead | Learn Oracle From The LeadersAppsLead | Learn Oracle From The Leaders
  • Home
  • Courses
    • About Courses

      • Free Training
        • Oracle ebusiness suite Free
        • Oracle Fusion Free
      • Online Live Training
        • Oracle ebusiness suite
        • Oracle Fusion
        • Oracle Database
        • Java & Middleware
      • All Training Courses
      • Training Schedule
      • Register For Live Course
      • Join Our Team
      • Exam Request
  • Blog
    • Oracle ebusiness Suite
      • Oracle Financial
      • Oracle HCM
      • Oracle SCM
    • Oracle Fusion
      • Fusion Financial
      • Fusion HCM
    • Our Authors
    • Be an Author
  • Schedule
  • FAQs
  • About Us
    • About Us
    • Our Services
    • Our Authors
  • Contact Us
  • Home
  • Courses
    • About Courses

      • Free Training
        • Oracle ebusiness suite Free
        • Oracle Fusion Free
      • Online Live Training
        • Oracle ebusiness suite
        • Oracle Fusion
        • Oracle Database
        • Java & Middleware
      • All Training Courses
      • Training Schedule
      • Register For Live Course
      • Join Our Team
      • Exam Request
  • Blog
    • Oracle ebusiness Suite
      • Oracle Financial
      • Oracle HCM
      • Oracle SCM
    • Oracle Fusion
      • Fusion Financial
      • Fusion HCM
    • Our Authors
    • Be an Author
  • Schedule
  • FAQs
  • About Us
    • About Us
    • Our Services
    • Our Authors
  • Contact Us

Blog

  • Home
  • Blog
  • Understanding form personalization architecture

Understanding form personalization architecture

  • Posted by Sameh Bakkar
  • Categories Blog
  • Date November 17, 2013
  • Comments 0 comment
Understanding form personalization architecture Using the Form Personalization you have option to alter Oracle code at runtime bypassing important validation logic. Form Personalizations allows you to fundamentally alter the behavior of the seeded product forms that Oracle provides you to access data.. Form Personalizations looks very simple and easy things,but sometime this may jeopardize the integrity of your data. Therefore developer and solution provider context , you must have a clarity in architectural understanding.
Many People are bit confuse about the personalization, take a note … “Personalizations are created Per Function , not per Form “ A function launches a form and passes specific parameters; the same form may be invoked by different functions and to a user could act completely differently. dgreybarrowUNDERSTANDING THE COMPONENTS Lets take a EBS form , and try to understand various sub-section What you can see in above form , a Typical Oracle apps form Personalization consist of four major things
  • Sequences
  • Trigger Events
  • Conditions
  • Context
these attributes also have link with personalization.
  • Action
  • Property
  • Message
A Oracle Application Form is driven by form Function, therefore all subcomponent are tightly putin together.
dgreybarrow Sequences
It manages both Rules and Actions that have in Sequence that must be entered
  • It is there in case you need things to be processed in a specific order
  • The sequence does not have to be unique
dgreybarrowTrigger Events If you aware with basic frame of Oracle EBS form(template.fmb) , then you must be aware with inbuilts triggers and there sequnce of firing, Some of the triggers can be best understood to handle the events. Here are the some of events:
  • WHEN-NEW-FORM-INSTANCE: once, when the form starts up.
  • WHEN-NEW-BLOCK-INSTANCE: each time the cursor moves to a new block.
  • WHEN-NEW-RECORD-INSTANCE: each time the cursor moves to a new record.
  • WHEN-NEW-ITEM-INSTANCE: each time the cursor moves to a new item.
  • WHEN-VALIDATE-RECORD: each time the current record has any change that needed to be validated.
  • SPECIAL1 through SPECIAL45: each time the user selects a menu entry from the Tools, Actions or Reports menu.
dgreybarrowConditions The Condition field lets you create an expression in SQL which evaluates the run time action. In case of TRUE at runtime, then the Actions are performed, where as in case of FALSE Actions are skipped. Each time condition is re-evaluated the rule is processed or not. dgreybarrowContext This handle controls of the personalization and it applies to either a)Level(Site, Responsibility, Industry, or User) or b)Value whiich is specific value when level is Responsibility, Industry, or User
  • If you set the Rule has a context of ‘Site’, it will be applied for everyone
  • If you set rule with a context of Responsibility that mena it does not ‘override’ Site
  • If you set a rule with a context of User does not ‘override’ Site or Responsibility
  • If 2 rules have the same Trigger Event, and Actions that change the same property, the rule with the higher sequence number will be performed last.
dgreybarrowActions Actions determine what personalization does.
dgreybarrow TECHICAL DETAILS Personalizations are stored in tables, separate from the forms they alter:
  • FND_FORM_CUSTOM_RULES
  • FND_FORM_CUSTOM_ACTIONS
  • FND_FORM_CUSTOM_SCOPES
  • FND_FORM_CUSTOM_PROP_LIST
  • FND_FORM_CUSTOM_PROP_VALUES
  • FND_FORM_CUSTOM_PARAMS
dgreybarrowAFTER APPLYING A PATCH There is some confusion , with Form Personalizations and Patch in EBS. A patch will not change any personalizations that you have created; however, they may no longer be valid. There might be couple of reason that may affect for non-avibality of Personalization in particular form , for example..
  • Objects within a form may have been renamed or deleted
  • Functionality at the various trigger points may be changed
  • Property settings could interfere with your Rules
dgreybarrow IF SOMETHING GOES WRING , WHAT CAN YOU DO? You need to identify the forms affected by a patch , the first things you need to do is to run the personalization screen from any form and select Tools > Administration This will identify all forms that have Personalizations and have just been patched. Once you idetified ,run each function, possibly setting Custom Code to ‘Off’ if it fails to open Then finally run the Personalization screen and select Tools > Validate All This way you do able to resolve any pop-up issue beacuse of Patch.

Tag:form personalization

  • Share:
Admin bar avatar
Sameh Bakkar
Sameh Bakkar has over 15 years Oracle Applications implementation experience (EBS/Fusion) and he is an Oracle authorized trainer. He has in-depth technical and Functional knowledge of Oracle Applications and Oracle HCM Cloud. Sameh has excellent experience in Team management, Man Power and resource planning, and Pre-Sales management Process. Additionally he has also given Best Practices seminars on Oracle e-business suite and Oracle Fusion.

Previous post

ERP Overview
November 17, 2013

Next post

Profile Options in Oracle Apps
17 November, 2013

Leave A Reply Cancel reply

Your email address will not be published. Required fields are marked *

Search

Categories

  • Blog
  • Fusion HCM
  • Oracle ebusiness Suite
  • Oracle Financial
  • Oracle Fusion
  • Oracle HCM
  • Oracle SCM

Latest Courses

R12.x Oracle E-Business Suite Essentials for Implementers

R12.x Oracle E-Business Suite Essentials for Implementers

Free
R12.x Oracle HRMS Work Structures Fundamentals

R12.x Oracle HRMS Work Structures Fundamentals

Free
R12.x Oracle Payroll Fundamentals

R12.x Oracle Payroll Fundamentals

Free
AppsLead | Learn Oracle From The Leaders

+2 0100 62 62 837

[email protected]

Company

  • About Us
  • Blog
  • Contact Us

Links

  • Events

Copyright © 2017 AppsLead, All rights reserved. Developed by ECDSCS Co.

  • Privacy
  • Terms
  • Sitemap