CRM RDS Scope Document - websmp202.sap-ag.desapidp/012002523100013609852014E/RDS... ·...

SAP Rapid Deployment Solution

EHP7 for SAP ERP 6.0

EHP3 for SAP CRM 7.0

SAP Convergent Charging 4.0

January 2015

English

Scope Description SAP Billing and Revenue Innovation Management rapid-deployment solution V5.607


/15 Public

Copyright © 2014 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Revision Change Date Description

0


Content 1 Use of this Document ................................................................................................................................... 4

2 Introduction ................................................................................................................................................... 5

2.1 Solution View ..................................................................................................................................... 5

2.2 Use Cases for rapid-deployment ....................................................................................................... 5

2.3 Industry Variants of the Content ........................................................................................................ 6

3 Solution and Industry Scope ........................................................................................................................ 8

3.1 Process Scope ................................................................................................................................... 8

3.2 Industry Scope ................................................................................................................................. 11

3.3 Configuration Scope ......................................................................................................................... 12

4 Integration Aspects and Deployment Prerequisites ................................................................................... 13

4.1 Software and System Prerequisites ................................................................................................. 13

4.2 Localization Aspects ........................................................................................................................ 14

5 Decision point ............................................................................................................................................. 15


/15 Public

1 Use of this Document

This document describes the covered scope as well as best-practices how to use the SAP Billing and Revenue Innovation Management rapid-deployment solution.

The focus is to give a condensed overview

about the content available with this rapid-deployment solution is providing

and how this content can be used as a starting point for an implementation

of SAP Billing and Revenue Innovation Management.

The information provided in this document shall help to take the decision of this rapid-deployment solution being recommended to be used to accelerate a specific implementation project of SAP Billing and Revenue Innovation Management.

The document therefore focusses on the concepts and use-cases of the rapid-deployment solution. As a prerequisite a general knowledge about the SAP Billing and Revenue Innovation Management solution is expected.

Note: Since this document shall be self-contained, it also includes summarized information which (in more detail) is available in other RDS documents as well.

The structure of the document is as follows:

The “Introduction” chapter provides a quick overview of the solution, the main use cases and prerequisites to be able to use the rapid-deployment solution, and the industry specifics of the content.

The “Solution and Industry Scope” chapter provides further details on the processes and industry variants which are configured as part of the rapid-deployment solution. And it adds a basic description on the different types/layers of the delivered configuration.

The “Integration Aspects and Deployment Prerequisites” chapter describes both technical prerequisites and configuration prerequisites. It mainly focusses on how the configuration content interacts with existing configuration of SAP ERP / FI-GL. And it describes how the configuration content is built w.r.t. different country configurations in a system.

The “Decision point” chapter offers some examples how – based on the check of the project demand vs. the provided configuration and knowledge content – a decision to “Use”, “Not Use” or “Partly Use” of the rapid-deployment solution can be taken.


/15 Public

2 Introduction

2.1 Solution View

The SAP Billing and Revenue Innovation Management rapid-deployment solution includes the core features customers need to monetize their services and share revenue throughout their partner ecosystem.

The solution joins

the SAP Customer Relationship Management (SAP CRM) application,

the SAP Convergent Charging application,

the SAP Convergent Invoicing package (part of SAP ERP),

and the SAP Customer Financial Management package (part of SAP ERP)

to create a comprehensive software solution that supports sales order and contract creation and the consume-to-cash business process.

With this integrated solution, you can flexibly set and charge fees in real time, optimize your billing and invoicing process, and manage receivables, payables, financial customer care, dispute management, and collections with full transparency. You can also obtain a single, complete view of customer activities.

The rapid-deployment solution allows to quickly setup the baseline of SAP Billing and Revenue Innovation Management solution at a predictable price by:

Connecting the different products and components of the solution

Delivering end-to-end process configuration in the most commonly used solution areas

Setting up sample master data which allows to directly run the sample processes

Providing best-practices configuration which can build the foundation for the final production setup

2.2 Use Cases for rapid-deployment

The main use case is a complete new / “greenfield” configuration of an SAP Billing and Revenue Innovation Management solution comprised of

- A new SAP CRM system or a new client of an existing system

- A new SAP Convergent Charging system

- Either new SAP ERP system or new or existing client of an existing SAP ERP (FI-GL) system

For all systems a specific release and support level is prerequisite for an automated deployment of the configuration content – as well as being able to execute all processes pre-configured by the rapid-deployment solution.

The technical scenario above is the main use case the rapid-deployment solution is built for. The rapid-deployment solution provides configuration across the three systems, which allows to run a set of standard processes (“Order to fulfillment” and “Usage to pay”) immediately after the content is deployed.

For other system scenarios the rapid-deployment solution content can support in various ways, but is not out-of-the box ready.

Examples of such scenarios are:


/15 Public

- Deployment into a landscape without an SAP CRM system

- Deployment into a landscape where SAP CRM is already fully configured

- Deployment for SAP ERP only.

For such scenarios there are two main ways how the rapid-deployment solution can be used:

- One way is to use the configuration guides provided with the automated deployment content to configure those part of the solution required in the specific context.

- The second way – which needs deeper understanding of the content and the deployment tool (Solution Explorer) – is to adjust the automated content (Solution Scope) to the scenario and system scope.

2.3 Industry Variants of the Content

The industry variants supported by the rapid-deployment solution relate to two aspects:

a) Setup of the SAP ERP system (which FI-CA variant is active?)

b) Configuration/master data of the rapid-deployment solution

Regarding a) the so called “Business Function Set” which is either already active or is planned to be activated in the SAP ERP system is important to be known. The Contract Accounts Receivables/Payables solution (FI-CA) is available as part of multiple industry solutions – which are represented by different “Business Function Sets” in the SAP ERP system.

For the automated content deployment of this rapid-deployment solution two different Business Function Sets in SAP ERP are supported:

- Contract A/R + AP (technical name: FICAX)

- Telco (technical name: TELCO)

In a SAP Billing and Revenue Innovation Management solution landscape, exactly one of those two Business Function Sets in SAP ERP can be active – and the activation affects the complete system, not only a single client.

Other Business Function Sets which contain FI-CA are currently not officially part of the SAP Billing and Revenue Innovation Management solution and therefore also not included into the rapid-deployment solution.

Note: For more information on Business Function Sets, please check http://help.sap.com/saphelp_erp60_sp/helpdata/en/42/f1825bfaf93255e10000000a1553f7/frameset.htm

For SAP CRM the activation of the SAP Billing and Revenue Innovation Management solution is controlled via Enterprise Business Functions – which have to be activated separately for this solution and work with any of the two SAP ERP Business Function Set variants.

For SAP Convergent Charging there is no similar approach of Business Function Sets or Enterprise Business Functions. The product works with any of the valid system configuration w.r.t Business Function Sets in SAP ERP and Business Function in SAP CRM as outlined above.

Regarding b) the rapid-deployment solution is to a high degree industry-agnostic. The entire integration configuration, base configuration and most of the process configuration are not built for a specific industry, but can be used for any industry – to extend the processes fit to this industry.

http://help.sap.com/saphelp_erp60_sp/helpdata/en/42/f1825bfaf93255e10000000a1553f7/frameset.htm


/15 Public

In addition to this configuration the rapid-deployment solution contains a set of pre-populated master data – mainly products and charge plan examples (in SAP CRM, SAP Convergent Charging) as well as the necessary configuration to bill and invoice these products and charge plans in SAP ERP.

These products and charge plans examples are defined having industry specific use cases in mind. With this they are aimed as examples showing capabilities provided by the SAP Billing and Revenue Innovation Management solution along the process chain.

Depending on the system setup the rapid-deployment solution offers a set of master data following the main use cases for such a Business Function Set configuration:

- Business Function Set “Telco”: Here the example master data defines products for a “Mobile Service Provider” delivering Postpaid and Prepaid Services – both for Consumers as well as for Business Customers.

For the automated deployment of the content, the deployed scenarios/scope items can still be configured. One example for this would be to only deploy either Postpaid or Prepaid Services configuration (where the default is to deploy both).

- Business Function Set “Contract A/R + A/P”: Here the example master data as well as the automated deployment offers industry variants.

Note: “Contract A/R + A/P” is the cross-industry variant of the solution – used by industries like High Tech, Postal Services, Logistic Services Providers, and more.)

The example master data is built for:

o High Tech - Simple IT/Cloud Service Products which support Postpaid and Prepaid Services – both for Consumers as well as for Business Customers. The process scope is exactly the same like for “Telco”.

o Postal Services – Simple Package and Special Letter based Postpaid products – both for Consumers as well as for Business Customers. The process scope is a subset of the “High Tech” scope – using different products.

o Banking – Is a special case of this rapid-deployment solution. The banking specific scenarios only relate to SAP ERP – they do not need a SAP Convergent Charging or SAP CRM. The process scope is covering exactly one scenario specific for banking.

Due to the high degree of industry agnostic configuration and content delivered by the rapid-deployment solution, any implementation project can leverage this content and example master data – independent of the industry.

Only prerequisite is to fulfill the system landscape and Business Function Set requirements of the SAP Billing and Revenue Management solution in general.


/15 Public

3 Solution and Industry Scope

The SAP Billing and Revenue Innovation rapid-deployment solution covers multiple aspects both from a process and from a solution perspective. The previous chapter provided a general overview on the solution and the content provided by the rapid-deployment solution.

This chapter adds more details on the process scope and industry scope delivered by the content of the rapid-deployment solution. The view provided here covers three main dimensions of this rapid-deployment solution:

- Process Scope -> which processes are pre-configured

- Industry Scope -> which industries are supported by example master data

- Configuration Scope -> how is the configuration structured and re-usable

-

The chapter “Configuration Scope” adds a new dimension to understand how the rapid-deployment solution helps in an implementation project. It separates the content looking into the character of the configuration (Foundation, Integration, Process and Master Data).

3.1 Process Scope The processes pre-configured as part of the rapid-deployment solution can be grouped as follows:

- Postpaid End-to-End processes

- Prepaid End-to-End processes

- Financial Customer Care

- Business-to-Business process

- Banking industry example

3.1.1 Postpaid End-to-End Processes

The processes summarized here deliver a baseline configuration as well as master data examples to support the main End-to-End processes for a postpaid service provider. The single scope items are part of the E2E processes:

- Offer to Fulfill and

- Consume to Cash.

The process configuration delivered by the rapid-deployment solution is mostly industry agnostic. Product master data examples are tailored for specific industries. For postpaid processes these are:

- Telecommunications

- High Tech and

- Postal Services.

The included scope items are:

Offer to Fulfill:

- Customer and Contract Creation


/15 Public

- Contract Creation and Refill for Allowances

Consume to Cash:

- Convergent Mediation – Batch Scenario

- Use Service, Create Invoices and Pay

- Consume Allowances and Recognize the Revenue

Others:

- Daily and Monthly closing

- Creation of Sample Master Data using Data Migration

Further details on the single processes / scope items are available in the complete rapid-deployment solution documentation e.g. in the Scope Item Fact Sheets.

3.1.2 Prepaid End-to-End Processes

The processes summarized here deliver a baseline configuration as well as master data examples to support the main End-to-End processes for a prepaid service provider. The single scope items are part of the E2E processes:

- Offer to Fulfill and

- Consume to Cash / Balance Management.

The process configuration delivered by the rapid-deployment solution is mostly industry agnostic. Product master data examples are tailored for specific industries. For postpaid processes these are:

- Telecommunications and

- High Tech.


Offer to Fulfill:

- Customer and Contract Creation

- Contract Change from Prepaid to Postpaid Product

Consume to Cash:

- Use Service, Manage Balance and Financials

- Refill Prepaid Account by “One Time Permission”

- Termination of Prepaid Service and Closing of Prepaid Account

- Refill Prepaid Account via Voucher Activation

Others:

- Daily and Monthly closing

- Creation of Sample Master Data using Data Migration


/15 Public


3.1.3 Financial Customer Care

Financial Customer Care offers a 360 degree view on all financial management related activities and allows handling all types of customer queries from one place - the SAP CRM Interaction Center.


- Financial Inquiries

- Bill Display and Dispute Management

- Collections in CRM Interaction Center

- Actions on Prepaid Accounts


3.1.4 Business-to-Business Processes

Service providers need to offer new multi-sided business models where they have to manage partner revenue. And they need the ability to handle complex contracts and master agreements to support delivering service to organizations and companies.


- B2B Master Agreement with Counter Sharing

- Bulk Ordering and Mass Cancellation of Provider Contracts

- Revenue Sharing and Partner Settlement

- Data Storage for Consumption Items

- Preliminary Invoice

- Item Corrections in Convergent Invoicing


3.1.5 Banking Industry example

As an example how the solution can be used in other industries, a scenario from the banking industry is delivered with the rapid-deployment solution.

The included scope item is:

- Consolidated Statements for Banking Postpaid Services



/15 Public

3.2 Industry Scope

As explained in the previous chapters the configuration content of the rapid-deployment solution is mainly industry-agnostic. This means the configuration itself does not contain any industry codes or similar.

The industry relation of configuration content is mainly related to the processes which are pre-configured by the rapid-deployment solution. In combination with the industry specific product master data provided, the content delivers more sophisticated process support.

Industries with dedicated master data examples are:

- Telecommunications -> postpaid and prepaid mobile services

- High Tech -> postpaid and prepaid cloud service charging

- Postal Services -> postpaid letter and parcel charging

- Banking -> consolidated bank statements

As explained in Chapter 2.3, the configuration content is industry agnostic and enables the processes described in Chapter 3.1.

If the rapid-deployment solution is aimed to be used for a different industry, or for a different use-case within one of the listed industries,

- the configuration still can be used as baseline and

- the master data examples can be used as templates to create the required master data.


/15 Public

3.3 Configuration Scope

In this chapter a more detailed view on the content building block structure for this rapid-deployment solution will be provided.

Foundation – covers the configuration required to prepare the systems which are part of the SAP Billing and Revenue Innovation Management solution both from technical and business perspective.

Technical configuration covers topics like activation of the Business Function Sets and all technical settings which are prerequisite for the solutions. Business configuration covers areas like the organizational structure settings and general settings for e.g. business partner, contract account, payment cards, number ranges.

Integration – covers the configuration required to connect the systems which form the SAP Billing and Revenue Innovation Management solution with each other. The integration configuration is done specifically for the solution.

Covered are the areas of master data replication and transaction data replication, as well as the integration of financial customer care into the SAP CRM Interaction center. With this configuration not only the processes provided as part of the rapid-deployment solution are covered, but all the main functionality of SAP Billing and Revenue Innovation Management solution is supported.

Processes – covers the configuration of the processes supported by the rapid-deployment solution. Process configuration is to major part industry agnostic. Variations apply e.g. for Postal Services deployments where prepaid processes are not in scope.

Details on the processes can be found in the overall scope item list and as a summary in chapter 3.1 of this document.


/15 Public

4 Integration Aspects and Deployment Prerequisites

The SAP Billing and Revenue Innovation Management rapid-deployment solution provides content for the full solution landscape:

SAP Customer Relationship Management (SAP CRM) application,

SAP Convergent Charging application,

SAP Convergent Invoicing package (part of SAP ERP),

and the SAP Customer Financial Management package (part of SAP ERP)

The solution offers great flexibility both with regards to supported business processes as well as possible deployment variants. The rapid-deployment solution covers ONE main deployment variant of the solution which is explained in more detail in the next chapter.

In addition the rapid-deployment solution has a specific approach how to handle integration and localization aspects to existing solutions.

4.1 Software and System Prerequisites

This main deployment option is the full deployment of the solution – which technically are the systems:

Enhancement package 7 for SAP ERP 6.0 - SPS06

Enhancement package 3 for SAP CRM 7.0 - SPS06

SAP Convergent Charging 4.0 SP06

(optional) SAP Convergent Mediation by DigitalRoute 2.1

Since the configuration has to fit and interact with potentially existing configuration, the rapid-deployment solution defines a set of prerequisites regarding the client(s) which are used for a standard deployment:

SAP CRM: a new client copy from Client 000 – without any configuration from any other CRM client

SAP ERP: a new client copy from Client 000 – into which the demanded prerequisite configuration (e.g. FI-GL) can either be transported from another system or has been configured. Please observe that the use of client copy from a system which was installed on a release lower than EHP7 of ERP 6.0 requires configuration enhancements to provide the required configuration prerequisites.

Other deployment variants with regards to client setup are not tested with the automated deployment of configuration content. Depending on the individual configuration setup of the client in which the rapid-deployment solution is planned to be deployed, both preparations of the clients and/or the configuration content activation may require additional (manual) efforts.

4.1.1 SAP CRM Prerequisites

For SAP CRM the rapid-deployment solution does not require any specific configuration prerequisites. All necessary base configurations are part of the standard configuration delivered with the software. For further details how to ensure that all base configurations are available in the new SAP CRM client is provided by the technical guides which are part of the deployment description.


/15 Public

4.1.2 SAP ERP Prerequisites

For SAP ERP the rapid-deployment solution has a number of configuration prerequisites which need to be fulfilled to allow the automated deployment of the configuration. The configuration content delivered with the rapid-deployment solution covers only the solution specific parts. The concept behind is to not interfere with non-solution specific configuration and in this way allow the integration of the new configuration content to already existing setups.

The rapid-deployment solution assumes the following main areas in SAP ERP already being configured:

Organizational Structure: Has to be defined as a prerequisite for the automated deployment of the configuration content. With this, each deployment has the choice to create their own structure (in the boundaries described in the detailed prerequisite guides). But there is neither a pre-defined numbering, nor does the automated deployment overwrite any existing settings.

Chart of Accounts / FI-GL: The rapid-deployment assumes an existing FI-GL (General Ledger) to integrate with SAP Customer Financials Management (which is part of the overall solution). Both FI-GL and SAP Customer Financials Management share the same Chart of Accounts. For SAP Customer Financials Management a set of G/L accounts is required to do the necessary G/L postings. Since G/L accounts are usually customer/country specific all required G/L accounts have to be created in FI-GL for the specific company code before the rapid-deployment solution can be deployed.

Tax calculation and posting: All tax calculation related configuration needs to be available to deploy the automated content. At least one input tax and one output tax have to be defined.

In addition the rapid-deployment solution needs all base configurations which are part of standard configuration delivered with the software. For further details how to ensure that all base configurations are available in the new SAP ERP client is provided by the technical guides which are part of the deployment description.

4.1.3 Other Prerequisites

For both SAP Convergent Charging and SAP Convergent Mediation by DigitalRoute there are no specific content prerequisites defined.

The assumption is that new/empty instances of the products are deployed and integrated into the system landscape.

4.2 Localization Aspects

The rapid-deployment solution configuration content does not cover any country / localization specific aspect of the solution. The base and process configuration as well as the example master data contains only limited country or localization specific parts – allowing fast adoption to the specific demands of a project.

To allow the deployment of the configuration into any system which fulfills the prerequisites described in chapter 4.1, all country related objects like e.g. Country Code, Currency, Company Code, Chart of Accounts, etc. do not have fixed definition, but are defined at the point of deploying the configuration content. By this they can be substituted with the system specific settings and the deployed configuration content is in sync with the existing configuration.


/15 Public

5 Decision point

With the information provided in this document the decision point about use of the rapid-deployment solution in a project is reached. Here some indication and examples which shall help taking that decision based on facts:

Possible decision outcomes here are Usable / Partly Usable / Not Usable:

- Usable: The system landscape / use case and the industry related as well as the process aspects for the SAP Billing and Revenue Innovation Management rapid-deployment solution are fulfilled, there is a clear indication to start an implementation by deploying the rapid-deployment solution first. Further detailed work on both technical/system prerequisites to implement the solution and on the way how to best use the rapid-deployment solution is the next propose step going forward.

- Partly : Besides clear “Usable” cases – e.g. greenfield setups of an E2E system for SAP Billing and Revenue Innovation Management – there are many cases where the rapid-deployment solution can help in various ways.

Identification of the best way to use the content is subject to the project team. To give some indication here an example:

SAP CRM is already fully configured: Here a merge of the content delivered by the rapid-deployment solution and the existing SAP CRM content is required. Depending on the depth of configuration in SAP CRM there are different ways to do this – which need to be decided on project level. Still the rapid-deployment solution content can be used, as it in detail describes what configuration is required by the SAP Billing and Revenue Innovation Management solution.

Since the rapid-deployment solution not only supports automated configuration deployment, but as well covers detailed descriptions of each configuration step necessary structured by the different systems and scenarios/processes affected, the use of this content simplifies the implementation of the solution. It removes the need to evaluate what steps need to be done to configure for a certain scenario, and allows focusing on how in detail that scenario shall work.

- Not: If none of the system landscape / use case prerequisites are met, and if there is also not intend to move the project from a scope perspective towards a broader use case, such project might not benefit from using the rapid-deployment solution. One example for such a case is a “pure” SAP Convergent Charging implementation which is not linked to SAP CRM or SAP ERP. Another example is a SAP CRM implementation for e.g. Order Management (using the SAP Billing and Revenue Innovation Management related new functionality) – but without having SAP Convergent Charging or SAP ERP in place.

CRM RDS Scope Document - websmp202.sap-ag.desapidp/012002523100013609852014E/RDS... ·...

Documents

Transcript of CRM RDS Scope Document - websmp202.sap-ag.desapidp/012002523100013609852014E/RDS... ·...