3.15.8
Release Date: 2024-08-07
Software Version
The document refers to the following applications and corresponding software versions:
| Application | Version |
|---|---|
| Promotion Calculation Engine | 3.15.8 |
The software depends on the following applications:
| Application | Version |
|---|---|
|
SAP Omnichannel Point-of-Sale by GK |
7.7 (5.25.1) |
| SAP Customer Activity Repository Including XSAC_OPP_PPS Software Component Version | - |
What's New
| Issue Key | Release Notes | Note |
|---|---|---|
| PPCE-7291 | Restriction for customer-specific price promotions and SAP ExtendedDiscountAmount handling From now on, the PCE can apply only one customer-specific price promotion to each line item. This changes the previous behavior where, in some cases, multiple customer-specific price promotions could be applied to a single line item, resulting in an unintended and confusing result. This new restriction applies to both the SAP context and GK context. The previous behavior can be restored by a project-specific PCE customization if necessary. In addition, the calculation logic for the ExtendedDiscountAmount value in the SAP ClientAPI response has been changed. Similar to the GK context, this value now also considers possible price increases from applied line item-related promotions. But in contrast to the GK context, the field in the response contains a non-zero value only if the total of all discounts and price increases provided by all applied line item-related promotions leads to reduction of the original line item's price. |
|
| PPCE-7342 |
Conflicting Promotion Pairs Resolution From now on, the PCE supports a special algorithm for faster resolution of conflicting promotion pairs which was taken over from the Loyalty Engine. If enabled by the system parameter conflictingPromotionPairsResolutionEnabled, the new algorithm is executed before the standard conflict resolution algorithm such as the BruteForce or Greedy algorithm. It tries to find a promotion which conflicts with one other promotion only and applies such a promotion if it provides a better benefit for a customer. This can significantly reduce the number of conflicting promotions to be processed by the regular conflict resolution algorithm in some specific cases. In other cases, however, the new algorithm may not be able to resolve any conflict and all conflicting promotions must be processed by the standard conflict resolution algorithm anyway. This includes situations where each promotion conflicts with two or more other promotions, or situations where some of the conflicting promotions need to consume a coupon. The conflicting promotion pairs resolution algorithm is mainly intended to be combined with the BruteForce conflict resolution strategy, where it can reduce the number of combinations the BruteForce has to check. It can be combined with the Greedy conflict resolution strategy as well. In that case, the overall calculation cannot be faster but the final result may be more precise, which means it can provide a better benefit for a customer than a pure Greedy would calculate. For more details, see the chapter Resolution of Conflicting Promotion Pairs in the PCE Functional Guide. |
Resolved Issues
| Issue Key | Release Notes | Note |
|---|---|---|
| PPCE-7478 | MAPO modifier on a weighted line item with a fixed price leads to lower discount A bug in the normalization of external and MAPO modifiers in a line item with a fixed price has been corrected. Such modifiers no longer lead to a reduction of the calculation base amount because of rounding and therefore to a lower discount of regular promotions applied by the PCE. |
|
| PPCE-7427 | Incorrect detection of independent promotions for best price calculation If, for some reason (e.g. due to a limit), the trigger item did not receive a benefit from a promotion, then it was considered as not related to this promotion. This could lead to incorrect identification of independent promotions and incorrect calculation of the best price. This bug has been fixed. |