1 / 25

The Power of Personalization in the E-Business Suite

The Power of Personalization in the E-Business Suite. Bob Brown Practice Director - CRM & Order Management February 22, 2008. A Long Awaited Capability …. For centuries, Oracle apps customers have wanted to Remove fields, buttons, tabs, etc. from the screen because they never use them

kylan-schultz
Download Presentation

The Power of Personalization in the E-Business Suite

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Power of Personalization in the E-Business Suite Bob Brown Practice Director - CRM & Order Management February 22, 2008

  2. A Long Awaited Capability … • For centuries, Oracle apps customers have wanted to • Remove fields, buttons, tabs, etc. from the screen because they never use them • Re-label fields, buttons, tips to match their terminology • Change the default value of fields • Allow easy access from one form to another, passing context • Do any of the above for only a particular user or responsibility • Do any of the above only if certain conditions are true. • Do all of the above without writing code, and without violating Support agreements • Folder technology introduced in 11i is great, but the Personalization capabilities deployed in 11i10 take folders to a new level

  3. Personalization Features • Allows you to make declarative changes to a form. • Changes are applied at runtime when the proper trigger event occurs. • Changes can get applied based on who you are and other conditions • You can: • Change object properties • Execute certain Forms built-ins • Display messages • Activate menu entries • Personalizations are a system-administration function

  4. Rule Structure • Personalizations consist of the following: • Description, and personalization level, e.g. Form or Function • Condition (when) • The triggering form event, and option form object • Additional condition(s) • Context (who) • Site • Responsibility • User • Actions (what) • The set of steps to perform when the personalization executes

  5. Rules and Conditions

  6. Rules and Conditions • Be careful when entering a new rule, and the default “Level” is Function • The same form launched from different places is a different function • Sales Order / Quick Sales Order form launched from the Navigator versus from the Organizer • Trigger Events • WHEN-NEW-FORM-INSTANCE : triggered when form is first opened • WHEN-NEW-BLOCK-INSTANCE : triggered when “focus” is set for a given block • WHEN-NEW-RECORD-INSTANCE : triggered when the cursor is placed on a record • WHEN-NEW-ITEM-INSTANCE : triggered when the cursor is placed in a displayed field • SPECIALx : used for adding to the Tools menu

  7. Actions

  8. Actions • “Property” allows you to alter the characteristics of objects in the form, e.g. • Make fields required that • Hide tab pages • Display formatting • “Message” allows you to display a message box to the user with static or variable text • “Builtin” allows some level of flow and navigation control: • Field navigation • Launching another form • Launching an SRS form • “Menu” is for defining additional Tools options

  9. Actions - Property

  10. Actions - Builtin

  11. Case Study • Title insurance policy remittance, inventory, and receivables management implementation • Agent sells title policy at a “gross premium” • Agent keeps from a percent of the gross premium • Difference is owed to Title Insurance Company, and managed through Receivables • Order entry form must display • Gross premium • Gross premium override • Net premium (or net override) • Flexfields not acceptable for data entry of non-standard fields, e.g. Policy Liability Amount, Gross Premium Override • Data entry must support 10-key type entry

  12. Personalized Quick OE Form

  13. Personalized Quick OE Form • Liability Amount and Gross Override Fields are non-used form fields that we used to capture numeric information • “Liability Amount” is Customer Shipment Number • “Gross Override” is Customer Model Serial Number • “File Number” is Customer Line Number • Liability Amount personalization • Formatting upon cursor entry into “File Number” • Copy value to DFF • Gross Override personalization • Formatting upon cursor entry into “Net” field • Tools Option to show Remittance (order) totals

  14. Formatting

  15. Formatting

  16. Remittance Totals • Add new option to Tools Menu to view relevant totals • Personalization uses “unused” fields in the form to store data and then display

  17. Remittance Totals – Define Menu

  18. Remittance Totals - Execute

  19. Remittance Totals - Execute

  20. Remittance Totals - Execute

  21. Remittance Totals - Execute

  22. Other Uses of Personalization Field defaulting Data validation Report launching Script launching Customer selection in order entry by virtually any field Lessons Learned Personalize first, then folderize Test until you can’t test any more Be very careful when copying / altering fields in the form Trigger behavior is not always as expected, especially NEW-ITEM-INSTANCE triggers (make sure you test) Be aware of navigation restrictions Formatting Validation control Did I mention testing? Other Applications, Lessons Learned

  23. Questions

  24. DARC Presentations

More Related