SAP CPQ 2.0 - Variant Pricing - Line Item prices stopped working since Release 2305 & showed error.

[Alexander_0001]

Dear SAP Community,
since the release of 2305 the Variant Pricing stopped working for our system for configurable products. The base price is still available in catalog, configuration interface and on the quote but the line items and their variant prices are not available any more.

Since they have been disappeared we got the following error message in the log:

<strong>Level: </strong>Error Labels<br><strong>Title: </strong>The pricing document contains errors.<br><strong>Description: </strong>Userexit (type VAL, appl. V, usage A, number 48) is not implemented<br><strong>Logger:</strong> CPSDocumentPricingOrchestrator

The General Attribute Mapping has the following setup

The Price Mapping of my Pricing Procedure and Price Conditions is the following:

Parts of the Pricing Call Payoad looks the following way:

<strong>CPS request received<br>URL: https://..
Method: POST
Status: 200
Request Payload: {"docCurrency":"EUR","locCurrency":null,"pricingProcedure":"Y10101","groupCondition":false,"itemConditionsRequired":true,"items":[{"itemId":"1","externalId":null,"quantity":{"value":1.0,"unit":"EA"},"exchRateType":"M","exchRateDate":"2023-05-24","productDetails":{"productId":"000000000000000474","baseUnit":"EA","alternateProductUnits":null},"attributes":[{"name":"KOMK-WAERK","values":["EUR"]},{"name":"KOMP-PRSFD","values":["X"]},{"name":"VBAK-VTWEG","values":["10"]},{"name":"KOMK-VKORG","values":["1000"]},{"name":"KOMK-SPART","values":["00"]},{"name":"KOMK-LAND1","values":["DE"]},{"name":"KOMK-VTWEG","values":["10"]},{"name":"KOMK-KUNNR","values":["1000051"]},{"name":"KOMP-PMATN","values":["000000000000000474"]},{"name":"KOMP-SPART","values":["00"]}],"accessDateList":[{"name":"KOMK-PRSDT","value":"2023-05-24"},{"name":"KOMK-FBUDA","value":"2023-05-24"}],"variantConditions":[{"factor":1.0,"key":"BOO_0020"},{"factor":1.0,"key":"CAM_0010"},{"factor":1.0,"key":"ENG_0020"},{"factor":1.0,"key":"FBL_0010"},{"factor":1.0,"key":"HEA_0020"},{"factor":1.0,"key":"HYD_0020"},{"factor":1.0,"key":"LIG_0010"},{"factor":1.0,"key":"OUT_0010"},{"factor":1.0,"key":"OUT_0020"},{"factor":1.0,"key":"RAD_0010"},{"factor":1.0,"key":"RBL_0020"},{"factor":1.0,"key":"SEA_0020"},{"factor":1.0,"key":"SPE_0010"},{"factor":1.0,"key":"TIE_0030"}],"statistical":false,"subItems":[]}]}

I assume the error could be caused by the General Attributes Mapping but I am not sure. Additionally, I have no clue how to fix the mentioned error. It would be great if someone could share a General Attributes Mapping that could work on a very simple level. If someone has already faced the error and found a solution that which could be shared that would be great help for me as well.

Look forward to your suggestions and your approaches to set up a working pricing.

Kind regards
Alexander

[dirkfischer · Accepted solution]

Hi Alexander,

regarding the missing table you may open a customer case on component LOD-CPS to check this. Nevertheless the error could point into a direction of missing privileges for the used replication user. Table A305 is a standard table and should be available on the backend system.

[former_member319514]

Hello Alexander,

VAL formula 48 is for the "Down payment" scenario which is not supported by CPS pricing.

Please refer to the below note (point 6)
2894167 - Differences between Pricing service and ERP’s sales pricing

But VAL Formula 48 should not be the reason for the issue reported by you.

In the CPS/CPQ context, you may remove the conditions related to the down payment scenario from the pricing procedure.

Please create the ticket in LOD-CPS-PRC with the CPS tenant details and request JSON to further look into why there is no value populated for VARC condition purpose.

[Michael_W]

Hi Alexander.

From Pricing service perspective I can tell that message 'Userexit (type VAL, appl. V, usage A, number 48) is not implemented' is just a warning that you should also see in the response of the pricing service. But that's not new, was not introduced in May.

List of supported condition VALue formulas can be found here: Condition Value Formulas | SAP Help Portal

As 48 is not supported the related condition type would be returned as inactive by the pricing service:

Overview | SAP Help Portal

If a pricing procedure contains routines that are not supported, the respective condition will be marked as inactive, inactiveFlag = X, in the pricing result. Requirements need some special consideration: if the requirement formula is not supported, it is treated as if returning false. Such conditions will not be part of the pricing result.

In your pricing service payload, I only see one item (no subitems) and many variant condition keys. So I assume you do not expect real quote items to see in the responder but the surcharges because of selected options/condition keys.

So you would have to check first if active surcharges are returned by the pricing service for those variant condition keys. If not, reproduce with engine trace enabled and see why nothing was found for those variant condition keys: Trace for Pricing Service | SAP Help Portal

If Pricing service returns active conditions for those variant condition keys, but they are not displayed in CPQ responder, then this might be a bug on CPQ side.

[Alexander_0001]

Hi Michael, thank you very much for your very detailed reply on my issue.
I checked the pricing procedure in S/4HANA bu found only the identifier 48 as an alternative calculation for a condition type:

I want to check if we would fix the warning with removing the respective Condition types from the pricing procedure or replacing the calculation/ pricing routine maybe with another one.

I found maybe something in the CPS service which could be te reason for my issue:

The CPS service tells me that it can not find a pricing table (A305).
Could this lead to the unsuccessful price request?

[yogananda]

alexander-maerz

seems like a BUG.. could you quickly raise Support ticket for your issue