Adobe Captivate - Oracle



Slide 3 - Oracle Order Management Cloud

[pic]

Slide notes

Hello, my name is Deebika. Welcome to training for Oracle Fusion Order Management in Oracle Order Management Cloud.

In this session, we talk about various enhancements in Oracle Fusion Order Management.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 4 - Agenda

[pic]

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 5 - Enhancements Overview

[pic]

Slide notes

For this update, we are enhancing the REST service, Sales Order for Order Hub. Using this REST service, organizations would be now able to create orders for PTO, ATO & Kits in Order Management Cloud.

Order Management now supports order revisions via web services or FBDI even after an order has been revised from the Order Management UI.

We have also enhanced order revision to progress orders by forcefully re-compensating or automatically retrying fulfillment lines that are not progressing.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 6 - Enhancements Overview

[pic]

Slide notes

The new capability covered in this training lets you use a predefined order number sequence and specify an initial value for the sequence. If you do not specify an initial value, the default value i.e. 1 will be used.

Order Management Cloud uses the predefined document sequence for each sales order that you create through the following channels:

• Work Area in Order Management Cloud (UI)

• Direct Web Service Integration (SOA, REST, ADF, HVOP)

• File Based Data Import and Batch Import (FBDI Template)

• Business to Business Integration (EDI)

The predefined sequence is used for sales orders, return orders and orders for internal material transfer.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 7 - Manage Sales Orders Using a REST Service

[pic]

Slide notes

The REST service in this update will support primarily creating sales orders for ATO, PTO & Kits.

As indicated here, this service supports all aspects of a Sales Order such as header, lines, charges, sales credits, attachments, extended flexfields and additional entities mentioned above.

Both pre-priced and orders priced in Fusion are supported by the REST Service.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 8 - Manage Sales Orders for Order Hub Using a REST Service

[pic]

Slide notes

The REST service supports creating sales orders for ATO, PTO & Kits based on product structures or against the rules defined in configurator modeling in the case of PTO & ATO models.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 9 - Manage Sales Orders for Order Hub Using a REST Service

[pic]

Slide notes

REST service explodes included items for the Models & Kits as part of order creation.

REST service uses the configuration effective date Order Management parameter while validating the configuration and to filter effective components of the model.

The REST service supports creating an order either using value attributes or ID attributes or a combination of both.

Orders can be either created in a draft state or can be submitted once they are created in draft.

Orders with both one-time & recurring billing are supported.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 10 - Manage Sales Orders for Order Hub Using a REST Service

[pic]

Slide notes

The Service returns a JSON payload with the order keys & status along with the original set of attributes that are passed in the request.

Any new entities that gets created when the order is created need to be explicitly fetched using the GET method.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 11 - Manage Sales Orders for Order Hub Using a REST Service

[pic]

Slide notes

In terms of business value, the sales orders for order hub REST service provides a canonical representation of the sales order and this will lead to efficient transfer of data across systems over the internet.

As a result of the new REST service, integrations that include REST support for resources will be simpler and highly configurable. REST services provide the foundation for cloud based development and also enable customers to extend their solutions for any customer specific needs in the context of integrating channel/order capture systems.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 12 - Revise Orders via Web Services or FBDI

[pic]

Slide notes

Prior to this update, revisions to an order via web services or FBDI was not supported if the prior revision was through Order Management UI. Only further revisions through the UI were supported.

With this update, Order Management now allows you to perform further order revisions via web service or FBDI as well.

If you enable this functionality, the attribute values in the revisions are compared directly to the attribute values in the order to determine if a change has occurred to the order. This implies that you have to ensure that attribute values of unchanged attributes in the web service payload or FBDI input are derived from the in-process order and re-sent to Order Management.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 13 - Revise Orders via Web Services or FBDI After a Revision from UI

[pic]

Slide notes

In terms of business value, this provides enhanced multi-channel order management capabilities as you can revise orders using web services or FBDI even after a revision has been done from the Order Management UI.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 14 - Force Compensation

[pic]

Slide notes

Force compensation helps in scenarios where the user is neither able to update nor progress the sales order because of a few lines that are serving as bottlenecks.

Users with special privilege will now be able to use the usual Revise order action to perform an over-ridden compensation of these lines.

Fulfillment lines that are not eligible for normal update or cancelation, and have not progressed in the past 90 minutes will become eligible for force compensation.

Note that in this release, force compensation is recommended only for scheduling and reservation task layer related errors.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 15 - Force Compensation

[pic]

Slide notes

With this force compensation enhancement, special users can now perform an overridden order revision on eligible orders.

You will be able to update all the fulfillment lines that are not yet fulfilled and not closed.

And an order becomes eligible if it has a line with a functional error or has stopped progressing.

These fulfillment lines that need attention are marked using a draft level error icon & an error message on click & on hover.

To be able to perform Revise Order action in the force compensation mode, the user should have a role that has the privilege called “FOM_FIX_EXCEPTIONS_ON_ORDER_LINES.”

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 16 - Force Compensation

[pic]

Slide notes

On loading the Revise Order page, this warning message means that you are in the force compensation mode.

You will be in force compensation mode only if you have the “FOM_FIX_EXCEPTIONS_ON_ORDER_LINES” privilege and you have eligible fulfillment lines in your order.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 17 - Force Compensation

[pic]

Slide notes

Please note that even if you don’t edit or change a fulfillment line that has a problem, we will now automatically try to recover the line when you submit an order revision.

Let’s consider the following examples:

• In example 1, let’s say your order had a fulfillment line with a scheduling related functional error and another line that had stopped progressing. And you can see that both lines are marked as problem lines during order revision. But you choose to only update the fulfillment line with the scheduling error and you have submitted the revision. Now apart from re-compensating the line that you have changed or updated, the other problem line will also be re-run as an attempt to recover it.

• In example 2, for the same order which had a fulfillment line with a scheduling related functional error and another line that had stopped progressing. You choose to just submit the revision without updating any lines. All problem lines in the order will be rerun in an attempt to recover it.

Note that for Functional errors, the automatic rerun will resolve the problem only when the underlying problem has been fixed externally.

For example, if the on-hand quantity is now available to reserve in the same warehouse because of increase in inventory.

Now while re-compensating, the fulfillment line would get past the functional error in the reservation task that was erroring out because of unavailable quantity.

Slide 18 - Force Compensation

[pic]

Slide notes

In terms of business value, this provides enhanced control as you can revise orders which have fulfillment lines that have stopped progressing.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 19 - Setup Sequences for Sales Order Numbers

[pic]

Slide notes

The predefined database sequence ORA_FOM_DOC_SEQUENCE_AUTO can be accessed using the Manage Database Sequences task in Setup & Maintenance.

In the Initial value field, the user can specify an initial value of their choice. The default value is 1. This is a one-time setup and applicable to all future sales orders, return orders and internal material transfer orders.

The Start Date is defaulted and denotes when the predefined sequence becomes effective. The End Date is left blank and this indicates that Order Management will continue to increment the order number in perpetuity. The Audit checkbox can be used to enable auditing on the order number sequence, but this functionality is not supported in this release. The Display and Message fields are also not used in this release.

For orders imported from external order capture channels, if you don’t want to use this predefined sequence, you can enable the “Retain Sales Order Number for Orchestration Order Number” profile option in the Manage Order Profiles task in Setup & Maintenance. This option instructs Order Management to continue to use order numbers that are generated in the external order capture system, and not to use the predefined sequence.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 59 - Summary of Enhancement Capabilities

[pic]

Slide notes

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

The feature ‘Setup Sequences for Sales Order Numbers’ lets you use a predefined order number sequence for sales orders, return orders & internal material transfer orders and to setup an initial value for the sequence. The predefined sequence is common to sales orders, return orders and internal material transfer orders in this release.

For orders imported from external order capture channels, the use of this predefined order number sequence can be prevented by using the “Retain Sales Order Number for Orchestration Order Number” profile option which allows users to retain externally generated order numbers.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 60 - Summary of Enhancement Capabilities

[pic]

Slide notes

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

The feature ’Manage sales orders for order hub using a REST Service’ is an enhancement and allows creation of sales orders for PTO, ATO Models & Kit items using a REST service.

The feature ‘Revise orders via web services or FBDI after a revision from UI’ allows creation of order revisions even if the previous revisions were from the Order Management UI.

The feature ‘Force Compensation’ let’s advanced users perform an overridden revision on orders which have fulfillment lines that have stopped progressing. In this release it is recommended to use force compensation only on fulfillment lines that have stopped in scheduling or reservation related errors.

Notes

| |

| |

| |

| |

| |

| |

Slide 61 - Additional Information

[pic]

Slide notes

In this release i.e. 19B, customers will be able to use the predefined order sequence but will not be able to configure their own order sequences.

If this is your first deployment of Order Management and you're going live on 19B, then you must specify the Initial Value attribute for the document sequence. If you do not specify an initial value, the default value i.e. 1 will be used.

There are no constraints that prevent a user with appropriate privileges to modify the predefined order number sequence. Hence, the user must be careful not to modify or delete the sequence in a way that will cause problems. The setting of the initial value on the predefined sequence is a one-time setup. Customers are advised not to make repetitive changes to this setting to avoid potential order number overlap issues.

If you're updating from update 19A to 19B, then you can use an update script that Oracle provides. You apply this script during the update process.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 62 - Implementation Advice

[pic]

Slide notes

In this implementation advice section, we will go through what you need to consider before enabling these features in your business, and what you need to know to set them up.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 63 - Feature Impact Guidelines

[pic]

Slide notes

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

All features have actions to be done by the administrator before they become available to your business. They can be accessed through existing shipped job roles.

There is no Opt-In for any of these features.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 64 - Implementation Decision Points

[pic]

Slide notes

You should enable this capability only if order revisions via web service or FBDI are needed after a user has submitted a revision from the Order Management UI.

If this capability is enabled, the attribute values in the payload for revisions to all the orders would be compared directly to the attribute values from the in-process order. Any difference in attribute value would be presumed to be an attribute change and processed accordingly.

This implies that you have to ensure that attribute values of unchanged attributes in the web service payload or FBDI input are derived from the in-process order and re-sent to Order Management in the payload.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 65 - Actions Needed

[pic]

Slide notes

The admin can further review the REST service definition in the REST API guides to leverage this functionality. If you are using REST services with your Oracle Cloud implementation for the first time, then follow the instructions in the Quick Start section of the REST API from Oracle Supply Chain Management Cloud guide, available in Oracle Help Center.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 66 - Action Needed to Use Feature Force Compensation

[pic]

Slide notes

Force compensation is an overridden revision on orders with fulfillment lines that have stopped progressing and serve as bottlenecks. As this overridden revision reinitiates communication with all fulfilment layers, it is recommended to only allow advanced users to monitor and perform such revision. Hence you will need to add “Fix Exceptions on Order Lines” privilege or alternatively add “Error Recovery Manager” job role to these advanced users.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 67 - Action Needed to Use Feature Revise Orders via Web Services or FBDI

[pic]

Slide notes

You can enable the “Revise orders via web services or FBDI after a revision from UI” capability using the Order Management Parameter “Compare Change Order to Fulfillment Values”. Set the parameter value to ‘Yes’ to enable it. It is not enabled by default.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 68 - Actions Needed to Use Feature Setup Sequences for Sales Order Numbers

[pic]

Slide notes

This feature Setup Sequences for Sales Order Numbers is delivered ready to use for new instance customers. New instance customers can set an initial value of their own for the sequence OR use the default value i.e. 1. Upgrade customers can use the upgrade script that will set the initial value of the new sequence to the next value of the existing sequence.

The enablement for Setup Sequences for Sales Order Numbers is achieved by setting up an initial value for the predefined order number sequence in the Manage Document Sequences task.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 69 - Enablement Detail for Setup Sequences for Sales Order Numbers

[pic]

Slide notes

If this is your first deployment of Order Management and you're going live on 19B, then you must specify the Initial Value attribute for the document sequence. If you do not specify an initial value, the default value i.e. 1 will be used.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 70 - Job Roles

[pic]

Slide notes

This table details the shipped job roles that will access the new capabilities covered in this training.

All the features except force compensation can be accessed using job role Order Manager and Order Entry Specialist.

Force compensation requires the privilege to fix orders (FOM_FIX_EXCEPTIONS_ON_ORDER_LINES) and it is assigned to Error Recovery Manager job role.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 71 - Business Process Information

[pic]

Slide notes

The business processes associated with the new capabilities covered in this training are detailed here.

The high level business process is Order Fulfillment.

The detailed business process associated with the new capability is Manage Sales Orders with activity Create Sales Orders and tasks Book, Import & Revise Order.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 72 - Associated Training

[pic]

Slide notes

The feature Manage Sales Orders for Order Hub covered in this training is a continuous enhancement from prior release. Please review 18C Order Management readiness training for Force Cancelation & REST Service Enhancements for more details.

This concludes this presentation, thank you for listening. You can easily pause and rewind any of these slides 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