SAP Billing and Revenue Innovation Management Rapid ...sapidp/... · SAP Billing and Revenue Innovation Management Rapid- ... English SAP Billing and Revenue Innovation Management

SAP Billing and Revenue Innovation Management Rapid-Deployment Solution V5.607

January 2015

English

SAP Billing and Revenue Innovation Management Rapid-Deployment Solution: Software and Delivery Requirements

SAP SE Dietmar-Hopp-Allee 16 69190 Walldorf Germany

Document Revisions Date

0

1

2

SAP Rapid Deployment Solutions Software and Delivery Requirements

© SAP SE Public Page 2 of 13

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 SE or an SAP affiliate company.

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

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

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company 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.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark



Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

External Process

Business Process Alternative/Decision Choice

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

Example text

Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT

Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example

text

Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example

text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example

text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.



Contents

1 Purpose of the Document ......................................................................................................... 5

2 General Project Prerequisites ................................................................................................... 5

3 Technical Requirements ........................................................................................................... 5

3.1 Software Product Versions ............................................................................................. 6

3.2 SAP Notes...................................................................................................................... 7

3.3 SAP Solution Manager Content Add-On ......................................................................... 9

3.4 Activation Content ........................................................................................................ 10

3.5 Active Business Function Set/Business Functions......................................................... 10

3.6 System Landscape ....................................................................................................... 13



1 Purpose of the Document This document contains all information to:

Validate that key prerequisites such as software products and versions match the customer situation

Check that all prerequisites for a customer implementation are in place

Check that correct content, tools and skills are in place before the project starts

The document lists different kinds of requirements on package level if they are valid for all scope items included in the package. For requirements valid for certain scope items only, these scope items are mentioned.

The document contains pre-requisites only, not the procedures to meet them. For how-to information (e.g. how to find the download area) please refer to the configuration guides.

2 General Project Prerequisites The following prerequisites need to be in place before an implementation project can start.

Prerequisite Responsibility

Kick off and workshop dates, location and attendees agreed Customer

Customer team allocated with correct skills and training in place Customer

Project sponsors and stakeholder identified Customer

Hardware fully commissioned Customer

Software licenses in place Customer

Infrastructure team can respond to requests quickly enough e.g. CSS notes, BW content, patches, user requests, authorization changes and transports

Customer

User interfaces agreed e.g. SAPGUI, Netweaver Business Client or Portal

Customer

Remote access is in place for SAP consultants and SAP Active Global Support

Customer

Decision made whether pre-assembled delivery will be used Customer

Decision made whether SAP Best Practices Solution Builder will be used to activate content.

Customer

Decision made whether Solution Manager will be used. Solution Manager set up with any relevant templates.

Customer

Tool for project repository and collaboration agreed Customer

Test management tool agreed Customer

3 Technical Requirements This section contains technical requirements in different areas. For each requirement, the relevance for scope items of the package is provided.



3.1 Software Product Versions The following software products and versions are required:

Product Product Version

Components Comments Relevance

SAP ERP EHP7 FOR SAP ERP 6.0

SPS06

Kernel has to be upgraded to the latest level

Utilities/Waste&Recycl./Telco

&

FINBASIS

* see remarks below this table

Industry specific Business Function Set “TELCO” has to be active. Refer to below section Active Business Function Set/Business Functions

For industry: Telecommunications

Leasing/Contract A/R & A/P

AND

FINBASIS

* see remarks below this table

Industry specific Business Function Set “FICAX” has to be active. Refer to below section Active Business Function Set/Business Functions

For industry: High Tech/ Postal Services/ Banking

SAP CRM EHP3 FOR SAP CRM 7.0

SPS06

Kernel has to be upgraded to the latest level

CRM Application Server ABAP

Activate Virtual Machine Container (VMC)

VMC is the prerequisite for running pricing. Refer to SAP Note 854170 for Activating the "VM Container" component.

Not required for Banking


SPS06

CRM Application Server Java


SAP Convergent Charging

SAP Convergent Charging 4.0

SP06

Core Server

BART Server

IEC

Please install rater instance,updater instance, dispatcher instance,guider instance, bulkloader instance and guider instance when install core server.

Please alwayse choose "Billing, Invoicing and Storage of Consumption Data in SAP Convergent Invoicing" as SAP Convergent Charging Integration Scenario during setup


http://service.sap.com/sap/support/notes/854170



SAP Convergent Mediation by DigitalRoute

SAP CM BY DIGITALROUTE 2.1

Optional Only revelvant for scope item U97 Convergent Mediation - Offline Scenario

SAP Best Practices Solution Builder

BP-SOLBLD 70Vx

Always use the latest available version as outlined in SAP Note 1301301.

BP-SOLBLD Add-on for the implementation tool (only necessary to be implemented in a system where content activation shall be done using the Solution Builder (i.e. Sandbox or Development System).

All Scope Items

SAP Solution Manager Logical Component:

Product Product Version SAP Solution Manager Logical Component

Relevance

SAP ERP EHP7 FOR SAP ERP 6.0

ERP60_EHP7_CENTRAL_APPL_BRIM All Scope Items


CRM70_EHP3_APPL_SERV_ABAP


For Business Function Set "TELCO":

Component "Utilities/Waste&Recyl./Telco" (comprising of multiple Software Components) has to be installed on EHP7 – SPS06 level;

Software Component "FINBASIS" has to be installed on EHP7 (Technical release 747) – SPS06 level

For Business Function Set "FICAX":

Component "Leasing/Contract A/R & A/P" (comprising of multiple Software Components) has to be installed on EHP7 – SPS06 level;

Software Component "FINBASIS" has to be installed on EHP7 (Technical release 747) – SPS06 level

Please be aware the Components have pre-requisites, which might demand to install/upgrade those Components/Software Components to EHP7 as well.

3.2 SAP Notes The following SAP Notes need to be considered:

SAP Note No

Content Comments Relevance




1886757 This SAP Note contains critical information for implementing the SAP Billing and Revenue Innovation Management rapid deployment solution

Before you start the activation of the related SAP Best Practices scope, check the latest versions of this SAP Note.

All Scope Items

1301301 Release Strategy for SAP Best Practices Package ABAP Add-ons

Attached to this add-on specific note you can find the corrections for the add-on. Always apply the correction transport for the corresponding add-on.

For example, for BP-SOLBLD 70V9, see SAP Note 1866271 and implement the Hotfix Note 1862674

All Scope Items when using automated content activation via solution builder

The following SAP Notes need to be applied in SAP ERP:

SAP Note No

Description Cross client

Comments

1287953 FS-CD: VKKKCUSTOD includes CI_FKKOP and CI_FKKOPK

X Manual correction only for software component INSURANCE with release lower than 605

1555393 BP_BCL: Adjustments of EA_FINSERV 600-605 for combinations with SAP_ABA 7.31, SAP_APPL 6.06 (or higher)

partly Only for EA_FINSERV 600-605.

The manual steps are not cross client

2068498 FKKBIX: abrrechenbare Positionen mit unterschiedlicher Währung in einer Abrechnungseinheit im Prepaid-Szenario nicht möglich

X

2087137 FKKBIX: BIT-Storno selektiert nur ein Vertragskonto des Geschäftspartners

X

2067235 FKKBIX: Except-Bausteine vereinheitlichen X

2085742 FKKBIX: Stammdaten-Anzeige in der Korrekturworkbench

X

2093209 Division Error in Health check X

2065582 Error in report RFKK_ENH_PPACC - DDIC prerequisite

X Implement the note then run report NOTE_2065582

2065490 Error in report RFKK_ENH_PPACC X Do read the solution in the Note

2028970 SEPA mandate: Check for 36 months of non-use

X







2049890 SEPA mandate: Check for 36 months of non-use II

X

2084040 Convergent Invoicing Prepaid Refill (unexpected additional BIT)

X Applicable if you use sample report RFKKBIXBITSAMPLE

2096133 FKKINV: SEGMENT is not transferred from billing document item

X

The following SAP Notes need to be applied in SAP CRM:

SAP Note No

Description Cross client

Comments

2093209 Division Error in Health check X

2106492 Business Agreement defaulting in Provider Order API

X

1152413 Error message CA_TTE429: Calling system ID is not defined

Manual correction

3.3 SAP Solution Manager Content Add-On For the implementation of the solution package, a SAP Solution Manager system is recommended. For SAP rapid-deployment solutions, implementation content is delivered via SAP Solution Manager templates.

Industry Telecommunications:

Template ID and Template Name

RDS_O2C_TC_ERP607V5 - SAP Billing and Revenue Innovation Management RDS for TC_V5

Solution Package Name(s)

SAP Billing and Revenue Innovation Management RDS for TC_V5

Industry High Tech:


RDS_O2C_HT_ERP607V5 - SAP Billing and Revenue Innovation Management RDS for HT_V5


SAP Billing and Revenue Innovation Management RDS for HT_V5

Industry Postal Services:


RDS_O2C_PT_ERP607V5 - SAP Billing and Revenue Innovation Management RDS for PT_ V5


SAP Billing and Revenue Innovation Management RDS for PT_ V5

Industry Banking:


RDS_O2C_BK_ERP607V5 - SAP Billing and Revenue Innovation Management RDS for BK_V5


SAP Billing and Revenue Innovation Management RDS for BK_V5



The latest available ST-RDS 100 content support package can be downloaded from the SAP Software Download Center on SAP Support Portal at http://support.sap.com/swdc.

3.4 Activation Content The following content is required:

Product Product Version Components as tested

Comments Relevance

SAP Best Practices Configuration Content (for SAP ERP)

BP-ERP 617Vx

BP-CANW 740Vx

Always use the latest available versions as outlined in SAP Note 1301301.

BP-ERP

BP-CANW

Add-ons containing ERP configuration content (only necessary to be implemented in the system which is used for the initial content activation (i.e. Sandbox or Development System).

SAP ERP

All Scope Items

SAP Best Practices Configuration Content (for SAP CRM)

BP-CRM 713Vx

BP-CANW 740Vx

Always use the latest available versions as outlined in SAP Note 1301301.

BP-CRM

BP-CANW

Add-ons containing CRM configuration content (only necessary to be implemented in the system which is used for the initial content activation (i.e. Sandbox or Development System).

SAP CRM

All Scope Items. Not required for Banking

3.5 Active Business Function Set/Business Functions Functionality in this solution package requires certain business functions to be active in the SAP landscape. These business functions need to be activated:

For SAP ERP Business Function Set: TELCO Telco

Business Function Description

CONVERGENT_INVOICING

Telco: Invoicing to Contract Accounts Receivable and Payable

FICA_FSCM_CRM_DISPUTE

Integration FICA Dispute / CRM Complaint

FIN_FSCM_BD SAP Biller Direct Buy Side

FIN_FSCM_BD_2 Biller Direct: Promise to Pay, Customer Field Extension

RM_CA Telco: Revenue Management - Contract Accounting

TEL_BI_INV_1 Telco,Enhanced Billing&Invoicing

TEL_CA_1 Telco, Enhanced Revenue Mgmt

TEL_CA_2 Telco, Enhanced Revenue Mgmt.

TEL_CA_3 Telco, Contract Accounts A/R and A/P 3

TEL_CA_4 Telco, Contract Accounts A/R and A/P 4





TEL_CA_5 Contract Accounts A/R and A/P, ERP 6.07 (Reversible)

TEL_CA_5B Contract Accounts Receivable and Payable, ERP 6.07 SP4 (Reversible)

TEL_CA_5E Contract Accounts Receivable and Payable, ERP 6.07 SP6 (Reversible)

TEL_CONV_INV_1 Telco, Enhanced Invoicing

TEL_EDR_BILLING Telecommunications, Billing

TEL_INV_1 Telco, Convergent Invoicing

TEL_INV_2 SAP Convergent Invoicing, ERP 6.07 (Reversible)

TEL_INV_PP_1 Telco, Invoicing in Contract Accounts Receivable and Payable

TEL_INV_PP_2 Telco, Billing in Contract Accounts Receivable and Payable 2

TEL_INV_PP_3 SAP Convergent Invoicing, ERP 6.07 (Reversible)

TEL_INV_PP_3A SAP Convergent Invoicing, ERP 6.07a (Reversible)

TEL_INV_PP_3D SAP Convergent Invoicing, ERP 6.07d (Reversible)

TEL_INV_PP_3E Billing in Contract Accounts Receivable and Payable 3E (Reversible)

For SAP ERP Business Function Set: FICAX Contract A/R + A/P


FICAX Non-Industry Contract Accounts Receivable and Payable, FI-CA Extended

FICAX_BILL_INVOICING Billing and Invoicing

FICAX_CI_1 Contract Accounts Receivable and Payable, 01

FICAX_CI_2 Contract Accounts A/R and A/P, 02

FICAX_CI_3 Contract Accounts A/R and A/P, 03

FICAX_CI_4 Contract Accounts A/R and A/P, 04 (Reversible)

FICAX_CI_5 Contract Accounts Receivable and Payable, ERP 6.07 (Reversible)

FICAX_CI_5B Contract Accounts Receivable and Payable, 05B (Reversible)

FICAX_CI_5E Contract Accounts Receivable and Payable, 05E (Reversible)

FICAX_CONV_INVOICING

Convergent Invoicing in Non-Ind.Contract Accts Receivable and Payable, FI-CAX

FICAX_INV_1 Invoicing Enhancements, SD Integration

FICAX_INV_2 Invoicing in Contract Accounts A/R and A/P, 02 (Reversible)

FICAX_INV_PP_1 Billing in Contract Accounts Receivable and Payable (FI-CA)

FICAX_INV_PP_2 Billing in Contract Accounts A/R and A/P, 01

FICAX_INV_PP_3 Billing in Contract Accounts Receivable and Payable, 02 (Reversible)

FICAX_INV_PP_3A Billing in Contract Accounts Receivable and Payable, 02A (Reversible)

FICAX_INV_PP_3D Billing in Contract Accounts Receivable and Payable, 02D (Reversible)



FICAX_INV_PP_3E Billing in Contract A/R and A/P, 02E (Reversible)

FICAX_LOC_1 Country-Specific Functions, 01 (Reversible)

FICA_FSCM_CRM_DISPUTE

Integration FICA Dispute / CRM Complaint

For SAP CRM:

You do NOT need to choose additonal entry in field Business Function Set. Keep this field empty.


CRM_FCA_1 FCC and Dispute Management for Contract AR/AP

CRM_FCA_2 FCC and Dispute Management for Contract AR/AP, 1

CRM_PROVORDERINT_1

Integration of SAP CC and SAP CI with the Provider Order

CRM_PROVORDERINT_2

Integration of SAP CC and SAP CI with the Provider Order for EhP3

CRM_PROVORDERINT_3_2

Integration of SAP CC and SAP CI with the Provider Order for EhP3 SP2 (Reversible)


Integration of SAP CC and SAP CI with the Provider Order for EhP3 SP4 (Reversible)


Integration of SAP CC and SAP CI with the Provider Order for EHP3 SP5 (Reversible)

CRM_SLS_SRV_1 Sales and Service

CRM_TEL_SOM_1 Sales & Order Management for Telecommunications

following Business Functions are for CRM Improvement like UI and Performance

CRM_INF_1 Infrastructure

CRM_PERFORMANCE Performance and Large Contracts

CRM_PERFORMANCE_2 Performance and Business Transaction Item Processing

CRM_TCI_1 Reduction of Implementation Time

CRM_WFI_FILTER_1 Filter for Workflow Inbox

UI_FRW_1 UI Framework

UI_FRW_1_DOCU UI Framework Documentation

UI_FRW_2_DOCU WebClient UI Framework Documentation

following Business Function is for SEPA (Single Euro Payments Area)

CRM_SEPA_1 Single Euro Payments Area (SEPA) Mandates

following Business Functions are for Simplified Configuration for product modeling

CRM_UT_BILL_CORR Utilities, Bill Correction (Reversible)

CRM_UT_CC_IREC_QV1 Utilities, Interaction Record Quick View on Identification (Reversible)

CRM_UT_CC_IREC_QV2 Utilities, Interaction Record Quick View on Overview (Reversible)



CRM_UT_CC_IREC_SCH Utilities, Interaction Record Improved Search (Reversible)

CRM_UT_ER_1 Utilities Energy Retailer

CRM_UT_ER_2 Utilities Energy Retailer 2

CRM_UT_ER_3 Utilities Energy Management (Reversible)

CRM_UT_IC_MAX_HITS Utilities, Maximum Number of Hits in Interaction Center (Reversible)

CRM_UT_MR_VAL Utilities, Meter Reading in Contract Management (Reversible)

3.6 System Landscape

* Convergent Mediation is optional in the rapid-deployment solution

Documents

SAP Billing and Revenue Innovation Management Rapid ...sapidp/... · SAP Billing and Revenue Innovation Management Rapid- ... English SAP Billing and Revenue Innovation Management