Adobe Captivate



Slide 3 - Oracle Order Management Cloud

[pic]

Slide notes

Hello, my name is Pradipta. Welcome to training for Oracle Pricing Cloud Enhancements in Oracle Order Management Cloud. In this session, we talk about Import or Update a large number of Price Lists in Oracle Pricing Cloud.

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

With the Import and Update of Large Number of Price Lists, we are releasing a new, and an enhanced feature, for managing price list data.

Using the file based, data import framework, you can import data related to multiple price lists, in a single batch.

The new feature supports create, append, and update operations, for the different price list entities. The overall process has been improved for importing large volumes of data. It not only provides a high performant mass maintenance solution, but also a stable process for all your data migration requirements.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 6 - Import or Update a Large Number of Price Lists

[pic]

Slide notes

With this file based, data import feature, you can process the different price list entities, like headers, access sets, items, charges, attribute adjustments, along with flexfields at all levels. There is a new excel template now, which supports the different operation codes of Create, Update, and No-Op.

This feature can process data related to multiple price lists, in a single batch. In terms of error reporting, the feature provides both summary, and detailed level of number of records processed, including the error messages.

The scheduled processes are also enabled for monitoring, which lets the user track the progress of the different jobs. You can cancel the import jobs after you submitted them, both at the parent and the child levels.

Finally, you can resubmit the import job to continue processing, if an earlier job was either cancelled or did not complete.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 7 - Import or Update Large Number of Price Lists

[pic]

Slide notes

Company A recently moved into Pricing Cloud. They have large volumes of pricing data, and they find it very difficult to process periodic updates.

Also, some of their divisions have legacy pricing applications, and there is no easy way for them to continuously synchronize their data, with Pricing Cloud.

They want an efficient, and automated way to sync and manage updates, for their pricing data. With the mass import, and update feature, you can now process your price list data, in an accurate, and efficient manner. Using this feature, you can build a process for migrating data from a source system, or a legacy application into Pricing Cloud, and also for doing periodic maintenance. The bulk processing capabilities used in this feature, has ensured that a large number of records can be imported in quick time. This feature will help organizations move strategically into a centralized pricing model.

Notes

| |

| |

| |

| |

| |

| |

Slide 8 - Additional Information

[pic]

Slide notes

From Update 20B onwards, you will have two separate file based import solutions for price list. Some of the differences between the two solutions, are highlighted in the above slide. The two solutions will co-exist in the near future. The old solution will be phased out, once the new solution has complete enablement of all the entities and operations. The new process name is called “Import Price Lists Batch.” It supports create, update, No-Op, and End-Insert operations. It can process multiple price lists in a single batch, and comes with bulk processing capabilities.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 9 - Additional Information

[pic]

Slide notes

The following information should be understood before you can start using the import process. First, it is important to note that the spreadsheet template is an Excel workbook, for entering the price list data. You will find the following sheets representing the interface tables – Headers, Access Sets, Items, Charges, Matrix Dimensions, and Matrix Rules. You will also see an Instructions sheet with some basic information, and the CSV file generation button.

Second, you will see a column called Batch Name, in the Headers interface sheet. You will need to enter a name of your choice (alpha-numeric), and it becomes a unique identifier for the entire data set you want to import. Do remember that you will have to select this Batch Name, while running the ‘Import Price Lists Batch’ job.

Next, you will find the column Operation Code, on each and every sheet in the template. You can use the following operation codes namely CREATE, NO-OP, UPDATE, END-INSERT. For creating an entity, use the code as CREATE. For updating that entity, use the code as UPDATE. For linking to a child entity, use the code as No-Op.

For example, if you need to append new items to an existing header, use No-Op operation code at the header and Create for the item. The End-Insert is a new operation code, applicable for Charges only. It is used for end dating an existing charge, and creating a new one with an effectivity date. The scheduled process “Import Price Lists Batch” will be used for invoking the new solution.

Notes

| |

| |

| |

| |

Slide 10 - Additional Information

[pic]

Slide notes

The list of attributes which can be updated, is given in the template’s Instructions page. For update scenarios, the identifier keys represent the set of attributes, with which you can uniquely identify the record in the database. The identifier keys for each of the price list entities, are given in the template’s instructions page.

For example, a price list header can be uniquely identified by its Name. However, for price list items, you need the combination of item number, pricing unit of measure, line type, service duration and service duration period.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 11 - Additional Information

[pic]

Slide notes

This feature supports 2 variations in which the data, for update operation, can be entered in the excel template. They are ‘Delta Update’ and ‘Replace’.

In Delta Update, you need to enter only the attribute to be updated. In Replace mode, you enter all the attributes, for that record in the template.

To explain, let’s take an example: There is a price list header, which exists in the system, and you want to update the end date.

First, you should begin with an operation code of UPDATE. Next, you should enter the source and identifier keys.

In this case, the source key is the Source Price List ID. And the identifier key is the price list Name. With the above, the import process would be able to understand that this input is an update, and it needs to locate the given price list.

Now, you can enter the attribute to be updated in 2 ways, which in this case is the End Date. In the first way, you just enter the End Date and that’s it. This is called the Delta Update. In the second way, apart from the End Date, you can enter the other attributes as well. In this case, it can be description, currency code, business unit, start date, etc. This is called the Replace mode. It will try to replace, or update the attributes if possible.

Notes

| |

| |

| |

| |

| |

Slide 12 - Additional Information

[pic]

Slide notes

For this feature, the identifier key for Price List Charges is the “Source Charge ID.” For updating the charges, you need to enter the Source Charge ID, in the template for identifying the record. The Source Charge ID on the template maps to the External System Reference ID in the Price List Charges base table. While creating charges using the new file based import process, the Source Charge ID given in the template, will get populated in the External System Reference ID. In future, if you want to update such charges, then the Source Charge ID used in the create operation, must be used for processing the updates.

For example, a price list charge was created using the import process with the Source Charge ID as 6001. Next time, when you try to update the same charge, you must provide the same Source Charge ID…that is 6001.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 13 - Additional Information

[pic]

Slide notes

We are introducing a new attribute called the External System Reference ID. For Price List Charges created with the new FBDI feature, the Source Charge ID will be mapped to the External System Reference ID. For Charges which have not been created using the FBDI feature, (that is charges created using UI, REST, ADFDI, old FBDI feature), you can use the Charge Line Number, to process the update operation.

However, you need to ensure that the Source Charge ID used in this update, will be used as the identifier for any future update operations. The Source Charge ID for the first update using the FBDI feature will get populated into the External System Reference ID

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 14 - Additional Information

[pic]

Slide notes

For this feature, you can use a special type of update called End Insert. In this, you can end date an existing charge, and create a new charge with the effective start date. The operation to be used is End Insert. The feature creates a new charge with the new Base Price, and the Start Date. It end dates the existing charge with the given Start Date. The system keeps a difference of one second, to prevent overlap.

Kindly note that there is a new attribute in the template, called New Source Charge ID. While processing an End Insert operation, you need to enter the identifier for the new charge, in the New Source Charge ID column.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 15 - Additional Information

[pic]

Slide notes

For this feature, the identifier key for Matrix Rules is the “Source Rule ID.” For updating the Matrix Rules, you need to enter the Source Rule ID in the template, for identifying the record. The source Rule ID on the template maps to the External System Reference ID, in the Matrix Rules base table.

While creating matrix rules using the file based import, the Source Rule ID given in the template will get populated in the External System Reference ID.

In future, if you want to update such matrix rules, then the Source Rule ID used in the create operation must be used for processing the updates.

For example, a matrix rule was created using the import process with the Source Rule ID as 1500001. Next time, when you try to update the same rule, you must provide the same Source Rule ID…that is 1500001.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 16 - Additional Information

[pic]

Slide notes

We are introducing a new attribute in the Matrix Rules base tables called the External System Reference ID. For Matrix Rules created with this FBDI feature, the Source Rule ID provided in the template will be mapped to this External System Reference ID.

For existing Matrix Rules, we had provided an Upgrade script for Release 20A to populate the Dynamic Matrix Rule ID (primary key) into the External System Reference ID. For Matrix Rules created after Release 20A using non FBDI channels (like UI, ADFDI, REST), the External System Reference ID would get auto-populated with the Dynamic Matrix Rule ID.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 17 - Additional Information

[pic]

Slide notes

The new price list import feature, comes with the ability to Resubmit the parent job, in case it had to be cancelled, or did not complete. Once you select the earlier parent job, the Resubmit button becomes available, which enables you to submit the job again with the same parameters.

The resubmit feature will process all records in New or Validated status, for that pricing batch. The enablement of the Resubmit button is controlled by a profile option – ESS Allow Process Submission.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 57 - 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 58 - Feature Impact Guidelines

[pic]

Slide notes

This table depicts key update information for the features covered in this training. The feature, ‘Import or Update Large Number of Price Lists’, covered in this training is delivered ready to use. Also, it can be accessed through existing shipped job roles.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 59 - Feature Delivered Ready to Use Impact Analysis

[pic]

Slide notes

This table details the impact to your current business flows, of features in this training that are delivered ready to use by your end-users. The feature, Import or Update Large Number of Price Lists, is a new Oracle delivered process that can be used to enhance your existing business processes.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 60 - Job Roles

[pic]

Slide notes

This table details the shipped job roles that will access the new capabilities covered in this training. The shipped job roles are Pricing Administrator, Pricing Manager and Pricing Analyst.

Notes

| |

| |

| |

| |

| |

| |

| |

| |

Slide 61 - 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 Plan Pricing. This feature belongs to the Activity of Establish Pricing Rules, which takes into the account the management of pricing setup data like prices, discounts, adjustments, etc. for goods and services. The task pertaining to this feature is Manage Price Lists.

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