This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
Date | Update Version | Notes |
---|---|---|
20 OCT 2017 | Update 17D | New features delivered in update 17D. |
01 SEP 2017 | Update 17C | New features delivered in update 17C. |
25 AUG 2017 | Update 17B | Revised update 17B. |
This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
Date | Feature | Notes |
---|---|---|
20 OCT 2017 | Created initial document. |
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 in this guide 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 you have created custom job roles, then you can use this information to add new privileges to those roles as needed.
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.
Optional Uptake of New Features (Opt In)
We continue to add many new features to the Oracle Cloud Applications, and for some features, you can take advantage of new functionality at a pace that suits you by “opting in” to the feature when you’re ready. You can opt in to a feature in two ways: by using the New Features work area, or by using the Setup and Maintenance work area.
To opt in using the New Features work area:
- Click the Navigator, and then click New Features (under the My Enterprise heading).
- On the New Features page, select the offering that includes new features you’d like to review.
- Click Opt In for any feature that you want to opt in to.
- On the Edit Features page, select the Enable option for the feature, and then click Done.
To opt in using the Setup and Maintenance work area:
- Click the Navigator, and then click Setup and Maintenance.
- On the Setup page, select your offering, and then click Change Feature Opt In.
- On the Opt In page, click the Edit Features icon.
- On the Edit Features page, select the Enable option for any feature you want to opt in to. If the Enable column includes an Edit icon instead of a check box, then click the icon, select your feature options, and click Save and Close.
- Click Done.
This section gives you information to help you plan, deploy, and validate your update. We make frequent additions to this document, so don’t forget to check back and get the latest information before your update starts.
Action Required to Enable Feature |
|||||
---|---|---|---|---|---|
Feature |
None (Automatically Available) |
Enable via Opt In UI Only |
Enable via Opt In UI Plus Additional Steps |
Not Enabled via Opt In UI but Setup Required |
Issue Service Request |
Enable Custom Payloads for Downstream Integration
You can now extend the existing cloud-to-cloud integration from Oracle Order Management Cloud to Oracle Shipping Cloud, Oracle Purchasing Cloud, and Oracle Receiving Cloud. Order Management includes integration with other SCM applications for a complete order-to-cash process flow. While these integrations are comprehensive, additional information may be required to be passed from an order to meet specific business needs. You can now add additional attributes to the existing cloud-to-cloud integrations from Order Management to Shipping, Purchasing, and Receiving. For example, the supplier price can now be passed to a purchase order. This integration extensibility reduces implementation time and order processing costs.
Steps to Enable
Set up the feature options as follows:
- In the Navigator, click Setup and Maintenance.
- On the Setup and Maintenance page, click the Order Management offering.
- Click Change Feature Opt In.
- Click Edit Features for Order Management.
- Select Enable Custom Payloads for Downstream Integration and select the Enable checkbox. The Feature name: Enable Custom Payloads for Downstream Integration dialog box appears.
- Select the checkbox for each integration that you want to enable.
- Click Save and Close.
Define the mapping of attributes between the Order object and the Invoice interface object as follows:
- In the Pricing Administration work area, click Tasks.
- Navigate to Order Management Configuration > Manage Service Mappings. There are predefined objects under the FulfillmentIntegration context.
- Use the predefined attributes to define the required mapping.
Tips And Considerations
If you plan to use the extensible or descriptive attributes for mapping, gather information about the implemented extended flexfields for order objects and the implemented descriptive flexfields for invoice objects. The attributes you plan to use in the Manage Algorithm page must be defined under the Sources and Service tabs of the Manage Service Mappings page.
If you plan to map attributes across levels, then you must first create algorithms using the Manage Algorithms page. The fulfillment line is at the same level as the invoice interface line. Other entities from the order object are either a level higher or lower with respect to the invoice interface line.
Key Resources
- Oracle Supply Chain Management Cloud: Implementing Order Management Guide, available on the Oracle Help Center.
- Oracle Supply Chain Management Cloud: Administering Pricing Guide, available on the Oracle Help Center.
This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
Date | Feature | Notes |
---|---|---|
01 SEP 2017 | Created initial document. |
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 & NEW FEATURES
If your system has modified security structures, you may need to advise your security administrator of new features you would like to take advantage of.
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.
Optional Uptake of New Features (Opt In)
We continue to add many new features to Oracle Cloud Applications and we now give you the option to take advantage of new functionality at a pace that suits you. The ‘New Features UI’ is available to you from your cloud homepage, where you can make your choices and do any configuration necessary.
This section gives you information to help you plan, deploy, and validate your update. We make frequent additions to this document, so don’t forget to check back and get the latest information before your update starts.
Action Required to Enable Feature |
||||
---|---|---|---|---|
Feature |
Automatically Available |
End User Action Required |
Administrator Action Required |
Oracle Service Request Required |
Rules-Based Selection of Accounts Receivable Transaction Types |
||||
Effectively Test Changes Across Impacted Models Prior to Release |
||||
Add Supplemental Attributes to Simplify the Guided Selling Process |
||||
Expand Configurator Extensions Rules Functionality with New Event Types |
Order Coverage and Subscription Services
Selling coverage services, such as extended warranties, with an item on an order or after an item sale provides an additional high margin revenue stream. Offering products with a subscription model can simplify purchases for customers and make revenue more predictable through recurring sales. The ability to order and process both coverages and subscriptions in a common format will help prevent order errors and reduce order processing costs. Coverage and subscriptions services include the following:
- Addition of coverage to an order and its association with the order line to be covered
- Automatic modification or cancelation of a Coverage when there is a modification or cancellation of the associated covered line
- Manual cancellation of a coverage
- Addition of coverage to a previously ordered item
- Refund the coverage amount in the event of an associated covered product return or when the coverage alone is returned
- Create orders with coverage and subscriptions through the Order Management UI or through order import
- Search and retrieval of orders or order lines with coverage and subscription services
- New product type for subscription services, with the ability to leverage Order Management business rules, validations, and processing constraints during order capture and fulfillment processing
- Ordering standalone subscription services or subscription service with an associated coverage
- Ability to select duration (fixed, variable, or open ended), billing period, billing frequency (one time or recurring) and add start date for coverages and subscriptions
- Pricing of a coverage independent or dependent on the covered item price
- Coverages for shippable (e.g. a computer) and non-shippable items (e.g. software and subscriptions). Coverages for configured items
- Split of Coverage proportionately when the associated covered line splits
- Sending coverages and subscriptions downstream for invoicing
As part of this update, Order Management supports ordering of service products such as Coverages and Subscriptions, both through the Order Management user interface and order import.
A coverage product is a service that is associated with another product that we call the covered product. A coverage product cannot exist in isolation and is always ordered against a covered product. Examples of coverages are extended warranty and service level agreement.
A coverage product is a service item that is not shippable. It is defined with one of the four Sales product types in Product Information Management:
- Extended Warranty
- Software Maintenance
- Service Level Agreement
- Preventive Maintenance
Coverage would also have a service duration and duration period.
A covered product is defined in Product Information Management by setting the Enable Contract Coverage option to Yes. A covered product can be shippable, such as computer hardware, or can be virtual, such as computer software or subscription. A covered product could be a standard product or a configured product, such as Assemble to Order (ATO) model, Pick to Order (PTO) model, Hybrid, and Kit.
Order Management allows ordering of coverage along with the covered product in the same sales order, which is called the Immediate Coverage scenario.
When a coverage item is selected in the catalog row, the Add button changes to Select Covered Item. Duration and Duration Period replace Quantity and UOM and display values from item setup, and can be updated if the item is a variable duration service.
The Select Covered Item dialog box lets you select the covered product from items in the current order or a previous order. When this selection is made to current order, it becomes an Immediate coverage. In the Select Covered Item dialog box, the Quantity and UOM fields display values from the covered item and cannot be changed. The coverage quantity and UOM always remain the same as the associated covered product quantity and UOM. Contract start date is displayed from the requested ship date of the covered product, but can be overridden based on the Order Management parameter setup Coverage Start Date, that is applicable for a shippable covered product. The Add button adds the item to the order and associates it with its covered product.
You can add more than one coverage to the same covered product, for example, a Standard Desktop can be covered by the extended warranty and coverage such as Service level agreement or Preventive maintenance. However, a coverage line can cover only one covered product.
When coverage is ordered against a configured covered product through the Order Management user interface, a coverage line gets automatically added for every component of the model, be it included item, option class, or option item that is coverable. By coverable, what we mean is that this component can have an associated service attached that is set by setting the Enable Contract Coverage option as Yes in Product Information Management.
In the above scenario, the Order Lines table displays only the root coverage line along with the rollup of all charges. The More link below this root coverage line displays the child lines.
If the user changes the quantity or UOM of the covered line, the coverage product line changes automatically to be in sync with the covered line for these attributes. The coverage line can be deleted or canceled by itself during order creation or revision; however, the coverage line is deleted or canceled automatically if the associated covered item is deleted or canceled.
In cases where a customer has not ordered for coverage while ordering the covered product, Order Management allows the coverage to be ordered at a later point of time as long as the covered line is in closed status. We call this scenario Delayed Coverage.
For a delayed coverage order, you must select the covered line from a previous order. The coverage being ordered will have the same quantity and UOM of the closed covered line, net of any quantity returned for the covered line.
In cases of delayed coverage where the covered model is in another order, only the child coverages are displayed on the Components page, below the root, with a comment pointing to what they cover.
In a given a sales order, there could be both Immediate and Delayed coverage lines.
Once an order is submitted, the fulfillment view of the order shows the new service attributes that can be exposed via the View menu.
When a coverage line is selected in the Fulfillment view, the new Service Details tab shows additional information on the service attributes. There is also a link to the covered product that this line covers.
In the returns flow, the return of coverages may have two use case variants – coverage gets returned automatically when the associated covered product gets returned or coverage alone get returned.
When a closed covered line is returned, the valid associated coverage lines from across orders are also displayed in the Return dialog.
For coverages, the quantity to return is by default the quantity of the covered item being returned. When the Create Order button is selected, an order is created with return lines for both the covered item and the coverages, and the credit amount defaults to what the customer paid on the initial order. The prices can be adjusted, in case a different amount is needed to be refunded.
Similarly, if the customer only wants to terminate the coverage but keep the covered product, they can select the coverage; but in this case, the return quantity must be the entire returnable quantity of the associated covered product.
The other type of service that is supported for ordering as part of this release is Subscription. A Subscription service is provisioned on a recurring basis, such as Software subscription and Software-as-a-Service (SaaS).
A subscription can be ordered alone or it can take the role of a covered product by having an associated coverage. Example of a subscription product with an associated coverage is a Subscription to the Order Management Cloud with an associated coverage of Service Level Agreement of 99%.
A subscription could be a standard product or could be any of the supported Configured product types, such as Assemble to Order (ATO) Model, Pick to Order (PTO) Model, Hybrid, and Kit.
When a subscription item is selected in the catalog row, there would be some changes to the display. Duration and Duration Period display in addition to quantity and UOM. By default, Duration and Period are populated from Item setup, and can be updated if the Item is a variable duration subscription. If it is open-ended subscription, the Duration and Duration Period can be entered, if required. The Add button adds the item to the order just like any goods item.
We have thus seen how service ordering is enabled using the Order Management user interface. The following section showcases how import helps in service ordering.
Order Management supports the import of service order lines, be it coverages or subscriptions from any upstream system to create, modify, cancel, and return such service lines. You can import coverage lines against both standard and configured covered products. These coverages can be part of an Immediate Coverage order or Delayed Coverage order.
All the existing import mechanisms, such as the File based import, the Service Oriented Architecture (SOA) webservice, the Application Development Framework (ADF) webservice, and Business-to-Business (B2B) or Electronic Data Interchange (EDI) Messaging framework, support service lines.
In order to accommodate import of service product lines such as coverages and subscriptions, the payload has been enhanced to capture key service attributes, such as Service Duration, Duration Period, and Billing periodicity. Note the subtle differences in the way the payload needs to be sent when the order is Pre-priced or Fusion priced.
So far, we have discussed how coverages and subscriptions can be handled using the Order Management user interface or through import. The following section deals with specifics around Pricing, Fulfillment, and Billing of such service products.
A coverage item can be priced in a variety of ways, for example , you can set a standard price for the coverage that is independent of the covered item price or you can set the coverage price to be a percentage of the covered item price. When it is percentage based, the basis could be Net price, List price, or any other. This is applicable in the case of both Immediate and Delayed coverage orders. The coverage item could have a one-time charge, recurring charge, or multiple charges associated with it. Order Management also calculates the amount that customer will need to pay for the entire duration for the given charge. There is also support for calculation of duration amounts in the cases of partial periodicities, where time unit of measure for service duration is different from the charge periodicity.
When coverage is against a configured covered product, its price can be defined at the root model level and all components that are coverable are evaluated for pricing. Rollup charge is calculated for the coverage lines covering eligible components. Pricing is supported for coverage items that may have fixed service duration, variable service duration, or are open-ended.
Just like coverages, various types of charges can be defined for Subscription items, such as one-time, recurring, or multiple charges. These subscription items can be of fixed service duration, variable service duration, or open-ended. Order Management calculates the amount for the total duration that the customer would need to pay for the entire duration for the given charge, that includes partial periodicities wherein the time unit of measure for service duration is different from the charge periodicity.
Return lines for coverages and subscriptions could be priced as long as there is original order reference. Manual price adjustments on all return lines, irrespective of they being regular product lines or service lines, have been introduced as part of this release.
Now coming to fulfillment aspects of service products, Order Management provides users with options to coordinate the fulfillment of covered products and associated coverages. For example, the orchestration process can be defined such that the coverage is not processed until the covered product is shipped.
The contract dates of the coverage can also be computed based on the fulfillment milestones of the covered product. This is applicable when the covered product is shippable. This functionality is not enabled by default and it can be enabled using the Order Management setup parameter, Coverage start date, where the milestone can be specified at a Business Unit level.
If a covered product is split during fulfillment, the associated coverages will also be split proportionally and associated with the relevant split covered product lines.
With regard to Billing integration, charge periodicity and billing periodicity have been decoupled as part of this release. You now have support for billing scenarios, such as recurring billing for an item with a one-time charge and one-time billing for an item with recurring charge. With this change, Billing is no longer driven based on the charge type against the item.
You can now capture the recurring billing information directly on the line.
When there is coverage against a configured covered product and if the coverage has a billing plan, then the billing plan on the coverage is cascaded to the coverage associated to every covered option (the child coverage lines). You can then modify the billing plan at the coverage option level as needed.
Order Management supports partial credits for coverage and subscription items with recurring billing after recurring billing has started.
Lastly, new attributes, such as Sales product type, Service Duration, and Duration Period, are available for various setups. These are available for support in business rules, processing constraints, delta attributes, order import, fulfillment system payloads, order information services, business events, and business intelligence reporting.
Steps to Enable
No steps are needed to enable this feature.
Key Resources
For more information on this feature, refer to the following guide, available on the Oracle Help Center:
- Oracle Supply Chain Management Cloud: Implementing Order Management
Create Extensions for Advanced Defaulting and Validation
Order Management includes validations to ensure that an order has the right information before it is submitted for fulfillment. While these validations are comprehensive, businesses often require additional order information to be validated. For example, adding a sales territory attribute that is derived from an external system and checking that the territory field is populated before order submission. This feature allows customers to extend order management validation and defaulting behaviors as part of the order booking flow.
- Allows extensions to be defined at event points on Order Save and at the beginning or end of Order Submission
- Extension apply to imported orders and orders entered using the Order Management user interface
- Within the extensions, write validation logic to stop the flow and raise a message, default or override the attributes, and call out to systems or functions outside Order Management
The flexibility of these extensions improves order data quality by incorporating checks against the master data and using web services provided by Oracle Applications Cloud and third-party systems. This reduces the chance of exceptions during fulfillment and results in a faster order-to-cash cycle.
When the extensions validate the order and produce warning and error messages, they are visible in the Order Management work area to end users in a manner consistent with other application messages.
The messages created within the extension framework are defined by customers and can be categorized into existing message types or into new message types for ease of viewing and searching.
Steps to Enable
Define new validation and defaulting logic using the Manage Order Management Extensions task in Functional Setup Manager.
Tips And Considerations
- Extension code can call only the web services defined in Manage Web Service Definitions
- Web services are supported for synchronous interaction only
- Specific attributes are enabled for defaulting at each event point
Key Resources
For more information, refer to support.oracle.com:
- Defining Extensions That Modify Order Management Cloud (Doc ID 2252683.1)
Extend Integration with Financials
Order Management includes integration with Financials to enable a complete order-to-cash process flow. While this integration is comprehensive, there may be additional information that must be passed from an order to meet a specific business need. For example, send the primary sales rep to Financials, or modify the product description to include the product name that is getting covered in a coverage line. Users can now extend the existing integration to include additional attributes lowering the cost and speeding implementation time.
Steps to Enable
You need to define the mapping of attributes from Order object to the Invoice interface object. Navigation for this setup is as below:
- Navigate to the Pricing Administration work area.
- Click on the Tasks pane.
- Navigate to Order Management Configuration > Manage Service Mappings.
There are predefined objects under FulfillmentIntegration context. These attributes can be used to perform the desired mapping.
Tips And Considerations
Gather information about the implemented extended flexfields for order objects and the implemented descriptive flexfields for invoice objects, if you plan to use the object attributes for mapping. The attribute you plan to use in the Manage Algorithm page must be defined under the sources and service tabs of the Manage Service Mappings page.
If you plan to map attributes across levels, then you must first create algorithms using the Manage Algorithms page. The fulfillment line is at the same level as the invoice interface line. Other entities from the order object are either a level higher or lower with respect to the invoice interface line.
Key Resources
- Oracle Supply Chain Management Cloud: Implementing Order Management
- Oracle Supply Chain Management Cloud: Administering Pricing
Rules-Based Selection of Accounts Receivable Transaction Types
Orders include information that is needed to determine the proper accounting for financial transactions, such as invoice and debit and credit memo. Order Management now includes AR Transaction Type as a standard attribute. This allows users to define rules (Pre/Post Transformation) to select the desired AR Transaction Type using information on the order, such as business unit, order type, line type, and product, ensuring that the order flows smoothly through Financials.
The following figure shows a sample Pre Transformation Rule for Receivables Transaction Type (Billing Trx Type):
Steps to Enable
No steps are required to enable this feature.
Business Intelligence for Draft Orders
Transactional analytics allow users to easily identify order priority and orders in exception. This helps maximize order revenue and expedient resolution of order exceptions. Users can now create and view transactional reports for orders in a draft status, including draft orders categorized by validation error types. The reports are created using Oracle Transactional Business Intelligence and can be viewed on Business Intelligence dashboards or the Order Management spring board. Handy access to prioritized list of orders to submit improves user productivity as well as responsiveness to customer orders.
To select only draft orders in your report, you would need to select the Booked attribute from the appropriate folder and then apply a filter to restrict the value to N. If your report is an order header level report, you can find this attribute under the Order Details folder in the Order Headers subject area as shown in the following figure.
On the other hand, if the granularity of the desired report is Fulfillment Line or children entities of Fulfillment Line, then you would build the report in Fulfillment Lines subject area. Here, you would find the Booked attribute under the Order Header Detail folder as shown in the following figure.
Creating reports on draft orders that are in an exception state serves as a means to resolve the underlying cause for the exception. Thus, this empowers you by helping to close revenue on time such as before the end of a financial quarter.
Steps to Enable
No steps are required to enable this feature.
Tips And Considerations
Note that if you want to exclude draft or unbooked orders from your report, you must select the Booked attribute and apply a filter to restrict the value to Y. If you do not apply this filter, your report may include both booked and draft orders depending upon the filter criteria and the sales order data.
Key Resources
- Oracle SCM Cloud: Creating and Administering Analytics and Reports Guide Release 13 (update 17B)
Define Pricing Rules Based on Item Attributes
Often companies want to calculate or adjust a price based on the attributes of a product, but it is too time consuming to define it individually for each product. You can define item attributes on an item class to represent additional information about a product or service. This additional product information may then be used in pricing rules to determine price or discount eligibility. Examples include discounting a price based on a product color or size or uplifting a base price based on an item's material such as gold, silver or copper.
In this release, the following features are supported:
- Ability to use item attributes within a pricing algorithm, including Price Sales Transaction
- Reference item attributes in a Pricing Matrix on a price list line. This is supported at All Items level and Item level
- Reference item attributes in a Pricing Matrix on a discount list line. This is supported at All Items level and Item level
Creating pricing rules based on attributes of the product or service provides a convenient and efficient solution for creating and maintaining your pricing logic. In addition, it provides the flexibility to create differentiated pricing based on key business drivers.
Steps to Enable
Set up the item attributes in Product Information Management. This includes the details for the attribute groups, attributes, and validation using value sets. Associate the attributes to an item class and then define an attribute page. This attribute page needs to be associated to the Pricing functional area. Ensure that the item attribute values are assigned for the item.
Once these item attributes are defined, you can use them as a matrix condition column on a price list charge adjustment or in a discount list adjustment. Review the predefined matrix classes and set up condition columns corresponding to the item attributes. A new domain type will be available to assign the item attribute to the condition.
In order to retrieve the values of the item attributes in a pricing algorithm, you will need to set the variable GetAllUserDefinedAttributesFlag from false to true in the Set Initial Values pricing algorithm.
Key Resources
- Oracle SCM Cloud: Administering Pricing guide, available on the Oracle Help Center
Effectively Test Changes Across Impacted Models Prior to Release
When making changes to configurator models, product structures, or other product information which may impact existing configurations, you often need to test any models which may be impacted prior to releasing the changes. Depending on the change, the number of models which may be impacted can be substantial. In order to efficiently test a large number of models, the testing needs to be executed without requiring user input.
In this release, a new configuration testing service allows you to invoke configurator in a non-interactive mode. The service takes as input a payload that creates the configuration, performs one or more configuration operations on the components of the model, and closes the configuration. All of these operations are performed without any end user interaction.
This allows you to efficiently test any changes and assess the impact of those changes across all models prior to release, ensuring the quality of any given release.
Steps to Enable
No steps are required to enable this feature.
Key Resources
- Oracle Supply Chain Management Cloud: Configurator Modeling Guide, available at Oracle Help Center.
Add Supplemental Attributes to Simplify the Guided Selling Process
For complex, customizable products it is often difficult for the customer to understand which individual product options are required to best satisfy their underlying requirements. Guided selling questions are frequently used during product configuration to help customers choose the product best fulfilling their needs. In order to do this Configurator needs to match attributes of components in the solution to criteria specified in the selection processes. For example, a guided selling process may be used to help a customer select the best car components in their configuration. Based on how the customer intends on using the vehicle, supplemental attributes such as fuel economy rating, comfort index, cabin size, etc. are compared to those same attributes on individual car components to help make the optimal selections in the configuration.
In this release you can expand the definition of supplemental and item structure and then use these attributes in rules to find the best possible match between them.
The preceding figure illustrates the creation of a supplemental attributes and shows how the response to a guided selling question in Configurator runtime can be used to reduce the number of valid selections in the configuration. In the example shown we see that the available set of engine type components is reduced from a broader list by evaluating and matching the supplemental attributes defined on the guided selling response and the engine components.
Steps to Enable
No steps are required to enable this feature.
Key Resources
- Oracle Supply Chain Management Cloud: Configurator Modeling Guide, available at Oracle Help Center.
Leverage New UI Template for Additional Dynamic Content
New templates with header level facets for option classes and option features enables the design of user interfaces that can include additional dynamic content about the item. Additionally, at design time, the Product Configuration Manager can override the item display value of a node with a combination of the item name and description. Enhancements to the UI templates will increase usability and accuracy of configured items during order capture.
The following figure illustrates a user interface using a check box group with quality and facets.
Steps to Enable
No steps are required to enable this feature.
Key Resources
- Oracle Supply Chain Management Cloud: Configurator Modeling Guide, available at Oracle Help Center.
Efficiently Manage Supplemental Structures
In order to guide customers to select the best product which meets their needs, Fusion Configurator allows the Product Configuration Manager to define additional information, which is not captured in the product structure, to help in the guided selling process. This is called supplemental structure and it consists of option features, corresponding options, structure attributes, and their values. For companies that have large number of models with complex structures, maintaining this additional structure information can be a difficult and time consuming activity.
With this release, management of these supplemental structures is enhanced using Oracle ADF Desktop Integration (ADFdi) Services. ADFdi is one of the features of Oracle ADF that enables integration with Microsoft Excel spreadsheets to manage large volumes of data from web applications.
Manage Supplemental Structure – The Product Configuration Manager will be able to efficiently maintain the supplemental structure using Microsoft Excel spreadsheets. These spreadsheets support comprehensive search capabilities along with download and upload functions. It not only supports create, update, delete operations but also provide the same validations as applicable in the Configurator Modeling Environment (CME) user interface. The spreadsheets also ensure data accuracy and function security.
Common Supplemental Structure – This release introduces the ability to maintain a common supplemental structure, also called the Cross Model Option Feature, across multiple configuration model drafts and workspaces. The Cross Model Option Feature is essentially a list of option features and corresponding options, with a set of related supplemental attributes and values. With integration to Oracle ADFdi services, you can create or update the Cross Model Option Feature in a Microsoft Excel spreadsheet and then upload them across multiple model drafts within the Configurator Modeling Environment.
Steps to Enable
- The appropriate ADFdi plug-in needs to be downloaded and installed
- The respective ADFdi spreadsheets have to be downloaded before usage
Key Resources
- Oracle Supply Chain Management Cloud: Configurator Modeling Guide, available at Oracle Help Center.
Expand Configurator Extensions Rules Functionality with New Event Types
Configurator extension rules allow you to expand configuration behavior at runtime to create user-defined complex model logic. This release extends the events at which the extension rules can be called to include the postConfigSave and preAutoComplete events. These events allow extension rules to be executed after a configuration has been saved and before the auto-complete process starts.
To add configuration logic after a configuration has been saved or before the auto-complete process starts:
- Create a new extension rule and provide the Groovy code required to perform the business logic.
- During the event binding creation, select the postConfigConfig or preAutoComplete event for the event type.
The following figure illustrates postConfigSave or preAutoComplete event for an extension rule:
Steps to Enable
No steps are required to enable this feature.
Key Resources
- Oracle Supply Chain Management Cloud: Configurator Modeling Guide, Oracle Help Center.
This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
Date | Feature | Notes |
---|---|---|
25 AUG 2017 | Accept Credit Cards for Payments |
Removed feature from update 17B. |
21 APR 2017 | Created initial document. |
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 & New Features
If your system has modified security structures, you may need to advise your security administrator of new features you would like to take advantage of. Appendices A and B provide a listing of the security attributes needed to employ the new features after you have decided to implement them.
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.
Optional Uptake of New Features (Opt In)
We continue to add many new features to Oracle Cloud Applications and we now give you the option to take advantage of new functionality at a pace that suits you. The ‘New Features UI’ is available to you from your cloud homepage, where you can make your choices and do any configuration necessary.
This section gives you information to help you plan, deploy, and validate your update. We make frequent additions to this document, so don’t forget to check back and get the latest information before your update starts.
Action Required to Enable Feature |
||||
---|---|---|---|---|
Feature |
Automatically Available |
End User Action Required |
Administrator Action Required |
Oracle Service Request Required |
Analytic-Driven Infolets on the Home Page and Work Area Landing Pages |
||||
Receive Delivery Information From Transportation Management Systems |
||||
Update Status and Exceptions Using Business Events Compatible with Oracle Integration Cloud Service |
||||
Integrate Configurator Run Time Across Your Order Capture Channels |
||||
Tailor and Segment Views in the Global Order Promising User Interface |
||||
Synchronize Sales Orders with External Order Management Systems |
||||
Modern order management business flows must operate in a multi-faceted, dynamic environment. These business flows must support:
- Multiple sources of order capture.
- Multiple methods of order fulfillment.
- Consistency of governance and order promising.
- Streamlined customer experience.
- Seamless integration with billing and finance.
To facilitate these business flows, Oracle provides a multichannel order management capability with a central order hub at its core. This hub includes capabilities for order capture and fulfillment orchestration, pricing, product configuration, inventory management, and order promising.
Oracle’s innovative supply orchestration architecture provides the flexibility required for differing order policies and promising and fulfillment methods while managing any exception conditions that may arise.
A successful order-to-cash business process relies on your ability to aggregate, analyze, and act upon key insights that drive timely and reliable business decisions. You need highly visual, analytically driven, and timely information at the forefront of the applications you use every day. This releases introduces a revamped home experience page and work area landing pages that provide visual, insightful, and actionable information for your entire order-to-cash business process.
Analytic-Driven Infolets on the Home Page and Work Area Landing Pages
The new home experience and application work area pages provide modern user interface components called infolets. An infolet is a self-contained, interactive container that helps you quickly visualize high-level information, review relevant details, and proceed to action. Because infolets are role-based, you see only what is relevant to your specific role. Progressive disclosure of details is available to you by expanding or inverting the infolet as needed. You can also rearrange the layout of your infolets or hide the ones that you do not need.
Infolets are available to you at two levels:
- Home experience infolet page: This page exists at the same level as your springboard page (where you access your application icons). You can click the page controls (indicated by dots at the top-center of the home page) to access a set of logically grouped infolets aggregated from multiple application work areas. If you have all the relevant roles, you are able to view infolets on the home experience infolet page that aggregate critical information for your entire order-to-cash business process.
- Infolet-based landing pages: An infolet-based work area landing page contains infolets specific to a single product work area. You can access a work area page by clicking an icon button on the springboard, an icon button in the springboard strip, a work area name in the Navigator, or an infolet on a home experience infolet page. The redesigned work area landing pages present information quickly and clearly to draw your attention to actionable content, which is key to your productivity. Infolet-based work area landing pages have easy-to-read analytic tiles that users can rearrange and configure to meet personalized needs. The tiles also provide additional metrics and improved usability. This design allows all users to monitor the part of the operation that best meets their own role or interest.
Where applicable, infolets pertinent to individual infolet landing pages of application work areas are covered in the following product sections in this document:
- Order Management
- Global Order Promising
The following table summarizes the infolets grouped on the home experience infolet page for the order-to-cash process.
Product |
Infolet |
Infolet Description |
---|---|---|
Inventory Management |
Shipments by Priority |
Displays the top five priorities, in terms of volume of shipments. |
Open Shipment Lines |
Displays shipping lines that haven't been shipped, are open today, and have been open the past 30 days. |
|
Shipment Exceptions |
Displays all of the shipment-level exceptions. For example, Shipment Lines on Hold, Pick Release Warnings, Shipment Lines on Hold for Update, Packed Lines not Interfaced, and Shipping Cost Interface Processing Errors. |
|
Cost Management |
Inventory Valuation |
Displays the current value of on-hand inventory in all organizations. |
The following screen capture illustrates the new welcome experience page:
Steps to Enable
No steps are required to enable this feature.
Key Resources
- Oracle Supply Chain Management Cloud: Using Order Management, available on the Oracle Help Center.
This release adds significant order management capability in the following areas:
- Payment method support
- Credit checks
- Trade compliance
- Adjusting the Calculated Net Price
- Order approval workflows
- Integration abilities with transportation and trade management solutions
Steps to Enable
There are no steps necessary to enable this enhancement.
Order Management answers the business need to configure and automate order approval workflow, speeds order processing, and ensures orders meet policy.
Configure Approval Conditions and Assignment Routing
Approval rules allow you to configure approvals and assignment routing based on conditions using a variety of order attributes and reporting hierarchies. For example, you might have conditions where the maximum manual price discount for an order entry user is 10% and a manual discount of greater than 10% requires sales director approval. You can use the graphical rules editor to:
- Define, edit, and delete the conditions using attributes from the sales order. For example, you might want to reconfigure the following attributes: total monetary value of the order, discount on one or more lines of the order exceeding a certain percentage or value off the list or net price of an item, the ordered quantity of an item, requested ship date, requested arrival date, and so on.
- Configure the approval routing to a specific individual, a supervisory hierarchy, a predefined approval group, or a hierarchy based on job roles or positions. For example, you might have a rule that manual discounts above 20% require approval from the area manager and the vice president of sales.
The order approval flow is triggered based on the value of the Order Management parameter ‘Start Approval Process for Sales Orders’. This parameter can be set up specific to a given source order system. If the parameter value is set to No, the order approval rules, even if defined, will not be evaluated; if the parameter value is set to Yes, and no rules defined for approval, the orders will be moved to fulfillment with processing status automatically. You can use the following Manage Order Management Parameters page to set the value for this parameter:
The approval rules are created using a visual editor in the Manage Order Approval Rules setup task. You can use the setup task to create, edit, delete, and publish approval rules. Approval rule creation involves specifying the approval conditions, and subsequently, configuring the approval routing. Attributes on Order Header, Order Totals, Order Line, Order Charges, Price Adjustment, and validation attributes are used to define the conditions. The following screen capture illustrates how the conditions for order approval are defined:
Once the approval conditions are defined, the next step is to specify the actions that drive the approval assignment. You can set the order to be Auto Approved or Rejected based on certain conditions, assign the order to an individual user for approval, or assign the order approval to an approval group, position hierarchy, job level hierarchy, or supervisory hierarchy. User and hierarchy information is sourced from Identity Management. The following screen capture shows the actions that drive the approval assignment and the definition of the assignment:
Steps to Enable
- Enable the ‘Start approval process for Sales orders’ parameter for the given source system.
- Define approval groups (if approval action is required to be assigned to a group) using the Manage Approval Groups for Supply Chain Management setup task.
- Define approval rules using the Manage Order Approval Rules setup task.
Key Resources
- Oracle Supply Chain Management Cloud: Implementing Order Management, available on the Oracle Help Center.
Trigger Approvals During Order Entry
Order-to-cash cycle times are improved by reducing the idle time during order exceptions by automating the workflow and notification to those persons best suited to address them. Approval notifications, assignments, and actions are available in the Order Management user interface and include the following:
- User will be notified that an approval is required and the cause.
- User can follow the approval status including who has approved, who still needs to approve, and if the order has been approved or rejected.
- Users can’t edit an order that has pending approvals.
- Order entry users can withdraw an approval request if they need to edit the order and resubmit for approval.
- History of approval or rejection for an order is preserved in the system and is viewable by the user.
Assume that order approval is enabled for the given source system and that the order entry user has submitted an order for approval based on the applicable approval rules. In this case, the order is in the ‘Approval pending’ status. The lock icon next to the status indicates that the order is locked from being edited. The following screen capture shows the View Order Details page:
If the order entry user wants to know who receives the order for approval, how many levels of approvals are required before the order is moved to fulfillment, and the reason for the order moving to approval phase, they can click the View Approval Information button to view the details as seen in the screen capture below:
An order that is assigned for approval can be acted upon by the assignee using Worklist and Notifications. As shown in the following screen capture, clicking the notification icon (Bell icon) displays the pending notifications:
Clicking a given notification opens a task form with the order details, as shown in the following screen capture:
The task form displays order information and the reasons for assignment. The approver can perform various actions on the order, including Approve, Reject, Request Information, Reassign, and Create Subtask. There is also a provision to provide comments against an approval or rejection. In case of a rejection, the comments are required so that the order entry user knows the reason for rejection.
When the required action is taken by the approver, the order entry user receives a notification in the work area. The order entry user can open the notification and view order details, including the approval or rejection comments.
An order rejected by the approver goes back to the Draft status. The order details include a new tab for Approval Notes. Clicking the tab displays the notes entered in the comments section on order rejection. The following screen capture shows the new Approval Notes tab for a draft order:
The order can be edited or fixed based on the comments, and then again follow the approval cycle as stated earlier.
Steps to Enable
No steps are required to enable this feature.
Key Resources
- Oracle Supply Chain Management Cloud: Implementing Order Management, available on the Oracle Help Center.
- Oracle Supply Chain Management Cloud: Using Order Management, available on the Oracle Help Center.
Check Credit During Order Entry and Fulfillment Processing
Order Management is integrated with Oracle Financials Cloud to provide the complete flow of setting credit limits and executing order processing within them. The system uses credit limits defined in Oracle Financials Cloud to control the financial exposure for new order creation and order changes. It provides support for credit checking during order submission, communicating credit check information to downstream billing systems, processing order changes, applying credit holds, and releasing holds where necessary.
The choice of when to run a credit check is dependent on your business processes. Credit checking is configurable at specific points in the order flow; it provides support for credit check during order submission (including order import) to assess the customer’s credit standing. A credit check can also be initiated from a step within an orchestration fulfillment process (for example, prior to shipping for long lead time orders). Default workflows include credit check at order creation and prior to shipment. Orders that fail credit checks are put on hold.
Customer credit check during order submission is turned off out-of-the-box. You can turn on credit check at order submission by setting the Order Management parameter ‘Activate Check on Order Submit’ to Yes. You can also specify the business units where you want to enforce credit check. You can choose to turn it on for all business units, or for a specific business unit. Credit check can also be turned on or off for a specific customer within the customer profile. The following screenshot shows the Manage Order Management Parameters page, where you can enable the customer credit check at order submission:
You can use another Order Management parameter to control how to handle the order when credit check fails during submit. The name of the parameter is ‘Credit Check Failure at Order Submit’. You can select one of the following actions:
- Save Order in Draft Status: If any line within an order fails the credit check, then order submission fails, and the order is saved in the draft status. No credit check hold is applied on any of the Lines.
- Submit Order with Hold on Lines that Failed Credit Check: Order is submitted even if it fails credit check, however the lines which failed credit check will have a credit check hold applied. This hold ensures that the lines are held in the first step of the orchestration process. Lines which passed credit check progress to the next step in the process.
The following screenshot illustrates the options available in case of credit check failure:
Credit check is also modeled as a new task type. You can configure orchestration process to include steps for customer credit check at appropriate time during fulfillment. For instance, the request for credit check can be sent after indentifying a source and reserving inventory in the case of a complex configuration with a large manufacturing lead time. In this case, the request to ship the product is sent only if customer credit check passes. The following screen capture shows an orchestration process with a step for credit check:
Steps to Enable
No steps are required to enable this feature.
Orders with credit holds show up on watchlists, reports, and searches for credit holds for ready access. An authorized user can review orders that are on credit hold and release the hold. Credit holds can also be released based on revisions made to the order (such as deletion of items to reduce total price) or automatically based on an update of credit status from Oracle Financials Cloud.
CREDIT CHECK AT ORDER SUBMISSION
If credit check is enabled at order submission, the credit check is performed on all orders, excluding prepaid orders and internal orders. Return lines are also excluded for the credit check. If the order submission fails, credit check authorizations are rolled back.
For every order line which passes credit check, the credit check authorization information, such as Credit Reference and Expiration Date, are displayed under the Billing tab for the given fulfillment line. Credit Reference is sent to the billing system each time a line becomes eligible for billing.
Customer credit checking is also executed on change orders. For change orders, original authorizations are removed, and new authorizations are obtained for the entire change order. In case of order line cancellations, any existing ‘Credit Reference’ on the lines is sent to the billing system via de-authorization call to relieve customer credit.
You can view the credit check authorization information under the Billing tab in the fulfillment details region, as shown in the following screen capture:
If any group fails the credit check, then either the entire order is moved back to draft, or the order can continue with failed lines on credit check hold (predefined hold). Credit check hold is applied automatically in this case. The failed lines with credit check hold belonging to a group will be at the first orchestration step. The action that is performed depends on the customer needs, and is controlled using the following Order Management parameter: Credit Check Failure at Order Submit.
NOTE: Within a bill-to customer group, all lines pass credit check or all lines fail. Having some lines pass and other fail within the same bill-to customer group is not supported.
Once the customer credit issue is resolved, the credit check hold must be released manually. The fulfillment line proceeds to the next step in the process if the credit check hold is released successfully.
The following screenshot illustrates credit check hold:
CREDIT CHECK DURING ORDER FULFILLMENT
Credit check can also be added as a step within the orchestration process. If the fulfillment process contains a credit check task, the credit check will be executed. During credit check, lines with same bill-to customer are grouped, just as during credit check at order submission. Only lines with expired authorizations undergo credit check again. If any customer fails credit check, the credit check task will go into error recovery, and users can initiate the Recover Error action. No credit check hold is applied to the lines which failed credit check in this case. You must resolve the credit check issue and perform error recovery. Error recovery will again execute credit check validations.
Please note that the credit check task is not delta attribute dependent, and will always be executed again during change order processing.
PRE-CREDIT-CHECKED ORDERS
Order Management supports pre-credit-checked orders. All orders submitted from the Order Management UI and via order import are eligible for credit check. Pre-credit-checked orders can come in via order import, batch import, and new order import service. These orders have a Pre-Credit Checked check box at the order level, and Credit Reference Number and Expiry Date at the line level on applicable lines. If the Pre-Credit Checked check box is selected, customers can choose to send Credit Authorization Reference Number and Credit Authorization Expiration Date.
If any pre-credit-checked order has at least one order line for which the Credit Reference Number has expired, re-authorization of the entire order is initiated based on the setting of the parameter ‘Activate Credit Check on Order Submit’ for the sales order business unit. For instance, if Pre-Credit Checked = Y but authorization has expired then Order Management will run credit check if the sales order business unit is enabled for credit check. The expired authorization remains as is if the business unit is not enabled for credit check.
If the expiration date is not specified, then a credit check is not executed, as it is considered to be an open-ended authorization. If an order is pre-credit-checked and all authorizations are valid or not expired, then credit check is skipped within Order Management during order submission.
Steps to Enable
- Enable the credit check at order submission using the Order Management parameter ’Activate Check on Order Submit’.
- Define a fulfillment process with a step to check customer credit during fulfillment, if applicable.
NOTE: Even if a Credit Check step is included in the fulfillment process, the parameter ‘Activate Credit Check on Order Submit’ is still selected for the sales order business unit. If Credit Check for that business unit is set to ‘N’, Order Management will skip the credit check step during fulfillment.
Key Resources
- Oracle Supply Chain Management Cloud: Implementing Order Management, available on the Oracle Help Center.
- Oracle Supply Chain Management Cloud: Using Order Management, available on the Oracle Help Center.
- Oracle Financials Cloud: Implementing Receivables Credit to Cash, available on the Oracle Help Center.
Additional Order Management Enhancements
Visually Monitor Order Status and Exceptions
Presenting information quickly to draw the attention of users to actionable content is important for user productivity. The Order Management work area landing page has easy-to-read analytic tiles that users can rearrange and configure to meet personalized needs. The tiles also provide additional metrics and improved usability. This design allows all users to monitor the part of the operation that best meets their own role or interest.
Order analysts can now look at order validation errors, and operations managers can keep an eye on issues that might potentially cause customer delays. Users can expand or invert the tiles to present alternate views and drill down to transactional data to address the most urgent orders. The following table provides the analytic tiles available in the Order Management landing page.
Order Management Tile |
Description |
---|---|
Orders on backorder |
Time-phased view of backorder delays, as well as the ranked order value of the backordered demand by customer. |
Orders past due |
Orders that have been delayed past the scheduled due date, as well as the ranked order value of delayed orders by customer. |
Fulfillment lines in jeopardy |
A categorized count of lines in each jeopardy priority, as well as the ranked monetary value of the at risk order lines by customer. |
Orders in jeopardy |
A categorized count of orders in each jeopardy priority, as well as the ranked monetary value of the at risk orders by customer. |
Orders on hold |
The distribution of orders on hold by hold type, as well as the ranked monetary value of the held orders by customer. |
Orders in error |
The distribution of submitted orders by error type, as well as the ranked monetary value of the orders in error by customer. |
Draft orders in error |
The distribution of draft orders by error type, as well as the ranked monetary value of the draft orders in error by customer. |
The following screen capture illustrates the Order Management work area:
Steps to Enable
No steps are required to enable this feature.
Key Resources
- Oracle Supply Chain Management Cloud: Using Order Management, available on the Oracle Help Center.
Enable Global Trade Compliance
Order Management allows you to use global trade management systems to provide efficient trade compliance checks during order entry and downstream fulfillment processes. Global trade compliance screening decreases order cycle times, minimizes risk, and enables quick access to new markets. For example, you can screen your sales orders for restricted parties, embargoes, export licenses, required documents, and other trade requirements.
You can use export trade management systems, such are Oracle’s Global Trade Management, to provide the following:
- Configure automatic checking of global trade compliance during order submission.
- Configure a fulfillment process to include a step to check for global trade compliance and add additional process steps based on the outcome of the check.
Compliance screening allows users to:
- Receive order error messages for non-compliance.
- Take action to resolve noncompliance (for example, cancel an order, select a different supply source, or change carriers).
- Search for noncompliant orders, view analytic summaries of noncompliant order errors and holds, and drill down to a list of noncompliant orders and select a specific order.
Whether an order is sent to the trade management system for compliance screening at order submission depends on the Order Management parameter ‘Check for Trade Compliance when User Submits Sales Order’. You can use the Manage Order Management Parameters page to enable the trade compliance screening at order submission, as shown in the following screen capture:
Trade compliance check is disabled at order submission out-of-the-box. Once enabled, all orders are checked for trade compliance before being released to fulfillment. It has three possible outcomes – passed, failed, or under review. If the order passed the trade compliance check and no other violation was detected, the order will be released to fulfillment. If the order failed the trade compliance check or additional compliance review was required, whether the order is rejected for additional edit and review is based on the business needs. For instance, business may decide to reject all orders from the customers that are the restricted party list. It may also choose to release the orders to fulfillment regardless and address the compliance issues later on after other fulfillment information is available. Order Management leverages the existing processing constraint framework to reject orders with trade compliance issue. Out-of-the-box, orders with trade compliance issue will be rejected based on the predefined constraint rule. Business can disable it if needed. If additional review and approval is required before releasing an order with trade compliance issue, business can define approval rules based on the outcome of the compliance check.
The following screen capture illustrates the definition of the predefined constraint rule for rejecting order with trade compliance issue:
You can view the outcome of the trade compliance check on the Order Details page. The trade compliance status of the entire order is the most restrictive trade compliance status of the order lines that the order contains. For example, if the status for one order line is Failed, then the status for the entire order is Failed. Order Management uses the following hierarchy to determine which status is most restrictive, where 1 is least restrictive, and 3 is most restrictive:
- Passed
- Under Review
- Failed
The color of the Trade Compliance Status icon on the Order Details page indicates the outcome of the compliance check: green for Passed, red for Failed, and yellow for Under Review, as shown in the following screen capture:
Click the View Details link to view the trade compliance details. Three types of trade compliance screening are supported:
- Restricted Party
- Sanctioned Country or Territory
- Trade Control
The outcome of each screening type is available on the Trade Compliance Details window. You can disable some trade compliance types as needed, and you can enable different types of trade compliance screening at order submission and at order fulfillment. If a screening type is disabled, no status is reported for that screening type.
The trade compliance status of the order line is the most restrictive trade compliance status of the screening types enabled. In the following example, the trade compliance status of the order line is Failed, because the result of the Sanctioned Country or Territory screening type is Failed:
If a line didn’t pass the trade compliance check, you can click on the View Details link for more details, as shown in the following screen capture:
If it’s a configuration, only the top model line is displayed in the trade compliance details page. The roll-up status for the entire configuration is displayed on this page. You can click on the Component Details icon to view the trade compliance details for the configuration components, as shown in the following screen capture:
In addition, you can quickly identify and work on the orders with trade compliance issue through order search, as shown in the following screen capture:
Check of global trade compliance can also happen after order is released to fulfillment. Optionally, you can define a fulfillment process with a step to check global trade compliance during fulfillment, as shown in the following screen capture:
The fulfillment line will proceed to the next fulfillment task if it passed the compliance check. Additional process steps based on the outcome of the check may also be configured. For instance, you can add a pause task after trade compliance check for business review.
You can view the outcome of the trade compliance check in the Fulfillment Line pages as well, as shown in the following screen capture:
The fulfillment line search is also enhanced to allow search based on the outcome of the compliance check, as shown in the following screen capture:
Steps to Enable
- Enable global trade compliance check at order submission using the Order Management parameter ‘Check for Trade Compliance when User Submits Sales Order’.
- Define a fulfillment process with a step to check global trade compliance during fulfillment, if applicable.
Key Resources
- Oracle Supply Chain Management Cloud: Implementing Order Management, available on the Oracle Help Center.
- Oracle Supply Chain Management Cloud: Using Order Management, available on the Oracle Help Center.
Adjusting the Calculated Net Price
Sometimes, an authorized person needs to adjust the automated price of a product or service: for example, to offer a customer a discretionary discount. However , you must control the extent of the adjustment to prevent unprofitable discounting practices.
This new feature allows authorized users to apply adjustments to the net price on the order line. You can make the following types of adjustments:
- Adjust the net price by a percentage of the list price or net price
- Adjust the net price by a specific value
- Specify a new value for the net price
You can apply one or more adjustments to a pricing charge for an order line. You can also specify a reason and justification for the adjustment. The adjustment is presented in the price break down summary on the order line.
Manual price adjustments are validated against any pricing guidelines defined in Oracle Pricing Cloud. Pricing guidelines control by how much the net price can be adjusted, for example, customers can define pricing guideline rules that prevent a manual price adjustment from exceeding 50% of the list price.
This gives you the flexibility to adjust the net price of a product or service when the business permits such exceptions, while ensuring that such adjustments are within constraints set by corporate pricing policies.
If a charge is enabled for a manual price adjustment, you can invoke the adjustment dialogue by clicking the Edit icon.
You can now validate prices against pricing guidelines, which are administered in Oracle Pricing Cloud. Pricing allows pricing administrators to define pricing guidelines against various pricing components, such as net price or manual price adjustment. When a transaction is validated, the guidelines associated with the pricing strategy are evaluated and the appropriate violation type (error, information only, or warning) is returned. If any violations exist, you are provided with appropriate warnings based on the violation defined for the guideline. Order Management also allows authorized users to override the exceptions and submit the order for further processing. If approvals are configured, then a transaction with pricing violations can be routed to appropriate users for the necessary approvals.
You can take corrective action by adjusting the discount, or you can submit the order with the violation. An order with a pricing violation can also be routed to the appropriate user for approval, provided that approvals are configured.
Steps to Enable
Define pricing guidelines in Oracle Pricing Cloud and associate these guidelines with one or more pricing strategies. For details, refer to the Controlling Pricing and Discounting Practices section.
Key Resources
- Oracle SCM Cloud: Administering Pricing, available on the Oracle Help Center
Receive Delivery Information From Transportation Management Systems
Order Management allows you to use transportation management systems to provide efficient transportation planning. Transportation management systems optimize the shipments associated with your sales orders to minimize freight costs while adhering to your customers’ delivery requirements. Transportation systems also provide complete in-transit visibility of shipments from the moment they depart your facility to receipt by your customers.
You can use Oracle’s Transportation Management to enable the following:
- Automate extraction of orders for transportation planning
- Get early visibility to scheduled shipment dates from the transportation plan
- Receive delivery notification when the shipment is delivered
A new predefined task type has been added which enables orders to be interfaced to transportation management systems automatically. This task type provides multiple invocation modes – asynchronous service, synchronous service and business event - to integrate with external systems. The business event mode can be used for integration with transportation management systems via Oracle Integration Cloud Service (ICS).
The computed scheduled dates post-transportation planning and the actual delivery date after the item is delivered can be updated in Order Management. These updates can be done even when the active task type is not related to transportation planning. This provides flexibility in modeling the orchestration process as per the business needs.
As an example, consider a business requirement to wait for proof of delivery before invoicing an order. This can be modeled using a pause step post shipment task but before the invoicing task. The pause task condition is defined to release the pause only after receiving the proof of delivery from the fulfillment system. In such a case, the actual delivery date can be updated while waiting at the pause step, which would then release the pause and enable invoicing of the order.
Steps to Enable
Define a fulfillment process with a step to interface orders to transportation management systems during fulfillment.
Key Resources
- Oracle Supply Chain Management Cloud: Implementing Order Management, available on the Oracle Help Center.
- Oracle Supply Chain Management Cloud: Using Order Management, available on the Oracle Help Center.
Update Status and Exceptions Using Business Events Compatible with Oracle Integration Cloud Service
Order Management exposes business events to Oracle Integration Cloud Service to provide more detailed status updates, better process synchronization, and easier integration for order-to-cash environments that involve multiple capture and fulfillment systems.
Integration Cloud Service-enabled events provide the ability to:
- Use the Integration Cloud Service platform to navigate and discover the Order Management events.
- Map Order Management events graphically to customer specific web services.
- Allow external applications to consume business events in a common integration framework.
- Apply cross referencing to transform attributes understandable by a target system.
You can subscribe to the Sales Order Notification event to get status change or order exception notifications from Order Management. To subscribe to the notification, browse the Oracle ERP Cloud catalog in the Integration Cloud Service, and select the With Business Events option for Configure a Request. Browsing business events in the Integrations area of the Integration Cloud Service is illustrated in the following screen capture:
Further, you can leverage the new operation GetCrossReferenceData under the Order Information Service to fetch cross-referenced values corresponding to the data snapshot published in the Sales Order Notification event that your subscribing system can understand. In order to achieve this, you need to:
- Create a connection that points to the Order Information service.
-
Build an integration of type ‘Subscribe To ICS’, where your subscribing system gets the event notification from ICS. In this integration, drag the connection created in the previous step on to the Enrichment Trigger node and use the GetCrossReferenceData operation. The following screenshot shows the configuration of the enrichment service:
- Map the identifiers, source system, and cross referenced data elements in the output of the Sales Order Notification event to the appropriate data elements in the input of the GetCrossReferenceData operation.
-
Map the Sales Order Notification event to your target system. Here you can map data elements from both the output of the Sales Order Notification event as well as the response of the GetCrossReferenceData operation. The following screenshot shows the source side of the mapping illustrating this:
Steps to Enable
Subscription to the Sales Order Notification business event requires you to enable the relevant event triggering points using the Manage Business Event Trigger Points task as shown in the below screen capture:
The fulfillment line-level status values, for which you would like to receive a business event notification, are enabled via the Manage Orchestration Process Definitions task. Here you would search and select the appropriate orchestration process and choose the Edit action. In the Process Details region, select the Status Conditions tab and the Fulfillment Line Status Values subtab. Next, click the Edit Status Rule Set button to bring up the setup page shown below. Check the Notify External Systems checkbox for the appropriate fulfillment line status values for which you would like to generate an event notification, as shown in the following screen capture:
Key Resources
- Oracle Supply Chain Management Cloud: Implementing Order Management, available on the Oracle Help Center.
Oracle Pricing Cloud provides an advanced, flexible price management capability so that you can price products and services for each targeted customer segment while supporting your corporate pricing practices. The price administration functionality allows you to design pricing rules that meet your specific revenue and business objectives. The pricing architecture allows you to configure and customize the software so that you can implement your new pricing rules and processes.
Controlling Pricing and Discounting Practices
In many companies unrestricted pricing and discounting leads to unprofitable orders, and in some cases unaudited business practices, which leads to compliance issues. Pricing guidelines allow you to define rules to control this behavior.
You can define pricing guidelines for price components such as Net Price, Manual Price Adjustment, and Margin. For example, you can set a guideline that the margin on order needs to be above 20%. The guideline rules associated with the pricing strategy are evaluated when the order is validated. For any guidelines that are violated, you are provided with the appropriate warnings based on the type of violation: error, information only, or warning. If authorized, you can override the exceptions and submit the order for further processing.
This ensures that all orders conform to pricing and discount strategies setup by corporate pricing policies, which allows you to manage order profitability, discounting discipline, and compliance.
Steps to Enable
- In the Setup and Maintenance work area, determine the price elements against which to set pricing guidelines in the Manage Price Elements task. For example, to define a pricing guideline based on net price, ensure that the Used in Pricing Guidelines check box is selected for the price element Net Price.
- In the Pricing Administration work area, click the Manage Matrix Classes task, and add conditions to the Pricing Charge Guideline matrix class. You can then use those conditions when defining a new guideline.
Tips And Considerations
A charge can be enabled or disabled for manual price adjustment, which gives control to the pricing administrator for the discounting behavior. This is controlled by selecting the Allow Manual Adjustments check box on the price list charge
Key Resources
- Oracle SCM Cloud: Administering Pricing, available on the Oracle Help Center.
Price Coverage Services on a Service Contract
Pricing is enhanced to support coverage pricing through an integration with Oracle Fusion Service Contracts.
Pricing administrators can now manage coverage pricing rules on a price list. Price lists are enhanced to support the association between coverages and their covered items. The pricing rules for covered items can be defined at the All Items level for one-time and recurring charges. These rules can be based on an amount or a percentage of the covered item's price (charges). Pricing administrators can export and import coverage pricing rules from price lists. Pricing administrators can also search for coverage pricing rules on the Search Pricing Rules page and Pricing Administration work area.
Coverage pricing rules are calculated based on an amount or as a percentage of the covered item's price for a given duration. For example, the price for the Premier Coverage for a laptop for 3 years is $10 per year. Pricing supports one or more charges for a specific coverage and covered item association. These charges can be one-time or recurring charges. Pricing support the calculation of pricing totals to aggregate the extended amount for a given duration.
Steps to Enable
- For percentage-based coverage pricing rules, define a coverage basis in the Manage Pricing Bases task in the Setup and Maintenance work area.
- Ensure that the Manage Time Unit Classes are defined for the UOM in Oracle Enterprise Contracts Cloud.
Key Resources
- Oracle SCM Cloud: Administering Pricing, available on the Oracle Help Center.
- Oracle Sales Cloud: Using Customer Contracts, available on the Oracle Help Center.
Call External Service From Price Execution Algorithms
If you need to obtain pricing information from an external source, Pricing now provides administration services to set up external pricing calls from pricing algorithms. For example, you might want to call a freight costing service or a service to obtain a commodity value for price determination.
Steps to Enable
- Register your target system in the Manage Web Service Details task in the Setup and Maintenance work area.
- Ensure that your web service has been set up in the Manage External Service Details for Algorithms task in the Setup and Maintenance work area. You can register as many services as needed and invoke them in the pricing algorithms using their connector name. When registering a web service, you must provide at least the target system, a name, an invocation mode (synchronous), and the actual connection URL for the service. Optionally, you can provide a brief description as well as authentication credentials if the service is secured.
- Capture your input and output payload details in the Manage Service Mappings task.
- Configure your pricing algorithm as needed based on the business requirement in the Manage Algorithms task.
Key Resources
- Oracle SCM Cloud: Administering Pricing, available on the Oracle Help Center.
Oracle Configurator Cloud is a powerful selling and configuration product that enables you to model products and services that are configurable, multioption, and customizable. Using underlying constraint-based technology, you can model complex customizable products as a series of rules and options. These options guide customers to the best solutions and ensure that only valid configurations are created. This integrated, flexible process eliminates order errors and rework costs. It also automates the order-to-production process to reduce overall sales cycle times.
Integrate Configurator Run Time Across Your Order Capture Channels
In a multichannel environment, your customers will expect key data such as price and product configuration to be the same independent of channel. As such, there is a need to provide consistent order capture across channels and business units. With this release, Configurator provides an embeddable iframe and a set of services that allow you to embed the Configurator run-time user interface in your order capture applications. These services enable you to launch the Configurator run time within an iframe page, validate the configuration, and return the configuration results to the order capture application. This integration allows you to provide a consistent user experience for product and service configuration across your sales channels and business units.
Steps to Enable
No steps are required to enable this feature.
Key Resources
- Oracle Supply Chain Management Cloud: Configurator Modeling Guide, Oracle Help Center.
Call External Service From Configurator Extension Rules
If you need to obtain information to support product configuration from an external source, Configurator now provides administration services to set up external service calls from a configuration extension rule. This allows your product configurator managers to query and retrieve data from external sources and to use the information in the same configuration session.
To register a new web service, from the Setup and Maintenance work area, first launch the Manage External Service Details for Extensions task. Then use the Manage Connector Details page as a guide to register the web service to be used during the external service calls from a configuration extension rule.
The following screen capture shows the Manage Connector Details page:
Steps to Enable
No steps are required to enable this feature.
Key Resources
- Oracle Supply Chain Management Cloud: Configurator Modeling Guide, Oracle Help Center.
Use Extension Rules for Configuration Initialization
Configurator run-time logic can be complex and difficult to model through the configurator statement rules. Extension rules allow you to expand the behavior of the configurator run time, to model more complex logic. With this release, Configurator expands extension rules to allow you to add configuration logic on initialization of a new or restored configuration.
To add configuration logic on initialization of a new or restored configuration, create a new extension rule and provide the Groovy code necessary to perform the business logic. Then during the event binding creation, select the ‘postInitConfig’ event for the event type. The following screen capture shows how to add a new, post-configuration initialization event for an extension rule:
Steps to Enable
No steps are required to enable this feature.
Key Resources
- Oracle Supply Chain Management Cloud: Configurator Modeling Guide, Oracle Help Center.
Support for Decimal Tolerance in Configurator Rules
With this release, Configurator provides improved support for decimal values in rules to ensure that decimal comparisons are evaluated correctly. The Configurator engine now uses a decimal tolerance of 0.000000001 to convert the decimal comparison to a mathematical equation for evaluation.
Steps to Enable
No steps are required to enable this feature.
Key Resources
- Oracle Supply Chain Management Cloud: Configurator Modeling Guide, Oracle Help Center.
Oracle Global Order Promising Cloud is an optional component of Oracle Order Management Cloud that intelligently matches order demand with available supply. As each order arrives, Global Order Promising selects the best fulfillment approach, accounting for current and future availability, destination, expected delivery dates, and preferred delivery methods. Promising alternatives can include manufacturing or buying items to meet demand. You can also handle complex fulfillment scenarios, such as configure-to-order, contract manufacturing, and drop shipment. When supply is limited, Global Order Promising can allocate fixed quantities or percentages to specific customers or channels. Customers benefit from more accurate order promise dates and better utilization of available supply.
Tailor and Segment Views in the Global Order Promising User Interface
You can perform interactive order promising tasks more efficiently with the new modern, flexible Global Order Promising user interface. The new user interface allows you to:
- Easily tailor screens. Set up user-specific and group-specific infotile views with fully configurable supporting details, display promising performance using a wide variety of info graphics, and review supply availability and allocation in pivot tables.
- Segment your work. Use a unified set of data dimensions to select and work on specific supply chain segments across planning and order promising.
Steps to Enable
No steps are required to enable this feature, for viewing predefined analytics.
For custom analytics, select from a comprehensive set of predefined measures, apply predefined dimensions at the levels you prefer, and filter for specific members that you want to view.
Tips And Considerations
- You must first run collections and refresh and start the order promising server in order to view the latest order scheduling performance information in the Global Order Promising work area.
- The scheduled process Refresh Order Promising Analytics ensures that the analytics depict the order scheduling performance accurately. This process runs automatically when you re-schedule an order from the Global Order Promising work area or start the Global Order Promising application.
Key Resources
- Release Training – Global Order Promising Enhancements: Configurable GOP UI, Schedule Expense Destination Transfers, available at OracleCloud:SupplyChain Management Release Readiness.
Schedule Expense Destination Transfers
Inventory transfers can reposition material for delivery to customers, or move it to an internal organization where the material can be consumed for corporate purposes. Goods used internally might be expensed and consumed immediately rather than tracked as on-hand inventory. This release adds a new inventory transfer type and appropriately handles the supply for inventory transfers to these internal expense destinations so that customers can schedule them using Global Order Promising.
Steps to Enable
No steps are required to enable this feature.
Tips And Considerations
To create a fulfillment line corresponding to an expense destination transfer, you need to interface the related transfer order with Order Management.
Key Resources
- Release Training – Global Order Promising Enhancements: Configurable GOP UI, Schedule Expense Destination Transfers, available at Oracle Cloud: Supply Chain Management Release Readiness.
Synchronize Sales Orders with External Order Management Systems
While most Global Order Promising customers will use Order Management to capture and fulfill sales orders, some might want to use on-premise or third-party order management systems to handle some or all of their demand. This release introduces a sales order file load that synchronizes the status of orders from an external system so that Global Order Promising can account for new orders, as well as any changes, cancelations, and completions. As a result, customers can centrally plan and promise orders that are captured across multiple sales channels.
Steps to Enable
- Enable the external system as a collection source for sales orders using the Manage Planning Source Systems page.
- Load the sales order data you require from your external system using the standard file upload facility provided in the Oracle Cloud. In order to support promising of orders for an external system, you will also need to use the file upload facility to load the applicable reference data, supply data, and Global Order Promising rules. Key examples of each type of data are:
- Reference Data– items, item structures, units of measure, customers, suppliers, organizations, calendars, shipping networks, ship methods, resources, routings, sourcing rules, assignment sets
- Supply Data – on hand, purchase orders and requisitions, transfer orders, reservations
- Global Order Promising Rules – ATP rules, ATP rule assignments, allocation rules, allocation rule assignments
- In the Navigator, click the Plan Inputs work area, and then select the Load Planning Data from Flat Files task to complete upload of your data.
Tips And Considerations
- You can now run Global Order Promising independently while maintaining all your supply chain information in an external system, without having to represent them in your Oracle Supply Chain Management Cloud.
- This capability is intended to be used in conjunction with Global Order Promising public web services. Using these web services, Global Order Promising receives orders from an external system in real time, schedules the orders, and then communicates promise dates back to the external system through the web services. The scheduled external system sales orders should then be loaded prior to each restart of the Global Order Promising server so that their demands can be accounted for as Global Order Promising promises future orders.
Appendix A: Function Security Aggregate Privileges
This release includes new roles and privileges that facilitate function security for new features. If you have created custom job roles, then you can add new privileges to those custom roles as needed.
The aggregate privilege in table A-1 is required for the following feature in this release:
Administer Orchestration Infrastructure Web Service Sourcing Rule
Table A-1 Aggregate Privilege for Configurator
Aggregate Privilege Name and Code |
Job Role Name and Code |
---|---|
Administer Orchestration Infrastructure Web Service Sourcing Rule DOO_ADMINISTER_ORCHESTRATION_INFRASTRUCTURE_WEB_SERVICE_SOURCING_RULE |
Product Configurator Manager ORA_CZ_PRODUCT_CONFIGURATOR_MANAGER_JOB |
Appendix B: Function Security Privileges
This release may include new roles and privileges that facilitate function security for new features. If you have created custom job roles, then you can add new privileges to those custom roles as needed.
Table B-1 Function Security Privileges for Order Management
Privilege Name and Code |
Job Role Name and Code |
---|---|
Manage Orchestration Order Trade Compliance Interface Web Service DOO_MANAGE_ORCHESTRATION_ORDER_TRADE_COMPLIANCE_INTERFACE_WEB_SERVICE |
Web Services Application Identity (SCM) FUSION_APPS_SCM_SOA_APPID |
Manage Web Service Interface to Transportation Data for Sales Order DOO_MANAGE_WEB_SERVICE_INTERFACE_TO_TRANSPORTATION_DATA_FOR_SALES_ORDER |
Web Services Application Identity (SCM) FUSION_APPS_SCM_SOA_APPID |
Manage Order Approval Rules FOM_MANAGE_ORDER_APPROVAL_RULES |
Order Administrator ORA_DOO_ORDER_ADMINISTRATOR |
View Order to Cash Infolet Page FOM_VIEW_ORDER_TO_CASH_INFOLET_PAGE |
Order Manager ORA_DOO_ORDER_MANAGER |
Table B-2 Function Security Privileges for Pricing
Privilege Name and Code |
Job Role Name and Code |
---|---|
Administer Orchestration Infrastructure Web Service Sourcing Rule DOO_ADMINISTER_ORCHESTRATION_INFRASTRUCTURE_WEB_SERVICE_SOURCING_RULE |
Pricing Manager ORA_QP_PRICING_ADMINISTRATOR Pricing Administrator ORA_QP_PRICING_ADMINISTRATOR Pricing Analyst ORA_QP_PRICING_ANALYST |
---
Copyright © 2017, Oracle and/or its affiliates. All rights reserved.
This document is provided for information purposes only, and the contents hereof are subject to change without notice.This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.