82a0a579eac14c53af9724ac64dbd3ab
82a0a579eac14c53af9724ac64dbd3ab
82a0a579eac14c53af9724ac64dbd3ab
1 Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2 System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Create Communication System for SAP Master Data Integration Connections. . . . . . . . . . . . . . .26
Pricing Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
6.2 View Prepackaged integration flows using SAP Cloud Integration Web UI. . . . . . . . . . . . . . . . . . . . . 46
6.4 Configuration of the Integration flow “Create Sales Order from SAP CPQ in S4HANA
Cloud_Quote2.0_SOAP”. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
6.5 Configuration for integration flow “Replicate Sales Order status from SAP S4HANA to SAP CPQ
Quote 2.0”. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
6.6 Configuration for integration flow “Replicate Product from SAP S/4HANA”. . . . . . . . . . . . . . . . . . . 50
6.7 Configuration for integration flow “Replicate Business Partner from SAP Master Data Integration”
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
6.8 Value Mapping for SAP CPQ integration with SAP S/4HANA Cloud. . . . . . . . . . . . . . . . . . . . . . . . . 53
7 Data Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
8 Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Learn how to configure the basic integration between SAP CPQ and sales orders in SAP S/4HANA Cloud using
SAP Cloud Integration.
SAP CPQ can be integrated with SAP S/4HANA Cloud to provide a workflow for users to automatically create a
sales order in SAP S/4HANA Cloud whenever a SAP CPQ quote is sent to SAP S/4HANA Cloud. The follow-up
documents are then created in SAP S/4HANA Cloud automatically.
Note
The setup instructions in this guide only describe the basic authentication. Nevertheless, a certificate-
based authentication might also be possible, depending on the system preconditions.
Limitations
• This integration works only with the Quote 2.0 engine in SAP CPQ.
• This integration supports only simple products and single-level configurable products.
Learn about the system requirements for an integration between SAP CPQ and sales orders in SAP S/4HANA
Cloud.
You must fulfill the following system requirements for a successful configuration:
Learn about the prerequisites for an integration between SAP CPQ and sales orders in SAP S/4HANA Cloud.
Note
You can only set up this integration using Quote 2.0, not Quote 1.0.
SAP CPQ
• You have enabled Quote 2.0 and business partners in the SAP CPQ tenant.
• You have configured the application parameter Allowed origins for the CORS filter. If one or more domains
are entered in this field, only the API calls from these domains are allowed. This means: If the parameter
is not set to *, you must enter both the URL of your tenant and the URLs of the integrated applications to
enable API communication. Values are separated with a semicolon (“;”).
• You have a business user that contains the SAP_CORE_BC_COM (Communication Management) business
catalog, for example, a user based on the the SAP_BR_ADMINISTRATOR (Administrator) business role
template.
The business catalog contains the following apps:
• Maintain Communication Users
• Communication Arrangements
• Communication Systems
For more information about business users and business roles, see Identity and Access Management.
• The following scope items are active in your system:
• Sell from Stock (BD9)
• Make-to-Order Production with Variant Configuration (1YT)
• Business Event Handling (1NN)
For more information about these sope items, see SAP Signavio Process Navigator .
Depending on your configuration environment for SAP S/4HANA Cloud, choose one of the following
options to check the status:
• Manage Your Solution View Solution Scope
• SAP Central Business Configuration Explore Activities . Search for Define Scope, and choose
Open.
If a scope item hasn't been activated yet, please create a support ticket on component XX-S4C-OPR-SRV
to request the activation.
For any integration issues related to SAP S/4HANA Cloud, please create a support ticket on component
CA-GTF-INT.
Others
• You have contacted the Network Security team to prepare the network environment across different
systems and to check security aspects.
Note
Markets are not replicated, so you must create them manually in SAP CPQ. Sales organizations in SAP
S/4HANA Cloud correspond to markets in SAP CPQ.
• Your SAP Cloud Integration tenant has been provisioned. For more information, see SAP Cloud Integration.
This chapter describes the configuration that needs to be done in SAP CPQ system to integrate it with SAP
S/4HANA Cloud.
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.
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 create the password. The same password is to be used in SAP Cloud Integration at the time
of creating user credentials for SAP CPQ.
To manage the pricing procedures, enable the SAP S/4HANA Cloud integration in SAP CPQ.
Context
When the integration is enabled, administrators see new settings in the setup:
• New section Pricing/Calculations Pricing Procedures . In this section, administrators can map pricing
procedure properties to the corresponding fields in the quote or the quote item.
• New column Synced from Back Office in the product grid ( Setup Product Catalog Product ). This
column indicates if a product is replicated from S/4HANA Cloud or is created in SAP CPQ.
Procedure
The integration with SAP Variant Configuration and Pricing is to be enabled as described in the documentation.
The prepackaged integration content uses the SAP Event Mesh to process events.For the initial setup of SAP
Event Mesh please refer to the link to create the SAP Event Mesh Service Instance. The following steps describe
how to enable the event processing in SAP Event Mesh.
1. Create Service Key: In the 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 SAP 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 SAP 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. Enter the queue name, leave all other values as suggested
Context
The default pricing for the products coming from SAP S/4HANA Cloud to SAP CPQ is the SAP Variant
Configuration and Pricing. Alternatively, you can also use the CPQ pricing instead.
Steps to map the general attributes after connecting SAP CPQ to SAP Variant Configuration and Pricing:
A market is created in SAP CPQ against every Sales Organization of SAP S/4HANA Cloud system. This will help
in pricing determination in Quote in SAP CPQ system.
Procedure
Note
4.7.2 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
Note
The above selection will allow users with user type ‘Sales’ to give discounts on the 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.
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.
SAP CPQ administrators can map pricing conditions from pricing procedures in SAP S/4HANA Cloud to quote
item or header fields in SAP CPQ. That way, the prices from SAP CPQ are sent to the back-end system when an
order is placed.
Pricing procedures exist in the back-end system, but they need to be specified manually in SAP CPQ for which
steps from the link are to be followed.
The default status of the quote is Preparing and changes to Order Confirmation Pending when the Place Order
action is executed. In that moment SAP CPQ publishes event and SAP Cloud Integration creates Sales Order in
S/4HANA Cloud. To support errors that might occur in quote data replication process, SAP Cloud Integration
implements error handling logic which requires additional workflow settings in SAP CPQ. The error handling
requires the setup of additional quote status as an interim status between Preparing and Order Placed.
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:
• If SAP S/4HANA Cloud 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
• If SAP S/4HANA Cloud does not return an error, the quote goes to status Order Placed.
When the SAP S/4HANA Cloud 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 S/4HANA Cloud integration is enabled.
SAP CPQ Quote is sent via SAP Cloud Integration to SAP S/4HANA Cloud. The success or error message
from SAP S/4HANA Cloud are received asynchronously and sent back to SAP CPQ via SAP Cloud Integration
(through the Integration flow Sales Order Status from SAP S/4HANA Cloud to SAP CPQ). Errors which are
returned from SAP S/4HANA Cloud 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 S/4HANA Cloud in the language the user used for integration.
The action for creating Sales Order in SAP S/4HANA Cloud needs to be enabled 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.
Ensure the below Partner Functions that are supported in the integration between SAP CPQ and SAP S/
4HANA Cloud are available in SAP CPQ. This can be checked in the path Setup Setup Quotes Partner
Functions :
Procedure:
As the Sold-To Party is mandatory, it is useful to display this partner function by default for a new quote.
The SAP S/4HANA Cloud 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
Note
Partner functions can only be replicated from SAP CPQ to SAP S/4HANA Cloud if the partner function key
exists in SAP S/4HANA Cloud and was entered on the More tab in the integration flow configuration.
According to the Permission groups maintained in SAP CPQ, the Business Partners can be used in the quote
creation.
Procedure
The integration of SAP CPQ with the SAP S/4HANA Cloud sales order supports these product types:
• Simple products
• Single-level configurable products
Products are mastered in SAP S/4HANA Cloud and they arrive via SAP Cloud Integration to SAP CPQ. If
single-level configurations are needed, SAP Variant Configuration and Pricing Service attributes are added to
the simple products.
Replicated Data
Products are replicated from SAP S/4HANA Cloud into SAP CPQ using the ImportMaterialsFromERP SOAP
API.
The following product details are sent to SAP CPQ from SAP S/4HANA Cloud via the SAP Cloud Integration:
• name
• system ID
• product type
• part number
• unit of measure
• category
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.
Follow the below procedure to create Product Type in SAP CPQ. This Product Type is mapped from SAP
S/4HANA Cloud Material Group 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.
As there is no product hierarchy in SAP S/4HANA Cloud, the Category is always the same for every replicated
product. The name of this category can be entered during the configuration of the product replication
Integration flow. If you want more than one category for the replicated products, the categories must be
manually created and assigned in the SAP CPQ Setup.
Note
This Chapter is optional and is required when more than one category is used.
Users of SAP CPQ and SAP S/4HANA Cloud 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.
Learn about the configuration in SAP S/4HANA Cloud for an integration with SAP CPQ.
Trust relationships enable you to establish secure connections between known servers whose identity can be
confirmed by a signed certificate. You need to download the certificate of SAP Cloud Integration (SCI) tenant
from a web browser and import it in SAP S/4HANA Cloud. We recommend using Google Chrome.
1. Access SAP Cloud Integration using a URL like the following: https://<tenant management node>/itspaces
2. In the browser address bar, choose the lock icon and then Connection is secure.
3. Choose Certificate is valid.
4. In the Certificate Viewer, go to the Details tab.
5. Choose Export.
6. Enter a file name, choose where to save the file, and save it (for example, in format Base64-encoded ASCII,
single certificate (*pem;*crt)).
Note
Check if the certificate for SAP Cloud Integration is already available. If yes, you can ignore the
following steps.
3. Next to the Certificate Trusts table, choose the plus icon to add the certificate.
4. Browse for the SAP Cloud Integration certificate that you downloaded previously and choose Upload.
1. Go to the SAP BTP subaccount where you want the SAP Master Data Integration instance to be created.
On the left side, under Services, select Instances and Subscriptions.
2. On the top right, choose Create.
3. Select the following:
• Service: Master Data Integration
• Plan: sap-integration
• Runtime Environment: <Cloud Foundry>
• Space: for example <mdi-hybrid-2021>
4. Enter the Instance Name, for example <CG4_100>.
5. Choose Next, and enter the JSON to create the service instance.
6. Choose Next, review, and choose Create.
7. Select the Service Instance that you created and choose Create service Key.
8. Choose Next and then Create.
1. Go to the SAP BTP subaccount where you want the SAP Master Data Integration instance to be created.
On the left side, under Services, select Instances and Subscriptions.
2. On the top right, choose Create.
3. Select the following:
• Service: Master Data Integration
• Plan: sap-integration
• Runtime Environment: <Cloud Foundry>
• Space: for example <mdi-hybrid-2021>
4. Enter the Instance Name, for example <Generic_configuration>.
5. Choose Next, and enter the JSON to create the service instance.
6. Choose Next, review, and choose Create.
7. Select the Service Instance that you created and choose Create service Key.
8. Choose Next and then Create.
1. Navigate to your subaccount and choose Connectivity and then the Destinations tab on the left side.
2. Choose New Destination.
Type HTTP
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.
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.
Note
NOTE: Please refer to the link for any further details related to Business Partner replication through Master
Data Integration.
The communication user defined in the SAP S/4HANA Cloud system is used for inbound communication and
processing messages in the system. Technically, the user is needed to call services in SAP S/4HANA Cloud.
Field Value
Note
5. Choose Create.
If communication systems for SAP Cloud Integration connections or SAP Master Data Integration connections
are already in place, use these. If not, create new communication systems as described.
The communication system is used to define the host name of the SAP Cloud Integration and to assign
inbound and outbound users of SAP S/4HANA Cloud.
Field Value
System Name We recommend to use the same name as the system ID,
for example, <SCI_123>.
5. Maintain the Host Name of the fully qualified SAP Cloud Integration runtime URL.
Note
Make sure that https:// is not included in the host
name.
Logical System We recommend to use the same name as the system ID,
for example, <SCI_123>.
Business System We recommend to use the same name as the system ID,
for example, <SCI_123>.
Username <COM_USER_S4C>
Username and password are the Client ID and client secret respectively from the service key of the SAP
Cloud Integration instance in SAP BTP.
The communication system is used to define the host name of the SAP Master Data Integration and to assign
inbound and outbound users of SAP S/4HANA Cloud.
Field Value
System Name We recommend to use the same name as the system ID,
for example, <MDI_123>.
5. Maintain the Host Name of the fully qualified SAP Cloud Integration runtime URL.
Note
Make sure that https:// is not included in the host
name.
Logical System We recommend to use the same name as the system ID,
for example, <MDI_123>.
Business System We recommend to use the same name as the system ID,
for example, <MDI_123>.
Username <COM_USER_S4C>
Note
Username and password are the Client ID and client secret respectively from the service key of the SAP
Master Data Integration instance in SAP BTP.
The communication arrangement in the SAP S/4HANA Cloud system defines all relevant information for the
interface. The inbound and outbound authentication is set on communication system level and is automatically
passed on to the related communication arrangements.
Learn how to set up communication scenario SAP_COM_0288 for transactional data integration for sales
orders with the Communication Arrangements app.
Field Value
Note
You can use the value help to search for a specific
scenario.
5. Choose Create.
6. Maintain Common Data. In the Communication System field, select the communication system for the SAP
Cloud Integration connections that you created earlier, for example, <SCI_123>.
7. The inbound and outbound communication user is entered automatically.
8. The following Outbound Services need to be active and the details filled as follows:
Outbound Application
Service Service Status Protocol Port Path Service URL Use WSRM
Note
For all the service endpoints, you must add the prefix /cxf to the path. Ensure that the service URLs
match the configuration of endpoints in the respective integration flows. The endpoint of the sales
order status integration flow is set during the integration flow configuration or can be looked up in the
SAP Cloud Integration under Overview Manage Integration Content . Select the integration flow
Learn how to set up communication scenario SAP_COM_0008 for master data integration for business
partner, customer, and contact with the Communication Arrangements app.
Field Value
Note
You can use the value help to search for a specific
scenario.
5. Choose Create.
6. Maintain Common Data. In the Communication System field, select the communication system for SAP
Master Data Integration connections that you created earlier, for example, <MDI_123>.
Note
For all the service endpoints, you must add the prefix /cxf to the path. Ensure that the service URLs
match the configuration of endpoints in the respective integration flows.
7. Deactivate all IDoc-based outbound services. To find out if a service is IDoc-based, look at the Application
Protocol field.
8. The following outbound services need to be active and the details filled as follows:
9. For the Additional Properties section of the active outbound service Business Partner - Replicate from SAP
S/4HANA Cloud to Client, select the following values:
Replication Model Enter a name that indicates what the replication model
does, for example, <RE_BP_CPQ>.
Learn how to set up communication scenario SAP_COM_0009 for master data integration for products with
the Communication Arrangements app.
Field Value
Note
You can use the value help to search for a specific
scenario.
5. Choose Create.
6. Maintain Common Data. In the Communication System field, select the communication system for
SAP Cloud Integration connections that you created earlier, for example, <SCI_123>. The inbound and
outbound communication users are entered automatically.
7. The following outbound services need to be active and the details filled as follows:
Outbound Application
Service Service Status Protocol Port Path Service URL Use WSRM
Note
For all the service endpoints, you must add the prefix /cxf to the path. Ensure that the service URLs
match the configuration of endpoints in the respective integration flows.
8. For the Additional Properties section of the active outbound service Product Master - Replicate from SAP
S/4HANA Cloud to Client, select the following values:
Replication Model Enter a name that indicates what the replication model
does, for example <RE_PRD_CPQ>.
9. Choose Save.
10. The communication arrangement is now active.
Learn how to set up pricing for an integration between SAP CPQ and sales orders in SAP S/4HANA Cloud.
Learn how to set up pricing condition types for an integration between SAP CPQ and sales orders in SAP
S/4HANA Cloud.
In a sales order, price elements are represented by condition types. Price elements can be, for example, prices,
surcharges, discounts, taxes or freight, and are stored in the system in condition records. You can, for example,
define whether a discount is calculated as a percentage or a fixed amount using the condition type. You specify
an access sequence in every condition type. In this way you define which fields the system checks when
searching for a valid condition record.
Note
If you don't use SAP Variant Configuration and Pricing [page 9], you can define condition types without
access sequences. In SAP CPQ, you must then assign these condition types to CPQ item prices.
1. In your configuration environment, use the search function to open the following activity: Set Condition
Types for Pricing in Sales.
2. Choose Configure and then New Entries to create the necessary condition types.
Example
The following condition types illustrate how you can set up discounts and surcharges that are then used in a
pricing procedure.
Condition Type 1
Field Value
Control Data 1
Plus/Minus X (Negative)
Item Condition X
Delete X
Amount/Percent X
Master Data
Scales
Condition Type 2
Field Value
Control Data 1
Plus/Minus A (Positive)
Header Condition X
Delete X
Amount/Percent X
Master Data
Learn how to set up pricing procedures for an integration between SAP CPQ and sales orders in SAP S/4HANA
Cloud.
After having created the condition types, you can create pricing procedures using these condition types. In
the pricing procedures, you define which condition types are to be taken into account and in which sequence.
During pricing, the system automatically determines which pricing procedure is valid for a sales order. The
system then takes the condition types contained in the pricing procedure into account, one after the other. If
you want to use one-time prices and cumulated discounts, you must create your own pricing procedures.
The integration between SAP CPQ and sales orders in SAP S/4HANA Cloud uses document pricing (that is,
the determined prices are applied to the entire quote). You can define mappings between the SAP CPQ quote
or custom fields and the price conditions in the pricing procedure in SAP S/4HANA Cloud. In this scenario,
you must create the quote before you can add a product. This allows the system to determine the pricing
procedure in advance, so that SAP Variant Configuration and Pricing can do the necessary calculations. Once
you add, delete, or change items in the SAP CPQ quote, SAP Variant Configuration and Pricing is called and all
mapped conditions are sent.
Example
The following settings illustrate how you can set up a pricing procedure.
Pricing Procedure
Rel-
evan
t for
Ac-
cou Alt. Alt.
nt Calc Cnd
De- . n
Con- De- ter- Re- Cnd Bas Ac- Ac-
Step di- scri Fro Re- Sta- min- Prin quir n e cou Ac- cess
Num Cou tion ptio m To Man quir tis- atio t Sub- eme Amn Valu nt crua Leve
ber nter Type n Step Step ual ed tics n Type total nt t e Key ls l
90 0 Sub- 30 35 5 0 0 0
total
Var-
iant
Pric
e
100 0 Gros 10 80 a 1 0 2 0
s
Valu
e
700 0 Net 0 0 a 2 0 2 0
Valu
e1
740 0 Stat. 0 0 0 82 0
Valu
e
with-
out
Freig
ht
800 0 Net 0 0 3 0 2 0
Valu
e2
900 0 Total 0 0 A 0 4 0
Valu
e
950 0 Profi 0 0 0 11 0
t
Mar-
gin
Learn how to set up the pricing procedure determination for an integration between SAP CPQ and sales orders
in SAP S/4HANA Cloud.
When you set a pricing procedure determination, you define how the system determines the correct
pricing procedure every time a sales order is created. The pricing procedure should follow the setup of the
organizational structure in the system.
1. In your configuration environment, use the search function to open the following activity: Set Pricing
Procedure Determination.
2. Choose Configure and then New Entries to create the necessary pricing procedure determination.
3. Create a new procedure (for example, ZCPQDP) and add a description (for example, CPQ Sales Order
for Doc Prc).
Example
The following settings illustrate how you can set up the pricing procedure determination, using the pricing
procedure created before.
1710 10 00 Y1 Z3 ZCPQDP
Before the integration flow can be used, it must be copied to the local 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.
View Prepackaged integration flows using SAP Cloud Integration Web UI [page 46]
Configuration of the Integration flow “Create Sales Order from SAP CPQ in S4HANA
Cloud_Quote2.0_SOAP” [page 47]
Configuration for integration flow “Replicate Sales Order status from SAP S4HANA to SAP CPQ Quote 2.0”
[page 49]
Configuration for integration flow “Replicate Product from SAP S/4HANA” [page 50]
Configuration for integration flow “Replicate Business Partner from SAP Master Data Integration” [page
52]
Value Mapping for SAP CPQ integration with SAP S/4HANA Cloud [page 53]
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.
Field Value
6. Choose Deploy.
7. Choose Create and select User Credentials.
8. Enter the following details for user of SAP S/4HANA Cloud.
Field Value
9. Choose Deploy.
To import and deploy integration flows, AuthGroup.IntegrationDeveloper role is to be assigned in the tenant.
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 Create Sales Order from CPQ Quote 2.0 in SAP S/4HANA Cloud.
4. All the artifacts of this package will be displayed when Artifacts is selected.
1. Connect to the tenant management node of the SAP Cloud Integration system with the URL: http://
<tenant management node URL>/itspaces.
2. 2. On the Discover tab, select the package for example, SAP CPQ - Quote 2.0 Integration with SAP S/
4HANA Sales Order. Choose Artifacts to view all the integration flows related to this integration package.
3. Choose Copy on the right top corner to copy it to design area.
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
Note
The integration flow package does not have a retry mechanism and does not support certificate-based
authentication.
Receiver Tab
The receivers can be configured individually by choosing from the receiver dropdown.
Receiver Quote2OrderPostProcessingExit
Receiver • SAP_CPQ_QuotesAPI
• SAP_CPQ_QuoteItemsCountAPI
• S4_CPQ_1924
• SAP_CPQ_QuoteItemsAPI
Credential Name User Credentials created for SAP CPQ. For example,
<COM_USER_CPQINT_SCLOUD>
Timeout (in ms) Time until Connection Timeout, default Value is 60 000
Receiver S4HANACLOUD
Authentication Basic
Credential Name User Credentials created for SAP S/4HANA Cloud. For ex-
ample, <COM_USER_S4C>
Timeout (in ms) Time until Connection Timeout, default Value is 60 000
More Tab
Extension Implemented Only configure this receiver if you intend to modify the
standard mapping through your own Integration flow. De-
fault value is False
S4 Item Increment Interval SAP S/4HANA Cloud has another numbering interval than
SAP CPQ. The items in the Sales Order might do not have
subsequent numbering as in SAP CPQ (1,2,3 etc.) but can
also be 10,20,30 etc. In this case, the value would be 10
S4_Language EN
Sender Business System Name of the Business System from SAP S/4HANA Cloud.
This ID is important to identify the correct recipient
system for the Sales Order Confirmation. For example,
<SCI_123>. This is found in the Communication System
for SAP Cloud Integration connections
Recipient Business System This ID is important to identify the correct recipient system
for the Sales Order.
Deployment
Sender Tab
Sender Sender
Receiver Tab
Receiver • CPQ_ErrorMessage_1924
• CPQ_Message_1923
Credential Name User Credentials created for SAP CPQ. For example,
<COM_USER_CPQINT_SCLOUD>
Deployment
Sender S4HANA
Receiver Tab
The receivers can be configured individually by choosing from the receiver dropdown.
Receiver CPQ
Authentication Basic
Credential Name User Credentials created for SAP S/4HANA Cloud. For ex-
ample, <CPQS4HINTEG>
Timeout in ms 60000
Receiver MaterialReplicationPostExit
Category Enter the name of the category where all products from SAP
S/4HANA Cloud will be replicated to for example, default
category is <SAP_CLOUD_CATEGORY>
EnableLog Set true to enable log files, false to disable logs. Default value
is false
Sender Tab
Sender S4HANA
Receiver CPQ
Receiver BusinessPartnerReplicationProcessingExit
More Tab
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.
Country
Region
Time Zone
Form of Address
This section describes how to execute the initial data load of material and customer master from your SAP
S/4HANA Cloud system to the SAP CPQ system.
Procedure
Procedure
Procedure
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.
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 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.