3.14.11

SAP Omnichannel Point-of-Sale by GK

7.6 (5.23.3)

SAP Customer Activity Repository Including XSAC_OPP_PPS Software Component Version

Remove trailing zeros in missingAmount/missingQuantity

From now on, trailing zeros are removed in the missing amount and missing quantity values in the promotion recommendations.

Therefore, expectations for missing amount and missing quantity values in the following JBehave tests had to be corrected:

• cha_promo_recommendation_1
• cha_promo_recommendation_2
• cha_promo_recommendation_3
• cha_promo_recommendation_4
• cha_promo_recommendation_5
• cha_promo_recommendation_6
• cha_promo_recommendation_7
• cha_promo_recommendation_8
• cha_promo_recommendation_9
• cha_promo_recommendation_10
• enhanced_uom_calculation
• force_the_promo_recommendation
• items_without_uom_calc

NPE can be thrown if line item filtering by RebatableItemFilterPlugin is used

PCE could throw a null pointer exception if a RebatableItemFilterPlugin implementation filtered out some items from the benefit calculation and, at the same time, a currently processed eligibility had the thresholdForSingleItemFlag parameter set to true. This bug has been fixed.

Loyalty discount initially shown in registration mask but missing on subtotal mask

PCE now checks generated internal eligibility IDs for ad-hoc promotions for possible duplicity and re-generates such IDs, if necessary.

Loyalty points with new price

The behavior of the bonus points promotions with price modification method "New price" has been corrected for the following cases:

• the transaction-related promotion applied a bonus count which is lower than previously applied bonus points count by another transaction-related promotion, in this case the promotion is invalidated correctly
• line item- and transaction-related bonus points promotions are applied to the returned items

CalculationBaseSequence -2 is missing in a ClientAPI response

Mapping of promotion data loaded from SAP DAL has been corrected to not take null value instead of -2 for the calculation base sequence. Thanks to this change, the ClientAPI response now always contains the original CalculationBaseSequence value set in the promotion MD.

External RPM prevents internal RPM with lower sequence to be mapped to ClientAPI response

If a line item has external and internal retail price modifiers, and the internal retail price modifier has a lower sequence than the external one, then the internal retail price modifier is not mapped into the ClientAPI response. This bug has been fixed.

NPE when processing ad hoc eligibility with MSet

PCE no longer throws a null pointer exception if its request contains an ad hoc promotion with a merchandise set eligibility, but, at the same time, the request transaction does not contain a line item yet.

Duplicate key exception when multiple conditions are triggered

Ad-hoc promotions with multiple conditions triggered at the same time are now not causing an exception and all conditions are applied to the transaction.