No pricing procedure in CPQ for the Variant Configuration

[ildar_dlw]

Dear experts,

We have a solution with CPQ-Variant Configuration and Pricing-S4.

In CPQ we are trying to create a quote with correct pricing and the following error appears in the logs:

As I can see in the error message, pricing procedure is empty (item details replaced with NNN):

CPS communication error for requested URL: https://cpservices-pricing.cfapps.eu10.hana.ondemand.com/api/v1/statelesspricing
Method: POST
Status:
RequestBody: {"docCurrency":"EUR","locCurrency":null,"pricingProcedure":"","groupCondition":false,"itemConditionsRequired":true,"items":[{"itemId":"1",NNN}]}
ResponseBody: {
"status" : 400,
"typeId" : "40002",
"type" : "validation_violation",
"message" : "One or more fields contain an error",
"moreInfo" : null,
"details" : [ {
"typeId" : "40002.001",
"type" : "missing_field",
"field" : "StatelessPricingController.getPricingResult.priceCalcInput.pricingProcedure",
"value" : "",
"message" : "Pricing procedure must be present.",
"moreInfo" : null
} ]
}
Exception:
The remote server returned an error: (400) Bad Request.

Could you please advise from where it comes? And how I can fill the pricing procedure in CPQ?

And should it match pricing procedures available in the Variant Configuration?

Thank you!

[MaxGag · Accepted solution]

Hello,

Have you filled the pricing procedure section in Providers/General Attribute Mappings?

Thanks

[jose_rangel · Accepted solution]

Hi maxgag2,

maybe you have an idea what might be my error.

The pricing procedure that should be used in the CPQ was correctly replicated to the CPS, but after filling the General Attribute Mappings with that pricing procedure, I get the following error:

Could this be related to a wrong filling of the attributes KOMK-VTWEG or KMOK-VKORG?

Thank you

[MaxGag · Accepted solution]

Hello jose_rangel ,

I don't see the error in your last comment.

Thanks

[jose_rangel · Accepted solution]

Hi maxgag2,

we were getting the error that the pricing procedure was not replicated even though we could see a successful replication in the CPS cockpit. We started the replication of the pricing procedure and after that the CPQ could find it.