Implementing Subscription Management Full Docs

Oracle Subscription
Management Cloud
Implementing Subscription
Management
19D
Oracle Subscription Management Cloud
Implementing Subscription Management
19D
Part Number F22086-03
Copyright © 2011, 2019, Oracle and/or its aliates. All rights reserved.
Author: Abhay Singh, Debjit Nag
Contributor: Gnanaprakash Dasari, Carmen Myrick, Carol Robinson, Sudeep Vaidyanathan, Shubhaprada Muthyam
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by
intellectual property laws. Except as expressly permied in your license agreement or allowed by law, you may not use, copy, reproduce, translate,
broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering,
disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you nd any errors, please report
them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then
the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware,
and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition
Regulation and agency-specic supplemental regulations. As such, use, duplication, disclosure, modication, and adaptation of the programs,
including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license
terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use
in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in
dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe
use. Oracle Corporation and its aliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its aliates. 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.
This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle
Corporation and its aliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and
services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its aliates will not be responsible
for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable
agreement between you and Oracle.
The business names used in this documentation are ctitious, and are not intended to identify any real companies currently or previously in existence.
Contents
Preface i
1 About This Guide 1

Audience and Scope ..................................................................................................................................................................... 1
Related Guides ................................................................................................................................................................................ 1
2 Implementation Overview 3
Start Implementing Subscriptions ............................................................................................................................................. 3
Where You Perform Subscriptions Setup Tasks .................................................................................................................... 3
Summary of the Subscriptions Setup Steps ........................................................................................................................... 4
System Requirements .................................................................................................................................................................. 5
3 Subscription Management Setup Checklist 7

Create a Subscriptions Implementation Project ..................................................................................................................... 7
Dene Legal Entities for Subscriptions .................................................................................................................................... 7
Dene Business Units and Assign Business Function, Ledger, and Legal Entity for Subscriptions ............................ 8
Create and Manage Customers ................................................................................................................................................. 9
Dene Party Roles and Contact Roles for Subscriptions .................................................................................................... 10
Set Up User Statuses and User Transitions for Subscriptions .......................................................................................... 10
Dene Unit of Measure ............................................................................................................................................................... 11
Dene Subscription Time Unit Mappings .............................................................................................................................. 12
Dene Order Management Parameters ................................................................................................................................. 12
Manage Items ............................................................................................................................................................................... 12
Dene Pricing ............................................................................................................................................................................... 14
Dene Customer Billing Conguration for Subscriptions ................................................................................................... 15
Dene AutoInvoice Line Ordering Rules ................................................................................................................................ 17
Dene AutoInvoice Grouping Rules ........................................................................................................................................ 17
Dene Receivables Payment Terms ........................................................................................................................................ 18
Dene AutoAccounting Rules ................................................................................................................................................... 18
Subscription Copy Map .............................................................................................................................................................. 18
Register Third Party Applications for Subscriptions ........................................................................................................... 20
Dene Subscription Cancellation Reasons ............................................................................................................................ 20
Dene Subscription Close Reasons ........................................................................................................................................ 20
Scheduled Processes for Subscriptions .................................................................................................................................. 21
4 Common Application Setup Concepts 23

Users and Security ...................................................................................................................................................................... 23
Currencies ..................................................................................................................................................................................... 26
Enterprise Structures .................................................................................................................................................................. 27
5 Conguring Subscriptions 31
Create and Manage Subscription Proles .............................................................................................................................. 31
Create and Manage Subscription Renewal Templates ....................................................................................................... 32
Create and Manage Subscription Event Notication Rules and Template Sets ............................................................ 34
Create Subscription Rules ......................................................................................................................................................... 35
Create Coverage Calendar Schedule and Exceptions ......................................................................................................... 36
Create Standard Coverage ........................................................................................................................................................ 36
Create Default Coverage ........................................................................................................................................................... 37
Generate Data Model XML ....................................................................................................................................................... 37
Create and Manage Account Receivables Service Mappings ........................................................................................... 38
Set Up Coverage Services ......................................................................................................................................................... 42
6 Seing Up Subscription 360 45

Enable Subscription 360 in Accounts .................................................................................................................................... 45
Congure the Subscriptions Role for Salespeople .............................................................................................................. 45
7 Revenue Management Integration 47

Integration Overview .................................................................................................................................................................. 47
Integration Set Up Steps ........................................................................................................................................................... 48
Examples of Subscription Activation Impact on Revenue Management ....................................................................... 48
Oracle Subscription Management Cloud Preface
Preface
This preface introduces information sources that can help you use the application.
Using Oracle Applications
Help
Use help icons to access help in the application. If you don't see any help icons on your page, click your user image
or name in the global header and select Show Help Icons. Not all pages have help icons. You can also access the Oracle
Help Center to nd guides and videos.
Watch: This video tutorial shows you how to nd and use help.

You can also read about it instead.
Additional Resources
• Community: Use Oracle Cloud Customer Connect to get information from experts at Oracle, the partner
community, and other users.
• Training: Take courses on Oracle Cloud from Oracle University.
Conventions
The following table explains the text conventions used in this guide.
Convention Meaning
boldface Boldface type indicates user interface elements, navigation paths, or values you enter or select.
monospace Monospace type indicates le, folder, and directory names, code examples, commands, and URLs.
> Greater than symbol separates elements in a navigation path.
i
Oracle Subscription Management Cloud Preface
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website.
Videos included in this guide are provided as a media alternative for text-based help topics also available in this guide.
Contacting Oracle
Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For
information, visit My Oracle Support or visit Accessible Oracle Support if you are hearing impaired.
Comments and Suggestions

Please give us feedback about Oracle Applications Help and guides! You can send an e-mail to:
oracle_fusion_applications_help_ww_grp@oracle.com.
ii
Oracle Subscription Management Cloud Chapter 1
Implementing Subscription Management About This Guide
1 About This Guide
Audience and Scope

This guide provides information for implementors and administrators when conguring and seing up Oracle
Subscription Management. It summarizes and details specic setup tasks for Subscription Management. It also is
designed as a reference to conguring required Oracle Applications Cloud common application features at a high level.
This guide assumes your company's application cloud service is up and running at a basic level, for example, as
described in the use case contained in the Oracle Engagement Cloud Geing Started with Your Implementation guide.
Note: With release 19A (11.13.19.01.0), "Oracle Sales Cloud" has been incorporated within "Oracle Engagement
Cloud." Existing Oracle Sales Cloud users will retain access to Oracle Sales Cloud features under their
preexisting licensing agreements. Any new users created within your current Oracle Sales Cloud license
count will also retain the same access to Oracle Sales Cloud. Users may obtain access to additional Oracle
Engagement Cloud features by renewing their subscriptions under the Oracle Engagement Cloud SKU. This
document describes features available to users under both Oracle Sales Cloud and Oracle Engagement Cloud
licensing agreements.
Related Guides
In addition to this guide, you may want to consult other guides when seing up, conguring, and managing
Subscription Management. Here are other guides that can help you understand more about the setups and functionality
mentioned in this guide.
Guide Description
Using Subscription Management Provides overviews of the product and subscription life cycle, plus details procedures for
subscription users in the application.

Oracle Engagement Cloud Describes your initial Oracle Engagement Cloud implementation procedures, based on a
Geing Started with Your Sales simple sales-force-automation use case.
Implementation

Oracle Applications Cloud Using Describes how to use the Setup and Maintenance work area when implementing and
Functional Setup Manager conguring Oracle Engagement Cloud.

Oracle Engagement Cloud Provides a reference to conceptual information and procedures required to implement
Implementing Sales components and features of Oracle Engagement Cloud.

Oracle Engagement Cloud Using Contains information to help sales managers, salespeople, and other sales end users when
Sales using Oracle Engagement Cloud to perform their day-to-day tasks.

1
Implementing Subscription Management About This Guide
Guide Description
Oracle Engagement Cloud Extending Describes how to create and enhance objects and congure the user interfaces and navigation
Sales and Service menus.

Oracle Engagement Cloud Securing Contains information to help setup users and sales administrators congure access to Oracle
Sales and Service Engagement Cloud functionality and data.

Oracle Engagement Cloud Security Provides a reference of roles, role hierarchies, privileges, and policies as delivered for the
Reference for Sales and Service Oracle Engagement Cloud.

2
Implementing Subscription Management Implementation Overview
2 Implementation Overview
Start Implementing Subscriptions

To start an implementation of Oracle Subscription Management, a user with the Application Implementation Consultant
role (ORA_ASM_APPLICATION_IMPLEMENTATION_CONSULTANT_JOB) must opt in to the oerings applicable to
your business requirements. Refer to the Oracle Applications Cloud Using Functional Setup Manager guide to manage
the opt-in and setup of your oerings. Users must have the Subscription Specialist role to access Subscription
Management.
Subscriptions
Use the Subscriptions functional area in the Sales oering to congure Subscription Management.
Here are the functional areas you must set up to enable the oering. For a full list of functional areas and features in this
oering, use the Associated Features report that you review when you plan the implementation of your oering.
Functional Area Description
Company Prole Use this functional area to set up the common CRM Business Units prole options.

Sales Foundation Use this functional area to set up public unique identier prole options.

Subscriptions Use this functional area to set up subscriptions.

Related Topics
• Oracle Applications Cloud Using Functional Setup Manager
• Plan Your Implementation
Where You Perform Subscriptions Setup Tasks

You mainly access two areas when seing up, conguring, and managing Subscription Management from an
implementation perspective: the Setup and Maintenance and the Subscription Management work areas.
Setup and Maintenance Setups

For the Setup and Maintenance tasks, you go to:
• Oering: Sales
3
• Functional Area: Subscriptions
Subscription Management Work Area Setups

Once you have done the setups in the Setup and Maintenance work area, go to the Subscription Conguration work
area to congure these rules:
• Subscription Rules
• Event Models
• Entitlement Availability and Coverage
• Asset Lifecycle Management
• Subscription Preview
Related Topics
• Create Subscription Rules
• Create and Manage Subscription Proles
• Create and Manage Subscription Renewal Templates
• Create Standard Coverage
Summary of the Subscriptions Setup Steps

Here's a summary of the setup steps that you will need to perform to set up Subscription Management.
Setup Step Where You Find More Information
Congure the Subscriptions oering See the Create a Subscriptions Implementation Project topic.
and create an implementation project

Dene legal entities See the Dene Legal Entities for Subscriptions topic.

Dene business units, assign See the Dene Business Units and Assign Business Function, Ledger, and Legal Entity for
business functions, and assign ledger Subscriptions topic.
and legal entity

Dene Party Roles and Contact Roles See the Dene Parry Roles, Contact Roles, and Role Sources topic.
for Subscriptions

Manage user statuses and user See the Set Up User Statuses and User Transitions for Subscriptions topic.
transitions

Manage time unit mappings See the Specify Time Unit Mappings topic.

4
Setup Step Where You Find More Information
Dene pricing See the Dene Pricing for Subscriptions topic.

Dene Customer Billing Conguration

for Subscriptions See the following topics:

• Dene Customer Billing Conguration
• Dene AutoInvoice Line Ordering Rules
• Dene AutoInvoice Grouping Rules
• Dene Receivables Payment Terms
• Dene AutoAccounting Rules
Subscription Copy Map See the Subscription Copy Map topic.

Register Third Party Applications for See the Register Third Party Applications for Subscriptions.
Subscriptions

Dene Subscription Cancellation See the Dene Subscription Cancellation Reasons.

Reasons

Dene Subscription Close Reasons See the Dene Subscription Close Reasons.

Set up application users See the Common Application Setup Concepts chapter.

Congure customer billing See the Dene Customer Billing Conguration for Subscriptions topic.

Manage subscription rules See the Conguring Subscriptions chapter.

Entitlements Management See the Conguring Subscriptions chapter.

System Requirements
Before using Oracle cloud applications in browsers and on your mobile devices, check the supported browsers and
other system requirements. For information about system requirements, see hps://www.oracle.com/system-
requirements/. For previous releases, scroll to the end of the page and nd the system requirements link for the
applicable previous release.
Related Topics
• System Requirements for Oracle Applications Cloud
5
6
Implementing Subscription Management Subscription Management Setup Checklist
3 Subscription Management Setup Checklist
Create a Subscriptions Implementation Project

Create an implementation project to congure Subscription Management.
1. Navigate to My Enterprise and select Oerings.
2. On the Oerings page, select the Sales oering and then click Opt In Features.
3. On the Opt In page, enable Subscriptions and click Done.
4. Go to the Setup and Maintenance work area.
5. Open the Tasks side panel and click Manage Implementation Projects.
6. On the Implementation Projects page, click Create to begin creating a project.
7. Enter your project name and click Next.
8. Expand Sales, include Sales and Subscriptions, and then click Save and Open Project.
Once you open the project, you can congure all the appropriate tasks.
Dene Legal Entities for Subscriptions

To dene legal entities for use with subscriptions, proceed as follows:
1. In your implementation project, go to the Manage Legal Addresses task.
2. Select a country from the Country drop-down list, and a new location.
3. Enter the new location information on the Location Create page.
4. Click Save and Close.
5. In your implementation project, search for the Dene Legal Entities for Sales task list and open the Manage
Legal Entity task.
6. On the Select Scope page select Manage Legal Entity.
7. Select the Create New option from the Legal Entity drop-down list.
8. Click Apply and Go to Task.
9. Click Create.
10. On the Create Legal Entity page, select your country.
11. Enter the name of the legal entity and the identier.
12. Optionally enter Start Date. When the start date is blank the legal entity is eective from the creation date.
13. Optionally enter an End Date.
14. Optionally, if your legal entity should be registered to report payroll tax and social insurance, select the Payroll
statutory unit check box.
15. Optionally, if your legal entity has employees, select the Legal employer check box.
16. Optionally, if this legal entity is not a payroll statutory unit, select an existing payroll statutory unit to report
payroll tax and social instance on behalf of this legal entity.
17. In the Registration Information section, select a legal address and enter the Legal Reporting Unit Registration
Number.
18. Enter the EIN or TIN.
20. In your implementation project, select Dene Legal Entities for Sales from the task list.
21. Click the Select and Add icon. Search for and add the following tasks to the Dene Legal Entities for Sales
folder: Manage Legislative Data Groups and Manage Legal Entity HCM Information.
7
22. Use the Manage Legislative Data Groups task to dene at least one legislative data group for each country or
territory where your enterprise operates. See the Implementing Global Payroll Interface guide. Select your legal
entity and proceed.
23. On the Manage Legislative Data Groups page, click Create.
24. Enter the name of the legislative data group.
25. Select the country and currency.
26. Optionally, select the cost allocation structure.
27. Click Submit and then Done.
28. Use the Manage Legal Entity HCM Information task to verify information related to the payroll statutory units
and the legal employer. See the Implementing Enterprise Structure and General Ledgers guide.
29. Click Done.
Related Topics
• Manage Legislative Data Groups
Dene Business Units and Assign Business Function,

Ledger, and Legal Entity for Subscriptions
A business unit can perform many business functions. A business function represents a business process, or an activity
that can be performed by people working within a business unit and describes how a business unit is used. Also, a
business unit can process transactions on behalf of many legal entities. For example, a payables invoice has an explicit
legal entity eld. Your accounts payables department can process supplier invoices on behalf of one or many business
units. In some cases, your legal entity is inferred from your business unit that is processing the transaction.
1. In your implementation project, navigate to Dene Company Prole for Sales, Dene Business Units for
Sales, and open the Manage Business Unit task
a. Click the create icon.
b. Enter the required information on the Create Business Unit page. Select Create from the Default Set
drop-down list.
c. Create a reference data set and click OK.
d. Select the reference data set created from the Default Set drop-down list and click Save and Close.
2. Navigate to Dene Company Prole for Sales, Dene Business Units for Sales, and click Select for the task
Assign Business Unit Business Function to select the business unit you created as the task list scope
a. Click Select and Add in the dialog to set the BU you created as the task list scope.
b. Click the task Assign Business Unit Business Function.
c. Enter the required information and click Save and Close. Click the up arrow, and select Subscriptions to
go to the main folder structure.
3. Navigate to Dene Company Prole for Sales, Dene Business Units for Sales, and open the Manage
Business Unit Set Assignment task. You can update or override the reference data set code for a particular
reference data object.
Related Topics
• Business Units
• Business Functions
• Legal Entities
8
Create and Manage Customers

You create customers to properly record and account for sales transactions, as well as to identify other aributes of the
selling relationship. Recording a sales transaction requires that a customer, stored as a party in the trading community
model, has both a customer account and customer site with a bill-to business purpose.
To understand the role of a customer in the context of the trading community model, it's helpful to understand a few
related concepts. The key concepts related to customers and customer activities are:
• Party
• Customer
• Customer Account
• Site
• Relationship
Party
A party is an entity that can enter into a business relationship with another party, such as buying and selling goods
or oering services. A party can be either an organization or a person. A party exists separately from any business
relationship that it enters into with another party.
Customer
A customer is a party, either an organization or a person, with whom you have a selling relationship. This selling
relationship can result, for example, from the purchase of products and services or from the negotiation of terms and
conditions that provide the basis for future purchases.
Customer Account
A customer account represents the aributes of the business relationship that a party can enter into with another party.
The customer account has information about the terms and conditions of doing business with the party.
For example, you can create a commercial account for purchases made by a company for internal use, and a reseller
account for purchases made by the same company for sales of your products to end users.
You can create multiple customer accounts for a party to maintain information about dierent categories of business
activities. For example, to track invoices for dierent types of purchases, you can maintain an account for purchasing
oce supplies and another account for purchasing furniture.
You can also maintain multiple customer accounts for a customer that transacts business with more than one line of
business in your organization.
You can share information about a party, such as prole information, creditworthiness, addresses, and contacts, across
the customer accounts of the party. In addition, you can also maintain separate proles and contacts, along with contact
addresses and contact points, for each customer account.
Site
A site is a point in space described by an address. A party site is the place where a party is physically located.
9
A customer site is a party site that's used in the context of a customer account. A single customer account can have
multiple sites.
A customer address is a site that's used for billing, shipping, or other purposes that are part of the selling relationship.
An identifying address is the party site address that identies the location of the party. Every party has only one
identifying address, but a party can have multiple party sites.
Relationship
A party relationship is the role of the party in the context of another party. Examples include aliate, subsidiary,
partner, employee, or contact.
An account relationship between dierent customer accounts of a party allows for the sharing of billing, shipping, and
payment information.
Here are the steps to dene Organization Name, Accounts, and Sites:
1. Navigate to the Setup and Maintenance work area.

2. Search and select the Manage Customers task.
3. On the Manage Customers page, click the Create icon.
4. On the Create Organization Customer page, enter the required information in the Account Address section.
Note: The information in the Account Address section must match the information dened
for Customer Account Site in the Manage Set Assignments for the Business Unit section.

6. To enter additional accounts for a customer, click the Create icon in the Account section and enter the required
information on the Create Account page.
8. To add sites associated with the account have created, click the Create icon in the Sites section and enter the
required information on the Create Account Sites page.
9. Ensure that there's at least one Site with the Purpose set as Bill to or Bill to and Ship to.
Dene Party Roles and Contact Roles for Subscriptions

Party roles provide a way of specifying the roles of dierent parties in the subscription. For example, a sales contract
may include the customer, a partner, and the internal business unit selling the product or service. The application
comes with predened party roles, but you can create additional roles to suit your needs.
To dene party roles, contact roles, and role sources:
1. In your implementation project, navigate to Dene Subscriptions and open the Manage Subscription Party
Roles task
2. Create new party roles as needed.
3. Navigate to Dene Subscriptions and open the Manage Subscription Contact Roles task.
4. Create new contact roles as needed.
5. For each party role set up in the previous step, enter the required information for the associated contact roles.
10
Set Up User Statuses and User Transitions for

Subscriptions
A subscription has predened statuses that characterizes its life cycle. In addition, you can dene user statuses and their
transitions.
For example, as a subscription specialist you may want to pass the subscription for a more thorough review by the
appropriate team, such as Legal, Financial, and Accounts. You can do this using the user statuses and transitions that
you dene.
To dene user and status transitions:

1. Dene user statuses and their transitions using the Manage Subscription User Statuses and Transitions task.
Note: While dening user statuses, ensure that you select Allow Assignment for each of
the user transitions. This enables you to assign the subscription to named assignees during a
user transition.
2. Use the Event Models tasks from the Subscription Conguration work area to create new events and actions for
the business object oracle.apps.subscriptionManagementsubscriptionService.view.SubscriptionsVO.
a. A new state associated with the new user status must be added to the appropriate event model.
b. The action associated with the "Entry" event of the new state is then set to update the user status code to
the new user status.
c. Add any other possible events for this new state.
d. Link to the existing state by adding a new event for the "DRAFT" state so that your new status is available
for a subscription in Draft status.
3. Set these events up for each To and From state of the user transition. For seeded states you can select from
available events and actions. An example of an action could be a groovy script.
4. Save this new State based event model and specify the condition that can use this. For subscriptions of the
specied condition, the user statuses and transitions that you created are available as Action menu items.
You can use these action menu items to pass a subscription between teams for review before submiing the
subscription for approval.
User statuses and transitions apply only to subscriptions that fulll the condition dened in the Event Model.
Dene Unit of Measure

The way you dene unit of measure conversion for time in Oracle Subscription Management is dierent from other
cloud applications. Time-unit mapping ensures that the scheduling is more accurate than a simple conversion, such as
6 months = 180 days. To dene your own time unit conversions for billing scheduling, you must dene your own time
unit conversions.
To dene unit of measure:
1. Open the Manage Units of Measure Proles task.
2. Search for the Prole Option Code RCS_DEFAULT_UOM_SERVICE_DURATION_CLASS.
3. Select the Prole Value to specify a default unit of measure class.
11
Dene Subscription Time Unit Mappings

Time unit mappings are used to convert the service duration and period between dierent time units. To dene time
unit mappings for the Manage Subscription Time Unit Mappings task:
1. In the Setup and Maintenance work area, search for your implementation project, navigate to Manage
Subscription Time Unit Mappings task .
2. Click the Create icon to dene base units and conversion rate to be applied to user units you have selected for
your time unit UOM.
Dene Order Management Parameters

Specify the item validation organization to validate and display item for the subscription that the user enters for a
business unit.
For example, assume you create a record in the Item Validation Organization list, you set the Business Unit for this
record to Vision Operations, and you set the Organization to Vision America. In this situation, only the items that are
associated with Vision America are displayed when the user creates an order for Vision Operations.
Note:
• You must specify an item validation organization for each business unit. If you do not do this, then
Subscription Management disables search for the item in each subscription that references a business
unit that you do not specify. As an alternative, if you use the same master organization for every business
unit, then you can specify this organization in the Item Validation Organization parameter, and then set the
Business Unit for this parameter to All Business Units.
• You can set the Item Validation Organization only for business units that Subscription Management
associates with your login responsibility. If it associates your login responsibility with only one business unit,
then it uses this business unit as the item validation organization.
To dene Order Management Parameters:
1. In your implementation project, navigate to Dene Subscriptions and open the Manage Order Management
Parameters task.
2. Click Item Validation Organization in the General tab and select a business unit and organization from the
drop-down lists. Add or remove rows, if necessary.
Manage Items
Use the Product Management application to create and manage included warranty, coverage, and subscription items.
12
Create Included Warranty Items

To create an included warranty item:
1. Go to Product Management > Product Information Management.
2. Expand the Tasks region and select Create Items.
3. On the Create Item page, select the organization , enter the number of items, and select the item class.
Ensure that the selected list does not contain any template.
4. Click Ok.
5. Enter the item name and description.
6. Select the item status and lifecycle phase.
7. Ensure that the primary unit of measure, in the Mandatory Aributes section, is same as the primary unit of
measure in the Unit of Measure section.
8. Go to the Specications tab and select Item Organization > Service.
a.In the Asset section, select Customer Asset from the Enable Asset Tracking drop-down list.
b.In the Service section, set Enable Contract Coverage to Yes.
c.In the Service Contracts section, select Fixed from the Service Duration Type drop-down list.
d.In the Service Contracts section, select Milestone from the Service Start Type drop-down list. This
refers to the customer asset shipment date.
e. In the Service Contracts section, enter the Service Start Delay days. The Included Warranty Start Date is
Asset Shipment Date + Service Start Delay days.
f. In the Service Contracts section, select an appropriate standard coverage.
9. Go to the Specications tab and select Item Organization > Sales and Order Management .
a. In the Order management section, set Customer Ordered to No.
b. In the Order management section, set Customer Orders Enabled to No.
c. In the Order management section, select Included Warranty from the Sales Product Type drop-down
list.
10. In the Relationship tab, create a relationship for the item. Ensure that the relationship type is Warranty.
11. Click Save.
Create Coverage Items

To create a coverage item:
4. Click Ok.
7. Ensure that the primary unit of measure, in the Mandatory Aributes section, is same as the primary unit of
measure in the Unit of Measure section.
8. Go to the Specications tab and select Item Organization > Service.
a. In the Asset section, select Not Tracked from the Enable Asset Tracking drop-down list.
b. In the Service Contracts section, select Open Ended from the Service Duration Type drop-down list.
13
c. In the Service Contracts section, Enter the Service Start Delay days. The Included Warranty Start Date is
Asset Shipment Date + Service Start Delay days.
d. In the Service Contracts section, select an appropriate standard coverage.
9. Go to the Specications tab and select Item Organization > Sales and Order Management .
a. In the Order management section, set Customer Ordered to Yes.
b. In the Order management section, set Customer Orders Enabled to Yes.
c. In the Order management section, select Extended Warranty, Service Level Agreements, or Software
Maintenance from the Sales Product Type drop-down list.
10. Click Save.
Create Subscription Items

To create a subscription item:
4. Click Ok.
7. Ensure that the primary unit of measure is Each.
8. Select Sales and Order Management.
9. Set Customer Ordered to Yes.
10. Set Customer Orders Enabled to Yes.
11. Set Sales Product Type to Subscription.
Dene Pricing
You must rst set up the pricing strategy for the subscription. The pricing strategy of the subscription is then retrieved
when the Business Unit, Legal Entity, contract Type, Number and Primary Party are entered during subscription
creation. When lines are added, the pricing information is retrieved automatically.
Oracle Subscription Management supports these charges:
• One-time charges, such as activation fees.
• Recurring charges, such as monthly membership charges.
• Usage-based charges, such as monthly cloud storage consumption fee.
The application identies all the usage-based charges that you dene using the charge prex. You can congure this
prex using the prole option OSS_USAGE_CHARGE_IDENTIFIER.
Use this high-level procedure for quick setup of pricing lines, after your full pricing setups are done in Oracle Supply
Chain Management (SCM) Cloud. See the related topics for additional details. To dene pricing:
1. Sign in to the application with access to pricing administration.
2. Navigate to the Pricing Administration work area.
3. In the Pricing Rules tab, open the price list to which this item is associated.
4. Create a price list line for a coverage item. Click Associated Items to dene unit price and percent price based
on covered items.
14
5. Enter the recurring price details of the item.

6. Create a price list line for a subscription item.
7. Create dierent charges such as one time setup fee, recurring at monthly fee, or recurring usage based fee.
Here is a summary of steps that you need to perform to set up pricing.
Setup Where you nd more information
Create a customer. Create and Manage Customers in the Subscription Management Setup Checklist chapter

Set up pricing charge denition, Manage Pricing Charge Denitions topic in Administering Pricing guide.
charge types and charge sub types.

Create pricing segment. Manage Pricing Segments topic in Administering Pricing guide.

Create customer pricing prole. Manage Pricing Proles topic in Administering Pricing guide.

Create subscription, coverage, and Pricing for Covered Items topic in Administering Pricing guide.
covered asset items.

Create and approve price lists. Manage Price Lists topic in Administering Pricing guide.

Add items to price lists and add one-

time, recurring, and usage charges.

Create a pricing strategy. Add price Manage Pricing Guidelines topic in Administering Pricing guide.
lists with items and charges. Approve
pricing strategy.

Assign a pricing segment and pricing See the Strategies topic in Administering Pricing guide.
prole to a relevant pricing strategy.

For auto adjustments, go to Manage See the Manage Discount Lists topic in Administering Pricing guide.
Discount Lists and create a new
Discount List, add items with auto
adjustment rules and approve. Add
Discount List to pricing strategy that's
being used.

For details, refer to the Oracle Supply Chain Management Cloud, Administering Pricing guide.
Related Topics
• Overview of Subscription Pricing
• Manage Pricing Charge Denitions
• Manage Pricing Segments
• Manage Pricing Proles
• Pricing for Covered Items
15
Dene Customer Billing Conguration for Subscriptions

To dene customer billing conguration, you dene payment terms, dene business unit rules for accounting, and
manage transaction sources.
Use this high-level procedure for quick setup of billing. See the related topics for additional details.
1. Drill down to the Dene Customer Billing Conguration for Subscription Management task in Dene
Subscriptions.
2. Click each task within Dene Customer Billing Conguration for Subscription Management.
◦ Dene payment terms in the Manage Receivables Payment Terms page.
For details about payment terms, see the Dene Payment Terms section in the Oracle Financials Cloud,
Implementing Receivables Credit to Cash guide.
◦ Dene rules based on your Business Unit in the Manage AutoAccounting Rules page.
For details about AutoAccounting, see the Dene AutoAccounting section in the Oracle Financials Cloud,
Implementing Receivables Credit to Cash guide.
◦ Ensure that the seeded transaction source ORA_Subscriptions is present in the Manage Transaction
Sources page. You must use this transaction source when you run your program.
◦ Ensure that the seeded transaction types of ORA_OSS_Credit Memo and ORA_OSS_Invoice are available in the
Manage Transaction Types page.
To dene subscription usage-based billing, proceed as follows:
1. Drill down to the Dene Subscriptions task and click Register Third Party Applications for Subscription.
2. Enter Endpoint URL, User Name and Password, and click Save and Close.
For details about managing auto-invoice, see the Managing AutoInvoice section in the Oracle Financials Cloud, Using
Receivables Credit to Cash guide.
Usage-Based Billing
Oracle Subscription Management support a exible usage rating model comprising of at rate and tiered pricing.
Complex usage rating models can be implement using algorithm extensions. Usage is always billed in arrears.
Note: Subscription Management supports rating summarized usage quantities per billing period. You must
handle the usage data processing, aggregation, and mediation in a third-party application such as PaaS.
16
This graphic describes the usage acquisition and rating.
Related Topics
• Dene Payment Terms
• Dene AutoAccounting
Dene AutoInvoice Line Ordering Rules

Dene an AutoInvoice line ordering rule to organize the transaction lines belonging to a transaction created by the
grouping rule in a specic order.
1. In your implementation project, navigate to Dene Subscriptions > Dene Customer Billing Conguration
for Subscription Management, and open the Manage AutoInvoice Line Ordering Rules task.
2. Click Create.
3. On the Create AutoInvoice Line Ordering Rule page, enter the rule name and eective date.
4. Click Add Row, to create an ordering rule. In the ordering rule, enter the transaction aribute and its sequence.
5. Click Done.
Dene AutoInvoice Grouping Rules

Dene an AutoInvoice grouping rule to identify the transaction aributes that must be identical in order to group
transaction lines on the same transaction.
for Subscription Management, and open the Manage AutoInvoice Grouping Rules task.
2. Click Create to create a grouping rule. Optionally, select ordering rule.
3. Enter name, eective date.
4. Click Add Row, in the Transaction Classes section, and select an appropriate transaction class.
5. For each transactional class, optionally, enter grouping characteristics.
17
Related Topics
• Using AutoInvoice Grouping Rules
Dene Receivables Payment Terms

Use payment terms to identify due dates and discount dates on your customer transactions.
for Subscription Management, and open the Manage Receivables Payment Terms task.
2. Click Create.
3. Select the payment term set.
4. Enter the name of your payment set.
5. Select the discount basis and eective date.
6. Select the installment option.
7. Enter the base amount.
8. Enter payment schedule and the discount for each payment schedule.
Related Topics
• Dene Payment Terms
Dene AutoAccounting Rules

Dene AutoAccounting to specify how to determine the default general ledger accounts for transactions that you
enter manually or import using AutoInvoice. You must dene AutoAccounting before you can enter transactions
in Receivables. When you enter or update transactions, you can override the default general ledger accounts that
AutoAccounting creates.
for Subscription Management, and open the Manage AutoAccounting Rules task.
2. Click the Create icon.
3. Select your business unit and account type.
4. Click Done.
5. Select the business unit. In the Segments region, select the appropriate value source and constant value.
Related Topics
• Dene AutoAccounting
Subscription Copy Map

Subscription copy map enables you to create new subscription by copying aributes from an existing subscription.
The application provides you with these maps to copy subscription and subscription products: Copy Subscription and
Copy Subscription product. You can create your own maps to suit your business.
1. Sign is as a user with Application Composer access and verify that you have an active sandbox.
2. Access Application Composer by selecting Application Composer from the Navigator menu, in the
Conguration category.
18
3. Select Copy Maps, in the Advanced Setup section.

4. Select Copy Subscription, and click Actions > Add.
5. Enter the name of the map and click Ok.
6. In the Application Module Mapping section, enter appropriate information.
Field Description
Map Group Select Copy Subscription

To Select SubscriptionManagementAM

From Select SubscriptionManagementAM

7. In the Entity Mappings section, add a record for each view object that you're copying by completing these
elds.
Field Description
To Select the new view object that you're copying to.

From Select the existing view object that you're copying from.

Query Name Select one of the three query types: Unique Identier, Join, or All Records.

If you select All Records, then don't enter any information in the remaining elds.

Query Aribute If you selected either Unique Identier or Join in the Query Type eld, then select an
aribute to use during runtime. The aribute is used to lter the records that are copied to
the new object. For example, if you select Account Number, then during runtime, only the
records matching the account number passed to the copy map engine are copied.

Joined View Object and Joined

Aribute If you selected Join in the Query Type eld, then use these two elds to specify the following:

◦ The view object to which this object is joined
◦ The aribute used as the basis of the join
8. Select each line in the Entity Mappings section, and add records to the Aribute Mappings section for each of
the aributes by completing these elds.
Field Description
To Select the aribute to which the selected entity is copied.

Referenced View Object If this aribute is a foreign key, select the view object joined by this foreign key. The
application generates new foreign keys that keep the reference intact.
19
Field Description
Primary Key If this aribute is a primary key, select this check box. Instead of copying the value in the
From object, the application generates a unique value for this key eld in each record in the
To object.

From Select the aribute from which the selected entity is copied.

From Expression Optionally, you can enter a Groovy expression to change the value in this aribute. For
example, you want to change the value of the From object to some new value in the aribute
of the To object. You can also enter a constant to ll this aribute with a constant value in
every record of the To object.


10. Specify the map in the OSS_COPY_SUBCR_MAP prole option.
Similarly, you can create maps to copy subscription products. Use the default Copy Subscription Product map to create
your map. Once you have created your map, use the OSS_COPY_SUBCR_PRODUCT_MAP prole option to specify your
map.
Register Third Party Applications for Subscriptions

To retrieve usage-related data for billing, you need to register third-party application in your subscription.
1. In you implementation project, navigate to the Dene Subscriptions task and click Register Third Party
Applications for Subscription.
2. Click New.
3. Enter application name, integration type, endpoint URL, user name, and password.
Dene Subscription Cancellation Reasons

To dene cancellation reason for your subscriptions, proceed as follows:
1. In you implementation project, navigate to the Dene Subscriptions task and click Manage Subscription
Cancellation Reasons.
The default cancellation reasons are available in the Subscription Cancellation Reasons lookup.
2. To add a lookup code, click New, in the lookup codes region.
3. Enter the lookup code, display sequence, start and end dates, meaning, and description.
4. Click Save.
20
Dene Subscription Close Reasons

To dene close reasons for subscriptions, proceed as follows:
1. In you implementation project, navigate to the Dene Subscriptions task and click Manage Subscription
Close Reasons.
The default close reasons are available in the Subscription Close Reasons lookup.
2. To add a lookup code, click New, in the lookup codes region.
3. Enter the lookup code, display sequence, start and end dates, meaning, and description.
4. Click Save.
Scheduled Processes for Subscriptions

Here are the scheduled processes:
• Fetch and Rate Usage (optional if you don't have usage data):
◦ Acquire Subscription Usage Data from an External Web Service

◦ Fetch Pricing Information for Subscriptions and Generate Billing Schedule
• Interface Invoices to AR and Post Invoice Details in Subscriptions
◦ Send Subscription Billing Information to Receivables

◦ Import AutoInvoice (with transaction source as ORA_Subscriptions). This job needs to be run in Account
Receivables.
◦ Fetch Subscription Invoice Information from Receivables
• Interface Subscriptions to Revenue Management Cloud
◦ Send Subscription Revenue Information to Oracle Revenue Management Cloud

◦ Validate Customer Contract Source Data
◦ Identify Customer Contracts
21
22
Implementing Subscription Management Common Application Setup Concepts
4 Common Application Setup Concepts
Users and Security

Overview of Users and Security Setup
Access to the cloud application functionality and data is secured using role-based access control. In a role-based access
control model, users are assigned roles, and roles are assigned access privileges to protected system resources. Initial
access is limited to one initial user that Oracle creates. Using this initial user, you create other required users, such as
setup users, the sales administration user, and application users. You then provision each user with roles, which provide
access to application functions and data.
Sales users who access the transactional UI, such as the Leads and Opportunities work areas, are created as resources
and are known as sales resources.
To set up default preferences for users and roles, you access the Security Console as a setup user or other user with
the IT Security Manager job role. Only setup users, or other users with the IT Security Manager job role, can access the
Security Console. You perform user-related tasks both during implementation and later as requirements emerge. If you
are a new customer, follow the steps in the Oracle Engagement Cloud Geing Started with Your Sales Implementation
guide. For ongoing maintenance of users, use the Users and Security functional area in Setup and Maintenance and
the Users and Roles task in the Navigator. For more information about creating and importing users, see the Geing
Started with Your Sales Implementation guide. For more information about seing up security and provisioning roles to
users, see the Oracle Engagement Cloud Securing Sales and Service guide. You can nd these guides on the Oracle Help
Center site, linked in the Related Topics section of this topic.
LDAP Identity Store

The Oracle Cloud authentication providers access the LDAP identity store, which is a logical repository of enterprise
user identity data. Your LDAP directory stores denitions of LDAP user accounts. In general, changes you make to user
accounts are automatically synchronized between the sales applications and your LDAP directory server. However, you
must also run processes on a daily basis to manage information exchange between your application and your LDAP
directory server. For information, see the chapter about seing up application security in the Securing Sales and Service
guide.
Setup Tasks in the UI and Other Setup Options

As a setup user, you access multiple tasks in Setup and Maintenance to create and maintain users. You also have
additional setup options to consider. The following table describes these tasks and setup options.
Setup Task or Option and Description

Navigation
Manage Job Roles Task

Oracle provides many predened job roles. The relevant sales roles are listed in the Geing
Navigation: Setup and Maintenance Started with Your Sales Implementation guide.
> Sales Oering > Users and Security
functional area

23

Navigation
You perform the Manage Job Roles task to:
• Review the role hierarchy of a job or abstract role.

• Create custom job and abstract roles.
• View the roles assigned to a user and list the users who have a specic role.
This task opens the Roles tab of the Security Console.
Manage Duties Task

You perform the Manage Duties task to:
Manage Sales and Service Access
Management Task • Review the duties of a job or abstract role.
• Manage the duties of a custom job or abstract role.
Navigation: Setup and Maintenance • Create custom duty roles.
functional area
This task opens the Roles tab of the Security Console.
Manage Data Security Policies Task You use the Manage Data Security Policies task to manage the data security policies that
determine grants of entitlement to a user or role on an object or aribute group. This task
Manage Sales and Service Access opens the Roles tab of the Security Console.
Task
You can also use the Manage Sales and Service Access task to review and congure
Navigation: Setup and Maintenance data security. This task opens the Sales and Service Access Management work area. For
> Sales Oering > Users and Security information, see the Securing Sales and Service guide.
functional area

Users and Roles Task You create application users in the UI using the Users and Roles task. A user with the IT
Security Manager job role performs the Manage Users tasks.
Navigation: Navigator > Users and
Roles item or Setup and Maintenance Note: You can also create sales users by importing users. For information on the
functional area user import options available, see the Oracle Engagement Cloud Understanding
Import and Export Management guide.

Manage HCM Role Provisioning Rules Oracle provides predened role mapping rules for provisioning many of the standard job
Task roles included with the application. However you can create any additional role mappings you
need to control the provisioning of roles to application users using the Manage HCM Role
Navigation: Setup and Maintenance Provisioning Rules task. For example, you can create a role mapping to provision the Channel
Sales Oering > Users and Security Sales Manager role automatically to specied sales managers.
functional area

File-Based Data Import You can import users in bulk using le-based data import. See the Understanding File-Based
Data Import and Export guide for more information.

Import Partner Users Task You can also import partner contact data using the Import Partner Users task. For more
information, see the Oracle Engagement Cloud Geing Started with Your Partner Relationship
Manage File Import Activities Management Implementation guide.

Single Sign-On Authentication Single sign-on authentication, which enables users to sign in once and access multiple
applications, is optionally available for user authentication. If your enterprise has moved from
a traditional on-premises environment to an Oracle Cloud implementation, you might want to
24

Navigation
use your existing identity management solution for authenticating your employees, and you
might also want to provide a single sign-on experience. Implementing federated single sign-
on lets you provide users with single sign-on access to applications and systems located across
organizational boundaries. For additional information, see Oracle Applications Cloud Service
Entitlements (Doc ID 2004494.1) on My Oracle Support at hps: / /supportoraclecom.

Reseing User Passwords Setup users, who are provisioned with the IT Security Manager job role, can use the Users tab
in the Security Console work area to reset passwords for all application users. Users who can't
access the Security Console can reset only their own passwords using the Set Preferences link
in the Seings and Actions menu available by clicking their user name in the application or by
using the Forgot Password link on the sign-in page. See the Geing Started with Your Sales
Implementation guide for more information.

Updating Email Addresses Use the Users tab in the Security Console work area to change user email addresses. You
can use the procedure described in this topic to update addresses of both setup users and
sales users. If you are updating the email addresses of sales users, then you can also use
the same import process you use to create them. See the Geing Started with Your Sales
Implementation guide for more information.

Note: Other data security tasks listed in the Users and Security functional area task list do not apply to the
sales applications. Follow the guidance in the Geing Started with Your Sales Implementation guide and the
Securing Sales and Service guide.
About Sales Resources

After creating your setup users and the sales administrator, you create sales resources. Creating resources is covered
in the Geing Started with Your Sales Implementation guide. Ongoing maintenance of sales resources is performed by
the sales administrator and by other transactional users, such as sales managers. Sales resources can also update their
own information. Some of these tasks (setup-related) are covered in this chapter. For tasks related to maintaining sales
resource information, such as proles, photos, and the like, refer to the Using Sales guide.
Related Topics
• Oracle Engagement Cloud Geing Started with Your Sales Implementation guide
• Oracle Engagement Cloud Securing Sales and Service guide
• Managing Resources chapter of the Oracle Engagement Cloud Using Sales guide
• Oracle Help Center
• Report on System User Activity
Dene Setup Users

One of your rst tasks when seing up the application is the creation of users who can perform setup tasks.
Oracle creates an initial user for you when your environment is provisioned. This initial user is congured to perform
security tasks, such as creating other users and granting additional privileges. As an initial user you can create users,
known as setup users, to help with application setup. The setup user performs the tasks in implementation projects,
sets up enterprise structures, creates application users, and administers security.
25
Use the Manage Users task in the Setup and Maintenance work area to create setup users. You can access this task in
the Setup and Maintenance work area by selecting these options:
• Oering: Customer Data Management
• Functional Area: Users and Security
• Task: Manage Users
For information about creating setup users, see the Oracle Engagement Cloud Geing Started with Your Sales
Implementation guide.
Related Topics
• Oracle Engagement Cloud Geing Started with Your Sales Implementation guide
• Oracle Engagement Cloud Securing Sales and Service guide
Currencies
Seing Up Multiple Currencies
The applications support multiple currencies, multiple daily rates, and currency rate conversion. If you're going to use
multiple currencies, at a minimum you need to:
• Specify corporate currency: You may have already done this if you were following the currency setup in the
Geing Started With Your Implementation guide. If you have already specied your corporate currency, you do
not need to do so again.
• Specify the default currency: You may already have done this if you were following the currency setup in the
geing started guide. If so, you do not need to do it again.
• Import or enter daily currency conversion rates.
• Enable the currencies you are going to use, if you previously disabled them.
Points to Consider for Currencies

When creating or editing currencies, consider these points relevant to entering the currency code, date range, or symbol
for the currency.
Currency Codes
You can't change a currency code after you enable the currency, even if you later disable that currency.
Date Ranges
You can enter transactions denominated in the currency only for the dates within the specied range. If you don't enter
a start date, then the currency is valid immediately. If you don't enter an end date, then the currency is valid indenitely.
Symbols
Some applications support displaying currency symbols. You may enter the symbol associated with a currency so that it
appears along with the amount.
26
Related Topics
• What's the dierence between precision, extended precision, and minimum accountable unit for a currency
• What's a statistical unit currency type
• Euro Currency Derivation
Enterprise Structures
Overview of Legal Entities
A legal entity is a recognized party with rights and responsibilities given by legislation.
Legal entities have the following rights and responsibilities to:
• Own property
• Trade
• Repay debt
• Account for themselves to regulators, taxation authorities, and owners according to rules specied in the
relevant legislation
Their rights and responsibilities may be enforced through the judicial system. Dene a legal entity for each registered
company or other entity recognized in law for which you want to record assets, liabilities, expenses and income, pay
transaction taxes, or perform intercompany trading.
A legal entity has responsibility for elements of your enterprise for the following reasons:
• Facilitating local compliance
• Minimizing the enterprise's tax liability
• Preparing for acquisitions or disposals of parts of the enterprise
• Isolating one area of the business from risks in another area. For example, your enterprise develops property
and also leases properties. You could operate the property development business as a separate legal entity to
limit risk to your leasing business.
The Role of Your Legal Entities

In conguring your enterprise structure in Oracle Fusion Applications, the contracting party on any transaction is always
the legal entity. Individual legal entities:
• Own the assets of the enterprise
• Record sales and pay taxes on those sales
• Make purchases and incur expenses
• Perform other transactions
Legal entities must comply with the regulations of jurisdictions, in which they register. Europe now allows for companies
to register in one member country and do business in all member countries, and the US allows for companies to register
in one state and do business in all states. To support local reporting requirements, legal reporting units are created and
registered.
27
You are required to publish specic and periodic disclosures of your legal entities' operations based on dierent
jurisdictions' requirements. Certain annual or more frequent accounting reports are referred to as statutory or external
reporting. These reports must be led with specied national and regulatory authorities. For example, in the United
States (US), your publicly owned entities (corporations) are required to le quarterly and annual reports, as well as other
periodic reports, with the Securities and Exchange Commission (SEC), which enforces statutory reporting requirements
for public corporations.
Individual entities privately held or held by public companies don't have to le separately. In other countries, your
individual entities do have to le in their own name, as well as at the public group level. Disclosure requirements are
diverse. For example, your local entities may have to le locally to comply with local regulations in a local currency, as
well as being included in your enterprise's reporting requirements in dierent currency.
A legal entity can represent all or part of your enterprise's management framework. For example, if you operate in a
large country such as the United Kingdom or Germany, you might incorporate each division in the country as a separate
legal entity. In a smaller country, for example Austria, you might use a single legal entity to host all of your business
operations across divisions.
Overview of Business Units

A business unit is a unit of an enterprise that performs one or many business functions that can be rolled up in a
management hierarchy. A business unit can process transactions on behalf of many legal entities. Normally, it has a
manager, strategic objectives, a level of autonomy, and responsibility for its prot and loss. Roll business units up into
divisions if you structure your chart of accounts with this type of hierarchy.
In Oracle Fusion Applications you do the following:
• Assign your business units to one primary ledger. For example, if a business unit is processing payables
invoices, then it must post to a particular ledger. This assignment is required for your business units with
business functions that produce nancial transactions.
• Use a business unit as a securing mechanism for transactions. For example, if you run your export business
separately from your domestic sales business, then secure the export business data to prevent access by the
domestic sales employees. To accomplish this security, set up the export business and domestic sales business
as two separate business units.
The Oracle Fusion Applications business unit model provides the following advantages:
• Enables exible implementation
• Provides consistent entity that controls and reports on transactions
• Shares sets of reference data across applications
Business units process transactions using reference data sets that reect your business rules and policies and can dier
from country to country. With Oracle Fusion Application functionality, you can share reference data, such as payment
terms and transaction types, across business units, or you can have each business unit manage its own set depending
on the level at which you want to enforce common policies.
In summary, use business units for:

• Management reporting
• Transaction processing
• Transactional data security
• Reference data sharing and denition
28
Brief Overview of Business Unit Security

A number of Oracle Fusion Applications use business units to implement data security. You assign roles like Accounts
Payable Manager to users to permit them to perform specic functions, and you assign business units for each role to
users to give them access to data in those business units. For example, users who have been assigned a Payables role
for a particular business unit, can perform the function of payables invoicing on the data in that business unit. Roles can
be assigned to users manually using the Security Console, or automatically using provisioning rules. Business Units can
be assigned to users using the Manage Data Access for Users task found in Setup and Maintenance.
Related Topics
• Reference Data Sets and Sharing Methods
29
30
Implementing Subscription Management Conguring Subscriptions
5 Conguring Subscriptions
Create and Manage Subscription Proles

A subscription prole consists of its pricing and billing strategy and a layout template.
Subscription proles have unique aributes, which upon selection determine the billing schedules of the subscription.
As a setup user, you can create subscription proles that salespeople can use during subscription creation. For example,
if you select Advance Invoice as the Invoicing Rule, it guarantees that the billing takes place before the period begins.
You can change your billing aributes when creating the subscription as long as the status is Draft.
To create a subscription prole:
1. Sign in as a setup user.

2. Go to the Subscription Management work area.
3. On the Subscriptions landing page, click the Subscription Conguration tab.
4. Click Manage Subscription Rules.
5. Click the Subscription Proles subtab.
6. Click Create.
7. On the Create Subscription Prole page, enter the prole name.
8. Enter pricing and billing information. This section consists of aributes that specify the subscription's billing
schedule and pricing details.
This table describes the pricing and billing parameters.
Parameter Description
Bill Service The options are: Bill, Do not bill, Bill on renewal.

Invoicing Rule You can choose between bill payments in the form of 'Advance Invoice' and 'Arrears Invoice'.

Billing Frequency You can choose the following billing periods: Month, Year, Quarter, and Year.

Billing Date You can choose from the following options: Period Start, Period End, Day, and Oset. For
example, if you select Period Start, the billing happens at the start of the dened period. If
you select Oset, then the billing starts after the number of days dened in oset.

The invoice date is controlled by the Billing Date. For example, you can set Billing Date
as Period Start so that the invoice date is always at the beginning of the billing period. In
some situations, you may want to send invoices to Account Receivables 3 days prior so that
invoices can be prepared and sent out to customers on or before the invoice date.

Accounting Rule You can select this to determine the rule for revenue recognition.

Transaction Type You can select this to determine if the billing is going to be an Invoice or a Credit Memo.

31
Parameter Description
Payment Terms You can choose to have various types of payment methods, such as Immediate, Last Day
Month, Due 10th, and so on. This indicates the period within which the customer must pay.

Billing System
The billing system can have a valuer of either Oracle Fusion or Third Party.
If the billing system is Oracle Fusion, then the billing interface errors are wrien
◦ in the appropriate schedule process log le. A mapping exists between Oracle
Subscription Management and Oracle Account Receivables.
If the billing system is Third Party, then the billing interface errors are wrien on
◦ the bill lines. These errors can then be shown BI reports.
You can send the following information to Oracle Account Receivables: line formation,
header information, covered level aributes, and bill line aributes.
Period Start You can choose your billing period to begin either on the date on which the service began:
Service Start, or Calendar month.

Period Type You must choose between Actual and Fixed to determine if the billing period is based on the
number of days in the month, or a xed duration, such as 30 days.

Close Credit Method You can choose from the following: Prorate with credit, Prorate without credit, Full to
determine whether or not partial or full charges will be waived as a refund upon termination.

Invoice Text In order to process the descriptions of the invoice by an accounts receivables application,
you must add aributes for the subscription invoice text. This includes Charge name, Item
name, Bill to date, Bill from date, and so on.

Coverage Invoice Text In order to process the descriptions of the invoice by an accounts receivables application,
you must add aributes for the coverage invoice text. This includes Asset number, Item
name, Bill to date, Bill from date, and so on.

The combination of the Invoicing Rule, Billing Frequency, and Billing Date determine the billing schedule of the
subscription.
9. In the Contract Layout Template section, select a layout template and language.
Create and Manage Subscription Renewal Templates

Subscriptions can be renewed either manually or automatically. A subscriptions user can manually renew subscriptions
using the renew action, or you can congure the application to automatically renew subscriptions. Renewal rules
determine the default renewal actions. The application uses the renewal rules template associated with a subscription to
gather the renewal process, customer acceptance criteria, and internal approval criteria.
32
Subscription renewal makes a copy of the existing source subscription. The source subscription can be in an active or
expired status. The application changes the eectivity and price details on the new renewal subscription based on the
default setup.
The life cycle of a renewal subscription is similar to a newly authored subscription. However, you can congure a
dierent life cycle for a renewal subscription using the Event Model conguration. You can congure an event model
to route the renewal subscription to the customer for acceptance, or to the subscription administrator for internal
approval. You can also activate the subscription without either Customer Acceptance or Internal Approval.
Create a new template by doing this:

2. Go to the Subscription Conguration work area.
3. On the Subscriptions landing page, click the Subscription Conguration tab.
5. Click the Renewal Rules Template subtab.
6. Click Create.
7. On the Create Renewal Rules Template page, enter the details of the template as described here.
8. Enter a name for the template.
9. Select the renewal level. All lines include all the lines from the subscriptions that may include other lines also.
Eligible lines include only eligible lines from subscriptions.
10. Optionally, select Consolidate subscriptions. This option decides whether to consolidate subscriptions during
the renewal process or not. The consolidation process applies to automatic renewals. If you select this option,
then all subscriptions to be renewed over a given period are consolidated into a single subscription.
11. Select the Price Adjustment Type.
If you select Reprice, then the application calculates the latest price of the item at the time of renewal. If
you select Markdown or Markup, then you must enter Price Adjustment Basis and Price Adjustment
Value to adjust the list price of the product. Markup adjusts the price up by the adjustment basis and value.
Alternatively, markdown adjusts the price down by the adjustment basis and value.
12. Enter a value in Days Before Expiration. This is the number of days prior to expiration before the renew
eligible subscriptions process picks the subscription for renewal.
13. Enter the minimum renewal duration. This is the minimum number of days for which the subscription is
renewed.
14. Select the Renewal Period. The renewal is based on the renewal duration and period.
15. Select the Renewal Process.
The three options to congure the renewal process at the time of subscription creation are:
◦ Automatic: The application automatically renews and activates the subscription.

◦ Manual: The renewed subscription is created and placed in draft status.
◦ Do not renew: This option prevents the application from automatically renewing the subscription. If you
select this option, the application removes the Renewal Type column from the dashboard for all lines and
covered assets of the subscription. The subscription specialist can manually renew and email active and
expired subscriptions.
The application renews all subscriptions that you identify for automatic or manual renewal.
16. Select the Customer Acceptance Required and Internal Approval criteria.
This table describes the combinations of Renewal Process, Customer Acceptance, and Internal Approval criteria.
33
Renewal Process Customer Acceptance Internal Approval Description

Required
Automatic Not required Not required The application renews and

activates the subscription.

Automatic Not required Required The application renews and

submits the subscription for
approval.

Automatic Required N/A The application renews

the subscription and
leaves it in the subscription
administrator's queue for
further action. You can
congure event notication
rules to automatically send
the subscription to the
customer for acceptance.

Manual N/A N/A The application renews

the subscription and
leaves it in the subscription
administrator's queue for
further action.

Do not renew N/A N/A The application does not

renew the subscription.

17. Select the Subscription Prole.

18. Select the communication channel. This determines how you want to communicate and engage with your
customers.
19. Optionally select Enable Reminders. This option indicates whether or not your customer receives reminders.
20. Select the applicable Coterminate option.
If you select Latest end date, the all target lines are aligned to the latest target end date. The target
subscription header is also adjusted according to the target lines.
Related Topics
• Subscription Renewal
• Renew Subscriptions
Create and Manage Subscription Event Notication Rules

and Template Sets
Congure templates that your users can use as notications. You can also set up rules to trigger notications.
34
Note: The notication events are sourced from the Customer Notication Event
(ORA_OSS_CUST_NOTIF_EVENTS) lookup.
To create an event notication rules and template set, do the following:

5. Click the Event Notication Rules and Template Set subtab.
6. Click Create.
7. On the Create Event Notication Rules and Template Set page, enter the basic details: Template Name, Start
Date, and Sender Email Address.
8. Click Create, in the Condition region.
Set up the conditions:
Condition Description
Event A specic event in the subscription life cycle. The values are sourced from the event model.

Days before subscription start date The number of days before the renewal start date that you would like to send the
notication.

Notication Type
There are three types of notications:
◦ Quote
◦ Reminder
◦ Any User Dened Type
Customer Acceptance Select between Required and Not Required. Use the indicator to skip the notication for
an auto-renew subscription where customer acceptance is not required for the renewal
subscription activation.

Communication Channel The channel on which the notication will be delivered. If you select email, the application
sends an email to the customer to contact. If you select custom, it includes third-party
portals. The application will then raise a business event with the message and aachment
details.

9. In the Message region, click Create. Select the Language, Message Template, and Message Subject along with
the Start and End date.
Create Subscription Rules

You must select the appropriate subscription prole, renewal template, and event notications for every rule. This
enables the application to support customer-specic and business unit-specic billing, renewal, and notication rules.
35
To manage subscription rules:

5. In the Manage Subscription Rules page, add a row to the table.
6. Set up the Renewal Rules Template and Business Unit conditions as needed. You may also select Subscription
Prole and Event Notication Rules and Template Set.
7. Enter Precedence value, if necessary.
Create Coverage Calendar Schedule and Exceptions

Here are the steps to create your own coverage schedule calendars with the intervals and holidays specic to your
business:
4. Click Entitlements Management > Manage Availability.
5. On the Schedules tab, click Create in the Schedules pane to create a new coverage schedule, or select an
existing entry and click Duplicate to copy and update it.
a. Enter the following details:
• Schedule Name: Name of the coverage schedule
• Time Zone: Time zone for which you're creating the coverage schedule.
b. To include exceptions in the coverage schedule, select an exception from the Exceptions drop-down list.
c. To delete a schedule, click Delete in the Schedules pane.
d. Click Save.
6. To add the holidays, nonworking times, or extended working hours that are applicable to the coverage
schedule, click the Exceptions tab.
a. Click Create in the Exceptions pane to create a new coverage schedule exception, or select an existing
entry and click Duplicate to copy and update it.
b. In the Availability Exceptions section, click Add Event.
c. Enter the name of the exception event, the date and times of the event, and the availability during the
event.
d. Click Save.
e. To delete an exception, click Delete in the Exceptions pane.
You can create multiple coverage schedules and use them as needed in the standard coverage templates.
Create Standard Coverage

Standard coverage acts as a template that contains entitlement rules specifying when milestones are due and for what
conditions.
36
You can create multiple standard coverage templates for the dierent service levels that you want to provide to a
customer. Let's say, you want to create a standard coverage to provide regular service from 9 a.m. to 6 p.m. every day,
for 5 days a week. In addition, you can create a standard coverage that provides service 24 hours a day, 7 days a week.
1. Navigate to the Subscription Conguration work area.
2. Select Standard Coverage, in the Entitlements Management section.
3. On the Manage Standard Coverage page, click Create Standard Coverage.
4. Enter template name, description, and start date.
5. Select an entitlement type.
6. Click Save and Continue.
This way you have created a standard coverage placeholder. Now, you must add entitlements.
1. On the Edit Standard Coverage page, click Actions > Add Entitlements.
2. Select the appropriate conditions from the Edit Covered Level page, and click Next.
3. Select the appropriate result columns, and click Finish.
You can now see the Entitlement Rules section. Next, create the entitlement rules based on the columns that you have
added.
After you create a standard coverage, create a default coverage.
Create Default Coverage

A default coverage applies a standard coverage template to specic customers, or globally for all customers.
4. Click Entitlements Management > Default Coverage.
5. Click Create to add a new coverage.
6. Select the Default Level for the coverage:
◦ Select Global to assign the coverage to all customers.
Then select the standard coverage in the Coverage column that you want to apply to all customers.
◦ Select Customer to assign the coverage to a specic customer.
Then select the customer in the Default Level Value column, and then select the standard coverage in
the Coverage column that you want to apply to that customer.
7. Enter the start and end date for the coverage.
8. Click Save.
Generate Data Model XML

Using the BI Publisher, you can create a new layout template by adding the subscription data model aributes supplied
with the application. To nd the subscription data model aributes, use Generate Data model XML to download the
latest data model aributes as the static XML le.
Here's the list of aribute types included in the downloaded data model XML le:
• Subscription
37
• Subscription additional parties

• Subscription team
• Subscription parties contacts
• Subscription product
• Subscription product charges
• Subscription product charge adjustments
• Subscription product charge tiers
• Subscription product bill lines
• Subscription product bill adjustments
• Subscription covered levels (all child entities)
• Subscription coverage line (coverage entitlement)
• Subscription product relationships
• Custom child at header and product level
Download Data Model XML

Here are the steps to download the data model XML:

4. Click Generate Data Model XML to download the OSSXMLDATA le in the XML format.
Create and Manage Account Receivables Service

Mappings
A service mapping is a referential map that creates relationships between services, sources, entities, and aributes. It
species a group of entities and aributes that a service can retrieve and update. You can use it to model entities and
aributes in a declarative environment.
The Subscription AR Integration service mapping provides a exible mechanism to map subscription aributes and
custom aributes to account receivables interface tables. The additional aributes are used for downstream invoice
grouping, invoice printing, reporting, and so on. The Subscription AR Integration seeded mapping is created between
subscription and account receivables invoice interface. The mapping is supported at the invoice header and invoice
line level. The Subscription AR Integration seeded mapping sends eligible subscription billing information to accounts
receivables. As an administrator, you can modify this seeded mapping, create additional entity aributes, and dene
transformation logic for the aributes.
38
Here's a graphic that shows how a typical Subscription AR Integration service mapping is processed.
Service Mapping
Subscription
Management
- Header
- Line
- Bill Lines
- Sales Credit
- Covered Levels Input SDO
- Charges
Source
Output SDO
Subscription Account Fusion Account

Receivables Interface Receivables
Algorithm Interface Algorithm
Steps for Seing the Subscription AR Integration Service Mapping

Here are the steps for seing the Subscription AR Integration Service Mapping:
1. Create AR Descriptive Flexelds at the line and header level.

2. Create and activate a sandbox. In this sandbox, create the required custom aributes (Subscription,
Subscription Product, Covered Level, and so on) at dierent levels using Application Composer. Duplicate
standard details layout, pull in required custom aributes, and publish the sandbox.
Note: You must ensure that the custom aribute data type match with Service Mapping
aribute data type.
3. Create Service Mapping with required aributes

4. Edit and Publish Algorithm.
5. Create Subscription. Enter required details to verify custom aribute data and activate the subscription.
6. Run the Send Subscription Information to Receivables ESS job.
7. Connect to database and verify database details for custom aributes using:
SELECT * FROM fusion.RA_INTERFACE_LINES_ALL where interface_line_attribute1=<subscription number>;
Conrm that the custom aribute values passed in the subscription are displayed against the corresponding
columns in account receivables interface tables.
39
Create AR Transaction Line Descriptive Flexelds

Here are the steps for creating the line level descriptive exelds:
1. In the Setup and Maintenance work area, go to the Manage Descriptive Flexelds task.
2. Enter RA_CUSTOMER_TRX_LINES in Flexeld Code and click Search.
3. Select the Invoice Lines record from search results and click Edit.
4. Click Create to create a new global segment record and enter the required details.
Note: From the Column Assignment section, note the value selected in the Table Column
eld on the Create Segment page. This value is used in the algorithm and the same column
value is queried in the database for the mapped value.

6. Click Deploy Flexeld.
7. Click OK once the deployment process is complete.
Create AR Transaction Header Descriptive Flexelds

Here are the steps for creating the header level descriptive exelds:
1. In the Setup and Maintenance work area, go to the Manage Descriptive Flexelds task.
2. Enter RA_CUSTOMER_TRX in Flexeld Code and click Search.
3. Select the Invoice Lines record from search results and click Edit.
4. Click Create to create a new global segment record and enter the required details.
Note: From the Column Assignment section, note the value selected in the Table Column
eld on the Create Segment page. This value is used in the algorithm and the same column
value is queried in the database for the mapped value.

6. Click Deploy Flexeld.
7. Click OK once the deployment process is complete.
Congure Service Mappings

Here are the steps you must perform to congure the subscription service mappings:

4. Click Manage Service Mappings.
5. Click Subscription AR Integration.
6. Select an entity from the Entity tab.
7. Click Add Row in the Details section to create custom entity aributes to map the custom descriptive exelds
aributes.
40
Note: Use the sux "_Custom" in the Aribute column when adding a custom descriptive
exelds aribute. For example, let assume that the custom aribute created in above steps
is ListPrice. To enter ListPrice in the Aribute column, you must use "ListPrice_Custom" as
the value.
8. Click the Sources tab.
9. Select the entity and map the new custom aributes to view object aributes.
10. Click the Services tab.
11. Select the entity. Add the new custom aributes and provide the read and write access.
Edit and Publish Algorithm

Here are the steps required for editing and publishing algorithm:
4. Click Manage Algorithms.
5. Select the Subscription Management and Account Receivables Integration algorithm and click Actions > Create
version to create a new version of this algorithm in the In progress status.
6. Click the latest version of the Subscription Management and Account Receivables Integration algorithm to open
it in the edit mode.
7. On the Algorithm tab, click Edit to edit Actions in the Each Row Actions section.
8. On the Edit Actions page, enter the code for adding additional descriptive exelds aributes. Here's the table
that describe the values required in the code:
Name Description Examples of required values
AributeContext This aribute is used to identify the AR TransactionLineD

descriptive exelds.
TransactionInterfaceHeaderD

AributeName Table column or standard column name. ATTRIBUTE8 or BU_NAME

AributeValue Value of the aribute. It can be sourced BillLines. ListPriceCustom

from any subscription entities.
Here BillLines is a subscription entity and
ListPrice_ Custom is an aribute.

FlexContext Descriptive exelds context name Invoice Lines

9. Go to the Variables tab.

10. Select the CustomizationFlag value and update the Default expression value as "True".
Note: The Default expression value is set as "False" by default.
11. Click Save and Close
41
12. Select the same Subscription Management and Account Receivables Integration algorithm and click Actions >
Publish.
Run the Send Subscription Information to Receivables ESS Job

Here are the steps required to run the ESS job after creating and activating a subscription:
1. Navigate to the Scheduled Processes page.
2. In the Search Results region of the Overview page, click Schedule New Process.
3. In the Schedule New Process window, enter Send Subscription Information to Receivables in the Name eld,
and click OK.
4. In the Process Details window, click Submit.
5. In the Conrmation window, click OK.
6. In the Process Details window, click Close.
Set Up Coverage Services

Whenever an asset is created in Asset Lifecycle Management, the corresponding included warranty also gets created in
subscription management for managing downstream customer asset transactions. As a subscription specialist, you can
update coverage lines when a customer asset is updated in Asset Lifecycle Management or Installed Base to maintain
asset coverage status in sync.
Subscription Management integrates with Asset Lifecycle Management and simplies xed asset accounting tasks.
Standard asset management tasks, such as reinstating, transferring, spliing, expiring, replacing, and upgrading assets,
can be streamlined with automated business ows.
Here is the summary of the common steps you must perform to set up coverage services:
Setup Steps Details
Set up business units and assign For more information, see Dene Business Units, Assign Business Function, and Assign Ledger
business function, ledger, or legal and Legal Entity in the Subscription Management Setup Checklist chapter.
entity for Subscriptions.

Set up party, account, and account For more information, see Create and Manage Customers in the Subscription Management
sites. Setup Checklist chapter

Set up Order Management For more information, see Dene Order Management Parameters in Subscriptions in the
Parameters. Subscription Management Setup Checklist chapter.

Set up prole option code for time For more information, see Specify Time Unit Mapping Management Setup Checklist chapter.
unit mapping.

Set up the manage subscription time For more information, see Dene Subscription Time Unit Mappings in the Subscription
unit mappings. Management Setup Checklist chapter.

Set up included warranty items and For more information, see Manage Items in the Subscription Management Setup Checklist
coverage items. chapter.
42
Setup Steps Details

Set up pricing strategy and charges. For more information, see Dene Pricing in the Subscription Management Setup Checklist
chapter.

43
44
Implementing Subscription Management Seing Up Subscription 360
6 Seing Up Subscription 360
Enable Subscription 360 in Accounts

The Subscriptions subtab in the sales Accounts details page, also known as Subscription 360, summarizes information
about subscriptions owned by the customer.
Salespeople use the Subscription 360 page to see active subscriptions, draft subscriptions, subscriptions about
to expire, and monthly recurring revenue of active subscriptions. Salespeople can use it to create and manage
subscriptions and review key metrics. The Subscription 360 task ow can be embedded in Accounts, Contacts, or
Households objects based on your business requirements.
To enable the Subscriptions subtab in the Account Details page, do the following:
1. Sign in to the application as a setup user.

2. Ensure that you are working in an active sandbox.
3. Navigate to Application Composer, in the Conguration category.
4. In the navigation tree, expand Standard Objects, expand Account, and click Pages.
5. Ensure that the Simplied Pages tab is selected.
6. In the Details Page Layout section, duplicate the Standard layout.
7. Enter a new layout name, and click Save and Edit.
The Details Layout page appears.

8. Click Add in the Subtabs Region.
The Create Subtab page appears.

9. Select Mashup Content and click Next.
The Select Mashup Content page appears.

10. Click Task Flows.
11. Select Subscriptions and click Insert.
The Task Flows page appears.

12. Enter Subscriptions as the Display Label.
This subtab appears on the Account page.

13. Click the default image and select an appropriate image to change the default image on the subtab.
14. Select Registry ID as the partyNumber.
16. On the Details Layout page, click Done.
17. Ensure that the layout status for your new layout is Active.
18. Test the changes: As a salesperson or sales manager, navigate to Sales > Accounts. Verify that you can see the
Subscriptions subtab on the Edit Account page.
45
Implementing Subscription Management Seing Up Subscription 360
Congure the Subscriptions Role for Salespeople

Salespeople working with accounts may not have access to the Subscriptions page. In such a scenario, even if they
can see Subscription subtab, also known as Subscription 360, on the Accounts page, they can't view, create, or edit
subscriptions.
To enable Subscriptions 360, add the View Subscriptions for an Account functional privilege to the relevant role. After
you have added the functional privilege, add the Subscription Amendment External, Subscription Authoring External,
and Subscription Search and View Access External roles. Assign these to a user.
To enable Subscriptions 360 for salespeople:
1. Sign in to the application as an administrator with the IT Security Manager (ORA_FND_IT_SECURITY_MANAGER_JOB)

role.
2. Click Navigator > Security Console.
3. Search for the role to which you want to grant subscriptions permissions.
4. Go to the Function Security page.
5. Click Add Function Security Policy.
The Add Function Security Policy dialog box appears.

6. Search for the View Subscriptions for an Account privilege.
7. Click Add Privilege to Role.
8. Click Next to go to the Data Security Policy page.
9. Click Create Data Security Policy.
10. On the Create Data Security Policy dialog box, do the following:
a. Enter the policy name, for example, Grant on Subscription.

b. Select Subscription as the Database Resource.
c. Enter start and end dates.
d. Select the appropriate data set.
e. Select all the available actions to grant complete access to subscription.
f. Click Ok.
11. Click Next to the go to the Role Hierarchy page.
12. Click Add Role and add these duty roles:
◦ Subscription Amendment External

◦ Subscription Authoring External
◦ Subscription Search and View Access External
13. Verify the summary information and click Submit and Close.
46
Implementing Subscription Management Revenue Management Integration
7 Revenue Management Integration
Integration Overview
You can use Oracle Revenue Management to automate end-to-end revenue compliance and revenue recognition
processes for your enterprise. You can integrate Oracle Revenue Management with Oracle Subscription Management
to ensure the revenue schedule from a subscription is reected accurately for revenue recognition. The integration also
ensures that the revenue is recognized based on the new ASC 606 and IFRS 15 standards.
The integration between Revenue Management and Subscription Management provides this functionality to:
• Automatically import subscription lines for subscriptions and usage-products.
• Automatically import subscription changes as revisions from Subscription Management, which are treated as
retrospective accounting contract revisions in Revenue Management.
• Import various performance events from Subscription Management to record initial performance events and
satisfaction events in Revenue Management.
• Import subscription billing from Receivables to Revenue Management to clear contract asset balances, record
discounts or premiums, and record initial performance events.
The subscription data must be imported into Revenue Management to create customer contracts and performance
obligations. Revenue is recognized for the performance obligations as and when dierent subscription events occur.
Here are the subscription events that lead to data transfer from Subscription Management to Revenue Management:
• Subscription activation
• Subscription amendment
• Subscription renewal
• Subscription termination
• Usage billing
• Evergreen billing
• Pricing term
The integration supports all scenarios in Subscription Lifecycle Management including subscription ordering with
one-time, recurring and usage charges, evergreen subscriptions, subscription amendment, subscription termination,
subscription renewal, and pricing term. This table explains how this integration process handles these subscription
scenarios in Subscription Lifecycle Management:
Scenarios Impact
Revenue contracts identication Each subscription line is treated as a revenue contract. If the subscription line is part of a
bundle, the complete bundle is treated as a revenue contract. You can modify this action by
changing the Contract Identication Rule.

Performance obligations and Each subscription product charge line is treated as a separate promised detail. By default, each
promised details identication subscription product is treated as an independent performance obligation. You can modify this
action by changing the Performance Obligation Identication Rule.

47
Scenarios Impact
Revenue recognition for one-time, One-time charges are recognized on subscription activation. Recurring charges are recognized
recurring, and usage charges over the subscription duration. Usage charges are recognized as and when usage charges are
billed. Usage charges result in a new revenue contract.

Subscription amendments, Amendments and terminations result in a material modication or termination of the existing
terminations, and renewals impact revenue contract. Renewals and amendments result in a new revenue contract.

Evergreen subscriptions impact on Evergreen Subscriptions result in a new revenue contract for every billing cycle. Subscriptions
revenue with anniversary pricing result in a new revenue contract for every pricing term.

Standalone selling price calculation The charge list price is used as the standalone selling price.

Ad hoc charges and bill adjustments All ad hoc adjustments and bill adjustments result in a material modication of the existing
calculation revenue contract.

Integration Set Up Steps

Here are the steps to enable Revenue Management integration with Subscription Management:
1. In the Setup and Maintenance work area, use the following to navigate to the Manage System Options for
Revenue Management page
◦ Oering: Financial
◦ Functional Area: Revenue Management
◦ Task: Manage System Options for Revenue Management
2. Click Add from the Integration section to add a row in the Source Document Types table.
3. Select a ledger from the Ledger drop-down list.
4. Select Oracle Subscription Management from the Source Document Type drop-down list.
5. Search and select a revenue clearing account from the Appropriate Revenue Clearing drop-down list.
Examples of Subscription Activation Impact on Revenue

Management
When you activate a subscription in Subscription Management, the integration process automatically transfers data in
the following Oracle Revenue Management database tables:
48
Interface Table Description
VRM_ SOURCE_ DOCUMENTS Stores the subscription header information.

VRM_ SOURCE_ DOC_LINES Stores information about the subscription lines, such as the quantity, unit selling price, and line
amount.

VRM_ SOURCE_ DOC_SUB_LINES Stores the information about satisfaction events.

The VRM_SOURCE_DOCUMENTS table stores the basic subscription header information such as document date,
document number, bill-to customer ID, bill-to site ID, subscription start date, subscription number, and so on.
This example describes how the subscription data is processed by the Revenue Management and inserted into:
• VRM_SOURCE_DOC_LINES
• VRM_SOURCE_DOC_SUB_LINES
Let's assume that a customer has purchased a Blast Internet Connection subscription with the following details:
Subscription Fees Blast Internet Basic Blast Internet Premium
Activation Fee (One-time) $80 $80

Internet Fee (Recurring) $50 $60

Consumption Fee (Usage) Free Allowance: 100GB Free Allowance: 100GB

Usage fee after 100 GB: $1 for every 2GB Usage fee after 100 GB: $1 for every 2GB

• The extra consumption fee is charged when the customer exceeds the data consumption limit of 100 GB per
month. When internet data consumption exceeds the limit, the customer is charged with $1 for every 2 GB of
extra usage.
• At any time, customers can upgrade their subscription and opt for the premium package that costs $60 per
month.
• The customer has purchased the subscription for 12 months.
Scenario 1: Basic Subscription Activation

This scenario covers the impact of activating Blast Internet Connection subscription on the Revenue Management
database tables where the customer has only opted for the basic internet plan of $50 per month for one year.
Impact on VRM_SOURCE_DOC_LINES
Here's the table that displays the values inserted in the VRM_SOURCE_DOC_LINES database table:
49
Table Aributes Doc Line 1 Doc Line 2
Source Line Source Line 1 Source Line 2

Item Blast Internet Basic Blast Internet Basic

Extensible Aribute 1 Internet (Recurring) Activation Fee(One-time)

Extensible Aribute 2 Monthly One-time

UOM Year Year

Quantity 1 1

Unit Selling Price 600 80

Line Amount 600 80

List Price 600 80

Version Number 1 1

Version Flag Null Null

Plan Start Date 01-Jan-2020

Plan End Date 31-Dec-2020

Satisfaction Measurement Model ORA_ MEASURE_ PERIOD_ SATISFIED ORA_ MEASURE_ QUANTITY_ SATISFIED

Subscription activation results in the addition of two rows in this table:
• Doc Line 1 stores the values associated with the recurring monthly internet fees of $50. Therefore, the unit
selling price becomes $600 ($50 for 12 months).
• Doc Line 2 stores the values associated with one-time activation fees of $80.
Impact on VRM_SOURCE_DOC_SUB_LINES
Values in this table are only populated for the document lines that are completely satised. Here's the table that displays
the values inserted in the VRM_SOURCE_DOC_SUB_LINES database table:
50
Table Aributes Doc Sub Line 1
Source Line 2

Sub Line Type Code ORA_ SATIS_ EVENT_ SMM_QUANTITY

Satisfaction Measurement Date 1-Jan-2020

Satised Quantity 1

At the time of subscription activation, the only charge completely satised was the activation fee. Because charges
related to Doc Line 2 are paid immediately at the time of subscription activation, only values associated with the
activation fee are populated in this table.
Once the charges associated with the monthly fees are completely satised, new rows for the monthly internet fees of
$50 are added to this table at the end of every month.
Scenario 2: Subscription with Usage fees

This scenario covers the situation where an extra consumption fee is applicable because the customer has exceeded his
internet data limit of 100 GB per month by:
• 20 GB in January
• 30 GB in February
Here's the table that displays the values inserted in the VRM_SOURCE_DOC_LINES database table when usage charges
are applied on the subscription:
Source Line Source Line 3 Source Line 4

Item Blast Internet Basic Blast Internet Basic

Extensible Aribute 1 Internet (Recurring) Internet (Recurring)

UOM Year Year

Quantity 120 130

Unit Selling Price 10/120 15/130

Line Amount 10 15

51
List Price 10/120 15/130

Plan Start Date 01-Jan-2020 01-Feb-2020

Plan End Date 31-Jan-2020 28-Feb-2020

Satisfaction Measurement Model ORA_ MEASURE_ PERIOD_ SATISFIED ORA_ MEASURE_ PERIOD_ SATISFIED

Note: New rows in the VRM_SOURCE_DOC_LINES table are not inserted at the time of subscription activation.
In the case of usage charges, a new accounting contract is created for every usage line. The customer is
charged only when the usage fee becomes applicable.
The consumption fees result in the addition of two rows:
• Doc Line 3 stores the values associated with the usage fees associated with January. Line Amount is $10 as the
customer has used 20 GB extra data, and every 2 GB data costs $1.
• Doc Line 4 stores the values associated with the usage fees associated with February. Line Amount is $15 as the
customer has used 30 GB extra data.
Exceeding the usage limit doesn't impact the VRM_SOURCE_DOC_SUB_LINES values. The
VRM_SOURCE_DOC_SUB_LINES table displays the same values as described in Scenario 1.
Scenario 3: Upgraded Subscription

This scenario covers the situation where a customer decides to upgrade his subscription to premium, which costs $60
per month, for six months from 01-July-2020 to 31-Dec-2020.
Here's the table that displays the values inserted in the VRM_SOURCE_DOC_LINES database table when the customer
upgrades the subscription:
Table Aributes Doc Line 1 Doc Line 2 Doc Line 3 Doc Line 4
Source Line Source Line 1 Source Line 2 Source Line 3 Source Line 1

Item Blast Internet Basic Blast Internet Basic Blast Internet Premium Blast Internet Basic

Extensible Aribute 1 Internet (Recurring) Activation Fee (One- Internet (Recurring) Internet (Recurring)
time)

Extensible Aribute 2 Monthly One-time Monthly Monthly

UOM Year Year Year Year

52
Table Aributes Doc Line 1 Doc Line 2 Doc Line 3 Doc Line 4
Quantity 1 1 1 1

Unit Selling Price 600 80 360 600

Line Amount 600 80 360 300

List Price 600 80 360 600

Version Number 1 1 1 2

Version Flag Null Null Null Y

Plan Start Date 01-Jan-2020 01-Jul-2020 01-Jan-2020

Plan End Date 31-Dec-2020 31-Dec-2020 30-Jun-2020

Satisfaction ORA_ MEASURE_ ORA_ MEASURE_ ORA_ MEASURE_ ORA_ MEASURE_

Measurement Model PERIOD_ SATISFIED QUANTITY_ SATISFIED PERIOD_ SATISFIED PERIOD_ SATISFIED

When a subscription is upgraded, two new rows are inserted in this Revenue Management table:
• Doc Line 3 stores the values associated with the recurring premium monthly internet fees of $60. Therefore,
the unit selling price becomes $360 ($60 for 6 months).
• Doc Line 4 in this table is created as the new version of Doc Line 1 created at the time of the subscription
activation. Doc Line 4 stores the values associated with the monthly internet fees paid until 30 June 2020.
Therefore, the unit selling price becomes $300 ($50 *6 months). Also, as this is the revision of the existing Doc
Line 1, the Version Number becomes 2 and the Version Flag becomes Y.
Upgrading the subscription doesn't impact the VRM_SOURCE_DOC_SUB_LINES values. The

VRM_SOURCE_DOC_SUB_LINES table displays the same values as described in Scenario 1.
Related Topics
• How Revenue Basis Import Data Is Processed
• How Revenue Recognition Is Processed
53
54
Oracle Subscription Management Cloud Glossary
Glossary
business function
A business process or an activity that can be performed by people working within a business unit. Describes how a
business unit is used.
chart of accounts
The account structure your organization uses to record transactions and maintain account balances.
division
A business-oriented subdivision within an enterprise. Each division is organized to deliver products and services or
address different markets.
legal entity
An entity identified and given rights and responsibilities by commercial law through the registration with country's
appropriate authority.
primary ledger
Main record-keeping ledger.
reference data set

Contains reference data that can be shared across a number of business units or other determinant types. A set
supports common administration of that reference data.
resource
People designated as able to be assigned to work objects, for example, service agents, sales managers, or partner
contacts. A sales manager and partner contact can be assigned to work on a lead or opportunity. A service agent can be
assigned to a service request.
55
Oracle Subscription Management Cloud Glossary
56

Implementing Subscription Management Full Docs

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Implementing Subscription Management Full Docs

Hochgeladen von

Copyright:

Verfügbare Formate

Oracle Subscription

Author: Abhay Singh, Debjit Nag

1 About This Guide 1

3 Subscription Management Setup Checklist 7

4 Common Application Setup Concepts 23

6 Seing Up Subscription 360 45

7 Revenue Management Integration 47

Using Oracle Applications

• Training: Take courses on Oracle Cloud from Oracle University.

> Greater than symbol separates elements in a navigation path.

Access to Oracle Support

Comments and Suggestions

1 About This Guide

Audience and Scope

Start Implementing Subscriptions

Functional Area Description

Subscriptions Use this functional area to set up subscriptions.

Where You Perform Subscriptions Setup Tasks

Setup and Maintenance Setups

• Functional Area: Subscriptions

Subscription Management Work Area Setups

Summary of the Subscriptions Setup Steps

Setup Step Where You Find More Information

Setup Step Where You Find More Information

Dene pricing See the Dene Pricing for Subscriptions topic.

Dene Customer Billing Conguration

Subscription Copy Map See the Subscription Copy Map topic.

Dene Subscription Cancellation See the Dene Subscription Cancellation Reasons.

Manage subscription rules See the Conguring Subscriptions chapter.

Entitlements Management See the Conguring Subscriptions chapter.

3 Subscription Management Setup Checklist

Create a Subscriptions Implementation Project

Dene Legal Entities for Subscriptions

Dene Business Units and Assign Business Function,

Create and Manage Customers

1. Navigate to the Setup and Maintenance work area.

5. Click Save and Close.

Dene Party Roles and Contact Roles for Subscriptions

Set Up User Statuses and User Transitions for

To dene user and status transitions:

Dene Unit of Measure

4. Click Save and Close.

Dene Subscription Time Unit Mappings

Dene Order Management Parameters

To dene Order Management Parameters:

Create Included Warranty Items

Create Coverage Items

Create Subscription Items

5. Enter the recurring price details of the item.

Setup Where you nd more information

Add items to price lists and add one-

Dene Customer Billing Conguration for Subscriptions

◦ Dene payment terms in the Manage Receivables Payment Terms page.

This graphic describes the usage acquisition and rating.

Dene AutoInvoice Line Ordering Rules

Dene AutoInvoice Grouping Rules

Dene Receivables Payment Terms

Dene AutoAccounting Rules

Subscription Copy Map

3. Select Copy Maps, in the Advanced Setup section.

Map Group Select Copy Subscription

From Select SubscriptionManagementAM

To Select the new view object that you're copying to.