3.15.7
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.7 |
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-7376 |
PCE - Validation of negative discount values Validation of negative values was added for rebate and Mix&Match rules. The rebate rule will be rejected if a negative value is present for the specified price modification method. The Mix&Match rule will be rejected if all values for the specified reduction methods in all matching items are negative. |
Resolved Issues
| Issue Key | Release Notes | Note |
|---|---|---|
| PPCE-7396 |
Fix mapping of the LoyaltyRewardLineItem Mapping of a LoyaltyRewardLineItem from the ClientAPI request to the internal PCE data model and back to the ClientAPI response was fixed. Now, all appropriate values (PointsAwardedCount, FrequentShopperPointsEarnedAmount and CalculationBaseAmount) are correctly inverted based on a transaction category. |
|
| PPCE-7387 |
Sales vs. Returns: Wrong behavior when using RegularSalesPrice When FixedPriceFlag = true and RegularSalesPrice is provided in the ClientAPI request, the positive RegularSalesPrice for returned items was mapped directly to the internal PCE data model which led to incorrect calculations. The bug has been fixed and now the RegularSalesPrice is negated for the returned items. |
|
| PPCE-7340 |
Negative values in ClientAPI response on the PriceModificationLineItem are not allowed Mapping of a PriceModificationLineItem from the ClientAPI request to the internal PCE data model and back to the ClientAPI response was fixed. Now, all appropriate values (Amount, ExtendedAmountBeforeModification, ExtendedAmountAfterModification, ExtraAmount and CalculationBaseAmount) are inverted correctly. Expectations in the following JBehave test had to be corrected:
|