Symptom
When sending a multi-valued attribute in a Document Pricing call, the separator is not being processed, resulting in a single valued attribute (single string containing all values).
Environment
SAP CPQ
Reproducing the Issue
- On Pricing Procedure, create an Item Specific Pricing attribute and set it as multi valued
- Configure a product, and check that, on configurator, where Stateless Call is done, the multi valued attribute is properly parsed, and sent to CPS as multiple values ({"name":"MultiValuedPricingAttribute","values":["<value1>","<value2>"]})
- When Document Pricing Call occurs, on Quote Level, verify that for same attribute, the multi valued attribute is considered as a single value ({"name":"MultiValuedPricingAttribute","values":["<value1>|<value2>"]}.
Cause
Limitation.
Resolution
- Issue: Document Pricing is not properly processing multi-valued pricing attributes, resulting in pipe-delimited values being sent as a single string in CPS Call
- Workaround: Avoid using multi valued attribute in Document Pricing Calls and if needed
- ETA:CPQ-2608.
See Also
Keywords
document pricing, multi-valued attribute, multiple values, stateless pricing, CPS, Integration, Variant Configuration, VC, CPQ , KBA , CEC-SAL-CPQ , Sales Cloud CPQ , Problem
Product
SAP CPQ 2024
SAP Knowledge Base Article - Public