The release includes:

This section describes the new and enhanced user interface features in this release, including:

The Service History Types zone in the Completion tab of the Work Activity portal lists valid service history types and condition assessment service history types associated to the assessment class for the asset in context or planned service history types for the activity. In this release, this zone allows you to create a service history against only an activity by clicking Add prior to broadcasting an asset row. Previously, you needed to broadcast an asset to view the service history types and you could not create a service history unless Asset or Asset Location was populated.

Additionally, the Asset Service History zone is renamed to Asset Service Histories and the application only displays this zone after you broadcast an asset or asset location. The Activity Service History zone is also changed to Activity Service Histories and is always displayed regardless of if the activity has an asset or not. Previously, the application always displayed the Asset Service History zone and the Activity Service History zone was only displayed if the activity did not have an asset.

No steps are required to enable this feature.

If an activity does not have an asset, the existing Default Location From Asset or Activity on Service History (W1-DEFLOCASH) algorithm copies the asset location and work location to the service history. You can deactivate this algorithm by doing the following:

The GIS Map Viewer allows you to view assets and work information based on geospatial mapping. In the Asset tab, you can now filter assets based on asset characteristics. In the Work tab, the number of entries in the list are displayed together with the number of filters selected. In both these tabs, the filter tooltips show drop-down filter descriptions instead of codes. The GIS Map Viewer also provides a Clear List shortcut that quickly removes all selected assets from the list.

No steps are required to enable this feature.

The new GIS Map Viewer brings a complete Redwood user experience, the existing Legacy Map Viewer features, and the following additional functions:

In this release, the GIS Map Viewer uses the latest ESRI ArcGIS JavaScript API and Oracle JET. Previously, the map viewer was built on the ArcGIS JavaScript version 3 API.

No steps are required to enable this feature.

Access to the new GIS Map Viewer is via the W1GISMAP application service.

The application automatically gives access to the new GIS Map Viewer to users with access to the Legacy GIS Map Viewer.

Saved asset filters are accessible in the enhanced GIS Map Viewer.

The recommended system requirements for the enhanced GIS Map Viewer are as follows:

A new parameter Allow Employees To Approve Own Timesheet is introduced in the Work Management Master Configuration. If the value is blank or No, employees cannot approve their own Timesheet. If Yes, employees can approve their own Timesheet.

This gives you control over whether employees are allowed to approve their own timesheets even though they are approvers on the approval profile.

To enable this feature, set the Allow Employees To Approve Own Timesheet parameter in the Work Management Master Configuration according to your business rules.

This section describes the new and enhanced asset management features in this release, including:

The new Automated Number zone in the Main tab of the Asset Type portal enables you to configure the asset type to automatically generate an asset number and/or badge number for a new asset. For auto-generated numbers, you can assign custom or calendar prefixes and set the length of the numbering sequence. Using a calendar prefix inserts the current year into the auto-generated number and the sequence number resets to zero at the beginning of each calendar year.

These fields facilitate the configuration of an asset type's auto-generated number settings:

No steps are required to enable this feature.

The Cycle Now button in the Maintenance Trigger zone of the Maintenance tab in Asset portal enables any user to skip pre-configured rules for asset preventive maintenance and force the running of a preventive maintenance trigger to create a maintenance work order. The "W1-ASSET" application service for Asset MO now provides a "Maintenance Trigger Force Execution" access mode that limits the use of the Cycle Now button to user groups assigned with the new access mode.

This grants control to users that are only authorized to force preventive maintenance triggers of cycling assets.

No steps are required to enable this feature.

System administrators should grant "Maintenance Trigger Force Execution" access to the appropriate user group(s) in the "W1-ASSET" application service.

The Transition Planned Asset to In Service (W1PLANDSTRN) algorithm provides customers with the capability to automatically transition the status of new non-tracked, non-inventory assets to "In Service" from "Planned". Previously, only assets created through the ESRI GIS integration were given the option to automatically transition from the "Planned" to "In Service" status.

The algorithm is available in the Planned In/Out of Service Asset Root business object and its default setting is a "No" transition (meaning assets stay in planned status). You can automatically transition the asset status from "Planned" to "In Service" using the following parameters:

No steps are required to enable this feature.

The Asset Location Attribute Types field of the Asset Location Types portal enables you to store GIS-like attribute information.

As a result, you no longer need to create custom Asset Location business objects to store GIS-like attributes.

No steps are required to enable this feature.

The Update Fixed Asset Information (W1UF) access mode enables you to manually create or update a fixed asset without a construction work activity or compatible unit. The Send Fixed Asset Information (W1SF) access mode allows you to send the created or updated fixed asset information to an external system. Previously, the application only supported the creation or update of fixed assets via Construction Work Activity or Received/Accepted Capital Spare Items.

System administrators should grant Update Fixed Asset Information (W1UF) and Send Fixed Asset Information (W1SF) access to the appropriate user group(s) in the application services of Asset business objects.

You can now configure asset attributes by asset type on Engineering Specifications. Previously, new Engineering Specification business objects were needed and created to configure asset attributes on asset types.

You do not have to create Engineering Specification business objects to capture different asset attributes.

No steps are required to enable this feature.

You can move "Rejected" or "In Repair" tracked assets to the "In Receipt" status. This bypasses the "In Store" status. Previously, when "In Receipt" tracked assets encountered failures, the application moved these assets to the "Rejected" or "In Repair" status only and the assets were returned to the vendor.

This reduces implementation costs.

No steps are required to enable this feature.

The tree views of the Organization and Asset Location portals now display the entire organization and location structures respectively, and the direct parent/child hierarchy. Additionally, both tree views load more efficiently in this release. Previously, the Organization and Asset Location tree views only displayed direct hierarchy, which included its child organizations and locations.

No steps are required to enable this feature.

The 360 tab on the Asset portal serves as a comprehensive summary hub that provides a centralized view of all relevant information about a specific asset. By consolidating data and insights in one location, it offers a clearer understanding of the events and actions associated with that asset. This streamlined approach eliminates the need to navigate across multiple portals or click through various links to gather similar information, facilitating more efficient decision-making and management.

The following zones are available in the 360 tab:

The Asset 360 tab is the default tab for the Asset portal once an asset is selected. You are given an option to opt out of the 360 default tab and make the Main tab the default on a system-wide basis or at the user-level.

To enable this feature, refer to the Asset 360 Configuration and Setting the Asset Portal Default Tab sections of the Administrative User Guide for more information.

Asset search provides the capability to select a Predefined Characteristic Type query filter from options that are sorted alphabetically by description. The Asset Attributes zone also uses Predefined Characteristic Type, providing you a list of attributes during editing that are sorted and displayed alphabetically by description.

This enhances the user experience by displaying Predefined Characteristic Types drop-down values by description and in alphabetical order, making the selection in Asset Characteristic search and editing in Asset Attributes easier.

No steps are required to enable this feature.

The Detailed Description field (with a 4000 character limit) in the following Asset Location business objects enables you to provide a clearer and comprehensive asset location description:

Also, the Asset Location search now enables you to search records with detailed descriptions using the Description filter.

No steps are required to enable this feature.

You can now assign sequence numbers for valid attributes on an asset type for assets and specifications for that asset type. Those attributes on assets and specifications will be displayed in the order of the sequence numbers.

This gives you control of the order in which attributes are displayed.

No steps are required to enable this feature.

Reading Date/Time now defaults to the current date/time to ensure Measurement records accurately reflect the date and time the measurement was taken. Previously, when a Measurement record was created, the Reading Date/Time defaulted to a blank field, requiring the date and time to be manually selected and usually defaulted to 12:00 AM. In situations where the default date and time were not revised, this made the record incorrect.

This ensures Measurement records accurately reflect the date and time when the measurement was taken.

No steps are required to enable this feature.

This portal is a streamlined version of the Work and Asset Management asset portal and includes only the tabs relevant to Operational Device Management assets:

This improves the user experience. It focuses you on only relevant Operational Device Management-related information.

Users must be granted "Inquire" access to the Operational Device Management Asset Portal (W1ODMAST) application service to use this feature.

The Operational Device Management Asset portal is secured by the Operational Device Management Asset Portal (W1ODMAST) application service. You must be granted Inquire access to view this page.

The following Operational Device Management asset business objects are impacted by this change:

To opt out of the Operational Device Management Asset portal and continue using the Work and Asset Management Asset Portal for Operational Device Management assets:

The character limit of the Service History Comments field is now 4000, addressing the need for more detailed record-keeping and overall usability. Previously, the character limit was 254. This update aligns with the requirements for improved documentation and operational efficiency.

This provides the capability for more detailed and comprehensive record-keeping.

No steps are required to enable this feature.

This section describes the new and enhanced batch processing features in this release, including:

Currently, attachments are stored in the database along with its entire content in a CLOB field. This poses a problem for uploading and maintaining very large attachments, such as videos and so on. The Application Framework has been enhanced to store content of large files in Oracle Cloud Object Storage based on a configurable file size threshold (current default is 20MB), however the Loader can only process content in the database. A validation is put in place such that only attachments stored in the database can be referenced on an Online or Batch Loader Request Type. If your organization takes advantage of object storage and the .csv file you try to load is above the file size threshold, you need to split it into smaller files and upload those smaller files separately.

This provides validation upfront before you submit the batch job 'W1-GAUPL' and encounter errors if the actual attachment data is not stored in the database of the application because of its size.

No steps are required to enable this feature.

This section describes the new and enhanced inventory features in this release, including:

All items of the same stock item in a storeroom should be assigned an Average Unit Price (AUP). Unlike regular stock items, trackable stock items use asset disposition to track inventory quantity and the average unit price is captured on each asset. Repairable stock items can be assigned "Repaired Prices" when returned to the inventory. The assigned repaired price for the repaired item is used for financial transactions (like increase of inventory value) when a repaired asset is returned to a storeroom and impacts the average unit price of the stock item. Also, the AUP Contribution Amount on assets of that stock item in the storeroom gets updated to match the AUP and prevents the AUP from changing after assets are issued at a later time.

This accurately tracks inventory value for repaired and returned tracked assets.

No steps are required to enable this feature.

The Accept on Receipt parameter of the Receiving Inventory process instructs the application whether to receive and accept the item at same time (set to Yes) or receive and accept the item separately (set to No and a multi-step receiving process occurs). For purchase orders with several line items, multi-step receiving is tedious to complete as it involves several mouse clicks and page loads. This release provides an "Accept All Pick List" option to reduce the completion steps of multi-step processing for regular inventory items. The option includes the Receive All and Accept Regular Inventory and Receive All and Accept Regular Inventory (Batch) links, which appear in the Additional Processes section of the receipt. The Receive All and Accept Regular Inventory (previously Receive and Accept All Regular Inventory) process fully receives and accepts all the regular inventory items but excludes those that are individually not selected. The Receive All and Accept Regular Inventory (Batch) process is recommended for receiving large numbers of purchase orders and is similar to the first process, but the difference is that the items are submitted automatically via a batch job.

Additionally, the Receipt portal provides a new Activity tab that displays the Purchase Order Line Activity zone. Previously, the zone appeared in the Main tab of the portal.

No steps are required to enable this feature.

The application only presents the "Accept All Pick List" if the receipt has at least one regular inventory item that will go through the multi-step receiving (the corresponding Accept on Receipt parameter is set to No). Otherwise, the application does not display the UI and fully receives and accepts all regular inventory items.

If needed, you can submit the Receive All and Accept Regular Inventory batch job in debug mode (trace output enabled). To turn on the batch debug mode, complete these steps:

To turn off the batch debug mode:

System administrators should grant user groups with the Execute access to the W1RCACAL application service in order to run the W1RCACAL batch control, which handles the receive and accept batch processing.

The Receive All and Accept Items (online and batch) links in the Additional Processes section of the Receipt portal can now process non-inventory items, such as direct purchase and expense at receipt. The Accept on Receipt parameter of the Receiving Inventory process instructs the application whether to receive and accept inventory and non-inventory items at same time (set to Yes) or receive and accept the items separately (set to No and a multi-step receiving process occurs). The Accept All Pick List option that reduces the completion steps of multi-step processing for regular inventory items now also applies to non-inventory items. Previously, only regular inventory items were processed by the Receive All and Accept Items links.

No steps are required to enable this feature.

The Purchase Order search filter in the Return search portal has been improved to utilize the PO header search instead of the PO line search. This upgrade allows users to search for returns associated with the entire PO, eliminating the need to examine one PO line at a time.

Additionally, the Return search option has been added to the PO context menu, reducing clicks needed to access the Return search portal.

No steps are required to enable this feature.

The application now displays in the Physical Inventory Header zone the number of items selected by the system and the number of discarded items in the Items Summary zone. Previously, you could specify various criteria on a Physical Inventory Count Header and the system would select the stock items accordingly. You could also manually discard the items from being included in the actual count.

This provides high-level statistics information about a physical inventory.

No steps are required to enable this feature.

This section describes the new and enhanced purchasing-related features in this release, including:

The calculation rules for the Blanket Contract Used Amount now consider scenarios of unfulfilled orders or items received/accepted exceeding the original number of orders. The calculation rules take into account whether the blanket contract consists of a Blanket Purchase Agreement (contract with items) or Contract Purchase Agreement (contract without line items). For a blanket purchase agreement, the Blanket Contract Used Amount calculation rules only include purchase order line items that reference any of the blanket contract's line items. For a contract purchase agreement, the calculation rules include all of the purchase order's line items that reference the blanket contract. After determining the purchase order line items, these rules are applied to calculate the PO Line Contributed Amount (POLCA), which is summed up as the Blanket Contract Used Amount:

Previously, the calculation rules for the Blanket Contract Used Amount were as follows:

However, if the purchase order was completed but all the order was not fulfilled, the calculation rules did not adjust the Blanket Contract Used Amount to reflect the unfulfilled orders.

No steps are required to enable this feature.

This release extends the decimal limit of the Unit Price field to seven places for purchase orders, purchase requisitions, and blanket contracts. Previously, the limit was two or three decimal places depending on the currency used.

This captures a more accurate unit price value.

No steps are required to enable this feature.

When you create a Purchase Order or a Blanket Contract from a Purchase Requisition, notes and standard notes from the Purchase Requisition header and lines are copied onto the header and lines, respectively, of the Purchase Order or Blanket Contract.

This makes creating Purchase Orders or Blanket Contracts more efficient.

No steps are required to enable this feature.

When you create a Purchase Requisition or a Purchase Order from a Blanket Contract, notes and standard notes from the Blanket Contract header and lines are copied onto the header and lines, respectively, of the Purchase Requisition or Purchase Order.

This makes creating Purchase Requisitions or Purchase Orders from Blanket Contracts more efficient.

No steps are required to enable this feature.

When you create a Purchase Order revision or a Blanket Contract revision, the notes and standard notes from the previous revision's header and lines are copied onto the header and lines, respectively, of the new revision.

This makes creating Purchase Order revisions and Blanket Contract revisions more efficient and avoids audit issues.

No steps are required to enable this feature.

Easily back out all the financial impact of the original invoice by creating a credit memo and specifying an amount for freight and extra cost on a credit memo invoice header. You can also choose to prorate the freight and extra cost to credit memo lines.

This allows you to credit back freight and extra cost when creating a credit memo.

No steps are required to enable this feature.

Creating a new purchase order revision automatically carries over the attachments from the originating revision to the new revision.

This makes purchase order revisioning easier and more accurate.

No steps are required to enable this feature.

This section describes the new and enhanced resource management features in this release, including:

The Employee zone of the Timekeeper portal now sorts and displays the Employee list by last name then by first name. Previously, the zone sorted records by Employee ID.

This improves the user experience.

No steps are required to enable this feature.

The W1_PARENT_ORG_MT_VW materialized view is regularly refreshed in both staging and production environments using a DBMS scheduler batch job. However, this refresh process, which completely refreshes the data, is causing performance delays. To mitigate this issue, all crew shift schedules and work planning search queries that use the materialized view have been redesigned and no longer rely on this materialized view.

Rework work planning and crew shift schedule search queries to bypass the materialized view improves performance and reducing resource consumption.

No steps are required to enable this feature.

Due to the redesign of the work planning and crew-shift schedule queries, the W1_PARENT_ORG_MT_VW materialized view is no longer needed and has been removed. Customers should review their custom code and remove any references to the W1_PARENT_ORG_MT_VW materialized view. Specific base package zones that have been impacted by this change include the following:

The all-in-one Timekeeper portal has been separated into a Search portal and a Maintenance portal. The Owning Organization field has also been added to the Timekeeper record. When the Owning Organization field on a Timekeeper record is specified, only users with that Owning Organization can search for, thus view and update that Timekeeper record.

No steps are required to enable this feature.

New Timekeeper search portal along with a new application service 'W1TMKPRQ' is introduced. All users with access to the existing all-in-one portal for Timekeeper are automatically given access to the Timekeeper search portal through this application service.

On the Activity Resource Requirement's Quick Add and Activity Resource maintenance, you can modify the Expense Code value. However, when the resource type's Default Values to Activity flag is set to "Yes", the Expense Code should not be changed from the resource type's value. In this release, each of the Activity Resource Requirement business object's Application Services and the WAM_SERVICES user group includes the Override Expense Code access mode, preventing the Expense Code to be change to the resource type's value when the Default Values to Activity flag is set to "Yes".

Provide the required access before using the feature.

System administrators should grant "W1OE- Override Expense Code" access to the appropriate user group(s) in the following application services:

You can now delete compatible units when a construction work activity is at an "Approved", "Active", "In Progress", "Sent", or "Sent In Progress" status. Planned assets existing under the deleted compatible unit will be deleted. Also, when the deleted compatible unit is the only contributor to an Activity Resource Requirement, the application cancels that activity resource requirement.

Previously, compatible units could only be deleted when the construction work activity was at a "Planning" status. Also, after the construction work activity had been approved and the compatible unit was not needed anymore or no work was carried out for the compatible unit, you could update the Actual/Completed Quantity to zero for the deleted compatible unit.

No steps are required to enable this feature.

This section describes the new and enhanced work management features in this release, including:

The Maintain Work Order Activity (W1-WOACTAMSG) and Cancel Work Order Activity (W1-WOACTFMSG) outbound message types enable you to route construction work activities to an external system for scheduling and execution.

By setting configurations at each construction work activity type level, a construction work activity can be routed to an external system for scheduling and execution.

To enable this feature, complete these steps:

System administrators should grant access to the Construction Work Activity BO application service to any user that routes construction work activities to external systems.

The Construction Work Activity portal enables you to maintain a construction work activity record. The new Planned Service History Type zone in the Main tab allows you to add a mandatory or optional planned service history type to the record. The Activity Type portal allows you to maintain activity types, which represent a broad range of activities like maintenance, repairs ,and inspections. The Activity Type zone in its Main tab enables you to define the main attributes of a planned service history. In this release, the application copies all planned service history types from the activity type to the created construction work activity record. If the activity is routed to an external system, the activity outbound details include the planned service history types.

No steps are required to enable this feature.

You can now select template construction work activities from a template construction work order and add these work activities to an existing construction work order. You can perform this action by using the Add Activities from Template Construction Work Order option in the Activity Information zone of the Construction Work Order portal. Previously, a construction work order was only created from a complete copy of a template construction work order through the Create Construction Work Order button of the Template Construction Work Order portal.

No steps are required to enable this feature.

This release enables the application to assign the estimated cost of a Compatible Unit as the default value of customer-contributed assets during the creation of a work activity reconciliation. Previously, you can only manually enter a customer-contributed asset value at the end of the construction work activity.

This provides default customer-contributed asset values at the end of construction work activities.

No steps are required to enable this feature.

A template construction work activity now includes a Planned Service History Type, Duration, and Unit of Time. You can mark the planned service history type as "Optional" or "Required".

These align the elements of the template construction work activities with the regular template and work activities.

No steps are required to enable this feature.

The Activity Dependency zone of the Construction Work Activity portal lists the active construction work activities that are dependent on the current construction work activity record. This zone provides the new resource option, Same (W1SM), which indicates that the crew or shift assigned to the activity must be the same as the crew or shift working on the dependent activity. Previously, the resource options provided by the zone were as follows and the crew or shift working on the activity had to be different from the dependent activity:

No steps are required to enable this feature.

The Backlog Group fields in the Construction Work Activity and Template Construction Work Activity portals enable you to add backlog group information to construction activities and templates. Additionally, a construction work activity created using a template with a defined backlog group automatically inherits that group. Previously, backlog group information can only be added to a regular work order and work order template.

This provides consistency between the creation of regular and construction work activities.

No steps are required to enable this feature.

The Work Location zone now includes a Service Area field, enabling you to define a logical boundary for your organization's service territory.

This enables you to assign the appropriate crew or shift to a work location.

No steps are required to enable this feature.

The application can now process interim completion information sent by Oracle Field Service or an external system. The application keeps the construction work activity in its current "In Progress" state and processes the interim completion of other activities like asset installation/removal, service histories and measurements creation, and construction location update. When the application resends the activity to the crew, the activity details reflect all the work and interim completion for the activity. Previously, the mobile construction work activity completion service assumed a completed work activity when Oracle Field Service or the external system sent the activity information to the application.

No steps are required to enable this feature.

This section describes the new and enhanced inbound and outbound web services and integration features in this release, including:

The integration between Oracle Utilities Work and Asset Management and Oracle Fusion Cloud Project Management enables you to:

To enable this feature, refer to the Oracle Utilities Work and Asset Cloud Service Integration to Oracle Assets Configuration Guide for more information.

The synchronization of GIS feature classes to Oracle Utilities Work and Asset Management could be defined through the Filter Statement Builder or the default "Skip" behavior. Previously, all GIS feature classes were synchronized to Oracle Utilities Work and Asset Management except those marked as "SKIP". With the Filter Statement Builder, you can synchronize GIS feature classes whose GIS field-value combination match that of the WAM Sync Mapping extendable lookup.

This provides flexibility in configuring GIS Field and GIS Value with various comparison operators and data types, which enables the generation and submission of a filter statement to retrieve a subset of records from GIS tables.

To enable this feature, complete these steps:

This feature is not supported with the "Work and Asset Management to Geographic Information System Integration - File Based Synchronization Process" feature described elsewhere in these release notes.

The ESRI ArcGIS Field Maps-Oracle Field Service integration extends the capabilities of the Oracle Field Service mobile solution by bridging the following key GIS functionality from ArcGIS Field Maps:

Additionally, Oracle Integration Cloud Service facilitates the integration, utility-specific workflows are accessible from both ESRI ArcGIS Field Maps and Oracle Field Service, and data synchronization between the ArcGIS ESRI geodatabase and Oracle Work and Asset Management provides asset information.

To enable this feature, refer to the Oracle Utilities Work and Asset Cloud Service Integration to Oracle Field Service Configuration Guide for more information.

In this release, the Mobile Activity Completion (W1–MblActCom) API accepts construction work activity completion information such as asset installation, asset removal, service histories creation, measurements creation, and construction location details updates from an external system. The construction work activity is automatically completed once Oracle Utilities Work and Asset Management records all the completion information. In addition, a complete integration solution is now available for construction work activities - Oracle Utilities Work and Asset Management initiates construction work activity, it sends all the necessary construction location and compatible unit information along with the required actions to the external system, W1–MblActCom sends fieldwork information completed in the external system to Oracle Utilities Work and Asset Management automatically records the fieldwork information and completes the activity. Previously, all construction work activity tasks performed in an external system were manually entered in Oracle Utilities Work and Asset Management.

To create completion events from the Mobile Activity Completion API, add the following completion event types to the activity's activity type:

System administrators should set/grant users/grant access to the Execute Completion Events and Completion Error access modes to process completion events from an external system.

The Mobile Activity Completion (W1–MblActCom) inbound web service now accepts additional updates for asset identifiers (badge number, asset number, and serial number) and asset attributes.

This provides additional updates for asset identifiers and asset attributes.

No steps are required to enable this feature.

The existing Get Asset Details (W1GAstDtlBNo) inbound web service has been enhanced to provide callers with the following options:

A new Get Question and Answer (W1GetQstnAns) inbound web service has been created which returns the questions and answers for a specific Service History.

No steps are required to enable this feature.

The Mobile Storeroom Inventory (W1-MOBILESTOREROOMINVENTORY) inbound web service now includes the asset type for each asset in the inventory. This enables field workers to select the correct asset by matching the asset type on the compatible unit with the asset needed for construction work.

This helps field workers select the right asset by matching the asset type with the one needed for construction work.

No steps are required to enable this feature.

The Activity Assets and Truck Items pages have been added to Oracle Field Service Accelerator for Oracle Utilities Work and Asset Management. These pages can be used instead of the standard Assets and Equipment pages.

The Activity Assets page displays the locations and assets, including components, related to the activity:

The Truck Item page displays the assets, including components, and items related to the trucks that are included in the activity:

Asset or item actions can be performed directly from a list entry. This removes the necessity of navigating first to the Asset or Equipment Details pages before performing these action. The actions available for a location, asset, or item in the Activity Assets or Truck Items pages depend on the location, asset, or item’s current state.

To enable this feature, refer to the Oracle Utilities Work and Asset Cloud Service Integration to Oracle Field Service Configuration Guide for more information.

The status of the Craft, Equipment, and Miscellaneous resource types are now included in the Admin Sync inbound web service.

This notifies the external system of any previously synchronized resource types that have been deactivated.

No steps are required to enable this feature.

The new file-based synchronization process works with any Geographic Information System (GIS) vendor to load Geographic Information System data into Oracle Utilities Work and Asset Management. This process requires the data to be in GeoJSON newline-delimited format and uses fewer batches to create or update asset and asset locations in Work and Asset Management. GIS File Upload (W1GISUPL) batch control has been introduced to create composite sync requests from the GeoJSON newline-delimited file. Asset and asset location are either created or updated from the composite sync requests. Compared to the Legacy Geographic Information System Integration, this new process requires fewer batches to complete the synchronization.

Additionally, this release includes a W1-GISIntegrationConfiguration admin sync API. This API provides the Geographic Information System to Oracle Utilities Work and Asset Management mapping information needed for file-based integration with external systems.

To enable this feature, refer to the GIS File-Based and Legacy GIS Documentation for more information.

The GIS File Upload batch control is secured by the GIS File Upload (W1GISUPL) application service.

System administrators should grant Execute access to the GIS File Upload (W1GISUPL) application service to any user that will run the batch control.

The Get Asset Details (W1GAstDtlBNo) inbound web service includes the following options:

Also, the existing External Mobile Control Data (W1-ExtMobileControlData) inbound web service now retrieves Measurement Types and Service History Types.

No steps are required to enable this feature.

The Material Issue API facilitates the communication of material issues from Oracle Fusion Supply Chain Management to Oracle Utilities Work and Asset Management. Once the material issue is created in Oracle Utilities Work and Asset Management:

Oracle Fusion Supply Chain Management will update the inventory quantity and average unit price of the stock item detail through the Add Inventory Adjustment API.

No steps are required to enable this feature.

The Admin Sync integration process sets the crafts, equipment, and other resources used in the Oracle Field Service accelerator for Oracle Utilities Work and Asset Management to active or inactive based on the state of the corresponding resource type in Oracle Utilities Work and Asset Management.

Timesheets, equipment usage, and other usage entry in the Oracle Field Service Accelerator for Oracle Utilities Work and Asset Management limits the crafts, equipment, and other resources available for selection to only those that are active.

No steps are required to enable this feature.

Rules and processes were implemented to support a productized integration of fixed asset information to Oracle Assets. Additional fields (for example, account segments and project related fields) are now sent to Oracle Assets.

These provide additional support for fixed assets integration with Oracle Assets.

To enable this feature, refer to the Oracle Utilities Work and Asset Cloud Service Integration to Oracle Assets Configuration Guide for more information.

The enhanced Work Activity API enables you to pass additional asset information, such as asset attributes, asset numbers, and serial numbers to an external system. With this information, crews can add or update asset attributes and (if permitted) badge numbers, asset numbers, and/or serial numbers. If a crew is specified on the activity, the API passes the information to the external system as the preferred crew and the external system may use or override the preferred crew when scheduling the activity.

No steps are required to enable this feature.

The following user-defined fields were added to the Work Activity API to enable you to send custom information to an external system:

This reduces implementation and support costs.

To enable this feature, complete these steps.

Refer to the sample custom algorithm in the Master Demo environment.

In this release, the Oracle Utilities Work and Asset Management-Oracle Field Service integration enables you to review in Oracle Field Service the asset attributes of a work activity created in Oracle Utilities Work and Asset Management.

This extends the work activity information available in Oracle Field Service.

To enable this feature, refer to the Oracle Utilities Work and Asset Cloud Service Integration to Oracle Field Service Configuration Guide for more information.

You can now configure your application to pass the backlog group information of a work activity to an external system. Previously, work activity was assigned to an admin bucket on the external system based on the activity's service area. In some cases, the admin bucket was more similar to the activity's backlog group than the service area that was most likely defined geographically.

This provides external systems with the flexibility to configure where to assign the backlog group information.

No steps are required to enable this feature.

The Exclude Questionnaire Details and Exclude Failure Information parameters in the Integration Parameters section of Work Management Master Configuration provide the option to send the outbound activity message, questionnaire details, and failure information separately. Previously, the application passed all the questions and answers, and failure information for the asset to the external system via the activity outbound message.

Sending the message and information separately prevents integrations from failing due to large message sizes.

To enable this feature, complete these steps:

When recording the installation of a tracked asset in Oracle Field Service as part of a construction work activity, the asset to be installed can be identified by either of the following:

This provides more flexibility around how assets are installed for construction work activities.

To enable this feature, refer to the Oracle Utilities Work and Asset Cloud Service Integration to Oracle Field Service Configuration Guide for more information.

A 'Manually Discarded' status, which has its own access mode 'W1MD', has been added to the following outbound sync request business objects:

This gives the ability to manually cancel an outbound sync request when it is not needed anymore, for example, the corresponding update has been manually made in the target system.

System administrators should set/grant users/grant access to the new access mode 'W1MD' to application services of the mentioned outbound sync request business objects.

To support demand forecasting and replenishment planning within supply chain management, the Stock Item Detail Demand Extract (W1SIDDEX) batch control relays material demand information in Oracle Utilities Work and Asset Management to Oracle Fusion Supply Chain Management.

This batch control creates an extract file containing all Stock Item Details with planned demand and Required By Dates in the future. Oracle Fusion Supply Chain Management uses this information for effective forecasting and replenishment planning. Refer to the Enterprise Resource Planning Integration Master Configuration Demand Forecasting settings for Lead Time (Days), High Demand, and the Additional Demand Calculation setting that define demand quantity calculation. Stock Item Details with an ABC Class of A, B, or C will also be included in the extract, regardless of the Master Configuration settings.

In addition, the Manage Stock Item Detail API has been enhanced to accept ABC Class and Lead Time (Days) information from an external system. This information is used when generating the extract file that is sent to Oracle Fusion Supply Chain Management.

No steps are required to enable this feature.

The Stock Item Detail Demand Extract batch control is secured by the Stock Item Detail Demand Extract (W1SIDDEX) application service. Users must be granted Execute access to run this batch control.

System administrators should grant Execute access to the Stock Item Detail Demand Extract (W1SIDDEX) application service to any user that will run the batch control.

This section describes the new and enhanced implementation tools features in this release, including:

In previous releases, enabling Oracle Utilities Work and Asset to connect to the ESRI Geodatabase and webservices the configuration file deployed in GIS must have the owner of the DEFAULT version in the ESRI Geodatabase and an Admin user of ArcGIS Server. As of this release, the configuration file can be configured with any ERSI Geodatabase user having access to the required feature classes. In addition, the ArcGIS Server user need not be an Admin user to access ArcGIS Server services.

This allows the use of non-admin users for GIS-Work and Asset integrations and supports implementations with policies that do not grant owner or admin users access rights to regular business processes.

To enable this optional feature for a Geodatabase user: