3.15.13
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.13 |
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-7830 |
MLP - Adjust SAP ClientAPI mapping The promotion recommendation benefit mapping for loyalty point type has been changed for the ClientAPI response. |
|
| PPCE-7720 |
Change logging level to WARNING in case an invalid value is to be used for a system parameter but default value is used instead Logging level has been changed from ERROR to WARNING in case an invalid value is to be used for the system parameter but the default value is used instead. Unified logging in case null value was used. Redundancy from log messages and redundant logging have been removed. |
|
| PPCE-7717 |
Improved condition validation for transaction-related promotions The validation for negative discount and bonus points and price increase related validations for transaction-related total condition results have been extracted to dedicated ConditionRebateValidator plugins. These validations are now also handled by the PCE's internal validator service rather than being distributed all over the code at different points of the calculation for a more cohesive code base. |
Resolved Issues
| Issue Key | Release Notes | Note |
|---|---|---|
| PPCE-7809 |
RPM for applied transaction-related promotion is missing in the transaction If a single transaction-related manual promotion was applied multiple times due to several manual triggers registered in a transaction with different trigger sequence numbers, and if that manual promotion conflicted with some other promotion(s) and the Brute Force conflict resolution algorithm was used to resolve the conflicts, then some retail price modifiers or frequent shopper points modifiers for successfully applied promotions might be missing in the result transaction. This bug has been fixed. |