Adobe Captivate - Oracle



Slide 3 - Oracle Supply Chain Management Cloud

[pic]

Slide notes

Hello, my name is Pierre. Welcome to training for Maintenance Cloud in Oracle Supply Chain Management Cloud.

In this session, we talk about work order attributes defaulting.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 4 - Agenda

[pic]

Slide notes

For the capabilities covered in this training, we’ll give an overview, followed by more detail to explain how you can use them, and what business value they bring. Then, we’ll walk you through a demonstration. Next, we’ll explain what you need to consider before enabling these features in your business, and what you need to know to set them up.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 5 - Capabilities Overview

[pic]

Slide notes

The capabilities covered in this training will provide you with the ability to default data for Work Order and, more specifically, to default the work order description, the work order type and work order subtype.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 6 - Get Default Work Order Attributes

[pic]

Slide notes

This capability will provide you with the ability to derive defaulting information from either the work order context asset or maintenance work definition.

Defaulting happen s automatically when you create a work order manually thought the UI, using FBDI and REST. It also happen when work orders are created from a maintenance program

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 7 - Get Default Work Order Attributes

[pic]

Slide notes

Today, not all companies are able to perform an analysis of their maintenance process because optional data are not always entered by users when creating Work Orders. As a result, it is difficult to improve these maintenance processes.

This new feature allows the Work Order Type, Work Order Subtype and, if a Work Definition is used, the Work Order Description to be filled in by default. It therefore saves time, as the user no longer has to search for values to enter, and ensures the reliability of the information to expose for future analysis.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 50 - Additional Information for Get Default Work Order Attributes Work Order Type and Subtype

[pic]

Slide notes

The following are the work order type and subtype defaulting rules:

The first and main scenario is manual work order creation. In this scenario you have to remember that work definition takes precedence over all the asset and manual entries. When work definition is selected during the Work Order creation, if values defined at work definition are not null, then existing values of Work Order Type and Work Order Subtype fields are always overwritten. Otherwise, if values pulled from work definition are null, then existing values (or null values) are retained. Values are defaulted from the asset only if:

• There is no work definition defined for the work order, even if Work Order Type and Work Order Subtype fields are manually defined.

• Or there is a work definition defined for the work order, but Work Order Type and Work Order Subtype fields are null.

The defaulting process fills either the Work Order Type and Work Order Subtype, or the Work Order Type only, or nothing. As these fields are mandatory to create a work order, you manually select the missing required fields.

You can manually update the defaulted values at any time. But, if you later enter or update either asset or work definition, the existing values are overwritten by the defaulting process.

Notes

| |

|x |

| |

| |

| |

Slide 51 - Additional Information for Get Default Work Order Attributes Work Order Type and Subtype

[pic]

Slide notes

When you create a work order using an FBDI template or REST service, the process is different: the values passed in the XLSM template or the REST Payload are used first. If no values are passed for Work Order Type, Work Order Subtype or Work Order Description, then defaulting occurs normally, as described for the manual creation. Last, when you create a work order from a maintenance program, there’s no defaulting from either the context asset or maintenance work definition. We automatically default the Work Order Type as preventive and Work Order Subtype as planned.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 52 - Additional Information for Get Default Work Order Attributes Work Order Description

[pic]

Slide notes

The work order description is defaulted from the work definition description. Therefore, defaulting only happen if you select a work definition at work order creation.

For work orders created from a maintenance programs, defaulting rules are little more complex. Depending on maintenance program setup, tree scenarios can happen:

1. The maintenance programs use a single work definition or concurrent requirements option is set to suppress. In this case, as for manual work order creation, work order description is defaulted from the work definition description.

2. The work order is created from merged work definitions within a single maintenance program's work requirement: In this scenario, work order description is defaulted with the work requirement name.

3. The work order is created from merged work definitions across multiple work requirements within a maintenance program, as multiple work requirements are involved.

Notes

| |

| |

| |

Slide 53 - Implementation Advice

[pic]

Slide notes

In this section, we provide implementation considerations and setup instructions for the enhancements covered.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 54 - Feature Impact Guidelines

[pic]

Slide notes

This table depicts key update information for the features covered in this training.

The Get Default Work Order Attributes feature doesn’t require specific setup, but until the next update, it requires an opt-in.

Details and associated job roles are covered next.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 55 - Get Default Work Order Attributes Impact

[pic]

Slide notes

The Get Default Work Order Attributes feature is delivered disabled. You are required to opt-in to enable it.

The feature can be accessed using the Maintenance Manager job role or Maintenance User job role.

The business process associated with this feature is Execute Maintenance and Repairs.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 56 - Summary of Actions Needed to Use Get Default Work Order Attributes

[pic]

Slide notes

Before commencing enablement for this feature there are implementation considerations that need to be taken into account.

• There is no additional setup required to use this feature, but defaulting occurs automatically as soon as defaulting information are entered either at asset or work definition level.

• Defaulting process cannot be disabled for a particular asset or work definition.

Until revision 20C, the enablement for Get Default Work Order Attributes requires you activate Opt-In option.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 57 - Enablement Detail for Get Default Work Order Attributes Impact

[pic]

Slide notes

In order to enable this feature, you need to login the system using a job role that allows you to update the application setup.

Navigate to Setup and Maintenance option from the navigator then select Manufacturing and Supply Chain Material Management on the list of values on top. Scroll down to Maintenance Management and open the action menu.

Click on Change feature selection to open the Edit Feature UI and enable this feature.

This concludes this presentation. Thank you for listening. You can easily pause and rewind if you require additional time to take in the detail.

Notes

| |

| |

| |

| |

| |

| |

| |

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download