3.15.10

Release Date: 2024-10-11

Software Version

The document refers to the following applications and corresponding software versions:


Application	Version
Promotion Calculation Engine	3.15.10

The software depends on the following applications:


Application	Version
SAP Omnichannel Point-of-Sale by GK	7.7 (5.25.2)
SAP Customer Activity Repository Including XSAC_OPP_PPS Software Component Version	-

What's New


Issue Key	Release Notes	Note
PPCE-7523	CalculationBaseSequence for Bonus Points Multiplier Promotions The Bonus Point Multiplier promotion calculation has been enhanced to consider the previously ignored calculationBaseSequence parameter of the price derivation rule. The calculationBaseSequence parameter's value is considered the same way as it is for other promotions on their respective calculation level. In the event of multiple Bonus Point Multiplier promotions being available, the possible different values of the calculationBaseSequence parameter allow the retailer to define whether any two multipliers should stack (apply on top of each other) or not (use the same original calculation base amount) giving more refined control over the calculation result. The calculationBaseSequence-related enhancement for Bonus Point Multiplier promotions is disabled by default to ensure backwards compatibility and can be enabled using the benefitMultiplierCalculationBaseSequenceEnabled PCE system parameter.
PPCE-2859	Increase test coverage for pce-consulting-packages After pce-consulting-packages were moved to the PCE repository, it was discovered that test coverage was low - only approx. 60%. Test coverage has now been increased to more than 85% as usual.
PPCE-2503	Refactor use of ManualRuleWrapper The PCE internal ManualRuleWrapper class was refactored and optimized. After the changes, the manual rule wrapper was added to the PCE's model API to make sure that it is stable for release. Separate default and GK-specific implementations are maintained now. The latter allows convenient access to the GK-specific custom fields of the rule. The use of the ManualRuleWrapper was optimized so the previously observed double rule wrapping is now avoided in all cases.

Resolved Issues


Issue Key	Release Notes	Note
PPCE-7623	Correct handling of "not consumed" coupons Coupon consumption code NOT_CONSUMED(02) now behaves as "consumed per transaction". When a promotion with such a consumption code is applied, the coupon is consumed by a transaction and is not available for subsequent promotions with a different consumption type (CONSUME(00) and CONSUME_PER_ITEM(01)). However, the coupon consumed by a transaction will be available for subsequent promotions with the same type of consumption (NOT_CONSUMED(02)). See the Functional Guide for more details.
PPCE-7621	NPE when some fields are not specified in the external modifier PCE code for mapping a ClientAPI request and response has been adjusted to not throw a NullPointerException when any optional field is missing in a modifier or a modification line item is added to the request for an externally applied promotion price derivation rule.
PPCE-7619	Corrected appliedQuantity for prorated Buy N Get M benefit The retailPriceModifier's appliedQuantity value has been corrected for Buy N Get M benefits which are prorated between all triggering items. Prior to the fix, the appliedQuantity contained the quantity of all triggering items - in this scenario, the quantity of proration items. This was corrected according to the specification, which says that the appliedQuantity is the sum of the quantity of all discounted items.
PPCE-7613	Externally applied benefits are not considered and, at the same time, points proration is wrong for bonus points transaction-related promotions Within this task, two problems related to bonus points transaction-related promotions were fixed. First, it has been fixed that externally applied benefits are considered. In addition, it has been fixed that proration for each line item is calculated correctly.
PPCE-7587	Line items are not sorted according to their sequence number for Recalculate Transaction API The sorting of line items according to their sequence number for Recalculate Transaction API has been fixed.