r12 Apps Tech Rcd

RELEASE CONTENT DOCUMENT Release 12 Oracle Applications Technology Prepared by ATG Product Management

Last Updated: 05/02/2006

Version: 3.1

Copyright © 2006, Oracle. All rights reserved.

R12 Applications Technology Release Content Document, Rev. 1.0 ii

Table of Contents

1. Disclaimer 1

2. Introduction 2 2.1. Purpose of Document 2 2.2. Reference Documents 2

3. Technology Stack 3 3.1. Overview 3 3.2. Technology Components 3

4. Look and Feel – “Swan” User Interface 5 4.1. Overview 5 4.2. Features 5

4.2.1. OAF/JTT Applications 5 4.2.2. Forms Applications 6

5. Application Object Library 7 5.1. Overview 7 5.2. Identity Management Integration 7

5.2.1. Overview 7 5.2.2. Features 7

5.2.2.1. Revised Login and Change Password Pages 7 5.2.2.2. Synchronous LDAP User Provisioning 7 5.2.2.3. User Name Enhancements 7 5.2.2.4. New Deployment Scenarios 7 5.2.2.5. On Demand User Creation 7 5.2.2.6. SSO Hint Cookie 7 5.2.2.7. Automatic Linking of User Accounts 8 5.2.2.8. Password Validation against Oracle Internet Directory 8 5.2.2.9. Mixed Case Passwords 8 5.2.2.10. Server-to-Server Authentication 8

5.3. Security 8 5.3.1. Overview 8 5.3.2. Features 8

5.3.2.1. Change Schema Passwords with Ease 8 5.3.2.2. Best Practices for Internet Exposure Certified 8 5.3.2.3. Security and Manageability Enhanced via New File System Layout 9 5.3.2.4. Updated Techstack Improves Security 9

5.4. Oracle User Management 9 5.4.1. Overview 9 5.4.2. Features 10

R12 Applications Technology Release Content Document, Rev. 1.0 iii

5.4.2.1. Proxy User 10 5.4.2.2. Integration with Oracle Internal Controls Manager 10 5.4.2.3. Registration Process Enhancements 10 5.4.2.4. User Name Policies 10 5.4.2.5. Security Wizards 10 5.4.2.6. Centralized Account Provisioning 10

5.5. Functional Administration 10 5.5.1. Overview 10 5.5.2. Features 11

5.5.2.1. Server-Responsibility Profile Hierarchy Type 11 5.5.2.2. Profile Categories 11 5.5.2.3. Java Cache Support 11 5.5.2.4. Automatic Menu Compilation 11 5.5.2.5. Flexfield Segment Additional Where Clause 11 5.5.2.6. PL/SQL and Key Flexfield Validated Value Sets 11

5.6. Concurrent Processing 11 5.6.1. Overview 11 5.6.2. Features 11

5.6.2.1. Multi-Org Support 11 5.6.2.2. Restarting a Request Set 12 5.6.2.3. Failover Sensitive Workshift 12 5.6.2.4. Oracle Applications Framework-Based Request Set Submission UI 12 5.6.2.5. Request Security Implemented with Roles (RBAC) 12 5.6.2.6. Transaction Manager Implementation with AQ 12

5.7. Oracle Applications Tablespace Model (OATM) 13 5.7.1. Overview 13 5.7.2. Features 13

5.7.2.1. Automatic Restart of the Generation of Migration Commands and Execution 13 5.7.2.2. Configurable Default Extent Size 13 5.7.2.3. New “Tools” Tablespace 13

5.8. Industry Terminology 13 5.8.1. Overview 13 5.8.2. Features 14

6. Oracle Application Framework 15 6.1. Oracle Application Framework 15


6.1.2.1. Service Interface 15 6.1.2.2. Service Tester 15 6.1.2.3. “Swan” User Interface 15 6.1.2.4. Oracle JDeveloper 10g Release 3 (10.1.3) 15 6.1.2.5. Personalization Administration 16 6.1.2.6. Improved About this Page Feature 16 6.1.2.7. Admin Personalization Usability Enhancements 16 6.1.2.8. Add More Types of Content to OA Framework Pages 16 6.1.2.9. Corporate Branding Image 17 6.1.2.10. Custom Look-and-Feel 17 6.1.2.11. Personalized SPEL Bindings 17 6.1.2.12. Read-only Required Items 17 6.1.2.13. Home Page Favorites 17 6.1.2.14. Configurable Start Page 17 6.1.2.15. Home Page Navigator Personalization 17 6.1.2.16. Attachment Security 17 6.1.2.17. Flexfield Enhancements 17 6.1.2.18. Support for WSRP Portal Integration Standard 18

R12 Applications Technology Release Content Document, Rev. 1.0 iv

7. Workflow, Messaging, and Integration 19 7.1. Oracle Workflow 19


7.1.2.1. Workflow Directory Service Bulk Synchronization 19 7.1.2.2. Worklist Flexfields 19 7.1.2.3. Digital Signatures 19 7.1.2.4. Notification Mailer 20 7.1.2.5. Workflow Engine 20 7.1.2.6. Business Event System 20

7.2. Integration 21 7.2.1. Overview 21 7.2.2. Features 21

7.2.2.1. Integration Repository 21 7.2.2.2. Web Service Provider 21 7.2.2.3. Oracle Application Server Adapter for Oracle Applications 21

8. System Management 23 8.1. Oracle Applications Manager and Grid Control Plug-in for Oracle E-Business Suite 23


8.1.2.1. Oracle Applications Manager Dashboard Enhancements 23 8.1.2.2. Oracle Applications Manager System Alert Infrastructure Enhancements 24 8.1.2.3. Patch Impact Analysis Enhancements 24 8.1.2.4. Grid Control Plug-in for Oracle E-Business Suite 24

9. Other Applications 26 9.1. Applications Installation and Configuration Management 26


9.1.2.1. Store Base Configuration in Oracle E-Business Suite Database 26 9.1.2.2. Multiple Domain Support for Database and Middle Tier in Rapid Install 26 9.1.2.3. Read-Only Shared File System Support 26 9.1.2.4. RAC Support in Rapid Clone 26

10. Oracle XML Publisher 27 10.1. Oracle XML Publisher 27


10.1.2.1. XML Data Extraction Engine 27 10.1.2.2. Translation Support 28 10.1.2.3. Desktop Tools 28 10.1.2.4. Administration User Interface 28 10.1.2.5. RTF Template Enhancements 28 10.1.2.6. Bulk Printing Solution 30 10.1.2.7. Inbound EFT Document Support 30 10.1.2.8. PDF Book Creation 31

11. Oracle Web Applications Desktop Integrator 32 11.1. ADI SDK 32


11.1.2.1. Netscape Support 33 11.1.2.2. Multiple Concurrent Program Submission 33 11.1.2.3. Create Document Parameters 33 11.1.2.4. Parameter Validation 34 11.1.2.5. Performance 34

R12 Applications Technology Release Content Document, Rev. 1.0 v

11.1.2.6. Viewer Flexfield Formatting 34 11.1.2.7. Duplicate Row Management 34 11.1.2.8. Generated Value Support for Lines Region 35 11.1.2.9. Variable Data Type Support 35 11.1.2.10. Filters 36 11.1.2.11. Flexfield As Parameter 36 11.1.2.12. Limit Display of Integrators and Viewers 36 11.1.2.13. Read-Only Regions 37 11.1.2.14. Content Download Support for Multiple Sheets 37 11.1.2.15. Formulas 38 11.1.2.16. Extensible Viewer Menus 38 11.1.2.17. Password As Parameter 38 11.1.2.18. Graph 39 11.1.2.19. Layout Definition Enhancements 39 11.1.2.20. Custom Session Configuration 40 11.1.2.21. Mapping Unique Values to IDs 40 11.1.2.22. Context-Based Layout Management 40

11.2. Solutions 41 11.2.1. Overview 41 11.2.2. Features 41

11.2.2.1. General Ledger - Journals 41 12. Oracle Report Manager 42 12.1. Oracle Report Manager 42


12.1.2.1. Submit, Publish, Present, and Display 42 12.1.2.2. User to Value Security 43 12.1.2.3. Financial Reports Template Editor 43 12.1.2.4. Repository Management 43 12.1.2.5. Migration 44

12.1.3. Terminology 44 13. Oracle iSetup 45 13.1. Oracle iSetup 45


13.1.2.1. Reporting Enhancements 45 13.1.2.2. Support for Additional APIs 45 13.1.2.3. New Selection Sets 46 13.1.2.4. Transformations Decoupled from the Load Process 46 13.1.2.5. Upload 46 13.1.2.6. UI Changes 46 13.1.2.7. Performance Improvements 46 13.1.2.8. Hierarchical Selection Sets 46

13.1.3. Terminology 46 14. Oracle Tutor 47 14.1. Oracle Tutor 47


14.1.2.1. Ability to Customize HTML documents 47 14.1.2.2. Ability to Customize Student Guides 48 14.1.2.3. Ability to Customize Online Desk Manuals 48 14.1.2.4. Ability to Customize Author Features 48 14.1.2.5. Support for Hosted Environments 48 14.1.2.6. Support for Server Version of Author 48

R12 Applications Technology Release Content Document, Rev. 1.0 1

1. Disclaimer

This Release Content Document (RCD) describes product features that are proposed for the specified release of the Oracle E-Business Suite. This document describes new or changed functionality only. Existing functionality from prior releases is not described. It is intended solely to help you assess the business benefits of upgrading to Release 12.

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Software License and Service Agreement, which has been executed and with with you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.

This document is for informational purposes only and is intended solely to assist you in planning for the implementation and upgrade of the product features described. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.

Due to the nature of the product architecture, it may not be possible to safely include all features described in this document without risking significant destabilization of the code.


2. Introduction

2.1. Purpose of Document

The Release Content Document (RCD), produced as part of Oracle’s Applications Product Lifecycle (APL), communicates information about new or changed functionality in the specified release of the Oracle E-Business Suite. Existing functionality from prior point releases is not described. However, content introduced by family packs, mini-packs or standalone patches since the prior point release is included in this document and denoted accordingly.

2.2. Reference Documents

Name Location Completion Date


3. Technology Stack

3.1. Overview

The technology stack for Release 12 takes advantage of the latest Oracle technologies for the database and application server tiers. Oracle E-Business Suite now leverages the latest database version, Oracle 10g. On the middle tier, Release 12 uses Oracle Application Server 10g and Oracle JDeveloper 10.1.3 for Web-based Framework applications. On the client, Oracle E-Business Suite uses Version 5.0 of the Sun Java Plug-in.

3.2. Technology Components

Oracle E-Business Suite uses the following major technology components in the Release 12 Rapid Install. Some of these components are installed in the ORACLE_HOME directories; other components are rehosted in the APPL_TOP.

Please refer to the R12 Technology Stack Summary spreadsheet for latest availability.

Oracle Technology R12 RI Version

Oracle Database 10g1 10.2 XDK – Database1 10.1.0.4 XDB1 10.1.0.4 XDK – Middle tier 10.1.3 Oracle HTTP Client 10.1.3 Oracle Application Server 10.1.2/10.1.3 Developer Client Libraries 10.1.0.4.2 Oracle Database iAS Client Libraries 10.1.0.4.2 Oracle HTTP Server 10.1.3 Oracle JDeveloper 10.1.3 OracleAS Discoverer 10g2 10.1.2.0.2 OJSP3 2.0

Technology – Rehosted components R12 Version

BI Beans 3.1 JDBC 10.2

Technology – Third party components R12 Version

1 10g Release1 (10.1.0.4) minimum is provided initially. The target is to upgrade to 10g Release 2 (10.2.0.x), based on availability. 2 10g Release 2 (10.1.2 phase 1) minimum. The target is to upgrade to 10g Release 2 (10.1.2 phase 2) based on availability. The Oracle E-Business Suite database continues to contain Oracle Discoverer EUL schemas. However, Rapid Install does not automatically deliver and install OracleAS Discoverer 10g Release 2 (10.1.2). Customers wishing to use OracleAS Discoverer 10g Release 2 (10.1.2) must obtain Oracle Application Server 10g Release 2 (10.1.2) and install Discoverer. The OracleMetaLink note for OracleAS Discoverer 10g Release 2 (10.1.2). certification will be updated to reflect the process and any Oracle E-Business Suite-specific steps. Also note that Oracle Discoverer 4i is installed with Oracle9i Application Server Release 1 (1.0.2.2) and as such remains present, but not used, in the Release 12 installation. 3 OJSP 2.0 is packaged in Oracle Application Server 10g Release 3 (10.1.3).


JDK for Web tier 5.0 JDK for concurrent processing tier 5.0 Sun Java Plug-in 5.0

Oracle Technology – non-embedded Applications integration

R12 Version

OracleAS 10g Portal4 10.1.4 OracleAS 10g Single Sign-On/Oracle Internet Directory3

10.1.2.0.2

Oracle Collaboration Suite5 10g Release 1 Oracle Enterprise Manager6 10g Release 1

(minimum; under discussion)

4 Rapid Install does not automatically install or configure this component. Customers wishing to use this technology must to obtain and install Oracle Application Server 10g. OracleMetaLink notes for the uptake of these technologies will be updated to reflect this process and any Oracle E-Business Suite-specific steps. 5The initial version of Oracle Collaboration Suite (OCS) is 10g Release 1 (10.1.1). Oracle Product Lifecycle Management has specified a dependency on 10g Release 2 which in turn depends on Oracle Internet Directory 10g Release 2 (10.1.2 Phase 2). This version of Oracle Internet Directory is not available until later in the Release12 development cycle. Rapid Install does not automatically install or configure this component. Customers wishing to use this technology must obtain and install Oracle Application Server 10g. OracleMetaLink notes for the uptake of these technologies will be updated to reflect this process and any Oracle E-Business Suite-specific steps. 6 10g Release 1at minimum; under discussion.


4. Look and Feel – “Swan” User Interface

4.1. Overview

The new “Swan” user interface (UI) greatly improves the look and feel of the Oracle E-Business Suite, significantly enhancing usability and productivity. The “Swan” UI brings together some of the best UI concepts from Oracle E-Business Suite, PeopleSoft, and JD Edwards applications.

4.2. Features

The “Swan” user interface is a subclass of Browser Look and Feel (BLAF), and replaces the former look and feel. Oracle E-Business Suite will use only the “Swan” look and feel for Release 12.

This new look and feel applies to the whole Oracle E-Business Suite as follows.

4.2.1. OAF/JTT Applications

As the relevant changes are made in the underlying technology layer, most products will not require any direct changes to be made. However, the changes to font size and field spacing may require some products to make a small number of minor changes.

The changes made at the technology layer for OAF and JTT products can be summarized as follows:

• The overall color usage has been changed to a more contemporary and compelling color scheme, which reduces eyestrain and provides a more pleasant look and feel.

• A new login screen complements the updates to the overall look and feel.

• The base font has been changed to Tahoma 9pt to make better use of available screen area.

• All buttons and tabs now have a gradient background, to increase their visibility on the screen as clickable elements.

• The button text and overall shape have been modified to reduce amount of space required for their display.

• Buttons are now standard HTML buttons instead of images, which required a display server to be set up.

• Background colors of page elements have been modified for better visual separation of screen elements.

• The entire icon suite has been upgraded to a more sophisticated style that integrates visually with the overall interface design.

• Tables and other containers have been modified to read well as distinct components.


• The page footer background has been changed to make it more readily distinguishable from other page elements.

• The Navigator has been restyled to be consistent with the other UI changes.

• Page tabs have been moved to the left side of the screen for better scanning and a clearer relationship with associated subtabs.

4.2.2. Forms Applications

The Forms color scheme has been changed to be consistent with the OAF/JTT products. Field values have been changed to normal weight, providing further consistency between products, and reducing the visual complexity of application screens.

As noted previously for OAF/JTT products, these changes have been made in the technology layer; no changes need to be made to individual products. No changes are made to the position or layout of any fields within Forms.


5. Application Object Library

5.1. Overview

The Oracle Application Object Library (AOL) provides Oracle E-Business Suite with a robust infrastructure for security, application administration, and configuration.

5.2. Identity Management Integration

5.2.1. Overview

Oracle Identity Management integration has been enhanced to improve usability and administration.

5.2.2. Features

5.2.2.1. Revised Login and Change Password Pages

The UI for the Applications Login and Change Password pages has been revised, and now allows customizations.

5.2.2.2. Synchronous LDAP User Provisioning

All user provisioning operations from Oracle E-Business Suite to Oracle Internet Directory are now done synchronously.

5.2.2.3. User Name Enhancements

User name changes in Oracle E-Business Suite are automatically synchronized to Oracle Internet Directory. Improved validation prevents the use of forbidden special characters.

5.2.2.4. New Deployment Scenarios

Oracle E-Business Suite now supports deployments with lopsided user populations, that is, scenarios where all user identities are stored in the corporate LDAP server, and only a subset of those are provisioned into Oracle E-Business Suite. Provisioning into Oracle E-Business Suite can be done via the new on demand user creation feature, the new automatic user account linking feature, unidirectional provisioning from Oracle E-Business Suite to Oracle Internet Directory, or some other custom-defined process.

5.2.2.5. On Demand User Creation

A user may be present in Oracle Internet Directory without a corresponding linked user account in Oracle E-Business Suite. Oracle Application Object Library now supports a mode in which an Oracle E-Business Suite user account is automatically created for SSO authenticated users when they first visit a page in Oracle E-Business Suite.

5.2.2.6. SSO Hint Cookie

The SSO Hint cookie provides a hint that a user may be authenticated via some other partner application. Based on this hint, Oracle E-Business Suite attempts to initiate an


authenticated Applications session instead of an anonymous guest session. Among other uses, this feature is used to trigger on demand user creation, and to ensure that public Oracle E-Business Suite pages correctly display personalized content.

5.2.2.7. Automatic Linking of User Accounts

Oracle E-Business Suite now supports a mode in which new user accounts created in Oracle E-Business Suite are automatically linked to existing accounts with the same user name in Oracle Internet Directory.

5.2.2.8. Password Validation against Oracle Internet Directory

The Oracle E-Business Suite login page can now authenticate a user, even if the password is stored externally in Oracle Internet Directory. This feature allows users to connect with a variety of clients which previously required passwords to be stored locally in Oracle E-Business Suite.

5.2.2.9. Mixed Case Passwords

Oracle E-Business Suite now supports case-sensitive passwords. For backward compatibility, a mix of case-sensitive and case-insensitive user passwords is supported.

5.2.2.10. Server-to-Server Authentication

Server-to-server authentication allows Oracle E-Business Suite products to integrate with Oracle Collaboration Suite components such as Oracle Files.

5.3. Security

5.3.1. Overview

The following security features are either new with Release 12 or introduced since the release of 11.5.10.

5.3.2. Features

5.3.2.1. Change Schema Passwords with Ease

A single command line invocation of FNDCPASS changes the password for all Oracle E-Business Suite base product schemas, which number approximately 200.

This feature was made available with Oracle Applications Technology 11i.ATG_PF.H Rollup 3 and with Oracle Critical Patch Update - January 2006.

In Release 12 the base product schemas are locked except during patching.

5.3.2.2. Best Practices for Internet Exposure Certified

Oracle E-Business Suite now has documented and certified best practices for exposing parts of the Suite to external parties via the Internet.

The certified configuration includes the following security-enhancing features:


• External Web tier: Separate from the internal application tier, the external Web tier only allows responsibilities configured as EXTERNAL to be assumed from the external Web tier.

• URL firewall: The URL firewall is a whitelist of URLs required for the certified external product or products. Any URL not on the whitelist cannot be invoked.

• mod_security: An apache module blocking obviously malicious requests.

• Reverse proxy: Reverse proxy can optionally be used for additional separation and deployment in the dirty DMZ.

The best practices for external deployment can be found in OracleMetaLink note 287176.1, "Oracle E-Business Suite 11i Configuration in a DMZ".

5.3.2.3. Security and Manageability Enhanced via New File System Layout

In Release 12, the Oracle E-Business Suite files are separated into directories according to best practice. Code trees are now free from configuration and log (output) files and can be mounted read-only at runtime (that is, outside of patching periods).

The read-only nature of the file system makes it easier to share a code tree between environments for development or load balancing purposes. It also facilitates compliance checking, by showing auditors that the code can only change during maintenance windows.

For a detailed description of this new feature, see “Read Only Shared File System Support”.

5.3.2.4. Updated Techstack Improves Security

The new technology stack introduced in Release12 enables faster production of patches to address any security issues that may arise, and also reduces the time required to address backport requests.

Additionally, the retirement of older and redundant technologies such as mod_plsql reduces vulnerability of the system to attackers.

5.4. Oracle User Management

5.4.1. Overview

Oracle User Management, introduced in Release 11.5.10, is a secure and scalable system that enables organizations to define administrative functions and manage users on the basis of specifications such as job role or geographic location.

Enhancements to User Management in Release 12 reduce the overall cost of ownership and improve the end user administrative experience.

Oracle User Management depends on the following products:

• Oracle Internet Directory

• Oracle Application Object Library

• Oracle Internal Controls Manager


• Oracle Workflow

5.4.2. Features

5.4.2.1. Proxy User

Oracle E-Business Suite now allows a user to specify a proxy who can act on their behalf. For example, an executive can designate an assistant as a proxy, allowing that assistant to create, edit or approve transactions on behalf of that executive.

5.4.2.2. Integration with Oracle Internal Controls Manager

Integration with Oracle Internal Controls Manager facilitates enforcement of constraints used for preventative separation of duties, reducing the possibility of error or fraud by ensuring that a single individual does not perform all the duties associated with a key business process or financial transaction.

5.4.2.3. Registration Process Enhancements

The Oracle User Management registration process functionality is enhanced to support the following features:

• Registration processes for administrative actions (role assignment) can be defined separately from policies relating to self-service requests.

• Specific business events or business logic can be invoked for each registration process, as required.

5.4.2.4. User Name Policies

User name format policies can be specified as required, based for example on:

• Email addresses

• User-defined user names

• Custom policies

5.4.2.5. Security Wizards

To assist administrators in granting permissions to roles, support is now provided for invoking specialized function and data security wizards from the role administration screens in Oracle User Management.

5.4.2.6. Centralized Account Provisioning

Support is now provided for routing Oracle E-Business Suite self-service account requests through a single registration flow.

5.5. Functional Administration

5.5.1. Overview

Release 12 provides a rich new set of features for functional administrators through an HTML user interface.


5.5.2. Features

5.5.2.1. Server-Responsibility Profile Hierarchy Type

Profile option values can now be set for a combination of a server and a responsibility.

5.5.2.2. Profile Categories

Categories can be used to organize profile options, and to enforce data security by restricting the profile categories that users can view or update.

5.5.2.3. Java Cache Support

Changes in setup data are immediately visible in all Java Virtual Machines (JVMs) without those JVMs having to be restarted.

5.5.2.4. Automatic Menu Compilation

Menu compilation now takes place automatically. Consequently, the “Compile Function Security” concurrent program and corresponding adadmin option are no longer required, and have been removed.

5.5.2.5. Flexfield Segment Additional Where Clause

An additional WHERE clause can be attached to a flexfield segment to enforce extra validation on that segment beyond the value set.

5.5.2.6. PL/SQL and Key Flexfield Validated Value Sets

Two new flexfield value set types are introduced: PL/SQL validated value sets are validated via a PL/SQL procedure, and Key flexfield validated value sets can declaratively reference a key flexfield combination.

5.6. Concurrent Processing

5.6.1. Overview

Following are new features for Concurrent Processing in Release 12.

5.6.2. Features

5.6.2.1. Multi-Org Support

5.6.2.1.1. Multi-Org Access Control

In Release 12, Multi-Org Access Control (MOAC) allows a user to access data for different operating units (OUs) in a Multi-Org enabled instance without switching responsibilities. In transaction entry or inquiry user interfaces, a user can either choose an operating unit explicitly, or use another org-sensitive field to derive the operating unit context.


5.6.2.1.2. Concurrent Program Definition

The Define Concurrent Programs window is now MOAC-enabled. A new field, “Operating Unit Mode”, allows users to specify the category for a concurrent program. A new list of values allows users to select one of these modes: “Single OU Concurrent Program”, “Multiple OU Concurrent Program”, or none (a null or blank value). The default is null.

5.6.2.1.3. Standard Request Submission

The Standard Request Submission window now allows users to execute single-org and multi-org concurrent programs. For single-org concurrent programs of MOAC-enabled products, the OU field is displayed to the user. This field is populated with the value of the “MO: Default Operating Unit” profile option, provided the value is valid.

At submission time, the operating unit for single-org concurrent programs of MOAC-enabled products is captured and stored as part of the request context. At execution time, multi-org initialization sets the CLIENT_INFO org context according to the request’s captured context.

5.6.2.2. Restarting a Request Set

If a process in the middle of a request set fails, users can now fix the cause of the failure and restart the request set from that point. They do not need to run the remaining processes manually, or restart the entire request set.

Additionally, users can now put a running request set on hold, and later remove the hold.

5.6.2.3. Failover Sensitive Workshift

A system administrator can now specify how many processes of the service instance should run when a service instance fails over to another node in a Parallel Concurrent Processing (PCP) environment. This feature allows system administrators to control resource allocation, for example by specifying that fewer processes should run on the failover node than on the original node.

5.6.2.4. Oracle Applications Framework-Based Request Set Submission UI

An Oracle Applications Framework-based UI for request set submission is available in this release.

5.6.2.5. Request Security Implemented with Roles (RBAC)

Permissions to submit requests and monitor requests are now based on grants to roles or users. An administrator can grant groups of programs or request sets (grouped by request group) to a grantee (a role or user). This functionality allows administrators to provide more granular access control on programs and requests. Existing assignments of request security groups to a responsibility still work as well.

5.6.2.6. Transaction Manager Implementation with AQ

The Transaction Manager communication mechanism is implemented using Oracle Advanced Queuing (AQ). The AQ communication mechanism removes the requirement to set up transaction manager instances for each Real Application Clusters (RAC) instance. This feature allows system administrators to use Concurrent Processing node


failover functionality for Transaction Managers. A new profile option, Concurrent TM: Transport Type, has been introduced to specify that the communication mechanism should use DBMS_PIPES in a non-RAC environment.

5.7. Oracle Applications Tablespace Model (OATM)

5.7.1. Overview

The following new features are available with Release 12.

5.7.2. Features

5.7.2.1. Automatic Restart of the Generation of Migration Commands and Execution

This new feature eliminates manual steps by automating the migration process for those commands that previously required manual steps. This enhancement reduces the overall migration time and improves manageability.

5.7.2.2. Configurable Default Extent Size

This new feature allows you to specify the default extent size as part of the migration process. The initial default extent size is 128K; to minimize space management operations for large tablespaces, this can if desired be increased to either 1MB or 10MB.

5.7.2.3. New “Tools” Tablespace

This new feature improves manageability and performance by consolidating tools-related database schema objects into a single tablespace called “Tools”. The new tablespace includes the database schema objects for products and components such as Oracle Portal (Repository), Oracle Discoverer (EUL), Oracle Internet Directory (Repository), Oracle Application Server Single Sign-On.

5.8. Industry Terminology

5.8.1. Overview

Terminology overlays are now available for specific industries. These overlays cause certain terms to be replaced by industry-specific terminology for that industry. As an example, the retail market may require that the term "Building" be replaced with "Store".

Each instance of Oracle E-Business Suite can run in one industry at a time, by running an “activator” that replaces existing seed data and activates the data in the personalization tables.

Terminology overlays are planned for 47 industries.


5.8.2. Features

• Oracle Forms user interfaces are modified using Forms personalizations. Because this framework is heavily optimized, overhead running these personalizations is minimal.

• Oracle Application Framework user interfaces are modified using the Oracle Application Personalization Framework in the “verticalization” layer.

• Terminology changes are also applied to messages and lookups.

• Changes are not applied to seeded menus or to applications written on the JTT technology stack.


6. Oracle Application Framework

6.1. Oracle Application Framework

6.1.1. Overview

Following are the new features for the Oracle Application Framework. The service interface, service tester, ”Swan” user interface changes, and uptake of Oracle JDeveloper 10g Release 3 (10.1.3) are new for Release 12. All other features first appeared in a patch to Release 11.5.10, and are now included in the base version of Release 12.

6.1.2. Features

6.1.2.1. Service Interface

The service interface is a Java interface that is designed to support both web services and local Java APIs. The service interface provides consistent APIs and error handling behavior across the different application products. Included is support for the new Service Data Object standard to increase interoperability in a Service Oriented Architecture. Service data objects are used to represent business objects in a standardized manner. See the Oracle Integration Repository for more information on how to register and discover services, and optionally configure a service as a public Web service.

6.1.2.2. Service Tester

The service tester user interface is used to create unit and integration tests. The tests are recorded in documents as structured XML data. For integration testing, each test file can contain multiple test suites, and each test suite can have multiple test cases. As part of periodic system tests, service tests can be played back from either JDeveloper or from the operating system command line.

The service tester supports the following features:

• Field masking, so that variable data such as the current date does not cause a test failure

• Pipelining, where the output of one test is used as the input of a subsequent test

• An option to suppress the commit of test data

6.1.2.3. “Swan” User Interface

As stated in Section 4, the new “Swan” user interface (UI) greatly improves the look and feel of the Oracle E-Business Suite, significantly enhancing usability and productivity. The “Swan” UI brings together some of the best UI concepts from Oracle E-Business Suite, PeopleSoft, and JD Edwards applications. Oracle E-Business Suite will use only the “Swan” look and feel for Release 12.

6.1.2.4. Oracle JDeveloper 10g Release 3 (10.1.3)

Release 12 leverages Oracle JDeveloper 10g Release 3 (10.1.3). This release of JDeveloper is a J2EE development environment with end-to-end support for modeling,


developing, and debugging applications and Web services. Oracle JDeveloper 10g Release 3 (10.1.3) allows existing Oracle Application Framework applications and services to be extended, or entirely new applications and services to be built easily.

6.1.2.5. Personalization Administration

Release 12 extends the existing command line personalization import/export capabilities with HTML pages included in the Functional Administrator responsibility. The Personalization Document Manager feature also allows you to replicate personalizations across database instances.

6.1.2.6. Improved About this Page Feature

The About this Page feature has been extended to include the following:

• Last 10 patches applied on the instance

• Flexfield definitions on the page, and whether they use unsupported features specific to the Oracle Forms stack

• The ability to launch Admin Personalization from the About page

6.1.2.7. Admin Personalization Usability Enhancements

Usability enhancements include:

• Jump directly to the Personalization Hierarchy page, bypassing the Choose Context page when the current context is known. When you use the Personalize links, the context defaults to the page, function, and responsibility you were using.

• On the Personalization Hierarchy page, a new "Simple" page hierarchy makes it easier to get to the items to be personalized by hiding layout-only container regions. The "Complete" view of the personalization hierarchy structure allows you to see and personalize all the layers of regions and containers.

• Personalization-related error messages include a link to launch the “About this Page” feature, where the associated personalizations can be reviewed and edited. If you have a problem with a personalization you've created, you can easily get to the Manage Levels page to view, edit, or deactivate your personalization if necessary.

• A new UI for personalizing configurable pages separates layout and content into two separate tabs. This greatly simplifies the personalization experience for configurable pages such as the Sales Dashboard.

6.1.2.8. Add More Types of Content to OA Framework Pages

Admin Personalization now supports the inclusion of more types of content in OA Framework pages.

• Add new regions or extend existing regions into pages.

• Include external JSP or HTML regions in existing pages.


• More item styles are supported for creating new items.

6.1.2.9. Corporate Branding Image

Now you can change the corporate branding logo using a profile option: set the profile option "Corporate Branding Image for Oracle Applications" (FND_CORPORATE_BRANDING_IMAGE) to the name of an image file (GIF) that contains your corporate image.

6.1.2.10. Custom Look-and-Feel

Custom Look-and-Feel (CLAF) gives you the ability to create new looks and feels (skins) to match your organization's web UI standards. You can create a new look and feel (LAF) that makes your E-Business Suite applications look like your corporate web site.Personalized SPEL Bindings

SPEL (simple expression) bindings can be used to substitute or override the base SPEL bindings for rendered, required, and read-only properties.

6.1.2.12. Read-only Required Items

Mandatory fields can be marked as read-only to prevent users from editing fields during an update record flow.

6.1.2.13. Home Page Favorites

When users add or edit Favorites links on the Home Page, the enhanced personalization interface now allows users to search for functions (business flows), add a favorite, rename a favorite, and reorder favorites from within a single page.

6.1.2.14. Configurable Start Page

Users can now use the Preferences link to set the start page that displays after login. This feature lets users bypass the Home page and go directly to the specified page.

6.1.2.15. Home Page Navigator Personalization

The Navigator feature of the Home Page can now be personalized to hide or show any of the responsibilities for a user.

6.1.2.16. Attachment Security

Attachments can now be secured at the category level. You can now secure an attachment category to Application Security rules, such that specific categories of attachments may be restricted for use to users in a specific role.

6.1.2.17. Flexfield Enhancements

Flexfield errors are handled more gracefully. Warnings are raised at flexfield compile time if an OA Framework flexfield uses incompatible features used by flexfields in the Oracle Forms-based forms.


6.1.2.18. Support for WSRP Portal Integration Standard

Release 12 of OA Framework includes support for the WSRP standard, which allows integration of content from multiple vendors into portal pages. Now you can put E-Business Suite content into Oracle Portal or other vendors' portal products.


7. Workflow, Messaging, and Integration

7.1. Oracle Workflow

7.1.1. Overview

Oracle Workflow delivers a complete business process management system that supports business process definition, business process automation, and business process integration. Oracle Workflow enables modeling, automation, and continuous improvement of business processes, routing information of any type according to user defined business rules.

Oracle Workflow in Release 12 adds new and enhanced features to improve supportability and performance.

7.1.2. Features

7.1.2.1. Workflow Directory Service Bulk Synchronization

The Workflow directory service bulk synchronization concurrent program can now recreate a directory service partition that includes roles that are part of a role hierarchy. In Release 11.5.10, after a role was used in a role hierarchy it was no longer possible to resynchronize the partition with the source originating system in its entirety, although data was incrementally synchronized at real time.

7.1.2.2. Worklist Flexfields

Oracle E-Business Suite system administrators can now promote information stored in notification message attributes from the notification detail page to a personal worklist view for viewing and sorting. For example, a dollar amount can be published from the workflow message to a personal worklist view and then used for sorting. The personal worklist views can be assigned to a function and then assigned to a user or group of users.

New pages are added to configure this feature:

• Worklist Flexfield Rules: Setup page for creating rules to populate the worklist flexfield columns

• Worklist Flexfield Rules Simulation: Test page used to show the net effect of multiple worklist flexfield rules on the Worklist

7.1.2.3. Digital Signatures

The digital signature infrastructure now supports the following:

• Ability to digitally sign the entire notification contents, including subject, message body, response attributes, and response action

• Ability to verify the signed documents through an evidence store user interface after the signing process


• Enhancement of the notification purge program to exclude purging of signature-enabled notifications

7.1.2.4. Notification Mailer

The notification mailer now includes the following new and improved features:

• Simplified configuration: The notification mailer configuration wizard is now split into basic and advanced pages.

• Override address: The test address is set in a new Set Override Address page and requires a verification code to be entered before the notification mailer begins sending notifications to that address.

• Enhanced error handling for mass failures: In cases where many users have been set up with invalid email addresses, the workflow directory service is updated to no longer send e-mails to those users.

• System alerts integration: When the Workflow Mailer Service encounters errors, it sends a system alert to provide easy visibility to system administrators and applications DBAs as to the status of the Workflow Mailer Service without having to review log files.

• SSL Support: The Workflow Mailer Service can now connect to IMAP and SMTP mail servers a using SSL authentication.

7.1.2.5. Workflow Engine

The Workflow Engine now includes a bulk array interface for creating and starting processes. These bulk array interfaces offer significant performance improvements over the single work item APIs when starting many workflows at the same time, such as in a batch program.

7.1.2.6. Business Event System

The Business Event System (BES) now includes:

• Event and subscription caching at the PL/SQL layer: When a business event is raised, the Event Dispatcher queries a cache before running SQL on database tables to identify the corresponding event subscriptions in order to reduce SQL executions. This feature provides performance gains for event subscriptions processed within a single session, such as batch programs or high volume data entry scenarios.

• PL/SQL rule function optimization: PL/SQL packages are generated for all registered rule functions during installation. BES calls a generated PL/SQL package statically by passing the function name to be executed. This feature eliminates the overhead of the dynamic SQL used to call rule functions prior to Release 12.

• Declarative event subscription error handling: You can choose between the following “On Error” conditions when defining new subscriptions:

o Stop and Rollback: Stop processing any further subscriptions and roll back those that have already been executed.

o Skip to Next: Roll back only the errored subscription and then continue processing subsequent subscriptions.


7.2. Integration

7.2.1. Overview

Following are the integration features that are new in Release 12.

7.2.2. Features

7.2.2.1. Integration Repository

The Integration Repository is a comprehensive online directory of Web services, interfaces, and integration points that acts as the service broker for Oracle E-Business Suite. This directory functions as a catalog of all Oracle E-Business Suite integration points, including Web services, business-to-business (B2B) protocols, application programming interfaces (APIs), legacy integration technologies, and business events.

This complete, online catalog allows users to discover and deploy the appropriate business service interface for integration with any system, application, or business partner. The Integration Repository includes pages for searching and viewing all available integration points with just a Web browser.

This unified repository exposes the following interface types:

• Web services

• XML messages

• EDI transactions

• PL/SQL procedures

• Java APIs

• Open interface tables

• Database views

• Concurrent programs

• Service beans

• Service Data Objects

7.2.2.2. Web Service Provider

The Web Service Provider allows you to publish, test, and deploy Web services. Built on top of the Integration Repository, it is a comprehensive tool to browse candidate integration services and to deploy them as Web services.

7.2.2.3. Oracle Application Server Adapter for Oracle Applications

Oracle Application Server Adapter for Oracle Applications is a component of Fusion Middleware accessible through Oracle BPEL Process Manager. The adapter provides comprehensive, bidirectional, multimodal, and real-time connectivity to Oracle E-Business Suite.

OracleAS Adapter for Oracle Applications exposes the following technology interfaces:


• Interface tables: Enable data to be inserted into or updated in Oracle E-Business Suite. The associated concurrent program should be running, to move the data from the interface tables to base tables.

• Views: Help with retrieval of data from Oracle E-Business Suite.

• APIs: Enable data to be insert into and updated in Oracle E-Business Suite.

• Concurrent programs: Enable data to be moved from interface tables to base tables, as well as providing other application-specific program functionality.

• Oracle e-Commerce Gateway: Provides a common, standards-based approach for Electronic Data Interchange (EDI) integration between Oracle E-Business Suite and third party applications.

• Oracle XML Gateway: Enables bidirectional integration with Oracle E-Business Suite. This technology helps with insertion and retrieval of data from Oracle E-Business Suite. Oracle XML Gateway is a higher-level API, which exposes OAGIS (Open Applications Group Information System)-formatted XML documents for commonly used Oracle E-Business Suite business objects and business interfaces. Oracle XML Gateway integrates with interface tables, the Business Event System, and views to insert and retrieve data.

• Business events: The Business Event System plays a key role in making any Oracle E-Business Suite instance open and easy to integrate with other application systems. Oracle E-Business Suite now has more than 900 integration points exposed as business events.


8. System Management

8.1. Oracle Applications Manager and Grid Control Plug-in for Oracle E-Business Suite

8.1.1. Overview

Oracle Applications Manager and the Grid Control Plug-in for Oracle E-Business Suite offer an integrated set of features for Oracle E-Business Suite system management. The Grid Control Plug-in for Oracle E-Business Suite extends Oracle Enterprise Manager to provide central monitoring and cloning automation for Oracle E-Business Suite. The plug-in also links Grid Control with Oracle Applications Manager. Built directly into Oracle E-Business Suite, Oracle Applications Manager provides a broad array of features to facilitate system management and maintenance.

The Grid Control Plug-in for Oracle E-Business Suite requires Oracle Enterprise Manager Grid Control 10g Release 2 (10.2).

Application system alerts are exposed as business events. Summary and context information for each alert is available as the business event payload in XML form. This information can be retrieved via standard business event integration mechanisms.

Following are the features that are new with Release 12.

8.1.2. Features

8.1.2.1. Oracle Applications Manager Dashboard Enhancements

8.1.2.1.1. Performance

The enhanced Performance dashboard provides administrators with key performance metrics related to online, batch, and workflow activity. For customers using Oracle Real Application Clusters, the dashboard shows these metrics for each RAC instance. Additionally, system administrators can now subscribe to receive automated alerts when concurrent requests run longer or wait longer than specified thresholds.

8.1.2.1.2. Security

An updated suite of diagnostic reports is now available within the Security dashboard. These reports check the Oracle E-Business Suite system configuration against Oracle’s best practices and detect possible security violations. These reports provide diagnostic information related to possible security issues such as:

• Dictionary attacks • Duplicate logins • Direct access to unauthorized functions • WTI failures

8.1.2.1.3. Diagnostics

Oracle Applications Manager now allows administrators to schedule and run Diagnostics tests as batch programs. The Diagnostics dashboard provides new graphical views of


diagnostic test executions and failures. Keyword searches can be performed on the test repository to locate relevant tests, which can then be grouped and executed directly from the same interface.

8.1.2.2. Oracle Applications Manager System Alert Infrastructure Enhancements

The system alerting infrastructure has been enhanced with a new “flood control” mechanism to prevent multiple instances of a given alert from overwhelming the alert system. This mechanism provides administrators with configuration options to customize the limits on the number of system alerts and occurrences that are generated by any given issues. Additionally, alerts are enhanced to allow summary and context information to be retrieved in XML format via standard business event integration mechanisms.

8.1.2.3. Patch Impact Analysis Enhancements

Key patch impact analysis enhancements include the following:

• Analysis of patch changes to customized files that are registered with the system.

• The ability for users to create a list of patches for analysis as a single set.

• The ability to identify and to merge multiple language patches that are applicable to that system.

• Impact analysis now highlights patches that include branched files to help System Administrators identify files from a particular branch that are being overwritten by the same file in another branch or in the mainline.

8.1.2.4. Grid Control Plug-in for Oracle E-Business Suite

8.1.2.4.1. Seamless Integration with OAM

The Grid Control plug-in now provides a tighter integration with Oracle Applications Manager. Several Grid Control features link directly to OAM features such as concurrent manager administration, workflow administration, Forms monitoring, configuration management and patch management.

8.1.2.4.2. Automated Discovery of Oracle E-Business Suite System

Registration of Oracle E-Business Suite systems with Grid Control is greatly simplified in this release. For Oracle E-Business Suite systems that use AutoConfig, Grid Control now has the ability to automatically discover much of the information required to register those systems.

8.1.2.4.3. Topology Views

The Grid Control plug-in now provides service and system topology views for Oracle E-Business Suite. These views enable administrators to perform root cause analysis of system alerts.

8.1.2.4.4. Clone Automation

The Grid Control plug-in now allows Oracle E-Business Suite systems to be cloned via the Grid Control provisioning framework. A step-by-step interview guides administrators though the cloning process. Grid Control automates the creation of clone systems and


executes any required application-specific actions. Additionally, administrators can modify the standard cloning process to include custom actions.

8.1.2.4.5. Configuration Management

The plug-in provides administrators with the ability to collect, compare and search Oracle E-Business Suite configuration data. The following configuration data are collected from the application system and automatically uploaded to the Oracle Enterprise Manager repository:

• Application system summary

• Patches applied

• Application context files and key configuration files

• Technology stack inventory

• Concurrent processing configuration

• Workflow configuration

• User activity

• Custom configuration

Administrators can compare snapshots of configuration information across multiple Oracle E-Business Suite systems.

8.1.2.4.6. Application Service Level Management

The Grid Control plug-in automatically provides service level reporting for key Oracle E-Business Suite infrastructure services such as concurrent processing and Oracle Workflow. Service level alerts can be configured for key throughput and availability metrics.


9. Other Applications

9.1. Applications Installation and Configuration Management

9.1.1. Overview

Following are the features that are new with Release 12.

9.1.2. Features

9.1.2.1. Store Base Configuration in Oracle E-Business Suite Database

During the installation process, Rapid Install stores its configuration information in the Oracle E-Business Suite database instead of the configuration file (config.txt) that was used in previous releases. This feature eliminates the need to manually copy the configuration information from the first node to all subsequent nodes during a multi-node installation.

9.1.2.2. Multiple Domain Support for Database and Middle Tier in Rapid Install

Rapid Install supports deploying the database node and the middle tier node into different domains. This enhancement provides the ability to have more than one domain for an Oracle E-Business Suite installation.

9.1.2.3. Read-Only Shared File System Support

This feature allows the full Oracle E-Business Suite file system to be shared. APPL_TOP, COMMON_TOP, and technology stack ORACLE_HOMEs can be deployed on a read-only shared file system.

9.1.2.4. RAC Support in Rapid Clone

Support for Oracle Real Application Clusters and grid computing is added to Rapid Clone. RAC support is extended to support ASM as well as features to expand an existing RAC system by adding a node to an existing RAC cluster.


10. Oracle XML Publisher

10.1. Oracle XML Publisher

10.1.1. Overview

Oracle XML Publisher is a new Java-based product available within the technology stack of Oracle E-Business Suite. Utilizing a set of familiar desktop tools such as Adobe Acrobat and Microsoft Word, users can create and maintain their own report formats based on development delivered XML data extracts. Oracle XML Publisher then converts these documents to the XSL-FO format. Users can also obtain third party provided PDF forms, such as government tax forms, and merge XML data generated from Oracle E-Business Suite to fill the forms with the required data.

Note that the features listed in this document were introduced in the mid-cycle Oracle XML Publisher releases since Oracle E-Business Suite Release 11.5.10. Customers who have taken the Oracle XML Publisher releases (through Release 5.6.1) will already have been able to take advantage of these features.

10.1.2. Features

Oracle XML Publisher introduces rich and powerful features in Release 12. Advances in functionality and usability are made across all aspects of the product.

• The RTF template is enhanced to be richer and more robust in layout options and data manipulation.

• Administrative functions are simplified with a new user interface.

• A fast and scalable data engine now provides the ability to generate the XML data for your reports.

• Desktop tools are available to plug in to Microsoft Word to automate the RTF template design process and provide advanced preview capabilities.

• Translation support is added for RTF templates. Translatable strings can be extracted in a separate file, enabling multiple translations from one source layout template.

10.1.2.1. XML Data Extraction Engine

Oracle XML Publisher now supports data generation. The Oracle XML Publisher data engine enables you to rapidly generate any kind of XML data structure against one or multiple databases in a scalable, efficient manner. The data template is an XML document that you construct to communicate your request for data to the data engine. The data engine can be called to execute the data template using the Concurrent Manager or an API. The data engine supports schema generation, flexfields, single and multiple data queries, distributed queries against multiple databases, query links, parameters, multiple data groups, aggregate functions, and event triggers. The data engine can also generate a default RTF template.


10.1.2.2. Translation Support

The Oracle XML Publisher Template Manager now allows you to define a template as "translatable." When you define a template as translatable, Oracle XML Publisher extracts the translatable strings. You can then export the strings into an XLIFF (.xlf) file. This XLIFF file can then be sent to a translation provider, or using a text editor, you can enter the translation for each string. Upload the translated XLIFF file back to the Template Manager to make the translated template available at runtime.

10.1.2.3. Desktop Tools

The Template Builder for Word and the Template Viewer are two desktop tools that increase your productivity using Oracle XML Publisher. The Template Builder is tightly integrated with Microsoft Word to automate many RTF template design tasks. It allows you to:

• Insert data fields, tables, forms, and charts

• Browse and update the content of form fields

• Extract boilerplate text into an XLIFF translation file and test translations

The Template Viewer is a Java application that facilitates the rapid development of templates by providing advanced preview capabilities.

10.1.2.4. Administration User Interface

The XML Publisher Administrator responsibility now provides an administration interface. Using this interface you can set configuration properties, define font mappings, upload font files, and define currency formats. You can configure the behavior of Oracle XML Publisher at the site level, data definition level, and template level. Previously the properties available through this feature were configurable only through the Oracle XML Publisher configuration file, and only at the server level. For customers who have already configured their systems using the xdo.cfg file, a command line utility is available to migrate their existing settings to the database.

10.1.2.4.1. Upload Font Files and Create Font Mappings

You can now upload fonts through the administration interface to make them available to Oracle XML Publisher at runtime. You can also create font mappings to map fonts used in your template to other fonts to be published in PDF output. The mapping can be defined at the site level, the template level, or the data definition level.

10.1.2.4.2. Define Currency Formats

This feature allows you to map a number format mask to a specific currency so that your reports can display multiple currencies with their own corresponding formatting.

10.1.2.5. RTF Template Enhancements

This release provides new features in the area of graphics and conditional formatting in RTF templates.


10.1.2.5.1. Graphics Support

• Drawing/shape support: Users can now use Microsoft Word’s native support for predefined drawing objects and custom drawings. In addition, they can manipulate shapes by stretching, compressing, skewing, and repeating them in the final output based on XML data or parameters. This behavior can also be applied to composite shapes in the template.

• Background/watermark support: The native MS Word functionality to add backgrounds and watermarks, text or images is now supported.

• SVG image support: Users can now embed SVG images directly in the template.

• SVG chart output support: Charts generated in the template are now converted to the SVG format. This conversion improves both the chart image and supporting labels for the chart.

• Hyperlink support for shapes: You can add a hyperlink to a shape to enable users to click the image in the document and link to an internal or external destination. The link can be static or dynamically determined at runtime.

10.1.2.5.2. Conditional Formatting

• If construct: Rather than requiring the normal xsl:if statement, Oracle XML Publisher now supports the more familiar “if … then … else” construct.

• Fixed-row enumeration: Users can now specify a fixed number of rows for a table regardless of the amount of data coming into the template at runtime.

• Currency formatting: Numeric values can now be formatted according to their associated currency code.

10.1.2.5.3. Data Manipulation with an RTF Template

• Brought Forward/Carry Forward page totals: Used frequently in financial reporting, this feature allows you to calculate the page total for a given field, display it at the bottom of the page to be carried forward, and then display it at the top of the subsequent page as the brought forward total.

• Updateable variables: Updateable variables differ from standard XSL variables <xsl:variable> in that they are updateable during the template application to the XML data. This functionality allows you to create many new features in your templates that require updateable variables, such as a running total.

• Parameters: You can now declare parameters in your template and pass values at runtime.

10.1.2.5.4. Batch Processing Enhancements

This release provides better support for batch processing based on RTF templates by providing support for the following new features:

• Restart page numbering for section breaks: For example, if generating invoices for multiple customers, you can now restart the page numbering for each new invoice.


• Reset header and footer: Similarly, if header and footer data are being supplied from the data (such as customer name), they can be reset for each new invoice.

10.1.2.5.5. Number and Date Formatting

You can now use the Oracle number and date format masks to control the display of numbers and dates. The Oracle masks ensure that at runtime the appropriate locale-specific formatting is used. The Microsoft native formatting masks are also supported.

10.1.2.5.6. PDF Bookmark Support

Oracle XML Publisher can now generate the bookmark links that display in the PDF navigation pane. These links can either be static bookmarks or dynamic and based on the incoming data stream.

10.1.2.5.7. Support for Variable Page Layouts Within a Report

• Odd and even header and footer support: You can now define different headers and footers for odd and even pages in your output.

• Last-page-only content support: You can specify the layout and content of the last page of the report. This feature is useful for documents such as checks, invoices or purchase orders in which content such as the check or a summary must appear in a specific place only on the last page.

10.1.2.5.8. Truncate Table Data

You can now choose to truncate data in a table cell that is too big for the cell. Previously all data was wrapped.

10.1.2.5.9. Multicolumn Pages

Microsoft Word’s native multicolumn page function is now supported.

10.1.2.5.10. Initial Page Number

You can now define the page number from which you want the first page of a report to begin.

10.1.2.5.11. Check Boxes

You can now include a check box in your template that you define to display as checked or unchecked based on a value from the incoming data.

10.1.2.6. Bulk Printing Solution

The printing of large documents, such as those that are thousands of pages long, is problematic in Oracle E-Business Suite using regular printing functionality. This release provides the ability to split an incoming document into multiple print jobs that can be directed to the printer or printers, enabling load balancing across a set of printers.

10.1.2.7. Inbound EFT Document Support

Previous releases of Oracle XML Publisher provided the ability to generate Electronic Funds Transfer (EFT) formats using an RTF template to communicate payment requests


to a financial institution in an electronic format. This release builds on that functionality providing several enhancements. In addition, Oracle XML Publisher now has the ability to accept a remittance message from the financial institution in the electronic format and to generate XML data from the message for the calling application to update its reconciliation tables.

10.1.2.8. PDF Book Creation

This release delivers the ability to create merged PDF documents from multiple subdocuments based on a command file. Customers can now create master documents that contain the following features:

Table of contents: The table of contents can span multiple documents.

Bookmarks: This feature is the Adobe interpretation of bookmarks, that is, the links that appear on the left side of the document when opened in Adobe client software.

Master header/footer layouts: These layouts can support portrait and landscape page formats in the same document.

Section and master page numbering: Users can implement page numbering across the complete master document, or across a section made up of multiple subdocuments and numbering on the base documents.

Hyperlinks: The control file allows the user to build a set of cross-referencing hyperlinks within the master document and across multiple separate documents.

Preamble/postscript text: The user can add text prior to or after the insertion of a subdocument into the master document.

These features allow the user to build composite documents from subdocuments in a fast, scalable fashion.


11. Oracle Web Applications Desktop Integrator

The features described in this document are split into two groups because they target different audiences. The first group of features is added to the ADI Software Development Kit (SDK), and these are of interest to development staff that build Oracle Web ADI based solutions. The second group of features is added into solutions that are currently built by the Oracle Web ADI product development team and shipped in the Oracle Web ADI patchset. These solutions include Oracle General Ledger Journals and Budgets, and are of interest to users of the Oracle General Ledger product.

11.1. ADI SDK

11.1.1. Overview

Developers, including Oracle development teams, use the ADI SDK to create desktop application front-ends to their products. This technology provides you the ability to use desktop applications with which end users are already familiar, like Microsoft Excel, Microsoft Word, or Microsoft Project, , to download, model, modify, and upload Oracle E-Business Suite data. These activities can conform to applications business rules and standards. End users require only a browser and the desktop application.

The principal focus for this release is to build new features that support the creation of the General Ledger - Budgets, Fixed Assets - Mass Additions and Fixed Assets - Physical Inventory solutions. The creation of these solutions is part of the project to migrate the existing functionality in client/server ADI to the Web. The features required to create these solutions are multiple concurrent program submission, document parameter creation, parameter validation, duplicate row management, generated value support for lines region, filters, flexfields as parameters, read-only regions, content download support for multiple sheets, line totals, extensible viewer menus, password as content parameter, graph, additional content download, and conditionally required field validation.

Other features are also included in this release to improve client environment support, including Netscape support;, usability, including performance, flexfield formatting, and BLAF; administration, including integrator control settings, layout definition enhancements, and central logging; and data handling, including variable data type support.

Existing solutions built using the ADI SDK were taken into consideration during the design of these features. Developers uptaking this release do need to take any actions to have their solutions continue to operate after applying this release. In some cases enhancements automatically become available, Filters, for example, become available for the end user after the release is applied. This will be noted on a feature-by-feature basis below.

Support for document generation by users who use the Netscape Web browser on Microsoft Windows is added in this release.

Support for document generation on Apple Macintosh (using either the Internet Explorer or Netscape Web browser) is generally available in this release.


11.1.2. Features

11.1.2.1. Netscape Support

Oracle Web ADI previously supported only one browser for generating documents, Internet Explorer (IE). This release provides support for Netscape versions 4.7 or higher on Microsoft Windows.

The implementation of Netscape support slightly changes the page flow the user sees after clicking the create document button in the Create Document Page Flow.

Netscape support is available to all solutions and customers in this release. No action is required to enable this feature.

11.1.2.2. Multiple Concurrent Program Submission

Existing import functionality allows you to call a post-processing program to automate the next step after a successful upload. The post-processing program can either be a concurrent program or a PL/SQL API. The functionality is enabled by metadata which controls which program to call, the number of times to call the program based on the variation of data in the upload, and error handling.

Some solutions require the ability to call more than one post-processing program to complete the upload. To complete the Fixed Assets - Physical Inventory solution upload, the end user now has the option of running two concurrent programs. The first compares the inventory data with the actual data; the second prepares a report on the results of the comparison.

Developers implementing this feature define the metadata for calling and controlling the post-processing programs following a similar process to the existing definition of a single program. Control of the programs includes the definition of parent-child dependencies and providing end users control over which programs they want to run in the Upload form. The feature is designed as a new import type, so existing import implementations are not affected by this new function.

11.1.2.3. Create Document Parameters

During the creation of a document, a developer has a limited opportunity to query the user for information that is required to create the document. The developer has the option of passing in the parameter from the form or menu from which the flow is called, or asking questions for shaping the data that is downloaded to the document on the Content Parameters page.

The Create Document Page Flow is now enhanced for additional questions to be asked based on end user selections at runtime. The Fixed Assets - Create Assets solution implements this feature to have the user select which corporate depreciation book is to be used. Without this input, the sheet cannot be generated because the Accounting Flexfield Chart of Accounts is defined in the corporate depreciation book. With this feature defined, after selecting the Fixed Assets - Create Assets solution on the Integrator page and clicking Next, the user is asked to supply the value for the corporate depreciation book before moving on to selecting a layout. The value entered can also be used in functions outside the creation process, such as upload.

Developers can implement this feature for their Integrator, Viewer or seeded layouts in the same way they define the parameters for their content, that is, by assigning a list of


the parameters. Where there is no list assigned, the user navigates to the next standard page. After they are defined, the parameter values the user supplies in the flow can be used in any of the extensible or metadata defined options that are currently available to the developer.

11.1.2.4. Parameter Validation

Existing parameter list functionality allows developers to validate parameters against data in FND_LOOKUPS or against a value set defined in Oracle E-Business Suite. A list of values generated from either of these two sources can be displayed as a list box.

Parameter validation is enhanced to provide the same level of list of values and validation support as is available for the interface columns. Visual representation may be different. You can also now define two parameters as a range. This functionality improves the end user experience. All parameters can now be validated so that errors entered can be caught and dealt with at the time, rather than waiting for the desktop document to generate to discover that an invalid value was entered. For example, an invalid content parameter may cause no data to be downloaded.

Developers can implement this feature through the already provided mechanism for defining parameter lists. No changes are made to the existing mechanisms for lists of values or validation, so existing parameter definitions are not impacted.

11.1.2.5. Performance

This release includes the following enhancements: a cancel button in the download data flow to allow users to cancel the download process, several minor performance improvements such as compression of data to reduce the network overhead, and collection of performance-related statistics to assist in identifying bottleneck areas.

All these performance improvements are enabled for all solutions and customers. No action is required to take advantage of these features.

11.1.2.6. Viewer Flexfield Formatting

The definition of flexfield value sets provides the implementation team with some useful shortcuts that assist end users in performing data entry. This feature enhances the Oracle Web ADI flexfield form, requiring the end user to conform to these data entry rules: right-justify and zero pad, numeric only, uppercase only, and width. This feature enables the right-justify and zero pad setting to be overridden, and have this setting turned on for all segments of a particular flexfield or flexfield structure.

This functionality is available by default to any solution that has implemented flexfields. The enhancement to the flexfield form is controlled by the definition of the flexfield value sets. A system administrator is responsible for overriding the right-justify and zero pad setting, using a flow in self-service. When enabled, the setting automatically zero pads the values in the spreadsheet and in the flexfield form. When disabled, which is the default behavior, the setting is based on the value set definition.

11.1.2.7. Duplicate Row Management

Previously, Oracle Web ADI did not consider the handling of duplicate rows from successive uploads when inserting into a table. The workaround was to upload to a PL/SQL API that could detect an existing row in the table and perform an update instead of inserting a duplicate row.


Developers can now define the detection and resolution options for a table that can have duplicate rows, using metadata rather than having to develop a PL/SQL API. This feature reduces the time required to define a solution, and removes the need for PL/SQL programming to build the API.

Developers activate this feature by defining the columns in an interface that make up the logical key that are used to detect a duplicate row. This logical unique key does not necessarily map to a database unique index, but it may include a database unique index. Resolution actions are also defined in metadata. These actions can include whether to overwrite or update column values in the current row, fail the current row, or fail the entire upload. The end user can be presented with these options in the upload form for selection at runtime where required.

Existing solutions that upload to a table interface continue to function as usual, because the absence of a logical unique key prevents duplicate row management from being applied to such solutions.

The General Ledger - Budgets, Fixed Assets - Mass Additions and Fixed Assets - Physical Inventory solutions use duplicate row management.

11.1.2.8. Generated Value Support for Lines Region

Most solutions have a common requirement for the generation of values at upload time. The best example of this is the generation of values for the Standard Who set of columns, which are defined for most Oracle E-Business Suite tables for auditing purposes. Some interfaces extend this requirement, requiring values to be generated for each row. If end users must enter these values, they need training to enter the correct values. This enhancement addresses the need for system-generated values that are unique for every row uploaded into an interface.

Developers encountering this need in their solutions can define columns whose values can be derived from a database sequence, serialized list or Java code. This functionality is enabled through an extension of the existing method used to define default value generation. The column selected to use this method of value generation must not be displayed in the document. If a developer defines the column to generate a new value for each row, and also to be displayed, the column is not displayed in the document.

Saved documents that are in use and that have a column that is redefined to use this feature continue to work in this release. The server-side code does not override any values uploaded from the saved sheet, but if no value is uploaded, then a value will be generated.

The Fixed Assets - Physical Inventory solution uses this feature to generate a unique sequence ID for one of the columns in the upload to its interface table.

11.1.2.9. Variable Data Type Support

Some solutions have business rules that allow for the data type of the value entered in the spreadsheet to be different than the data type that needs to be used when uploading to the interface. This feature provides a framework for supporting this scenario.

To implement this feature, developers write Java code to support the logic that detects and handles a column that may need to change its data type during upload.


The General Ledger - Journals solution implements this feature. This solution has a column in its interface defined as VARCHAR2. Depending on environment and user-selected values, the value for this column can either be the name of a period or a date. If the value is a date, the upload must correctly identify the data type and convert the date value into a string formatted using the database date format.

11.1.2.10. Filters

Microsoft Excel provides filtering technology as part of its standard feature set. This functionality could formerly be implemented on worksheets only by experienced Excel users. This feature provides this functionality to all end users, turning the filter functionality on for the lines region of the document. The feature is accessed through the Oracle menu, providing an end user with the ability to turn filtering on, reset the filter criteria, and turn filtering off.

This feature is enabled automatically for all solutions that create documents in Microsoft Excel. Developers can disable the feature by setting a flag against the Integrator definition. You can also disable the functionality through the layout definition.

11.1.2.11. Flexfield As Parameter

Parameter lists exist in Oracle Web ADI as a way of defining lists of data “parameters” in metadata that may be used for a number of different purposes. Oracle Web ADI supports the parameter types String, Date, Number, and Boolean. This feature adds Key Flexfields to this list, both as an individual parameter and as a parameter range, providing developers the flexibility to use flexfields as part of the Oracle Web ADI page flows.

Developers define a parameter as a key flexfield using metadata, assigning attributes that provide the information for retrieving the correct flexfield structure.

This new type of parameter is initially required for the Content parameter list in the General Ledger - Budgets and General Ledger - Daily Rates solutions.

11.1.2.12. Limit Display of Integrators and Viewers

This feature enhances the Create Document Page Flow in three ways: displaying the list of available integrators based on form function security, letting you hide integrators in the Create Document Page Flow, and associating viewers with integrators.

In Release11.5.10 the number of solutions being shipped increased to over 100, creating an impressive list to choose from on the Integrator page of the Create Document Page Flow. Optionally, parameters can be included to specify which integrators should be displayed. Release 11.5.10 also introduced the association of form functions with solutions by the developer. Using this known relationship, the list of solutions displayed on the Integrator page is now determined by whether the form function is present in the current responsibility.

Some solutions need to be accessed only through their product’s existing flows, which perform additional processing before passing parameters to the Create Document Page Flow. Attempts to use the solution directly through the Create Document Page Flow instead of the product flow result in an incomplete document. The ability to show or hide solutions prevents such solutions from being displayed in the Create Document Page Flow. Solutions are displayed by default but can be hidden by a flag set against the Integrator.


Oracle Web ADI currently supports three desktop applications: Microsoft Excel, Microsoft Word and Microsoft Project. While most solutions are developed for only one of these three applications, the Create Document Page Flow formerly did not prevent end users from choosing one of the other two applications instead. Developers can now define the relationships between solutions and desktop applications to provide a list of valid choices to the end user at runtime. If no relationships are defined, all desktop applications are displayed. This feature requires a change in the order of the Create Document Page Flow. The Integrator page is now displayed first, followed by the Viewer page. Users first choose what work they want to do, selecting the Integrator, and then which desktop application the work will be performed in.

11.1.2.13. Read-Only Regions

In a document, solutions require the ability to display data that is required for processing and providing the end user with context, without letting the end user modify this data. This requirement is addressed with read-only regions. These read-only regions are protected from modification by end users. Attempts to change the data in these regions result in error messages indicating that users cannot edit this data. To prevent accidental attempts at editing, these regions are differentiated from data entry regions by a different format, namely, a gray background.

Developers can implement read-only regions in two ways. If a column or parameter in an interface needs to be displayed without editing, the column can be flagged as read-only in metadata. If data rows need to be displayed without editing, flags can be introduced into the result set. Stored and passed SQL content is enhanced with a reserved column that can return a flag for the rows that are read-only. Java content is enhanced to include additional business rules to detect the conditions required for a read-only row and declare that row as read-only in the download data. Columns can also be declared as read-only using Java content.

11.1.2.14. Content Download Support for Multiple Sheets

This functionality lets you download data across multiple sheets and continue downloading data into the next worksheet after the current worksheet runs out of rows. All sheets are formatted using the instructions from the layout selected for the first sheet. Similarly, the upload includes the data from all sheets, not just the current sheet. The breaking up of data is controlled via Java or metadata against the content. This feature is supported for stored SQL, passed SQL, and text import.

Oracle Project Accounting implements budgeting functionality in which all the data can be generated into one worksheet, or with the data grouped into separate worksheets by category, such as department. Developers can define the categories in metadata or give end users the option of entering their own categories on the Content Parameters page.

Downloading data to multiple sheets is also designed to facilitate comparing data sets. In the General Ledger - Budget solution, the download can bring down budget data for editing and actuals data for comparison. A parameter selected by the end user at runtime determines whether to download the actuals data as well. The Java content constructs the download document with the flags to indicate where a new sheet is to be started.

The download functionality is enhanced to detect when the worksheet can no longer hold any more rows, create another sheet, and continue downloading the data into that sheet. Microsoft Excel worksheets have a maximum row limit of 65,536 rows. Although this limit is large, the data stored in Oracle E-Business Suite tables may exceed it. Oracle’s own production instance contains over a million General Ledger Accounting Key


Flexfield code combinations. This functionality is automatically enabled for any solution downloading data into Microsoft Excel.

11.1.2.15. Formulas

Using existing functionality, a developer can flag columns in metadata so that when the document is generated a formula is placed into a total line at the bottom of the lines region to sum all of the values in the column. Some solutions need to provide users with a total column to display the sum of values in a row.

Using the default value in the layout definition page to generate formulas into the sheet, is problematic because the values may not handle the inclusion of a new column into the sheet.

In this release, developers and end users continue to use default values to define their formulas. Developers now also have the option of defining the default value against the interface column so that the formula applies to all layouts that include that column. A new default value type identifies when the entered default value is a formula. The entered formulas reference the columns by their interface column names rather than the Microsoft Excel cell references; the columns are converted into the correct references at sheet creation time, when the actual column location is known. Any valid Microsoft Excel formula can be used in the default value.

Oracle General Ledger and Oracle Project Accounting are introducing solutions using the formulas feature.

11.1.2.16. Extensible Viewer Menus

Some solutions have business needs in the desktop application that cannot be met generically. This functionality allows developers to build their own code which is generated into the desktop application when a document is created, with the option of providing a menu item in the spreadsheet’s Oracle menu to launch their solution-specific functionality. This feature can be used to improve the efficiency of end user tasks by automating activities.

Developers build the VBA code using the existing libraries provided by the platform or by uploading code that has been built on the desktop. Note that code built using the libraries can have any message or UI values automatically translated, while uploaded code cannot. After the code is built and uploaded, it is associated with a solution, and a menu item can be defined to call the code.

The General Ledger - Budgets solution implements this functionality, providing end users with the budget notes and insert new account features.

The menu definition functionality can also be used for calling form functions, URLs, or servlets, allowing end users to continue their workflow without having to return to the self-service window. The functionality is defined by the developer using metadata, and provides the option of displaying the page either in an embedded form within the desktop application or in a browser window.

11.1.2.17. Password As Parameter

Some solutions include additional password protection on top of the existing Oracle E-Business Suite account. This enhancement lets solutions prompt users for a password and validate the password, as part of the Create Document Page Flow. This feature also


includes appropriate error handling for invalid passwords ensuring that passwords are not saved or cached anywhere, prompting for the password again on subsequent downloads, and ignoring passwords passed in when calling the Create Document Page Flow.

To enable this feature, a developer builds Java code that performs the validation check, and then associates this Java code with the password parameter in the parameter list. Failure to enter the correct value prevents the user from moving past that page. Metadata defined for the parameter prevents the value entered from being displayed or saved.

The General Ledger - Budget solution, which is being migrated from client/server ADI to Oracle Web ADI, implements this enhancement. The budgeting function within Oracle General Ledger provides for budget data to be secured by a password protecting a budget organization.

11.1.2.18. Graph

Existing Oracle Web ADI functionality lets users graph data in an Excel spreadsheet through the Chart Wizard function. Depending on the data range being graphed, these graphs may require additional formatting to be presentable to others not familiar with the data. For example, depending on the range of data selected, correct labels may need to be added to make the graph meaningful.

This feature uses the information defined for the solution to correctly format the chart. When graph support is used in conjunction with the “Content Download Support for Multiple Sheets” feature, two sets of data can be automatically generated into the same graph. The General Ledger - Budgets solution provides end users the ability to graph the budgets and actuals data downloaded into separate worksheets in the same graph. This process is time -consuming when performed manually, but can be quickly performed using Oracle Web ADI.

Developers enable graphs for a solution and define the properties of the graph using metadata such as titles, axes names, and labels. The creation of a graph is initiated by an end user. After an Excel worksheet is created for a graph-enabled solution, the option to create a graph appears in the Oracle menu. When a user selects this menu option a default graph is generated in a separate worksheet. Another menu option allows the properties of the graph, such as the chart type, to be modified where required.

Layouts can also be defined to create the graphs automatically when a document is created. A layout includes the definition to create the graph, as well as some basic properties of the graph, such as the chart type.

11.1.2.19. Layout Definition Enhancements

The layout definition functionality provides control over which fields of a solution are displayed in the documents created, providing documents that contain only the fields that are relevant to the task that end users perform. Enhancements for the layout definition flow include the ability to:

• Modify the default display order of fields.

• Define the width for fields that are placed in the lines region, or hide a column by setting its width to zero.

• Display the header level fields in multiple columns to reduce the number of rows used by the header.


• Control the width of fields in the header level.

• Select which columns to continue displaying on the left when scrolling horizontally.

The documents created by Oracle Web ADI use a style definition to control which colors, fonts, and other formatting are applied to the spreadsheet. The Oracle style is based on the BLAF standard and has been defined using metadata so that the style can be changed without changing the code. This enhancement enables specific styles to be designed for Oracle Web ADI documents, with the style being chosen when generating a document. The system administrator can set a default style for all documents being defined; when a layout is defined a style can be assigned to the layout; and users can also select a style in the Create Document Page Flow. To define a style, a sample layout is generated into Excel. The designer can then use the standard formatting tools in Excel to format the different regions. When the style is complete, the designer performs an upload from the Oracle menu to upload not data from the sheet but the formatting information. This data is then processed and stored in the database as metadata.

11.1.2.20. Custom Session Configuration

Some Oracle E-Business Suite applications must perform additional configuration or initialization of their sessions. This configuration allows for a cleaner interaction between the desktop and the middle tier, in which only the required information and parameters need be transmitted across the network.

This feature provides a Java extensible interface to support this requirement. To enable calling Java code, an integrator developer defines metadata that directs Oracle Web ADI to the correct class at runtime.

11.1.2.21. Mapping Unique Values to IDs

Information displayed to end users appears differently from how it is stored in the database. To enhance performance when resolving the values an end user has selected back to the corresponding IDs , Oracle Web ADI provides the tools to store an ID along with the value that the user has selected from the list of values; to permit updates only via the list of values; and to assist the end user in working with this information.

Integrator developers can enable this feature when associating the columns that contain the value and ID. Additional behavior can be mandated based on other metadata settings made as part of the solution requirements.

11.1.2.22. Context-Based Layout Management

The layout definition pages allow the combination of fields that appear in the spreadsheet to be defined to match the relevant business processes. Depending on the solution or implementation, some users may not be allowed to access some fields. Context-based layout management reduces the number of layouts required and controls access to those layouts.

Context-based layout management provides developers with the option of creating a Java plug-in that can review the columns assigned to the current layout and remove columns that break any of the product’s business rules. The plug-in has access to the session and consequently can base its processing logic on any information that can be derived from that access. After the review is completed, the layout is created in the spreadsheet.


Oracle iStore solutions implement this new feature.

11.2. Solutions

11.2.1. Overview

Solutions define the integration between a desktop application and an Oracle E-Business Suite product. They are built using the ADI SDK then shipped independently of Oracle Web ADI, either in their own patch or as part of a wider product release. In the Release 11.5.10, the following products released solutions: Oracle Financials Intelligence, Funds & Budgets, Oracle Engineering Online, Oracle General Ledger, Oracle Human Resources, Oracle Internal Controls Manager, Oracle International Public Sector Financials, Oracle Sales Offline, Oracle Projects, Oracle Public Sector HR, Oracle Sales Compensation, Oracle Student Systems, and Oracle Training Administration.

11.2.2. Features

11.2.2.1. General Ledger - Journals

The ADI SDK was used to create the Journals solution provided in Release 11.5.8. This solution allows users to enter and upload journal information from a worksheet on the desktop to Oracle General Ledger.

Several improvements in validation functionality are included in this release.


12. Oracle Report Manager

12.1. Oracle Report Manager

12.1.1. Overview

Oracle Report Manager provides a central, secured, point-in-time, self-service report repository that delivers information to thousands of subscribers simultaneously. This strategy cuts costs by eliminating the need to ship paper reports, and by allowing people in an organization to make smarter business decisions through easier, more timely information access.

The focus of this release is to move away from the existing client/server-based definition, submission and publishing model to a Web-based model. No client-side Oracle software is required for working with a report; only the client-side application used to view the report, such as Microsoft Excel or Adobe Acrobat Reader, needs to be available.

The move to the Web requires a change in how reports are stored and when they are formatted for presentation to the end user. All reports run for Oracle Report Manager deliver their output in XML format. This output is stored in the repository until an end user makes a request to view the report. Only at this point is the presentation formatting applied. This change allows the formatting to be updated, which formerly would have required the report to be rerun and published, because the formatted report, not the raw report, was stored in the database.

The move to the new architecture also allows the existing Oracle Report Manager solution to remain unchanged. This new release of Oracle Report Manager can be installed on a site without risk of losing reports published under previous releases. Migration tools assist a site to move the existing reports into the new repository as a post-installation activity.

Oracle Report Manager depends on the following products:

• Oracle XML Publisher

• Oracle General Ledger

12.1.2. Features

12.1.2.1. Submit, Publish, Present, and Display

The submission of financial statements, ad hoc financial statements, standard reports, and variable format reports are now made through Web-based page flows. Additional steps in the flow include the selection of where in the repository the report output should be stored. Users of standard and variable reports can now associate an expanded value with the report to build expanded reports. The presentation of report output is now formatted using templates that are based on the industry XSL:FO standard. The creation of a menu entry for accessing the report is improved, allowing the entry to be created under any menu.

Large production environments have the requirement to submit multiple reports. To meet this need, support is available for the submission of report sets (financial statements) and


request sets (standard and variable reports). Publishing and presentation options can be defined in advance and used each time the report or request sets are submitted.

Report output from the menu entries continues to support HTML and Excel output, and now also includes Adobe Acrobat. The display page by default displays HTML output, with the option to choose one of the other types.

12.1.2.2. User to Value Security

In this release the User to Value security functionality is updated and combined into a workbench.

12.1.2.3. Financial Reports Template Editor

The industry has developed the XSL:FO standard to format XML reports, and templates using this standard are used to format the report output in Oracle Report Manager. Experienced end users can develop templates using a standard word processor.

To improve the end user experience, this feature provides the means to create and modify templates for financial reports in Microsoft Excel. Templates by default work like the cell-level formatting themes, which require templates built for each financial report. To assist in this process, the page flow for creating a template asks for a report name and generates all the elements into a worksheet for further editing.

No client-side installation of any Oracle software is required to work with templates. Only Microsoft Internet Explorer and Microsoft Excel are required.

Templates are being adopted across Oracle E-Business Suite. Oracle XML Publisher provides a central template management feature for storing and administering templates. Oracle XML Publisher also provides tools and instructions for creating templates for other report types.

12.1.2.4. Repository Management

This release introduces functionality to organize and administer the reports that have been published to the database.

The repository management feature can be used to create a logical hierarchy for simplifying the administration of published reports. A folder hierarchy can be developed, and reports can be moved, re-ordered, merged, or deleted as required.

The repository is designed to store all instances of the same report under one node in the hierarchy. Variations in the report are recognized through a time frame or an expansion value. Users view the report from a form function linked to the report node. Where several reports are published to the same the node, time frame or expansion value combinations can be selected to let users view the report for a specific point in time and expansion value without leaving the page.

For each report in the repository, you can modify the default template, security level, and availability or create a new menu item.

Administration of the repository includes removing reports from repository after they are no longer relevant in the day-to-day operation of the organization. Some reports cannot be deleted but may require archiving to meet organizational policy or legislative


requirements. Reports are archived from the repository to a set of archive tables that can be backed up and purged. You can also restore these reports from the archive.

12.1.2.5. Migration

Previous releases of Oracle Report Manager stored reports in tables shared by other products in Oracle E-Business Suite. This release provides instead a set of dedicated tables for storing and administering reports. A migration path is provided for customers who have published reports using previous releases. You can run the migration as a post-installation option after you are satisfied with the installation of the new version. Repository management tools are also provided to merge old reports with new, and to assign reports in the repository to form functions that were defined using a prior release.

12.1.3. Terminology

Term Definition

Expansion value

A value assigned to the report to differentiate one variation of a report with one set of parameters to another variation of the same report with a different set of parameters. A financial statement when run with a content set that contains page expands automatically splits the report output and assigns an expansion value to each report. An end user can assign an expansion value to a standard or variable report during the submission, publish, and present page flow. After expansion values are assigned, they can be used to secure a report through the User to Value Security feature.

Expanded report

A report that has expansion values assigned, so that one report actually represents multiple variations of the same report. When viewed an expanded report includes an Expansion Values list that allows the end user to select a different variation of the same report to view.


13. Oracle iSetup

13.1. Oracle iSetup

13.1.1. Overview

Oracle iSetup is a web-based tool that supports data management for applications by enabling migration and monitoring of data throughout the application lifecycle. By automating migration and reporting of setup data, Oracle iSetup allows Oracle E-Business Suite to be implemented faster than ever before, and with lower risk. It also makes it easy to manage data on an ongoing basis.

13.1.2. Features

13.1.2.1. Reporting Enhancements

Reporting was introduced in Oracle E-Business Suite Release 11.5.9. For the present release, the following enhancements are made to the reporting module.

13.1.2.1.1. Reporting on Setup Data with no BC4J Wrappers

Users can now view a report on setup data that does not have any BC4J wrappers. These objects include many AOL objects, which use FNDLOAD utilities.

13.1.2.1.2. Comparison Reporting

In Release 11.5.10, users could report on setup data only for a single instance. Now, users can compare setup data between snapshot files. These snapshot files can be data from a single instance across time, or from two different instances.

13.1.2.1.3. Report Download Formats

Users can now download a report in PDF, RTF, and Excel formats. The user must specify the format at the time of report generation.

13.1.2.1.4. Reporting on Selective Data

Oracle iSetup enables reporting on a need basis. You can selectively choose objects for reporting while creating a standard or comparison report. This feature enables better performance for report generation.

13.1.2.1.5. Ability to Search Within a Generated Report

Oracle iSetup now has a new online view for a generated report that allows searching of records based on certain attributes of the record. This feature is available for both standard and comparison reports.

13.1.2.2. Support for Additional APIs

In addition to the setup objects supported for migration and reporting in Release 11.5.10, Oracle iSetup now supports object APIs for the Application Object Library, Financials, Manufacturing, and HRMS product families as well.


13.1.2.3. New Selection Sets

Oracle iSetup offers 16 predefined selection set templates. These templates are redesigned to include the new APIs and to offer better usability.

13.1.2.4. Transformations Decoupled from the Load Process

Earlier, Oracle iSetup only allowed attributes to be transformed at the time when the load process was initiated. Now, you can transform certain attributes of one or more data objects within an extract prior to initiating the load process. Note that not all data objects support transformation.

13.1.2.5. Upload

An Oracle iSetup extract can also be uploaded to an Oracle iSetup instance from your desktop or local file system. The extract you upload can be stored in an external repository or downloaded from another instance. After being uploaded successfully, the extract can be used for reporting or the load process.

13.1.2.6. UI Changes

The UI for Oracle iSetup has been changed to:

• Conform to the BLAF guidelines.

• Provide better usability.

13.1.2.7. Performance Improvements

The Oracle iSetup architecture in this release offers major performance enhancements in the extraction/loading and the reporting processes.

13.1.2.8. Hierarchical Selection Sets

Oracle iSetup now also supports hierarchical selection sets.

13.1.3. Terminology

Term Definition

Selection Sets A selection set is a logical grouping of setup objects. These sets are offered as templates to the user to help migrate data.


14. Oracle Tutor

14.1. Oracle Tutor

14.1.1. Overview

Oracle Tutor consists of two stand alone Windows applications: Tutor Author and Tutor Publisher, as well as a repository of model process documents and applications courseware related to Oracle’s E-Business Suite. Oracle Tutor is not dependent on the standard E-Business Suite 11i technology stack because it is Windows and Microsoft Office based.

Tutor Author requires Microsoft Word for its foundation. Author enables you to use Microsoft Word to edit and create process documentation and courseware easily and efficiently. It enforces the Tutor documentation standard, and it allows you to flowchart procedures and creates HTML versions of the Tutor documents. Tutor Author also helps you convert an an Oracle E-Business Suite online help file to Word for easy editing, and then reconverts it to the required HTML standard for uploading back into online help. If the Oracle Tutor documents will be uploaded into Oracle Applications online help, then the Oracle Applications online help must be available, as well as the Help Utility and Help Builder in the Self-Service Applications.

After a document has been edited or created with Tutor Author, it becomes a part of the Tutor model document repository. Tutor Publisher indexes the Tutor documents and allows you to create many different views of these documents – from desk manuals to owner manuals to student guides. If the Tutor document repository will be stored in Collaboration Suite, Oracle Drive should be installed on the system where the Publisher Program is used.

The Tutor model documents are complete process documents written according to generally accepted business practices in Microsoft Word. When a procedure task references Oracle E-Business Suite, the navigation path and the appropriate online help file are referenced. The model documents consist of procedures, instructions, and reference documents, all tightly integrated to create a complete set of process documentation for the core Oracle E-Business Suite applications.

Following are the new features for the Oracle Tutor.

14.1.2. Features

14.1.2.1. Ability to Customize HTML documents

The new HTML output options are:

• Display the effective or revision date at top

• Remove the Oracle.com link in the footer

• Display a flowchart first

• Include a Quick Link menu

• Flowchart size percentage


• Browse to HTML directory

14.1.2.2. Ability to Customize Student Guides

There are new skeletons for the table of contents and chapter cover pages that are easy to modify with company logos and so on. Other new options are:

• Display filenames in the table of contents

• Display the effective date in table of contents

• Display the revision number in the table of contents

14.1.2.3. Ability to Customize Online Desk Manuals

The new features are:

• Use ‘Newspaper’ columns in desk manuals and indexes

• Open desk manual links in a separate browser window

14.1.2.4. Ability to Customize Author Features

The new features are:

• Import Microsoft PowerPoint slides as GIFs

• Renumber between section title paragraphs

• Option to always open documents in Normal or Print layout

14.1.2.5. Support for Hosted Environments

Environments supported are: Tarantella, Terminal Server Client, Citrix.

14.1.2.6. Support for Server Version of Author

Tutor Author can be installed on a server and shared by multiple users.