Quite often we are seeing many issues related to Pricing with external system and configurations on the same , considering all these , this blog is prepared using help content available.

 

This Document focuses on the pricing integration available, how to configure and special considerations for usage.
Comparison of C4C and ERP Pricing

SAP ERP is based on condition technique, analyzing the pricing procedure with condition types and access sequence to determine the type of pricing to be used.

 

In general terms, conditions represent a set of circumstances that apply when a price is calculated.

 

For example, a particular customer orders a certain quantity of a particular product on a certain day. The variable factors here – the customer, the product, the order quantity, the date – determine the final price the customer gets. The information about each of these factors can be stored in the system as master data. This master data is stored in the form of condition records. Condition records allow you to store and retrieve pricing data in the system. All the pricing elements of your daily business – the prices, discounts, and surcharges for freight and taxes – that you want to use for automatic pricing must be stored in the system as condition records. You can define as many condition records as you want for the different pricing elements for any validity period.
Price Conditions Example:
10 Laptops ($1000 each): 1000.00 USD

5% Discount for Orders of $5000 or more: -500.00 USD

$100 Rebate: -100.00 USD

Transportation: +25.00 USD

Total Price: 9425.00 USD

 

In SAP ERP terms, conditions are combined with pricing procedures and access sequence to determine the right price.

 

/wp-content/uploads/2016/08/1_1027270.png

 

 

Whereas SAP Cloud for Customer starts with a base price and narrows it by additional price lists and discount types
/wp-content/uploads/2016/08/2_1027274.png

 

 

SAP Cloud for Customer internal pricing is simplified compared to SAP ERP pricing. SAP Cloud for Customer internal pricing has the following:
• Fixed amount of price list types

• Fixed amount of discount list types

• Single pricing procedure with predefined price elements

• Limited customizing capabilities

• One pricing procedure valid for ALL document types
Pricing integration with SAP ERP or SAP CRM is used when the pricing in SAP Cloud for Customer needs to follow the same pricing rules that already exist in SAP on-premise applications.

 

Pricing Integration with SAP ERP

 

Pricing integration works with opportunities, sales quotes, sales orders, and work tickets. The pricing with sales quotes, sales orders, and work ticket is referred to as external pricing that uses the ERP condition technique. The pricing with an opportunity simulates an order and returns the net pricing. First we will look at the opportunity pricing then look at the external pricing that is use for quotes, orders, and work tickets.

 

Opportunity Pricing

 

Opportunity pricing uses a Web Service that simulates a sales order and returns the net pricing. It does not allow the C4C user to additional discounts or add additional price conditions. This is because the opportunity pricing is a general price. The opportunity is not a legal binding document and does not have the final price the customer will pay. Once an opportunity is converted to a quote, the price is not converted; this is also because the opportunity price is not a legally binding price and should not be used for the quote price.

 

Cloud Configuration

 

There is one scoping question for the Opportunity pricing with SAP ERP. Within the questions for integration with ERP, the question is

 

Do you want to use your SAP ERP solution to calculate prices for opportunity items in your cloud solution?”

 

/wp-content/uploads/2016/08/3_1027275.png
The communication arrangement is Opportunity with Sales Pricing in SAP ERP. Be sure to use the integration flow spreadsheet at https://service.sap.com/cloud4customer to get all the details from the communication arrangement name to the target URL’s, to the operations mappings and all other details.

 

ERP Configuration

From transaction code SOAMANAGER search for the object name *pricing* and you will find the Web Service. It is called SALESORDERPRICINGINFORMATIONQU. This Web Service should be configured as other Web Services. Web Service configuration is not explained in detail here since it is not unique to C4C integration.

 

/wp-content/uploads/2016/08/4_1027276.png

When you configure the Web Service in SOAMANAGER the default binding name is normally ‘binding’. In the following screenshot, the name ‘pricingbinding’ was used. This is for example only to show the importance of referencing the path of the Web Service.

 

/wp-content/uploads/2016/08/5_1027277.png

Be sure to use the Transport Settings to know the exact URL required to be called from HCI or PI.

 

In the example below, the Access URL is: /sap/bc/srt/xip/sap/salesorderpricinginformationqu/800/salesorderpricing/pricingbinding

 

This is what will be used in the middleware to form the URL for the pricing call to SAP ERP./wp-content/uploads/2016/08/6_1027278.png

 

Middleware Configuration

 

The PI and HCI details are provided in the integration flow spreadsheet at https://service.sap.com/cloud4customer.

 

In the middleware configuration, you need to ensure the URL is set directly.

 

For example, in HCI it defaults to: https://{{Host}}:{{Port}}/sap/bc/srt/scs/sap/salesorderpricinginformationqu?sap-client={{client}}.
However, when looking at the transport settings we can see the URL we need is:

 

https://{{Host}}/sap/bc/srt/xip/sap/salesorderpricinginformationqu/{{client}}/salesorderpricing/pricingbinding.
Ensure the URL provided in the middleware matches what you configured in SOAMANAGER when you configured the Web Service.

 

Special considerations for opportunity pricing

 

Pricing for opportunity simulates a standard order type in ERP. The order type used for the simulation is defined in the middleware in value mapping. For example, in HCI value mapping has the following:

 

 

<group id=”fb114882f5a249c584595da0ea72c210″>

<entry>

<agency>ERP</agency>

<schema>ERPDocumentTypeCode</schema>

<value>TA</value>

</entry>

<entry>

<agency>COD</agency>

<schema>CODPricingRequest</schema>

<value>PricingRequest</value>

</entry>

</group>

 

 

By default, the opportunity uses the standard order type in SAP ERP. This cannot yet be overridden by code list mapping

 

When you do the pricing from the Opportunity, you must provide the complete sales area, so sales org, distribution channel, and division. You may need to Adapt/Personalize the Opportunity screen to see these fields

 

/wp-content/uploads/2016/08/7_1027279.png

 

As mentioned previously, when the opportunity is converted to a quote the pricing will not copy over. This works as designed. The opportunity is not legally binding and the quote document is, so the pricing must be specific to the quote object

 

External Pricing for Sales Quote, Sales Order, Work Ticket

 

The external pricing feature for sales quote, sales order and work ticket work the same. This pricing calls the SAP ERP pricing, returning the conditions and pricing, allowing the C4C user to adjust discounts, and or remove other special pricing, and then get updated pricing again from SAP ERP. Once the pricing on the C4C quote or C4C order is finalized, this pricing is passed to SAP ERP when the ERP order is created.

 

If free goods, product availability, credit status, product substitutions are maintained in SAP ERP or SAP CRM, they are returned with the call. Additionally, if the material is a bill-of-material (BOM), the pricing result also returns the BOM explosion.

 

Cloud Configuration

 

Cloud configuration for external pricing includes scoping, fine tuning, and code list mapping.

 

Scoping

 

For quote pricing, you must answer the question in the Integration into Sales, Service, and Marketing Processes area.

 

 

For quotes and orders in the Sales Quotes area answer the scoping question:

 

“Do you want to use an external application to determine prices, free goods, product availability, and credit status for sales quotes in your cloud solution?”

 

 

For work tickets in the Service Requests area answer the question:

 

“Do you use an external application to determine prices for work tickets in your cloud solution? “

 

/wp-content/uploads/2016/08/8_1027280.png


Fine tuning

 

In fine tuning you need to maintain document types, pricing procedures, condition types, and code list mapping. This is done in the fine tuning activities for Sales Quote, External Pricing, and Code List Mapping.

 

 

Fine Tuning for Sales Quotes: Within the fine tuning for quotes you add a document type. This document type is set to external pricing.

/wp-content/uploads/2016/08/9_1027281.png

In the code list mapping, the document type is mapped to the SAP ERP sales order type that is used to simulate the order to generate the pricing.

 

 

/wp-content/uploads/2016/08/10_1027282.png

Fine Tuning for External Pricing: In the External Pricing fine tuning activity you provide the SAP ERP pricing procedures and SAP ERP pricing conditions. The pricing procedure maintenance is required in order to maintain the schema-dependent texts for the sub-totals. The ERP condition types need to be maintained so that when you get call the pricing you can see the condition types with the correct text, as it is in SAP ERP. You also need to maintain the text subtotals. This will show up in the quote document.

 

 

The following screenshot shows a common pricing procedure in SAP ERP, RVCXUS. Notice the procedure name and steps in the procedure are provided.

/wp-content/uploads/2016/08/11_1027283.png

The following is an example of the condition types. These must be maintained so that the correct text is displayed in the quote.

 

/wp-content/uploads/2016/08/12_1027284.png

When you create the quote, you can personalize the screen to show the pricing procedure being used.

 

/wp-content/uploads/2016/08/13_1027285.png

 

When you create the quote you can see the pricing conditions in the quote.

 

/wp-content/uploads/2016/08/14_1027286.png

 

Communication Arrangement

 

The integration flow spreadsheet at https://service.sap.com/cloud4customer contains all the details from the communication arrangement name to the target URL’s, to the operations mappings and all other details. Note that there are separate communication arrangements integration flows for the quote and the work ticket pricing. This is due to the different mapping services required for different objects in SAP Cloud for Customer.

 

PDF Print Form

 

For print form SAP includes the following in the output message for the pricing details:

 

Item Data:
• AdjustedNetAmount

• AdjustedNetPrice

• PriceComponent from ‘ToBePrintedItemPriceComponent’

 

Header Data:
• NetAmount

• PricingProcedureCode

• PriceComponent from ‘ToBePrintedItemPriceComponent

 

To adapt the form template changes the Adobe LifeCycle Designer is required. The ‘ToBePrintedPriceComponent’ depends on the customizing of the OnPrem system. If condition is valid for printing the price element will be included in the output message.

 

ERP Configuration

 

In SAP ERP you need to configure the Web Service for the external pricing. It is called COD_SALESORDER_SIMULATE.

 

Middleware Configuration

 

There is no special configuration required for this scenario. The details of the iFlow and service names are found in the integration flow spreadsheet at https://service.sap.com/cloud4customer. Note that there are separate integration flows for the quote and the work ticket pricing. This is due to the mapping on the ERP side.

 

Example with free goods, product availability, and credit status

 

Free goods is shown when a pricing condition exists, for example, 0NRA in the example below, includes the free goods from the pricing

 

/wp-content/uploads/2016/08/15_1027287.png

 

Product substitutions are shown when the material determination has been configured in SAP ERP. In the C4C pricing call shown below, product ID 10000600 was the original product. After the pricing call, product 10000592 is the substituted product.

 

/wp-content/uploads/2016/08/16_1027288.png

 

The following screenshot shows an example of the product availability check return.

 

/wp-content/uploads/2016/08/17_1027289.png

 

The credit limit result is shown in the header part of the quote.

 

/wp-content/uploads/2016/08/18_1027290.png

 

In the next example first is shown a simple BOM in SAP ERP. Notice the material is called “Cloud server Medium” and it has two products in the BOM.

 

/wp-content/uploads/2016/08/19_1027291.png

 

For that same bill of material you see the “Cloud Server Medium” product in C4C prior to pricing call:

 

/wp-content/uploads/2016/08/20_1027292.png

 

After the pricing call we now see the two BOM products:

 

/wp-content/uploads/2016/08/21_1027293.png

 

Special considerations

 

Both internal and external pricing are supported for quotes. For sales orders, only external pricing is used today. The sales order will support external and internal pricing in an upcoming release.

 

Once you get the price results back, the external system controls what can and cannot be changed. For example, you can increase the price but cannot change a value added tax returned. Once you change a value and calculate the price, your change remains.

 

The status field has the status from ERP. Yellow means inactive and red means error.

 

/wp-content/uploads/2016/08/22_1027294.png

 

Sales Quote External Pricing for SAP CRM

 

CRM supports external pricing for the quote. It does not support external pricing for the order or the work ticket. For the quote it works the same as SAP ERP, so the cloud configuration previously discussed applies to SAP CRM as well. The service and middleware details are in the integration flow spreadsheet at https://service.sap.com/cloud4customer.

 

 

In SAP CRM transaction code SOAMANAGER you will see EXTERNALSALESDOCUMENTDATAQUERY.

 

/wp-content/uploads/2016/08/23_1027295.png

 

/wp-content/uploads/2016/08/24_1027296.png

 

BADIs (Business Add-In)

 

If you want to see the pay load of any of the pricing requests, turn on the trace in transaction code SRT_UTIL to trace the call and view the payload. If you are using SAP NetWeaver Process Integration or SAP Process Orchestration as your middleware, you can view the payload. If you are using SAP HANA Cloud Integration, you must turn on payload monitoring.

 

If you need to extend the pricing request, BADI’s are available in the IMG using the path Integration to Other mySAP.com Components → Integration with SAP Cloud for Customer → Application Specific Settings → Sales Processing → BADIs.

 

/wp-content/uploads/2016/08/25_1027297.png

 

 

You may also refer to :SAP Cloud for Sales Pricing

To report this post you need to login first.

3 Comments

You must be Logged on to comment or reply to a post.

Leave a Reply