Update 21D

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date	Product	Feature	Notes
17 SEP 2021			Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.

Security and New Features

The Role section of each feature identifies the security privilege and job role required to use the feature. If feature setup is required, then the Application Implementation Consultant job role is required to perform the setup, unless otherwise indicated. (If a feature doesn't include a Role section, then no security changes are required to use the feature.)

If you have created job roles, then you can use this information to add new privileges to those roles as needed. For details about how to compare your configured job roles to predefined job roles and add security artifacts to your configured job roles, see the Security Console and Roles and Role Assignments chapters in the Oracle SCM Cloud: Securing SCM guide on the Oracle Help Center.

HAVE AN IDEA?

We’re here and we’re listening. If you have a suggestion on how to make our cloud services even better then go ahead and tell us. There are several ways to submit your ideas, for example, through the Ideas Lab on Oracle Customer Connect. Wherever you see this icon after the feature name it means we delivered one of your ideas.

GIVE US FEEDBACK

We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com.

DISCLAIMER

The information contained in this document may include statements about Oracle’s product development plans. Many factors can materially affect Oracle’s product development plans and the nature and timing of future product releases. Accordingly, this Information is provided to you solely for information only, is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle.

This information may not be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. Oracle specifically disclaims any liability with respect to this information. Refer to the Legal Notices and Terms of Use for further information.

Pre-Update and Post-Update Tasks

Depending on the features you're using in your Cloud applications, you may be required to perform certain steps immediately before or after your quarterly update. For details of these pre-update and post-update steps and the product areas that are affected, refer to Oracle SCM Cloud: Performing Your Quarterly Update (doc ID 2337485.1) on My Oracle Support.

Optional Uptake of New Features (Opt In)

Oracle Cloud Applications delivers new updates every quarter. This means every three months you'll receive new functionality to help you efficiently and effectively manage your business. Some features are delivered Enabled meaning they are immediately available to end users. Other features are delivered Disabled meaning you have to take action to make available. Features delivered Disabled can be activated for end users by stepping through the following instructions using the following privileges:

• Review Applications Offering (ASM_REVIEW_APPLICATIONS_OFFERINGS_PRIV)
• Configure Oracle Fusion Applications Offering (ASM_CONFIGURE_OFFERING_PRIV)

Here’s how you opt in to new features:

1. Click Navigator > My Enterprise > New Features.
2. On the Features Overview page, select your offering to review new features specific to it. Or, you can leave the default selection All Enabled Offerings to review new features for all offerings.
3. On the New Features tab, review the new features and check the opt-in status of the feature in the Enabled column. If a feature has already been enabled, you will see a check mark. Otherwise, you will see an icon to enable the feature.
4. Click the icon in the Enabled column and complete the steps to enable the feature.

In some cases, you might want to opt in to a feature that's not listed in the New Features work area. Here's how to opt in:

1. Click Navigator > My Enterprise > Offerings.
2. On the Offerings page, select your offering, and then click Opt In Features.
3. On the Opt In page, click the Edit Features (pencil) icon for the offering, or for the functional area that includes your feature.
4. On the Edit Features page, complete the steps to enable the feature.

For more information and detailed instructions on opting in to new features for your offering, see Offering Configuration.

Opt In Expiration

Occasionally, features delivered Disabled via Opt In may be enabled automatically in a future update. This is known as an Opt In Expiration. If your cloud service has any Opt In Expirations you will see a related tab in this document. Click on that tab to see when the feature was originally delivered Disabled, and when the Opt In will expire, potentially automatically enabling the feature. You can also click here to see features with Opt In Expirations across all Oracle Cloud Applications.

Feature Summary

Maintenance

Maintenance

Connect Your Installed Base Assets and Fixed Assets

Sometimes, the maintenance cost incurred on the installed base asset increases the asset value and needs to be appropriately updated in the asset book. To initiate the cost transfer from maintenance to financial application, the fixed asset context is needed for adding the value. Hence, it's imperative to have an association between the installed base asset and fixed assets.

With this update, you can define a relationship between an installed base asset and many fixed assets. Each relationship will have a valid date range. If a relationship is end dated, the same fixed asset can be added again without overlapping dates with the previous associations.

Edit Asset UI > Fixed Asset Tab

Establishing a relationship between your installed base assets and its corresponding fixed assets enables you to have the complete picture of the asset.

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Manufacturing and Supply Chain Materials Management  No Longer Optional From: Update 22B

Tips And Considerations

For creating relationship between fixed assets to an installed base asset, a fixed asset corporate book needs to be associated to the asset operating organization. This setup is done in the Edit Inventory Organization page, where a new field, Fixed Asset Corporate Book, is added.

Inventory Organization Parameters

When the asset operating organization is updated, all the existing fixed asset relationships are validated against the fixed asset corporate value in the new operating organization. All invalid relationships are end dated automatically.

For creating relationships, only the fixed assets of type CIP and Capitalized are considered.

Create a Work Order for an Asset from the Asset Hierarchy

With this feature, you can create work orders for your assets as you review the asset hierarchy on the Hierarchy Navigator page. Use the new Create Order button on the  header to create a work order for the selected asset. Click the button to open the Create Maintenance Work Order dialog box and enter the details for the work order. The asset field is filled by default with the value of the selected asset. After you enter other details for the work order in the dialog box, you have two options:

• Save and Close: Use this button on the Create Maintenance Work Order dialog box to return to the Hierarchy Navigator page. When you refresh this page, you'll see a new Review Work Order icon in the work order column for the context asset. Click the icon to go to the Manage Work Orders page that displays a list of orders in Unreleased and Released statuses.

• Save and Edit: Use this button to go to the Edit Work Order page for the newly-created work order. You can update your work order as you like, and even release it. Click the Save and Close button or the Cancel button to return to the Hierarchy Navigator page.

Your Create Work Order button is disabled for a selected hierarchy row in some cases, such as these:

• The row is the hierarchy name.
• The asset's is defined with the Create Work Order check box deselected.
• The asset is a logical asset that was created based off a BOM explosion during asset creation.
• The asset's item isn't enabled in the contextual maintenance organization for which you are viewing the logical hierarchy.
• The asset's definition doesn't include an item and is only a description-based asset.

With this update, you can create a maintenance work order without losing the context of the asset you want to maintain. You can also oversee your work load directly from the Hierarchy Navigator page using the new Review Work Order icon link.

Steps to Enable

You don't need to do anything to enable this feature.

Role Information

• Predefined job role name and code:
  • Asset Administrator (ORA_CSE_ASSET_ADMINISTRATOR_JOB)
  • Maintenance Manager (ORA_MNT_MAINTENANCE_MANAGER_JOB)

• Privileges:
  • Manage Customer Assets (CSI_MANAGE_CUSTOMER_ASSETS_PRIV)
  • Manage Maintainable Assets (MNT_MANAGE_MAINTAINABLE_ASSETS_PRIV)
  • Manage Maintenance Work Orders (MNT_MANAGE_MAINTENANCE_WORK_ORDER_HEADERS_PRIV)
  • Manage Maintenance Work Order Operations (MNT_MANAGE_MAINTENANCE_WORK_ORDER_OPERATIONS_PRIV)

Create Meter Readings Using File-Based Data Import

You can now create meter readings using a new file-based data import (FBDI) process called Import Meter Readings. This process supports only the creation of new readings that are sequential by date/time and meter-type validations. The readings are entered in a new FBDI spreadsheet template, supporting both asset-based meters and meters that are defined for subscriptions. This new process is useful for the loading of historical readings, as well as the routine capture and import of ongoing readings for a group of assets or subscriptions.

Each row of the new template corresponds to a sequential reading that references a unique import batch code and interface record number. For each reading, a combination of either an asset number and meter code, or a subscription product PUID value and meter code is required. These combinations allow the process to resolve to a unique meter for the asset or subscription. The reading date/time and reading value are required and reading comments can be optionally entered to provide context for the new readings. Additionally, you can specify if the reading has undergone a reset or rollover event by setting the applicable options. These options are validated, along with the meter reading value, against the source meter template for each reading.

Here are examples of the five types of asset meters with sequential readings, including resets and rollovers:

Template for Asset Meters

Here is an example of a subscription meter with sequential readings for a change ascending meter type:

Template for Subscription Meters

For asset meter readings, it can be time consuming to gather and enter the asset and meter code details into the template. To assist with this process, there's a new export asset meters option available on the Manage Assets page. You can query one or more assets and then click the Export Meters icon:

Export Asset Meters

Then, you get an option to include any child asset meters or not. Click OK to submit the export process:

Export Meter Option

After you submit the export process, an exported report of each asset from the search results and its meter details is produced by the scheduled process. You can track the process on the scheduled processes page to confirm its successful completion and to view the exported file:

Export File Successfully Created

The exported asset meter file includes the asset number, meter code, last active reading date and value. The format is very similar to the readings tab in the import file. You can copy and paste the applicable asset meters into the template, update the reading date and value as required, in reference to the last reading date, time and value.

After you have entered your reading data, follow the standard FBDI process of creating a CSV-based zip file by clicking the action button the first tab of the template. After the zip file is created, you can begin the two-step process of loading and then importing the meter readings from the interface tables. You can now directly access the loading process from the task menu on the Maintenance Management landing page called Load interface File for Import. Use this task to schedule a new process for loading the file:

Task Menu for File Import

During the load process, select the new Import Meter Readings process and then select the zip file for your readings:

Load the Zip File

After it's submitted, you receive a schedule process ID. You can track this on the scheduled processes page to confirm completion and successful import of the zip file into the interface tables. You can then use the same task menu to perform the second step, that's to import the meter readings from the interface tables and create new meter reading history records. For this process, select the unique batch code that corresponds to the meter readings in your zip file:

Import Meter Readings

After it's submitted, you receive a schedule process ID.. You can track this on the scheduled processes page to confirm completion and successful creation of new meter readings. The scheduled process creates an output log, containing a reference to the interface record number for every meter reading row in your zip file. The log indicates if each record was successfully created or if there was an error encountered. If there's an error, then a unique error message is provided, providing guidance on why it failed to create a new reading. It's possible that a file import can result in both the successful creation of some readings and the error result for some readings for a single asset or subscription meter.

Here is an example of an output log for readings that successfully processed:

Successful Readings

Here is an example of an output log for readings that ended in error:

Readings in Error

Readings that fail to create can be fixed by creating a new import file, with a new unique batch code, including only those readings that produced an error in an earlier upload. Additionally, you may need to run the interface table purge program if you find that the interface tables contain imports that ended in error or failed to load.

This new process is useful for the loading of historical readings, as well as the routine capture and import of ongoing readings for a group of assets or subscriptions.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

Only new, sequential readings can be imported using this new process. If reading history corrections are required, you must first perform these corrections in the user interface or using the Meter Reading REST API.

Role Information

• Predefined job role name and code:
  • Asset Administrator (ORA_CSE_ASSET_ADMINISTRATOR_JOB)
  • Maintenance Manager (ORA_MNT_MAINTENANCE_MANAGER_JOB)

• Privileges:
  • Manage Customer Assets (CSI_MANAGE_CUSTOMER_ASSETS_PRIV)
  • Manage Maintainable Assets (MNT_MANAGE_MAINTAINABLE_ASSETS_PRIV)
  • Record Meter Readings (MNT_RECORD_METER_READINGS)

• Configured job roles that do not include the Asset Administrator or Maintenance manage must include this role for the loading and import of FBDI zip files:
  • FSCM Load Interface Administration (ORA_FUN_FSCM_LOAD_INTERFACE_ADMIN_DUTY)

Create Work Orders in a Primary Maintenance Organization Using a REST API

The Maintenance Work Order REST API offers a configured action called createConditionBasedWorkOrders, that creates condition-based work orders for assets that are enabled in the Oracle IoT Asset Monitoring Cloud. Prior to this uptake, the asset had to operate in a maintenance-enabled organization and have a Maintenance Program defined with condition events. With this uptake, the configured action supports the creation of a work order header for an asset that's operating in a nonmaintenance organization and doesn't have a Maintenance Program with condition events defined. The work order can be created in a maintenance organization that's designated as the primary maintenance organization. This designation is defined using the Manage Maintenance Organization Relationships task in the Functional Setup Manager.

The configured action payload includes a reference to the asset, operating organization, condition code, and document type. The document type is this example is the IoT incident:

Payload Example

The configured action looks for maintenance programs in the organization that are defined for the asset and have a matching condition code:

• If a match is found, it creates one or more condition-based work orders based on the work definitions defined in the matching work requirements.

• If a match isn't found, but the asset is operating in the maintenance organization, then a work order header is created without any work definition reference.

• If a match isn't found and the asset isn't operating in the maintenance organization, then it looks for a primary organization relationship:
  • If a primary organization relationship is defined, then a work order header is created without any work definition reference in the primary maintenance-enabled organization
  • If there's no primary organization relationship defined, then no work order is created and an error returned by the service

Setting up a primary maintenance organization begins by establishing relationships between a maintenance organization and one or more nonmaintenance organizations. First, you search for the maintenance-enabled organization in the left region. Next, you select the result row for the organization, which refreshes the contextual relationships panel region to the right. Then, you click the Add button to define one or more rows of related organizations. If you select a nonmaintenance organization, the relationship defaults to Supports. If you select another maintenance organization, the relationship defaults to Reciprocal. 

Organization Relationship Setup

After you have defined one or more nonmaintenance organizations, you can choose to designate the maintenance-enabled organization on the left as the primary maintenance organization by selected the row and clicking the Set as Primary button. You can only have one maintenance-enabled organization set as primary for a nonmaintenance organization. However, the nonmaintenance organization can have other Supports relationships with other maintenance-enabled organizations.

Primary Relationship

This new capability supports assets that are enabled in the Oracle IoT Asset Monitoring Cloud, but are operating in a nonmaintenance organization. The creation of a work order header, even without any work definitions, is beneficial for managing these assets based on an IoT incident.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

The configured action is intended for assets that are enabled in the Oracle IoT Asset Monitoring Cloud. However, the configured action is available as part of the Maintenance Work Order REST API for other external integrations.

Role Information

• Predefined job role name and code:
  • Implementation Consultant (ORA_ASM_APPLICATION_IMPLEMENTATION_CONSULTANT_JOB)
  • Maintenance Manager (ORA_MNT_MAINTENANCE_MANAGER_JOB)

• Privileges: Need to be added to the relevant Predefined job roles or user-defined job roles, as required.
  • Manage Maintenance Organization Relationships (MNT_MANAGE_MAINTENANCE_ORGANIZATION_RELATIONSHIPS_PRIV)
  • Manage Maintenance Programs (MNT_MANAGE_MAINTENANCE_PROGRAMS_PRIV)

Generate Maintenance Program Forecasts Using Number of Days

Maintenance programs are used to define and generate a daily preventative maintenance forecast for one or more assets in an organization. The forecast is then used as the basis for creating preventative maintenance work orders, thus reducing the workload for maintenance planners, and allowing them to focus on maintenance program auditing, optimization, and exception-based events. Maintenance programs can now be forecasted using an interval method based on a number of days, in addition to the previous methods of a calendar pattern and asset meter. Additionally, you now have more control over which assets are included or excluded for an item-based work requirement and how the first due date for each asset is calculated.

You can now search for work requirements using the optional Query by Example (QBE) region. Enabled by clicking the icon. You can also sort by each column by clicking the up and down arrows on the column header names:

Query by Example

You can also select the new Day Interval forecasting method, revealing the method definition region below:

Day Interval Method

The value defined in the Base Interval in Days field is used as the interval duration between due dates in the maintenance forecast for this program. The forecast calculates the first due date as: Start Date + Base Interval in Days. Then each successive due date is calculated as: Previous Due Date + Base Interval in Days. For example, if the Start Date is on a Monday, then Day 1 is Tuesday, Day 2 is Wednesday, and then Day 7 is on the next Monday. Thus, this method allows you to more easily model intervals that could represent many different periods of time in days. You can then use a cycle of intervals to define when your work definitions are due on each interval in the cycle.

The Day Interval method also supports a Method to Calculate Next Due field, similar to the Meter Interval. The default value is Base interval, which keeps the forecast as being due based on the original start date of the work requirement, regardless of when the work order was actually accomplished. For example, you have a forecast in which each due date is due every 7 days into the future for the next 100 days. If you complete the first work order 1 day early and you have the option set to Base interval, then the forecast isn’t adjusted based on the work order completion. The next due date remains at its original date, which is 8 days after your previous work order accomplishment date. You can still enable the Next Work Order Only check box, however, the forecast doesn’t adjust the future due dates based on the last completion.

If the value is set to Last completion, the next due work order can be calculated based on the previous work order's actual completion date. To use this option, you must enable the Next Work Order Only check box, else the forecasted next due date isn’t dynamically adjusted. For example, you have a forecast in which each due date is due every 7 days into the future for the next 100 days. If you complete the first work order 1 day early and you have the option set to Last completion, then the entire forecast is pulled forward by 1 day. The next work order is then due in 7 days from the actual completion of the previous work order. If you complete the next work order 1 day later and you have the option set to Last completion, then the entire forecast is pushed back by 1 day. The next work order is then due in 7 days from the actual completion of the previous work order.

You can also select day intervals to compete with one or more meter intervals. In this case, the first due date among each method is the winner. a day interval can't be defined against a calendar pattern. If both methods are selected, a user error is presented.

For an item-based work requirement, you now have additional control over which assets are included or excluded from the effectivity of the work requirement. The new Include Assets field allows you to determine if all the assets for the defined item are automatically or manually included in the effectivity. Prior to this uptake, all assets were implicitly included in the effectivity of a work requirement. This capability continues to be supported in this uptake by using the default option, Automatically include assets:

Item-Based Requirement

For the default option, you can now view the affected assets by clicking the icon to navigate to a new dedicated page. All the assets for the item are implicitly included and their status is a green check mark, indicating they are included in the maintenance forecast. You can then choose to select one or many assets and exclude them. When excluded, the status changes from a green to a gray check mark, indicating they aren’t considered in the maintenance forecast:

Affected Assets Automatically Included

If you want to implicitly exclude all the assets in the effectivity of a work requirement, and then only manually include certain assets, then you can use the new option, Manually include assets. When you select this option, none of the assets for this item are included in the forecast by default:

Manually Include Assets

When you navigate to the Affected Assets page, you see that all of the assets for the item are implicitly excluded and their status is a gray check mark, indicating they aren’t included in the maintenance forecast. You can then search for and manually include one or more assets using the action buttons. When included, the status changes from gray to a green check mark, meaning they are now considered by the maintenance forecast. This new capability is useful if you wish to control the effectivity of the work requirement to only include assets that are explicitly included.

Affected Assets Manually Included

On the Affected Assets page, you can optionally define how the first due date is calculated and view forecast details for each asset. This page is now available for both asset and item-based work requirements and is helpful during initial implementation of a work requirement as well as the introduction of new affected assets in the future.

For each asset row that is included in the effectivity, these fields are editable if work orders have not been created for an asset in this work requirement::

• Historical Last Completed Date: you can optionally enter in the last time similar maintenance was accomplished from an external application. This date is considered by the forecast and works in coordination with the start date to calculate the first due for an asset. You can only enter a value that’s less than the application date and you must enter a date if the last interval is defined.

• Historical Last Interval: only applicable if the work requirement is cycle-based with intervals. This is the interval at which you last completed maintenance as of the Last Completed Date. You must enter an interval if the last completed date is defined.

• Forecast Start (Date): you can optionally define a start date that is before, equal to, or later than the work requirement start date. If defined, it supersedes the work requirement start date. Remember that the start date determines when the forecast begins calculating and if the date is in the future, the forecast doesn’t have any due dates before that date. If the start date is defined along with the last completed date, then the last completed date takes precedence and is used to anchor the start of the forecast and begin its calculations

When the first forecast is run, you see values in the Forecast Next Due (date) and Forecast Next Interval columns. This helps validate if the forecast method and definition meet the expected due date for each asset. You can adjust the work requirement start date, last completed date, last interval and forecast start (date) values as needed to refine the forecast before the first work order is created for an asset in the work requirement. When this even occurs, you can no longer adjust these fields and adjust the forecast of the first due date. In the future, after the work orders are completed, you see values in the Forecast Last Completed and Forecast Last interval columns, providing asset level forecast details.

You can also change methods from Automatically include assets to Manually include assets. When changing methods, you are presented a click-through validation message. If you click yes, then any changes you have made in the Affected Assets page are lost and you reset all the included and excluded assets actions and any historical data entry values when you click save. If you click no, or don’t save the changes, then the changes aren’t committed.

Validation Message

Additional forecast details are now displayed in the Gantt Chart when you hover over a due date node. This includes the new day interval method, last work order details, and next forecasted meter interval value:

Gantt Chart Due Date Details

The day interval method provides additional modeling capabilities that improve on the base calendar pattern method. The next completion option provides additional flexibility to choose whether credit is required for completing a work order early or late, against its forecasted due date, in the calculation of the next due date. Additionally, you can more easy model completing methods between a day interval and an Asset Meter. This includes being able to model a simple automotive oil change of 90 days or 3,000 miles for example.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

• We recommended you create new work requirements if you want to use the new day interval method and affected assets functionality. If work orders are already created for a work requirement, then you can still use the Affected Assets page to view forecast completion and next due details on existing work requirements. 

• You can also use the new affected assets functionality to reduce the number of work requirements during implementation or introduction of new requirements. The capability of defining individual start dates, along with historical last completed dates and intervals, may reduce the need to have individual work requirements for each asset.

Role Information

• Predefined job role name and code:
  • Maintenance Manager (ORA_MNT_MAINTENANCE_MANAGER_JOB)

• Privileges: Need to be added to the relevant predefined job roles or configured job roles as required.
  • Manage Maintenance Programs (MNT_MANAGE_MAINTENANCE_PROGRAMS_PRIV)

Search for and Select an Item Using Autosuggest and Additional Information in Maintenance UIs

Use the enhanced item picker in your maintenance UIs to perform a variety of tasks with greater ease. With this update, you can:

• Use the autosuggest feature for your item field
• Search by item keyword
• Search by and display customer item, MPN, supplier item, GTIN, EFFs and more
• Control functionality including autosuggest search using run time properties
• Choose to view additional related information when you search for items

This feature is enabled through a global opt-in control, Search and Selects Item more Efficiently. You get to choose if you want to switch from the previous item picker to the new item picker functionality.

Overview of the feature

Here’s some more information about two major functions of this feature: Autosuggest, and the Advanced Search functionality.

Autosuggest

• You can enter three or more characters and find matches.
• Your search is completed automatically.
• You can view suggestions in a drop-down window.
• You can select results from the autosuggest options based on attributes that are indexed.
• You can also extend the search by launching the item picker window.
• You can use the various autosuggest categories for item direct matches, matches to attributes/descriptions and relationships.

Autosuggest functionality

Advanced Search

Here’s how Advanced Search can help you enhance your search:

• You can perform a full parametric search.
• You can add predefined item attributes or extended attributes as your search criteria.
• Advance Search supports multiple operators, depending on your criteria field.
• You can add the same field multiple times to create an OR condition.
• You can include MPN, Customer Item, GTIN as your search criteria and in the search results table.

The Advanced Search Region

With this feature, you can use autosuggest to find items based on partial item information or keywords, thus greatly enhancing your search experience.

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Manufacturing and Supply Chain Materials Management

Role Information

All user roles are enabled with the new item picker.

Split Nonserialized Assets into Separate Assets

Split nonserialized assets into unique asset numbers and quantity. The assets that are eligible to be split have a new Split icon beside the Quantity and Unit of Measure fields. Click the icon to open the Split Asset dialog box where you can enter either a split quantity or select a split all option, and then click the Split Asset button:

The Split Asset Dialog Box: There are a variety of options you can consider when you split an asset. For example, you split your original asset quantity from 100 to the new asset quantity of 50. In the same dialog box session, you can continue to split the remaining quantity of 50 again to 25 and so forth, as needed. After each split action, the List of Split Assets section of the dialog box displays each newly created asset and quantity. When all the splits are completed, click Save and Close to create the new assets and quantity. At any time, if you click Cancel, the split action in the dialog box is canceled and no new assets are created. If you select the Split All check box, each of the newly created assets get a quantity of 1 after saving and closing.

Make sure the quantity your newly created assets is a whole number greater than or equal to one. If the asset has a primary and secondary unit of measure, the split quantity is always in the context of the primary unit of measure, however the new asset quantity is also recalculated for a secondary unit of measure.

There's an export function for all the rows in the List of Split Assets region that helps you export an excel-compatible file containing the list of assets. You can review the list of assets before committing to their creation using the Save and Close button. Remember, when you click Save and Close, your new assets are created.

New Assets: The newly created assets are assigned a new unique asset number based on the original asset being split. The new asset numbers have a sequential number appended to the end of the original asset number. But, you can choose to enter a starting prefix and starting number for your newly created assets. For each new asset, the asset's number considers these prefixed or suffixed values and not base the new asset numbers off the original asset number. You can enter only a starting prefix or starting number, or a combination of both values.

In your new assets, all of the asset attributes are inherited from the original asset in the Edit Asset tab. Also, the new assets have a transaction created in the Asset History tab. This transaction displays details about the original asset that was split. This helps you keep track of old and new assets being split overtime. You can also know the number of times the original asset are split by looking at the asset history record individually for each new asset.

By splitting your assets into separate assets, you can capture modifications that impact an asset's quantity, such as asset transfers and migrations.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

Non-serialized assets are eligible to be split only based on certain item and asset definitions, as well as current associations to other objects.

• An asset's item must be defined as:
  • Asset Tracked = Full Life Cycle or Customer Asset
  • Structure Item Type = Standard
  • Serial Generation = No serial Control
  • Lot Control, either of these options:
    • Full Lot Control
    • Not Lot Control, but inventory = No and Serial = No 
    • Not Lot Control, but inventory = Yes and Serial No
    • Lot Divisible = Yes
  • Dual Unit of Measure, either of these options:
    • Fixed
    • Default
    • No default

• An asset's details must be defined as:
  • Asset Quantity > 1
  • Asset Quantity is not a decimal for the Primary Unit of Measure
  • All Location types except In Inventory
  • For a Customer asset, the customer end date can't be set
  • Asset End Date is not set

• An asset must also pass these validations:
  • Not associated to an open maintenance work order
  • Not reserved for an open maintenance work order
  • Not associated to an open service request

Role Information

• Predefined job role name and code:
  • Asset Administrator (ORA_CSE_ASSET_ADMINISTRATOR_JOB)
  • Maintenance Manager (ORA_MNT_MAINTENANCE_MANAGER_JOB)

• Privileges:
  • Manage Customer Assets (CSI_MANAGE_CUSTOMER_ASSETS_PRIV)
  • Manage Maintainable Assets (MNT_MANAGE_MAINTAINABLE_ASSETS_PRIV)

Process Direct Sales Orders Transactions for Assets

In the retail industry, high-volume selling of products involves processing the inventory simultaneously in real time, which delays the billing for the order. In a 21C update, Order Management introduced a deferred mode that allows the inventory consumption to be deferred so billing can continue without delays. 

In this update, the feature also covers customer asset creation.

REAL-TIME UPDATES FOR DIRECT SALES ORDERS

This process is initiated at the Sales Order user interface. This process uses the predefined orchestration process, DOO_InventoryTransactionProcess. Note that DOO_InventoryTransactionProcess doesn't include the DOO_AssetManagement step. You must configure this process to include the asset management step to see the direct sales orders propagating to Installed Base. Configure the orchestration process assignment rules appropriately to pick the configured process.

The provision of picking the asset from inventory is enabled on the user interface itself and you need to pass these values to the Sales Order to process the transaction.

You can pick the asset from inventory on the Sales Order page itself. You must also define these values to the Sales Order to process the transaction:

• Customer name
• Item and quantity for each sales order line
• Supply Warehouse: Select your source organization the asset is transacted from,
• Subinventory: Select one sub inventory from your selected warehouse.
• Set the Allow Inventory Transaction option to Yes. This option is available in the Sales Order Line section after you set up items 3 and 4.
• Select Manage Lot and Serial Number from the drop down and pick a quantity along with a serial number, lot number, or both, based on the item definition. This option helps you components from the on-hand inventory and initiate your transaction

The Sales Order UI

When the sales order has finished processing, the on-hand balance is consumed based on the lots and serials selected at the time of booking the order. Also, the installed base asset will move from the inventory location to the customer location. The Direct Sales Order Issue inventory transaction consumes the inventory and the Installed Base Interface moves the asset from the inventory location to the customer location.

DEFERRED MODE UPDATE FOR DIRECT SALES ORDER

To execute direct sales order in a deferred mode, you must first set up an Order Management parameter. Here's how:

Manage Order Management Parameters > Process Inventory Transactions Immediately > Set to No

This parameter is used to defer the processing of the inventory transaction for the material consumed from inventory. The asset update always follows the inventory update. So, if you defer the inventory update, the asset update is also deferred automatically.

Order Management Parameter Set Up to Enable Deferred Mode

Next, process your sales order as usual on the Sales Order user interface itself. 

At this stage, the asset isn't moved to a customer location. To process inventory transfer and fulfill the inventory transaction, you must run two scheduled processes:

• Manage Inventory Transactions: Run this process to create a direct sales order issue to customer location. You can view this transaction recorded in the asset history as:
  • Source: Inventory Management
  • Type: Direct Sales Order Issue

• Process Pending and in-Error Genealogy and Installed Base Transactions: Run this process to complete the sales order fulfillment. You can view this transaction recorded in the asset history as:
  • Source: Distributed Order Orchestration
  • Type: Sales Order Fulfillment

After the scheduled processes are run successfully, the asset is moved the customer address and the two transactions are recorded on the Manage Asset History page.

Asset History Page with Completed Transactions of Inventory Transfer Processing and Inventory Transaction Fulfillment

DEFERRED MODE PROCESSING FOR SALES ORDERS

To handle large-volume sales orders or orders having too many lines, use this profile option in Installed Base to process the interfacing of Order Management data to installed base in a deferred mode.

• Profile Option Code: ORA_CSE_IB_INTERFACE_DEFERRED
• Profile Level: Site
• Profile Value: Yes

Profile Option to Process Large-Volume Sales Order in Deferred Mode??????

After the asset is moved to a customer location, the Asset History still doesn't list the fulfillment step. Hence, to complete the job, execute the Process Pending and in-Error Genealogy and Installed Base Transactions schedule process. Then, a new line is added on the Asset History page to indicate the deferred mode is completed.

• Source: Distributed Order Orchestration
• Type: Sales Order Fulfillment

Asset History Page Indicating the Deferred Mode is Completed

Use should be able to choose a deferred Sales Order mode for high volume transactions and skip the inventory update to a later time for convenience.

Steps to Enable

You don't need to do anything to enable this feature.

Role Information

You have a couple of options for giving people access to view asset history transactions, depending on whether you're assigning them predefined job roles or your own configured job roles.

Users who are assigned any of these predefined job roles can view asset history transactions:

• Asset Administrator (ORA_CSE_ASSET_ADMINISTRATOR_JOB)
• Maintenance Manager (ORA_MNT_MAINTENANCE_MANAGER_JOB)

Users who are assigned a configured job role that contains these privileges can view asset history transactions:

• Manage Customer Assets (CSI_MANAGE_CUSTOMER_ASSETS_PRIV)
• Manage Maintainable Assets (MNT_MANAGE_MAINTAINABLE_ASSETS_PRIV)

Additional roles are privileges are required for access to Order Management functionality.

Service Logistics

Improved Control for Field Service Logistics Process

Field service administrators and parts logistics coordinators can now approve, source, and order parts for field service work orders and field stocking locations. This feature enables field service administrators and parts coordinators to more effectively support your parts supply chain.

This feature includes the following enhancements:

1. The Manage Part Requirements UI now enables field service administrators and part logistics coordinators to manage part requirements and orders for the field stocking locations they support, including technician trunk stock.

2. For service providers that require the review and approval of field service technician part requirements before they are ordered, you can now  limit field service technicians from creating part orders for certain field stocking locations. This functionality exists in both the Oracle Field Service Cloud part ordering integration as well as in the Oracle Service Logistics Cloud Part UIs.

3. Two new infolets on the Service Logistics landing page help field service administrators and part logistics coordinators identify the part requirements that need their attention for both field service work orders and field stocking location replenishment.

MANAGE PART REQUIREMENTS UI

Three new search fields and two filter check boxes enable part logistics coordinators to easily access the part requirements that need their attention.

1. Destination Subinventory enables you to see all part requirements and orders destined for a technician trunk stock location or other field stocking locations for both replenishment and for field service work orders.

2. Work Order Area retrieves all of the part requirements for field service work orders assigned to the work area.

3. Technician retrieves all of the part requirements destined for the technician's trunk stock subinventories and for field service work orders assigned to the technician.

4. Selecting the Not Sourced check box filters the search results to only show part requirements that have not been sourced (parts not found).

5. Selecting the Sourced Not Ordered check box filters the search results to only show part requirements that have a source stocking location, but have not been ordered.

6. Use the Order button to create transfer orders for multiple work order part requirements with one click.

Manage Part Requirements UI

SERVICE LOGISTICS LANDING PAGE INFOLETS

Two new infolets on the Service Logistics landing page guide field service part coordinators and administrators to the part requirements that need attention.  The Work Order Part Requirements infolet displays counts of open part requirements for all work orders assigned to the landing page workarea. The Stocking Location Part Requirements infolet displays counts of open part requirements destined for subinventories in the landing page inventory organization.

Service Logistics Landing Page

This feature enables field service administrators and coordinators to better support the part needs of field service technicians through prompt delivery of parts required for work orders as well as replenishment of field stocking locations, including technician trunk stock.

Steps to Enable

The only setup in this feature is the ability to control whether field service technicians can order parts themselves or just create part requirements that get approved and ordered by field service administrators or parts coordinators. A new column labeled Allow Parts Orders has been added to the Manage Field Service Technician UI to control this behavior in both Service Logistics UIs and in the Oracle Field Service Cloud parts ordering integration.  This new field defaults to Yes to preserve backward compatibility.

MANAGE FIELD SERVICE TECHNICIANS UI

Manage Field Service Technicians UI

Role Information

To set up this feature, here's what you need:

• Job Role Name and Code:
  • Field Service Administrator (ORA_RCL_FIELD_SERVICE_ADMINISTRATOR)
  • Field Service Technician Duty (ORA_RCL_FIELD_SERVICE_TECHNICIAN_DUTY)
  • Depot Repair Manager (ORA_RCL_DEPOT_REPAIR_MANAGER_JOB)

Support Additional Types of Manual Service Charge Adjustments

Using Oracle Service Logistics Cloud, you can manually adjust charges and estimates to override the pricing calculation. This enables you to bill customers using a price adjusted by either a discount or a markup. Currently, users can only enter an override price to replace the price calculated by the pricing algorithm.

This feature enhances the Service Logistics manual pricing adjustment functionality by providing options similar to the pricing adjustments available in the Oracle SCM Cloud Order Management work area. You can use this feature in both the Field Service and Depot Repair flows.

Starting with the 21D update, you can choose from the following price adjustment types:

1. Markup Percent
2. Markup Amount
3. Discount Percent
4. Discount Amount
5. Price Override

EDIT PRICE DIALOG BOX

This enhancement enables you to:

• Add multiple adjustment entries for a single line item.
• Refer to the summary information for each adjustment line separately.
• View the sequence number, indicating chronological order, of each manual adjustment line.

It is now possible to add multiple manual adjustments to the charge or estimate lines along with automatic adjustments that are applied.

This feature provides multiple price adjustment options when applying discounts and markups to service charges and estimates.

Steps to Enable

You don't need to do anything to enable this feature.

Role Information

• Users who are assigned any of these predefined job roles are automatically able to access this feature:
  • Field Service Administrator (ORA_RCL_FIELD_SERVICE_ADMINISTRATORS)
  • Field Service Technician Duty (ORA_RCL_FIELD_SERVICE_TECHNICIAN_DUTY)
  • Depot Manager (ORA_RCL_DEPOT_REPAIR_MANAGER_JOB)

Use Additional Subscription Coverage Levels

Oracle Subscription Management Cloud introduced the following additional covered levels in the 21C update:

Party	Covers all assets of a party.
Customer Account	Covers all assets of a particular customer account.
Party Site	Covers all assets of a particular party site.

In this update, Oracle Service Logistics Cloud enhanced the input parameters passed to Subscription Management in order to leverage these additional covered levels.

The input parameters for a subscription call from Service Logistics now include Party, Customer Account, and Party Site.

You can find these additional covered levels in the Subscription Management Add Covered Level page, as shown in the following screenshot:

You can simplify your subscription setup steps by defining covered levels at higher level entities, such as Customer Account, Party, and Party Site, instead of defining them at an asset level.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• Refer to the Subscription Management 21C What's New topic Extend Covered Levels and Entitlements Support for Party, Customer Account, and Party Site.

Debrief Parts from Common Inventory for Projects

Oracle Service Logistics Cloud currently supports the debrief of parts for service work orders with a project association. With this update, you can also issue parts during the debrief process from the project’s common inventory.

To enable this update for an item (part), enable the Allow Use of Common Supply attribute for the item.

For items/parts which are set as 'Allow use of common supply' ,the option of issuing them from common inventory  is provided at the material debrief transaction screen in Service Logistics.

Add Part Details Page

For enabled parts, the Use Common Inventory check box appears when a technician performs a debrief transaction. Select the check box  to perform the material issue from the common project inventory instead of from the project-specific inventory. The Use Common Inventory check box is deselected by default.

Field technicians and administrators have the flexibility and choice to issue service parts from the project common inventory during the material debrief process.

Steps to Enable

Perform the following setup steps before issuing material debrief parts from the common project inventory.

• Enable the debrief organization for the project.
• Verify that the debrief header (work order) is associated to a project.
• Enable the Allow Use of Common Supply attribute for the item (part) before issuing the part during a debrief transaction.This feature is applicable for project enabled organizations only. 

Refer to the 21C New feature summary section 'Generate Project Expenditures for Service Debrief' for details on the project integration feature for service debrief.

Tips And Considerations

• This feature is applicable for project-enabled organizations only.
• Refer to the update 21C feature summary Generate Project Expenditures for Service Debrief for details on the project integration with the service debrief flow.

Role Information

• Users who are assigned these predefined job roles are automatically able to access this feature:
  • Field Service Administrator (ORA_RCL_FIELD_SERVICE_ADMINISTRATORS)
  • Field Service Technician Duty (ORA_RCL_FIELD_SERVICE_TECHNICIAN_DUTY)
  • Depot Manager (ORA_RCL_DEPOT_REPAIR_MANAGER_JOB)