Data_Governance / Monday, October 29, 2018

Slide 4 - Oracle Product Value Chain Cloud Release 9

Slide notes

Hello, my name is Ringo. Welcome to the Release 9 Training for Oracle Product Value Chain Cloud Product Hub Enhancements. In this session, we’ll cover the Data Governance enhancements we've made in this release.

Notes

Slide 5 - Agenda

Slide notes

For the enhancements 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 6 - Enhancements Overview

Slide notes

In this release training we’ll show you how the new features in Release 9 of Fusion Product Hub will help in validating GTIN numbers as well as improve user productivity and enhance governance processes to better manage new item introductions and change management for your product.

We'll show you how you can create validation rules for GTIN association either a) through the enhanced product rules or b) by using the product rules framework.

Notes

Slide 7 - Enhancements Overview

Slide notes

We’ll also show you how product managers and product data stewards will be able to:

View approval history

Configure entry and exit criteria per workflow status

Allow user-entered approvers in the approval workflow

Assign optional approvers to weigh in on the item changes or the introduction of new items

Permit one approval response from a group to complete the approval workflow

Notes

Slide 8 - Validate GTIN Association

Slide notes

In release 9, you can create validation rules to manage GTIN association and validate the GTIN digits.

The GTIN relationship attributes are now enabled in product rules.

Based on certain criteria involving item attributes or organization, you can create rules to validate whether a GTIN is associated with an item or whether the GTIN is changed.

Notes

Slide 9 - Validate GTIN Digits

Slide notes

Similarly, based on certain criteria, you can create rules to validate the digits of the GTIN that’s being associated.

For example, if an item attribute has a specific value, a rule can be created to enforce that the 8th digit of the GTIN must be of a certain value.

Notes

Slide 10 - Approval History for Change Orders

Slide notes

Additionally in Release 9,

Approval history is captured for interim approval and approval workflow for change orders.

This history is differentiated by the enabled approval stages, line approval and header approval.

During line approval you can view each approver’s assigned items.

Also, any action or comments added by approver on a notification is captured and displayed in the approval history.

And, as part of header approval, you can review items set for final approval.

Notes

Slide 11 - Entry and Exit Criteria for Change Management

Slide notes

As a part of change management enhancements,

You can now enforce entry and exit criteria for both change orders and new item request statuses.

These criteria created in manage item rule sets can be invoked from open status through approval status. However, depending upon the status, it can have an entry, exit or both criteria.

Each change order type or a new item request type can have its own entry and exit criteria set up.

In order to support this new feature, we've added, change order type and new item request as an association type in a rule set creation.

Validation rules are supported for entry and exit criteria which will be defined using the product rules. These rules are based on attributes or descriptive flex fields.

For example, you can create a validation rule where if ‘Reason’ is equal to ‘Cost’ then ‘Priority’ has to be ‘High’ and only then the change order can move to ‘Approval’ status.

Notes

Slide 12 - Change Order Type Enhancements

Slide notes

Other enhancements made to the change order type approval workflow set up will allow you to:

Select whether the approver for header approval is user-entered or is derived from rules.

If the user is user-entered, as long as he/she has the privilege to approve change orders, he/she can be added directly when you set up a change order type.

You can add optional approvers in the approval workflow who is given the power to reject the item changes.

Another new feature is added that will allow one response from one member of a group to determine the approval or rejection of the item changes.

For example, if you have a use case where one approval from within a group suffices for the change order to be considered approved, you can set ‘Response Required From” is equal to ‘One’ when ‘Assigned To’ is a group.

Notes

Slide 13 - Approval History Enhancements for New Item Request

Slide notes

Similar to change orders, new item request approval history will be displayed for the enabled approval stages.

During line approval, you can view each approver’s assigned items.

Any action taken or comments added by an approver on an approval notification is displayed in the approval history.

As part of header approval, you can review new items set for final approval.

Notes

Slide 14 - New Item Request Type Enhancements

Slide notes

As in change order type,

You can select header level approver to be user-entered or rule-based.

And, as long as the user has the privilege to approve new items, he/she can be added as an approver.

You can also add optional approvers who are given the power to reject the new item.

You can configure approval workflow so that only one approval is required from one member of a group for the new items to be considered approved or rejected.

Notes

Slide 15 - Data Governance – GTIN Validation Rules

Slide notes

In terms of business values, with the enhancements to data governance in release 9:

You can improve internal business processes by enforcing industry standards such as GS1 GTIN allocation rules. For example, you may want to make sure that there must be a GTIN number associated to all items in the Active status.

Similarly, you can validate the syntax of the GTIN number. For example, based on the Pack Type of the Item, the 8th digit of the GTIN must be set to the number 2. Other examples include validating the correct GS1 company prefix is embedded within the GTIN.

Notes

Slide 16 - Data Governance – Change Management

Slide notes

Other business values include:

Achievement of better operational control on the change management process by enforcing appropriate entry and exit criteria when a change order is moved from one workflow status to the next.

A detailed understanding of the overall approval process can be obtained by viewing the approval history of change orders and new item requests. This enables potential bottlenecks to be identified and mitigation strategies to be put in place.

You can achieve greater control and flexibility over the change management process by rapidly configuring approval workflows which conform to your unique business challenges.

Notes

Slide 174 - Summary of Enhancement Capabilities

Slide notes

Here is the summary of the features I have talked about today.

You can create validation rule sets to validate the GTIN association and validate the digits of the GTIN associated to an item.

Approval history is captured for change order and new item request.

You can enforce entry and exit criteria for change management.

Notes

Slide 175 - Summary of Enhancement Capabilities

Slide notes

Header approval doesn’t need to be always rule-driven, you can add approvers directly to a change order type or new item request type.

You can set optional approvers.

You can minimize the approval time by considering one response from a group.

Notes

Slide 176 - Implementation Advice

Slide notes

So that concludes the audio portion of this presentation, thank you for listening. There is no audio in the implementation advice section.

You can easily pause and rewind any of these slides if you require additional time to take in the detail.

Notes

Slide 177 - Feature Impact Guidelines

Slide notes

Notes

Slide 178 - Feature Impact Guidelines

Slide notes

Notes

Slide 179 - Setup Summary

Slide notes

Notes

Slide 218 - Job Roles & Associated Duty Roles

Slide notes

Notes

Slide 219 - Business Process Model Information

Slide notes

Notes

Slide 220 - Business Process Model Information

Slide notes

Notes

Page 1 of 22