Oracle Applications Framework (OAF) Immersion Training Oracle E-Business Suite 11 i 10

1. Oracle Applications Framework (OAF)Immersion TrainingOracle E-Business Suite 11i10 July 14, 2004 Adam Naser Product Director OAF 510 BASED

2. Oracle Applications Framework • The development and deployment platform for HTML-based Oracle E-Business Suite Applications • 100% Java & XML J2EE based, middle-tier application framework and services for the rapid development & deployment of HTML based applications

3. Agenda • Demo • Key Features / Strengths • Roadmap to customizing OA Applications • Variables to consider • What do you get, how and when • Your Questions

4. Key Strengths / Selling Points • Customizability • Interactivity • Architecture

5. Architecture Overview • Declarative, MVC architecture A component-based design with clean interfaces among model, view, and controller objects The model encapsulates the underlying data and business logic of the application The controller responds to user actions and directs application flow Controller Model View The view formats and presents data from a model to the user Meta-data Flows UI Objects DB Objects

6. User Interface Interactivity • Interactivity of the user interface is necessary for end-user productivity. The OA Framework offers a set of competitive interactivity features: • Partial Page Rendering • Hot keys • Save Model • Smart Choice List • LOV Auto Completion

7. Configuration Personalization Extensibility Interoperability Customizability • SomeVariables • Durable • Rich • Quick

8. Customization Roadmap - (No.1 Choice) • (No.1 Choice)Configuration: • Deployment Configurations Setup Application Server parameters • Global Functionality Configurations Setup profiles, responsibilities, orgs, grants • Application Specific Chart of accounts, Employee benefits

9. Customization Roadmap - (No.2 Choice) • (No.2 Choice)Admin Personalizations: • Five Levels: Function, Locale, Site, Organization & Responsibility • Long list of things that you can do to change look and content of a page • Limitations are in the areas of radical change to look and layout beyond that can be accomplished via style sheets and reordering of children of a container

10. Customization Roadmap - (No.3 Choice) • (No.2 Choice)Extensibility: • Add new schema, business logic and user interface Add a flow to link Quoting to Contracts Build a new application around TCA • Add a new attribute and expose it to the UI Expose closest walk-in service place on order screen • Default attribute values Default payment terms based on customer profile • Validate attribute value(s) Validate that subscriber age is no less than 18

11. Customization Roadmap - (No.3 Choice) • (No.3 Choice)Extensibility - detailed: • Add new schema, business logic and user interface Supplement EBS with a new application module • Create a new APP ID • Create new JDeveloper OA Extension Project • Create database table or reuse an existing table • Create a middle-tier Entity Object or reuse an existing • Create a middle-tier View Object or reuse an existing • Create a middle-tier Application Module or reuse • Create a page/flow of pages • Link new page to existing application or new menu

12. Customization Roadmap - (No.3 Choice) • (No.3 Choice)Extensibility - detailed: • Add a new attribute and expose it to the UI Expose closest walk-in service place on order screen • Create new database table or reuse existing • Assemble a new JDeveloper OA Extension Project • Create middle-tier Entity Object or reuse existing • Extend middle-tier View Object • Create and deploy a substitution • Use Admin Personalization to expose new attribute on UI

13. Customization Roadmap - (No.3 Choice) • (No.3 Choice)Extensibility - detailed: • Default attribute values Simple & Local: Default payment terms to Net 60 on a particular page • Use Admin Personalization Simple & Global: Default payment terms to Net 60 on all uses if an EO • Assemble a new JDeveloper OA Extension Project • Extend middle-tier Entity Object • Set default using BC4J Wizard • Create and deploy a substitution

14. Customization Roadmap - (No.3 Choice) • (No.3 Choice)Extensibility - detailed: • Default attribute values (cntd) Calculated: Default payment terms based on customer profile • Assemble a new JDeveloper OA Extension Project • Extend middle-tier Entity Object • Add code to EO Create method to set default value • Create and deploy a substitution

15. Customization Roadmap - (No.3 Choice) • (No.3 Choice)Extensibility - detailed: • Validate attribute value(s) Simple Attribute Level: Validate that subscriber age is no less than 18 • Assemble a new JDeveloper OA Extension Project • Extend middle-tier Entity Object • Set attribute validation using BC4J Wizard • Create and deploy a substitution Calculated Attribute Level: Validate that new hire salary is within job level salary band • Same as above, except for adding validation code in the set<attribute> method rather than using the BC4J Wizard

16. Customization Roadmap - (No.3 Choice) • (No.3 Choice)Extensibility - detailed: • Validate attribute value(s) (cntd) Cross Attributes: Validate that subscriber age is no less than 18 if her place of residence is in the USA • Assemble a new JDeveloper OA Extension Project • Extend middle-tier Entity Object • Add validation code to validateEntity method • Create and deploy a substitution Cross Entities: Validate that credit sale on shopping cart doesn’t exceed buyers credit limit • Same as above, except for adding validation code in the View Object’s Validate method

17. Customization Roadmap-(Parallel Choice) • (Parallel Choice)Interoperability: • Deployment Wide Single Sign On, Security, Cross Tech Stack • Application Specific Oracle iPayment to Credit Processors • Function Specific APIs, Web Services, EDI, XML, …

18. Some Variables To Consider • Not all products are OA Framework based • Check the matrix maintained by Ops http://cosdev01.us.oracle.com/archive/ebizops/metrics/build/techstack/Latest_techstack_review.html Or of http://www-apps.us.oracle.com:1100/fwk/ marketing tab | availability

19. Some Variables To Consider • Not all features of OA are implemented equally in all applications • An understanding of OA helps you determine which features are transparent to all applications and which features require extra work from product team, hence you may encounter some variability

20. Some Variables To Consider • Some older product pages are partially built programmatically, which limits your ability to personalize such pages • Check with product team, especially for products that were first released before 11.5.9 • Personalization of some pages and regions may have been turned off by development • Inspect the personalization UI

21. Some Variables To Consider • Customizations involving a change to a flow as opposed to creating a new flow could be fragile and not supported • Editing an FND function definition is the safest option, that is if one exist • Extending Controllers is discouraged and not supported • 11.X introduces new declarative page flows and new controller implementation that is not backward compatible, but would provide for a durable and supported solution

22. Some Variables To Consider • Extending SQL based BC4J Objects can be fragile • Implement regression tests to validate extensions on a test environment across patches and upgrades • Not all product teams publish documentation on their BC4J Objects • Check with product teams on project by project basis

23. What do you get, how and when • OA Framework ARU • JDeveloper OA Extension ARU downloadable off metalink • Includes documentation and tutorials • Product ARUs • Includes: metadata, java classes and BC4J XML files • These are sufficient to assemble extensibility projects. • Until EBS11i10 goes production we’ll continue to support consulting led EAP projects and expand as we go

24. Your Questions?