Oracle Utilities Work and Asset Management

Release Notes

Release 2.1.1

E69055-02

December 2015(Updated February 2016)

Oracle Utilities Work and Asset Management Release Notes, Release 2.1.1

Copyright © 2000, 2015 Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Preface

These release notes provide an overview of the key functionality, known issues, and other information in Oracle Utilities Work and Asset Management 2.1.1 and is intended for anyone installing or using Oracle Utilities Work and Asset Management 2.1.1.

Audience

This document is intended for anyone installing or using Oracle Utilities Work and Asset Management v2.1.1.

Related Documents

For more information, see these Oracle documents:

Installation Guides

•

Oracle Utilities Work and Asset Management Release Notes

•

Oracle Utilities Work and Asset Management Quick Install Guide

•

Oracle Utilities Work and Asset Management Installation Guide

•

Oracle Utilities Work and Asset Management DBA Guide

•

Oracle Utilities Work and Asset Management License Information User Guide

User Guides

•

Oracle Utilities Work and Asset Management and Oracle Utilities Operational Device Management Business User’s Guide

•

Oracle Utilities Work and Asset Management and Oracle Utilities Operational Device Management Administrative Guide

Supplemental Documents

•

Oracle Utilities Work and Asset Management Server Administration Guide

•

Oracle Utilities Work and Asset Management Security Guide

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

Release Notes

This document provides general information about this release of Oracle Utilities Work and Asset Management, including new functionality, known issues, and other important information.

Refer to the Quick Install Guide and Installation Guide for information regarding supported platforms and installation steps.

Please visit My Oracle Support (http://support.oracle.com) for the most recent service packs and patches for this release to ensure you have the most current version of this product.

This guide includes the following:

•

Release Overview

•

Oracle Utilities Work and Asset Management Enhancements

•

Known Issues

•

Supported Integrations

•

Demo Data Information

•

Oracle Utilities Application Framework v4.3.0.1 Release Notes

Release Overview

This release includes functionality updates for Oracle Utilities Work and Asset Management and Oracle Utilities Operational Device Management:

•

Oracle Utilities Work and Asset Management provides functionality to handle large volumes of assets and to manage the receipt, installation, maintenance, tracking and removal of those assets. The system also manages approval processing, tracks purchasing transactions, manages inventory and resources, and tracks costs, accounting and financial transactions.

•

Oracle Utilities Operational Device Management provides functionality to handle large volumes of Utilities industry devices and to manage the receipt, installation, maintenance, tracking and removal of those devices. Note: Oracle Utilities Operational Device Management is optimized for interoperability with Oracle Utilities Work and Asset Management, however a license for Oracle Utilities Work and Asset Management is required to take advantage of this functionality. Refer to the Oracle Utilities Work and Asset Management License Information User Guide for a description of licensing limitations.

This release includes the following components:

•

Oracle Utilities Application Framework v4.3.0.1

•

Oracle Utilities Work and Asset Management v2.1.1

Features introduced in this release are highlighted in the new enhancements section.

•

Refer to the Oracle Utilities Work and Asset Management Quick Install Guide for a full list of the media pack components and application components included with this release. Also refer to the Supported Platforms section in that guide for an updated list of supported platforms.

•

Visit My Oracle Support (http://support.oracle.com) for the most recent service packs and patches for this release to ensure you have the most current version of this product.

Supported Upgrades

This release must be installed as a new installation of Oracle Utilities Work and Asset Management version 2.1.1.0.0.

For the complete installation procedure, refer to the Oracle Utilities Work and Asset Management Installation Guide.

Database Changes

This release includes database enhancements. For more information, refer to the Oracle Utilities Work and Asset Management Database Administrator’s Guide.

Oracle Utilities Work and Asset Management Enhancements

This section describes new and enhanced features in this release of Oracle Utilities Work and Asset Management.

This release includes:

•

System Wide Enhancements

•

Asset Management Enhancements

•

Inventory Management Enhancements

•

Purchasing Enhancements

•

Work Management Enhancements

System Wide Enhancements

The following enhancements were added system wide:

OUAF Upgrade

•

Oracle Utilities Work and Asset Management v2.1.1 is released on Oracle Utilities Application Framework v4.3.0.1 which provides a more modern user interface and revamped menu functionality. Refer to the Oracle Utilities Application Framework v4.3.0.1 Release Notes section for more information.

WAM/ODM Interoperability

•

System elements (application services, objects, portals, zones, etc) are regulated by the ODM_SERVICES and WAM_SERVICES user groups so that only licensed users of either application have access to the related elements.

•

Business objects were redefined to make a clear distinction between ODM Activity Generators and WAM Work Orders.

•

Activity - renamed to Field Activity

•

Storeroom - renamed to Out of Service Location

•

Work Order - renamed to Activity Generator

•

Cleaned up drop-downs where there is a choice of activity types so that only relevant activity types shown. Activity Types for Activity Generators are now only Field Activity Types. Activity Types for Work Orders are now only Work Activity Types.

•

An owner flag was added to all tables related to the activity type maintenance object.

•

The user flow for on-line activity completion has been streamlined. Additional completion event business objects have been provided for easily configurable creation of service history, assets, and activities.

•

ODM tracked assets are now integrated with inventory and purchasing.Note: A WAM license is required to take advantage of this feature.

Approval Processing

•

Added more information to the approval detail list on the homepage and in the approval dashboard so that approvers have more details to use in making a decision without having to navigate to the specific approval request. The additional information includes the info string from the source document along with the requester.

•

Also enhanced the system so that if a user only belongs to one To Do role, the system bypasses the step where users have to select a role.

Attachment Processing

•

Modified processing so that when a document attachment is created from a record, the system prompts the user to upload the file. Document information zones throughout the system were also updated to include document information such as document type, class and category.

BI Publisher Enhancements

•

Added the ability to print a work order report from the Work Order portal that includes all related work activities.

•

Added Report Dispatch which allows users to search for all business objects that include a report function. Once a business object has been selected, a search portal is displayed to allow the user to filter the records that will be generated for the report. The generated report can also be printed.

•

Report Definition allows the user to import/export Definition Report records from one server to another.

Home Page

•

Updated home page charts display so that users with no default access group can select an owning organization from the drop down, click refresh, and display the applicable chart.

•

All work statistics that were formerly tied to the scheduling process were reworked so that they show simple counts of work orders and activities in the backlog. They are no longer tied to scheduling.

Search Related Enhancements

•

Modified search screens in several portals with more filter options and with foreign keys so that users can search by simplified values rather than by record ID. Also modified several results of search screens with more results options. Some modifications include:

•

Added status to the search screen for cost centers.

•

Added new fields to the stock item search screen.

•

Modified work order search so that you can search by status without entering a business object.

•

Added activity description to the Scheduler search results.

•

Modified activity searching in the Schedule portal.

•

Added vendor name to the search screen for Expedite PO.

•

Added an Asset Location field to the Service History search.

•

Added auto complete feature throughout the system when searching for stock items.

•

Added Planner field to the Scheduler search.

•

Added the ability to search Assets by specification.

Asset Management Enhancements

The following asset management enhancements were added:

General Asset Functionality

•

Bill of Materials functionality was revamped by making changes to Stock Items and the Bill of Materials portals. Refer to the Oracle Utilities Work and Asset Management Business User’s Guide for more information.

•

Modified processing so that users cannot use Mass Asset Disposition Update to move inventory tracked assets into or out of storerooms. Inventory transactions must be used for these transitions.

Asset Location

•

Introduced a new Out of Service Location Type and Out of Service Location to manage assets that are out of service. The location type for an asset can be configured to be an Asset Location Type, an Out of Service Location Type or a Storeroom Type. This replaced part of the functionality of the Storage Location and Storage Location Type, and these portals were removed. Refer to the Oracle Utilities Work and Asset Management Business User’s Guide for more information.

•

Modified the UI and processing so that the system takes a "snapshot" of the asset location at the time the asset is worked on. If the asset is later moved to another location, then the next "snapshot" associates that service history to the new asset location record. This enhancement also added a Service History zone to the Asset Location portal and added an Asset Location field to the Service History search.

Asset Performance

•

Added the Asset Performance Management menu which groups and consolidates all asset performance related portals in one menu selection for easy access.

•

Since questions are also used for inspections, not just condition assessment, the Question portal was renamed as "Question" instead of "Condition Assessment Question." The portal is also used to create questionnaires sent to MWM to be completed by crews.

•

On Service History Types that support questions, a Questionnaire Tree Zone was added to display the questions and answer text.

•

Added an Asset Type zone to the Assessment Class portal.

•

Relabeled the "Criticality" fields to "Asset Criticality" where applicable throughout the system for better clarity and to help align with BI reports.

•

Critical Number and Required by Date fields were added to the Activity History zone in the Asset portal. Also removed the critical number from the Preventive Maintenance Schedule portal.

•

Added cost information to the Asset Location portal.

Preventive Maintenance

•

Added the Preventive Maintenance menu to group and consolidate all preventive maintenance related portals in one menu selection for easy access.

•

Modified the Service History and Activity portals to better handle PM Anniversary:

•

Renamed the zone to "PM Anniversary Information".

•

Renamed fields to clarify their purpose:

•

PM Anniversary Date

•

Runtime Anniversary Value

•

Runtime Anniversary UOM

•

Fields are display only on Activities, but they are editable in Service History. When the anniversary date is changed on Service History, this allows users to control future anniversary based PM generation.

•

Modified the application to separate engineering specifications from preventive maintenance specifications.

•

Created a new maintenance specification as an attribute on Assets.

•

Created a new maintenance specification business object. This business object includes maintenance schedule definitions.

•

The former specification was renamed to "Engineering Specification" on Assets.

•

Removed the maintenance schedule definitions from the engineering specification business object.

•

Added a new zone in the Specification portal to display Assets.

Inventory Management Enhancements

The following inventory management enhancements were added:

Storeroom and Stock/Tracked Assets

•

Replaced the Storage Location portal with the Storeroom portal. This replaced part of the functionality of the Storage Location and Storage Location Type, and these portals were removed. This enhancement also added the ability to link or unlink a specification on a tracked stock item. The specification is the link between the stock item and the asset.Refer to the Oracle Utilities Work and Asset Management Business User’s Guide for more information.

•

Modified the system so that storerooms are selected from a drop-down when executing a search for a storeroom.

Physical Inventory and Inventory Adjustment

•

When users complete a price or quantity adjustment, the system navigates back to the stock item detail.

•

Added the ability to create quantity adjustments for tracked stock items on in the Stock Item Detail portal.

•

Added a Quantity column to the Stock Item Detail Lots zone.

•

To address the need for a comprehensive storeroom summary (including due in and due out counts), introduced the following zones to replace the Stock Item Availability zone in the Stock Item, Material Request, Material Return, Reorder Review and Home Page portals.

•

Stock Item Availability

•

Storeroom Alternative Stock Items

•

Storeroom Stock Item Lots

•

Direct Purchase Related Activities

•

Related Receipts

•

Added processing to ensure that users cannot adjust the price of a stock item when the inventory quantity is zero. Stock items must have both a quantity and an average unit price to create a financial transaction for a price adjustment.

Purchasing Enhancements

The following purchasing enhancements were added:

Invoicing

•

Added invoicing functionality. Refer to the Oracle Utilities Work and Asset Management Business User’s Guide and the Administrative Guide for more information.

Receiving

•

Modified processing so that if a rejection location is left blank on a purchasing receipt, the system uses a default location configured in the Purchasing Master Configuration.

•

Implemented multi-step receiving processing so that they system can:

•

Record delivery for a purchase order

•

Record a standalone delivery

•

Match items to a purchase order

•

Provide a pick list to select items from a purchase order

•

Receive items into inventory

•

Return items to suppliers (and remove quantities from inventory)

•

Quick receive items

•

Force complete purchase orders.

Refer to the Oracle Utilities Work and Asset Management Business User’s Guide for more information.

Purchase Orders and Purchase Requisitions

•

Added an Item Type column to the Purchase Requisition Line Item zone and made unit of purchase (UOP) a required value for line items. Also added processing to ensure that the item type is defaulted on the line item when a purchase request is created from activity resource requirements.

•

Added revision history to the Purchase Order header so that the all updates to the purchase order are displayed.

•

Added processing so that the Issue Date is set and displayed on the purchase order when the status is transitioned to Issued.

•

Added validation to prevent transitioning a purchase order to pending approval, approved or issued if there are no line items.

•

Added Cost Center and Expense Code to the purchase requisition line items, and updated the Create Tax Lines for purchase requisition line item algorithm so that the corresponding tax rate component’s cost center and expense code are captured. Settings related to this functionality are controlled in the Purchasing Master Configuration. Added a detailed description column to:

•

Purchase Requisition Line Item

•

Purchase Order Line Item

•

Blanket Contract Line Item

Work Management Enhancements

The following work management enhancements were added:

Crews, Employees and Timesheets

•

Added a new Work Management master configuration to allow or disallow creating timesheets against completed activities.

•

Added processing to ensure that employee unavailability is reflected on the employee calendar.

•

When there is a partial overlap of date time period between the Crew shift and Employee Unavailability, the system displays both the Crew shift and the Employee Unavailability on the Employee calendar.

•

When the date time of Employee Unavailability is a super set of the Crew Shift date/time period, we would only show the Employee Unavailability on the Employee Calendar.

•

Added a Crew field to the Timesheet. As applicable, the crew is populated after the timesheet is saved based on matching the employee ID on the Timesheet header, the date, and the crew shift start and end dates.

Work Requests, Work Orders and Activities

•

Modified the user interface so that the Work Request field is always displayed on the Work Order, even if there is no Work Request number.

•

Renamed "Parent Work Order" and "Parent Activity" to "Originating Work Order" and "Originating Activity". These types of work orders and activities are referenced on follow-up work.

•

Modified processing so that key fields are defaulted when a new activity is created.

•

Added processing so that when creating a Work Order, the WO Requester field defaults to the user name of the logged on user.

•

Added the ability to add items from a Bill of Materials pick list to a Work Activity.

•

Renamed the "Craft" field to "Labor" on Activity Resources.

•

Added planner field to Work Requests and Activities. This defaults from the asset location when the work request is created, if it is not specified by the user. When work orders or activities are created from the work request, the planner defaults from the work request. If the activity is created directly from the work order, the planner defaults from the work order. The defaults can be changed if necessary.

•

Location is now copied from the location on the asset when the asset is added to a work request. By default, the location information populates the address fields.

•

Project now defaults to template activities and template work orders when they are created from a work order. Any newly created activities or work orders are populated with the default project indicated on the template record. If the template work order has a different project than the activity, any activity created from the work order inherits the work order project.

•

Modified functionality so that creating completion events is more streamlined and straightforward:

•

Added new Planned Service History Types zone in the Template Activity and Activity portals so that your implementation can create "planned" service history types for use with template activities. These service history types can be selected by users when creating the completion event to add service history on an activity. The service history types entered must be valid for the asset type.

•

Added zones in the Completion Event Type portal where your implementation can link or unlink related activity types.

•

Added zones to the Service History Type portal where your implementation can link or unlink related asset types.

•

Added the following new base package completion event types:

•

Create Any Service History

•

Create Asset for Activity Location

•

Create Any Activity

•

Create Operational Reading

•

Create Service History Using Payload Completion Event **updated existing

Scheduling

•

Relabeled the "Scheduling Date Time" field to "Activation Date/Time" to more accurately reflect the function of the field which is to indicate the date and time that the activity should be activated after it is approved. For example, users can enter a future activation date if they don’t want the activity to be activated as soon as it is approved.

•

Implemented the following changes for weekly shift generation:

•

During weekly shift generation the system uses the 'Start Week Day' option set in the Resource Management Master Configuration. I this is not configured, Monday is used as the default.

•

The following rules were created to better align generation of a weekly shift via automated shift plan templates with the work weeks that users typically expect. These rules also ensure that the weekly shift is still generated when the shift plan template is applied via batch on a daily basis.

•

When a weekly shift is generated, it should have an end date set as the day before the start week day configured in the system. However, this is only applicable if an existing weekly shift is not already created for the given time interval.

•

The last weekly shift generated can again stretch beyond the processing end dates (of the shift plan template) and it can have an end date a day before the 'Start Week Day'.

•

Revised the lifecycle in scheduling portals by changing the stats from "Planned" to "Planning" and removing the "Pending" state. This enhancement also includes a modification to add "Active" status to the Schedule Plan. No scheduling can be done when a schedule plan or daily schedule is in Active status, but the planner can move the schedule back to "Planning" to make changes.

•

Added the Scheduled Labor Requirements zone to the Activity portal so that users can see which crew shifts are assigned to an activity. This enhancement also added new search criteria to the Crew Shift search.

Known Issues

This section lists issues that were found but not resolved in both Oracle Utilities Work and Asset Management and Oracle Utilities Application Framework at the time of release.

Oracle Utilities Work and Asset Management Known Issues

The following table lists known issues in this version of Oracle Utilities Work and Asset Management at the time of release.

Bug #

Description

n/a

Oracle Utilities Operational Device Management users may notice that the login screen, some application screens and the on-line help only make reference to Oracle Utilities Work and Asset Management. Product name differentiation will be supported in a future release.

22346281

Some WAM Asset Type business objects are still available in ODM. Tracked IT Component, Tracked General Component and In Out of Service Fleet Asset should not be available to ODM only users. ODM-only users must only use Asset Type business objects specifically marked as "Operational Device".

21436278

The explorer cube which is available on the Schedule tab of the Crew Shift portal and on in Purchase Requisition cannot save changes.

21847088

The time picker is not working correctly in the Operational Reading Quick Entry.

21878324

Charge date is misaligned in Other Direct Charges.

22290935

When users log in for ODM only, they can still see the BOM field on Assets; Stock Item, Maintenance Schedule, Engineering Specification, and Relationship Types on Specifications; and Measurement ID on Service History.

22300791

When users log in for ODM only they can still see the Purchase Order information section on Assets.

22302972

Need to provide Attachment support for modules.

22306714

Users can currently edit the location on service history. This should not be allowed because users could potentially enter invalid locations. The system should default the location when the service history effective date is changed.

22313179

When broadcasting in the Vendor Purchase Order History Summary zone in the Vendor portal, the zone is displayed with no data. The zone should display a graphical representation of PO Line amounts for each cost category capture on PO Line expense codes.

22340325

They system is calculating incorrect values for financial transactions created for material issue and material returns.

22352814

The WAM maintenance specification option is still available in ODM when selecting a specification class.

22354320

When a user executes the action to create a PO from a blanket contract and tries to associate the PO line item against an activity, the activity look up is querying ODM records, not WAM.

22361466

This release introduced changes to the WAM-ODM Admin menu sequence. As a

result, the sequence of some ODM Admin menus was modified. This change would require a permanent upgrade script to be packaged since sequence number is a customizable attribute and changes to the sequence number will not reflect in the case of an ODM to WAM upgrade.

22361715

Users cannot create asset types for components.

The following issues are pending resolution of Oracle Utilities Application Framework bugs

Bug #

Description

20352489

When adding an expedite order and searching for PO line items, the user has to keep selecting the appropriate PO Header ID to be able to search for related PO lines.

20640801

Navigation via bookmark causes screen search label problems.

20668277

Stock Item Detail portal: Search issues. The system is not properly showing results based on the selected query option.

20669627

Stock Item Detail portal: Cost center is highlighted even on the search pop-up.

20705614

Search results do not display as expected in the Template Work Order portal.

20834339

After a required field is highlighted in red when it is missing and the Search button is clicked, the highlight does not clear correctly after the user moves on to fix the field error.

20840945

The system shows an error when an employee search is executed from the Personal Information section on the Leave maintenance UI screen.

21200285

MWM-WAM Integration: Lookups marked as custom=no are accepting customer modification values.

21558612

The cost center field is not getting populated on work order UI.

21925827

Identifier section overlaps access control on Measurement Quick Entry Completion Event Types.

22201320

Invoice Quick Add:

•Issue 1: Unit of Purchase is not displayed on Quick Add when PO line has been broadcasted.

•Issue 2: Price in Quick Add shows the base currency.

22244817

Context menu navigation not working for query zone results.

Oracle Utilities Application Framework Known Issues

The following section provides a list of known issues in Oracle Utilities Application Framework version 4.3.0.0.1 at the time of release. This includes fixes for previous versions of the product that have not been included in this release. These fixes are planned for a future date for the current release using the bug numbers listed below.

Original Bug

Original Version

Description

4.3 Bug Fix

n/a

4.3.0.0.1

When an outbound message gets created or updated, any validation algorithms on the outbound message BO are not fired because the F1-OUTMSG MO is missing from System

@ Event Determine BO F1-STD-DTMBO (Determine Standard Business Object). The system event was added temporarily in Oracle Utilities Work and Asset Management.

20846956

n/a

4.3.0.0.1

In all in one (standalone) portals, when first broadcasting a record, the info string in the heading is not displayed. Navigate elsewhere then back to display the info string.

20738676

n/a

4.3.0.0.1

Multi query search input values are lost when users navigate back to a portal via history.

20579148

n/a

4.3.0.0.1

The filter icon does not always display in Firefox.

20576737

1641865221125544

2.2.0

Printing a zone outputs in portrait instead of landscape.

21125562

20570324

4.2.0.1.0

Search window will not launch when the Internet Explorer 9 browser zoom is set to 150% magnification.

20570329

21057439

4.2.0.2.0

Back button 2x "forgets" selected query in query option list

21057709

21104664

4.2.0.2.0

Label font color changed?spacing displayed in Chrome

21903486

21209873

4.2.0.2.0

Query zones with filter UI Maps do not restore input filters with defaults configured

21210495

21104765

4.2.0.3.0

Data grid shows extra column in Chrome

21294297

21243926

4.2.0.3.0

Filter values disappear on navigating back/forward in Chrome

21265682

21260161

4.2.0.3.0

Billable charge screen hangs on pricing info tab in Chrome

21287396

21304345

4.2.0.3.0

Link issue on account collection summary in Chrome

21339872

21355708

4.2.0.3.0

the Orahandledependentdatetime function is not working for date time fields in list

21441766

Supported Integrations

The following integrations are supported in this version of Oracle Utilities Work and Asset Management:

•

GIS Integration The GIS Integration uses ESRI GIS software to allow users to view asset layers on a map, and to create and view work requests and work orders on the map.

•

BI Publisher Reports Integration BI Publisher Reports allow users to generate and print reports for certain entities, such as operational data, activity reports, purchasing reports, inventory reports and so on.

•

Integration with Mobile Workforce Management Oracle Utilities Work and Asset Management integration with Oracle Utilities Mobile Workforce Management is managed through the Oracle Utilities Field Work Process Integration Pack.

Please refer to the Oracle Utilities Work and Asset Management Administrative Guide or the specific integration guides available on the Oracle Technology Network for more information.

Demo Data Information

The application delivers a demo database based on the application versions provided with the release, including Oracle Utilities Application Framework.

Demo data provides sample configuration and data for key application features. Demo data is delivered as part of the base installation. Refer to the Oracle Utilities Work and Asset Management Database Administrator’s Guide for more information, or contact Oracle Support.

Oracle recommends that you do not clone the demonstration environment as a basis for a new production environment. The demonstration environment typically includes transactional data that will be irrelevant to your production environment and can cause unexpected issues if it is not purged correctly. The recommended process is to start a new production environment from a new installation and migrate "clean" system data (such as business objects and algorithms) and administrative data (such as sample activity types or other administrative entities) from the demonstration and/or test or development environments as applicable.

Refer to the Oracle Utilities Work and Asset Management Administrative Guide for more information or contact Oracle Support.

Oracle Utilities Application Framework v4.3.0.1 Release Notes

This section describes enhancements, known issues and other updates in Oracle Utilities Application Framework version 4.3.0.1 including:

•

Oracle Utilities Application Framework Enhancements

•

New System Data Details

•

Deprecation Notices

Oracle Utilities Application Framework Enhancements

This section describes new and enhanced features in this release of Oracle Utilities Application Framework v4.3.0.1, including:

•

System Wide Enhancements

•

Online Help Enhancements

•

Security Enhancements

•

Configuration Tool Enhancements

•

Batch Enhancements

•

To Do Enhancements

•

Miscellaneous Enhancements

•

Extendable Lookup Enhancements

•

Web Service Enhancements

System Wide Enhancements

New Login Screen Images

In this release, the image visible in the Login screen for the application has been changed.

New Session Expiration Behavior

In previous releases, if a user's session had expired, the user was still able to perform some tasks that did not require interaction with the server. When the system attempted to interact with the server, the user was then returned to the login screen or was presented with an error.

In this release, the system has been enhanced to detect the timeout and show an alert that the session has expired, informing the user to login again.

Indicating Required Fields

In this release, required fields (elements) are marked using an asterisk. This is visible on the maintenance dialog objects defined using a business object that are maintained on a portal-based page (also referred to as ‘new style’). It is not visible on objects maintained on a fixed page (also referred to as ‘old style’).

Required elements for a row in a child collection (list) are also marked with an asterisk. Note that the system does not have any visual marking to indicate that at least one row in a child collection is required. It is only able to highlight which elements must be populated for each row.

The system relies on the field or element configuration (table/field metadata and BO schema configuration) to display the asterisk. If there are elements that are required via an algorithm or some other procedural code, the system is not able to detect that condition in order to display the asterisk.

If an implementation does not wish to enable this functionality, it may be turned off via the properties file. To turn this functionality off, uncomment the following setting #com.oracle.ouaf.ui.disableRequiredFieldIndicators = true in the spl.properties.template file.

Menu Behavior Enhancements

In the previous release, the menu behavior changed from the 4.2.x code line. In this release, some further changes have been made to the display of menus:

•

Clicking the Menu or Admin button causes the first sub-menu to appear. If other sub-menu options are available, a right arrow is visible on the menu line, the user can mouse- over the menu line to show the sub-menu. The user may now click this menu line to lock the sub-menu. The right arrow image is replaced by a padlock image. If the user's mouse moves away from the menu area, the locked sub-menu remains visible. This resolves the usability issue of needing to keep the cursor lined up on the menu line as the mouse is moved toward the sub-menu to further select the desired option.

The user may now do one of the following:

•

Click on or mouse over the desired sub-menu line to further open the next level and ultimately click the desired option.

•

Click on a different menu line to lock that sub-menu instead.

•

Click the ESC key or click on an area of the page outside the menu to close the menu.

•

For menu lines that support Search and Add options, the Search option now appears before the Add. This is an effort to use the menu line and item metadata configuration to drive the display. The base product menu lines always configure the search menu item first, followed by the add menu item. The menu rendering now follows that.

Note : If your implementation has custom menu lines with multiple menu items where the add is configured as the first menu item and search as the second, then the menu rendering will reflect that.

•

In the 4.2.x code line, the add option was rendered as an image (configured on the menu item). In 4.3.0.0, the menu rendering changed to use the word Add and an image is no longer used, however, the internal code still used the presence of the image reference in the menu item to signal which of the menu items is the ‘add’. Because the image itself is not necessary, the code has been enhanced to cater for no image configuration. In this case, the system assumes that when a menu line has two menu items, the first menu item represents the search and the second represents the add.

Note . For backward compatibility, the system will continue to look for an image and assume that the menu item with the image is the add. If your implementation has custom menu lines with two menu items, where the add is first (but still refers to an image), no changes are needed. (However, note that in this case, the add will display before the search option.) If you wish to remove the image (that is no longer needed), be sure that the search menu item is the first in the sequence.

Menu Configuration Enhancements

In this release, the Label Long on the Menu maintenance object has been suppressed from the user interface. This field is not used by the system.

In previous releases, the Description on the Menu maintenance object was only enabled for the Main and Admin menu types and was used to build the menu bar prior to version 4.3.0.0. In this release, the description is now available for all menu types and may be used to provide information about the menu. The menu search has also been enhanced to search by the description and to return the description in the results.

Toolbar History Enhancements

In this release, when a user navigates to a portal that is configured to display its information string as part of the page title (via the FK reference on the portal options), that detail is also visible in the History drop-down in the application toolbar.

This functionality is only available for portal based pages. It is not available for navigating to fixed pages. Also note that the current product standard is not to configure all-in-one portals to reference the information string.

Component Install/Deploy

In previous releases, installation and management of individual components of the product was complex. In this release the installation has now been altered to identify the roles supported by the installation to optimize the configuration and management of each installation. In this release, the online, integration and batch roles are supported to optimize the components available for configuration and deployment. An environment identifier has also been introduced to group disparate installations, even across machines, into a single managed environment. The roles for an installation are typically determined at installation time, but this enhancement allows change of roles after installation without the need for re-installation.

Online Help Enhancements

Oracle Help for the Web

In this release, implementations using WebLogic will see a new help implementation using Oracle Help for the Web (OHW). Besides a slightly different look and feel for the table of contents and the topics, OHW provides the following capabilities:

•

Full text search - If there is a term that you want to find help about, you can use the full text search to find topics that reference that term.

•

Combined index - In previous releases, if an implementation included multiple products in the stack, each with its own help set that was included, the index was separated. A user needed to first select the product and then search for the index term. With OHW, the index terms are combined for all products providing their separate help topics, increasing usability.

•

Various usability controls such as paging through topics

•

The ability to provide feedback to the documentation team through a feedback form

Oracle Help for the Web is not available in WebSphere. Clients using WebSphere will continue to see the Classic online help visible in previous releases.

Framework Help Included in Edge Product Help

In previous releases, the online help that is specific to the framework product was installed separately from online help provided by each edge product. The table of contents for the help was visible side by side. In the Classic help view, the index entries were kept separate as well.

Starting with this release, the edge products will incorporate the help for Oracle Utilities Application Framework into its build of the help.

The following provides additional details:

•

For the business process chapters, the framework topics User Interface Standard Features, To Do Processing and Reports are incorporated into the outline of the edge product help in a location appropriate for that product's help. For a business user, this removes the distinction of what functionality is provided by the framework layer and what functionality is provided by the edge product.

•

The business process chapters for Batch Processing and External Messages have been moved to the corresponding chapters in the Administrative User Guide.

•

The full set of Oracle Utilities Application Framework chapters are included in the Administrative User Guide, followed by the full set of chapters associated with the edge product.

Security Enhancements

In this release, the following enhancements have been made to the application security functionality.

Enhance User BO Used for External System Integration

In this release, changes have been made to the business object that is used to create Users from Oracle Identity Management (OIM) to support a template user.

In previous releases, in order to define a user from OIM, an implementation needed to define a Generic Technology Connector (GTC) to map information from OIM to the product. The implementation could choose to:

•

Expose the information to the OIM administrative user to define the information when creating the application users. For example, for this new user, specify their Home Page or valid User Groups.

•

Define standard values in the mapping file so that the OIM administrative user doesn't need to specify them for every user (for example the Language or the Time Zone).

In this release, the product provides the ability to use a template user in the application with appropriate configuration for users of that type. In OIM, the Generic Technology Connector (GTC) can be defined with the bare minimum needed to create a valid application user (such as their Name, Email Address and User ID) along with a template user from which all the other configuration data can be copied. This allows an implementation to define template users for standard roles. Each template user can define the appropriate User Groups, Home Page, Portal Preferences, To Do Roles, etc for users in that role.

The F1-IDMUser business object (User for External System Integration) now has a pre-processing algorithm that looks for a template user (defined as a characteristic). It retrieves the configuration from the template user. It creates the new user with a combination of the information passed in from OIM (such as name, User ID, Email Address) and the information from the template user.

Separately Secure Change to a User's User Groups

The ability to change the Enable / Disable flag on the user record requires special security. However in previous releases, all other attributes of a user could be modified by anyone with security for the Change access mode, including the user group configuration.

In this release a new access mode ( Administrator) has been introduced to the User application service allowing implementations to separately secure the ability to change a user's user groups.

Upgrade Note: For backward compatibility, all user groups that have security for the Change access mode will be updated to also have security for the new System Administrator access mode. Implementations can then decide if they would like to take advantage of the new capability to limit which user groups should allow changes to the user's user group information.

Configuration Tool Enhancements

In this release, the following enhancements have been made to configuration tool functionality.

Schema Editor Enhancements

The following enhancements have been made in the schema editor for defining elements for a business object:

•

Enhancement to Map XML Element Definition In previous releases, the schema editor's Map XML Field provided a search to find the appropriate field within the MO to use for the mapping. In this release, the field has been changed to a drop-down given the typically small number of CLOB or XML data type fields in a given MO.

•

Simple Field In this release, a new schema editor element type Simple Field has been introduced to help simplify the steps needed to create an element that is mapped using Map XML. This can be thought of as a type of wizard for a specific type of Field element. It exposes a subset of configuration available for the Field element type. In the Database Mapping section, only the Map XML Field element is exposed.Note that this is only available for the schema editor on Business Object because that is the only place where the maintenance object is known. For other schema editors on other pages, for example the Data Area schema editor, the Field element type must be selected to define this type of element.

Scripting Enhancements

The XQuery processor for scripting engines 2 and 3 has been upgraded. It now supports the functions ' matches', 'replace' and 'tokenize'. In addition, it is able to reuse more XPath expressions than before. As a result, implementations can reduce the XQuery LRU cache size in the spl properties file (com.oracle.XPath.LRUSize). The adjustment depends on your specific implementation. A rough recommendation is to reduce the cache size by about one-third.

Batch Enhancements

In this release, the following enhancements have been made to batch functionality.

Batch Parameter Security

In this release, a new security flag has been added to the batch control parameter collection to indicate if there should be some security applied to the value of the parameter. The values of the security flag are Encrypt and None. The default is None. The configuration of the parameter value's security must be set on the batch control.

If the parameter value's security is set to Encrypt:

•

Any default value set on the Batch Control will be stored in the database as encrypted

•

When the batch job is submitted using Batch Job Submission, the value will be shown encrypted.

•

In the log generated for the batch job, the parameter value will be written with asterisks.

Upgrade note : All existing base product owned batch controls have been updated to set the parameter to None to maintain backward compatibility. The configuration of any base owned batch control may be changed by an implementation. The recommendation for the F1-LDAP (LDAP Import) batch control is to configure the 'password' parameter value to Encrypt.

System Health Check

In this release, a new service has been provided to assess the health of the system. The current implementation of this service is to execute the batch control - level of service algorithms. It is possible that in the future additional health check types may be supported.

The service can return an overall status based on the details of the health check (for example based on the details of the level of service algorithm results).

•

200 indicates that everything is normal /healthy.

•

203 indicates that a non-critical function is degraded

•

500 indicates that one or more critical functions is degraded

•

The health check service maps the following results returned by the level of service algorithms:

•

If at least one algorithm returns a value of Error, an overall status of 500 is returned

•

If no algorithm returns a value of Error and at least one returns a value of Warning, an overall status of 203 is returned

•

If all algorithms return a value of Normal, an overall status of 200 is returned.

An Inbound Web Service F1-HealthCheck has also been provided allowing external systems to use a web service to retrieve this information.

In addition, the product provides a Health Check portal that shows the details of the health check. The output of each batch control's level of service algorithm is displayed.

To Do Enhancements

This section describes To Do related enhancements.

Allow Additional Sort Keys on Manual To Dos

In previous releases, the product allowed for a To Do Post Processing algorithm to populate custom sort keys. However, in the case the standard sort keys for a manual To Do (User ID, User Name and Subject) were not populated by the system.

In this release, the product ensures that the standard sort keys of User ID, User Name and Subject are populated on a manual To Do Entry even when custom sort keys are also populated. The To Do Type must define the standard sort keys for the manual To Do entry (as described in the Online Help).

Note: This functionality was originally implemented as a hot fix to the 4.2.0.2.0 code line via bug 20886978.

Miscellaneous Enhancements

Attachment Creation Enhancement

In previous releases, the procedure for creating an attachment was two steps: first choose the appropriate business object based on the type of attachment and enter a description; then upload the attachment.

In this release, the attachment creation has been streamlined to follow a more typical attachment dialog. Now when a user wants to create an attachment, first the user selects the file to upload. The system then determines the business object and prompts the user for the description (and any other fields that may get captured depending on your specific product). The uploaded attachment is then saved.

Upgrade note: If your implementation has created customized dialogs to create an attachment and call the base BPA F1-AttchMain (Attachment Maintenance), some minor changes are required to your custom BPAs to align the script's data areas with the F1-AttchMain.

In addition, if your implementation includes a custom BPA for uploading attachments and invokes the base UI Map F1-AttachmentUploadPopup following the pattern of the base BPA F1-AtchUplod the custom BPA will need to change how it invokes the Attachment Upload map to reflect the changes in the FW Attachment Upload BPA. The script step was changed from an Invoke Map step type to an Edit Data step type. It sets the target area as Page Area rather than Pop-Up Window and caters for the new Cancel action. Please contact Customer Support if you need more information.

Extendable Lookup Enhancements

This section describes enhancements to the extendable lookup.

Characteristics Added

In this release a standard characteristics collection has been added to Extendable Lookup. Extendable lookups may now be designed to capture additional information that may then be searchable by an algorithm or other internal process.

New CLOB Column Added

As previously delivered, the extendable lookup MO includes a standard CLOB column ( BO_DATA_AREA) that is configured to be customizable. It means that if a product supplied an extendable lookup BO that defined additional information for each lookup value and supplied base values for the lookup with that additional information populated, an implementation could change the values of the additional information.

In this release, a new CLOB column has been added to the extendable lookup that is configured to not allow customization (BASE_BO_DATA_AREA). This allows product teams to define an extendable lookup BO that delivers base values and includes additional information that an implementation may not change.

For example, imagine a product defines a Contact Type extendable lookup that captures the addition information Priority and Allow Extension. In addition, imagine that the product supplied base values for the lookup and included delivered values for Priority and Allow Extension.

Code

Description

Allow

Extension

Priority

Owner

C1-PHONE

Phone

Y

50

C1

C1-FAX

Fax

N

50

C1

C1-EMAIL

Email

N

10

C1

The design dictates that an implementation is allowed to change the Priority of the base record, but not the Allow Extension value. The design of the business object would look like this:

<lookupValue mdField="CONTACT_TYPE" mapField="F1_EXT_LOOKUP_VALUE"/>

<description mapField="DESCR"/>

<owner mapField="OWNER_FLG" dataType="lookup" lookup="OWNER_FLG"/>

…

<allowExtension mdField="ALLOW_EXT_SW" mapXML="BASE_BO_DATA_AREA"/>

<priority mdField="PRIORITY" mapXML="BO_DATA_AREA"/>

The Priority element is mapped to the customizable CLOB and the Allow Extension element is mapped to the non-customizable CLOB.

The following points should be noted about this functionality:

•

An implementation may change the value of additional fields mapped to the customizable CLOB field (in the above example Priority). When upgrading to the next release of the product, the overridden value of Priority will be retained.

•

An implementation may not change the value of additional fields mapped to the non-customizable CLOB field (in the above example Allow Extension). A user will receive an error when attempting to change the value via the application. If the value is changed in some other way, when upgrading to the next release of the product, the product's value for the elements will be restored.

Note : At this time the error issued to a user attempting to change an element mapped to the non-customizable CLOB will reference the label of the physical column rather than the label of the element defined in the BO. Using the above example, the user will be told that you cannot change the value of Base BO Data Area rather than being told that you cannot change the value of Allow Extension.

•

If allowed by the extendable lookup, an implementation may add new extendable lookup values and may define the values of all additional fields as necessary. (In the example, values for Priority and Allow Extension may be defined as appropriate.)

Upgrade Note: As part of this enhancement, the base lookup values for the Schema - Element Types (F1-SchemaNodes) extendable lookup have been updated to define the values of the Property Control element in the non-customizable column. This element may not be modifiable by implementations.

Override Description Visible in Extendable Lookup List

Extendable lookup supports an override description. In previous releases, if the override description was populated, it wasn't shown in the extendable lookup list zone. In this release, this has been fixed. The override description is now visible in the extendable lookup list zone.

Add Action Moved to Page Actions Area

In the previous release of the product, the Page Actions area was introduced and many portals adjusted their user interface to define the Add action in the page action area rather than as a hyperlink in the zone header. Extendable Lookup was not included in that update. In this release, the Add action for the extended lookup is now visible in the page actions area.

Validation Added to Several Base Extendable Lookups

In this release, several framework-owned extendable lookup business objects were enhanced to include a validation algorithm to issue an error if an implementation attempts to add a new lookup value. The functionality related to the extendable lookups does not support custom lookup values. This was true in previous releases as well, but there was no validation preventing custom records from being added. (Any custom records that may have been added were simply ignored). In this release, the explicit validation has been included to avoid confusion.

The following table highlights the list of extendable lookups that do not allow custom lookup values.

Extendable Lookup Business Object

Description

F1-BooleanValues

Generic Boolean Values

F1-SchemaActionValues

Schema - Action Values

F1-SchemaBoolTrue

Schema - Boolean True

F1-SchemaBooleanValues

Schema - Boolean Values

F1-SchemaDataTypes

Schema - Field Element Data Types

F1-SchemaDefaultSysVariables

Schema - Valid System Variables

F1-SchemaDefaultTypes

Schema - Default Key

F1-SchemaDispNoneKey

Schema - Conditionally Hide Key

F1-SchemaDispNoneOperator

Schema - Condition Operator

F1-SchemaElementSuppress

Schema - Suppress Element

F1-SchemaElementVisibleOn

Schema - Element Visibility Control

F1-SchemaFlatFieldRowValues

Schema - Flattened Field Row Values

F1-SchemaFlatRowType

Schema - Flattened Row Types

F1-SchemaListOrderBy

Schema - List Order By Setting

F1-SchemaNodes

Schema - Element Types

F1-SchemaPageActions

Schema - Page Actions

F1-SchemaProtectKey

Schema - Protect Key

F1-SchemaSearchBy

Schema - Search By

F1-SchemaSectColumns

Schema - Section Column Display

F1-SchemaSelectKey

Schema - Dropdown Select Key

F1-SchemaXMLNameSpaces

Schema - XML Namespaces

Manual Transition of Sync Request

In a previous release, logic was added to support the ability for a user to manually transition a sync request that is currently in a state with a deferred monitor.

In this release, the action button that appears has been changed from Process Sync to Process Now.

Support Currency Symbol on Number Fields

Elements defined for unit rates typically capture amounts that have a large number of decimal places. The display of these amounts should include a currency symbol. These types of elements cannot be defined as money data types, because the amounts capture in money data types are validated against their currency's decimal configuration.

In previous releases, to display the currency symbol for these types of fields, special logic was required and automatic UI rendering was not possible. In this release, schemas may now define a currency reference for number data types. Automatic UI rendering will include the currency symbol of the referenced currency. The system ignores the currency decimal configuration.

Refer to the Schema Tips on the business object, business service, data area and service script pages for more information.

Web Service Enhancements

This section provides information about web service oriented enhancements.

Support XAI Service Deployment via Inbound Web Services

For implementations using XAI inbound services for external messages, the product recommends moving to the inbound web service mechanism, which uses the J2EE Web Application Server to communicate with the product rather than the XAI servlet.

In this release, the product supplies an interim solution for XAI inbound services that use the Core Adapter. These are XAI inbound services that reference an underlying page service in the product. For these services, converting them to use inbound web services requires a business service to be created for the underlying page service (if one doesn’t already exist). However, the resulting schema produces for a business service differs from the Request and Response schemas for the analogous XAI inbound service (which are created using the Schema Editor). This requires a change to the integration to cater for the deferent schema.

Moving all incoming messages over to use IWS instead of XAI is the product recommendation. However, to aid in implementations that have many integrations in place using the XAI inbound services that use the Core Adapter (or any adapter whose message class is BASEADA), the product provides the ability to deploy these types of XAI inbound services to the J2EE Web Application Server along with the Inbound Web Services.

To take advantage of this capability, you must define a feature configuration option. Under the External Messages feature configuration type, the Support XAI Services via IWS is used to indicate if this feature is supported. Setting the value to true turns on the feature.

Refer to Support XAI Service Deployment via Inbound Web Services in the External Messages chapter of the Administrative User Guide for more information.

MDB in Inbound Web Service

In the last few releases, the Message Driven Bean (MDB) was included in the online server and interfacing into XAI. In an effort to isolate messaging traffic from online traffic for capacity management, the MDB has been moved to the same server as Inbound Web Services to establish an effort to create an integration server. The MDB has been updates to use IWS within the same server. The existing MDB will be supported in this transition.

New System Data Details

This section provides information about new system data delivered in this release that may need to be reviewed for possible impact by implementations, including:

•

New / Updated Application Services

•

System Data Update Details

New / Updated Application Services

ApplicationService

Description

Access Mode

Comments

F1HEALTH

Health Check Portal

Inquire

Provided for the new System Health Check portal.

CILTUSEP

User

System Administrator

New access mode provided to allow implementations to secure changes to the user's user groups independently of other changes to the user.

System Data Update Details

This section highlights miscellaneous changes to system data configuration.

•

The following maintenance objects updates were done to support Configuration Migration Assistant (CMA) functionality:

•

Access Group ( ACCT GROUP) - An option for the option type Non-Migrated Table was added with the value CI_ACC_GRP_DAR. This is a many-to-many relationship between this MO and the Data Access Group MO. For CMA purposes, the MO is now configured to copy this data across only with the Data Access Group.

•

To Do Role (Without Users) ( TO DO RL SC) - An option for the option type Non-Migrated Table was added with the value CI_TD_VAL_ROLE. This is a many-to-many relationship between this MO and the To Do Type MO. For CMA purposes, the MO is now configured to copy this data across only with the To Do Type.

•

The maintenance object Service Task ( F1-SVCTASK) was updated to configure its ILM Eligibility algorithm. This MO was enabled for ILM but did not have the eligibility algorithm configured.

•

The maintenance object Web Service Annotation ( F1-IWSANN) was updated to remove the table F1-IWS-SVC-ANN. This table was incorrectly included in that MO. Although it is a 'many-to-many' table between Inbound Web Service and Web Service Annotation, the information is only maintained on the Inbound Web Service.

•

The lookup F1_BATCH_LEVEL_OF_SERVICE_FLG has been changed to be non-customizable. This was incorrectly marked customizable in a previous release. The product does not support additional values.

•

The description of the lookup value F1SU for field ACCESS_MODE has been changed from Super User to System Administrator.

•

The description of the feature configuration type F1EM was changed from Email Configuration to External Messages. This feature type may be used to define options for other functionality related to external messages.

Deprecation Notices

This section describes items that are deprecated in this release or planned for deprecation in a future release, including:

Deprecated Notices for Oracle Utilities Application Framework 4.3.0.1

•

The table usage flag (TBL_USAGE_FLG) on MD Table (CI_MD_TBL) and the field usage flag (FLD_USAGE_FLG) on MD Table Field (CI_MD_TBL_FLD) will be deprecated in a future release. The fields are not used by the product.

•

Environment Reference. This administrative maintenance object was related to ConfigLab and Archiving, which are no longer supported. In a future release, the following will be removed:

•

Migration Plan F1-EnvironmentRef. Note that no base migration request references this plan. Implementations should ensure that no custom migration request references this plan.

•

Business Object F1-EnvironmentRefPhysicalBO

•

Maintenance Object ENV REF

•

The To Do Type F1-SYNRQ (Sync Request Error) is not in use and will be deleted in a future release. Errors for the Sync Request Monitor (that also has the name F1-SYNRQ) are reported using the To Do Type F1-SYNTD (Sync Request Monitor Errors).

•

The following metadata related to the legacy LDAP import functionality via XAI will be deprecated in a future release:

•

XAI Inbound Service LDAPImport

•

XAI Adapter LDAPImport

•

Message Class (formerly XAI Class) LDAPIMPRTADA

•

The following algorithm types and algorithms provided for the current LDAP import functionality do not include any logic. They will be removed in a future release.

•

Algorithm Type /Algorithm F1-LDAPIMPRT

•

Algorithm Type /Algorithm F1-LDAPPREPR

System Data Deprecation

The following points highlight system data deprecation in this release.

•

The service program EMAILSERVICE (Email Service) is invalid and has been removed. The service program F1-EMAILSERVICE is the valid one provided for the real-time email service functionality.

•

The lookup value F1LR for the algorithm entity flag lookup (ALG_ENTITY_FLG) is invalid and has been removed.

•

The application services F1BTCLSP (Batch Cluster), F1CLTHDP (Batch Cluster Thread Details) and F1CLUSTP (Batch Cluster Portal) have been removed. They were not used for any base functionality.

•

The following zones have been removed. F1-CLSDETAIL (Cluster Details), F1-CLSMEMBER (Cluster Members), F1-CLSTHPOOL (Cluster Thread Pools), F1-CLUSJOBS (Batch Jobs), F1-CLUSTER (Batch Cluster), F1-CLUSTHRD (Batch Threads). They were not referenced by any base functionality.