3.15.11
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.11 |
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-7641 |
PCE validators - Remove redundant validation Calculation result validation has been improved and redundancy has been removed. The PCE core implementations of the LineItemRebateValidator interface were split into the following three parts:
|
|
| PPCE-6781 |
SAP ClientAPI and DAL mapping for Multiple Loyalty Programs The SAP Client API mapping for the bonusPointsType of the RetailTransactionPromotionPriceDerivationRule and the RetailTransactionPromotionRecommendationBenefit were implemented. The new fields are mapped for loyalty points related promotions which define a bonusPointsType in case the Client API's requested version supports the fields. The SAP-related Data Access Layer has been enhanced to load promotions that define a loyaltyPointsType value depending on the current Client API's request version. All such promotions are loaded only if the current Client API's requested version supports the loyaltyPointsType field. In the case of a lower Client API's request version, only promotions which do not define any loyaltyPointsType or promotions which define loyaltyPointsType matching a value of the system parameter defaultBonusPointsType are loaded and processed. |
|
| PPCE-2800 |
Validation of system properties The validation of system properties has been enhanced. In general, negative values have been restricted and strings are allowed to contain only alphanumeric/whitespace characters, underscores and delimiters. More restrictive validation has been added in some specific cases. In case invalid values are used, this is logged and the values are replaced with default values. JUnits for customizable parameters have been added. |
Resolved Issues
| Issue Key | Release Notes | Note |
|---|---|---|
| PPCE-7661 |
Fix missing handling for manufacturerCouponPromotionTenderTypeCode and benefitChooseItemMethod Handling of the system parameters manufacturerCouponPromotionTenderTypeCode and benefitChooseItemMethod has been fixed so that they are no longer ignored by the PCE. |
|
| PPCE-7643 |
Zero position-related non-total points validation Bonus points validation for line item-related promotions with non-total price modification methods was unified with discount validation. |
|
| PPCE-7628 |
Promotions with the same sequence and different resolutions applied to the same item if TransactionRebateMethod=TOTAL Handling of transaction-related promotions in the case of TransactionRebateMethod value TOTAL has been corrected. Prior to the fix, if a line item was not used as a trigger but received a benefit because it was used for the calculation base amount due to the TransactionRebateMethod value TOTAL, such a line item may have received further benefit from another promotion with the same sequence and a lower resolution or, even worse, from another promotion with the same sequence and the same resolution. From now on, only one transaction-related promotion with a given sequence can use any line item as a trigger or grant it a benefit. |