3.15.9

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.9

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-7522	Improved GEC logging A message about disabled General Exclusion Criteria is now logged only once per condition calculation instead of several times per normalized line item before.
PPCE-7514	ApplicationType for Subsequent Discount Mapping of the SAP ClientAPI response has been enhanced to correctly report the application type of the subsequent discount if it is applied. Regardless of whether the price modification methods of the regular and subsequent discounts are the same or not, the ApplicationType attribute of the PriceDerivationRule in the RetailPriceModifier or in the discount line item now contains the correct value depending on the type of discount that the modifier or discount line item was created for.
PPCE-7339	Transaction-related promotion references Up until now, the PCE provided information about which line items in a transaction were used to trigger specific line item-related promotions (promotions with transactionControlBreakCode values PO or PC) or result-related promotions (promotions with transactionControlBreakCode value RC). From now on, the PCE can also provide information about which line items in a transaction were used to trigger specific transaction-related promotions (promotions with transactionControlBreakCode values SU or SP). For backwards compatibility, this feature must be enabled by the referencesForAppliedTransactionRelatedPromotionsEnabled system parameter. Its default value is false, which means the PCE will not create any new line item references for applied transaction-related promotions unless this is explicitly allowed by configuration. For more details, see the chapter Sale Return Line Item Modifier references in the PCE Functional Guide.
PPCE-5242	Remove circular dependencies in Spring A technical solution was implemented to break two circular dependencies in Spring.

Resolved Issues


Issue Key	Release Notes	Note
PPCE-7504	Bugs in conflict resolution algorithm Two bugs in the conflict resolution algorithm(s) have been corrected: The conflict resolution algorithm no longer stops completely if a group of conflicting partial results was fully resolved by a conflict resolution pre-processor The algorithm correctly splits conflicting partial results into independent groups and no longer produces any ghost groups that only bring calculation overhead
PPCE-7499	Bug in conflicting promotion pairs resolution algorithm The conflicting promotion pairs resolution algorithm no longer throws a NoSuchElementException when some conflicting partial results become independent during calculation.
PPCE-7498	NPE with Greedy - Multiple CSP promotions If multiple conflicting Customer Specific Price promotions with the same sequence and resolution are resolved by the Greedy conflict handler resolution strategy, a null pointer exception may be thrown. This bug has been fixed.
PPCE-7434	ProrateFrom link not referring to the correct line item Inconsistency in sequence numbers has been fixed. ProrateFrom link is now referring to the appropriate line item - either PriceModificationLineItem or LoyaltyRewardLineItem in the most cases. Regarding backwards compatibility, inconsistency can occur only in some edge cases.
PPCE-7362	NPE is thrown in case manual eligibility is present but manual trigger is missing NPE has been fixed in case an ad hoc promotion contains a manual trigger eligibility but a manual trigger in the line item is missing.
PPCE-3187	Wrong mapping of the external RPM's action code in ClientAPI If PreviousPrice or NewPrice parameters are missed in the request in the externally applied Retail Price Modifier, the amount's action code in the response may be wrong. The bug has been fixed and now the action code in the response is the same as in the request for the externally applied Retail Price Modifiers.