Upgrade Master Guide | PUBLIC

Document Version: 1.0.0 – 2024-09-09

SAP Billing and Revenue Innovation Management

Integration
© 2024 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN

Content

1 Integration with the Solution Quote Object in SAP S/4HANA: SAP Billing and Revenue
Innovation Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2 Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3 Quote-to-Cash Context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

4 System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

5 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

6 Configuration in SAP CPQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

6.1 Create Communication User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Client Certificate Authentication in SAP CPQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.2 Enable the Integration with SAP Billing and Revenue Innovation Management. . . . . . . . . . . . . . . . . . 15
6.3 Enable the Integration with SAP Cloud Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
6.4 Enable the Integration with SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
6.5 Enable the Integration with SAP Variant Configuration and Pricing. . . . . . . . . . . . . . . . . . . . . . . . . . 18
6.6 SAP General Attribute Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
6.7 Pricing Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Create Markets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Create Pricebook. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
Discounting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Discounting Priorities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Setting SAP S/4HANA Pricing Procedures in SAP CPQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Set up Calculations on Item Add/Copy/Delete. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Set up Calculations on Field Value Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Rounding Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
6.8 Configure Workflow in SAP CPQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Enable Workflow Actions and Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
6.9 Partner Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Create Partner Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Set Sold-To Party to Mandatory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Partner Functions in SAP CPQ quote. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
6.10 Create Business Partners. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
6.11 Product Replication Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Products: Types and Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Maintain Product Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Maintain Product Categories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33

SAP Billing and Revenue Innovation Management Integration

2 PUBLIC Content
 Maintain Billing Cycle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Maintain Service Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Maintain Response Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Maintain Billing Date. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Maintain Settlement Period. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
6.12 Enable Quote and Item Comments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Make the Fields Editable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Make the Fields Visible on Quotes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
6.13 Multi-level Products (Bundle and Non-bundle). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
6.14 Change Processes and Renewals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Add Assets Table to Quote Layout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Set up Workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Add Asset Table Column. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Add a Change Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Cancellation Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Make the Cancellation Fields Editable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Autorenewals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Make the Fields Editable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
Subscription Contract Renewal Process Capabilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

7 SAP S/4HANA Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

7.1 Important Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
7.2 Create User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
7.3 Define Logical System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
7.4 Business Partner Replication via SAP Master Data Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Activate Function Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Configure Data Replication Framework. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Create Replication Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Configuring SAP Master Data Integration for Business Partners replication. . . . . . . . . . . . . . . . . 58
Create Distribution models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
7.5 Product Replication from SAP Billing and Revenue Innovation Management to SAP CPQ using
SOAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Configure Data Replication Framework. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Configure Replication Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Configuration for Filter Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Automatically Generate Integration Settings for Data Exchange. . . . . . . . . . . . . . . . . . . . . . . . . 63
7.6 Settings in SOAMANAGER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
Port for Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Port for Business Partners. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
7.7 Configurations for Product Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Define Product Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Define Product Hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

SAP Billing and Revenue Innovation Management Integration

Content PUBLIC 3
7.8 Pricing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Condition Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
Define Pricing Procedure for Stateless Pricing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77
Pricing Procedure Determination for Stateless Pricing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84
Define Pricing Procedure for Document Pricing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Pricing Procedure Determination for Document Pricing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90
7.9 Transaction Customizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91
Define Partner Determination Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Maintain Organizational Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Define Transaction Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Define Item Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Define Item Category Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Define Item Category Determination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Copying of Transaction Types for Sales Order. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Define Copying Control for Transaction Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Define Copying Control for Item Categories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Subscription specific customizing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
7.10 Maintain Service Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
7.11 Maintain Response Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113
7.12 Activate Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
OData V2 services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113
OData V4 services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114
7.13 Periodic jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

8 Setup SAP Event Mesh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

8.1 Configuration in SAP Event Mesh for Sending Quote from SAP CPQ to SAP S/4HANA. . . . . . . . . . . 115
8.2 Configuration in SAP CPQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116
8.3 Configuration for processing of Change Contract Processing Status. . . . . . . . . . . . . . . . . . . . . . . . 117
8.4 Maintain Event Topics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
8.5 Create Queue for the Business Solution Quote events in SAP Event Mesh . . . . . . . . . . . . . . . . . . . . 118

9 SAP Cloud Integration Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

9.1 Creating User Credentials in SAP Cloud Integration System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
9.2 Client Certificate Authentication - SAP Cloud Integration Configuration. . . . . . . . . . . . . . . . . . . . . 120
9.3 View Prepackaged integration flows using SAP Cloud Integration Web UI. . . . . . . . . . . . . . . . . . . . .121
9.4 Configure and Deploy the integration flow using SAP Cloud Integration Web UI (Replication from
SAP CPQ to SAP Billing and Revenue Innovation Management). . . . . . . . . . . . . . . . . . . . . . . . . . . 121
9.5 Configuration of the integration flow “Replicate Quote 2.0 from SAP CPQ to SAP S/4HANA”. . . . . . .121
Sender Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Receiver Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
More Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Deployment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

SAP Billing and Revenue Innovation Management Integration

4 PUBLIC Content
 Extension Implemented. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
9.6 Configuration for integration flow “Replicate Product from SAP S/4HANA”. . . . . . . . . . . . . . . . . . . 126
Sender Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Receiver Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
More Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
9.7 Configuration for integration flow “Replicate Business Partner from SAP Master Data Integration”
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Receiver Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
More Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
9.8 Configuration for integration flow “Read Subscription contract header from SAP Billing and
Revenue Innovation Management”. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Receiver Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
More Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
9.9 Configuration for integration flow “Read Subscription contract items from SAP Billing and
Revenue Innovation Management” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Receiver Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131
More Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
9.10 Configuration for integration flow “Read Change Process Groups for Quote from SAP Billing and
Revenue Innovation Management”. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Receiver Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
More Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
9.11 Configuration for integration flow “Read Change Process for Quote from SAP Billing and Revenue
Innovation Management” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Receiver Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
More Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
9.12 Configuration for integration flow “Read allowed Change Process Groups for Subscription
Contract Item from SAP Billing and Revenue Innovation Management” . . . . . . . . . . . . . . . . . . . . . 134
Receiver Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
More Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
9.13 Configuration for integration flow “Replicate Change Contract Processing Status from SAP
S4HANA” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135
Sender Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Receiver Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
More Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
9.14 Settings in SAP Cloud Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
9.15 Create Distribution Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
9.16 Value Mapping for SAP CPQ Integration with SAP Billing and Revenue Innovation Management
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Product Category. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Country. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139
Region. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
OrderItemType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139
Time Zone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

SAP Billing and Revenue Innovation Management Integration

Content PUBLIC 5
 Primary Industry. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Form of Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140
Bundle Item Category. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

10 Master Data Creation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

10.1 Product Bundle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
10.2 Product Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
10.3 Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
10.4 Product Master Data: SOM_REC_CPQ_MOVIE_CONFIG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Create Product SOM_REC_CPQ_MOVIE_CONFIG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Maintain Characteristic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146
Create Class. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Maintain Variant Configuration Modeling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Maintain Prices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
10.5 Product Master Data: SOM_REC_CPQ_CLOUD_UNLIMITED_YEAR. . . . . . . . . . . . . . . . . . . . . . . . 156
Create Product SOM_REC_CPQ_CLOUD_UNLIMITED_YEAR. . . . . . . . . . . . . . . . . . . . . . . . . . 157
Maintain Prices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
10.6 Product Master Data: SOM_BSV_CPQ_CLOUD_001. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Create Product SOM_BSV_CPQ_CLOUD_001. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
10.7 Product Master Data: SOM_SLS_CPQ_TABLET_BASIC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Create Product SOM_SLS_CPQ_TABLET_BASIC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Maintain Prices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
10.8 Product Master Data: SOM_SLS_CPQ_TABLET_CONFIG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Create Product SOM_SLS_CPQ_TABLET_CONFIG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Maintain Characteristic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166
Create Class. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Maintain Variant Configuration Modeling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Maintain Prices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172
10.9 Product Master Data: SOM_SVC_CPQ_SUPPORT_GOLD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174
Create Product SOM_SVC_CPQ_SUPPORT_GOLD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Maintain Prices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
10.10 SAP S/4HANA Bundle Multi-Level Product. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Create Root Bundle Product SOM_BUN_CPQ_1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Create BOM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Maintain Variant Configuration Modeling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
10.11 Business Partner Master Data: BP_Test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

11 Data Loading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185

11.1 Business Partner (Customer Master). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
11.2 Product Master. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
11.3 Verify products in SAP CPQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
11.4 Verify Business Partner in SAP CPQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

SAP Billing and Revenue Innovation Management Integration

6 PUBLIC Content
12 Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
12.1 Ticket Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188
12.2 How to setup Cloud Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
12.3 BCP Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

SAP Billing and Revenue Innovation Management Integration

Content PUBLIC 7
1 Integration with the Solution Quote
Object in SAP S/4HANA: SAP Billing and
Revenue Innovation Management

This integration connects the quote object in the Quote 2.0 engine in SAP CPQ with the solution quote object in
SAP S/4HANA (SAP Billing and Revenue Innovation Management).

This integration uses SAP Cloud Integration as middleware for communicating data across the systems.

SAP Billing and Revenue Innovation Management Integration

Integration with the Solution Quote Object in SAP S/4HANA: SAP Billing and Revenue
8 PUBLIC Innovation Management
2 Purpose

This document describes the steps to configure the basic integration between SAP CPQ and SAP Billing and
Revenue Innovation Management using SAP Cloud Integration.

SAP CPQ can be integrated with SAP Billing and Revenue Innovation Management to provide a workflow for
users to automatically create an SAP S/4HANA Solution Quotation whenever a SAP CPQ quote is sent to
SAP Billing and Revenue Innovation Management. The follow-up documents are created inside SAP Billing and
Revenue Innovation Management automatically. This integration only works with the Quote 2.0 engine in SAP
CPQ.

The integration is triggered by the “Place Order” event when user chooses Place Order action in SAP
CPQ Quote, i.e. when the user finishes the quote process and sends the final quote to the backend which
would create a Solution Quotation and its follow-up documents (e.g. Subscription Contract). SAP Variant
Configuration and Pricing is used as default mechanism for configuring and pricing subscription (SAP Billing
and Revenue Innovation Management) products in SAP CPQ. If the quote item is configurable, the quote data
from SAP CPQ and the configuration data from SAP Variant Configuration and Pricing are combined and sent
to SAP Billing and Revenue Innovation Management. Otherwise, only the standard product information and
pricing details are transferred to SAP Billing and Revenue Innovation Management. Products that have not
been replicated from SAP Billing and Revenue Innovation Management, but created directly in SAP CPQ, are
ignored in the integration, which creates SAP S/4HANA Solution Quote from SAP CPQ Quote.

 Note

The setup instructions in this guide only describe the basic authentication. Nevertheless, certificate-based
authentication might also be possible, depending on the system preconditions.

SAP Billing and Revenue Innovation Management Integration

Purpose PUBLIC 9
3 Quote-to-Cash Context

The Quote-to-Cash process comprises activities that aim to convert sales opportunities into paying, long-
lasting return customers.

The SAP CPQ–SAP Billing and Revenue Innovation Management integration covers the essential part of the
quote-to-cash process.

The sales representative configures a quote in SAP CPQ and optionally negotiates legal terms in Icertis
Contract Intelligence with the customer until a final agreement is achieved and the customer has accepted the
contract. After the customer accepts the quote, it’s transformed into a solution quotation in SAP S/4HANA.
The confirmed solution quotation triggers order fulfillments, separated into physical, subscription, and service
contracts.

SAP Billing and Revenue Innovation Management Integration

10 PUBLIC Quote-to-Cash Context
4 System Requirements

The system requirements for a successful configuration:

1. SAP Billing Revenue and Innovation Management – minimum version 2021 FPS1 release
2. SAP CPQ
3. SAP Business Technology Platform
1. SAP Cloud Integration
2. SAP Variant Configuration and Pricing
3. SAP Master Data Integration
4. SAP Event Mesh

 Note

Contract lifecycle management is supported from 2021 FPS00 onwards.

SAP Billing and Revenue Innovation Management Integration

System Requirements PUBLIC 11
5 Prerequisites

There are some general prerequisites that need to be fulfilled so that users could integrate SAP CPQ and SAP
Billing and Revenue Innovation Management.

• Contact the Network Security team in order to prepare the network environment across different systems
and to set its security aspects.
• Quote 2.0 should be enabled in the SAP CPQ tenant.

 Note

It is important to note that this integration is not supported for Quote 1.0.

• The application parameter “Allowed origins for the CORS filter” needs to be configured in SAP CPQ. When
one or more domains are entered in this field, only the API calls originating from those domains are
allowed.
• To integrate SAP CPQ with other applications, if the above parameter is not set to *, it is necessary to fill
out the field with both the URL of your tenant, and the URLs of the integrated applications to enable API
communication. Values are separated with a “;”.
• SAP CPQ and SAP Billing and Revenue Innovation Management need to be synchronized in terms of
product master, business partners and markets (SAP S/4HANA) via SAP Cloud Integration. Products that
have not been replicated from SAP Billing and Revenue Innovation Management, but created directly in
SAP CPQ, are not replicated in Integration flow which creates SAP S/4HANA Solution Quote from SAP
CPQ Quote. Therefore, you must set up at least the products and business partner replication from SAP
Billing and Revenue Innovation Management to SAP CPQ.

 Note

Markets are not replicated so they need to be created manually.

It is important that all four systems are fully integrated.

• SAP CPQ instance

• SAP S/4HANA with SAP Billing Revenue and Innovation Management solution
• SAP BTP Services
• SAP Cloud Integration tenant: the SAP Cloud Integration Runtime URL is included in the SAP Cloud
Integration provisioning mail. For example: https://<YourTenant>-iflmap.hana.ondemand.com
• SAP Variant Configuration and Pricing instance: ensure that your SAP Variant Configuration and
Pricing instance is integrated with SAP S/4 HANA and that configured products are replicated
between the two systems
• SAP Event Mesh
• SAP Master Data Integration

 Note

The setup must be completed in the following order:

1. Business Partner Master Data

First setup SAP S/4HANA, MDI, CPI, and then setupSAP CPQ

SAP Billing and Revenue Innovation Management Integration

12 PUBLIC Prerequisites
 2. Product Master Data
First setup SAP S/4HANA, CPI, and then setup SAP CPQ
3. Quote Replication
First setup SAP S/4HANA, CPI, CPS, and then setup SAP CPQ

SAP Billing and Revenue Innovation Management Integration

Prerequisites PUBLIC 13
6 Configuration in SAP CPQ

This chapter describes the configuration that needs to be done and settings that need to be checked prior to
configuration in SAP CPQ system to integrate it with SAP Billing and Revenue Innovation Management.

6.1 Create Communication User

A communication user needs to be created in SAP CPQ System, which will be used in SAP Cloud Integration for
basic authentication to SAP CPQ.

Procedure

1. Log on to the SAP CPQ system using an Administrator User.

2. Choose Setup in the left menu bar and choose Setup.
3. In left navigation bar, select Users under Users.
4. Choose Add New User.
5. Enter the First Name, Last Name and Email for Communication User under General tab.
6. Enter Username, for example <COM_USER_SAP CPQINT>.
7. Choose User Type, for example as <Sales>.

 Note

Whatever user type is selected, make sure that the options Show prices and Allow adding incomplete
items are enabled for that user type in Setup Users User Types your user type .

8. Set the Administrator flag.

9. Select Company.
10. Choose Save.

 Note

After creating the user, the communication user will receive 2 E-Mails: One for the SAP CPQ user
registration and one for the SAP CPQ password creation. Login to SAP CPQ system using the above
username and reset the password and same password is to be used in SAP Cloud Integration at the time of
Creating User Credentials.

SAP Billing and Revenue Innovation Management Integration

14 PUBLIC Configuration in SAP CPQ
6.1.1 Client Certificate Authentication in SAP CPQ

1. Log on to the SAP CPQ system using an administrator user.

2. Choose Setup in the left menu bar and choose Setup.
3. In left navigation bar, select Security Certificate Management .
4. Select User Certificates tab and under it turn on Enable User Certificates.
1. Click New Certificate. A pop-up with the options User and Upload CER file will appear.
2. Enter the Communication User (created in Create Communication User [page 14]) and upload the *.cer
file.
This certificate will be used by SAP Cloud Integration to communicate with the SAP CPQ Token API to
retrieve the certificate access token.

6.2 Enable the Integration with SAP Billing and Revenue

Innovation Management

1. Log in to your SAP CPQ system using an Administration user.

2. Choose Setup in left menu bar and choose Setup.
3. Select Providers under Providers in left navigation bar.
4. From the Available Providers, select SAP tile.
5. In the Available SAP Providers page, choose SAP Billing and Revenue Innovation Management tile.
6. Turn on Enable Billing and Revenue Innovation Management Integration.

In the General tab, you need to fill out the following fields:

• Authentication mode –Basic authentication should be selected, if not selected by default.

• Username – username of the SAP Cloud Integration integration user.
• Password – password of the SAP Cloud Integration integration user.
• Contract Header iFlow URL – Endpoint to the Read Subscription contract header from SAP Billing and
Revenue Innovation Management integration flow. The integration flow reads the header-level details from
the contract in SAP S/4HANA and displays them in the Asset table on the quote.
• Contract Item iFlow URL –Endpoint to the Configuration for integration flow “Read Subscription contract
items from SAP Billing and Revenue Innovation Management” [page 131] integration flow. The integration
flow reads the item-level details from the contract in SAP S/4HANA and displays them in the Asset table
on the quote.
• Check Allowable Changes iFlow URL –Endpoint to the Configuration for integration flow “Read Change
Process Groups for Quote from SAP Billing and Revenue Innovation Management” [page 132] integration
flow. The integration flow gets the available change process groups for the asset on the quote.
• Change Process iFlow URL –Endpoint to the Configuration for integration flow “Read Change Process
for Quote from SAP Billing and Revenue Innovation Management” [page 133] integration flow. The
integration flow checks for the change processes available in SAP S/4HANA after administrators initiate
the synchronization of the change processes in the Setup, or initiate the adding of a change process.
• Change Process Group iFlow URL –Endpoint to the Configuration for integration flow “Read allowed Change
Process Groups for Subscription Contract Item from SAP Billing and Revenue Innovation Management”
[page 134] integration flow. The integration flow checks for the change process groups available in SAP

SAP Billing and Revenue Innovation Management Integration

Configuration in SAP CPQ PUBLIC 15
 S/4HANA after administrators initiate the synchronization of the change processes in the Setup, or initiate
the adding of a change process.
• Preselected partner function – the quote must contain an involved party with this partner function and a
business partner. The system then uses the assigned business partner to filter the contracts from SAP
S/4HANA and display only the contracts related to that business partner when creating a new asset.

The following is automatically set up when the integration is enabled:

• The Billing Cycle, Contract Duration and Contract Extension Periodsystem attributes are created in the
system to store values coming from SAP Billing and Revenue Innovation Management Material Master.
• Quote layout specifically designed for subscription business scenario is selected and it will be applied to all
new quotes. The layout for subscription quote item contains the following fields:
• Contract Start Date - the same as quote effective date. When the contract start date is changed, the
contract end date changes automatically based on the value of Contract Duration.
• Contract End Date - calculated from Contract Start date and Contract Duration. Change of Contract End
Date will not impact Contract Start Date and Contract Duration values.
• Billing Cycle – stores the value of Billing Cycle attribute selected in configurator. When Billing
Cycle item field value is changes, the system reconfigures the product and executes update item
calculations.
• Contract Duration - stores the value of Contract Duration attribute selected in configurator. When
Contract Duration item field value is changed, the system reconfigures the product and executes
update item calculations. When the contract end date is changed, the values won’t propagate back to
the contract duration (the value of the Contract Duration attribute changes only if manually changed).
This attribute has two main purposes:
• To drive the pricing – for example, Recurring List Price is lower if the contract duration is 24
months instead of 12 months.
• For the system to calculate the contract end date.
• Estimated Total Contract Value - Recurring Extended Amount * Contract Duration. The estimated total
amount that the client will pay for the time between contract start and end date.
• Cancellation Request Date - date when a contract item is cancelled in SAP CPQ.
• Cancellation Reason - reason why the contract item is being cancelled. This is a descriptive information
in SAP CPQ and it should be copied from SAP S/4HANA.

If users change the contract end date so that the contract duration lasts for a certain number of months,
or years, plus the days that are not a full month, to calculate the estimated total contract value, the system
multiples the recurring extended amount by the number of months. The number of months is calculated by
dividing the total number of days by the days in a month. The number of days in a month is either fixed and
defined by the administrator, or the system will take the actual number of days in months. This is defined in the
Providers page.

Quote layout specifically designed for Service Contract business scenario is selected and it will be applied to all
new quotes. The new layout for service contract quote item contains the following fields:

• Contract Start Date - the same as quote effective date. When the contract start date is changed, the
contract end date changes automatically based on the value of Contract Duration.
• Contract End Date - calculated from Contract Start date and Contract Duration. Change of Contract End
Date will not impact Contract Start Date and Contract Duration values.
• Estimated Total Contract Value - Recurring Extended Amount * Contract Duration. The estimated total
amount that the client will pay for the time between contract start and end date.

SAP Billing and Revenue Innovation Management Integration

16 PUBLIC Configuration in SAP CPQ
 • Service Profile – This is a list of value-codes that defines what is the time window in which a customer gets
service support for a particular service contract.
• Response Profile – This is a list of value-codes that defines what is the time window in which our client
needs to respond to his customer when he reports an issue.
• Service Contract Duration - User picks End Date to determine service contract validity.
• Settlement Period - This list determines frequency of a bill generation for the particular Service Contact
product.
• Billing Date - This is a list of value-codes that defines at which day bill will be generated for particular
service contract

 Note

After a product is added to a quote and changed its default contract start and contract end dates, if
you configure the product again, the dates will reset to the default values. Therefore, make sure you
first configure the product and then manage the pricing on the quote. Alternatively, if you change the
configuration of the product that’s already on the quote, you should readjust the dates after each time the
configuration is changed.

6.3 Enable the Integration with SAP Cloud Integration

1. Login to your SAP CPQ system using an Administrator User.

2. Choose Setup in left menu bar and choose Setup.
3. Select the SAP Integrations under the Providers in left navigation bar.
4. From the Available SAP Providers, select the Mandatory Settings tile.
5. Turn on the Enable SAP Cloud Integration.
6. In the General settings, define the following:
• Enter a value for the Transaction Label ID, which will be displayed on the Quote page. The default value
is "Sales Order Id". For more information, see Dynamic Label for the Target Transaction ID.
• Turn on the Send customers along with quote payload.
• The actual number of days in months and years – the system uses the actual number of days and years
as in the calendar when selected.
• Fixed number of days – the system uses the fixed number of days in months and years, when selected.

 Note

The number of days is used to calculate the total number of months and years in a contract duration.
For example, to calculate the total contract value for a contract duration of 12 months and 10 days,
the system divides the total number of days by the number of days in a month (as defined here) and
multiplies it by the monthly rate.

7. Choose the Save.

SAP Billing and Revenue Innovation Management Integration

Configuration in SAP CPQ PUBLIC 17
6.4 Enable the Integration with SAP ERP

To manage the pricing procedures, enable the SAP ERP integration in SAP CPQ.

1. Login to your SAP CPQ system using an Administrator User.

2. Choose Setup in left menu bar and choose Setup.
3. Select Providers under Providers in left navigation bar.
4. From the Available Providers, select SAP tile.
5. From the Available SAP Providers, select SAP ERP tile.
6. Turn on Enable Integration toggle.
7. Choose Save.

6.5 Enable the Integration with SAP Variant Configuration

and Pricing

The integration with SAP Variant Configuration and Pricing is to be enabled as described in the documentation.

6.6 SAP General Attribute Mappings

After connecting SAP CPQ to SAP Variant Configuration and pricing, General attributes are to be mapped. For
more information refer to General Attribute Mappings.

1. Login to your SAP CPQ system using an Administrator User.

2. Choose Setup in left menu bar and choose Setup.
3. Select the Providers under Providers in left navigation bar.
4. Choose the SAP tile and then choose SAP General Attribute Mappings tile.
5. In the Attributes (with Created Quote) tab, Under the Pricing During Configuration, select the Source of
Pricing Details as Condition Function Or Condition Type.
6. If the Condition Function is selected, Then Maintain Base Price as BASE, Selected Options as VARC.
If the Condition Type is selected, Then Maintain Base Price as BASE, Selected Options as VARC and VASE.
7. Maintain the Service Profile as DSP1 and Response profile as DSP2.
8. Turn on the Automatically Reconfigure Pricing Attributes on Pricing Procedure Change.
9. Configure the same on the Attributes (No Quote) tab.

6.7 Pricing Setup

In both SAP S/4HANA and SAP CPQ, pricing and configuration are handled by separate services.
Consequently, SAP Billing Revenue and Innovation Management products in SAP CPQ can leverage this

SAP Billing and Revenue Innovation Management Integration

18 PUBLIC Configuration in SAP CPQ
versatility and combine the pricing and configuration from the two systems or maintain them both in only
one system.

In SAP CPQ, these products can have the Standard SAP CPQ configuration type, or the Variant configuration
type, in which case configuration is handled by SAP Variant Configuration and Pricing. In addition, the available
pricing types are Pricebook Lookup and Custom Pricing, which are standard SAP CPQ features, as well as
Variant Pricing, in case pricing is handled by SAP Variant Configuration and Pricing.

If you are using SAP CPQ as a centralized location for maintaining prices, you can either maintain prices in
pricebooks or use custom pricing. However, the default configuration and pricing mechanism for SAP Billing
Revenue and Innovation Management products in SAP CPQ is SAP Variant Configuration and Pricing, in which
case products have the Variant configuration type and Variant Pricing selected.

 Note

To calculate Estimated Total Contract Value & Estimated Billing Period Value when Custom Pricing or
Pricebook is used, then Use Recurring Periods must be TRUE under General Parameter tab in Setup /
General / Application Parameters.

Supported Configuration and Pricing Configuration: SAP CPQ Configuration: SAP Variant Configura-
Scenarios
tion and Pricing
(configuration type: Standard)
(configuration type: Variant)

Pricing: SAP CPQ Supported Supported

(pricing type: Custom Pricing/

Pricebook Lookup)

Pricing: SAP Variant Configuration and Not Supported (except for subscription Supported (Default)
products)
Pricing

(pricing type: Variant Pricing)

When SAP CPQ is used as the configuration engine, one of the standard SAP CPQ pricing types should
be used. This is because SAP CPQ configuration doesn’t have a concept of variant conditions and variant
condition keys, and consequently, if SAP CPQ configuration is selected, configuration-related surcharges can’t
be calculated in SAP Variant Configuration and Pricing. In this scenario, SAP Variant Configuration and Pricing
can only return the base price, which functions only if product doesn’t have surcharges related to product
attribute selection.

However, for subscription products, it is allowed to combine SAP CPQ Standard configuration and Variant
Pricing, because subscription products can’t be simple products in SAP CPQ, as they have the Contract
Duration and Billing Cycle attributes by default. If subscription products are simple on the SAP S/4HANA side,
the configuration type for subscription products should be Standard, and the pricing type can be either one
of the standard SAP CPQ types or Variant Pricing. However, if the configuration type is Variant, there are no
limitations in respect to the pricing type.

If there are pricing conditions on the product and you want to send the prices from the SAP CPQ quote to SAP
S/4HANA when an order is placed, you need to define pricing procedure mappings in SAP CPQ.

SAP Billing and Revenue Innovation Management Integration

Configuration in SAP CPQ PUBLIC 19
6.7.1 Create Markets

A market is created in SAP CPQ against every Sales Organization of SAP Billing Revenue and Innovation
Management system. This will help in pricing determination in Quote in SAP CPQ system.

Procedure

1. Login to your SAP CPQ system using an Administrator User.

2. Choose Setup in left menu bar and choose Setup.
3. In left navigation bar, select Markets under Pricing/Calculations.
4. Choose Add new button.
5. Enter for example, <Sales Organization of SAP Billing Revenue and Innovation
Management system> in Market Code field.
6. Enter for example, <Sales Org US> in Market Name field.
7. Select for example, <USD> as Currency.
8. Enter Market Factor field as 1.
9. Choose Save.
10. In left Navigation bar, select Market Visibility under Pricing/Calculations.
11. Choose Add New button.
12. Select for example, <Sales Org US> (Market Name created above) under Market Name in Step 2
section.
13. In Step 3 section, enter Visibility Condition as 1.
14. Choose Save.

 Note

You can check the Sales Organizations and the assigned currencies in the SAP Billing Revenue and
Innovation Management system under SPRO SAP Reference IMG Enterprise Structure Definition
Sales and Distribution Define, copy, delete, check sales organization .

6.7.2 Create Pricebook

To create a pricebook, you first need to group it under a market, define who sees it and then add entries
(products and prices).

1. In Setup, access Pricing/Calculations and choose Pricebooks.

2. In the Pricebooks tab, select the Market and the list of underlying pricebooks displays.
3. Select Add New Pricebook and a page with the Definition and Entries tabs displays.
4. Define the pricebook name.
5. Select Visible to everyone if you wish everyone to have access to the pricebook.
Alternatively, define advanced or simple visibility conditions to restrict access to the pricebook. If not set
to be visible to everyone, a pricebook must have at least one visibility condition defined so that the system
could trace it and properly include it in the pricebook drop-down list on quotes.

SAP Billing and Revenue Innovation Management Integration

20 PUBLIC Configuration in SAP CPQ
 6. Select the dates in Valid from and Valid until to define when the pricebook is valid.
7. (Optional) Describe the pricebook in Description. Choose Save.
8. Navigate to the Entries tab to add products and their respective prices.

 Note

For more details on creating and managing pricebooks, please consult this page.

 Note

Make sure that the user selects the Default Pricebook (with the distribution channel from SAP S/4HANA)
and the Default Market on the User Page.

6.7.3 Discounting

One of the major functionalities of SAP CPQ is on the fly discounts based on products, product types, product
categories, users and user types.

You can setup discounting in Quote in your SAP CPQ system following below procedure. This chapter is
optional.

Procedure

1. Login to SAP CPQ system using an Administrator User.

2. Choose Setup in left menu bar and choose Setup.
3. In left navigation bar, select Discounts under Pricing/Calculations.
4. Choose Add New button.
5. Choose Select button to maintain USER TYPE as Sales under Step 1 section

 Note

The above selection will allow users with user type ‘Sales’ to give discounts in Sales Quote which we
will be defining in next step. Any condition for discount selection with User, User Type, Product, Product
Type or Category can be created.

6. Maintain Maximum Value for Discount as 10. It will allow Sales User to give maximum of 10 percent
discount. Above 10 percent discount will be subject to approval.
7. Under Step 3 section, enter Condition as 1. Conditions can also be created using scripting languages.
8. Choose Save.

SAP Billing and Revenue Innovation Management Integration

Configuration in SAP CPQ PUBLIC 21
6.7.4 Discounting Priorities

In SAP CPQ, discount to customers can be provided in Quote based on User, User Type, Product, Product Type
or Product Category conditions.

There might be a case with two or more valid conditions. Priority of the conditions is maintained as below. This
chapter is optional.

Procedure

1. Login to SAP CPQ system using an Administrator User.

2. Choose Setup in left menu bar and choose Setup.
3. In left navigation bar, select Discounting Priorities under Pricing/Calculations.
4. Select Rank as 1 for Product to have highest priority.
5. Further select Rank for Product Type as 2, Category as 3, User as 4 and User Type as 5.
6. Choose Save.

6.7.5 Setting SAP S/4HANA Pricing Procedures in SAP CPQ

Pricing procedures are defined in SAP S/4HANA and consist of different pricing conditions. In SAP CPQ, you
can map pricing conditions to quote item or header fields in order to send pricing data from the SAP CPQ
quote to SAP S/4HANA.

Detailed instructions for mapping pricing conditions to quote item or header fields are available in Pricing
Procedures from SAP Variant Configuration and Pricing.

First, you need to remove all SAP CPQ calculations from Calculations on Add/Copy/Delete Item in the Fields,
Calculations, Layout section of the Setup. Standard SAP CPQ calculations can't be combined with calculations
specifically used for pricing condition mapping. Following this step, you need to set the calculations according
to the instructions described in Calculations for Variant Pricing Items.

The following step is to set the correct pricing condition mappings in SAP CPQ so that the correct prices
appear on the quote. All prices are obtained from SAP Variant Configuration and Pricing. Likewise, all
calculations are done in SAP Variant Configuration and Pricing, and they are only mapped in SAP CPQ. An
example procedure which outlines the process of mapping pricing conditions to quote fields and setting them
up is available in Example Procedure for Mapping Pricing Conditions.

Troubleshooting Example

This is an example of an issue which may appear if calculations aren't correctly set or pricing conditions aren't
correctly mapped.

In this example, the prices in the quote field Recurring Extended List Price are calculated the following way:

SAP Billing and Revenue Innovation Management Integration

22 PUBLIC Configuration in SAP CPQ
 • Quantity: 1000 PC
• Price: 8,90€/1000 PC
• Position Total: 1000 * 8,90€ = 8.900,00€

The price is incorrectly calculated here because the standard SAP CPQ calculation Item Recurring Extended
List Price is added to the Calculations on Add/Copy/Delete Item in the Setup, and the price on the quote
was calculated according to this calculation. This is incorrect, as SAP CPQ calculations shouldn't be used in
combination with calculations specifically used for pricing condition mapping, and calculations need to be set
in the way described in Calculations for Variant Pricing Items. In addition to setting the correct calculations, the
appropriate pricing condition needs to be mapped to the field Recurring Extended List Price, as seen here:

Pricing Pricing Fre- Quote Order Item Display

Step Condition Name quency Rate/Value Quote Item Header Type Unit

500 / Periodic Monthly Value Recurring / Subscrip- On

Payment Extended tion
Net List Price

Once the calculations and the conditions are both correctly set, the correct price will be calculated on the
quote.

6.7.6 Set up Calculations on Item Add/Copy/Delete

The list of standard SAP CPQ calculations is expanded with additional calculations when the SAP CPQ - SAP
Billing Revenue and Innovation Management integration is enabled.

Some specific calculations need to be added to the list of calculations that are triggered whenever a
subscription item or a service contract item is added to the quote, as well as when the item is copied and
deleted.

Procedure

1. Login to SAP CPQ system using an Administrator User.

2. Choose Setup in left menu bar and choose Setup.
3. In left navigation bar, select Fields, Calculations, Layout under Quotes.
4. Choose Calculations on Add/Copy/Delete Item in the Fields and Calculations tab.
5. A list of Calculations that are triggered whenever an item is added, copied, or deleted is displayed.
6. Choose Add Calculation which is on right side of the displayed list of calculations.
7. Choose the arrow symbol next to the following calculations to add them to the list:
• Item Estimated Total Contract Value
• Item Estimated Billing Value
• Product Type Estimated Total Contract Value
• Total Estimated Contract Total Value
• Item Contract End Date
8. Choose the arrow symbol next to the following calculations to add them to the list for Service contract
Products:

SAP Billing and Revenue Innovation Management Integration

Configuration in SAP CPQ PUBLIC 23
 • Item Contract End Date Service Contract
• Item Estimated Billing Value Service Contract
9. These calculations are automatically added to the bottom of the existing list of calculations. rearrange
them, according to the business model.
10. Choose Save.

6.7.7 Set up Calculations on Field Value Changes

Some existing and new quote fields need to be set up in such a way that whenever their value is changed,
a specific set of calculation is triggered (calculations that affect subscription products and service contract
products).

Procedure

1. Login to SAP CPQ system using an Administrator User.

2. Choose Setup in left menu bar and choose Setup.
3. In left navigation bar, select Fields, Calculations, Layout under Quotes.
4. Expand MainItem section.
5. Add the calculations to fields as listed below:

Field Calculations

Recurring Extended amount Item Contract End Date

Item Contract End Date Service Contract

Item Estimated Billing Value

Item Estimated Billing Value Service

Contract

Item Estimated Total Contract Value

Product Type Estimated Total Contract

Value

Total Estimated Total Contract Value

SAP Billing and Revenue Innovation Management Integration

24 PUBLIC Configuration in SAP CPQ
 Field Calculations

Recurring Discount percent Item Contract End Date

Item Contract End Date Service Contract

Item Estimated Billing Value

Item Estimated Billing Value Service

Contract

Item Estimated Total Contract Value

Product Type Estimated Total Contract

Value

Total Estimated Total Contract Value

Recurring Discount amount Item Contract End Date

Item Contract End Date Service Contract

Item Estimated Billing Value

Item Estimated Billing Value Service

Contract

Item Estimated Total Contract Value

Product Type Estimated Total Contract

Value

Total Estimated Total Contract Value

Quantity Item Contract End Date

Item Contract End Date Service Contract

Item Estimated Billing Value

Item Estimated Billing Value Service

Contract

Item Estimated Total Contract Value

Product Type Estimated Total Contract

Value

Total Estimated Total Contract Value

SAP Billing and Revenue Innovation Management Integration

Configuration in SAP CPQ PUBLIC 25
 Field Calculations

Contract Start Date Item Contract End Date

Item Contract End Date Service Contract

Item Estimated Billing Value

Item Estimated Billing Value Service

Contract

Item Estimated Total Contract Value

Product Type Estimated Total Contract

Value

Total Estimated Total Contract Value

Contract End Date Item Estimated Billing Value

Item Estimated Billing Value Service

Contract

Item Estimated Total Contract Value

Product Type Estimated Total Contract

Value

Total Estimated Total Contract Value

Contract Change Activation Date Item Estimated Total Contract Value

Product Type Estimated Total Contract

Value

Total Estimated Total Contract Value

These calculations are automatically added to the bottom of the existing list of calculations. rearrange
them, according to the business model.

6. Choose Save.

6.7.8 Rounding Setup

Rounding in SAP CPQ differs from rounding in SAP S/4HANA. To ensure that quote item values from SAP
CPQ are rounded properly, the best practice is to define the default rounding that is applied to all quote item
columns.

1. Log in to SAP CPQ system as an administrator.

2. Choose Setup in left menu bar and choose Setup.
3. In the left navigation bar, select Rounding Setup under Pricing/Calculations.
The list of existing rounding rules displays.
4. Choose Edit for Default setup.
Column name is disabled, and Default is displayed.

SAP Billing and Revenue Innovation Management Integration

26 PUBLIC Configuration in SAP CPQ
 5. Enter Number of Decimals in Calculations.
6. Enter Number of Decimals when Rounding.

 Note

For the rounding to be properly transferred to SAP S/4HANA via the API, make sure to enter both the
number of decimals for calculations and the number of decimals for rounding and make sure to enter
the same number.

Since SAP S/4HANA uses different number of decimals for different currencies, you should enter a
high number of decimals in these fields in SAP CPQ, higher than the number of decimals in SAP
S/4HANA. This way you ensure that the values can be properly rounded in SAP S/4HANA.

7. Choose Save.
The rounding is now applied.

If you are not applying default rounding and you need to define rounding for each quote item field, make sure
that you not only set up rounding for that field but also for all other fields that affect its value.

6.8 Configure Workflow in SAP CPQ

The default status of the quote is Preparing and changes to Order Confirmation Pending when the Place Order
action is executed. The error handling requires the setup of additional quote status.

From status Preparing, the status should change to Order Confirmation Pending if the Place Order action is
executed. From Order Confirmation Pending, there are two options:

1. If SAP Billing Revenue and Innovation Management returns an error, the quote goes to status Order
Failed. From here, by executing the Place Order action, the user can go back to status Order Confirmation
Pending. This status allows to make necessary adjustments and execute Place Order action again
2. If SAP Billing Revenue and Innovation Management does not return an error, the quote goes to status
Order Placed.

When the SAP ERP integration is enabled in SAP CPQ, the system will automatically make the following
adjustments in the Workflow created.

• Order Confirmation Pending and Order Placed statuses have been created in the system, if they were not
available before.
• The Order Status Update action has been set up to lead from the Order Confirmation Pending status to
Order Placed when the SAP ERP integration is enabled.

Procedure

1. Login to SAP CPQ system using an Administrator User.

2. Choose Setup in left menu bar and choose Setup.
3. In left navigation bar, select Workflow under Workflow/Approval.
4. In the My Quotes tab, in the grid, Left side, vertical statuses are start statuses and Horizontal, top statuses
are target statuses.

SAP Billing and Revenue Innovation Management Integration

Configuration in SAP CPQ PUBLIC 27
5. Find the crossing of Preparing in vertical column and Order Confirmation Pending in horizontal row and
Select it. Scroll to action Place Order and select the checkbox in Selected column.
6. Choose Save.
(This means once, an order is placed, the quote status changes from Preparing to Order Confirmation
Pending)
7. Find the crossing of Order Confirmation Pending in vertical column and Order Placed in horizontal row and
select it. Scroll to action Order Status Update and select the checkbox in Selected column.
8. Choose Save.
9. Find the crossing of Order Failed in vertical column and Order Confirmation Pending in horizontal row and
select it. Scroll to action Place Order and select the checkbox in Selected column.
10. Choose Save.

SAP CPQ Quote is sent via SAP Cloud Integration to SAP Billing Revenue and Innovation Management. The
success or error message from SAP Billing Revenue and Innovation Management are received synchronously
and sent back to SAP CPQ via SAP Cloud Integration. Errors which are returned from SAP Billing Revenue
and Innovation Management are stored in SAP CPQ quote header with a generic error text. A detailed error
description is visible for administrators in the SAP CPQ log. The reason for this is that error messages are
returned from SAP Billing Revenue and Innovation Management in the language the user used for integration.

6.8.1 Enable Workflow Actions and Permissions

The action for creating Sales Order in SAP S/4HANA needs to be enabled in SAP CPQ.

Procedure

1. Login to SAP CPQ system using an Administrator User.

2. Choose Setup in left menu bar and choose Setup.
3. In left navigation bar, select Workflow under Workflow/Approval.
4. In My Quotes tab, find the crossing of Preparing in vertical column and Order Confirmation Pending in
horizontal row and Choose it. Scroll to action Place Order and select the checkbox in Selected column.
5. Choose Save.
6. Find the crossing of Order Confirmation Pending in vertical column and Order Confirmation Pending in
horizontal row and Choose it. Scroll to actions View and History and select the checkboxes in Selected
column.
7. Choose Save.
8. Find the crossing of Order Placed in vertical column and Order Placed in horizontal row and select it. Scroll
to actions View and History and select the checkboxes in Selected column.
9. Choose Save.
10. Find the crossing of Order Failed in vertical column and Order Placed in horizontal row and select it. Scroll
to actions Order Status Update and select the checkboxes in Selected column.
11. Choose Save.

SAP Billing and Revenue Innovation Management Integration

28 PUBLIC Configuration in SAP CPQ
  Note

Copy the same settings from My Quotes to Other Quotes tab as well. To do this, open the Other Quotes tab,
Select My Quotes from the dropdown selection in the Copy from field and choose Copy button.

• Enable the workflow permission as below

• In left navigation bar, select Workflow Permissions under Workflow/Approval.
• Under Action Permissions, search for Place Order action.
• Choose Add button (+), Select the checkbox for the User type Sales.
• Choose Save.
• In the same way, add for all the actions like Edit, History, Order Status Update and Save Quote
under Action Permissions the same user type selected for the communication user.

6.9 Partner Functions

6.9.1 Create Partner Function

To create partner functions in SAP CPQ, follow this procedure.

Partner Functions that are supported in the integration between SAP CPQ and SAP Billing and Revenue
Innovation Management are:

• Sold-To Party (mandatory)

• Ship-To Party
• Bill-To Party
• Payer Party
• Contact Person
• Employee Responsible

6.9.2 Set Sold-To Party to Mandatory

The automatic partner determination for the Sold-To Party in SAP Billing and Revenue Innovation Management
exclusively works during quote creation, not during quote update. Sold-To Party is of particular importance as it
explicitly specifies the quote recipient and is thus mandatory for the creation of a Solution Quotation.

By design, SAP Billing and Revenue Innovation Management does not perform the automatic partner
determination if this field is empty or updated. Therefore, if the quote does not have a Sold-To Party assigned
when the Order Placed action is first placed, there would be no possibility to obtain an error-free Solution

SAP Billing and Revenue Innovation Management Integration

Configuration in SAP CPQ PUBLIC 29
Quotation by assigning a Sold-To Party to the quote and send an update by executing the Place Order action
again.

To avoid this error, it is important to set (at least) Sold-To Party partner function as mandatory in the SAP CPQ
Setup.

Procedure
1. Login to SAP CPQ system using an Administrator User.
2. Choose Setup in left menu bar and choose Setup.
3. In left navigation bar, select Required Fields by Workflow Action under Workflow/Approval.
4. The table shows field names on vertical and Actions on horizontal axis.
5. Check the crossing of Sold-to party and Place Order.
6. Choose Save.

As the Sold-To Party is mandatory, it is useful to display this Partner Function by default for new quote.

Procedure
1. Login to SAP CPQ system using an Administrator User.
2. Choose Setup in left menu bar and choose Setup.
3. In left navigation bar, select Partner Functions under Quotes.
4. Choose Edit for Sold-to party function.
5. Turn on the Show by default on new quotes toggle.
6. Choose Save.

6.9.3 Partner Functions in SAP CPQ quote

The SAP Billing and Revenue Innovation Management system can only deal with one value per Partner
Function. Therefore, the SAP CPQ system must not send more than one Business Partner for each Partner
Function.

Procedure
1. Login to SAP CPQ system using an Administrator User.
2. Choose Setup in left menu bar and choose Setup.
3. In left navigation bar, select Partner Functions under Quotes.
4. Choose Edit for Sold- to party, Ship-to party, Bill-to party, Employee Responsible and Payer partner
functions as they should be transferred to SAP Billing and Revenue Innovation Management.
5. Turn on the Can be used only once on quote toggle for each partner function.
6. Choose Save.

 Note

Partner Functions can only be replicated from SAP CPQ to SAP Billing and Revenue Innovation
Management if the Partner Function Key exists in SAP Billing and Revenue Innovation Management and
was entered on the More tab in the integration flow configuration.

SAP Billing and Revenue Innovation Management Integration

30 PUBLIC Configuration in SAP CPQ
6.10 Create Business Partners

To create business partner in SAP CPQ follow procedure on link.

 Note

In SAP CPQ, ID displayed in the field Partner ID on business partner should match the business partner
in SAP Billing and Revenue Innovation Management. Business partner in SAP CPQ should match busines
partner in SAP Billing and Revenue Innovation Management.

6.11 Product Replication Setup

Products: Types and Configuration [page 31]

Maintain Product Types [page 32]

Maintain Product Categories [page 33]

Maintain Billing Cycle [page 33]

Maintain Service Profile [page 34]

Maintain Response Profile [page 35]

Maintain Billing Date [page 35]

Maintain Settlement Period [page 36]

6.11.1 Products: Types and Configuration

The SAP CPQ-SAP Billing and Revenue Innovation Management integration supports simple and configurable
products. Subscription products are mastered in SAP Billing and Revenue Innovation Management and they
arrive via SAP Cloud Integration to SAP CPQ as simple products. Service Contract products are mastered
in SAP S/4HANA and they arrive via SAP Cloud Integration to SAP CPQ as simple products.They are then
added three system attributes (Contract Duration, Billing Cycle and Contract Extension Period) in case
of Subscription products and five system attributes (Service Profile, Response profile,billing date, service
contract duration,settlement period) in case of service contract products. . If more complex configuration
is needed, SAP CPQ or SAP Variant Configuration and Pricing Service attributes are added to the simple
products. When configured items are sent to Solution Quote, separate subscription contracts and service
contracts for each item are created.

Subscription products are replicated from SAP Billing and Revenue Innovation Management into SAP CPQ
using the ImportMaterialsFromERP SOAP API. All products arriving via this API that have the OrderItemType
property with the value Subscription, will automatically be created as configurable products in SAP CPQ.

SAP Billing and Revenue Innovation Management Integration

Configuration in SAP CPQ PUBLIC 31
Additionally, the API payload contains three system attributes Contract Duration. Billing Cycle and Contract
Extension Period which will be assigned/added to product during importmaterial process in SAP CPQ.

Similarly, products that have the OrderItemType property with the value Service Contracts, will automatically
be created as configurable products in SAP CPQ. Additionally, the API payload contains five system attributes,
Service Profile, Response Profile, Billing Date, Service Contract Duration, Settlement Period which will be
added to product during importmaterial process in SAP CPQ

The following are the product details that arrive to SAP CPQ from SAP Billing and Revenue Innovation
Management via the SAP Cloud Integration:

• name
• OrderItemType property with value Subscription or Service Contract. The value of Order Item Type can’t
be changed neither via the API nor in the application
• system ID
• product type
• part number
• unit of measure
• category
• Contract Duration, Billing Cycle and Contract Extension Period attributes with their values (only for
subscription products)

If SAP Variant Configuration is used for product configuration, the attributes (VC characteristics) are
synchronized from SAP Variant Configuration to SAP CPQ via knowledge base synchronization.

 Note

Parent/child (multilevel) subscription configurations mtaintained in SAP Variant Configuration and

Pricing aren't supported in the integration between SAP CPQ and SAP Billing and Revenue Innovation
Management. However, there is a way to use bundling with subscriptions in SAP CPQ. You need to replicate
the back-end product (a dummy product that's discarded later on in the SAP S/4HANA downstream
processes) in SAP CPQ and change the configuration/pricing type to other than Variant (configuration
should be Standard, pricing can be Custom or Pricebook). Change the display type of the product to
a parent/child configuration, then add an SAP CPQ container attribute to that product and reference
synchronized subscription products from that attribute. Synchronized subscription products should have
Variant configuration and pricing. Therefore, when a bundle product is configured, the synchronized
subscription child products will be configured and priced by calling SAP Variant Configuration and Pricing
in the back end. Such products, when added to quote, will reflect in item and subitem structure and
when order is placed, SAP S/4HANA will further discard the main item and take child items and create
subscription contracts out of them.

6.11.2 Maintain Product Types

Follow the below procedure to create Product Type in SAP CPQ. This Product Type is mapped from SAP
Billing and Revenue Innovation Management Material Group (SAP S/4HANA field: MARA-MATKL) in SAP Cloud
Integration middleware. If during product replication a product type does not exist in SAP CPQ, the product
is not replicated, and an error is raised. You have to replicate the product manually, after you maintained the
product type in SAP CPQ.

SAP Billing and Revenue Innovation Management Integration

32 PUBLIC Configuration in SAP CPQ
Procedure
1. Login to SAP CPQ system using an Administrator User.
2. Choose Setup in left menu bar and choose Setup.
3. In left navigation bar, select Product Types under Product Catalog.
4. Choose Add New button.
5. Maintain Product Type Name for example as <Metal Processing> and Product Type Rank, for example
<10>.
6. Choose Save.
7. Choose Add New button.
8. Maintain Product Type Name for example, <Electronics> and Product Type Rank for example <11>.
9. Choose Save.

6.11.3 Maintain Product Categories

In below steps, product catalog is created, which will help user to differentiate the product based on their
category. If product doesn’t have any Product Category, it cannot be replicated. The Product Category is
mapped with SAP Billing and Revenue Innovation Management Product Hierarchy in SAP Cloud Integration
middleware using a value mapping.

 Note

As the category field is mandatory in SAP CPQ, make sure that the hierarchy is maintained for the SAP
Billing and Revenue Innovation Management product (field MARA-PRDHA).

Procedure
1. Login to SAP CPQ system using an Administrator User.
2. Choose Setup in left menu bar and choose Setup.
3. In left navigation bar, select Categories under Product Catalog.
4. Choose Add New button.
5. Maintain the Product Category by giving Category Name for example, <Machines>, Category Description
for example, <Machines>, Rank for example, <10> and check the Active checkbox.
6. Choose Save.
7. Choose Add New button.
8. Maintain the Product Category by giving Category Name for example, <Vehicles>, Category Description
for example, <Vehicles>, Rank for example, <11> and check the Active checkbox.
9. Choose Save.

6.11.4 Maintain Billing Cycle

This step is only required for the replication of subscription products. SAP S/4HANA Sales Products do not
have a Billing Cycle. Billing Cycle attribute is automatically added to the list of global attributes when SAP CPQ

SAP Billing and Revenue Innovation Management Integration

Configuration in SAP CPQ PUBLIC 33
- SAP Billing and Revenue Innovation Management integration is enabled in SAP CPQ. Billing Cycle attribute
values need to be maintained manually. To do that you can follow next steps:

Procedure
1. Login to SAP CPQ system using an Administrator User.
2. Choose Setup in left menu bar and choose Setup.
3. In left navigation bar, select Attributes under Product Catalog.
4. Search in the list of attributes for Billing Cycle.
5. Choose Edit for Billing Cycle.
6. Choose Add Values under Attribute values and add the below details.
7. Enter the Value, description for the billing period for example as <Monthly,End of Month>.
8. Enter the Value Code for example as <0001>. The Value Code must match the Billing Cycle Value from the
SAP Billing and Revenue Innovation Management which is displayed in the Subscription Data section in the
Basic Product Data (Transaction MM03).
9. Billing Period is to be selected from the dropdown for example, <Monthly>.
10. Add the below values in the next line.
11. Enter the Value, description for the billing period for example, <Yearly>.
12. Enter the Value Code for example, <SOMY>. The Value Code must match the Billing Cycle Value from the
SAP Billing and Revenue Innovation Management which is displayed in the Subscription Data section in the
Basic Product Data (Transaction MM03).
13. Billing Period is to be selected from the dropdown for example, <Yearly>.
14. 14. Choose Save.

 Note

If you want to support more than one billing cycle attribute value for particular product in SAP CPQ, then
you have to set up the SAP S/4HANA product with a billing cycle (this is the default one) and a billing cycle
determination rule which allows you to accept the other billing cycle values.

6.11.5 Maintain Service Profile

This step is only required for the replication of Service Contract products. Service Profile attribute is
automatically added to the list of global attributes. Service Profile attribute values need to be maintained
manually. To do that you can follow next steps:

1. Login to SAP CPQ system using an Administrator User.

2. Choose Setup in left menu bar and choose Setup.
3. In left navigation bar, select Attributes under Product Catalog.
4. Search in the list of attributes for Service Profile.
5. Choose Edit for Service Profile.
6. Choose Add Values under Attribute values and add the below details.
7. Enter the Value, for example as < Mo-Fr: 7-17h>
.
8. Enter the Value Code for example as < 5X10>. The Value Code must match the Service Profile of Service
Contract product in S/4HANA.

SAP Billing and Revenue Innovation Management Integration

34 PUBLIC Configuration in SAP CPQ
 9. Choose Save.

6.11.6 Maintain Response Profile

This step is only required for the replication of Service contract products. Response Profile attribute is
automatically added to the list of global attributes when SAP CPQ - SAP Billing Revenue and Innovation
Management integration is enabled in SAP CPQ. Response Profile attribute values need to be maintained
manually. To do that you can follow next steps:

1. Login to SAP CPQ system using an Administrator User.

2. Choose Setup in left menu bar and choose Setup.
3. In left navigation bar, select Attributes under Product Catalog.
4. Search in the list of attributes for Response Profile.
5. Choose Edit for Response Profile.
6. Choose Add Values under Attribute values and add the below details.
7. Enter the Value, for example as < First Level Response Time>
.
8. Enter the Value Code for example as <FIRST>. The Response Profile must match the Response Profile of
Service Contract product in S/4HANA.
9. Choose Save.

6.11.7 Maintain Billing Date

This step is only required for the replication of Service Contract products. Billing Date attribute is automatically
added to the list of global attributes when SAP CPQ - SAP Billing Revenue and Innovation Management
integration is enabled in SAP CPQ. Billing Date attribute values need to be maintained manually. To do that you
can follow next steps:

1. Login to SAP CPQ system using an Administrator User.

2. Choose Setup in left menu bar and choose Setup.
3. In left navigation bar, select Attributes under Product Catalog.
4. Search in the list of attributes for Billing Date.
5. Choose Edit for Billing Date.
6. Choose Add Values under Attribute values and add the below details.
7. Enter the Value, for example as < First of the Month>
.
8. Enter the Value Code for example as <BILL0002>. The Value Code must match the Billing Date of Service
Contract product in S/4HANA.
9. Choose Save.

SAP Billing and Revenue Innovation Management Integration

Configuration in SAP CPQ PUBLIC 35
6.11.8 Maintain Settlement Period

This step is only required for the replication of Service contract products. Settlement Period attribute is
automatically added to the list of global attributes when SAP CPQ - SAP Billing Revenue and Innovation
Management integration is enabled in SAP CPQ. Settlement Period attribute values need to be maintained
manually. To do that you can follow next steps:

1. Login to SAP CPQ system using an Administrator User.

2. Choose Setup in left menu bar and choose Setup.
3. In left navigation bar, select Attributes under Product Catalog.
4. Search in the list of attributes for Settlement Period.
5. Choose Edit for Settlement Period.
6. Choose Add Values under Attribute values and add the below details.
7. Enter the Value, description for the billing period for example <Monthly>
.
8. Enter the Value Code for example as <BILL0001>. The Value Code must match the Settlement Period of
Service Contract product in S/4HANA.
9. Billing Period is to be selected from the dropdown for example, Monthly.
10. Choose Save.

6.12 Enable Quote and Item Comments

Users of SAP CPQ and SAP Billing and Revenue Innovation Management have the possibility to exchange
comments, both global quote level comments and item level comments. To make this possible for users, you
need to make the fields visible on the quote and to give users the editing permissions.

6.12.1 Make the Fields Editable

1. Login to your SAP CPQ system using an Administrator User.

2. Choose Setup in left menu bar and choose Setup.
3. Select Fields, Calculations, Layout under Quotes in left navigation bar.
4. Go to Field Editability tab.
5. Under Select Permission Group, expand for example, <User Types> and select for example,<Sales>.
6. Under Select Quote Status select for example,<Preparing>
7. Check the checkboxes under Selected fields are editable.
(The above steps are followed to delimit which users have the rights to post comments by selecting their
company, permission group, etc. and then Selecting which quote status is the comment editable.
For example:
• User Description – item-level comment, should be selected for both main and line items.
• Cart Comment – global quote-level comment)

SAP Billing and Revenue Innovation Management Integration

36 PUBLIC Configuration in SAP CPQ
 8. 8. Choose Save.

6.12.2 Make the Fields Visible on Quotes

1. Login to your SAP CPQ system using an Administrator User.

2. Choose Setup in left menu bar and choose Setup.
3. Select Fields, Calculations, Layout under Quotes in left navigation bar.
4. Go to Layout Permissions tab.
5. Under Select Permission Group, expand for example, <User Types> and select for example,<Sales>.
6. Under Select Layout Items select for example, <Columns> or for example, <Sections> or any
subcategories under each of them.
(The above steps are done to Delimit, to which users are the fields visible by selecting their company,
permission group, etc)
7. Choose Save.

6.13 Multi-level Products (Bundle and Non-bundle)

The usage of Multi-level subscription product (Bundle and Non-bundle) has been enabled in the integration
between SAP CPQ Quote 2.0 and SAP S/4HANA Solution Quotation.

Bundle Multi-level Product

A Multi-level bundle product is a product with a bundle product as its main item and regular products as its
sub-items (sales, service contract, subscription). A product that has a General Item Category Group Code of
"Bundle" is called a Bundle product. A user can add any type of product (Sales, Subscription, Service Contract)
as a child to a Bundle product.

Bundle Product will not be reflected in any actual transactional documents, such as a Sales Order or
Subscription Contract, from the Solution Quotation.

See example in the, SAP S/4HANA Bundle Multi-Level Product [page 177]

Flow of Bundle Multi-level Product From SAP S/4HANA to SAP CPQ

• The Bundle Parent Product must be created with the correct "General item category group," which is
meant for Bundles in SAP S/4HANA.
• Children of types Sales, Service contracts, and Subscriptions can be added to this Bundle Product. A
Bundle Multi-level Product is created in SAP S/4HANA. For more details, follow the steps mentioned in the
Master Data Creation [page 142] section.
• Once the Multi-level product bundle is created in SAP S/4HANA, replicate the product from SAP S/4HANA
to SAP CPQ.
• In the value mapping, “Value Mapping for SAP CPQ integration with SAP Billing and Revenue Innovation
Management” the Customer has to configure the value mapping Item Category as Bundle. See Bundle
Item Category [page 141] for more details. This will identify if a product is a Bundle Product and will be
mapped accordingly in the Quote iflow.

SAP Billing and Revenue Innovation Management Integration

Configuration in SAP CPQ PUBLIC 37
• A new field, General item category group, has been introduced in SAP CPQ to store this information. The
product will be replicated to SAP CPQ along with the General item category group information.

Non-bundle Multi-level Product

Multi-level Product contains multiple levels of components and sub-components, which are associated using
BOM explosion. In this product, there will not be any bundle product maintained as a parent or as a child.

Overview of Multi-level product supported in SAP CPQ-BRIM integration:

Order Item Type Bundle Non-bundle

Subscription Yes Yes

Service Contract Yes (Simple) No

Sales Yes (Simple) No

Bundle Products Supported Non-bundle Products Supported

Subscription Multi-level children are sup- Subscription Multi-level dependent config-

ported for SAP S/4HANA uration is supported
Bundle parent. Bundle sub-
scription products must be of
type "Sales order (SET)" in
variant configuration profile.

Service Contract For a Bundle Parent, only Service Contract Multi-level is not supported
nonconfigurable and single-
level service contract chil-
dren are supported. Service
contract Multi-level children
for a Bundle Parent are not
supported due to limitations
in the SAP S/4HANA Solu-
tion Quotation API.

Sales For a Bundle Parent, only Sales Multi-level is not supported

nonconfigurable and single-
level sales child types are
supported. Sales Multi-level
child for a Bundle Parent is
not supported due to a limi-
tation in the SAP S/4HANA
Solution Quotation API.

 Note

In a Multi-level bundle product structure, bundle products must not be placed between Non-bundle
products.

SAP Billing and Revenue Innovation Management Integration

38 PUBLIC Configuration in SAP CPQ
6.14 Change Processes and Renewals

It is possible to make changes to existing contracts in SAP Billing and Revenue Innovation Management from
SAP CPQ.

After a quote is created, the customer may decide after some time to change the quantity of an item, cancel
an item that is already in the quote, or renew a subscription by extending the contract duration. In such a
scenario, a sales representative in SAP CPQ finds the contract with the items that are to be updated, cancelled,
or renewed (contracts are located in SAP S/4HANA, they are not replicated in SAP CPQ), and adds the items
to SAP CPQ as assets. The sales representative then applies the needed change process group (for example, to
renew a contract item, they would apply a change process group with the EXTENSION change process) to the
asset which adds it to quote items. Eventually, they can update the item based on the customer’s wishes (for
example, extend contract duration for two years).

 Note

To be able to use these features on your tenant, please contact the SAP CPQ Support team to enable the
features.

Additionally, access rights administrators need to enable access rights for the Assets Table Management
and Change Processes sections as explained in Assign Access Rights for Setup Sections and Entities.
Otherwise, the sections won’t be visible in the Setup.

 Note

Take a look at the list of limitations for the change processes and renewals.

6.14.1 Add Assets Table to Quote Layout

In the Assets table users manage assets that are retrieved from the SAP Billing and Revenue Innovation
Management contracts. Administrators need to add the table to the quote layout and set up the workflow for
users to be able to use the table on the quote.

1. Log into SAP CPQ system using an Administrator User.

2. Choose Setup in left menu bar and choose Setup.
3. In left navigation bar, select Fields, Calculations, Layout under Quotes.
4. Go to the Layout tab.
5. Choose Add Sections.
A modal with a list of available sections is displayed.
6. Select Assets.
7. Choose Add Selected.
The section is added to the bottom of the page. Drag and drop it to the desired position.
8. Click Save.
The Assets table is now available on quotes.

SAP Billing and Revenue Innovation Management Integration

Configuration in SAP CPQ PUBLIC 39
6.14.2 Set up Workflow

1. Log into SAP CPQ system using an Administrator User.

2. Choose Setup in left menu bar and choose Setup.
3. In left navigation bar, select Workflow under Workflow/Approval.
4. In My Quotes tab, find the crossing of Preparing in vertical column and Preparing in horizontal row and
choose it.
5. Find the action Add asset to quote items and select the checkbox in Selected column.
6. 6. Find the following crossings and enable the actions as explained:
• Crossing of Order Confirmation Pending and Order Failed – action Creating Order Failed.
• Crossing of Order Confirmation Pending and Order Confirmation Pending – action Update Quote
Change Contract Processing Status.
• Crossing of Order Confirmation Pending and Pending Contract Change Processing – action Get Status
of Placed Order.
• Crossing of Order Confirmation Pending and Order Placed – action Order Status Update.
• Crossing of Pending Contract Change Processing and Order Failed – action Creating Order Failed.
• Crossing of Pending Contract Change Processing and Pending Contract Change Processing – action
Update Quote Change Contract Processing Status.
• Crossing of Pending Contract Change Processing and Order Placed – action Order Status Update.
7. Choose Save.
You have enabled the action for adding assets from the Assets table to quote items.

Enable the workflow permission as explained below:

1. In left navigation bar, select Workflow Permissions under Workflow/Approval.

2. Under Action Permissions, search for each action mentioned above.
3. Choose Add button (+) and select the checkbox for the user type of the communication user.
4. Repeat this for each action.
5. Choose Save
.

6.14.3 Add Asset Table Column

You can define which properties of the contract items coming from SAP Billing and Revenue Innovation
Management will be visible to users in the Assets table. One column in the Assets table displays one SAP Billing
and Revenue Innovation Management item property.

1. In Setup, navigate to Quotes and then Assets Table Management.

The list of existing asset columns is displayed.
2. The Change Process Group column is listed by default, and you can’t edit or remove it. This column
contains the available change process groups.
3. Choose Add new column.
4. Enter the Asset label.
The asset name and translation key are automatically generated.
5. Select a field in the External property field.

SAP Billing and Revenue Innovation Management Integration

40 PUBLIC Configuration in SAP CPQ
 This list contains contract header and item related fields from SAP Billing and Revenue Innovation
Management.
The type is automatically populated depending on the selected property.
Rank is automatically defined and can be edited only if you access Rank from the list of all assets.

 Note

There are some required properties that a contract item must contain so that it’s possible to add it
to the Assets table. We advise you to create columns for the required properties, so users have an
overview of the data in the table:
• Item/SubscrpnContrItmEndDateTime
• Item/SubscriptionContractExternalId
• Item/SubscriptionContractId
• Item/ SubscriptionContractItemId
• Item/Product
• Item/Quantity
• Item/SubscrpnContrItmStartDateTime
• Item/ SubscriptionContractDuration
• Item/SubscriptionContractDurationUnit
• Item/CaBillgCycle

6. In the Asset Table Management ranking dialog, the ContractId is a mandatory column, hence the rank must
be set to 1 and any changes to the rank should not be allowed.

6.14.4 Add a Change Process

Change processes are created and maintained in SAP Billing and Revenue Innovation Management and in SAP
CPQ they tell the system which fields should be editable when the asset is moved to quote items. Additionally,
based on the selected change process, the sales representative knows which changes are applied on the quote
later when the quote is converted into a change order.

One change process can belong to multiple change process groups. On the quote, users select a change
process group to be applied to the asset. Consequently, all change processes pertaining to the selected group
will be applied to the asset.

Additional Settings for Change Process Groups for New Contract, Co-Term, and Swap can be set.

The SAP CPQ Change Process Group allows customers to add relevant SAP CPQ Change Process group names.
This will be reflected in the Change Process Group column in the SAP CPQ Quote Assets section.

New Contract refers to applying changes made in existing contract to reflect in a new contractual document.
Existing contract will get canceled and reference to new contract is created in SAP Billing and Revenue
Innovation Management.

Prerequisite for New Contract: It can be selected for the change process group if it contains the change process
which is marked for new contract creation. New contract creation is denoted by the Document Flow Strategy
Field with value N in the change process in Subscription Order Management.

Co-Term refers to aligning different assets or manually added subscription products for the same contract end
date.

SAP Billing and Revenue Innovation Management Integration

Configuration in SAP CPQ PUBLIC 41
Prerequisite for Co-Term: You can select co-term in the change process group if it contains the change process
EXTENSION in Subscription Order Management.

Swap refers to swapping asset in a contract document with a manually added Subscription Product. New
Contract and Co-Term settings cannot be selected with the Swap setting.

Prerequiste for Swap: It can be selected for the change process group if it contains the change process
PROD_CHANGE in Subscription Order Management.

1. In Setup, navigate to Quotes and choose Change Processes.

The list of existing change processes is displayed.
Each entry contains the change process ID and the change process groups the change process belongs to.
2. Choose Synchronize in the change process groups.
Since the change processes available here are retrieved from SAP Billing and Revenue Innovation
Management, choosing the Synchronize button updates the change processes based on the changes made
on the SAP Billing and Revenue Innovation Management side.
3. For the selected change process group, the relevant Additional Settings of New Contract, Co-Term, Swap
can be set.
4. Navigate to change processes and choose Add Change Process. A modal window is displayed.
5. Use the filtering option to find the change process.
If you add a change process that is not supported and a change process without a change process group,
they will not be available for selection on the quote.
6. Choose Add in the Actions column. The change process is now added to SAP CPQ.
7. Choose Edit in the Actions column next to the change process that you’ve just added. A modal window
displays.
8. Select the fields that will be editable on the quote item after the change process is applied on the asset.
9. Enable the Make item editable toggle.
After users apply a change process to an asset and add it to the quote as a quote item, they will be able to
change the configuration of the item.

In the Assets table, when users open the dropdown to select a change process group, the system checks which
change process groups are available for the contract item in SAP Billing and Revenue Innovation Management
and lists those groups, regardless of which change processes are added in the Setup in SAP CPQ. After the
asset is moved to quote items, the system then checks which change processes from the selected change
process group are set up in SAP CPQ and makes editable all the fields that pertain to those change processes
(assuming that they are made editable in Setup Quotes Fields, Calculations, Layout ). Therefore, it is
important to align the change processes in SAP CPQ with what exists in SAP Billing and Revenue Innovation
Management.

6.14.5 Cancellation Setup

To enable users to cancel a contract item, you need to set up the cancellation process. The prerequsite for the
cancellation setup is that the CANCEL change process is added.

1. Navigate to Setup, choose SAP Integrations. Select SAP Billing Revenue Innovation Management.
2. Go to the Cancellation tab.
3. Choose Add New Cancellation.A modal window displays.

SAP Billing and Revenue Innovation Management Integration

42 PUBLIC Configuration in SAP CPQ
 4. Fill out the following fields:
• Description – the reason for cancellation. This description is available on the quote in the Cancellation
Reason field in quote items.
• Cancellation Party – descriptive information in SAP CPQ, should be copied from SAP S/4HANA.
• Cancellation Reason – descriptive information in SAP CPQ, should be copied from SAP S/4HANA.
• Cancellation Procedure - descriptive information in SAP CPQ, should be copied from SAP S/4HANA.
The cancellation process is now added, and it will be available in the Assets table in the dropdown list with
other change processes.

6.14.6 Make the Cancellation Fields Editable

1. Login to SAP CPQ system using an Administrator User.

2. Choose Setup in left menu bar and choose Setup.
3. In left navigation bar, select Fields, Calculations, Layout under Quotes.
4. Go to the Field Editability tab.
5. Select the permission group in the first column and the quote status in the second column.
6. In the third column, expand MainItem and select the Cancellation Request Date and Cancellation Reason.
7. Choose Save.
These two fields are now editable on quote items.

 Note

Although you have enabled the editability for the Cancellation Request Date and Cancellation Reason fields
for all quote items, they will be editable only for items created out of assets and only when the change
group with the cancellation process is selected. For other quote items, the fields will be empty without the
possibility to update them.

6.14.7 Autorenewals

In SAP S/4HANA, it is possible to indicate if a subscription item is going to be automatically renewed after the
contract expires. This information is also stored in SAP CPQ when the product is replicated, specifically in the
Auto Renewal Indicator field in product administration. The field is disabled, can’t be edited in SAP CPQ, and it
has these values:

• No, Selection can be changed – the Contract Auto Renewal Indicator field on the quote is not selected when
the product is added to quote, but users can select it.
• Set to Yes, Selection can be changed - the Contract Auto Renewal Indicator field on the quote is selected
when the product is added to quote, but users can unselect it.
• Not relevant for Auto Renewal – the Contract Auto Renewal Indicator field on the quote is not selected when
the product is added to quote and it’s disabled for selection.
• Set to Yes, Selection cannot be changed - the Contract Auto Renewal Indicator field on the quote is selected
when the product is added to quote but users can’t unselect it.

SAP Billing and Revenue Innovation Management Integration

Configuration in SAP CPQ PUBLIC 43
When the field Contract Auto Renewal Indicator is selected for a quote item, the Contract Extension attribute
becomes editable, and users can select values defined by the administrator in Setup.

6.14.8 Make the Fields Editable

1. Login to SAP CPQ system using an Administrator User.

2. Choose Setup in left menu bar and choose Setup.
3. In left navigation bar, select Fields, Calculations, Layout under Quotes.
4. Go to the Field Editability tab.
5. Select the permission group in the first column and the quote status in the second column.
6. In the third column, expand MainItem and select the Contract Extension field.
7. Choose Save.
The Contract Extension field is now editable on the quote (if the Contract Auto Renewal Indicator field is
selected).

6.14.9 Subscription Contract Renewal Process Capabilities

The subscription contract change processes maintains the life cycle of subscription contracts. The change
processes to edit the subscription contracts have been enhanced. The sales representative in SAP CPQ can
perform the following operations:

• Add a new subscription item to an existing contract or create a new contract document with reference to
an existing contract.
• Swap an existing subscription item with a new subscription item in a subscription contract.
• Merge different subscription contracts into a single subscription contract document after applying the
change process.
• Perform the cross-sell and up-sell operations on the subscription contracts.
• Edit the latest version of the subscription contract.

Related Information

Create New Subscription Contract based on Existing Subscription Contract [page 46]
Swap Subscription Contract [page 48]
Co-Term Subscription Contract [page 50]

SAP Billing and Revenue Innovation Management Integration

44 PUBLIC Configuration in SAP CPQ
6.14.9.1 Dynamic Label for the Target Transaction ID

On the Providers / SAP Integrations / General Mandatory Settings page new field Transaction ID Label is
introduced. The text maintained in this field will be visible on the SAP CPQ Quote page as a label for the
integrated transaction ID.

Currently, the label for the field displaying the target integrated object is the static text “Sales Order ID,”
regardless of whether the object is Solution Quotation, Sales Order, or Solution Order. With this new field,
customers can configure the label according to their business needs. The maximum allowed length of this field
is 120 characters.

Initially, the label on the SAP CPQ Quote page is Sales Order ID. In this new field, the initial text will also be
"Sales Order ID". There will be a Translate transaction ID label button available. The corresponding translation
for the initial text "Sales Order ID" will be available as part of the upgrade.

When this field is saved with an empty value, all the labels in SAP CPQ Quote and translations will be deleted,
and there will not be any label for the transaction ID on the SAP CPQ Quote page.

6.14.9.2 Price Calculations for Change Process

The Contract Change Activation Date will be pre populated as the current date, and the Estimated Total
Contract Value will be determined based on the Contract Change Activation Date. This will be applied to all the
change processes except cancel example (Swap, Change Contract, and so on).

 Note

For any scheduled contract the Contract Change Activation Date will be set as a future contract date.

Cancellation Change Process

When the Cancel Change Process is applied on an Asset and moved the same to the Product section then:

1. The Cancellation Request Date field will be the same as Current Date. This will be considered as immediate
cancellation and the Estimated Total Contract Value will be “0”. The contract end date will be the
cancellation request date.
2. The user can change the Cancellation request Date from Current Date to any future date within the contract
period. This will be considered as future cancellation. The contract end date will be the cancellation request
date. In this case, the contract duration will be from the Contract Change Activation Date to the cancellation
request date, and the Estimated Total Contract Value will be calculated accordingly.
3. For any scheduled contract, Cancellation Request Date will be the same as the Contract Change Activation
Date.

The cancellation request date must be a current or future date only. Past-date cancellations are not allowed.

 Note

Cancellation rules or conditions maintained in SAP S/4 HANA will not be considered in the SAP CPQ
Cancel change process calculation.

Extension Change Process

SAP Billing and Revenue Innovation Management Integration

Configuration in SAP CPQ PUBLIC 45
When the Extension change process is applied the contract end date will be extended according to the Contract
Extension field value and the calculation will be adjusted accordingly.

6.14.9.3 Create New Subscription Contract based on Existing

Subscription Contract

As a sales representative in SAP CPQ, you can apply change processes on single contract and create new
subscription contract document with reference to the existing contract.

Prerequisite

• You can select a new contract for the change process group. For more information, see Add a Change
Process [page 41].
• In Set up Quote Change Processes Change Process Group Tab Change Processes , for the
selected change process group, you must select the values for additional settings as New Contract.

Create a New Contract from a Single Subscription Contract

You can renew or change the existing subscription contract and create a new contract with reference to it.
Follow the steps below to create a new contract from a single subscription contract.

1. Open the Quote.

2. Add Involved Parties.
3. Under the Assets section, click + to add Assets.
4. Select relevant subscription contracts for which you should create a new contract and add the new
contract to the Assets table.

 Note

After adding items to the Asset table, the Create a New Subscription Contract Document toggle appears
in the header section of the quote. The toggle is turned off by default. Thus all changes will be applied
to the existing subscription contract document.

5. You can mark the toggle on when you want to create a new subscription contract from items (manually
added or asset items) in the Products table.
6. You can mark the toggle off when the change of items in the Products table (manually added or asset
items) are updated to an existing subscription contract.

 Note

The change process group marked for the new contract is visible in the dropdown.

7. Click the Add asset to quote item button.

SAP Billing and Revenue Innovation Management Integration

46 PUBLIC Configuration in SAP CPQ
 8. In the Products table, add Products from Catalogue that must be part of the new contract with the contract
items if required.
9. Perform the changes to the contract items as required (for example, change quantity etc.) in the Products
table.

 Note

On placing the order, the new contract is created in SAP S/4 HANA. The old contract is cancelled, and
the reference is available in SAP S/4 HANA Subscription contract document.

To add newly added product to existing contract, the Add Items to an existing subscription document action
item was used till now. This action item is removed.

For a contract in the subscription contract document if any scheduled changes are present:

• Active version of the contract is present as main line item, but it is not selectable as scheduled version is
present.
• Scheduled version is present as child line item and is selectable for any renewal changes.

6.14.9.4 Restructure or Consolidate Multiple Subscription

Contracts

As a sales representative in SAP CPQ, you can apply change processes on multiple contracts and restructure
or consolidate multiple subscription contracts.

Follow the steps below to restructure or consolidate multiple subscription contracts into one new subscription
contract.

1. Open the Quote.

2. Add Involved Parties.
3. Under Assets section, choose + to add Assets.

 Note

Add Assets modal will have the existing contract from the Asset Table pre-selected, if any. The user can
select a new contract and deselect the pre-selected contract. The determination of multiple or single
contracts will be based on the selection count. The final selection will be updated in the Asset Table.

4. Select relevant multiple Subscription contracts for which you are creating the new contracts and add the
contracts to the Assets Table

 Note

In the event of multiple contract selection, the Create a New Subscription Contract Document toggle is
set to on and disabled in the header section of the quote.

The change process groups marked for the new contract is visible in the drop-down.

5. In the Assets table, select appropriate change process group before adding existing subscription contract
to the Products table.
6. Choose the Add asset to quote item button.

SAP Billing and Revenue Innovation Management Integration

Configuration in SAP CPQ PUBLIC 47
7. In the Products table, along with the contract items, you can add products from the catalogue which can be
part of the new contract.

 Note

On placing the order, the new contract is created in SAP S/4 HANA. The old contracts are cancelled,
and the references are available in SAP S/4 HANA subscription contract document.

If a Templates/SubscriptionContractTemplate is customized or frozen, then the asset selection process from

the modal window will change.

If an old template is used in the quote page and the user adds a new product with existing assets and then
places the order, it is added to the existing contract document only.

For a contract in the subscription contract document if any scheduled changes are present:

• Active version of the contract is present as main line item, but it is not selectable as scheduled version is
present.
• Scheduled version is present as child line item and is selectable for any renewal changes.

6.14.9.5 Swap Subscription Contract

As a sales representative in SAP CPQ, you can swap existing subscription contract or product with new one.

Prerequisite

• Swap can be selected for the change process group if it contains the change process PROD_CHANGE in
Subscription Order Management.
• In Set up Quote Change Processes Change Process Group Tab , for the selected change process
group, you must select the values for additional settings to Swap.

Swap an Existing Subscription Item with a New Subscription Item

Follow the steps below to swap an existing subscription item with a new subscription item in a subscription
contract.

1. Open the Quote.

2. Add Involved Parties.
3. Under the Assets section, click + to add Assets.
4. Select the relevant subscription contract that you want to swap and add the new contract to the Assets
table.
5. In the Products table, add the subscription type Products from the catalogue that will be used to swap an
existing contract item.

SAP Billing and Revenue Innovation Management Integration

48 PUBLIC Configuration in SAP CPQ
  Note

One newly added product can be used to swap only one existing subscription contract.

6. Select the change process group that is is marked for swap from the drop-down for the contract item in the
Assets table.
7. Choose the add asset to quote item.

 Note

Swap modal window Swap Product Items appears.

8. Select relevant entries in the Current Assets and Products for Swap tables and choose the Select for Swap.

 Note

SAP CPQ currently not supporting applying change process for Multi-level product. Swap modal will
not be open if only multi-level subscription item available in product list. Multi-level product will not be
listed in swap modal under Products for Swap section.

9. Choose the Confirm button. Asset gets added to the Products table. You can see the swap icon on the
quote item to identify the association of swap.

 Note

Choose the swap icon to check the asset information.

On placing the order, the swap operation is executed in SAP S/4 HANA.

10. The new products that got swapped will have the same contract duration (Start Date and End Date) as the
old product in the Asset.

Cancellation of Swap

Prerequisite

• In the Setup Workflow Item Actions Workflow , check the cancel swap item actions.
• You can execute the cancel operation until quote is placed.

Follow the steps below to cancel the swap operation in the quote.

1. Select the Cancel Swap action from the list of available actions in the Products table next to product
marked for swapping

 Note

When you perform Cancel Swap, the association of the new product and old product will be removed,
the configurations will not be reverted, the Contract Change Activation Date will be null, and prices will
be adjusted based on the duration.

2. Choose Ok to confirm and cancel the swap operation.

SAP Billing and Revenue Innovation Management Integration

Configuration in SAP CPQ PUBLIC 49
6.14.9.6 Co-Term Subscription Contract

Co-Term refers to aligning different assets or manually added subscription products for the same contract
end date. A sales representative can use this feature while executing any change process (including up-sell,
cross-sell, etc.) until co-terming is allowed with selected change processes.

Prerequisite

• You can select co-term in the change process group if it contains the change process EXTENSION in
Subscription Order Management.
• In CPQ Set up Quote Change Processes Change Process Group Tab , for the selected change
process group, you must select the values for additional settings to Co-Term.

Enable Co-Term for Subscription Contract

Follow the steps below to enable co-term for renewable contracts

1. Open the Quote.

2. Add Involved Parties.
3. Click + to add Assets.
4. Select relevant subscription contracts for which you want to perform changes and add the contracts to the
Assets table.
5. Select the change process group from the drop-down marked for co-term for the selected contract item in
the Assets table.
6. Click the icon Add Asset to Quote Item button.
7. In the Products table, add products from the catalogue.

 Note

Once asset items or products are available in the Products table, a toggle Co-Term in the quote header
section is visible.

8. Switch on the Co-Term toggle to select the contract end date from the calendar.

 Note

The earliest end date that can be selected should be greater than the latest contract end date among
all the assets present in the Products table.

Once the end date is selected, the subscription contract end date of all the items in the Products table
is set to the selected co-term date. The subscription contract end date, subscription contract duration,
and subscription contract extension fields are non-editable. Prices of all the items are recalculated
based on the new subscription contract end date.

If you manually add items in the Products table after performing the co-term operation, the subscription
contract end date will be aligned to the selected co-term end date.

SAP Billing and Revenue Innovation Management Integration

50 PUBLIC Configuration in SAP CPQ
If the Co-Term toggle is disabled after enabling co-term for the subscription contract, the changes will not be
automatically reverted and will have to be manually adjusted.

On placing the order, in SAP S/4 HANA the subscription contract duration will get extended as per the new
co-term end date after approving the changes in SAP S/4 HANA.

 Note

Subscription contract duration is used to help a sales representative in SAP CPQ to calculate the contract
duration. If the contract start date or end date is changed manually in a quote, it won't have an effect on the
subscription contract duration and SAP CPQ will neither recalculate nor change its value.

6.14.9.7 Adding Asset modal in SAP CPQ

In order to facilitate the selection of contracts for change process implementation, the CPQ Quote page
includes the Add Asset modal. This modal allows users to add assets to the page and view them in a
hierarchical manner, with Subscription Contract Document/Asset serving as parents and Contract documents
as child. When assets are loaded into the modal, only the headers are initially visible. However, once an asset
is expanded, all items with their respective history, status, and relevant details are displayed. The following
headers and items are included:

Headers:

• Contract Number
• Sales Org
• Distribution Channel
• Division
• Business Partner (sold to)
• Contract Posting Date

Items

• Item ID
• External Contract ID
• Part Number
• Description
• Quantity
• Net Value
• Start Date
• End Date
• State

To select a contract for the change process, users can expand the header and choose the relevant item they
wish to modify. There are three methods of selecting contracts:

• Select All Option: By clicking on "Select All" at the header, all contracts can be selected.
• Selecting the Subscription Contract Document: By choosing the subscription contract document, all
items/contracts under that document will be automatically selected

SAP Billing and Revenue Innovation Management Integration

Configuration in SAP CPQ PUBLIC 51
• Manual Selection: Users can expand the subscription contract document and individually select each item.
If only a subset of items is chosen, the header indicator will be in an indeterminate state.

If multiple contracts are selected, users will receive an alert message stating Multiple Contracts Selected.
Selected contracts are preserved across pages and remain selected until the modal is closed.

 Note

Pagination only applies to subscription contract documents (headers).

It is not possible to remove assets from the Add Assets modal. However, if certain new contracts are
chosen while previously selected ones are deselected, those deselected contracts will be removed.

6.14.9.8 Scripting Capabilities for Asset Items

Sample Script for Asset Item:

quote = QuoteHelper.Get("<Quote_Number_string>")
quoteAssets = quote.Assets
asset=quoteAssets.GetAsset("Quote_Number_string", "Item_Number")
assetColumnNames = asset.GetAssetColumnNames()
assetItems=asset.GetAssetItems()
assetItem=assetItems.GetAssetItem("Item_Number")
assetItemColumnNames=assetItem.GetAssetItemColumnNames()
quantity = assetItem["Quantity"]
billToParty = assetItem["BillToParty"]

Script Explanation:

How to load quote in script:

// There are 2 ways to load quote:

quote = QuoteHelper.Get("<Quote_Number_string>")
// or
quote = QuoteHelper.Get(<cart_id_nummber>)
// quote variable will give quote level information

How to fetch assets from loaded quote:

quoteAssets = quote.Assets
// quoteAssets variable will give available asset list from the loaded quote

How to fetch single asset from asset list:

// There are 2 ways to fetch single asset from asset list:

// By passing contract Id and contract item Id
asset = quoteAssets.GetAsset("Quote_Number_string", "Item_Number")
// In case of invalid contract Id and contract item Id. Below error message will
be returned.
// There is no asset with provided contract Id: 6000369777 & contract item Id:
20.
// or
// By passing external contract number and contract item Id
asset = quoteAssets.GetAssetByExternalContractNumber("Contract_Document_Number",
"Item_Number")
// In case of invalid external contract number and contract item Id. Below error
message will be returned.

SAP Billing and Revenue Innovation Management Integration

52 PUBLIC Configuration in SAP CPQ
 // There is no asset with provided external contract Id: 1393580 & contract item
Id: 20.

How to fetch asset column names:

assetColumnNames = asset.GetAssetColumnNames()
// assetColumnNames variable will give all the column names separated by comma
(,).

How to read specific asset column value:

assetItemDescription = asset["ItemDescription"]

How to fetch asset items from the fetched asset:

assetItems=asset.GetAssetItems()
// assetItems variable will give available asset item list for the fetched asset

How to fetch single asset from asset list:

assetItem=assetItems.GetAssetItem("Item_Number")
// In case of invalid contract item Id. Below error message will be returned.
// There is no subscription contract item with provided contract item Id: 20.

How to fetch asset item column names:

assetItemColumnNames=assetItem.GetAssetItemColumnNames()
// assetItemColumnNames variable will give all the column names separated by
comma (,).

How to read specific asset item column value:

quantity = assetItem["Quantity"]
billToParty = assetItem["BillToParty"]

SAP Billing and Revenue Innovation Management Integration

Configuration in SAP CPQ PUBLIC 53
7 SAP S/4HANA Configuration

7.1 Important Notes

Following notes should be implemented in SAP S/4HANA before proceeding:

General Information

• 3048492
• 3026226

Needed for SAP S/4HANA 2020

• 3015231
• 3016807
• 3013330
• 3014472
• 3014920
• 3005931
• 3061373
• 3132614
• 3134080

Needed for SAP S/4HANA 2021

• 3132614
• 3134080
• 3118439

7.2 Create User

1. Access the following transaction:

Transaction code SU01

2. In the User Maintenance: Initial Screen, enter the following values

SAP Billing and Revenue Innovation Management Integration

54 PUBLIC SAP S/4HANA Configuration
 Field Name Value

User <CPQS4HINTEG>

3. Select Create.
4. In the Maintain Users Screen, navigate to Address tab

Last Name for example: <CPQS4HINTEG>

E-Mail Address valid E-Mail Address to send Request

for Quotations and Orders

Method Select Remote Mail from the drop down

5. In the Logon Data, enter the following values:

User Type Select Communications Data from the drop down

Password <password>

 Note

Ensure the user is assigned relevant authorizations to execute web service messaging calls like
external pricing and print preview.

6. Choose Save.

7.3 Define Logical System

This chapter describes the procedure to create a logical system that represents the SAP CPQ system in SAP
Billing and Revenue Innovation Management system. Logical systems are defined as cross-client systems.

1. Access the following transaction

Transaction code BD54

2. In the Change View “Logical Systems”: Overview, choose New Entries:

3. Create a logical system that identifies the on-demand system, as given in the table below

Logical System for example: <CPQINTS4H>

Name for example: <SAP CPQ integration with SAP

S/4HANA>

4. Choose Save.
5. Choose Ok to confirm the pop-up for saving the details in the transport request.

SAP Billing and Revenue Innovation Management Integration

SAP S/4HANA Configuration PUBLIC 55
7.4 Business Partner Replication via SAP Master Data
Integration

The Business Partner Replication can either be triggered directly from SAP Billing Revenue and Innovation
Management to SAP CPQ or via SAP Master Data Integration.

Both scenarios can make use of the same integration flow in SAP Cloud Integration as the inbound
Business Partner object has the same structure. However, the settings in SAP Billing and Revenue Innovation
Management determine if the Business Partner is replicated directly from SAP S/4HANA to SAP CPQ or from
SAP S/4HANA via SAP Master Data Integration to SAP CPQ.

7.4.1 Activate Function Modules

This step might be already done if you used the direct business partner integration before.

1. Access the transaction using the following navigation path:

Transaction code BUPA_CALL_FU

SAP IMG Path Cross-Application Components SAP Business

Partner Data Distribution Activate Function
Models .

2. In the Change View Data Exchange: Activation of Function Modules”: Overview maintain the following values
to activate the function module

Event Object Item Function Module Call

Business Partner Business Partner and 5000001 MDG_BS_BP_OUTBO X

Outbound BP Relationship UND_DRF

3. Choose Save.

7.4.2 Configure Data Replication Framework

1. Access the transaction using the following navigation path:

Transaction code DRFIMG

SAP IMG Path Data Replication Define Custom Settings for

Data Replication Define Technical Settings Define
Technical Systems for Business Systems

2. In the “Define Business Systems”: Overview choose Create New Entries and maintain the following values.

SAP Billing and Revenue Innovation Management Integration

56 PUBLIC SAP S/4HANA Configuration
 Business Logical File Unicode Code
System Logical System RFC Destination Path Download to PS Unicode Page

<CPQINTS4H> <CPQINTS4H 0
>

3. Choose the newly created business system and double click Define Bus.Systems, Bos:
4. 4. On the Screen Define Bus.Systems, Bos: Overview, choose Create New Entries:

BO Type Sys.Filt. Outp.Mode

986 <Selected> D Direct Output

5. Choose the newly created BO Type and double click Define Bus. Systems, Bos, Communication Channel:
6. 6. In the Define Bus. Systems, Bos, Communication Channel:Overview, choose Create New Entries:

C.Channel Key Harm. Upd.KM Storage Time Dep. Cr Templte Ch Templte

1 Replication Not Defined Not Defined Not Defined

Via Services

7. Choose Save.

7.4.3 Create Replication Model

1. Access the transaction using the following navigation path:

Transaction code DRFIMG

IMG Path Define Custom Settings for Data Replication Define

Replication Models

2. In the Define Replication Model:Overview, choose New Entries:

Replication Model Description Log Days Active

MDBP_SRVC BP Service on Cloud X

Platform

3. Choose Save.
4. Choose the created Replication Model and choose Assign Outbound Implementation in the left navigation
5. In the Assign Outbound Implementation:Overview, choose New Entries:

Outbound Communication
implementation Description Sequence Channel Filter Time

986_3 Outbound Impl. for 1 1 Replication via 2 Filter After Change

BP/REL via Services Services Analysis

6. Choose the newly created outbound Implementation and choose Assign Target Systems for Repl. Model/
Outb.Impl. in the left navigation.

SAP Billing and Revenue Innovation Management Integration

SAP S/4HANA Configuration PUBLIC 57
7. In the Assign Target Systems for Repl. Model/Outb.Impl.: overview, choose New Entries:

Business System

<CPQINTS4H>

8. Choose the newly created Business System and choose Assign Outbound Parameter in the left navigation,
9. In the Assign Outbound Parameter: Overview, choose New entries:

Outbound Parameter Parameter Description Mandatory Outbound Parameter Value

PACK_SIZE_BULK Package Size for Bulk <selected> 20

Messages

 Note

Outbound Parameter value for PACK_SIZE_BULK can be set as per most efficient package size, which
will differ from system to system.

10. Choose Save.

11. Navigate to the Define Replication Model: Overview Screen and choose Replication Model MDBP_SRVC.
12. Choose Activate.

7.4.4 Configuring SAP Master Data Integration for Business

Partners replication

7.4.4.1 Service Instance Creation for Business Partner

Read and replicate

1. Go the SAP BTP subaccount where you want the SAP Master Data Integration instance to be created. In
the left-hand side, under Services, select Instances and Subscriptions.
2. Click on Create on the top right side.
3. Select the Service as <Master Data Integration>, Plan as <sap-integration>, Runtime
Environment as <Cloud Foundry>, Space as <ies-mdi-hybrid-2021>
4. Enter the Instance Name for example as <QKW_650> and <CPQINTS4H>
5. Choose Next and enter the JSON to create the service instance. Refer to this link for sample JSON
6. Choose Next, review and choose Create.
7. Select the Service Instance created and choose Create service Key.
8. Choose Next and then Create.

SAP Billing and Revenue Innovation Management Integration

58 PUBLIC SAP S/4HANA Configuration
7.4.4.2 Setting up Generic Configuration

1. Go the SAP BTP subaccount where you want the SAP Master Data Integration instance to be created. In
the left-hand side, under Services, select Instances and Subscriptions.
2. Click on Create on the top right side.
3. Select the Service as <Master Data Integration>, Plan as <sap-integration>, Runtime
Environment as <Cloud Foundry>, Space as <ies-mdi-hybrid-2021>
4. Enter the Instance Name for example as <Generic_configuration> .
5. Choose Next and enter the JSON to create the service instance. Refer to this link for sample JSON
6. Choose Next, review and choose Create.
7. Select the Service Instance created and choose Create service Key.
8. Choose Next and then Create.

7.4.4.3 Create Outbound Destinations

1. Navigate to your subaccount and choose Connectivity and then Destinations tab on the left side.
2. Choose New Destination.

Name The name should have BPOUTBOUND as suffix as

SAP Master Data Integration will check for this
suffix and sends out data to these systems,for
example,<BusinessSystemName_BPOUTBOUND> .
Make sure “Business_System_Name” value is the same
as the one used in 5.4.1.1

Type HTTP

URL Endpoint URL of the Business Partner integration

flow in SAP Cloud Integration, for example,
<https://<CPI URL>/cxf/scpmasterdata/
bpreplicationtocpq>

Proxy Type On-Premise

Authentication Basic Authentication

User Credentials of the SAP Cloud Integration Communication

User

3. Choose Save.
4. Select MDOConsumer as true under Additional Properties.
5. Repeat the above steps to create <Business_System_Name>_BPCONFIRM,
<Business_System_Name>_BPRELOUTBOUND, BP_RELCONFIRM.

SAP Billing and Revenue Innovation Management Integration

SAP S/4HANA Configuration PUBLIC 59
7.4.5 Create Distribution models

1. Go the SAP BTP subaccount where you want the SAP Master Data Integration instance to be created. In
the left-hand side, under Services, select Instances and Subscriptions.
2. Select Master Data Integration Application under Subscriptions. (Subscribe to it if already not present)
3. Select Manage Distribution Model.
4. Select Create.
5. Provide a name for the Model and select Business Partner in the Business Object Type dropdown.
6. Set the Continuous distribution checkbox if you want the business partners to be replicated as soon as they
are created/updated.
7. Provide a value for Package Size. Package size specifies up to how many objects are contained in a single
outbound XML message from SAP Master Data Integration to the client system
8. Select Mode as Push.
9. Maintain a Description with Language as English and Item for example as <Replicate Business
Partner>
.
10. Select the latest stable API under the Provider Interface API as MDI_SOAP_BUSINESS_PARTNER
.
11. To create a Provider, click the Create button and select the provider: MDI
.
12. Similarly, for the Consumer, select the target destination. You can select the appropriate Application
Category if required.
13. Set Data filters if required.
14. Activate the Replication Model.

7.5 Product Replication from SAP Billing and Revenue

Innovation Management to SAP CPQ using SOAP

7.5.1 Configure Data Replication Framework

1. 1. Access the transaction using the following navigation path:

Transaction code DRFIMG

IMG Path Define Custom Settings for Data Replication Define

Technical Settings Define Technical Systems for
Business Systems

SAP Billing and Revenue Innovation Management Integration

60 PUBLIC SAP S/4HANA Configuration
 2. In the Change View Define Business Systems: Overview choose New Entries or use the entry created in
5.4.2:

Business Logical File Unicode Code

System Logical System RFC Destination Path Download to PS Unicode Page

<CPQINTS4H <CPQINTS4H 0
> >

3. Choose the Business System and double click Define Bus.Systems, Bos in the left navigation.
4. In the Change View Define Bus.Systems, Bos: Overview, choose New Entries:

BO Type Sys.Filt. Outp.Mode

194 <Selected> D Direct

Output

 Note

If Output Mode is selected as Direct Output, product data distribution will be triggered immediately on
Save. In this case, DRFOUT is not required to replicate changes. If Output Mode is selected as Pooled
Output, data is distributed using DRF change pointers and DRFOUT has to be executed or scheduled to
create and send the data.

5. Choose the BO Type and double click Define Bus. Systems, Bos, Communication Channel: in the left
navigation
6. In the Change View Define Bus. Systems, Bos, Communication Channel:Overview, choose New Entries:

C.Channel Key Harm. Upd.KM Storage Time Dep. Cr Templte

1 Replication Via Not Defined Not Defined Not Defined

Services

7. Choose Save.

7.5.2 Configure Replication Models

1. Access the transaction using the following navigation path:

Transaction code DRFIMG

IMG Path Define Custom Settings for Data Replication Define

Replication Models

SAP Billing and Revenue Innovation Management Integration

SAP S/4HANA Configuration PUBLIC 61
2. In the Define Replication Model:Overview, choose New Entries:

Replication Model Description Log Days Active

<CPQ_S4_INT> <SAP CPQ 50 <Selected>

Integration with
SAP S/4HANA>

3. Choose Save.
4. Choose the replication model and choose Assign Outbound Implementation in the left navigation.
5. In the Assign Outbound Implementation:Overview, choose New Entries:

Outbound Communication
Implementation Description Sequence Channel Filter Time

194_3 Outbound Impl. for 1 Replication via 2 Filter After Change

Product via Services Services Analysis

6. Enter and choose the new outbound implementation and choose Assign Target Systems for Repl. Model/
Outb.Impl. in the left navigation.
7. In the Assign Target Systems for Repl. Model/Outb.Impl.: overview, choose New Entries:

Business System

<CPQINTS4H>

8. Enter and choose the new Business System and double click Assign Outbound Parameter in the left
navigation.
9. In the Assign Outbound Parameter: Overview, choose New entries:

Outbound Parameter
Outbound Parameter Parameter Description Mandatory Value Value Description

PACK_SIZE_BULK Package Size for Bulk <selected> 20

Messages

 Note

Outbound Parameter value for PACK_SIZE_BULK can be set as per most efficient package size, which
will differ from system to system.

10. Choose Save.

11. Navigate to the Define Replication Model.
12. Choose the replication model CPQ_S4_INT and choose Activate.

SAP Billing and Revenue Innovation Management Integration

62 PUBLIC SAP S/4HANA Configuration
7.5.3 Configuration for Filter Values

The SAP CPQ integration only supports sales and subscriptions products. Therefore, you have to create a DRF
filter for the product replication, so that only these kinds of products are replicated.

If you use several distribution chains (Sales Organization and Distribution Channel) for your products, you have
to do the following, because in SAP CPQ only one distribution chain can be used:

Set a filter value in DRF on the distribution chain you want to use for the integration

If you do not use a filter, the first distribution chain is used, i.e. the attributes for contract terms are taken from
this distribution chain

 Note

These below steps are optional and should be performed based on your requirement.

Procedure

1. Access the transaction using the following navigation path:

Transaction code DRFF

2. Select the replication model for products and choose Create.

3. Define the SAP S/4HANA Product Types that are relevant for replication.
4. Filters can also be added on the distribution chain.
5. Select Segment filter for sales – MDM_SALE_F and enter the Sales Organization and
Distribution Channel.
6. Choose Save.

7.5.4 Automatically Generate Integration Settings for Data

Exchange

1. 1. Access the transaction using the following navigation path:

Transaction code RCOD_CONNECTIVITY

 Note

This transaction mainly creates following settings:

• Connection to SAP Cloud Integration

• Endpoints for all selected web services
• Periodic batch jobs needed for integration
• Logical ports for outbound web services

SAP Billing and Revenue Innovation Management Integration

SAP S/4HANA Configuration PUBLIC 63
2. In the Generate Integration Settings Step 1 of 5 (6) – Middleware Selection screen, choose SAP Cloud
Platform Integration and choose Next.
3. In the Generate Integration Settings Step 2 of 5 (6) – Scope Selection:
1. In the Business Partners section, select Do you want to replicate accounts and Contacts from SAP
S/4HANA to your cloud Solution?.
2. In the Products section, select Do you want to replicate products from SAP S/4HANA to your cloud
solution?.
4. Choose Next.
5. In the Generate Integration Settings Step 3 of 5 (6) – General Settings, maintain the below settings and
choose Next:

Field Entry

Logical System Do one of the following:

Enter the logical system of the SAP CPQ system or

choose Create Logical System to create new logical
system.

Job Schedule Interval Enter the frequency with which the inbound and
outbound IDocs should be processed in the SAP
Billing and Revenue Innovation Management system, for
example <15 min>

Job User Enter the user using which batch jobs are scheduled.

6. Choose Next.
7. On the Generate Integration Settings Step 4 of 5 (6) – Settings for SAP CPI maintain the below settings and
choose Next:

Field Entry

Runtime URL Worker node URL of the SAP Cloud Integration tenant
(without HTTPS ://)

Proxy details (Optional) Host name, service name, and the access details of the
forward or reverse proxy?

Authentication (basic or certificate) Either import the certificate or enter the user credentials.

8. In the Generate Integration Settings Step 5 of (6) – Consumer Proxy Settings screen maintain the below
settings and choose Next:

Field Entry

URL Access Path

Business Partner Replication /cxf/S4/CPQ/

BusinessPartnerSUITEBulkReplicateReques
t_Out

Business Partner Relationship Replication: /cxf/S4/CPQ/

ReplicateBusinessPartnerRelationship

Product Replication: /cxf/S4/CPQ/

ProductMDMBulkReplicateRequest_Out

SAP Billing and Revenue Innovation Management Integration

64 PUBLIC SAP S/4HANA Configuration
 Field Entry

Connection Parameters:

Logical Port CPQ_LOGPORT

Computer Name

URL Port 443

URL Protocol https

Proxy Password

Logon Procedure

SSL Client Certificate X

9. Choose Next.
10. In the Generate Integration Settings: Step 6 of 6 - Summary screen, choose Generate.
11. Choose Yes to confirm the pop up.

 Note

You could check the created entries in the log.

7.6 Settings in SOAMANAGER

7.6.1 Port for Products

1. Access the transaction using the following navigation path:

Transaction code SOAMANAGER

2. Choose Web Service Configuration in the browser.

3. In the Web Service Configuration page, under Design Time Object Search enter the following details.

Field Entry

Object Type Consumer Proxy

Object Name <ProductMDMBulkReplicateRequest_Out>

4. Choose the search result CO_MDM_PRD_BULK_REPL_REQ_OUT.

5. In the Configurations, check if the Logical port created using RCOD_CONNECTIVITY has the Creation Type
as Manually Created.

SAP Billing and Revenue Innovation Management Integration

SAP S/4HANA Configuration PUBLIC 65
6. Choose Ping Web Service and if the ping is not successful, select Edit Logical Port and maintain the
Authentication as below. Ensure the port is Active.

Field Entry

Authentication Method Username/Password (Basic)

User: Client ID of SAP Cloud Integration, for example <ABCD>

Password Client secret of SAP Cloud Integration, for example

<XYZ>

Logical Port is
Actions Logical Port State Default Description Creation Type

CPQ_LOGPORT Active Manually created

7.6.2 Port for Business Partners

7.6.2.1 Direct Integration from SAP S/4HANA to SAP CPQ

1. Access the transaction using the following navigation path:

Transaction code SOAMANAGER

2. Choose Web Service Configuration in the browser.

3. In the Web Service Configuration page, under Design Time Object Search enter the following details.

Field Entry

Object Type Consumer Proxy

Object Name Contains endpoint of the corresponding integration flow,

for example
<BusinessPartnerSUITEBulkReplicateReque
st_Out>

4. Choose the search result CO_MDG_BP_RPLCTRQ.

5. In the Configurations, check if the Creation Type is Manually Created.
6. In the Define Logical Ports add the Authentication as below and ensure the port is active.

Field Entry

Authentication Method Username/Password (Basic)

SAP Billing and Revenue Innovation Management Integration

66 PUBLIC SAP S/4HANA Configuration
 Field Entry

User: Enter a user, for example <ABCD>

Password Enter a password, for example <XYZ>

Logical Port is
Actions Logical Port State Default Description Creation Type

CLOUD_MD_SER Active true Business Partner Manually created

VICE Service on SAP
Cloud Integration

<CPQ_LOGPORT Active Manually created

>

7.6.2.2 Integration from SAP S/4HANA to SAP CPQ via

Master Data Integration

1. Access the transaction using the following navigation path:

Transaction code SOAMANAGER

2. Choose Web Service Configuration in the browser.

3. In the Web Service Configuration page, under Design Time Object Search enter the following details.

Field Entry

Object Type Consumer Proxy

Object Name Contains endpoint of the corresponding integration flow,

for example
<BusinessPartnerSUITEBulkReplicateReque
st_Out>

4. Choose the search result CO_MDG_BP_RPLCTRQ.

5. In the Configurations, check if the Creation Type is Manually Created.
6. In the Define Logical Ports add the Authentication as below and ensure the port is active.

Field Entry

Authentication Method Username/Password (Basic)

User Enter a user, for example <ABCD>

Password Enter a password, for example <XYZ>

Create the new port manually. Choose Create  Manual Configuration. Enter a name for the logical port,
e.g. CLOUD_MD_SERVICE.

SAP Billing and Revenue Innovation Management Integration

SAP S/4HANA Configuration PUBLIC 67
 Consumer Security

Authentication level Basic

Authentication Settings User ID / Password

User ID / Password Enter the User Name and the Password

from the Service Key in the SAP Cloud
Integration

Messaging

RM Protocol SAP RM

Message ID Protocol SAP Message ID

Data Transfer scope Basic Data Transfer

Transfer Protocol Transfer via SOAP header

Transport Settings

URL Access Path Radio Button: Complete URL

URL URL of the Master Data Integration

Service from the SAP Cloud Integration

Logon Language Language of User Context

Make Local Call No Call in Local System

Transport Binding Protocol SOAP 1.1

Maximum Wait for WS Consumer 0

Make sure the port is active and that pinging the port is successful:

Logical Port is
Actions Logical Port State Default Description Creation Type

CLOUD_MD_SER Active true Business Partner Manually created

VICE Service on SAP
Cloud Integration

<CPQ_LOGPORT Active Manually created

>

7.7 Configurations for Product Master Data

For the integration the product master must follow following rules:

• Product group (MARA-MATKL) is used for the mapping to SAP CPQ product type
• Product hierarchy (MARA-PRDHA) is used for mapping to SAP CPQ product category. As this is mandatory
in SAP CPQ the same as to be defined as a mandatory field in SAP S/4HANA product master. Additionally,
a value mapping in CPI must be maintained.

SAP Billing and Revenue Innovation Management Integration

68 PUBLIC SAP S/4HANA Configuration
 • Several billing cycles for the same product in SAP CPQ can be used, in that case a billing cycle
determination rule should be used in the SAP S/4HANA product. Additional billing cycle can be set in
the SAP S/4HANA product which is then used as default in the SAP CPQ product

7.7.1 Define Product Group

The Product Group (MARA-MATKL) in SAP Billing Revenue and Innovation Management are mapped to
Product Types in SAP CPQ. In SAP CPQ the product type is used to see intermediate sums based on product
types. This allows to distinguish between:

• Cloud Subscriptions
• HEC Subscriptions
• Printers
• Laptops and Desktops

1. Access the transaction using the following navigation path:

Transaction code OMSF

2. In the Change view “Material Groups”: Overview screen, create or choose the entries for material groups:

Default unit of Description 2 for the

Matl Group Material Group Desc. AGrp wt/DUW Material Group

BUND Bundle Product

HAWA Trading Goods

NLAG Non-stocks materials

NLAG-CTR Non-st contract mat

SUBS Subscription Product

3. Choose Save.

7.7.2 Define Product Hierarchy

The SAP S/4HANA Product Hierarchy (MARA-PRDHA) is mapped to any of the SAP CPQ Product Categories:

• Bundle Offerings
• Subscriptions Only
• Add On’s

1. Access the transaction using the following navigation path:

Transaction code OVSV

SAP Billing and Revenue Innovation Management Integration

SAP S/4HANA Configuration PUBLIC 69
 SAP IMG Path SPRO Logistics - General Material Master
Settings for Key Fields Data Relevant to Sales and
Distribution Define Product Hierarchies

2. Choose Maintenance: Prod.Hier.. and create New Entries:

Product Hierarchy Level.no. Description

00003 1 HAWA

00004 1 SUBS

00005 1 BUND

00006 1 NLAG

00007 1 SERV

3. Choose Save.

7.8 Pricing

7.8.1 Condition Types

 Note

If SAP Variant Configuration and Pricing is not used, condition types can be defined without access
sequence. These condition types must then be assigned in SAP CPQ to the SAP CPQ item prices.

If SAP Variant Configuration and Pricing is used for pricing, then you must add condition function BASE to
condition type for base price. For example, PSMB and condition function VARC to condition type for variant
condition for example, VASE.

You need to decide whether to use stateless pricing or document pricing. With stateless pricing, it’s not
possible to change the pricing information arriving from SAP Variant Configuration and Pricing to SAP CPQ.
On the other hand, document pricing only applies to the entire quote, and the functionality allows you to
manually change the pricing information from SAP Variant Configuration and Pricing by mapping pricing
conditions to fields in SAP CPQ. When document pricing is enabled, stateless pricing is still used in the
Configurator, but document pricing is used on the quote.

The following condition types are only an example on how monthly or yearly fees / surcharges can be assigned
in pricing procedure. Create those condition types which are relevant as per the requirements. Adjust the
pricing procedure mentioned in next chapter accordingly with the required condition types.

1. Access the transaction using the following navigation path:

SAP Billing and Revenue Innovation Management Integration

70 PUBLIC SAP S/4HANA Configuration
 Transaction code SPRO

SAP IMG menu Sales and Distribution Basic Functions Pricing

Pricing Control Define Condition Types

2. Choose Set Condition Types for Pricing

3. In the Change View :Conditions: Condition Types:” Overview, choose New Entries and maintain the following
condition types.

Field Value

Condition Type For example, ZMMS

Text <Man Surcharge Monthl>

Control Data 1

Condition Class: A (Discount or surcharge)

Calculation Type: M (Quantity- Monthly Price)

Dat.Rec.Source: Condition Technique (SAP S/4HANA)

Changes which can be made

Manual entries: C (Manual entry has priority)

Item Condition: X

Delete: X

Amount/Percent: X

Quantity Relation: X

Value: X

Master Data

Delete from DB: Do not delete (set the deletion flag only)

Scales

Scale Base Type: C (Quality scale)

Text Determination

TextDeterminationProcedure: 01 Price

Text ID: 0001 (Internal comment)

Condition Type For example, <ZMSC>

Text <Manual Surcharge>

Control Data 1

Condition Class: A (Discount or surcharge)

Calculation Type: C (Quantity)

Dat.Rec.Source: Condition Technique (SAP S/4HANA)

Changes which can be made

Manual entries: C (Manual entry has priority)

SAP Billing and Revenue Innovation Management Integration

SAP S/4HANA Configuration PUBLIC 71
 Field Value

Item Condition: X

Delete: X

Amount/Percent: X

Quantity Relation: X

Value: X

Master Data

Delete from DB: Do not delete (set the deletion flag only)

Scales

Scale Base Type: C (Quality scale)

Text Determination

TextDeterminationProcedure: 01 Price

Text ID: 0001 (Internal comment)

Condition Type For example, <ZSMB>

Text <Manual Surcharge>

Control Data 1

Condition Class: B (Prices)

Calculation Type: M (Quantity- Monthly Price)

Dat.Rec.Source: Condition Technique (SAP S/4HANA)

Changes which can be made

Manual entries: C (Manual entry has priority)

Item Condition: X

Delete: X

Amount/Percent: X

Quantity Relation: X

Value: X

Master Data

Delete from DB: Do not delete (set the deletion flag only)

Scales

Scale Base Type: C (Quality scale)

Text Determination

TextDeterminationProcedure: 01 Price

Text ID: 0001 (Internal comment)

Condition Type For example, <ZSYB>

Text <Man. Yearly Subs Fee>

SAP Billing and Revenue Innovation Management Integration

72 PUBLIC SAP S/4HANA Configuration
 Field Value

Control Data 1

Condition Class: B (Prices)

Calculation Type: N (Quantity – Year Price)

Dat.Rec.Source: Condition Technique (SAP S/4HANA)

Changes which can be made

Manual entries: C (Manual entry has priority)

Item Condition: X

Delete: X

Amount/Percent: X

Master Data

Delete from DB: Do not delete (set the deletion flag only)

Scales

Scale Base Type: C (Quality scale)

Scale Type B (To Scale)

Scale Unit YR

Text Determination

TextDeterminationProcedure: 01 Price

Text ID: 0001 (Internal comment)

Condition Type For example, <ZYMS>

Text <Man Surcharge Yearly>

Control Data 1

Condition Class: A (Discount or surcharge)

Calculation Type: N (Quantity – Year Price)

Dat.Rec.Source: Condition Technique (SAP S/4HANA)

Changes which can be made

Manual entries: C (Manual entry has priority)

Item Condition: X

Delete: X

Amount/Percent: X

Quantity Relation: X

Value: X

Master Data

Delete from DB: Do not delete (set the deletion flag only)

Scales

SAP Billing and Revenue Innovation Management Integration

SAP S/4HANA Configuration PUBLIC 73
 Field Value

Scale Base Type: C (Quality scale)

Text Determination

TextDeterminationProcedure: 01 Price

Text ID: 0001 (Internal comment)

Condition Type For example, <ZYSF>

Text <Yearly Subscr Fee>

Access Sequence PSMB (Recurring Subscr Price)

Control Data 1

Condition Class: B (Prices)

Calculation Type: N (Quantity – Year Price)

Condition Function Base

Dat.Rec.Source: Condition Technique (SAP S/4HANA)

Plus/Minus A (positive and negative)

Changes which can be made

Manual entries: C (Manual entry has priority)

Item Condition: X

Delete: X

Amount/Percent: X

Master Data

Delete from DB: Do not delete (set the deletion flag only)

Scales

Scale Base Type: C (Quality scale)

Scale Type B (To scale)

Scale Unit MON

Text Determination

TextDeterminationProcedure: 01 Price

Text ID: 0001 (Internal comment)

Condition Type For example, <ZYVA>

Text <Yearly Variant Price>

Access Sequence VA00 (Variants)

Control Data 1

Condition Class: A (Discount or surcharge)

Calculation Type: N (Quantity – Year Price)

Condition Function VARC

SAP Billing and Revenue Innovation Management Integration

74 PUBLIC SAP S/4HANA Configuration
 Field Value

Dat.Rec.Source: Condition Technique (SAP S/4HANA)

Changes which can be made

Manual entries: C (Manual entry has priority)

Item Condition: X

Delete: X

Amount/Percent: X

Quantity Relation: X

Value: X

Master Data

Delete from DB: Do not delete (set the deletion flag only)

Scales

Scale Base Type: C (Quality scale)

Control Data 2

Used for Var.Config X

Text Determination

TextDeterminationProcedure: 01 Price

Text ID: 0001 (Internal comment)

Condition Type For example, <ZPD1>

Text <Percentage Discount>

Access Sequence DPD1 (Customer/Price List)

Control Data 1

Condition Class: A (Discount or surcharge)

Calculation Type: A (Percentage)

Dat.Rec.Source: Condition Technique (SAP S/4HANA)

Changes which can be made

Manual entries: C (Manual entry has priority)

Item Condition: X

Delete: X

Amount/Percent: X

Master Data

Delete from DB: Do not delete (set the deletion flag only)

Condition Type For example, <ZPG1>

Text <Cust. Grp / Material>

Access Sequence DPG1 (Customer Price Group/Material)

SAP Billing and Revenue Innovation Management Integration

SAP S/4HANA Configuration PUBLIC 75
 Field Value

Control Data 1

Condition Class: A (Discount or surcharge)

Calculation Type: C (Quantity)

Plus/Minus X (Negative)

Dat.Rec.Source: Condition Technique (SAP S/4HANA)

Changes which can be made

Manual entries: C (Manual entry has priority)

Item Condition: X

Delete: X

Amount/Percent: X

Master Data

Delete from DB: Do not delete (set the deletion flag only)

Scales

Scale Base Type: C (Quality scale)

Control Data 2

Quantity Conversion X

Condition Type For example, <ZPG4>

Text <Customer/Mat.Pr.Grp>

Access Sequence DPG1 (Customer Price Group/Material)

Control Data 1

Condition Class: A (Discount or surcharge)

Calculation Type: C (Quantity)

Plus/Minus X (Negative)

Dat.Rec.Source: Condition Technique (SAP S/4HANA)

Changes which can be made

Manual entries: C (Manual entry has priority)

Item Condition: X

Delete: X

Amount/Percent: X

Master Data

Delete from DB: Do not delete (set the deletion flag only)

Scales

Scale Base Type: C (Quality scale)

Control Data 2

SAP Billing and Revenue Innovation Management Integration

76 PUBLIC SAP S/4HANA Configuration
 Field Value

Quantity Conversion X

7.8.2 Define Pricing Procedure for Stateless Pricing

Define a pricing procedure with the required condition types mentioned in the above chapter and assign it to
the Solution quotation and Subscription contract. User defined pricing procedure is required to define monthly
and yearly prices and cumulated discounts.

Stateless pricing is used only during product configuration in SAP CPQ. With stateless pricing, it’s not possible
to change the pricing information arriving from SAP Variant Configuration and Pricing in SAP CPQ, so it’s not
possible to manually change the pricing information from SAP Variant Configuration and Pricing by mapping
pricing conditions to fields in SAP CPQ.

1. Access the transaction using the following navigation path:

Transaction code SPRO

SAP IMG menu Sales and Distribution Basic Functions Pricing

Pricing Control Define And Assign Pricing Procedures

2. Choose the activity Set Pricing Procedure.

3. Choose New Entries

Field Value

Procedure For example <ZSQCPQ>

Description For example <Solution Quote from SAP CPQ>

4. Enter and choose the new pricing procedure and navigate to Procedures – Control data, in the left
navigation.
5. In the Change view: Procedures – Control Data”: Overview , choose New Entries.

Rele-
vant
for
Ac-
coun Alt.C
Con- t De- alc.C Alt.C
di- De- Man- Re- ter- Re- ndn ndn Ac- Ac-
Coun tion scrip From To ual quire min- Print Sub- quire Amo Base coun cu-
Step ter Type tion Step Step Only d ation Type total ment unt Value t Key rals

20 0 PPR0 Price 2 ERL

30 0 PSPB Bun- 2 ERL

dle
Price

SAP Billing and Revenue Innovation Management Integration

SAP S/4HANA Configuration PUBLIC 77
 Rele-
vant
for
Ac-
coun Alt.C
Con- t De- alc.C Alt.C
di- De- Man- Re- ter- Re- ndn ndn Ac- Ac-
Coun tion scrip From To ual quire min- Print Sub- quire Amo Base coun cu-
Step ter Type tion Step Step Only d ation Type total ment unt Value t Key rals

35 0 VA00 Var- 2 ERL

iant
Price

40 0 ZMS Man- 2 ERL

C ual
Sur-
charg
e

50 0 PMP Man- X 2 ERL

0 ual
Price

100 0 One- a 1 2
Time
Pay-
ment
Net

107 0 DAI1 Accnt a 2 ERS

ng
Ind.
(Abs.
)

108 0 DAI2 Ac- 100 a 2 ERS

count
ing
Ind.
(%)

120 0 DPG1 Cust. a 2 ERS

Grp /
Ma-
terial

190 0 DPG Cus- a 2 ERS

4 to-
mer/
Mat.
Pr.Gr
p

200 0 DRV1 Fixed X a 2 ERS

Amo
unt 1

SAP Billing and Revenue Innovation Management Integration

78 PUBLIC SAP S/4HANA Configuration
 Rele-
vant
for
Ac-
coun Alt.C
Con- t De- alc.C Alt.C
di- De- Man- Re- ter- Re- ndn ndn Ac- Ac-
Coun tion scrip From To ual quire min- Print Sub- quire Amo Base coun cu-
Step ter Type tion Step Step Only d ation Type total ment unt Value t Key rals

210 0 Sum 101 209

One-
Time
Surc
h./
Dis-
count
s

400 0 PSI1 Price 2 ERL

f.Srv.
Cntr.I
tm

410 0 PSM Mont 2 ERL

B hly
Subs
cr
Fee

420 0 VASE Var- 2 ERL

iant
Price

421 Sub- 4
total
VASE

425 0 ZMM Man 2 ERL

S Sur-
charg
e
Mont
hl

430 0 ZYSF Yearl 2 ERL

y
Subs
cr
Fee

440 0 ZYVA Yearl 2 ERL

y Var-
iant
Price

SAP Billing and Revenue Innovation Management Integration

SAP S/4HANA Configuration PUBLIC 79
 Rele-
vant
for
Ac-
coun Alt.C
Con- t De- alc.C Alt.C
di- De- Man- Re- ter- Re- ndn ndn Ac- Ac-
Coun tion scrip From To ual quire min- Print Sub- quire Amo Base coun cu-
Step ter Type tion Step Step Only d ation Type total ment unt Value t Key rals

445 0 ZYM Man 2 ERL

S Sur-
charg
e
Yearl
y

450 0 ZSM Man. X 2 ERL

B Mont
h.
Subs
Fee

460 0 ZSYB Man. X 2 ERL

Yearl
y
Subs
Fee

500 0 Peri- 400 499 2 2

odic
Pay-
ment
Net

510 0 DSI1 Man. X a 2 ERL

Srv.C
ntr.
Surc
h

515 0 DSP1 Serv- X a 2 ERL

ice
Pro-
file

516 0 DSP2 Re- X a 2 ERL

spon
se
Pro-
file

519 0 DSI2 Man. 500 518 X a 2 ERL

Srv.
Surc
h.
(%)

SAP Billing and Revenue Innovation Management Integration

80 PUBLIC SAP S/4HANA Configuration
 Rele-
vant
for
Ac-
coun Alt.C
Con- t De- alc.C Alt.C
di- De- Man- Re- ter- Re- ndn ndn Ac- Ac-
Coun tion scrip From To ual quire min- Print Sub- quire Amo Base coun cu-
Step ter Type tion Step Step Only d ation Type total ment unt Value t Key rals

520 0 DPD1 Per- 500 a 2 ERS

cent-
age
Dis-
count

530 0 Sum 501 529

Peri-
odic
Surc
h./
Dis-
count
s

600 0 Net a 3 2
Value

750 0 UTXJ Tax 600 X 84 MWS

Juris-
dict.C
ode

751 0 AR1 A/R 600 B MW1

Sales
Tax 1

752 0 AR2 A/R 600 B MW2

Sales
Tax 2

753 0 AR3 A/R 600 B MW3

Sales
Tax 3

754 0 AR4 A/R 600 B MW4

Sales
Tax 4

799 0 DRD1 Roun 13 16 4 ERS

ding
Off 1

802 0 EK02 Cal- X B

cu-
lated
costs

805 0 Gross 9 4
Value

SAP Billing and Revenue Innovation Management Integration

SAP S/4HANA Configuration PUBLIC 81
6. To create pricing procedure for Subscription Contract,Choose New Entries:

Field Value

Procedure For example < ZSCCPQ >

Description For example < Subscription Contract SAP

CPQ >

7. Enter and select the newly added pricing procedure. On the Procedures – Control data: Overview screen,
check or create the following Procedure steps:

Rele-
vant
for
Ac-
coun Alt.C
Con- t De- alc.C Alt.C
di- De- Man- Re- ter- Re- ndn ndn Ac- Ac-
Coun tion scrip From To ual quire min- Print Sub- quire Amo Base coun cu-
Step ter Type tion Step Step Only d ation Type total ment unt Value t Key rals

20 0 PSPB Bun- 2 ERL

dle
Price

25 0 VA00 Var- 2 ERL

iant
Price

30 0 PSM Mont 2 ERL

B hly
Subs
cr
Fee

40 0 VASE Var- 2 ERL

iant
Price

41 0 ZMM Man 2 ERL

S Sur-
charg
e
Mont
hl

42 0 ZYSF Yearl 2 ERL

y
Subs
cr
Fee

43 0 ZYVA Yearl 2 ERL

y Var-
iant
Price

SAP Billing and Revenue Innovation Management Integration

82 PUBLIC SAP S/4HANA Configuration
 Rele-
vant
for
Ac-
coun Alt.C
Con- t De- alc.C Alt.C
di- De- Man- Re- ter- Re- ndn ndn Ac- Ac-
Coun tion scrip From To ual quire min- Print Sub- quire Amo Base coun cu-
Step ter Type tion Step Step Only d ation Type total ment unt Value t Key rals

44 0 ZYM Man 2 ERL

S Sur-
charg
e
Yearl
y

50 0 PSLC Lock 2 ERL

Fee

100 0 Gross a 1 2

120 0 DPG1 Cust. a 2 ERS

Grp /
Ma-
terial

130 0 DCM Cus- a 2 ERS

1 to-
mer/
Ma-
terial

160 0 DM0 Ma- a 2 ERS

1 terial

170 0 DPD1 Per- 100 a 2 ERS

cent-
age
Dis-
count

400 0 Sum 101 399

Sur-
charg
es/
Dis-
count
s

600 0 Net a 2 2
Value
1

750 0 UTXJ Tax 600 84 MWS

Juris-
dict.C
ode

SAP Billing and Revenue Innovation Management Integration

SAP S/4HANA Configuration PUBLIC 83
 Rele-
vant
for
Ac-
coun Alt.C
Con- t De- alc.C Alt.C
di- De- Man- Re- ter- Re- ndn ndn Ac- Ac-
Coun tion scrip From To ual quire min- Print Sub- quire Amo Base coun cu-
Step ter Type tion Step Step Only d ation Type total ment unt Value t Key rals

751 0 AR1 A/R 600 X A MW1

Sales
Tax 1

752 0 AR2 A/R 600 X A MW2

Sales
Tax 2

753 0 AR3 A/R 600 X A MW3

Sales
Tax 3

754 0 AR4 A/R 600 X A MW4

Sales
Tax 4

799 0 DRD1 Roun 13 16 ERS

ding
Off 1

800 0 Total A 4
Value

805 0 Gross 9 4
Value

810 0 DCD1 Cash 9

Dis-
count
1

820 0 GRW Stat- 600 C 8

R istical
value

830 0 PCIP Inter- B 4

nal
Price

850 0 Profit 4 11
Mar-
gin

7.8.3 Pricing Procedure Determination for Stateless Pricing

You specify how the system determines pricing procedures for solution quotation and subscription contract
every time you create a document. This activity needs to be done individually according to the setup of the
organizational structure, which is different in every installation.

SAP Billing and Revenue Innovation Management Integration

84 PUBLIC SAP S/4HANA Configuration
 1. Access the transaction using the following navigation path:

Transaction code SPRO

SAP IMG menu Sales and Distribution Basic Functions Pricing

Pricing Control Define And Assign Pricing Procedures

2. Choose Set Pricing Procedure Determination.

3. In the Change View :Det. Of Pricing Procedure in Sales Docs.:” Overview, choose New Entries,to maintain the
pricing procedure determination:

Distribu- Condition Condition

Sales Or- tion Chan- Doc.Pric- Cust.Pric- Pricing Pricing Type for Type for
ganization nel Division ing.Proc ing.Pric Procedure Procedure Fast Entry Fast Entry

2020 10 10 A 1 ZSQCPQ Solution

Quote from
CP

2020 10 10 S2 1 ZSQCPQ Solution

Quote from
CP

2020 10 10 S5 1 ZSCCPQ Subscrip-

tion Con-
tract

4. Choose Save.

7.8.4 Define Pricing Procedure for Document Pricing

Define a pricing procedure with the required condition types mentioned in the above chapter and assign it to
the Solution quotation and Subscription contract. User defined pricing procedure is required to define monthly
and yearly prices and cumulated discounts.

Stateless pricing is used only during product configuration in SAP CPQ. With stateless pricing, it’s not possible
to change the pricing information arriving from CPS in SAP CPQ. On the other hand, document pricing only
applies to the entire quote, and the functionality allows to manually change the pricing information from CPS
by mapping pricing conditions to fields in SAP CPQ. When document pricing is enabled, stateless pricing is still
used in the configurator, but document pricing is used on the quote.

1. Access the transaction using the following navigation path:

Transaction code SPRO

SAP IMG menu Sales and Distribution Basic Functions Pricing

Pricing Control Define And Assign Pricing Procedures

2. Choose the activity Set Pricing Procedure.

3. Choose New Entries.
4. Enter and choose the new pricing procedure and navigate to Procedures – Control data, in the left
navigation.

SAP Billing and Revenue Innovation Management Integration

SAP S/4HANA Configuration PUBLIC 85
5. In the Change view: Procedures – Control Data”: Overview , choose New Entries.

Field Value

Procedure For example <ZCPQDP>

Description For example <Solution Quote for Document Pricing>

Rele-
vant
for
Ac-
count Alt.
De- Cal. Alt.C
Con- De- Man- Re- ter- Re- Cndn ndn Ac-
Coun dition scrip- From To ual quire mina- Print Sub quire Amo Base count Accu-
Step ter Type tion Step Step Only d tion Type total ment unt Value Key rals

20 0 PPR0 Price 2 ERL

30 0 PSPB Bun- 2 ERL

dle
Price

35 0 VA00 Var- 2 ERL

iant
Price

40 0 ZMS Man- 2 ERL

C ual
Sur-
charg
e

50 0 PMP Man- X 2 ERL

0 ual
Price

100 0 One- a 1 2
Time
Pay-
ment
Net

107 0 DAI1 Accnt a 2 ERS

ng
Ind.
(Abs.
)

108 0 DAI2 Ac- a 2 ERS

count
ing
Ind.
(%)

120 0 ZPG1 Cust. a 2 ERS

Grp /
Mate-
rial

SAP Billing and Revenue Innovation Management Integration

86 PUBLIC SAP S/4HANA Configuration
 Rele-
vant
for
Ac-
count Alt.
De- Cal. Alt.C
Con- De- Man- Re- ter- Re- Cndn ndn Ac-
Coun dition scrip- From To ual quire mina- Print Sub quire Amo Base count Accu-
Step ter Type tion Step Step Only d tion Type total ment unt Value Key rals

190 0 ZPG4 Cus- a 2 ERS

to-
mer/
Mat.P
r.Grp

200 0 DRV1 Fixed X a 2 ERS

Amou
nt 1

201 0 RA01 % 100 a 2 ERS

Disc.f
rom
Gross

210 0 Sum 101 209

One-
Time
Surch
./
Dis-
count
s

300 0 Sub 1 299 a 3 2

Total
One
Time

400 0 PSI1 Price 2 ERL

f.Srv.
Cntr.I
tm

401 0 400 400 a 6

402 0 DSI1 X a 2 ERL

403 0 DSP1 2 ERL

404 0 DSP2 a 2 ERL

405 0 DSI2 401 404 X a 2 ERL

406 0 ZPD2 401 a 2 ERS

407 0 402 406

408 0 401 406 a 6

SAP Billing and Revenue Innovation Management Integration

SAP S/4HANA Configuration PUBLIC 87
 Rele-
vant
for
Ac-
count Alt.
De- Cal. Alt.C
Con- De- Man- Re- ter- Re- Cndn ndn Ac-
Coun dition scrip- From To ual quire mina- Print Sub quire Amo Base count Accu-
Step ter Type tion Step Step Only d tion Type total ment unt Value Key rals

410 0 PSM Mont 2 ERL

B hly
Subs
cr Fee

420 0 VASE Var- 2 ERL

iant
Price

425 0 ZMM Man 2 ERL

S Sur-
charg
e
Mont
hl

430 0 ZYSF Yearly 2 ERL

Subs
cr Fee

440 0 ZYVA Yearly 2 ERL

Var-
iant
Price

445 0 ZYMS Man 2 ERL

Sur-
charg
e
Yearly

450 0 ZSM Man. X 2 ERL

B Mont
h.
Subs
Fee

460 0 ZSYB Man. X 2 ERL

Yearly
Subs
Fee

480 0 Sub- 420 420 4

total
VASE

SAP Billing and Revenue Innovation Management Integration

88 PUBLIC SAP S/4HANA Configuration
 Rele-
vant
for
Ac-
count Alt.
De- Cal. Alt.C
Con- De- Man- Re- ter- Re- Cndn ndn Ac-
Coun dition scrip- From To ual quire mina- Print Sub quire Amo Base count Accu-
Step ter Type tion Step Step Only d tion Type total ment unt Value Key rals

490 0 Peri- 400 470 a 2

odic
Pay-
ment
Net
DP

520 0 ZPD1 Per- 490 a 2 ERS

cent-
age
Dis-
count

530 0 Sum 501 529

Peri-
odic
Surch
./
Dis-
count
s

590 0 Sub 490 529 a 2

Total
Re-
cur-
ring

600 0 Net a 3 2
Value

750 0 UTXJ Tax 600 X 84 MWS

Juris-
dict.C
ode

751 0 AR1 A/R 600 B MW1

Sales
Tax 1

752 0 AR2 A/R 600 B MW2

Sales
Tax 2

753 0 AR3 A/R 600 B MW3

Sales
Tax 3

SAP Billing and Revenue Innovation Management Integration

SAP S/4HANA Configuration PUBLIC 89
 Rele-
vant
for
Ac-
count Alt.
De- Cal. Alt.C
Con- De- Man- Re- ter- Re- Cndn ndn Ac-
Coun dition scrip- From To ual quire mina- Print Sub quire Amo Base count Accu-
Step ter Type tion Step Step Only d tion Type total ment unt Value Key rals

754 0 AR4 A/R 600 B MW4

Sales
Tax 4

799 0 DRD1 Roun 13 16 4 ERS

ding
Off 1

802 0 EK02 Cal- X B

cu-
lated
costs

805 0 Gross 9 4
Value

7.8.5 Pricing Procedure Determination for Document Pricing

You specify how the system determines pricing procedures for solution quotation and subscription contract
every time you create a document. This activity needs to be done individually according to the setup of the
organizational structure, which is different in every installation.

1. Access the transaction using the following navigation path:

Transaction code SPRO

SAP IMG menu Sales and Distribution Basic Functions Pricing

Pricing Control Define And Assign Pricing Procedures

2. Choose Set Pricing Procedure Determination.

3. In the Change View :Det. Of Pricing Procedure in Sales Docs.:” Overview, choose New Entries,to maintain the
pricing procedure determination:

Distribu- Condition Condition

Sales Or- tion Chan- Doc.Pric- Cust.Pric- Pricing Pricing Type for Type for
ganization nel Division ing.Proc ing.Pric Procedure Procedure Fast Entry Fast Entry

2020 10 10 S2 1 ZCPQDP Solution

Quote for
Document
Pr

SAP Billing and Revenue Innovation Management Integration

90 PUBLIC SAP S/4HANA Configuration
 Distribu- Condition Condition
Sales Or- tion Chan- Doc.Pric- Cust.Pric- Pricing Pricing Type for Type for
ganization nel Division ing.Proc ing.Pric Procedure Procedure Fast Entry Fast Entry

2020 10 10 S3 1 ZCPQDP Solution

Quote for
Document
Pr

2020 10 10 S5 1 ZSCCPQ Subscrip-

tion Con-
tract

4. Choose Save.

7.9 Transaction Customizing

7.9.1 Define Partner Determination Procedure

1. Access the transaction using the following navigation path:

Transaction code SPRO

SAP IMG menu Service Basic Functions Partner Processing

Define Partner Determination Procedure

2. In the Change View: Partner Determination Procedures”: Overview. Choose New Entries:

Procedure Description Block Determine Log Permitted Functions

ZCPQ_SC Subscription: CPQ Standard (All Defined

partner functions)

<ZCPQ_SQH> <SAP CPQ Only functions

Solution assigned in procedure
Quotation:
Header>

3. Choose the partner determination procedure ZCPQ_SC and choose Procedure User in the left navigation.

Procedure User

User

BUS2000112 Service Contract

BUS2000115 Sales

SAP Billing and Revenue Innovation Management Integration

SAP S/4HANA Configuration PUBLIC 91
 Procedure User

BUS2000116 Service Order/Quotation

BUS2000131 Sales Item

BUS2000137 CServ. Contract Item

BUS2000140 Service Product Item

BUS2000146 Service. Material Item

BUS2000155 Provider Order Item

BUS2000156 Provider Contr. Item

BUS2000265 Subscription Order

BUS2000266 Subscription Contract

4. Choose Save.
5. Choose Partner Functions in Procedure in the left navigation and choose New Entries:

Partner Functions in Procedure

Entry changea- No.of occur- No.of occur-
Function ble/changeable rence/Minimum rence/Maximum Select.limit Access Sequence

0000001 Sold-To 1 1 0 001 Preceding

Party (CRM) Document :
Activity Partner
Preceding
Document : Sold-
To Party

0000002 Ship-To X 1 1 0 0021 Preceding

Party (CRM) Document
Preceding
Document Ship-
to/Service
Recepient
Business
Partner

0000003 Bill-To X 1 1 0 0005

Party (CRM) Preceding
Document
Business Partner
Relationships:
Sold-To Party
Current

SAP Billing and Revenue Innovation Management Integration

92 PUBLIC SAP S/4HANA Configuration
 Entry changea- No.of occur- No.of occur-
Function ble/changeable rence/Minimum rence/Maximum Select.limit Access Sequence

0000004 Payer X 1 1 0 0005

(CRM) Preceding
Document
Business Partner
Relationships:
Sold-To Party
Current

00000014 Em- X 0 5 0 0008

ployee Responsi- Preceding
ble (CRM) Document
User

6. Choose Save
7. Choose User Interface Settings in the left navigation and choose New Entries:

PartnerDetProc: ZCPQ_SC Subscription: CPQ

Header Screen

Partner Function1 0000001 Sold-To Party (CRM)

Partner Fucntion2 0000002 Ship-To Party (CRM)

Display

Display Variant 0101 Partner number/ Number type /Address

8. Choose Save.
9. Choose the partner determination procedure ZCPQ_SQH and choose Procedure User in the left navigation.

Procedure User

User

BUS2000126 Business Activity

BUS2000115 Sales

BUS2000116 Service Order/Quotation

10. Choose Save.

SAP Billing and Revenue Innovation Management Integration

SAP S/4HANA Configuration PUBLIC 93
11. Choose Partner Functions in Procedure in the left navigation and choose New Entries:

Entry changea- No.of occur- No.of occur-

Function ble/changeable rence/Minimum rence/Maximum Select.limit Access Sequence

0000001 Sold-To 1 1 0 0001

Party (CRM) Preceding
Document :
Activity Partner
Preceding
Document : Sold-
To Party

00000055 Ship- X 1 1 0 0005

To Party/Service- Preceding
Recepient (CRM) Document
Business Partner
Relationships:
Sold-To Party
Current

0000003 Bill-To X 1 1 0 0005

Party (CRM) Preceding
Document
Business Partner
Relationships:
Sold-To Party
Current

0000004 Payer X 1 1 0 0005

(CRM) Preceding
Document
Business Partner
Relationships:
Sold-To Party
Current

00000014 Em- X 0 5 0 0008

ployee Responsi- Preceding
ble (CRM) Document
User

00000015 Con- X 0 1 0 0005

tact Person Preceding
Document
Business Partner
Relationships:
Sold-To Party
Current

SAP Billing and Revenue Innovation Management Integration

94 PUBLIC SAP S/4HANA Configuration
 Entry changea- No.of occur- No.of occur-
Function ble/changeable rence/Minimum rence/Maximum Select.limit Access Sequence

00000056 Serv- X 0 1 0 0011 Organiza-

ice Employee tional Data: Serv-
Group ice Team Using
Product or Rule

12. Choose Save.

13. Choose User Interface Settings in the left navigation and choose New Entries:

PartnerDetProc: ZCPQ_SQH CPQ Solution Quotation

Header Screen

Partner Function1 0000001: Sold-To Party (CRM)

Partner Fucntion2 0000015: Contact Person (CRM)

Partner Function 3 0000003: Bill-to-Party(CRM)

Partner Function 4 0000014: Employee Responsible(CRM)

Display

Display Variant 0101 Partner number/ Number type /Address

14. Choose Save.

7.9.2 Maintain Organizational Data

1. Access the transaction using the following navigation path:

Transaction code SPRO

SAP IMG menu Service Master Data Organizational Management

Organizational Data Determination Change Rules and
Profiles Maintain Organizational Data Profile

2. In the Change View “Organization Data Profile” : Overview, choose New Entries:

Field Value

Profile ZCPQ_SQ SAP Sales Org.Data Profile (Header)

Scenario SALE Sales

Determination Rules

Organizational Model Determine. Rule: 10000166

Mandatory

Sales Organization X

SAP Billing and Revenue Innovation Management Integration

SAP S/4HANA Configuration PUBLIC 95
 Field Value

Distribution Channel X

Division

Sales Office

Sales Group

3. Choose Save.

7.9.3 Define Transaction Types

1. Access the transaction using the following navigation path:

Transaction code SPRO

SAP IMG menu Service Transactions Basic Settings Define

Transaction Types

2. 2. In the Change View “Definition of Transaction Types”: Overview, Choose New Entries and maintain the
following values:

Field Value

Transaction Type For example, <ZCSQ> CPQ Sol Quotation

General

Description CPQ Sol Quotation

Leading Transaction Category BUS2000116 Service Order/Quotation

Status Object Type

Contract Determination

Inactive

Commitment Date

No Change Documents

Template Type

ATP Type

Trans Classification

Source in a new window

Product Determination

Enter GTIN

Enter Partner Product

Product Description ID Search

SAP Billing and Revenue Innovation Management Integration

96 PUBLIC SAP S/4HANA Configuration
 Field Value

Bundle Explosion

Profiles

Text Det. Procedure SRV00002

Partner Determ. Proc ZCPQ_SQH

Status Profile

Org Data Prof ZCPQ_SQ

Partner Function Org: 0001 Sold-To-Party

Date Profile SRV_Quot

Action Profile Service_Quotation_PROD_PKG

Obj.Rel.Profile

Transaction numbering

No.Range Object CRM_SERVIC CRM Service Process

Int.No.Range.No 01

Ext.No.Range.No

Early No. Assgt

Item Numbering

Increasing Item

IncrementSubItm

Authorization Scope Checks

Authorization Domain

3. Choose Save.
4. In the left navigation, choose Assignment of Business Transaction Categories and choose New Entries

Assignment of Business Transactions Categories

Transaction Category

BUS2000115 Sales

BUS2000116 Service Order/Quot.

BUS2000126 Business Activity

BUS2000265 Subscription Order

5. Choose Save.
6. In the Change View “Definition of Transaction Types”: Overview, Choose New Entries and maintain the
following values:

Field Value

Transaction Type For example, ZCSC CPQ Subs Contract

SAP Billing and Revenue Innovation Management Integration

SAP S/4HANA Configuration PUBLIC 97
 Field Value

General

Description Subscription Contract for CPQ

Leading Transaction Category BUS2000266 Subscription Contract

Status Object Type

Contract Determination

Inactive

Commitment Date Commitment Date is Not Calculated

No Change Documents

Template Type

ATP Type

Trans Classification

Source in a new window

Product Determination

Enter GTIN

Enter Partner Product

Product Description ID Search

Bundle Explosion

Profiles

Text Det. Procedure ORDER001

Partner Determ. Proc ZCPQ_SC

Status Profile

Org Data Prof IST000000001

Partner Function Org: 0001 Sold-To-Party

Date Profile PROVHEADER

Action Profile

Cancellation Proceed ISTC

Transaction numbering

No.Range Object CRM_PRVCTR CRM Service Process

Int.No.Range.No 01

Ext.No.Range.No

Early No. Assgt

Item Numbering

Increasing Item 10

IncrementSubItm 10

SAP Billing and Revenue Innovation Management Integration

98 PUBLIC SAP S/4HANA Configuration
 Field Value

Authorization Scope Checks

Authorization Domain

7. Choose Save.
8. In the left navigation, choose Assignment of Business Transaction Categories and choose New Entries

Assignment of Business Transactions Categories

Transaction Category

BUS2000115 Sales

BUS2000266 Subscription Contr.

9. Choose Save.

 Note

It is recommended to use an own transaction type for the solution quotation and related subscription
contract to avoid that such documents created from SAP CPQ can be changed by any user in SAP
S/4HANA. Create authorizations accordingly for such transaction types, so that a normal user has only
display authorization. Only expert users should have authorization to maintain such documents directly in
SAP S/4HANA.

7.9.4 Define Item Category

A new Item Category for bundle product is needed. This item category is used if a dummy bundle product
is used which then should not create any follow-up documents. Therefore, copy control must be set up
accordingly for this item category to avoid creating a follow-up service order document for this bundle item.
There is no bundle logic in SAP S/4HANA Service, but only existing in SAP CPQ.

1. Access the transaction using the following navigation path:

Transaction code SPRO

SAP IMG menu Service Transactions Basic Settings Define

Item Categories

2. In the Change View “Definition of Item Categories” : Overview, choose New Entries

Field Value

Item Category ZBQI Bundle Item

General

Description Bundle Item (Quotation)

SAP Billing and Revenue Innovation Management Integration

SAP S/4HANA Configuration PUBLIC 99
 Field Value

Object Type Service Product Item

Bundle Explosion X

Profiles

Text Det Proc ORDER001 Sales Order Item

Partner Det Proc SRQP0001 Quotation: Service Item

Org Data Prof 000000000020 SAP Service Item Service

Date Profile: SRV_QUOT SAP Standard Service Quotation

Structure

Structure Scope A Single Level Explosion of Structure

Product

Delivery Group Do not Create Delivery Groups

3. Choose Save.
4. Choose the newly created item category and choose Assignment of Business Transaction Categories in the
left navigation

Assignment of Business Transactions Categories

Transaction Category

BUS2000115 Sales

BUS2000116 Service Order/Quot.

5. Choose Save.
6. Choose BUS2000115 Sales and select Customizing Item from the Dialog Structure.
7. Choose New Entries and maintain the following:

Field Value

Bill. Relevance Not Relevant for Billing

MileStoneBilling No Specific Calculation Type

Int. Billing External

Statist. Value System will copy item to header totals

Pricing. Indicat. Inactive

Pricing Process Standard

Relevance for Quotation 2 Is a Quotation

ATP profile: quote No Availability Check

8. Choose Save.
9. In the Change View “Definition of Item Categories”: Overview, choose all the item categories used
in solution quotation ,for example <PRQR> and maintain Default Configuration as Execute Default
Configuration Automatically.

SAP Billing and Revenue Innovation Management Integration

100 PUBLIC SAP S/4HANA Configuration
7.9.5 Define Item Category Group

New Item Category Group needed for bundle products which should not create a follow-up document, to find a
specific item category (ZQBI).

1. 1. Access the transaction using the following navigation path:

Transaction code SPRO

SAP IMG menu Service Transactions Basic Settings Define Item

Category Group

2. 2. In the “Materials: Item Category Groups in Material Master” screen, choose New Entries and maintain the
following value:

Field Value

ItCtGrp ZQSP

Description Quote Structure Prod

7.9.6 Define Item Category Determination

The Item Category Determination is not supported yest for Sales, Subscription or Service.

1. Access the transaction using the following navigation path:

Transaction code SPRO

SAP IMG menu Service Transactions Basic Settings Define Item

Category Determination

2. In the Item Category Determination: Overview screen, choose New Entries and maintain the following
entries:

Transac- Descrip- Main Desc.itm Desc.Itm Desc.alt.I

tion Type tion ItCGr ItmCat Item Cat. Item Cat. cat. Cty Alt.IC 1 C1

ZCSC CPQ Subs PRRP PRCP Subscr.

Contract Subscr.Us Contract
age only

ZCSC CPQ Subs PRRP PRCP PRCP Subscr.

Contract Subscr.Us Contract
age only

ZCSC CPQ Subs PRRP PRCP PRCP Subscr.

Contract Subscr.Us Contract
age only

SAP Billing and Revenue Innovation Management Integration

SAP S/4HANA Configuration PUBLIC 101
 Transac- Descrip- Main Desc.itm Desc.Itm Desc.alt.I
tion Type tion ItCGr ItmCat Item Cat. Item Cat. cat. Cty Alt.IC 1 C1

ZCSC CPQ Subs PRSR PRCP Subscr.

Contract Subscr.wi Contract
th.Recurr Rec

ZCSC CPQ Subs PRSR PRCP PRCP Subscr.

Contract Subscr.wi Contract
th.Recurr Rec

ZCSC CPQ Subs PRSR PRCP PRCP Subscr.

Contract Subscr.wi Contract
th.Recurr Rec

Transac- Main
tion Descrip- Itm- Item Item Desc.itm Desc.It Desc.alt. Desc.alt.
Type tion ItCGr Cat.Usg Cat. Cat. cat. Alt.IC 1 mCty IC 1 IC 2

ZCSQ CPQ Sol SRQP Service

Quota- Item
tion

ZCSQ CPQ Sol 0002 SRES Sales

Quota- Configu- Item Ext
tion ration Conf

ZCSQ CPQ Sol 0002 SRQP SRES Sales

Quota- Configu- Item Ext
tion ration Conf

ZCSQ CPQ Sol 0002 ZBQI SRES Sales

Quota- Configu- Item Ext
tion ration Conf

ZCSQ CPQ Sol NORM SRQS Sales SRQM Service

Quota- Stand- Item Spare
tion ard Item Item

ZCSQ CPQ Sol NORM PRQR SRQS Sales

Quota- Stand- Item
tion ard Item

ZCSQ CPQ Sol NORM SRQP SRQS Sales SRQM Service

Quota- Stand- Item Spare
tion ard Item Item

ZCSQ CPQ Sol NORM ZBQI SRQS Sales SRQM Service

Quota- Stand- Item Spare
tion ard Item Item

ZCSQ CPQ Sol PRRP PRQP Sub-

Quota- Subscr.U scription
tion sage Item
only

ZCSQ CPQ Sol PRRP PRQP PRQP Sub-

Quota- Subscr.U scription
tion sage Item
only

SAP Billing and Revenue Innovation Management Integration

102 PUBLIC SAP S/4HANA Configuration
 Transac- Main
tion Descrip- Itm- Item Item Desc.itm Desc.It Desc.alt. Desc.alt.
Type tion ItCGr Cat.Usg Cat. Cat. cat. Alt.IC 1 mCty IC 1 IC 2

ZCSQ CPQ Sol PRRP PRQP PRQP Sub-

Quota- Subscr.U scription
tion sage Item
only

ZCSQ CPQ Sol PRRP SRQP PRQP Sub-

Quota- Subscr.U scription
tion sage Item
only

ZCSQ CPQ Sol PRRP ZBQI PRQP Sub-

Quota- Subscr.U scription
tion sage Item
only

ZCSQ CPQ Sol PRSR PRQP Subscr. PRQR Subscr.

Quota- Subscr.w Item Item
tion ith Re- Rec. Rec.
curr

ZCSQ CPQ Sol PRSR PRQP PRQP Subscr.

Quota- Subscr.w Item
tion ith Re- Rec.
curr

ZCSQ CPQ Sol PRSR PRQP PRQP Subscr.

Quota- Subscr.w Item
tion ith Re- Rec.
curr

ZCSQ CPQ Sol PRSR SRQP PRQP Subscr.

Quota- Subscr.w Item
tion ith Re- Rec.
curr

ZCSQ CPQ Sol PRSR ZBQI PRQP Subscr.

Quota- Subscr.w Item
tion ith Re- Rec.
curr

ZCSQ CPQ Sol PRSR PROF Sub-

Quota- Subscr.w scription
tion ith Re- One Off
curr

ZCSQ CPQ Sol PRSR PRQP PROF Sub-

Quota- Subscr.w scription
tion ith Re- One Off
curr

ZCSQ CPQ Sol PRSR PRQP PROF Sub-

Quota- Subscr.w scription
tion ith Re- One Off
curr

SAP Billing and Revenue Innovation Management Integration

SAP S/4HANA Configuration PUBLIC 103
 Transac- Main
tion Descrip- Itm- Item Item Desc.itm Desc.It Desc.alt. Desc.alt.
Type tion ItCGr Cat.Usg Cat. Cat. cat. Alt.IC 1 mCty IC 1 IC 2

ZCSQ CPQ Sol PRSR SRQP PROF Sub-

Quota- Subscr.w scription
tion ith Re- One Off
curr

ZCSQ CPQ Sol PRSR ZBQI PROF Sub-

Quota- Subscr.w scription
tion ith Re- One Off
curr

ZCSQ CPQ Sol SCNP SCNP Service

Quota- Service Contract
tion Cntrct Itm
Prod.

ZCSQ CPQ Sol SCNP SRQP SCNP Service

Quota- Service Contract
tion Cntrct Itm
Prod.

ZCSQ CPQ Sol SCNP ZBQI SCNP Service

Quota- Service Contract
tion Cntrct Itm
Prod.

ZCSQ CPQ Sol SRVE SRQE Expense

Quota-
tion

ZCSQ CPQ Sol SRVE SRQP SRQE Expense

Quota-
tion

ZCSQ CPQ Sol SRVE ZBQI SRQE Expense

Quota-
tion

ZCSQ CPQ Sol SRVM SRQM Service

Quota- Service Spare
tion Material Item

ZCSQ CPQ Sol SRVM SRQP SRQM Service

Quota- Service Spare
tion Material Item

ZCSQ CPQ Sol SRVM ZBQI SRQM Service

Quota- Service Spare
tion Material Item

ZCSQ CPQ Sol SRVP SRQP Service SCNP Service ZBQI Bundle
Quota- Service Item Contract Item
tion Product Itm

ZCSQ CPQ Sol SRVP SRQP SRQP Service SCNP Service

Quota- Service Item Contract
tion Product Itm

SAP Billing and Revenue Innovation Management Integration

104 PUBLIC SAP S/4HANA Configuration
 Transac- Main
tion Descrip- Itm- Item Item Desc.itm Desc.It Desc.alt. Desc.alt.
Type tion ItCGr Cat.Usg Cat. Cat. cat. Alt.IC 1 mCty IC 1 IC 2

ZCSQ CPQ Sol SRVP ZBQI SRQP Service SCNP Service

Quota- Service Item Contract
tion Product Itm

ZCSQ CPQ Sol ZQSP ZBQI Bundle

Quota- Quote Item
tion Struc-
ture
Prod

ZCSQ CPQ Sol ZQSP SRQP ZBQI Bundle

Quota- Quote Item
tion Struc-
ture
Prod

ZCSQ CPQ Sol ZQSP ZBQI ZBQI Bundle

Quota- Quote Item
tion Struc-
ture
Prod

Transac- Main
tion Descrip- Itm- Item Item Desc. Desc. Desc.alt. Desc.alt.
Type tion ItCGr Cat.Usg Cat. Cat. itm cat. Alt. IC 1 ItmCty IC 1 IC 2

ZCSO CPQ 0002 PROS Subscr.

Subs Or- Configu- Ord.
der ration SalesIt

ZCSO CPQ LUMF PRSP Subscr.S

Subs Or- Struc- ales
der ture/ Package
Mat. Be-
low

ZCSO CPQ NORM PROS Subscr.

Subs Or- Stand- Ord.
der ard Item SalesIt

ZCSO CPQ NORM PROP PROS Subscr.

Subs Or- Stand- Ord.
der ard Item SalesIt

ZCSO CPQ NORM PROP PROS Subscr.

Subs Or- Stand- Ord.
der ard Item SalesIt

ZCSO CPQ NORM PRSP PROS Subscr.

Subs Or- Stand- Ord.
der ard Item SalesIt

ZCSO CPQ PRRP PROP Subscr.

Subs Or- Subscr.U Order
der sage Item
only

SAP Billing and Revenue Innovation Management Integration

SAP S/4HANA Configuration PUBLIC 105
 Transac- Main
tion Descrip- Itm- Item Item Desc. Desc. Desc.alt. Desc.alt.
Type tion ItCGr Cat.Usg Cat. Cat. itm cat. Alt. IC 1 ItmCty IC 1 IC 2

ZCSO CPQ PRRP PROP PROP Subscr.

Subs Or- Subscr.U Order
der sage Item
only

ZCSO CPQ PRSR PROP Subscr.

Subs Or- Subscr. Ord.Itm
der With Re- Rec.
curr

ZCSO CPQ PRSR PROP PROP Subscr.

Subs Or- Subscr. Ord.Itm
der With Re- Rec.
curr

ZCSO CPQ PRSR PROP PROP Subscr.

Subs Or- Subscr. Ord.Itm
der With Re- Rec.
curr

ZCSO CPQ PRSR PRSP PROP Subscr.

Subs Or- Subscr. Ord.Itm
der With Re- Rec.
curr

ZCSO CPQ PRSV PROF Subscr.

Subs Or- Subsrip- One Off
der tion Fee Item

ZCSO CPQ PRSV PROP PROF Subscr.

Subs Or- Subsrip- One Off
der tion Fee Item

ZCSO CPQ PRSV PROP PROF Subscr.

Subs Or- Subsrip- One Off
der tion Fee Item

ZCSO CPQ PRSV PRSP PROF Subscr.

Subs Or- Subsrip- One Off
der tion Fee Item

3. Choose Save.

7.9.7 Copying of Transaction Types for Sales Order

In this activity, maintain the copying of transaction types for creating a sales order from solution quote

1. Access the transaction using the following navigation path:

Transaction code SPRO

SAP Billing and Revenue Innovation Management Integration

106 PUBLIC SAP S/4HANA Configuration
 SAP IMG menu Service Transactions à Settings for Solutions
Copying Control for Solution Quotations and Sales
Transactions Define Copying of Transaction Types

2. In the Copying of Transaction Types: General Control: Overview screen, choose New Entries:

Field Value

Transaction Type ZCSQ

Sales Doc Type SRVP

Short Description CPQ Sol Quotation

3. Choose Save.

7.9.8 Define Copying Control for Transaction Types

In this activity, copy control settings for copying and to create a sales order from a solution quotation.

1. Access the transaction using the following navigation path:

Transaction code SPRO

SAP IMG menu Service Transactions Basic Settings Copying

Control for Business Transactions Copying Control for
Transaction Types

2. In the Copying of Transaction Types: General Control: Overview screen, choose New Entries:

Srce Trans. Tgt Trans. Short De- Copy Item Copying Copy PO Copy Price
Type Type scription no. ComplRef routine data Agreement

ZCSQ SC Service Con- <selected>

tract

ZCSQ SRVO Service Or- <selected>

der

ZCSQ ZCSC CPQ Subs <selected>

Contract

ZCSC ZCSO CPQ Subs <selected>

Order

ZCSC ZCSO CPQ Subs <selected> <selected>

Orde

3. Choose Save.

SAP Billing and Revenue Innovation Management Integration

SAP S/4HANA Configuration PUBLIC 107
7.9.9 Define Copying Control for Item Categories

1. Access the transaction using the following navigation path:

Transaction code SPRO

SAP IMG menu Service Transactions Basic Settings Copying

Control for Business Transactions Define Copying
Control for Item Categories

2. In the Copy Item Categories – General Control Data: Overview screen, choose New Entries:

Field Value

Source Item Cat PRQR

Target item cat.: PRCR

Copy Item Categories – General Control Data

Description: Subscr. Contract Rec

Copying routine:

Copy conditions: D Copy all conditions

Reexplode Structure/Free goods:

Copy Configuration: B Copy Configuration from Source Item

Fix:

Copy PO data:

Generate prod.master data again:

Price Agreements:

Copy Survey:

Copy Campaigns

3. Choose Save.

7.9.10 Subscription specific customizing

SAP Billing and Revenue Innovation Management Integration

108 PUBLIC SAP S/4HANA Configuration
7.9.10.1 Define Settings for Item Categories

1. Access the transaction using the following navigation path:

Transaction code SPRO

SAP IMG menu Service Transactions Settings for Subscription

Transactions Define Settings for Item Categories

2. In the Subscription-Specific Customizing of Item Categories: Overview screen, choose New Entries:

Show Show Al- Enable Rec. in

Item.Cat. Use Disc. Counter low One-off Split Qty Obj list Def. Distr CC

PRQR X X X

3. Choose Save.

7.9.10.2 Define Settings for Transaction Types

1. Access the transaction using the following navigation path:

Transaction code SPRO

SAP IMG menu Service Transactions Settings for Subscription

Transactions Define Settings for Transaction Types

2. In the Subscription Order Settings: Overview screen, choose New Entries and maintain the following values:

Contract Ac-
Short Descrip- count Assign-
Trans.Type tion ment CurrTmeSls CurrTme Chg DocPurpose Tgt Trans. type

ZCSQ CPQ Sol Quo- X X C Set current C Solution ZCSC

tation Time Stamp Quotation
and Enable Ac-
tivation Time
field

ZCSC CPQ Subs X X Standard Sub- ZCSO

Contract scription Order

ZCSO CPQ Subs Or- X X C Set current Standard Sub- ZCSC

der Time Stamp scription Order
and Enable Ac-
tivation Time
field

3. Choose Save.

SAP Billing and Revenue Innovation Management Integration

SAP S/4HANA Configuration PUBLIC 109
7.9.10.3 Define Settings for Documentation Distribution

1. Access the transaction using the following navigation path:

Transaction code SPRO

SAP IMG menu Service Transactions Settings for Subscription

Transactions Document Distribution Define Settings
for Document Distribution

2. In the Schema Determination screen, maintain the following values:

Document Distr.De-
Trans.Type Short Description Item.Cat. Description termination Class

ZCSC CPQ Subs Contract PRCP Subscr Contract CL_CRM_ISX_OR-

DER_MD_DET_DFLT

ZCSC CPQ Subs Contract PRCR Subscr. Contract Rec CL_CRM_ISX_OR-

DER_MD_DET_DFLT

3. 3. Choose ZCSC Subscr Contract and Item category PRCP and further choose Schema Assignment in the
left navigation to maintain the following values:

Schema Assignment

Schema Document Distribution Schema Default

PCAL Subscription Contract with Allowance

PCLK Subscription Contract Lock Unlock

PERP Subscription Contract Distribution X

4. 4. Choose ZCSC Subscr Contract entry and Item Category PRCR and further choose Schema Assignment
in the left navigation to maintain the following values:

Schema Assignment

Schema Document Distribution Schema Default

PCER Subscription Contract Early Distribu-

tion

PCLK Subscription Contract Lock Unlock

PERP Subscription Contract Distribution X

PPCM Subscription Contract Dist with CC

Recur

5. Choose Save.

SAP Billing and Revenue Innovation Management Integration

110 PUBLIC SAP S/4HANA Configuration
7.9.10.4 Define Billing Cycle Determination Rules

In this activity a billing cycle determination rule is defined. This is needed to allow several billing cycles for a
product, so that the user in CPQ can select the relevant billing cycle. This billing cycle determination rule must
be assigned to the product. In addition, a default billing cycle can be assigned in the product.

1. Access the transaction using the following navigation path:

Transaction code SPRO

SAP IMG menu Service Transactions Settings for Subscription

Transactions Recurring Fees Configure settings using
Billing Plans with Convergent Invoicing Define Billing
Cycle Determination Rules

2. In the “Billing Cycle Determination Rules Maintenance”: Overview screen, maintain the following values:

Billing Cycle
Determination
Billing Cy Description Default Cycle Billing Cycle Text Class

ZCPQ Test CPQ Integra- CL_CRMS4_SOM

tion _BC_RULE_EX-
AMPLE

3. Choose Save.

7.9.10.5 Define settings for Billing Plan Item Type

1. Access the transaction using the following navigation path:

Transaction code SPRO

SAP IMG menu Service Transactions Settings for Subscription

Transactions Recurring fees Configure Settings for
Recurring Fees with Billing Plans Assign Billing Plan and
Billing Plan Item Types

2. Choose New Entries, maintain the following values:

Billing Plan Item One-Off Billing Plan

Trans.Type Item Category Billing Plan Type Type Item Type

ZCSC PRCP SBPR CBPI1 CBPIO

ZCSC PRCR SBPR CBPI1 CBPIO

SAP Billing and Revenue Innovation Management Integration

SAP S/4HANA Configuration PUBLIC 111
7.9.10.6 Assign Billing Plan Type to Item Category

1. Access the transaction using the following navigation path:

Transaction code SPRO

SAP IMG menu Service Transactions Basic Settings Billing Plan

Assign Billing Plan Type to Item Category

2. Choose “New Entries”, maintain the following values:

Trans.Type Item Category Billing Plan Type OnlyItemBillPlan

ZCSQ SCNP 02 <Selected>

3. Choose Save.

7.10 Maintain Service Profile

1. Access the transaction using the following navigation path:

Transaction code SPRO

SAP IMG menu Service Transactions Settings for Service

Transactions Define Availability and Response Times

2. In the Change View “Service Profile”: Overview, choose New Entries and maintain Service Profile as SRV01
and Description as Service Profile 1.
3. Choose the Availability Times against SRV01.
4. Select the Rule under General Rule as W Weekly Periodic Availability Times.
5. Select the Week Rule under Weekly as 1 every week on.
6. Choose Mo and maintain from 8:00 – 5:00 Hrs UTC UTC+0.
7. Choose Tu and maintain from 8:00 – 5:00 Hrs UTC UTC+0.
8. Choose We and maintain from 8:00 – 5:00 Hrs UTC UTC+0.
9. Choose Th and maintain from 8:00 – 5:00 Hrs UTC UTC+0.
10. Choose Fr and maintain from 8:00 – 5:00 Hrs UTC UTC+0.
11. Choose Copy.
12. Choose Save.

SAP Billing and Revenue Innovation Management Integration

112 PUBLIC SAP S/4HANA Configuration
7.11 Maintain Response Profile

1. Access the transaction using the following navigation path:

Transaction code SPRO

SAP IMG menu Service Transactions Settings for Service

Transactions Define Availability and Response Times

2. In the Dialog structure, choose Response Profile and choose New Entries.
3. Maintain Response Profile for example as <RESP01> and Description for example as <Response Profile
1>.
4. Select Priority under Active Fields for the selection of Response Times.
5. Choose Save.
6. Select the above created Response Profile, and choose Indicators for Response times.
7. Choose New Entries and maintain the Priority and description values for example as, <1>, <3> and <very
high>, <high> respectively.
8. Choose Save.

7.12 Activate Services

 Note

General information about the needed services can be found in SAP Business Accelerator Hub .

7.12.1 OData V2 services

Following services must be activated in your Fiori Server with a system alias pointing to your S/4 system. Start
transaction /n/IWFND/MAINT_SERVICE and add following services:

• API_BUS_SOLUTION_QUOTATION_SRV
• API_SUBSCRIPTIONCONTRACT
• APL_LOG_MANAGEMENT_SRV

These are only services needed for the integration. If you use Fiori launchpad to maintain products, business
partners, etc. additional services must be activated.

SAP Billing and Revenue Innovation Management Integration

SAP S/4HANA Configuration PUBLIC 113
7.12.2 OData V4 services

Create a service binding for service API_CHANGEPROCESSGROUP. This can be done by using report /IWFND/
R_V4_ADMIN_PUBLISH_SERV

Further details how to publish a service group for OData V4 services can be found in documentation.

7.13 Periodic jobs

You must schedule report RSPPFPROCESS as a periodic batch job with following parameters:

• Action Definition: CRMS4_SOM_PROCESS_CHANGE_QUOTE

• Action Status: 0
• Set indicator “Processing Without Dialog”

This is needed that asynchronous change processes are executed and the status in CPQ is updated
accordingly.

SAP Billing and Revenue Innovation Management Integration

114 PUBLIC SAP S/4HANA Configuration
8 Setup SAP Event Mesh

8.1 Configuration in SAP Event Mesh for Sending Quote

from SAP CPQ to SAP S/4HANA

The prepackaged integration content uses the SAP Event Mesh to process events for the quote integration
from SAP CPQ to SAP S/4HANA and for the change contract processing status from SAP S/4HANA to SAP
CPQ. In both cases the sending system does not send the complete document but only a notification about a
create or change as an event. These events are stored in queues in SAP Event Mesh and are picked up from
there by the respective integration flows via AMQP protocol. To increase the stability of the integration both
integrations use a retry mechanism to reprocess the event in case of temporary processing errors. To enable
this retry mechanism both integrations use a so-called retry-queue in addition to the main processing queue.
For the initial setup of SAP Event Mesh please refer to the link to create the Event Mesh Service Instance.

The following steps describe how to enable the event processing in SAP Event

1. Create Service Key: In the SAP BTP Cockpit navigate to the details of the Event Mesh instance and Create
a service key. Provide a service key name, leave the field for the parameters in JSON format empty and
choose Create.
2. Create Queue for the Business Solution Quote events in SAP Event Mesh:
To process the events from SAP CPQ a queue needs to be created in SAP Event Mesh.
1. Navigate to your Cloud Foundry space and select your Event Mesh service instance.
2. In the left pane, select Service Instances.
3. Choose Open Dashboard under the list of Actions that correspond to your Event Mesh service instance.
4. In the messaging administration page, select Message Clients, select the Message Client that was created
when the instance was created in BTP cockpit.
5. Select the Queues tab and choose the Create Queue.
6. Enter the queue name.
7. Select the Access Type as EXCLUSIVE.
8. Leave all other values as suggested.

The integration flow is using a retry mechanism in case of a temporary error (example, a system is no
reachable). For this a so-called retry queue is used in SAP Event Mesh.

1. Navigate to your Cloud Foundry space and select your Event Mesh service instance.
2. In the left pane, select Service Instances.
3. Choose Open Dashboard under the list of Actions that correspond to your Event Mesh service instance.
4. In the messaging administration page, select Message Clients, select the Message Client that was created
when the instance was created in SAP BTP cockpit.
5. Select the Queues tab and choose the Create Queue.
6. For the queue name use the same name you used for the queue created above and add “Retry” at the end
of the name.

SAP Billing and Revenue Innovation Management Integration

Setup SAP Event Mesh PUBLIC 115
7. In the drop-down box for “Dead Message Queue” select the queue you created above.
8. Activate “Respect Time to Live in seconds”.
9. Set parameter “Max Time to Live” to 18000. If you require a higher interval than 5 hours between retries in
the message processing you can increase this parameter. This parameter sets the maximum time between
retries, the actual time can be configured in the integration flow.

8.2 Configuration in SAP CPQ

The following steps describe the setup in SAP CPQ:

1. Login to SAP CPQ with Admin credentials

2. Navigate to the Setup of SAP CPQ instance
3. Choose Providers and choose Subscription to Events
4. Select Add new Subscription to Event
5. Enter the following Information
• Name: for example, <Quote_to_S4>
• Description: For example, <send quote to S/4>
• Webhook URL: For example, <https://enterprise-messaging-pubsub.cfapps.sap.hana.ondemand.com/
messagingrest/v1/queues/<queue-name>/messages>
Where queue-name needs to be URL-encoded, for example <company/CPQQuote/queue/Quote”
needs to be entered as “company%2FCPQQuote%2Fqueue%2FQuote>
• Webhook HTTP method: POST
• Event Name: QuoteEvent
• Quote event: OnPlaceOrder
• Authentication Type: OAuth
• Authenticaiton URL: URL from entry tokenendpoint of section with protocol “httprest” in SAP BTP
Service Key of the Event Mesh instance
• Authentication HTTP method: POST
• Send Credentials Through: Body
• Client ID: ClientID from entry tokenendpoint of section with protocol “httprest” in SAP BTP Service Key
of the Event Mesh instance
• Client Secret: ClientSecret from entry tokenendpoint of section with protocol “httprest” in SAP BTP
Service Key of the Event Mesh instance
• Add customer header entry by choosing link “Add custom header entry”
Key: x-qos
Value: 1
6. Save Settings

SAP Billing and Revenue Innovation Management Integration

116 PUBLIC Setup SAP Event Mesh
8.3 Configuration for processing of Change Contract
Processing Status

Create an instance in EMS and create a service key similar to the previous topic.

When a change quote is processed in SAP S/4 HANA the single line items are processed separately and trigger
events with their processing status. These events are send to SAP Event Mesh and from there trigger the
integration flow in SAP Cloud Integration for the update of the Quote in SAP CPQ. The Setup steps for this
integration are described below.

Create another instance in SAP Event Mesh and create a service key similar as described for the send process
from CPQ to SAP S/4HANA.

In SAP S/4HANA create a channel configuration to send the events .

1. Execute transaction /n/IWXBE/CONFIG.

2. Choose the via Service Key (Create new channel via Service Key) button.
3. Enter the following:
1. Channel for example, < EM_S4H_CPQ_ProcStatus>
2. Description for example, < Connection to SAP Event Mesh for change contract processing status>
3. Destination Enter your preferred RFC destination name, the RFC destination will be created
automatically, for example, <EM_S4H_CPQ_ProcStatus>.
4. OAuth 2.0 Configuration Enter your preferred name. The name must not have been used yet, OAuth2.0
Configuration will be created automatically for example, < EM_S4H_CPQ_ProcStatus>
4. Enter the JSON coding for the service key created in SAP BTP Cockpit for integration from SAP S/4
HANAto SAP CPQ.
5. Choose Save configuration or press Enter.
6. If the Channel is not active, activate it.
This step creates the configuration in SAP S/4HANA including the RFC-Destination to connect to SAP
Event Mesh and the OAuth 2.0 configuration.

8.4 Maintain Event Topics

After a channel has been created, the topic for the Business Solution Quote needs to be assigned to the
channel. This is required to publish events for processes Business Solution Quotes to the corresponding SAP
Enterprise Messaging instance. Each event is assigned to one topic.

1. In transaction SPRO, open the SAP Reference IMG and execute transaction /IWXBE/OUTBOUND_CFG.
2. Once you have created a channel, you must configure outbound binding for the BusinessSolutionQuotation
to enable sending events. To do so, proceed as follows:
• Press the Outbound Bindings button.
• Choose an active channel from the list and press New Outbound Binding.
• In the list of outbound bindings for the selected channel, select the topic „sap/s4/beh/
businesssolutionquotation/v1/BusinessSolutionQuotation/Processed/v1”. Choose Save configuration
or press Enter.

SAP Billing and Revenue Innovation Management Integration

Setup SAP Event Mesh PUBLIC 117
8.5 Create Queue for the Business Solution Quote events in
SAP Event Mesh

To process the events from SAP S/4HANA a queue and a subscription to the topic created in SAP S/4HANA
need to be created in SAP Event Mesh.

1. Navigate to your Cloud Foundry space and select your Event Mesh service instance.
2. In the left pane, select Service Instances.
3. Choose Open Dashboard under the list of Actions that correspond to your Event Mesh service instance.
4. In the messaging administration page, select Message Clients, select the Message Client that was created
when the instance was created in SAP BTP cockpit
5. Select the Queues tab and press the Create Queue button
6. Enter the queue name, leave all other values as suggested
7. In the Queue List under Actions for the newly created Queue select Queue Subscriptions
8. For the Topic enter the topic to subscribe to. The topic name consists of the following parts:
<Message Client Namespace>/ce/sap/s4/beh/businesssolutionquotation/v1/
BusinessSolutionQuotation/Processed/v1 where the <Message Client Namespace> is displayed in the
overview of the Message Client in the upper left.

The integration flow is using a retry mechanism in case of a temporary error (e.g. a system is no reachable). For
this a so-called retry queue is used in SAP Event Mesh.

1. Navigate to your Cloud Foundry space and select your Event Mesh service instance.
2. In the left pane, select Service Instances.
3. Choose Open Dashboard under the list of Actions that correspond to your Event Mesh service instance.
4. In the messaging administration page, select Message Clients, select the Message Client that was created
when the instance was created in SAP BTP cockpit.
5. Select the Queues tab and choose the Create Queue button.
6. For the queue name use the same name you used for the queue created above and add “Retry” at the end
of the name.
7. In the drop-down box for “Dead Message Queue” select the queue you created above.
8. Activate “Respect Time to Live in seconds”.

Set parameter “Max Time to Live” to 18000. If you require a higher interval than 5 hours between retries in the
message processing you can increase this parameter. This parameter sets the maximum time between retries,
the actual time can be configured in the integration flow.

SAP Billing and Revenue Innovation Management Integration

118 PUBLIC Setup SAP Event Mesh
9 SAP Cloud Integration Configuration

Before the integration flow can be used, it must be copied to the local customer environment and configured.
During this configuration, the integration flow is adapted to the integration environment by providing system
details of the sending and receiving system.

9.1 Creating User Credentials in SAP Cloud Integration

System

1. Log on to the tenant management node of the SAP Cloud Integration system with the URL http://
<tenant management node URL>/itspaces.
2. Choose Monitor from left navigation bar.
3. Navigate to Manage Security section and choose Security Material.
4. Choose Create and select User Credentials.
5. Enter the following details for user of SAP CPQ.

 Note

For Client Certificate Authenticaton using the Access Token, there is no need to create credentials.
Follow the steps mentioned in Client Certificate Authentication - SAP Cloud Integration Configuration
[page 120].

Field Value

Name For Example, <COM_USER_CPQINT>

Type User Credentials

User Communication user maintained in CPQ # Domain of SAP

CPQ system.

For basic authentication using the access token, create

the following credentials:
1. OLD tenant url is configured, for example,
<COM_USER_CPQINT#SAPIEE_OP_TEST>
2. NEW tenant URL (domain NOT required) is config-
ured, for example, <COM_USER_CPQINT>

Password Enter the password maintained for the communication

user in SAP CPQ system.

6. Choose Deploy.
7. Choose Create and select User Credentials.

SAP Billing and Revenue Innovation Management Integration

SAP Cloud Integration Configuration PUBLIC 119
8. Enter the following details for user of SAP Billing and Revenue Innovation Management.

Field Value

Name For Example, <CPQS4HINTEG>

Type User Credentials

User For example, <CPQS4HINTEG>

Password Enter the password of user CPQS4HINTEG

9. Choose Deploy.
10. Enter the Following details to create credentials for EMS:

Field Name Value

Name For Example, <EMSINT>

Grant Type Client Credentials

Description For example, <Integration with EMS>

Token Service URL Tokenendpoint from the service key for oa2 and protocol
amqp10ws

Client ID Clientid from the service key of EMS

Client Secret Client Secret from the service key of EMS

Client Authentication Send as Request Header

11. Choose Deploy.

9.2 Client Certificate Authentication - SAP Cloud

Integration Configuration

1. Log on to the tenant management node of the SAP Cloud Integration system with the URL http://
<tenant management node URL>/itspaces.
2. Choose Monitor from the left navigation bar.
3. Navigate to Manage Security section and choose Keystore.
4. Click on Add and Select Key Pair.
5. Enter the Alias name for the certificate and select the pfx or p12 certificate to upload.

 Note

Note that SAP Cloud Integration requires certificate in *.p12 & *.pfx file format for uploading the Key
Pair certificate. The certificate uploaded in SAP CPQ should be used to generate files in the *.p12 &
*.pfx file format.

6. Enter the Password for the uploaded *.p12 & *.pfx certificate file and click Add.
7. Verify under Entries that the certificate key pair uploaded in added.

SAP Billing and Revenue Innovation Management Integration

120 PUBLIC SAP Cloud Integration Configuration
9.3 View Prepackaged integration flows using SAP Cloud
Integration Web UI

To import and deploy integration flows, AuthGroup.IntegrationDeveloper role is to be assigned in the tenant.

Upload SAP CPQ SSL Certificates in SAP Cloud Integration.

1. Access the SAP Cloud Integration Web UI from the provisioning e-mail. It should be in the format: http://
<tenant management node URL>/itspaces.
2. On the Discover tab, you should be able to view all pre-packaged integration flows delivered by SAP.
3. Choose the package SAP CPQ - Quote 2.0 Integration with SAP Billing and Revenue Innovation
Management. All the artifacts of this package will be displayed when Artifacts is selected.

9.4 Configure and Deploy the integration flow using SAP

Cloud Integration Web UI (Replication from SAP CPQ to
SAP Billing and Revenue Innovation Management)

1. Connect to the tenant management node of the SAP Cloud Integration system with the URL: http://
<tenant management node URL>/itspaces.
2. On the Discover tab, select the package for example, SAP CPQ - Quote 2.0 Integration with SAP Billing and
Revenue Innovation Management.
3. Choose Artifacts to view all the integration flows related to this integration package.
4. Choose Copy on the right top corner to copy it to design area.

 Note

If the Integration package were being created for the first time, then you would see the message
‘Integration Package Created’. If not, you will see the below dialog box asking to either Create a new
copy of the package or to Overwrite the existing integration package content. Choose Overwrite

5. Select the Design mode in left navigation bar.

6. Package is now visible in the design area and can be configured.

9.5 Configuration of the integration flow “Replicate Quote

2.0 from SAP CPQ to SAP S/4HANA”

1. Select the Integration Package copied.

2. Choose Artifacts tab of the package to view list of integration flows.
3. Choose the Actions symbol beside the integration flow, for example, <Replicate Quote 2.0 from SAP
CPQ to SAP S4HANA> .

SAP Billing and Revenue Innovation Management Integration

SAP Cloud Integration Configuration PUBLIC 121
4. Choose Configure.
5. The configuration is explained in the following topics. Configuration of the sender system (In this case,
SAP CPQ) and the receiver system (In this case, SAP Billing and Revenue Innovation Management) and
additional information.
6. Choose Save after completing configuration in a tab.
7. Choose Deploy after completion of whole configuration.

9.5.1 Sender Tab

Field Value

Sender SAPEventMesh

Adapter Type AMQP

Host EMS Host, for exam-

ple, <enterprise-messaging-messaging-
gateway.cfapps.sap.hana.ondemand.com>

Port 443

Path /protocols/amqp10ws

Credential Name Credentials created above for SAP Event Mesh. For example,
<EMSINT>

Queue Name Path Created in SAP Event Mesh for example, <queue:sap/
EMSINT/CPQUID/CPQQuote>

Number of Concurrent Processes 1

9.5.2 Receiver Tab

The receivers can be configured individually by choosing from the receiver dropdown.

 Note

For communication from SAP Cloud Integration to SAP CPQ, the latest released integration flow can be
configured to use either Basic or Client Certificate Authentication. This authentication mechanism uses the
Access Token fetched from the respective SAP CPQ Token API.

Field Value

Receiver • SAP_CPQ_ACCESS_TOKEN_API

Adapter Type HTTP

SAP Billing and Revenue Innovation Management Integration

122 PUBLIC SAP Cloud Integration Configuration
 Field Value

SAP CPQ Host URL of the SAP CPQ host. For example,
<www.webcomcpq.com>

Authentication For Basic Authentication using the Access Token select None
from the dropdown.

 Note
Make sure that the Credentials – “CPQCredentials” is
created in SAP Cloud Integration.

For Client Certificate Authentication select Client Certificate

from the dropdown then provide Private Key Alias of the
certificate.

Field Value

Receiver • SAP_CPQ
• SAP_CPQ_2

Adapter Type HTTP

SAP CPQ Host URL of the SAP CPQ host. For example,
<www.webcomcpq.com>

Field Value

Receiver • SAP_S4

Adapter Type HTTP

S4_Host Logical Port of the SAP Billing and Revenue Innovation Man-
agement system. For example, <abc:443>

SAP-Client SAP Client in following format: sap client=<client number>.

For example,<sap-client=650>

Proxy Type On-Premise

Authentication Basic

Credential Name User Credentials created for SAP S/4HANA. For example,
<CPQS4HINTEG>

Field Value

Receiver Quote2OrderPostProcessingExit

Adapter Type Process Direct

Address Endpoint URL. For example, </CPQ/S4/

Quote2Order_PostExit>

SAP Billing and Revenue Innovation Management Integration

SAP Cloud Integration Configuration PUBLIC 123
Field Value

Sender SAPEventMeshRetry

Adapter Type AMQP

Host SAP Event Mesh Host, for ex-

ample, <enterprise-messaging-messaging-
gateway.cfapps.sap.hana.ondemand.com>

Port 443

Path /protocols/amqp10ws

Credential Name Credentials created for SAP Event Mesh, <EMSINT>

Queue Name Path Created in SAP Event Mesh for example,

<queue:sap/EMSINT/CPQUID/CPQQuoteRetry>

Expiration Period (in s) 3600

9.5.3 More Tab

Field Value

Type Choose All Parameters

BilltoPartyKey Key of the Bill to Party role in SAP Billing and Revenue Inno-
vation Management, For example, <BP>

ContactPersonKey Key of the Contact Person role in SAP Billing and Revenue
Innovation Management, For example, <CP>

enableLog Set true to enable log files, false to disable logs. Default value
is false

Extension Implemented By using an extension, it is possible to call a customer-spe-

cific integration flow in the Extension subprocess. Default
value is false.

PayerPartyKey Key of the Payer Party role in SAP Billing and Revenue Inno-
vation Management, For example, <PY>

S4_Division Division to which the products are assigned in the SAP

Billing and Revenue Innovation Management. For example,
<10>

S4_Language Language of the SAP Billing and Revenue Innovation Man-

agement system. For example, <EN>

S4_SolutionQuotationType Solution Quotation type of the SAP Billing and Revenue Inno-
vation Management system. For example, <ZCSQ> (Trans-
action Type that is created in Chapter Define Transaction
Type)

S4_VariantCondition Name of the variant condition for SAP Billing and Revenue
Innovation Management system. For example, <VARCOND>

SAP Billing and Revenue Innovation Management Integration

124 PUBLIC SAP Cloud Integration Configuration
 Field Value

SalesRepresentativeKey Key of the Sales representative role in SAP Billing and Reve-
nue Innovation Management, For example, <SR>

ShiptoPartyKey Key of the Ship to Party role in SAP Billing and Revenue
Innovation Management, For example, <SH>

SoldtoPartyKey Key of the Sold to Party role in SAP Billing and Revenue
Innovation Management, For example, <SP>

CPQ_Domain If using the old tenant URL, enter the CPQ Domain name.

For new tenant URL, domain name is not required. Leave it

blank.

CPQCredentials For Basic Authentication using Access Token make sure that
the credentials are created in SAP Cloud Integration Config-
uration.

S4_SolutionQuote_CREATE_ONLY Set true to ONLY "CREATE" Solution Quotation in SOM. De-

fault value is false or blank

9.5.4 Deployment

1. Choose Deploy after all the above configurations are done.

2. Choose Monitor from the left navigation bar.
3. Choose All from Manage Integration Content.
4. Check if the deployment was successful. The status should be started and an endpoint URL is displayed.

9.5.5 Extension Implemented

This field allows to make changes to the integration flow without changing the standard integration flow. To
do this, set the parameter Extension Enabled in the integration flow configuration to true and configure the
endpoint Address. This enables the user to call a custom integration flow in the respective section of the
standard integration flow.

The Inbound Adapter is Process Direct and automatically retrieves the endpoint URL value
that was entered during the integration flow configuration for the receiver. For example,
<Quote2OrderPostProcessingExit>.

By calling a customer-specific integration flow, the customer can make changes to the integration flow without
touching the standard integration flow logic (e.g. to add mapping for Custom Fields).

The extension integration flow has to be created in the same integration package as the integration flow that
calls it. For the integration flow for example, Replicate Quote 2.0 from SAP CPQ to SAP S4HANA the input
message for the external integration flow is a concatenation of the mapping result and the original (unmapped)
values for the Quote Header and the Quote Items.

SAP Billing and Revenue Innovation Management Integration

SAP Cloud Integration Configuration PUBLIC 125
Please note that the interface definitions in the extension integration flow mapping have to match the mapping
in the main integration flow, especially for the outbound format. Therefore, please download the corresponding
XSD files from the Resource section of the standard integration flow and upload them in the customer-specific
extension integration flow.

9.6 Configuration for integration flow “Replicate Product

from SAP S/4HANA”

1. Select the Integration Package copied.

2. Choose Artifacts tab of the package to view list of integration flows.
3. Choose the Actions symbol beside the integration flow, for example, <Replicate Product from SAP
S/4HANA>.
4. Choose Configure.
5. The configuration is explained in the following topics. Configuration of the sender system (In this case,
SAP Billing and Revenue Innovation Management) and the receiver system (In this case, SAP CPQ) and
additional information.
6. Choose Save after completing configuration in a tab.
7. Choose Deploy after completion of whole configuration.

Features

Basic data long text from SAP S/4HANA Product Master will be replicated as a description in the SAP CPQ
Product setup page without any character restrictions.

9.6.1 Sender Tab

Field Value

Sender S4HANA

Adapter Type SOAP

Address integration flow endpoint, For example, </S4/CPQ/

ProductReplicateRequest_Out>

Authorization User Role

User Role ESBMessaging.send

SAP Billing and Revenue Innovation Management Integration

126 PUBLIC SAP Cloud Integration Configuration
9.6.2 Receiver Tab

The receivers can be configured individually by choosing from the receiver dropdown.

 Note

For communication from SAP Cloud Integration to SAP CPQ, the latest released integration flow can be
configured to use either Basic or Client Certificate Authentication. This authentication mechanism uses the
Access Token fetched from the respective SAP CPQ Token API.

Field Value

Receiver • SAP_CPQ_ACCESS_TOKEN_API

Authentication For Basic Authentication using the Access Token select

None from the dropdown. Make sure that the Credentials
– “CPQCredentials” is created in SAP Cloud Integration.

For Client Certificate Authentication select Client Certificate

from the dropdown then provide Private Key Alias of the
certificate.

Field Value

Receiver CPQ

Adapter Type SOAP

Address For example, <https://<SAP CPQ Host>/wsAPI/

wssrv.asmx>,www.webcomcpq.com is the SAP CPQ
Host

SAP CPQ Host For example, <www.webcomcpq.com>, without http

protocol in front

Proxy Type Internet

Authentication
None

 Note
Authentication type is already selected in previous sec-
tion under SAP_CPQ_ACCESS_TOKEN_API.

Timeout in ms 60000

Allow Chunking Selected

Field Value

Receiver MaterialReplicationPostExit

Adapter Type Process Direct

SAP Billing and Revenue Innovation Management Integration

SAP Cloud Integration Configuration PUBLIC 127
Field Value

Address Endpoint URL. For example,</S4/CPQ/

ProductReplicateRequest_Out_PostExit>

9.6.3 More Tab

Field Value

Type Select All Parameters from the dropdown

EnableLog Set true to enable log files, false to disable logs. Default value
is false

Extension Implemented By using an extension, it is possible to call a customer-spe-

cific integration flow in the Extension subprocess. Default
value is false

CPQ_Domain CPQ_Domain If using the old tenant URL, enter the CPQ
Domain name.

For new tenant URL, domain name is not required. Leave it

blank.

CPQCredentials For Basic Authentication using the Access Token make sure
that the credentials are created in SAP Cloud Integration
Configuration.

9.7 Configuration for integration flow “Replicate Business

Partner from SAP Master Data Integration”

1. Select the Integration Package copied.

2. Choose Artifacts tab of the package to view list of integration flows.
3. Choose the Actions symbol beside the integration flow, for example, <Replicate Business Partner
from SAP Master Data Integration> .
4. Choose Configure.
5. The configuration is explained in the following topics. Configuration of the sender system (In this case,
SAP Billing and Revenue Innovation Management) and the receiver system (In this case, SAP CPQ) and
additional information.
6. Choose Save after completing configuration in a tab.
7. Choose Deploy after completion of whole configuration.

SAP Billing and Revenue Innovation Management Integration

128 PUBLIC SAP Cloud Integration Configuration
9.7.1 Receiver Tab

The receivers can be configured individually by choosing from the receiver dropdown.

 Note

For communication from SAP Cloud Integration to SAP CPQ, the latest released integration flow can be
configured to use either Basic or Client Certificate Authentication. This authentication mechanism uses the
Access Token fetched from the respective SAP CPQ Token API.

Field Value

Receiver • SAP_CPQ_ACCESS_TOKEN_API

Authentication For Basic Authentication using the Access Token select

None from the dropdown. Make sure that the Credentials
– “CPQCredentials” is created in SAP Cloud Integration.

For Client Certificate Authentication select Client Certificate

from the dropdown then provide Private Key Alias of the
certificate.

Field Value

Receiver CPQ

Adapter Type HTTP

Address SAP CPQ API for creating new Business Partner.

For example, <https://<SAP CPQ Host>/api/
businesspartner/v1/businesspartner> for
the API Endpoint /api/businesspartner/v1/
businesspartner

SAP CPQ Host For example, <www.webcomcpq.com>

Field Value

Receiver BusinessPartnerReplicationProcessingExit

Adapter Type Process Direct

Address Endpoint URL. For example, </S4/CPQ/

BusinessPartnerReplicate_PostExit >

SAP Billing and Revenue Innovation Management Integration

SAP Cloud Integration Configuration PUBLIC 129
9.7.2 More Tab

Field Value

Type Select All Parameters from the dropdown

CPQCredentials User Credentials created for SAP CPQ. For example,

<COM_USER_CPQINT>

Post Processing Extensions Implemented By using an extension, it is possible to call a customer-spe-

cific integration flow in the Extension subprocess. Default
value is false

9.8 Configuration for integration flow “Read Subscription

contract header from SAP Billing and Revenue
Innovation Management”

1. Select the Integration Package copied.

2. Choose Artifacts tab of the package to view list of integration flows.
3. Choose the Actions symbol beside the integration flow, for example, <Read Subscription contract header
from SAP Billing and Revenue Innovation Management >.
4. Choose Configure.
5. The configuration is explained in the following topics. Configuration of the receiver system (In this case,
SAP S4) and additional information.
6. Choose Save after completing configuration in a tab.
7. Choose Deploy after completion of whole configuration.

9.8.1 Receiver Tab

The receivers can be configured individually by choosing from the receiver dropdown.

Fields Name Value

Receiver S4

Adapter Type HTTP

Change_Process_Group For example, < http://sap-client:443/sap/opu/odata/sap/

API_SUBSCRIPTIONCONTRACT>

Credential Name Credentials for S4 system for example, <CPQS4HINTEG>

SAP Billing and Revenue Innovation Management Integration

130 PUBLIC SAP Cloud Integration Configuration
9.8.2 More Tab

Field Name Value

Type Select All Parameters from the dropdown

Sap_Client_Value Client Id for example, <650>

9.9 Configuration for integration flow “Read Subscription

contract items from SAP Billing and Revenue
Innovation Management”

1. Select the Integration Package copied.

2. Choose Artifacts tab of the package to view list of integration flows.
3. Choose the Actions symbol beside the integration flow, for example, < Read Subscription contract items
from SAP Billing and Revenue Innovation Management>.
4. Choose Configure.
5. The configuration is explained in the following topics. Configuration of the receiver system (In this case,
SAP S4) and additional information.
6. Choose Save after completing configuration in a tab.
7. Choose Deploy after completion of whole configuration.

9.9.1 Receiver Tab

The receivers can be configured individually by choosing from the receiver dropdown.

Field Name Value

Receiver S4

Adapter Type HTTP

Subscription_Contract For example, < http://sap-client:443/sap/opu/odata/sap/

API_SUBSCRIPTIONCONTRACT>

Credential Name Credentials for S4 system for example, <CPQS4HINTEG>

SAP Billing and Revenue Innovation Management Integration

SAP Cloud Integration Configuration PUBLIC 131
9.9.2 More Tab

Field Name Value

Type Select All Parameters from the dropdown

Sap_Client_Value Client Id for example, <650>

9.10 Configuration for integration flow “Read Change

Process Groups for Quote from SAP Billing and
Revenue Innovation Management”

1. Select the Integration Package copied.

2. Choose Artifacts tab of the package to view list of integration flows.
3. Choose the Actions symbol beside the integration flow, for example, < Read Change Process Groups for
Quote from SAP Billing and Revenue Innovation Management>.
4. Choose Configure.
5. The configuration is explained in the following topics. Configuration of the receiver system (In this case,
SAP S4) and additional information.
6. Choose Save after completing configuration in a tab.
7. Choose Deploy after completion of whole configuration.

9.10.1 Receiver Tab

The receivers can be configured individually by choosing from the receiver dropdown.

Field Name Value

Receiver Receiver

Adapter Type HTTP

Change_Process_Group For example,

<http://sap-client:443/sap/opu/odata4/sap/api_change-
processgroup/srvd_a2x/sap/changeprocessgroup/0001>

Credential Name Credentials for S4 system for example, <CPQS4HINTEG>

SAP Billing and Revenue Innovation Management Integration

132 PUBLIC SAP Cloud Integration Configuration
9.10.2 More Tab

Field Name Value

Type Select All Parameters from the dropdown

Sap_Client_Value Client Id for example, <650>

9.11 Configuration for integration flow “Read Change

Process for Quote from SAP Billing and Revenue
Innovation Management”

1. Select the Integration Package copied.

2. Choose Artifacts tab of the package to view list of integration flows.
3. Choose the Actions symbol beside the integration flow, for example, < Read Change Process for Quote from
SAP Billing and Revenue Innovation Management>.
4. Choose Configure.
5. The configuration is explained in the following topics. Configuration of the receiver system (In this case,
SAP S4) and additional information.
6. Choose Save after completing configuration in a tab.
7. Choose Deploy after completion of whole configuration.

9.11.1 Receiver Tab

The receivers can be configured individually by choosing from the receiver dropdown.

Field Name Value

Receiver Receiver

Adapter Type HTTP

Change_Process_Group For example,

<http://sap-client:443/sap/opu/odata4/sap/api_change-
processgroup/srvd_a2x/sap/changeprocessgroup/0001>

Credential Name Credentials for SAP S/4HANA system for example,

<CPQS4HINTEG>

SAP Billing and Revenue Innovation Management Integration

SAP Cloud Integration Configuration PUBLIC 133
9.11.2 More Tab

Field Name Value

Type Select All Parameters from the dropdown

Sap_Client_Value Client Id for example, <650>

9.12 Configuration for integration flow “Read allowed

Change Process Groups for Subscription Contract Item
from SAP Billing and Revenue Innovation Management”

1. Select the Integration Package copied.

2. Choose Artifacts tab of the package to view list of integration flows.
3. Choose the Actions symbol beside the integration flow, for example, < Read allowed Change Process
Groups for Subscription Contract Item from SAP Billing and Revenue Innovation Management>.
4. Choose Configure.
5. The configuration is explained in the following topics. Configuration of the receiver system (In this case,
SAP S4) and additional information.
6. Choose Save after completing configuration in a tab.
7. Choose Deploy after completion of whole configuration.

9.12.1 Receiver Tab

The receivers can be configured individually by choosing from the receiver dropdown.

Field Name Value

Receiver S4

Adapter Type HTTP

Subscription_Contract http://sap-client:443/sap/opu/odata/sap/
API_SUBSCRIPTIONCONTRACT

Credential Name For example, <CPQS4HINTEG>

SAP Billing and Revenue Innovation Management Integration

134 PUBLIC SAP Cloud Integration Configuration
9.12.2 More Tab

Field Name Value

Type Select All Parameters from the dropdown

Sap_Client_Value Client Id for example, <650>

9.13 Configuration for integration flow “Replicate Change

Contract Processing Status from SAP S4HANA”

1. Select the Integration Package copied.

2. Choose Artifacts tab of the package to view list of integration flows.
3. Choose the Actions symbol beside the integration flow, for example, < Replicate Change Contract
Processing Status from SAP S4HANA>.
4. Choose Configure.
5. The configuration is explained in the following topics. Configuration of the sender system (In this case,
EMS) and the receiver system (In this case, SAP CPQ and SAP S/4HANA) and additional information.
6. Choose Save after completing configuration in a tab.
7. Choose Deploy after completion of whole configuration.

9.13.1 Sender Tab

Field Name Value

Sender SAPEventMesh

Adapter Type AMQP

Host SAP Event Mesh Host For ex-

ample, <cpqemsvlab2111-m1y2attx.enterprise-messag-
ing.cfapps.sap.hana.ondemand.com>

Port Port number For example, <443>

Path For example, </protocols/amqp10ws>

Credential Name SAP Event Mesh Credentials, for example, <EMSINT>

Queue Name Queue for example, <queue:sap/IESEMSHybCPQ/CPQUID/

ChangeQuoteEvents>

Number of Concurrent Processes 1

SAP Billing and Revenue Innovation Management Integration

SAP Cloud Integration Configuration PUBLIC 135
9.13.2 Receiver Tab

The receivers can be configured individually by choosing from the receiver dropdown.

Field Value

Receiver • SAP_CPQ_ACCESS_TOKEN_API

Adapter Type HTTP

SAP CPQ Host URL of the SAP CPQ host. For example,
<www.webcomcpq.com>

Authentication For Basic Authentication using the Access Token select None
from the dropdown.

 Note
Make sure that the Credentials – “CPQCredentials” is
created in SAP Cloud Integration.

For Client Certificate Authentication select Client Certificate

from the dropdown then provide Private Key Alias of the
certificate.

Field Name Value

Receiver CPQ, CPQ_StatusUpdate

Adapter Type HTTP

SAP CPQ Host For example, <www.webcomcpq.com>

Field Name Value

Receiver S4

Adapter Type HTTP

S4_Host For example, <sap-client:443>

Credential Name For example, <CPQS4HINTEG>

Field Name Value

Receiver SAPEventMeshRetry

Field Name Value

Adapter Type AMQP

Host SAP Event Mesh Host For exam-

ple, <cpqemsvlab2111-m1y2attx.enterprise-
messaging.cfapps.sap.hana.ondemand.com>

Port Port number For example, <443>

SAP Billing and Revenue Innovation Management Integration

136 PUBLIC SAP Cloud Integration Configuration
 Field Name Value

Path For example, </protocols/amqp10ws>

Credential Name SAP Event Mesh Credentials, for example, < EMSINT >

Queue name Queue for example, <queue:sap/EMSINT/CPQUID/

ChangeQuoteRetry>

Expiration Period (in s) 3600

9.13.3 More Tab

Field Name Value

Type Select All Parameters from the dropdown

Sap_Client_Value Client Id for example, <650>

9.14 Settings in SAP Cloud Integration

1. Access SAP Cloud Integration and select the correct subaccount.

2. Select Service Instances and create / adjust a Master Data Integration Service.
This will later need the Credentials from this Service Instance for the Webservice Configuration. Client ID
will be the User and Client Secret will be the password.
3. Go to Destinations and create a new destination for the Business Partner integration in the subaccount

Name The name should have BPOUTBOUND as suffix as MDI

will check for this suffix and sends out data to these
systems,for example, <CPQ_BPOUTBOUND>

Type HTTP

URL Endpoint URL of the Business Partner Integration

iFlow in SAP Cloud Integration, for example,
<https://<CPI URL>/cxf/scpmasterdata/
bpreplicationtocpq>

Proxy Type Internet

Authentication Basic

User Credentials of the SAP Cloud Integration Communication

User

After making these settings, choose save. Then add the additional Property MDOCONSUMER=true:
Then check if the connection is working by choosing the “Check Connection” button.

4. Make sure that the subaccount is connected in the Cloud Connector.

SAP Billing and Revenue Innovation Management Integration

SAP Cloud Integration Configuration PUBLIC 137
9.15 Create Distribution Model

1. Log on to the MDI MDO UI to create Distribution Model

2. Choose Manage Distribution Model tile:
3. Enter the following values:

Field Value

Model Name CPQ_BP

Description Replicate Business Partner to CPQ

Business Object Type Business Partner (147)

Package Size 20

Continuous Distribution Yes (alternative: define a recurrence pattern)

Provider MDO-Provider (choose the value from the help)

Consumer Choose the destination from the Cloud Platform, for

example, <CPQ_OUTBOUND>

Object Selection/Include Set BusinessPartner.Status equals to 02. This

means that when a new business partner is created in
MDI, it will first be sent to S/4 HANA and activated
there. Afterwards, it will be sent to SAP CPQ. Otherwise,
the system would send the business partner to both S/
4HANA and SAP CPQ after creation.

9.16 Value Mapping for SAP CPQ Integration with SAP

Billing and Revenue Innovation Management

1. Select the Integration Package copied

2. Choose Artifacts tab of the package to view list of integration flows.
3. Choose the Actions symbol beside the integration flow, for example, <Value Mapping for SAP CPQ
Integration with SAP Billing and Revenue Innovation Management>
4. Choose Configure.
5. The configuration is explained in the following topics. Configuration of the sender system (In this case,
SAP Billing and Revenue Innovation Management) and the receiver system (In this case, SAP CPQ) and
additional information.
6. Choose Save after completing configuration in a tab.

 Note

The identifiers in the value mapping must be identical to the names that are mentioned in the following
chapters, including capitalization. As these identifiers are used to call the value mapping inside the
integration flow, deviations would lead to integration flow failure as the value mapping would not be
accessible if the respective identifier cannot be found.

SAP Billing and Revenue Innovation Management Integration

138 PUBLIC SAP Cloud Integration Configuration
9.16.1 Product Category

1. In the Bi-Directional Mapping, create a new mapping by selecting Add.

2. Enter Agency as S4 and Identifier as ProductHierarchyInternalID in the left side and SAP CPQ as
Agency and Identifier as ProductCategoryUSEnglish in the right side.
3. Mention the Product Hierarchy in SAP Billing and Revenue Innovation Management system in left column
S4, ProductHierarchyInternalID. Innovation
4. Enter the respective Product Category in SAP CPQ system in right column SAP CPQ,
ProductCategoryUSEnglish.

 Note

As the category field is mandatory in SAP CPQ, make sure that the hierarchy is maintained for the SAP
Billing Revenue and Innovation Management product (field MARA-PRDHA).

9.16.2 Country

1. In the Bi-Directional Mapping, create a new mapping by selecting Add.

2. Enter Agency as S4 and Identifier as CountryCode in the left side and SAP CPQ as Agency and Identifier as
CountryAbbrev in the right side.
3. Mention the Country Code in SAP Billing and Revenue Innovation Management system in left column S4,
CountryCode. You can check Country Code in SAP Billing and Revenue Innovation Management in T005
Table.
4. Enter the respective Country Code in SAP CPQ system in right column SAP CPQ, Country

9.16.3 Region

1. In the Bi-Directional Mapping, create a new mapping by selecting Add.

2. Enter Agency as S4 and Identifier as RegionCode in the left side and SAP CPQ as Agency and Identifier as
StateAbbrev in the right side.
3. Mention the Region Code in SAP Billing and Revenue Innovation Management system in left column S4,
RegionCode. You can check Region Code in SAP Billing Revenue and Innovation Management in T005S
Table.
4. Enter the respective Region Code in SAP CPQ system in right column SAP CPQ, State

9.16.4 OrderItemType

1. In the Bi-Directional Mapping, create a new mapping by selecting Add.

2. Enter Agency as S4 and Identifier as ProductTypeCode_ItemCategoryGroupCodein the left side and CPQ as
Agency and Identifier as OrderItemTypein the right side.

SAP Billing and Revenue Innovation Management Integration

SAP Cloud Integration Configuration PUBLIC 139
3. Mention Material Types for Subscriptions_Item Category group code in SAP Billing Revenue and Innovation
Management system on the left column S4, ProductTypeCode_ItemCategoryGroupCode.
4. For the respective S4 fields maintain order Item type of CPQ in the right column – CPQ, OrderItemType

9.16.5 Time Zone

1. In the Bi-Directional Mapping, create a new mapping by selecting Add.

2. Enter Agency as S4 and Identifier as TimeZoneCode in the left side and SAP CPQ as Agency and Identifier
as TimeZone in the right side.
3. Mention the Time Zones for Subscriptions in SAP Billing Revenue and Innovation Management system
on the left column, S4, TimeZoneCode. You find the Time Zone definitions in the Customizing under
SPRO SAP Customization Implementation Guide SAP NetWeaver General Settings Time Zones
Maintain Time Zones .
4. Enter the respective Country Code in SAP CPQ system in right column, SAP CPQ, TimeZone.

9.16.6 Primary Industry

1. In the Bi-Directional Mapping, create a new mapping by selecting Add.

2. Enter Agency as S4 and Identifier as IndustrialSectorCode in the left side and SAP CPQ as Agency and
Identifier as PrimaryIndustry in the right side.
3. Mention the Industrial Sector Code for Subscriptions in SAP Billing Revenue and Innovation Management
system on the left column, S4, IndustrialSectorCode. You can check Industrial Sector Code in SAP Billing
Revenue and Innovation Management in TB038B Table.
4. Enter the respective Primary Industry value in SAP CPQ system in right column SAP CPQ, PrimaryIndustry

9.16.7 Form of Address

1. In the Bi-Directional Mapping, create a new mapping by selecting Add.

2. Enter Agency as S4 and Identifier as FormOfAddressCode in the left side and SAP CPQ as Agency and
Identifier as FormOfAddress in the right side.
3. Mention the Form of Address Code for Subscriptions in SAP Billing Revenue and Innovation Management
system on the left column, S4, FormOfAddressCode. You can check Form of Address Code in SAP Billing
Revenue and Innovation Management in TSAD3 Table.
4. Enter the respective Form of Address value in SAP CPQ system in right column SAP CPQ, FormOfAddress.

SAP Billing and Revenue Innovation Management Integration

140 PUBLIC SAP Cloud Integration Configuration
9.16.8 Bundle Item Category

Bundle Item Category

A new identifier is introduced to identify whether an item category is meant for a bundle or not.

All the general item categories for bundles from the Basic Data section in SAP S/4HANA Product Master need
to be maintained as "Bundle" in this iflow. This will identify a product as a bundle product and will be mapped
accordingly in the Quote iflow.

Agency Identifier

SAP CPQ BundleItemCategory

SAP S/4HANA Bundle

SAP Billing and Revenue Innovation Management Integration

SAP Cloud Integration Configuration PUBLIC 141
10 Master Data Creation

 Note

This Chapter is to create test data and is optional.

10.1 Product Bundle

Product bundles defined in SAP S/4HANA are not replicated to SAP CPQ and should not be used for this
integration scenario, i.e. do not replicate such bundle products. A bundle product can be defined directly in
SAP CPQ. Therefore, a root product must be created in SAP S/4HANA which is used as the root product for
this bundle. This root product can either be a subscription product or a dummy product. Dummy product will
not create any follow-up documents in SAP S/4HANA and it is used only for the bundling purpose. For such
a dummy product a specific item category and item category group should be assigned as described in later
section.

10.2 Product Type

A product type that has the product hierarchy as mandatory field should be created.

The product type (MARA-MTART) is used in SAP Cloud Integration value mapping to distinguish between sales,
subscription and service contract products.

10.3 Roles

Below roles are to be assigned to the users

• SAP_BR_BUPA_MASTER_SPECIALIST
• SAP_BR_INTRNAL_SALESREP_SOM
• SAP_BR_INVOICING_SPEC_CINV
• SAP_BR_PRODUCT_CONFIG_MODELER
• SAP_BR_PROD_CONF_MODELR_SOM

SAP Billing and Revenue Innovation Management Integration

142 PUBLIC Master Data Creation
10.4 Product Master Data: SOM_REC_CPQ_MOVIE_CONFIG

10.4.1 Create Product SOM_REC_CPQ_MOVIE_CONFIG

Test Step # Test Step Name Instruction Expected Result

1 Log On Log on to the SAP Fiori The Home page appears.

Launchpad as a Master Data
Specialist - Product Data
(MDG)

2 Access the SAP Fiori app Choose the Manage Product The Manage Product Master
Master Data tile. Data (Initial Screen) is dis-
played.

3 Maintain Material Basic Choose Create and make the In the Create Master Data
Data following entries in the Create Record window, basic details
Master Data Record window are entered and the product
that pops up can be created further

• Product Number:
SOM_REC_CPQ_MOVI
E_CONFIG
• Base Unit: Each (EA)
• Product Type:
Subscription
Product (SUBS)
• Product Group:
Subscription
Product (SUBS)
• Description:
Configurable
Movie
Subscription for
CPQ

4 Make the product configu- Navigate to Configuration Product can be configured as

rable section and select the the checkbox is selected.
checkbox for Product is
Configurable

SAP Billing and Revenue Innovation Management Integration

Master Data Creation PUBLIC 143
Test Step # Test Step Name Instruction Expected Result

5 Maintain Sales Data Navigate to Sales section of Product details are entered.

the product and enter the fol-

lowing details:

1. Billing Cycle:
Monthly, At
End of Month,
Overwriteable
(0001)
2. Billing Cycle
Determination Rule:
Test CPQ
Integration
(ZCPQ)

SAP Billing and Revenue Innovation Management Integration

144 PUBLIC Master Data Creation
 Test Step # Test Step Name Instruction Expected Result

6 Maintain Distribution Navigate to Distribution Redirected back to the prod-

Chains values Chains section and choose uct creation page
Create. Make the following
entries in the page that
opens.

• Sales Organization:
Whitefield South
(2020)
• Distribution Channel:
SOM Direct Sales
(10)
• Cash Discount:
Selected
• Default Contract Term:
12
• Alternative Contract
Term 1: 24
• Alternative Contract
Term 2: 36
• Unit for Contract Term:
Month (M)
• Default Extension Period:
6
• Alternative Extension
Period 1 : 12
• Alternative Extension
Period 2: 24
• Unit for Extension
Period: Month (M)
• Item Category Group:
Subscr. with
Recurr. (PRSR)
• Tax Classification: 1
for all entries
Choose Apply

7 Maintain Plant Details Navigate to Plants section Plant data is saved and re-
and choose Create. Maintain directed back to the product
Plant as SOM Plant (2020) creation page
and choose Apply

8 Save the product Choose Save on the product Product is created.

creation page

SAP Billing and Revenue Innovation Management Integration

Master Data Creation PUBLIC 145
  Note

Materials of other product types or product groups can be created in the similar way mentioned above. As
per the Business requirement other fields can be modified.

10.4.2 Maintain Characteristic

Test Step # Test Step Name Instruction Expected Result

1 Log on and Access the SAP Log on to the SAP Fiori The Characteristics page ap-
Fiori Launchpad and choose pears.
Manage Characteristics tile

2 Create Characteristic Enter Characteristic as Create Characteristic Page is

MOVIE_SIZE MOVIE_SIZE and choose displayed.
Create

3 Maintain Basic Data Maintain the following Values Basic details of Characteris-
in Basic Data tab tic are maintained

• Description: Movie
Package Size
• Status: Released
• Data Type: Character
Format
• Number of Chars: 10
• Value Assignment:
Single Value

4 Maintain Values for Charac- Navigate to Values section Characteristic is created.

teristic
and enter XS, S, M,
L and XL as Characteristic
Values. Make any one of the
values as default for exam-
ple, S.

Choose Save

5 Create Characteristic Enter Characteristic as Create Characteristic Page is

MOVIE_QUALITY MOVIE_QUALITY and displayed.
choose Create

SAP Billing and Revenue Innovation Management Integration

146 PUBLIC Master Data Creation
 Test Step # Test Step Name Instruction Expected Result

6 Maintain Basic Data Maintain the following Values Basic details of Characteris-
in Basic Data tab tic are maintained

• Description: Movie
Quality
• Status: Released
• Data Type: Character
Format
• Number of Chars: 10
• Value Assignment:
Single Value

7 Maintain Values for Charac- Navigate to Values section Characteristic is created.

teristic
and enter SD, HD, FHD,
UHD as Characteristic Values.
Make any one of the values
as default as per the require-
ment.

Choose Save

8 Create Characteristic Enter Characteristic as Create Characteristic Page is

MOVIE_STREAM_QTY MOVIE_STREAM_QTY and displayed.
choose Create

9 Maintain Basic Data Maintain the following Values Basic details of Characteris-
in Basic Data tab tic are maintained

• Description: Number
of parallel
streams
• Status: Released
• Data Type: Numeric
Format
• Number of Chars: 1
• Decimal Places: 0
• Exp. display: No
exponent
• Value Assignment:
Single Value

10 Maintain Values for Charac- Navigate to Values sec- Characteristic is created.

teristic
tion and enter 1,2,3 as
Characteristic Values. Make
any one of the values as de-
fault as per the requirement.

Choose Save

SAP Billing and Revenue Innovation Management Integration

Master Data Creation PUBLIC 147
Test Step # Test Step Name Instruction Expected Result

11 Create Characteristic Enter Characteristic as Create Characteristic Page is

VARKOND VARKOND and choose Create displayed.

12 Maintain Basic Data Maintain the following Values Basic details of Characteris-
in Basic Data tab tic are maintained

• Description: Variant
Condition
• Status: Released
• Data Type: Character
Format
• Number of Chars: 26
• Case Sensitive:
Selected
• Value Assignment:
Multiple Values

13 Maintain Additional data for Navigate to Additional Data Characteristic is created.

Characteristic
section and enter Table
Name as SDCOM and Field
Name as VKOND

Choose Save

 Note

Characteristics relevant to business need can be created in the similar way mentioned above.

10.4.3 Create Class

Test Step # Test Step Name Instruction Expected Result

1 Log On Log on to the SAP Fiori The Create Class page ap-
Launchpad and choose pears.
Create Classes tile.

2 Create Class CL_MOVIE Enter Class as CL_MOVIE, Create Class Page is dis-
Class Type as 300 and played.
choose Create

SAP Billing and Revenue Innovation Management Integration

148 PUBLIC Master Data Creation
 Test Step # Test Step Name Instruction Expected Result

3 Maintain Basic Data Maintain the following Values Basic details of Characteris-
in Basic Data tab tic are maintained

• Description: Class
for Movie
Subscription
• Status: Released

4 Maintain Characteristic for Navigate to Characteristic Class is created.

Class
section and en-
ter Characteristics
as MOVIE_SIZE,
MOVIE_QUALITY,
MOVIE_STREAM_QTY and
VARKOND.

Choose Save

 Note

Classes relevant to business need can be created in the similar way mentioned above adding the required
Characteristics to a particular class.

10.4.4 Maintain Variant Configuration Modeling

Test Step # Test Step Name Instruction Expected Result

1 Log On Log on to the SAP Fiori The Home page appears.

Launchpad.

2 Access the SAP Fiori app Choose the VC Modeling Initial Screen of Variant
Environment tile.
Configuration Modeling
Environment

Page is displayed.

3 Enter Model Enter Material as Configuration for

SOM_REC_CPQ_MOVIE_C SOM_REC_CPQ_MOVIE_CO
ONFIG, Class as 300 and NFIG Page is displayed.
choose Enter Model

SAP Billing and Revenue Innovation Management Integration

Master Data Creation PUBLIC 149
Test Step # Test Step Name Instruction Expected Result

4 Create Configuration Profile Select the material, right- Configuration Profile is cre-
ated
click and choose Create
Configuration Profile. Choose
Continue on the pop up and

Maintain Status as
1 Released and
Processing Mode as A
Advanced Variant
Configuration

5 Assign Class Select the material, right- Class is assigned

click and choose Assign
Class. Enter Class as
CL_MOVIE and choose
Continue. Make sure the
Status is Released

SAP Billing and Revenue Innovation Management Integration

150 PUBLIC Master Data Creation
 Test Step # Test Step Name Instruction Expected Result

6 Maintain Variant conditions Select the Material and navi- Variant Conditions are main-
for Characteristics gate to Variant Pricing. Main- tained for Characteristics
tain the following values.

Var-
Var- iant
Char iant Cond
ac- Char. Con- . De-
teris- Valu di- scrip
tic e tion tion

MOVI FHD MQ_ Full

E_QU FHD High
AL- Defi-
ITY nition

MOVI HD MQ_ High

E_QU HD De-
AL- feini-
ITY tion

MOVI SD MQ_ Stan

E_QU SD dard
AL- Defi-
ITY nition

MOVI UHD MQ_ Ultra

E_QU UHD High
AL- Defi-
ITY nition

MOVI L MS_L Movi

E_SI e
ZE Pack-
age L

MOVI M MS_ Movi

E_SI M e
ZE Pack-
age
M

MOVI S MS_ Movi

E_SI S e
ZE Pack-
age S

MOVI XS MS_ Movi

E_SI XS e
ZE Pack-
age
XS

MOVI XL MS_ Movi

E_SI XL e
ZE Pack-

SAP Billing and Revenue Innovation Management Integration

Master Data Creation PUBLIC 151
Test Step # Test Step Name Instruction Expected Result

Var-
Var- iant
Char iant Cond
ac- Char. Con- . De-
teris- Valu di- scrip
tic e tion tion

age
XS

7 Create KB Object Select the material, right- Knowledge Base object is

click and choose Create or created.
Assign KB Object. Choose
Continue on the pop up.
Maintain Status as 1 and
choose Save

SAP Billing and Revenue Innovation Management Integration

152 PUBLIC Master Data Creation
 Test Step # Test Step Name Instruction Expected Result

8 Create Dependency Choose the Configuration dependency is created

Profile of the material, right-

click and choose Create
Dependency and then Local
(Not Reusable) and maintain
the following

Under Editor, enter

 Sample Code

(
$SET_PRICING_F
ACTOR($SELF,
VARKOND,
'MQ_SD' , 2 ),
$SET_PRICING_F
ACTOR($SELF,
VARKOND,
'MQ_HD' , 2 ),
$SET_PRICING_F
ACTOR($SELF,
VARKOND,
'MQ_FHD' ,
2 ),
$SET_PRICING_F
ACTOR($SELF,
VARKOND,
'MQ_UHD' , 2 )
)
IF
MOVIE_STREAM_Q
TY = 2,
(
$SET_PRICING_F
ACTOR($SELF,
VARKOND,
'MQ_SD' , 3 ),
$SET_PRICING_F
ACTOR($SELF,
VARKOND,
'MQ_HD' , 3 ),
$SET_PRICING_F
ACTOR($SELF,
VARKOND,
'MQ_FHD' ,
3 ),
$SET_PRICING_F
ACTOR($SELF,
VARKOND,
'MQ_UHD' , 3 )
)
IF
MOVIE_STREAM_Q
TY = 3

Under Basic Data tab,

SAP Billing and Revenue Innovation Management Integration

Master Data Creation PUBLIC 153
Test Step # Test Step Name Instruction Expected Result

Description: Set Pricing

Factor

Processing Mode: A
Advanced Variant
Configuration

Status: Released

9 Create Runtime Version Select the KB object cre- Runtime Version is saved.

ated, right click and choose

Create Runtime Version. En-
ter Version as 0001 for ex-
ample and choose Continue.

Maintain the following values

• Status: 1
• Plant: 2020
• BOM Application: SD01

Choose Generate and Save.

Choose Yes in the pop up.

(A new runtime version is to

be created for any change
done to the configuration
model.)

 Note

As per the Business need, appropriate classes can be assigned to a product and corresponding variant
conditions can be maintained.

Refer to SAP Note 3026226 for further details on setting up the configuration model for solution
quotation creation.

10.4.5 Maintain Prices

Test Step # Test Step Name Instruction Expected Result

1 Log On Log on to the SAP Fiori The Home page appears.

Launchpad.

2 Access the SAP Fiori app Choose the Manage Prices- Manage Prices-Sales
Sales tile.
Page is displayed.

SAP Billing and Revenue Innovation Management Integration

154 PUBLIC Master Data Creation
 Test Step # Test Step Name Instruction Expected Result

3 Maintain Monthly Subscrip- Choose Create and maintain Monthly Subscription fee is
tion Fee the following maintained

• Condition Type:
Monthly Subscr
Fee (PSMB)
• Condition Table: 004
• Sales Organization:
Whitefield South
(2020)
• Distribution Channel:
SOM Direct Sales
(10)
• Product: Created
above
(Configurable
Movie
Subscription for
CPQ
(SOM_REC_CPQ_MOV
IE_CONFIG))
• Condition Amount: for
example, 10 USD
• Pricing Unit: 1 EA
• Calculation type:
Quantity -
Monthly Price
(M)

SAP Billing and Revenue Innovation Management Integration

Master Data Creation PUBLIC 155
Test Step # Test Step Name Instruction Expected Result

4 Create Variant Price Choose Create and maintain Variant Price is created
the following

• Condition Type:
Variant Price
(VASE)
• Condition Table: 057
• Variant Key: MS_M
• Sales Organization:
Whitefield South
(2020)
• Distribution Channel:
SOM Direct Sales
(10)
• Product: Created
above
(Configurable
Movie
Subscription for
CPQ
(SOM_REC_CPQ_MOV
IE_CONFIG))
• Condition Amount: for
example, 5 USD
• Pricing Unit: 1 EA
• Calculation type:
Quantity -
Monthly Price
(M)

 Note

Similarly maintain variant price for all the variant keys used in the Variant Configuration

10.5 Product Master Data:

SOM_REC_CPQ_CLOUD_UNLIMITED_YEAR

SAP Billing and Revenue Innovation Management Integration

156 PUBLIC Master Data Creation
10.5.1 Create Product
SOM_REC_CPQ_CLOUD_UNLIMITED_YEAR

Test Step # Test Step Name Instruction Expected Result

1 Log On Log on to the SAP Fiori The Home page appears.

Launchpad as a Master Data
Specialist - Product Data
(MDG)

2 Access the SAP Fiori app Choose the Manage Product The Manage Product Master
Master Data tile. Data (Initial Screen) is dis-
played.

3 Maintain Material Basic Data Choose Create and make the In the Create Master Data
following entries in the Create Record window, basic details
Master Data Record window are entered and the product
that pops up can be created further

• Product Number:
SOM_REC_CPQ_CLOU
D_UNLIMITED_YEAR
• Base Unit: Each (EA)
• Product Type:
Subscription
Product (SUBS)
• Product Group:
Subscription
Product (SUBS)
• Description: Cloud
Service
Unlimited Use
for CPQ Year

4 Maintain Sales Data Navigate to Sales section of Product details are entered.

the product and enter the fol-

lowing details

Billing Cycle: SOM

Yealy Billing Cycle
(SOMY)

Billing Cycle Determination

Rule: Test CPQ
Integration (ZCPQ)

SAP Billing and Revenue Innovation Management Integration

Master Data Creation PUBLIC 157
Test Step # Test Step Name Instruction Expected Result

5 Maintain Distribution Chains Navigate to Distribution Redirected back to the prod-

values Chains section and choose uct creation page
Create. Make the following
entries in the page that
opens.

• Sales Organization:
Whitefield South
(2020)
• Distribution Channel:
SOM Direct Sales
(10)
• Cash Discount:
Selected
• Product Hierarchy: SUBS
(00004)
• Default Contract Term: 1
• Alternative Contract
Term 1: 2
• Alternative Contract
Term 2: 3
• Unit for Contract Term:
Year (Y)
• Default Extension Period:
1
• Alternative Extension
Period 1 : 2
• Alternative Extension
Period 2: 3
• Unit for Extension
Period: Year (Y)
• Item Category Group:
Subscr. with
Recurr. (PRSR)
• Tax Classification: 1
for all entries

6 Maintain Plant Details Navigate to Plants section Plant data is saved and re-
and choose Create. Main- directed back to the product
tain Plant as SOM Plant creation page
(2020) and choose Apply

7 Save the product Choose Save on the product Product is created.

creation page

SAP Billing and Revenue Innovation Management Integration

158 PUBLIC Master Data Creation
10.5.2 Maintain Prices

Test Step # Test Step Name Instruction Expected Result

1 Log On Log on to the SAP Fiori The Home page appears.

Launchpad.

2 Access the SAP Fiori app Choose the Manage Prices- Manage Prices-Sales
Sales tile.
Page is displayed.

3 Maintain Yearly Subscrip- Choose Create and maintain Monthly Subscription fee is
tion Fee the following maintained

• Condition Type: Yearly

Subscr Fee
(ZYSF)
• Condition Table: 004
• Sales Organization:
Whitefield South
(2020)
• Distribution Channel:
SOM Direct Sales
(10)
• Product: Created
above (Cloud
Service
Unlimited Use
for CPQ Year
(SOM_REC_CPQ_CLO
UD_UNLIMITED_YEA
R))
• Condition Amount: for
example, 1500 USD
• Pricing Unit: 1 EA
• Calculation type:
Quantity - Year
Price (N)

10.6 Product Master Data: SOM_BSV_CPQ_CLOUD_001

SAP Billing and Revenue Innovation Management Integration

Master Data Creation PUBLIC 159
10.6.1 Create Product SOM_BSV_CPQ_CLOUD_001

Test Step # Test Step Name Instruction Expected Result

1 Log On Log on to the SAP Fiori The Home page appears.

Launchpad as a Master Data
Specialist - Product Data
(MDG)

2 Access the SAP Fiori app Choose the Manage Product The Manage Product Master
Master Data tile. Data (Initial Screen) is dis-
played.

3 Maintain Material Basic Data Choose Create and make the In the Create Master Data
following entries in the Create Record window, basic details
Master Data Record window are entered and the product
that pops up can be created further

• Product Number:
SOM_BSV_CPQ_CLOU
D_001
• Base Unit: Each (EA)
• Product Type: Bundle
Product (BUND)
• Product Group: Bundle
Product (BUND)
• Description: Cloud
Bundle 001:
Subscription

4 Maintain Distribution Chains Navigate to Distribution Redirected back to the prod-

values Chains section and choose uct creation page
Create. Make the following
entries in the page that
opens.

• Sales Organization:
Whitefield South
(2020)
• Distribution Channel:
SOM Direct Sales
(10)
• Cash Discount:
Selected
• Item Category Group:
Quote Structure
Prod (ZQSP)
• Tax Classification: 0
for all entries
Choose Apply

SAP Billing and Revenue Innovation Management Integration

160 PUBLIC Master Data Creation
 Test Step # Test Step Name Instruction Expected Result

5 Save the product Choose Save on the product Product is created.

creation page

10.7 Product Master Data: SOM_SLS_CPQ_TABLET_BASIC

10.7.1 Create Product SOM_SLS_CPQ_TABLET_BASIC

Test Step # Test Step Name Instruction Expected Result

1 Log on to the SAP Fiori The Home page appears.

Launchpad as a Master Data

Specialist - Product Data
(MDG)

2 Access the SAP Fiori app Choose the Manage Product The Manage Product Master
Master Data tile. Data (Initial Screen) is dis-
played.

3 Maintain Material Basic Data Choose Create and make the In the Create Master Data
following entries in the Create Record window, basic details
Master Data Record window are entered and the product
that pops up can be created further

• Product Number: SOM_

SLS_CPQ_TABLET_B
ASIC
• Base Unit: Each (EA)
• Product Type: Trading
Goods (HAWA)
• Product Group:
Trading Goods
(HAWA)
• Description: Tablet
Basic for CPQ

SAP Billing and Revenue Innovation Management Integration

Master Data Creation PUBLIC 161
Test Step # Test Step Name Instruction Expected Result

4 Maintain Distribution Chains Navigate to Distribution Redirected back to the prod-

values Chains section and choose uct creation page
Create. Make the following
entries in the page that
opens.

• Sales Organization:
Whitefield South
(2020)
• Distribution Channel:
SOM Direct Sales
(10)
• Item Category Group:
Standard item
(NORM)

Tax Classification: 1 for

all entries

SAP Billing and Revenue Innovation Management Integration

162 PUBLIC Master Data Creation
 Test Step # Test Step Name Instruction Expected Result

5 Maintain Plant Details Navigate to Plants section Plant data is saved and re-
and choose Create. Maintain directed back to the product
the following details: creation page

• Plant: SOM Plant

(2020)
• Loading Group: Crane
(0001)
• Availability check:
Individ.requirem
ents (02)
• MRP Relevancy
for Dependent
Requirements:
Materials
for dependent
requirements are
planned
• Procurement Type:
External
procurement (F)
• Plan Explosion: The
Default Value
from Customizing
is Used
• Pegging Strategy: Use
Timely Receipts
• Product Alerts:
Determine Direct
Alerts, Relevant
to Network
Alerts
• Fixed Pegging:
Fixed Pegging
According to
Client Setting

6 Save the product Choose Save on the product Product is created.

creation page

SAP Billing and Revenue Innovation Management Integration

Master Data Creation PUBLIC 163
10.7.2 Maintain Prices

Test Step # Test Step Name Instruction Expected Result

1 Log On Log on to the SAP Fiori The Home page appears.

Launchpad.

2 Access the SAP Fiori app Choose the Manage Prices- Manage Prices-Sales
Sales tile.
Page is displayed.

3 Maintain Price Choose Create and maintain Monthly Subscription fee is

the following maintained

• Condition Type: Price

(PPR0)
• Condition Table: 304
• Sales Organization:
Whitefield South
(2020)
• Distribution Channel:
SOM Direct Sales
(10)
• Product: Created
above Tablet
Basic for CPQ
(SOM_SLS_CPQ_TAB
LET_BASIC)
• Condition Amount: for
example, 120 USD
• Pricing Unit: 1 EA
• Calculation type:
Quantity (C)

10.8 Product Master Data: SOM_SLS_CPQ_TABLET_CONFIG

SAP Billing and Revenue Innovation Management Integration

164 PUBLIC Master Data Creation
10.8.1 Create Product SOM_SLS_CPQ_TABLET_CONFIG

Test Step # Test Step Name Instruction Expected Result

1 Log On Log on to the SAP Fiori The Home page appears.

Launchpad as a Master Data
Specialist - Product Data
(MDG)

2 Access the SAP Fiori app Choose the Manage Product The Manage Product Master
Master Data tile. Data (Initial Screen) is dis-
played.

3 Maintain Material Basic Data Choose Create and make the In the Create Master Data
following entries in the Cre- Record window, basic details
ate Master Data Record win- are entered and the product
dow that pops up can be created further

• Product Number:
SOM_SLS_CPQ_TABL
ET_CONFIG
• Base Unit: Each (EA)
• Product Type: Trading
Goods (HAWA)
• Product Group:
Trading Goods
(HAWA)
• Description:
Configurable
Tablet for CPQ

4 Make the product configura- Navigate to Configuration Product can be configured as

ble section and select the the checkbox is selected.
checkbox for Product is
Configurable

SAP Billing and Revenue Innovation Management Integration

Master Data Creation PUBLIC 165
Test Step # Test Step Name Instruction Expected Result

6 Maintain Distribution Chains Navigate to Distribution Redirected back to the prod-

values Chains section and choose uct creation page
Create. Make the following
entries in the page that
opens.

• Sales Organization:
Whitefield South
(2020)
• Distribution Channel:
SOM Direct Sales
(10)
• Cash Discount:
Selected
• Delivery Plant: SOM
Plant (2020)
• Item Category Group:
Standard item
(NORM)
• Tax Classification: 1
for all entries
Choose Apply

8 Save the product Choose Save on the product Product is created.

creation page

10.8.2 Maintain Characteristic

Test Step # Test Step Name Instruction Expected Result

1 Log on and Access the SAP Log on to the SAP Fiori The Characteristics page ap-
Fiori Launchpad and choose pears.
Manage Characteristics tile

2 Create Characteristic Enter Characteristic as Create Characteristic Page is

SCREEN_SIZE SCREEN_SIZE and choose displayed.
Create

SAP Billing and Revenue Innovation Management Integration

166 PUBLIC Master Data Creation
 Test Step # Test Step Name Instruction Expected Result

3 Maintain Basic Data Maintain the following Values Basic details of Characteris-
in Basic Data tab tic are maintained

• Description: Tablet
Screen Size
• Status: Released
• Data Type: Character
Format
• Number of Chars: 5

4 Maintain Values for Charac- Navigate to Values section Characteristic is created.

teristic
and enter 8, 10, 12 as
Characteristic Values and 8
Inch, 10 Inch, 12
Inch as their corresponding
Description. Make any one of
the values as default for ex-
ample, 10.

Choose Save

5 Create Characteristic Enter Characteristic as Create Characteristic Page is

CPU_CORE CPU_CORE and choose displayed.
Create

6 Maintain Basic Data Maintain the following Values Basic details of Characteris-
in Basic Data tab tic are maintained

• Description:Number
of CPU Cores
• Status: Released
• Data Type: Character
Format
• Number of Chars: 5

7 Maintain Values for Charac- Navigate to Values section Characteristic is created.

teristic
and enter 2, 4,6,8 as
Characteristic Values and 2
Cores, 4 Cores, 6
Cores, 8 Cores as their
corresponding Description.
Make any one of the values
as default as per the require-
ment.

Choose Save

8 Create Characteristic OPER- Enter Characteristic as Create Characteristic Page is

ATION_SYSTEM OPERATION_SYSTEM and displayed.
choose Create

SAP Billing and Revenue Innovation Management Integration

Master Data Creation PUBLIC 167
Test Step # Test Step Name Instruction Expected Result

9 Maintain Basic Data Maintain the following Values Basic details of Characteris-
in Basic Data tab tic are maintained

• Description:Operatio
n System
• Status: 1 Released
• Data Type: CHAR
Character Format
• Number of Chars: 10

10 Maintain Values for Charac- Navigate to Values section Characteristic is created.

teristic
and enter IOS, ANDROID
as Characteristic Values and
2 Cores, 4 Cores, 6
Cores, 8 Cores as their
corresponding iOS, Android .
Make any one of the values
as default as per the require-
ment.

Choose Save

11 Create Characteristic VAR- Enter Characteristic as Create Characteristic Page is

KOND VARKOND and choose Create displayed.

12 Maintain Basic Data Maintain the following Values Basic details of Characteris-
in Basic Data tab tic are maintained

• Description:Variant
Condition
• Status: 1 Released
• Data Type: CHAR
Character Format
• Case Sensitive:
Selected
• Number of Chars: 26
• Value Assignment:
Multiple Values

13 Maintain Additional data for Navigate to Additional Data Characteristic is created.

Characteristic
section and enter Table
Name as SDCOM and Field
Name as VKOND

Choose Save

SAP Billing and Revenue Innovation Management Integration

168 PUBLIC Master Data Creation
10.8.3 Create Class

Test Step # Test Step Name Instruction Expected Result

1 Log On Log on to the SAP Fiori The Class page appears.

Launchpad and choose
Create Classes tile

2 Create Class CL_CPQ_TAB- Enter Class as Create Class Page is dis-

LET CL_CPQ_TABLET, Class played.
Type as 300 and choose
Create

3 Maintain Basic Data Maintain the following Values Basic details of Characteris-
in Basic Data tab tic are maintained

• Description: Class
for Tablets
• Status: 1 Released

4 Maintain Characteristic for Navigate to Characteristic Class is created.

Class
section and en-
ter Characteristics
as SCREEN_SIZE,
CPU_CORE,
OPERATION_SYSTEM and
VARKOND.

Choose Save

10.8.4 Maintain Variant Configuration Modeling

Test Step # Test Step Name Instruction Expected Result

1 Log On Log on to the SAP Fiori The Home page appears.

Launchpad.

2 Access the SAP Fiori app Choose the VC Modeling Initial Screen of Variant
Environment tile.
Configuration Modeling
Environment

Page is displayed.

3 Enter Model Enter Material as Configuration

SOM_SLS_CPQ_TABLET_ for SOM_SLS_CPQ_TAB-
CONFIG, Class as 300 and LET_CONFIG Page is dis-
choose Enter Model played.

SAP Billing and Revenue Innovation Management Integration

Master Data Creation PUBLIC 169
Test Step # Test Step Name Instruction Expected Result

4 Create Configuration Profile Select the material, right- Configuration Profile is cre-
ated
click and choose Create
Configuration Profile. Choose
Continue on the pop up and

Maintain Status as
1 Released and
Processing Mode as A
Advanced Variant
Configuration

5 Assign Class Select the material, right- Class is assigned

click and choose Assign
Class. Enter Class as
CL_CPQ_TABLET and
choose Continue. Make sure
the Status is Released

SAP Billing and Revenue Innovation Management Integration

170 PUBLIC Master Data Creation
 Test Step # Test Step Name Instruction Expected Result

6 Maintain Variant conditions Select the Material and navi- Variant Conditions are main-
for Characteristics gate to Variant Pricing. Main- tained for Characteristics
tain the following values.

Var-
Var- iant
Char iant Cond
ac- Char. Con- . De-
teris- Valu di- scrip
tic e tion tion

CPU_ 4 CPU_ 4
COR 4 Core
E s

CPU_ 6 CPU_ 4
COR 6 Core
E s

CPU_ 8 CPU_
COR 8
E

OP- AN- OS_A An-

ERA- DROI NDR droid
TION D OID
_SYS
TEM

OP- IOS OS_I Ios

ERA- OS
TION
_SYS
TEM

SCR 10 DIS- 10
EEN_ PLAY inch
SIZE _10

SCR 12 DIS- 12
EEN_ PLAY inch
SIZE _12

7 Create KB Object Select the material, right- Knowledge Base object is

click and choose Create or created.
Assign KB Object. Choose
Continue on the pop up.
Maintain Status as 1 and
choose Save

SAP Billing and Revenue Innovation Management Integration

Master Data Creation PUBLIC 171
Test Step # Test Step Name Instruction Expected Result

8 Create Runtime Version Select the KB object created, Runtime Version is saved.
right click and choose Create
Runtime Version. Enter Ver-
sion as 0001 for example and
choose Continue.

Maintain the following values

• Status: 1
• Plant: 2020
• BOM Application: SD01

Choose Generate and Save.

Choose Yes in the pop up.

(A new runtime version is to

be created for any change
done to the configuration
model.)

10.8.5 Maintain Prices

Test Step # Test Step Name Instruction Expected Result

1 Log On Log on to the SAP Fiori The Home page appears.

Launchpad.

2 Access the SAP Fiori app Choose the Manage Prices- Manage Prices-Sales
Sales tile.
Page is displayed.

SAP Billing and Revenue Innovation Management Integration

172 PUBLIC Master Data Creation
 Test Step # Test Step Name Instruction Expected Result

3 Maintain Price Choose Create and maintain Monthly Subscription fee is

the following maintained

• Condition Type: Price

(PPR0)
• Condition Table: 304
• Sales Organization:
Whitefield South
(2020)
• Distribution Channel:
SOM Direct Sales
(10)
• Product: Created above,
Configurable
Tablet for
CPQ(SOM_SLS_CPQ_
TABLET_CONFIG)
• Condition Amount: for
example, 150 USD
• Pricing Unit: 1 EA
• Calculation type: Quan-
tity (C)

SAP Billing and Revenue Innovation Management Integration

Master Data Creation PUBLIC 173
Test Step # Test Step Name Instruction Expected Result

4 Create Variant Price Choose Create and maintain Variant Price is created
the following

• Condition Type:
Variant Price
(VA00)
• Condition Table: 057
• Variant Key: Android
(OS_ANDROID)
• Sales Organization:
Whitefield South
(2020)
• Distribution Channel:
SOM Direct Sales
(10)
• Product: Created above,
Configurable
Tablet for
CPQ(SOM_SLS_CPQ_
TABLET_CONFIG)
• Condition Amount: for
example, 10 USD
• Pricing Unit: 1 EA
• Calculation type: Quan-
tity (C)

Similarly maintain variant

price for all the variant keys
used in the Variant Configu-
ration

10.9 Product Master Data: SOM_SVC_CPQ_SUPPORT_GOLD

SAP Billing and Revenue Innovation Management Integration

174 PUBLIC Master Data Creation
10.9.1 Create Product SOM_SVC_CPQ_SUPPORT_GOLD

Test Step # Test Step Name Instruction Expected Result

1 Log On Log on to the SAP Fiori The Home page appears.

Launchpad as a Master Data
Specialist - Product Data
(MDG)

2 Access the SAP Fiori app Choose the Manage Product The Manage Product Master
Master Data tile. Data (Initial Screen) is dis-
played.

3 Maintain Material Basic Data Choose Create and make the In the Create Master Data
following entries in the Cre- Record window, basic details
ate Master Data Record win- are entered and the product
dow that pops up can be created further

• Product Number:
SOM_SVC_CPQ_SUPP
ORT_GOLD
• Base Unit: Each (EA)
• Product Type: Non-
stock materials
(NLAG)
• Product Group: Non-
st contract mat
(NLAG-CTR)
• Description: Support
contract gold
for CPQ

SAP Billing and Revenue Innovation Management Integration

Master Data Creation PUBLIC 175
Test Step # Test Step Name Instruction Expected Result

4 Maintain Distribution Chains Navigate to Distribution Redirected back to the prod-

values Chains section and choose uct creation page
Create. Make the following
entries in the page that
opens.

• Sales Organization:
Whitefield South
(2020)
• Distribution Channel:
SOM Direct Sales
(10)
• Cash Discount:
Selected
• Delivery Plant: SOM
Plant (2020)
• Item Category Group:
Service Cntrct
Prod. (SCNP)
• Tax Classification: 1
for all entries
Choose Apply

5 Save the product Choose Save on the product Product is created.

creation page

10.9.2 Maintain Prices

Test Step # Test Step Name Instruction Expected Result

1 Log On Log on to the SAP Fiori The Home page appears.

Launchpad.

2 Access the SAP Fiori app Choose the Manage Prices- Manage Prices-Sales
Sales tile.
Page is displayed.

SAP Billing and Revenue Innovation Management Integration

176 PUBLIC Master Data Creation
 Test Step # Test Step Name Instruction Expected Result

3 Maintain Price Choose Create and maintain Monthly Subscription fee is

the following maintained

• Condition Type: Price

f.Srv.Cntr.Itm
(PSI1)
• Condition Table: 004
• Sales Organization:
Whitefield South
(2020)
• Distribution Channel:
SOM Direct Sales
(10)
• Product: Created above,
Support contract
gold for CPQ
(SOM_SVC_CPQ_SUP
PORT_GOLD)
• Condition Amount: for
example, 100 USD
• Pricing Unit: 1 EA
• Calculation type: Quan-
tity - Monthly Price (M)

 Note

Sales product/service product can be configured in the same way as mentioned in Product Master Data:
SOM_REC_CPQ_MOVIE_CONFIG [page 143].

10.10 SAP S/4HANA Bundle Multi-Level Product

Level Product Product Type

1 BUND

1.1 SOM_BUN_CPQ_1_1 BUND

1.1.1 SOM_SVC_CPQ_SUP- NLAG-CTR

PORT_GOLD

1.1.2 SOM_REC_CPQ_CLOUD_UN SUBS

LIMITED_YEAR

1.2 SOM_BUN_CPQ_1_2 BUND

SAP Billing and Revenue Innovation Management Integration

Master Data Creation PUBLIC 177
Level Product Product Type

1.2.1 SOM_REC_CPQ_CLOUD_UN SUBS

LIMITED_YEAR

1.2.2 SOM_REC_CPQ_MOVIE_CO SUBS

NFIG

1.2.3 SOM_SVC_CPQ_SUP- NLAG-CTR

PORT_GOLD

1.3 SOM_BUN_CPQ_1_3 BUND

1.3.1 SOM_REC_CPQ_MOVIE_CO SUBS

NFIG

1.3.2 SOM_SVC_CPQ_SUP- NLAG-CTR

PORT_GOLD

10.10.1 Create Root Bundle Product SOM_BUN_CPQ_1

Test Step # Test Step Name Instruction Expected Result

1 Log On Log on to the SAP Fiori The Home page appears.

Launchpad as a Master Data
Specialist - Product Data
(MDG)

2 Access the SAP Fiori app Choose the Manage Product The Manage Product Master
Master Data tile. Data (Initial Screen) is dis-
played.

3 Maintain Material Basic Data Choose Create and make the Details are entered and the
following entries in the Cre- product can be created fur-
ate Master Data Record win- ther.
dow that pops up:

• Product Number:
SOM_BUN_CPQ_1
• Base Unit: Each (EA)
• Product Type: Configura-
ble materials (KMAT)
• Product Group: Bundle
Product (BUND)
• Description: Root Bundle

4 Enter Bundle Item Category In the section General Product will be identified as
Group code information enter Item cate- Bundle product.
gory group code as SQBG
which is meant for Bundle
products.

SAP Billing and Revenue Innovation Management Integration

178 PUBLIC Master Data Creation
 Test Step # Test Step Name Instruction Expected Result

5 Make the product configura- Navigate to Configuration Product can be configured as

ble section and select the the checkbox is selected.
checkbox for Product is
Configurable.

6 Maintain Distribution Chains Navigate to Distribution Redirected back to the prod-

values Chains section and choose uct creation page.
Create. Make the following
entries in the page that
opens.

• Sales Organization:
Whitefield South (2020)
• Distribution Channel:
SOM Direct Sales (10)
• Delivery Plant: SOM
Plant (2020)
• Item Category Group:
SQBG
• Tax Classification: 1 for
all entries

Choose Apply

7 Save the product Choose Save on the product Product is created.

creation page

Similarly, you can create Child Bundle Product from the above example. Create Characteristics and Class for
the below Bundle Products and Root Bundle Product SOM_BUN_CPQ_1.

• SOM_BUN_CPQ_1_1
• SOM_BUN_CPQ_1_2
• SOM_BUN_CPQ_1_3

From the above examples in this document you would have already created subscription and service contract
products.

• SOM_SVC_CPQ_SUPPORT_GOLD
• SOM_REC_CPQ_CLOUD_UNLIMITED_YEAR
• SOM_REC_CPQ_MOVIE_CONFIG

10.10.2 Create BOM

Test Step # Test Step Name Instruction Expected Result

1 Log On Log on to the SAP GUI or The Home page appears.

alternatively, use SAP Fiori
Launchpad.

SAP Billing and Revenue Innovation Management Integration

Master Data Creation PUBLIC 179
Test Step # Test Step Name Instruction Expected Result

2 Access the transaction Enter transaction code CS01 Initial Screen Material BOM is
to create a new BOM. In
Fiori Launchpad, use the app Page is displayed.
“Maintain Bill of Material”

3 Enter BOM Enter Material as BOM for SOM_BUN_CPQ_1 is

SOM_BUN_CPQ_1, Plant as displayed.
2020, BOM Usage as 5 (sales
and distribution) and choose
Enter

4 Add BOM Components Add the product Component added to BOM

SOM_BUN_CPQ_1_1 to the
list of components, which
you want in the BOM. Choose
Item Category N (non-stock
item) and Qty 1. Proceed
with the other components:
SOM_BUN_CPQ_1_2 and
SOM_BUN_CPQ_1_3

5 Save BOM Save the created BOM with BOM is created

the added components

6 Create the BOMs for the bun- Create the BOMs for prod- BOMs for 2nd level are cre-
dle products on Level 2 ucts SOM_BUN_CPQ_1_1, ated
SOM_BUN_CPQ_1_2 and
SOM_BUN_CPQ_1_3 accord-
ing to the list.

10.10.3 Maintain Variant Configuration Modeling

Test Step # Test Step Name Instruction Expected Result

1 Log On Log on to the SAP Fiori The Home page appears.

Launchpad.

2 Access the SAP Fiori app Choose the VC Modeling Initial Screen of Variant
Environment tile.
Configuration Modeling
Environment

Page is displayed.

3 Enter Model Enter Material as Configuration

SOM_BUN_CPQ_1, Class as for SOM_SLS_CPQ_TAB-
300 and choose Plant 2020 LET_CONFIG Page is dis-
and BOM Application SD01 played.
to Enter Model.

SAP Billing and Revenue Innovation Management Integration

180 PUBLIC Master Data Creation
 Test Step # Test Step Name Instruction Expected Result

4 Create Configuration Profile Select the material, right- Configuration Profile is cre-
ated
click and choose Create Con-
figuration Profile. Choose
Continue on the pop up and

Maintain Status as 1 Re-

leased, Processing Mode as
A Advanced Variant Configu-
ration, Process as Sales Or-
der (SET) and BOM Explo-
sion as Multi-Level (SD01
Sales and Distribution).

5 Assign Class Select the material, right- Class is assigned

click and choose Assign
Class. Enter Class, which
was created previously and
choose Continue. Make sure
the Status is Released.

6 Create KB Object Select the material, right- Knowledge Base object is

click and choose Create or created.
Assign KB Object. Choose
Continue on the pop up.
Maintain Status as 1 and
choose Save.

7 Create Runtime Version Select the KB object created,

right click and choose Create
Runtime Version. Enter Ver-
sion as 0001 for example and
choose Continue.

Maintain the following values:

• Status: 1
• Plant: 2020
• BOM Application: SD01

Choose Generate and choose

Save. Choose Yes in the pop
up.

(A new runtime version is to

be created for any change
done to the configuration
model.)

SAP Billing and Revenue Innovation Management Integration

Master Data Creation PUBLIC 181
10.11 Business Partner Master Data: BP_Test

Test Step # Test Step Name Instruction Expected Result

1 Log On Log on to the SAP and access The Maintain Business

the Transaction BP Partner page appears.

2 Access BP transaction Choose Create Person or The Create Person or Create

Create Organization to create Organization page is dis-
Business Partner for Person played.
or Organization

3 Maintain BP Role Sold-To- General details of Business

Select CRM000 Sold-To
Party Partner are maintained.
Party for Create in BP role
and choose Create in the
pop-up.

Maintain the following de-

tails:

• Grouping: 0001
Internal Number
Assignment
• First Name: Test
• Last Name: BP
• Correspondence lang. :
EN
• Search Term 1: Test
• Street Address:
Address details

SAP Billing and Revenue Innovation Management Integration

182 PUBLIC Master Data Creation
 Test Step # Test Step Name Instruction Expected Result

4 Maintain Sales and Distribu- Choose Sales and Sold-To-Party role is saved.
tion data Distribution button on top of
the screen. Maintain the fol-
lowing details:

• Sales Org: 2020

• Distr. Channel: 10
• Division: 10

In the Orders tab,

• Sales District: 000002

• Price Group: 01

In the Billing tab,

• Terms of Payment:
0001
• Tax classification : 1 for
all output tax

Choose Save

5 Maintain BP role Contract Choose Edit and main- Contract Partner role is
Partner saved
tain MKK Contract
Partner for Change in BP
role

Choose Save

6 Maintain FI Customer BP role Choose Edit and maintain FI Customer role is saved

FLCU00 FI Customer
for Change in BP role.

Choose Company Code but-

ton on top of the screen and
maintain Company Code as
US01 and Reconciliation acct
as 121000.

Choose Save

7 Create a Contract Account Access the transaction CAA1 Contract Account Creation
and enter the following Page is displayed.

• Business Partner:
Business Partner
created above
• Cont. Acct Cat.: 03

SAP Billing and Revenue Innovation Management Integration

Master Data Creation PUBLIC 183
Test Step # Test Step Name Instruction Expected Result

8 Maintain Details for Contract Maintain the following details Contract Account is saved.
Account
In General Data tab:

• Acct. Relation: 01
Account Holder
• Tolerance Group: 0001
• Account determin. ID:
01
• Payment terms: 0001

In Payments/Taxes:

• Company Code Gp:

US01
• Standard CoCode: US01

SAP Billing and Revenue Innovation Management Integration

184 PUBLIC Master Data Creation
11 Data Loading

Purpose

This section describes how to execute the initial data load of material and customer master from your SAP
Billing and Revenue Innovation Management system to the SAP CPQ system.

11.1 Business Partner (Customer Master)

1. Access the below transaction.

Transaction code DRFOUT

2. In section Replication Model Enter a replication model for example, <CPQ_S4_INT>.

3. In section Outbound Implementation enter for example, <986_3>.
4. In section Outbound Implementation enter for example, <986_3>.

 Note

Choose Manual to replicate specific business partners.

5. Choose Manual Replication Filter Criteria in top menu.

6. In Manual Replication Filter Criteria screen, choose Business Partner from left menu and enter the Business
Partner for example as, <12315>, choose Back.
7. Choose Yes in the pop- up and choose Execute.

 Note

Although the overall status shows as green, there can be errors that are only shown in the log. To see
detailed log, Choose on the details view and make sure that every item status is green.

11.2 Product Master

1. Access the below transaction.

Transaction code DRFOUT

2. In section Replication Model enter the value for example as, <CPQ_S4_INT>.
3. In section Outbound Implementation enter the value for example as, <194_3>.

SAP Billing and Revenue Innovation Management Integration

Data Loading PUBLIC 185
4. In section Replicate Mode select radio button Manual and check box Manual Replication Filter Criteria
Available.

 Note

Choose Manual to replicate specific Material.

5. Choose Manual Replication Filter Criteria in top menu.

6. In Manual Replication Filter Criteria screen, choose Material from left menu and enter the Material for
example as <SOM_REC_CPQ_CLOUD_CONFIG>, choose Back.
7. Choose Yes in the pop-up and choose Execute

 Note

Although the overall status shows as green, there can be errors that are only shown in the log. To see
detailed log, Choose on the details view and make sure that every item status is green.

11.3 Verify products in SAP CPQ

This section describes the steps to verify the product in SAP CPQ.

Procedure

1. Log in to your SAP CPQ system using an Administrator User.

2. Choose Setup in the left menu bar and choose Setup.
3. In left navigation bar, select Product under Product Catalog.
4. Search for the product in filter by name or part number for example as <SOM_REC_CPQ_CLOUD_CONFIG>.
5. Choose on Edit in the Actions tab.
6. Verify the below details in Definitions and Pricing tab.
• System ID: for example, <SOM_REC_CPQ_CLOUD_CONFIG>
• Part Number: for example, <SOM_REC_CPQ_CLOUD_CONFIG>
• Product Description: for example, <Cloud Configuration>
• Display Type: for example, <Configurable Product>
• Product Type: for example, <SUBS>
• Unit Of Measure: for example, <EA>
• Category: for example, <SUBS>
• Active: for example, <YES>
• Subscription Product: for example, <YES>
• Created By: for example, <CPQ-Communication User>

SAP Billing and Revenue Innovation Management Integration

186 PUBLIC Data Loading
11.4 Verify Business Partner in SAP CPQ

This section describes the steps to verify the product in SAP CPQ.

Procedure

1. Log in to your SAP CPQ system using an Administrator User.

2. Choose Setup in the left menu bar and choose Setup.
3. In left navigation bar, select Business Partners under Business Partners.
4. Search for the product in filter by name for example as <BP_test>.
5. Choose on Edit in the Actions tab.
6. Verify the details in General tab.
• Name: for example, <BP_test>
• Partner ID: for example, <123>
• First Name: for example, <Test>
• Last Name: for example, <BP>
• Address Info: as provided in the SAP S/4HANA

SAP Billing and Revenue Innovation Management Integration

Data Loading PUBLIC 187
12 Appendix

12.1 Ticket Component

Implementation Step Component Comment

SV-RDS-CFC

12.2 How to setup Cloud Connector

Purpose

You need to have Cloud Connector Virtual Host URL for SAP Billing Revenue and Innovation Management
system, which will be used in SAP Cloud Integration system as address path to call the SAP Billing Revenue and
Innovation Management system.

Procedure

1. Login to your S/4HANA Cloud Connector system using an Administrator User.

2. Select the Account of your SAP Cloud Integration system.
3. Choose Access Control to add Mapping Virtual to Internal System.
4. Choose on Add button.
5. Select ABAP System in Back-end Type and choose Next.
6. Select HTTPS as Protocol and choose Next.
7. Enter the Internal Host and choose Next. You can find HTTPS host and port of your system in SMICM
transaction Goto Services .
8. Enter the Internal Port and Choose Next.
9. Enter the Virtual Host which you must maintain in SAP Cloud Integration integration flows and choose
Next.
10. Select Principal Type as none and choose Next.

SAP Billing and Revenue Innovation Management Integration

188 PUBLIC Appendix
 11. Enter the Description and choose Next.
12. Choose Finish button.
13. Select the Entry for Virtual Host Mapping created in above steps.
14. Choose Add in Resource Accessible and Add / as URL Path.
15. Choose Save.

12.3 BCP Components

Important: If you have any queries or feedback on this document, please create a ticket for the BCP
component, depending on which product the query is related to:

• SAP CPQ: CEC-SAL-SAP CPQ• SAP CPQ: CEC-SAL-SAP CPQ

• SAP SAP Billing Revenue and Innovation Management HANA: CRM-S4-SOM

SAP Billing and Revenue Innovation Management Integration

Appendix PUBLIC 189
Important Disclaimers and Legal Information

Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:

• Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:

• The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.

• SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

• Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering an SAP-hosted Web site. By using
such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.

Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within
the control or responsibility of SAP.

Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities,
genders, and abilities.

SAP Billing and Revenue Innovation Management Integration

190 PUBLIC Important Disclaimers and Legal Information
SAP Billing and Revenue Innovation Management Integration
Important Disclaimers and Legal Information PUBLIC 191
www.sap.com/contactsap

© 2024 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. The information contained herein may be changed
without prior notice.

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 or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP 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.

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. All
other product and service names mentioned are the trademarks of their
respective companies.

Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.

THE BEST RUN