Sie sind auf Seite 1von 76
SAP Best Practices for SAP Hybris Billing V8.1610

SAP Best Practices for SAP Hybris Billing

V8.1610

SAP Best Practices for SAP Hybris Billing V8.1610 Customer

Customer

SAP Best Practices for SAP Hybris Billing

V8.1610

SAP Best Practices for SAP Hybris Billing V8.1610 Customer

Customer

Contents

Overview

Scope

Financial Customer Care - Financial Inquiries

Financial Customer Care - Bill Display and Dispute Management

Financial Customer Care - Actions on Prepaid Accounts

Financial Customer Care - Collections in CRM Interaction Center

Customer and Contract Creation for Postpaid Services

Use Service, Create Invoices, and Pay for Postpaid Service

Contract Change from Prepaid to Postpaid Product

Customer and Contract Creation for Prepaid Services

Use Service and Manage Balance and Financials for Prepaid Service

Termination of a Prepaid Service and Closing of the Prepaid Account

Refill Prepaid Account by "One Time Permission"

Refill Prepaid Account via Voucher Activation

Daily and Monthly Closing

Consolidated Statements for Banking Postpaid Services

B2B Master Agreement with Counter Sharing

Revenue Sharing and Partner Settlement

Data Storage for Consumption Items

Preliminary Invoice

Item Corrections in Convergent Invoicing

Bulk Ordering and Mass Cancellation of Provider Contracts

Convergent Mediation - Batch Scenario

Customer, Contract Creation and Refill for Allowances

Consume Allowances and Recognize the Revenue

Delivery Approach

Software Products and Landscape

SAP Service and Support Overview

At-a-Glance: SAP Best Practices for SAP Hybris Billing

At-a-Glance: SAP Best Practices for SAP Hybris Billing Rapidly setup the baseline for your next-generation billing

Rapidly setup the baseline for your next-generation billing platform

Business Requirement

What is my pain?

Inability of marketing and sales to adapt quickly to support sophisticated pricing models and multifaceted revenue relationships

No clear visibility for customer service of the complete customer financial relationship and an inability to make decisions to increase loyalty

Lack of integrated financial systems for finance and billing resulting in longer DSO

and reduced customer profitability

Inability of partner management to offer compelling revenue share terms to partners to attract them and increase the value of an offering

Solution

Solution description

The SAP Best Practices for SAP Hybris Billing enables you to define innovative

tariffs and launch new business models quickly. With the Best Practices, you can

set up a baseline solution for your specific implementation more quickly than a traditional approach allows.

What are my needs?

These Best Practices help you to quickly set up the baseline configuration for the SAP Hybris Billing solution, which after completed implementation, allows you to:

Create and launch market-beating offers by marketing and sales faster than the competition

Enjoy a 360-degree view of the customer relationship with full detail for customer service, leading to quicker service and more satisfied customers

Gain comprehensive control for finance and billing of the entire order capture and billing chain with automated operation

Calculate and report flexible revenue share terms for partner management, in a timely and accurate manner

Learn more
Learn more
Agenda Overview Scope Delivery Approach Software Products and Landscape SAP Service and Support Overview

Agenda

Overview

Scope

Delivery Approach Software Products and Landscape SAP Service and Support Overview

Agenda Overview Scope Delivery Approach Software Products and Landscape SAP Service and Support Overview

Rapidly setup the baseline for your next-generation billing platform

Business challenges

Inability of marketing and sales to adapt quickly to

support sophisticated pricing models and multifaceted revenue relationships

No clear visibility for customer service of the complete customer financial relationship and an inability to make decisions to increase loyalty

Lack of integrated financial systems for finance and billing resulting in longer days sales outstanding (DSO) and reduced customer profitability

Inability of partner management to offer compelling revenue share terms to partners to attract them and increase the value of an offering

There is a solution

The SAP Best Practices for SAP Hybris Billing enable

you to define innovative tariffs and launch new business models quickly. With the Best Practices, you can set up a baseline solution for your specific implementation more quickly than a traditional approach allows.

General Solution Overview

SOFTWARE COMPONENTS
SOFTWARE
COMPONENTS

SAP CRM

SAP Convergent Mediation by DigitalRoute

Convergent

Mediation

Convergent

Policy

SAP

Convergent

Charging

SAP

Convergent

Pricing

Simulation

SAP Flexible

Solution

Billing

SAP ERP Business Suite or S/4HANA OP

Convergent

Invoicing

(CI)

Contract Accounts Receivable and Payable (FI-CA)

SAP

CRM

Please note: Not every feature of the solution is covered by the Best Practices
Please note: Not every feature of the solution is covered by the Best Practices

Benefits for you

Business benefits

This solution package helps you to quickly set up the

baseline configuration for the SAP Best Practices for SAP Hybris Billing, which after completed implementation, allows you to:

Create and launch market-beating offers by marketing and sales faster than the competition

Enjoy a 360-degree view of the customer relationship

with full detail for customer service, leading to quicker service and more satisfied customers

Gain comprehensive control for finance and billing of the entire order capture and billing chain with automated operation

Calculate and report flexible revenue share terms for

partner management, in a timely and accurate manner

Measurable success

Reduced customer churn

Less time to market for new pricing and revenue share offers

Increased average revenue per user

Increased revenue share for new products

Less days sales outstanding (DSO)

Innovation adoption made simple!

with SAP Best Practices™

• Get a jump-start for your implementations with SAP Best Practices™ Fast time to value
• Get a jump-start for your implementations with SAP
Best Practices™
Fast time to value
• Deploy SAP innovations fast, simple and flexible
value • Deploy SAP innovations fast, simple and flexible © 2017 SAP SE or an SAP
value • Deploy SAP innovations fast, simple and flexible © 2017 SAP SE or an SAP

Innovation adoption made simple!

with SAP Best Practices

Innovation adoption at scale, your way

SAP Best Practices

preconfigured cloud and on-premise solutions

across SAP’s solution portfolio

based on proven business best practices

portfolio • based on proven business best practices User Experience and Mobility Business Applications
User Experience and Mobility Business Applications Analytics Enterprise Industry Lines of Resource Solutions
User Experience and Mobility
Business Applications
Analytics
Enterprise
Industry
Lines of
Resource
Solutions
Business
Planning
Database & Technology
Cloud

simple to deploy with a proven methodology

at predictable time and efforts

delivered by SAP and partners

Agenda Overview Scope Delivery Approach Software Products and Landscape SAP Service and Support Overview

Agenda

Overview

Scope

Delivery Approach Software Products and Landscape SAP Service and Support Overview

Agenda Overview Scope Delivery Approach Software Products and Landscape SAP Service and Support Overview

Scope Summary

The process configuration provided is mostly industry agnostic. Product master data examples are tailored for specific industries listed below.

Postpaid End-to-End Processes

F80

Customer and contract creation for postpaid services

F81

Use service, create invoices, and pay for postpaid service

U97

Convergent mediation batch scenario

U98

Customer, contract creation, and refill for allowances

U99

Consume allowances and recognize the revenue

F88

Daily and monthly closing

Examples for Telecom, High Tech, Postal

Financial Customer Care

Financial Customer Care

F77

Financial customer care financial inquiries

F78

Financial customer care bill display and dispute management

F79

Financial customer care collections in CRM

interaction center

U95

Financial customer care actions on prepaid accounts

Examples for Telecom, High Tech, Postal

Prepaid End-to-End Processes

Prepaid End-to-End Processes

F83

Customer and contract creation for prepaid services

F84

Use service and manage balance and financials for prepaid service

F86

Refill prepaid account via voucher activation

F87

Refill prepaid account by "one-time permission"

F85

Termination of a prepaid service and closing of the prepaid account

F82

Contract change from prepaid to postpaid product

F88

Daily and monthly closing

Examples for Telecom, High Tech

B2B Processes

U90

B2B master agreement with counter sharing

U96

Bulk ordering and mass cancellation of provider contracts

U91

Revenue sharing and partner settlement

U92

Data storage for consumption items

U93

Preliminary invoice

U94

Item corrections in convergent invoicing

Examples for Telecom, High Tech, Postal

Note: Number denotes the best-practice scenario number.

Banking Industry

F89

Consolidated statements for banking postpaid services

Example for Banking

statements for banking postpaid services Example for Banking © 2015 SAP SE or an SAP affiliate

Financial Customer Care - Financial Inquiries

Scope and benefits

Financial inquiries and initiation of follow-up processes support the work of a call center agent by providing an accurate view of the A/R information of a customer in SAP CRM. Besides being able to see data like account balance and account history, the call center agent can initiate processes. Examples are the creation of a credit memo or the creation of an installment plan in A/R within SAP CRM. Besides this process, additional functions are available as

part of the solution, but are not explicitly described in

this item.

Increase customer satisfaction due to ability of call center agent to process all types of A/R related inquiries Increase call center efficiency due to fewer handovers and less demand for software system changes

Use single data source for both call center agent and back-office employees

Financial Customer Care - Financial Inquiries

In the system

Key functionality

Identifying customer and business agreement

Accessing account balance overview

Getting details of account history

Creating credit memos

Creating installment plans

Industry focus: Telecommunications, High Tech and Postal Services

focus: Telecommunications, High Tech and Postal Services Account overview © 2017 SAP SE or an SAP

Account overview

Financial Customer Care - Bill Display and Dispute Management

Scope and benefits

Access to customer bills supports the processing of

customer bill disputes on all detail levels (Bill, Bill Line Item(s), Bill Detail Records). The call center agent can create dispute cases on the different levels, these cases are replicated to SAP S/4HANA and linked to the respective objects. The status of a dispute is tracked through status settings and can in case of approval trigger the creation of an adjustment request. The adjustment request then initiates the creation of a credit memo.

Integrate processes with synchronized data across

both SAP CRM and SAP S/4HANA Increase call center efficiency due to fewer handovers and less demand for software system changes

Financial Customer Care - Bill Display and Dispute Management

In the system

Key functionality

Identification of customer and business agreement

Access to customer bills and selection of

the affected bill details

Creation of a dispute case and distribution of the case information to SAP

S/4HANA

Creation of an adjustment according to

the case status

Automatic creation of a credit memo in SAP S/4HANA after final approval and releasing of the adjustment

Industry focus: Telecommunications, High

Tech and Postal Services

focus: Telecommunications, High Tech and Postal Services Dispute details with credit memo reference © 2017 SAP

Dispute details with credit memo reference

Financial Customer Care - Actions on Prepaid Accounts

Scope and benefits

Multiple processes and actions on the customers’ prepaid credit are made available in the CRM Interaction Center

Integrated process with synchronized data across

both SAP CRM and SAP S/4HANA

Financial Customer Care - Actions on Prepaid Accounts

In the system

Key functionality

Identification of customer and prepaid account

Refilling of prepaid account

Refunding prepaid account credit

Transferring balances

Industry focus: Telecommunications and

High Tech

balances Industry focus: Telecommunications and High Tech Refll prepaid account in CRM Interaction Center © 2017

Refll prepaid account in CRM Interaction Center

Financial Customer Care - Collections in CRM Interaction Center

Scope and benefits

As a preparation step, a dunning run creating dunning activities for the CRM collection process has to be executed in SAP S/4HANA. The work items created in dunning are assigned to a collection team. The collection process uses the work items to start the interactive part with the customer. Here, the main

source of information is the collection fact sheet

(providing the necessary information of the customer

like dunning history, promises to pay, installment plans, account balance, and even drill-down to the detailed documents). After negotiating with the customer, a "promise to pay" is created (which is one follow-up step

in outbound collections) and the collections work item is

closed. Assuming the customer pays as he promised, the respective incoming payment is processed in SAP S/4HANA. The promises to pay undergo a regular

valuation run to check if the promise has been fulfilled and the "promise to pay" can be closed. The status can

then be checked in SAP CRM.

Integrated process with synchronized data across both SAP CRM and SAP S/4HANA

Improved collection efficiency due to integrated collection workflow with all relevant options available for the call center agent in negotiation with the customer

Financial Customer Care - Collections in CRM Interaction Center

In the system

Key functionality

Dunning and creating collection work items in SAP S/4HANA

Processing of work items in the CRM

Interaction Center

Displaying the collection fact sheet with all collection relevant information

Creating a "promise-to-pay" as one possible follow-up action

Creating and processing of incoming

payments in SAP S/4HANA

Executing the "promise-to-pay" valuation and closing the promise to pay

Industry focus: Telecommunications, High Tech and Postal Services

focus: Telecommunications, High Tech and Postal Services Dispute details with credit memo reference © 2017 SAP

Dispute details with credit memo reference

Customer and Contract Creation for Postpaid Services

Scope and benefits

A new customer wants to subscribe to a postpaid service of the company. He calls the company’s call center and is routed to a call center agent. The agent

recognizes that the customer is new, so a new customer master record is created capturing all relevant customer data like name, address, bank, or credit card information. Assuming that the customer has already decided which postpaid service he wants to

use, the call center agent creates an order for the

customer. In this order, the agent defines which service (product) the customer wants to subscribe to. Depending on the product, additional configuration

options are available for the customer and need to be selected by the call center agent. After the selection is

completed, the order is submitted to the fulfillment

system and, based on the selected product, a customer contract is created. While this happens, the relevant master and transaction data of the contract is distributed to the relevant backend systems.

Simplified creation and change of customer master data in a Web UI

Captured customer orders in the CRM Interaction Center

using configurable predefined postpaid products

Automated creation of customer contracts for the services the customer has subscribed to

Integrated and flexible distribution of master and transaction data to SAP Hybris Billing, charging, SAP Hybris Billing, invoicing, and SAP Hybris Billing, customer financials

Customer and Contract Creation for Postpaid Services

In the system

Key functionality

Create new customer

Create new order for existing postpaid product

Submit order and create contract

Industry focus: Telecommunications, High Tech and Postal Services

focus: Telecommunications, High Tech and Postal Services Order creation in CRM Interaction Center © 2017 SAP

Order creation in CRM Interaction Center

Use Service, Create Invoices, and Pay for Postpaid Service

Scope and benefits

Consumption of a postpaid service by the customer leads to the creation of consumption data records which are provided to the SAP Hybris Billing, charging application to do flexible, rule-based rating and charging for this consumption. After passing SAP Hybris Billing, charging, the rated events are sent to SAP Hybris Billing, invoicing to create the final invoice and to do the A/R posting. SAP Hybris Billing, customer financials provides multiple

functionalities for A/R processing. In this particular

case, the open item is not paid by the customer and becomes overdue and thus a dunning letter is sent to the customer, who then pays his/her outstanding debt.

Flexible charging of the created usage (using the predefined product definition and charge plans)

Billing and invoicing of the charged items according to

configurable rules in SAP Hybris Billing, invoicing

Automatic integration with SAP Hybris Billing, customer financials

Use Service, Create Invoices, and Pay for Postpaid Service

In the system

Key functionality

The customer starts using the service and usage activity is simulated and provided to SAP Hybris Billing, charging.

At the end of the bill cycle, an invoice is generated, including all one-off charges. With this, all counters (for example, for free SMS) are reset.

The customer receives a bill which is posted to the A/R and transferred to the general ledger.

The customer has selected "Bank Transfer" as payment option, but does not pay his bill in time.

The outstanding debt enters the dunning procedure. After the first dunning step, the customer pays.

Industry focus: Telecommunications, High Tech and Postal Services

Customer and Contract Creation for Prepaid Services

Scope and benefits

A new customer wants to subscribe to a prepaid service of the company. He calls the company’s call center and is routed to a call center agent. The agent recognizes

that the customer is new. So, a new customer master

record is created capturing all relevant customer data like name and address. Assuming that the customer has already decided which prepaid service he wants to

use, the call center agent creates an order for the customer. In this order, the agent defines which service

(product) the customer wants to subscribe to.

Depending on the product, additional configuration options are available for the customer and need to be selected by the call center agent. After the selection is completed, the order is submitted to the fulfillment systems and, based on the selected product, a

customer contract is created. While this happens, the

relevant master and transaction data of the contract is distributed to the relevant backend systems.

Simple creation and change of customer master data in a Web UI

Capturing customer orders in the CRM Interaction

Center using configurable predefined prepaid products

Automated creation of customer contracts for the services the customer has subscribed to

Integrated and flexible distribution of master and transaction data to SAP Hybris Billing, charging, SAP Hybris Billing, invoicing, and SAP Hybris Billing, customer financials

Customer and Contract Creation for Prepaid Services

In the system

Key functionality

Create new customer

Create new order for existing prepaid product

Submit order and create contract

Industry focus: Telecommunications and High Tech

contract Industry focus: Telecommunications and High Tech Order creation in CRM Interaction Center © 2017 SAP

Order creation in CRM Interaction Center

Use Service and Manage Balance and Financials for Prepaid

Service - Scope and benefits

Consumption of a prepaid service by the customer leads to the creation of consumption data records which are provided to the SAP Hybris Billing, charging application to do the rating and charging for this consumption. In addition, additional prepaid- related processes (like reducing the prepaid balance) are executed. SAP Hybris Billing, charging provides flexible, rule-based charging. After passing SAP Hybris Billing, charging, the consumption is sent to

SAP Hybris Billing, invoicing and SAP Hybris Billing,

customer financials for the required financial and postings.

Flexible charging of the created usage (using the predefined product definition and charge plans)

Automatic integration to SAP Hybris Billing, invoicing

and SAP Hybris Billing, customer financials

Use Service and Manage Balance and Financials for Prepaid

Service - In the system

Key functionality

The customer starts using the service and usage activity is simulated and provided to SAP Hybris Billing,

charging

SAP Hybris Billing, charging deducts the calculated charges from the available prepaid balance

SAP Hybris Billing, charging sends the details on the usage to SAP Hybris Billing, invoicing and SAP Hybris Billing, customer financials for the required financial postings

Industry focus: Telecommunications and High Tech

Termination of a Prepaid Service and Closing of the Prepaid

Account - Scope and benefits

Termination of a prepaid service and closing of the prepaid account supports the automatic processing of prepaid accounts which are not used for a specified period of time. The application recognizes this fact and closes the prepaid accounts automatically. The closing of expired prepaid

accounts is realized in SAP Hybris Billing, charging. Closed prepaid accounts are no longer available for use. Closed accounts may or may not have a zero

balance that needs to be analyzed, adjusted, and

written off before posting to the company's balance sheet.

Automatic closing of prepaid accounts if they are not used for a specified period of time

Rule-based execution of the required follow-up

process in contract accounts receivable and payable

Termination of a Prepaid Service and Closing of the Prepaid

Account - In the system

Key functionality

Automatic closing of prepaid accounts if they are not used for a specified period of time

Manual clarification of how to handle the outstanding balance of the prepaid account

Writing off the outstanding balance

Industry focus: Telecommunications and High Tech

Refill Prepaid Account by "One Time Permission"

Scope and benefits

Refill prepaid account that has "one time permission" by capturing payment card data and the amount which should be credited. In the SAP Best Practices for SAP Hybris Billing this specific refill process starts when SAP S/4HANA informs SAP Hybris Billing, charging that a prepaid account is to be

refilled with a certain credit. This trigger initiates all required follow-up processes in SAP Hybris Billing, invoicing and SAP Hybris Billing, customer

financials to record the correct amounts to the

general ledger.

Integrated refill process for a refill with "one time permission"

Transparent audit trail of refill amounts across the

different parts of the solution

Refill Prepaid Account by "One Time Permission"

In the system

Key functionality

Verify or create the necessary payment card data for the customer

Increase available credit in SAP Hybris Billing, charging

Transfer detail information for processing to SAP Hybris Billing, invoicing and SAP Hybris Billing, customer financials

Process the detail information and create the appropriate general ledger posting

Industry focus: Telecommunications and High Tech

Refill Prepaid Account via Voucher Activation

Scope and benefits

Refill prepaid account via voucher activation supports the use of a voucher to refill the balance of a prepaid account. Such activation is often done with the help of voucher management systems which help ensure that each voucher is only used once. In the SAP Best Practices for SAP Hybris Billing, this specific refill process starts when the third-party voucher management system (which is simulated) informs SAP Hybris Billing, charging that a prepaid

account is to be refilled with a certain credit. This

trigger initiates all required follow-up processes in SAP Hybris Billing, invoicing and SAP Hybris Billing, customer financials to record the correct amounts to the general ledger.

Integrated refill process for voucher-based refill (and others)

Transparent audit trail of refill amounts across the

different parts of the solution

Refill Prepaid Account via Voucher Activation

In the system

Key functionality

Increase available credit in SAP Hybris Billing, charging

Transfer detail information for processing to SAP Hybris Billing, invoicing and SAP Hybris Billing, customer financials

Process the detail information and create the appropriate general ledger posting

Industry focus: Telecommunications and High Tech

Daily and Monthly Closing

Scope and benefits

Daily and monthly closing processes are periodic tasks in SAP S/4HANA that need to be executed for the A/R part of the solution. The closing operations help ensure the accurate data transfer between the A/R solution and FI-GL. For monthly closing, additional process steps, such as the closing of the posting periods, are required.

Closing helps ensure consistency between A/R and G/L

Reconciliation helps guarantee audit-proof data

Daily and Monthly Closing

In the system

Key functionality

Closing of reconciliation keys

Closing of posting period

Executing transfer to G/L

Executing reconciliation reporting

Industry focus: Telecommunications, High Tech, Postal Services and Banking

Consolidated Statements for Banking Postpaid Services

Scope and benefits

Consolidated statement creation supports the creation of a single collective invoice in A/R through the use of SAP Hybris Billing, invoicing as a collector for the single external bills and statements of a customer from multiple applications and multiple accounts. SAP Hybris Billing, invoicing uses collective contract accounts to combine the data in A/R and creates a collective invoice as a combination of the provided single invoice data.

Look across lines of business to consolidate billing information for multiple customer accounts

Automate process for consolidating billing documents

and statements from multiple source applications

Maintain an audit trail from source transactions to generated bill/statements

Consolidate receivables in a single source of truth

Consolidated Statements for Banking Postpaid Services

In the system

Key functionality

Upload billable items from external application (through file interface)

Execute billing for the individual accounts

Execute invoicing for the individual accounts

Execute consolidated invoicing for the collective accounts

Create and print the consolidated statement

Industry focus: Banking

and print the consolidated statement Industry focus: Banking Example of a consolidated Bill © 2017 SAP

Example of a consolidated Bill

B2B Master Agreement with Counter Sharing

Scope and benefits

Master agreements and sharing orders/contracts in the SAP Best Practices for SAP Hybris Billing. A master agreement is a contract between a provider and a customer (usually a large company) in which common terms for future contracts are defined. The common terms can cover aspects of ordering (who

can order which products and under which conditions), invoice creation (layout, recipient, payer, additional invoicing lists…) and discounting (which

services are discounted and who benefits). Master

agreements can be combined with sharing contracts, which allow counter sharing - also known as enterprise sharing or sharing contracts -which is a concept where different customer contracts signed

with the same provider can share similar counters.

Ability to handle complex frame contracts for business customers

Cover the full process chain of B2B from contract to

invoice

Allowing the sharing of counters across different contracts of a customer

B2B Master Agreement with Counter Sharing

In the system

Key functionality

Creating a master agreement

Creating sharing order and a sharing contract

Creating provider order/contract with reference to a master agreement

Activating recurring charges

Simulating usage

Executing billing and invoicing

Creating invoice list

Industry focus: Telecommunications,

High Tech and Postal Services

focus: Telecommunications, High Tech and Postal Services Creation of a master agreement © 2017 SAP SE

Creation of a master agreement

Revenue Sharing and Partner Settlement

Scope and benefits

Revenue sharing and partner settlement allows the creation of sophisticated revenue sharing models in the SAP Best Practices for SAP Hybris Billing. Through specific master data, both the potential

partners, the revenue splitting and the settlement rules are defined. The solution calculates the partner portions of the revenue on item level in SAP Hybris Billing, charging and settles the partner revenue in SAP Hybris Billing, customer

financials for payout.

Support of multi-sided business models

Flexible definition of revenue sharing rules and partners

Flexible definition of settlement rules

Revenue Sharing and Partner Settlement

In the system

Key functionality

Creation of partner master data and partner agreement

Use of service for which revenue sharing is defined

Creation of customer invoice

Settlement of partner revenue

Industry focus: Telecommunications and High Tech

Data Storage for Consumption Items

Scope and benefits

Data storage for consumption items allows to store the source information records coming from the mediation systems or other event source systems in SAP Hybris Billing, invoicing. This allowing improved handling for rerating and other new processes in SAP Hybris Billing, invoicing like e.g. scaled prices and manual corrections.

Ability to run rerating for an technically unlimited number of days

Allow the application of scaled prices

Data Storage for Consumption Items

In the system

Key functionality

Generation of unrated consumption items

Execution of rating and invoice creation

Running a re-rating process

Creating a provider order/contract for deferred rating (Telco and High Tech only)

Execution of the deferred rating process (Telco and High Tech only)

Industry focus: Telecommunications, High Tech and Postal Services

Preliminary Invoice

Scope and benefits

Creation of a preliminary invoice in SAP Hybris Billing, invoicing

Ability to create a invoice document before actual posting

Improvement of customer relationship by having the

invoice checked by a customer before it is actually

posted to A/R

Preliminary Invoice

In the system

Key functionality

Creation of preliminary invoice

Acceptance of preliminary invoice

Reversing of preliminary invoice

Industry focus: Telecommunications, High Tech and Postal Services

Item Corrections in Convergent Invoicing

Scope and benefits

Manual creation, changing and excepting of consumption and billable items in SAP Hybris Billing, invoicing allows to handle specific cases mainly for business customers, which cannot be handled (with acceptable efforts) by the system(s) delivering the data to SAP Hybris Billing, invoicing or to handle cases which are not covered by any source system at all.

Simplification of invoice correction (mainly for business customers)

Ability to integrate data (on low volume) for sources,

which are not technically integrated

Item Corrections in Convergent Invoicing

In the system

Key functionality

Manual capturing of consumption items

Manual creation of billable items

Changing and excepting of unrated consumption items

Changing and excepting of unbilled billable items

Industry focus: Telecommunications, High Tech and Postal Services

Bulk Ordering and Mass Cancellation of Provider Contracts

Scope and benefits

Bulk ordering and mass cancellation of provider contracts allows the creation of a number of provider contract based on externally provided data (e.g. a file). The mass creation process is in this case linked to a master agreement for which the contracts are either created or cancelled.

Improved support of B2B processes

Reduction of data entry efforts

Automated and consistent handling

Bulk Ordering and Mass Cancellation of Provider Contracts

In the system

Key functionality

Creation of provider orders in a mass run

Cancellation of provider orders in a mass run

Industry focus: Telecommunications and High Tech

a mass run Industry focus: Telecommunications and High Tech Create mass run © 2017 SAP SE

Create mass run

Convergent Mediation - Batch Scenario

Scope and benefits

The batch scenario for SAP Hybris Billing, mediation by DigitalRoute provides a CSV-file based upload capability for usage data into SAP Hybris Billing, charging. The example is realized as a very

simple offline mediation scenario, illustrating the out- of-the-box integration between SAP Hybris Billing, mediation by DigitalRoute and SAP Hybris Billing, charging. In the context of the package supported processes the batch scenario is integrated

with both "Use service, create invoices, and pay for

postpaid Service" and "Use service and manage balance and financials for prepaid service".

Out-of-the-box integration of SAP Hybris Billing, mediation by DigitalRoute and SAP Hybris Billing, charging

Convergent Mediation - Batch Scenario

In the system

Key functionality

Connecting to SAP Convergent Mediation by DigitalRoute 3.1

Starting the batch collection workflow

Running the CDR submission workflow

Industry focus: Telecommunications

CDR submission workflow Industry focus: Telecommunications CDR submission workflow © 2017 SAP SE or an SAP

CDR submission workflow

Customer, Contract Creation and Refill for Allowances

Scope and benefits

A new customer wants to subscribe to a service of the

company. He contacts the company (e.g. through a letter).If the customer is new to the company a new customer master record is created. Assuming that the customer has

already decided which service he wants to use, the

employee creates an order for the customer. In this order, the employee defines which service (product) the customer wants to subscribe to. Depending on the product, additional configuration options are available for the customer and

need to be selected by the call center agent. In this specific

case the customer has chosen a product which offers also

allowances. After the selection is completed, the order is submitted to the fulfillment system and, based on the selected product, a customer contract is created. While this happens, the relevant master and transaction data of the contract is distributed to the relevant backend systems. As

last step a "manual refill" for the allowance is executed.

Simplified creation and change of customer master data in a Web UI

Captured customer orders in the SAP CRM using configurable predefined products - specifically products

containing allowances

Automated creation of customer contracts for the services the customer has subscribed to

Ability to manual refill allowances in SAP CRM

Integrated and flexible distribution of master and transaction data to SAP Hybris Billing, charging,

SAP Hybris Billing, invoicing, and SAP Hybris Billing,

customer financials

Customer, Contract Creation and Refill for Allowances

In the system

Key functionality

Create new customer

Create new order for existing product - containing allowances

Submit order and create contract

Manual refill of allowance

Industry focus: Telecommunications

and High Tech

allowance Industry focus: Telecommunications and High Tech Order creation with allowances © 2017 SAP SE or

Order creation with allowances

Consume Allowances and Recognize the Revenue

Scope and benefits

The deferred revenue has been created by the manual refill of allowances in SAP CRM (U98). Consuming the service associated to the allowance (by sending consumption data records to SAP Hybris Billing, charging) reduces the respective allowance quantity accordingly and by this the deferred revenue is recognized as "real" revenue in SAP Hybris Billing, customer financials.

Out-of-the-box integration to SAP Hybris Billing, Invoicing and SAP Hybris Billing, customer financials allowing accurate revenue recognition

Consume Allowances and Recognize the Revenue

In the system

Key functionality

SAP Hybris Billing, charging deducts

the consumed portion of the allowance

from the allowances balance

For consumed portions of the allowance the respective revenue can be recognized in SAP Hybris Billing, customer financials

Industry focus: Telecommunications and High Tech

financials Industry focus: Telecommunications and High Tech Allowances definition in SAP Hybris Billing, charging ©

Allowances definition in SAP Hybris Billing, charging

Contract Change from Prepaid to Postpaid Product

Scope and benefits

The change of a customer contract from a prepaid to a postpaid product supports the initiation of the product change in SAP Customer Relationship Management. Through this, the customer contract is adjusted and the changes are distributed to the other affected parts of the solution.

Automatic transition of contract from prepaid to postpaid without manual intervention

Consistency of customer contract across all part of

the solution through centrally initiated and monitored

change process

Both postpaid and prepaid subscribers can be in one platform, leading to prepaid to postpaid and postpaid- to -prepaid migrations

Contract Change from Prepaid to Postpaid Product

In the system

Key functionality

Start product change from prepaid to postpaid product in SAP Customer relationship management

Check the application of the change in the affected parts of the solution

Industry focus: Telecommunications and High Tech

Quick-start Implementation of SAP Hybris Billing

What’s included – Service scope

Leverage the SAP Services organization to quickly

deploy SAP Best Practices for SAP Hybris Billing (baseline configuration for more than twenty comprehensive order-to-cash business scenarios). Educate your team on the SAP Best Practices for SAP Hybris Billing as a preamble to an efficient and cost-efficient full implementation.

to an efficient and cost-efficient full implementation. © 2017 SAP SE or an SAP affiliate company.

Service Scope Options

A service scope option is a combination of scope that can be removed to reduce the service price.

Scope options

Required

Functionality delivered

M Foundation

Mandatory

SAP Best Practices for SAP Hybris Billing deployed

01 Software Installation

Optional

Software installed

02 FI Best Practice

Optional

SAP Best Practices S/4HANA Content Package selected scope items J59 deployed (providing baseline Financial Settings)

Deployment

03

End-User Review

Optional

Extended knowledge transfer to Key Users on SAP Best Practices for SAP Hybris Billing content

Partner’s scope of service may vary.

Integration Points in Scope

These Best Practices cover the E2E integration of the SAP Products/Product-Features which form the SAP Hybris Billing Solution. Additional integration points are listed below.

Integration point
Integration
point
From Product/ Solution
From Product/
Solution
To Product/ Solution
To Product/
Solution
Type
Type
Description
Description

Short description of integration point

From SAP product that integrates

To SAP product that integrates

Technical nature of integration e.g. ALE

Longer description of scope of integration perhaps covering business objects or data

Org. Structure

SAP S/4HANA

SAP CRM

CRM Middleware

Optional download and delta loads of customer master data from S/4HANA to Business Partners in CRM

Master Data: Chart of

SAP FI-GL

SAP S/4HANA

Chart of Account is referenced in the personalization step of the

Accounts

Contract Accounts Receivable and Payable

package deployment

Master Data: G/L Accounts

SAP FI-GL

SAP S/4HANA Contract Accounts Receivable and Payable

The G/L Accounts required for the Contract Accounts Receivable and Payable need to be created in the existing FI-GL Chart of Accounts and are referenced in the personalization step of the package deployment.

Master Data: House Bank, Currency Code, Bank Clearing Account, Payment Terms, Document Type for GL Transfer

SAP FI-GL

SAP S/4HANA Contract Accounts Receivable and Payable

The master data listed is referenced in the personalization step of the package deployment

Agenda Overview Scope Delivery Approach Software Products and Landscape SAP Service and Support Overview

Agenda

Overview

Scope

Agenda Overview Scope Delivery Approach Software Products and Landscape SAP Service and Support Overview

Delivery Approach Software Products and Landscape SAP Service and Support Overview

Agenda Overview Scope Delivery Approach Software Products and Landscape SAP Service and Support Overview

Typical Project Plan

Shows main project activities

START

4 to 7 Weeks

1 to 3 Weeks

Go-Live

1 Day

END

Prepare & Explore Realize Deploy Prepare Project Knowledge Transfer Workshop Hand Over Deliverables Confirm
Prepare & Explore
Realize
Deploy
Prepare Project
Knowledge Transfer
Workshop
Hand Over Deliverables
Confirm Installation
Test Solution
Preassembly - Activate
Solution
Preassembly - Confirm
Activation
Initial Hardware Sizing
Proposal
Project Kick-Off
SAP involvement
Validate Solution Workshop
Customer involvement

Project Team

SAP project manager

Serves as a central contact person, from project initiation to go-live and support

On the SAP side, responsible for functional project management,

coordination, support, and coaching of the customer’s project

manager, and so on

SAP consultants

Principal Business Process Consultant

Senior Business Process Architect

Senior Business Process Consultant

Principal Technology Consultant

Technology Consultant

Responsible for implementation of the agreed scope

 Responsible for implementation of the agreed scope © 2017 SAP SE or an SAP affiliate

Responsibilities

What SAP is responsible for?

Technical Installation check

Initial review workshop to confirm pre-defined requirements and assumptions

Baseline pre-configuration deployment related deliverables : Work Breakdown Structure with

schedule, baseline pre-configuration test scripts and

acceptance documents

Activation, configuration and unit tests of baseline pre-configuration Initial knowledge transfer to key customer users upon baseline pre-configuration content

Partner’s scope of service may vary.

Partner’s scope of service may vary.

What do you have to do?

Provide licenses and IT infrastructure (hardware)

compliant with SAP minimal hardware requirements

Coordination of work required from Licensee’s hosting or other third party vendors

Install SAP CRM, SAP S/4HANA (Industry Switch

FICAX or TELCO), SAP Hybris Billing, charging 4.1,

and optional SAP Hybris Billing, mediation on the development or sandbox environment

Provide User ID's and authorizations

Creation of net-new clients in SAP CRM and SAP

S/4HANA

Responsibilities

What do you have to do?

Activities included but not limited to the following list are considered out of the scope:

1. Analysis of as-is business processes

2. Field enhancements, developments, interfaces to other systems and any changes required because of pre-existing enhancements, developments or interfaces to other systems

3. Changes that are required because of industry specific functionality or requirements for country specific localization others than described

Partner’s scope of service may vary.

Partner’s scope of service may vary.

4. Data migration, data migration design, data

migration programs, changes required because of quality or values of Licensee’s master and transactional data or archiving strategy

5. End User training, formal SAP education classes

or other offerings from SAP Education

6. Deployment of the solution into multiple systems others than one (1) development or sandbox system

7. Performance, integration testing or Go-live preparation and execution

Combine Best Practices and Services into One Project

Combines multiple SAP Best Practices and engineered services into a single implementation project. It provides a faster lower cost alternative to the traditional design-based approach.

= SAP Best SAP Best Engineered Practices TM Service + Design Based Tasks for extra
=
SAP Best
SAP Best
Engineered
Practices TM
Service
+ Design Based Tasks
for extra scope
Practices TM
+ Extra A2O tasks for
design, integration,
testing and governance.
Project
for design, integration, testing and governance. Project Provides a new way to deliver projects faster based

Provides a new way to deliver projects faster based on best practices and

engineered services

faster based on best practices and engineered services An engineered delivery model uses local, near-shore and

An engineered delivery model uses local, near-shore and

offshore resources

Agenda Overview Scope Delivery Approach Software Products and Landscape SAP Service and Support Overview

Agenda

Overview

Scope

Delivery Approach Software Products and Landscape SAP Service and Support Overview

Agenda Overview Scope Delivery Approach Software Products and Landscape SAP Service and Support Overview
Agenda Overview Scope Delivery Approach Software Products and Landscape SAP Service and Support Overview

Which software is used?

SAP S/4HANA ON-PREMISE 1610 FPS 02

Enhancement package 4 FOR SAP CRM 7.0 SPS05

SAP Convergent Charging 4.1 SP02

(optional) SAP Convergent Mediation by DigitalRoute 3.2

* For more detailed information please refer to the Software and Delivery Requirements document.

SAP Best Practices for SAP Hybris Billing solution System landscape

CRM Server Convergent Mediation * S/4HANA Server SAP Convergent Mediation by DigitalRoute 3.1 Enhancement Package
CRM Server
Convergent Mediation *
S/4HANA Server
SAP Convergent
Mediation by
DigitalRoute 3.1
Enhancement Package 4
for SAP CRM 7.0 SPS05-
CRM Application Server ABAP
Convergent Charging
Enhancement Package 4
for SAP CRM 7.0 SPS05-
SAP Convergent
Charging 4.1 SP02
CRM Application Server JAVA
SAP S/4HANA ON-
PREMISE 1610
FPS 02

>

S/4HAHA Server has to be configured with a specific Business Function Set.

The Business Function Sets supported by the solution are

- TELCO

- FICAX

Telecommunications

High Tech, Banking, Postal Services

* Convergent Mediation is an optional product in this scenarios (for details check test script,Convergent Mediation Batch Scenario)

Agenda Overview Scope Delivery Approach Software Products and Landscape SAP Service and Support Overview

Agenda

Overview

Scope

Delivery Approach Software Products and Landscape SAP Service and Support Overview

Agenda Overview Scope Delivery Approach Software Products and Landscape SAP Service and Support Overview
Agenda Overview Scope Delivery Approach Software Products and Landscape SAP Service and Support Overview

One Global Team

Our consultants all over the world deliver SAP services to you, onsite as well as
Our consultants all over the world
deliver SAP services to you,
onsite as well as remote.

Alignment

We are closely aligned – ONE SAP to meet your needs best.
We are closely aligned – ONE SAP
to meet your needs best.

Vast Experience

Nowhere else can you find that

much experience on SAP solutions.

else can you find that much experience on SAP solutions. © 2017 SAP SE or an
else can you find that much experience on SAP solutions. © 2017 SAP SE or an

Risk Mitigation

Following a proven delivery model ensures project success.
Following a proven delivery
model ensures project success.
Thank you Contact information: F name MI. L name Title Address Phone number © 2016

Thank you

Contact information:

F name MI. L name

Title

Address Phone number

© 2016 SAP SE or an SAP affiliate company. All rights reserved.