<Insert Picture Here> Umsetzung funktionaler Anforderungen durch Personalisierung in der Oracle E-Business Suite Fabian Aulkemeier Berater Applications Technology, Oracle Consulting 1
Personalization Agenda Outline Terminology Personalization Types Concepts Framework Architecture Personalization Capabilities Insight Profile Options Analyzing Pages Implementation Deployment <Insert Picture Here> Important Terminology Installation Moving E-Business Suite to host (operating) system Configuration Set customer specific parameters and information Personalization Making changes to forms/pages from within EBS Extension Making programmatic changes to forms/pages Customization Creating new pages/forms Deployment Moving Personalization, Extension or Customization to server 2
Personalization vs. Extension Done in Page? Special Tool? Programming? Personalization Yes No No Extension No Yes Yes Likely to Survive an Upgrade / Patch? Yes No Always use Personalization where possible Personalizations Types End User Personalizations No special authority needed Available on inquiry pages built to allow saved searches Can modify query criteria, display of results Administrator Personalizations Administrator must have profile options set to access the Administrator Personalization UI Can make changes for all OA Framework based pages 3
End User Personalizations End users can personalize inquiry pages using query regions to create specific views of data. Create and save a search Tailor table column titles Hide/show columns Reorder columns Add a data filter Change sorting order Users access the Personalization UI from Save View or Personalize button. A system administrator can seed user views and defaults. Example End User Personalizations 4
Page Personalizations Pages and Personalizations are getting stored in MDS Repository. Personalizations modify the user interface of a page. Personalizations are layered on top of the base page at runtime. Base product pages are not changed. MDS Repository Personalization Personalization Definition Personalization Definition Definition Base Product Page Definition Multilayered User Interface Personalizations can be turned on and off easily Personalizations survive upgrades/patches 5
Framework Architecture User Interface: Pages, Regions and Items A page is a location a user can navigate to from a menu, tab, or another page. A page provides a specific piece of functionality. An administrator can create Personalizations at the page level. A region is a specific part of a page. Arranged hierarchically (regions within a region, within a region, ). An administrator can create Personalizations at the region level. An end user can create Personalizations for specific regions (for inquiry pages if enabled). An item is a field, button, poplist, or other user interface widget. Items must be contained in a region. An administrator can personalize almost all items. An end user can personalize items in specific regions (for inquiry pages if enabled). 6
User Interface: Object Hierarchy Page Item Region Region Item Administrator Personalization Capabilities Tailor text for labels, prompts and tip messages Tailor graphs and charts Hide/show components Reorder components Add new components Restrict query results Seed end-user views 7
Step 1: Profile Options Personalize Self-Service Defn Personalize Region Link Enabled FND: Diagnostics Functional Administrator Create, Review, Import/Export Personalizations 8
Step 2: Analysis Use the About this Page feature to analyze: Existing Personalizations Regions in the page View Objects (underlying data sources) used in the page Menu and function structures used for navigation to the page Current settings of commonly-used profile options Flexfields available in the page And much more Use the Personalization UI to analyze existing Personalizations About this Page Subtabs provide different information 9
Step 3: Navigate to Page and Start Personalizing Personalization UI The hierarchical grid is an abstraction of the OAF based page. Each indent level in the hierarchy represents a container region. Each leaf node is an item (field or widget). 10
Choosing the Personalization Context Scope Page: Any shared regions are only changed for that page (single instance scope). Shared Region: Personalization apply for any page using that shared region (assuming the personalization context is valid). Personalization Levels Function Location Site Organization Responsibility Implement Changes Reorder Objects Change order how objects are displayed on the page Change Object Properties Properties depend on object style Set values for different levels Fixed values, inherit or dynamic properties Create and Delete Objects Adding new objects to regions Map object to existing View Object attributes 11
Advanced Personalization Features Descriptive Flexfields Enable existing Flexfields Add Flexfields declaratively if View Object contains data Extend View Object programmatically using substitution Add new Regions With existing content With new content Include URL Include own HTML code Reference external site Migrating Personalizations Set Profile Option for Import/Export path FND: Personalization Document Root Path Use Functional Administrator responsibility to export Personalizations to file system Move.xml file to Import/Export path on target server Use Functional Administrator responsibility to import Personalizations from file system 12
For More Information Oracle Application Framework Personalization Guide Oracle Application Framework Developers Guide Oracle Forums E-Business Suite OA Framework search.oracle.com or oracle.com 13