As of SAP Hybris Marketing Recommendation 1602, the following additional and enhanced functions are available:
The PROD_RECO_RUNTIME_SRV
OData service now enables customer channels to receive recommendations generated by Recommendation. For more information, see SAP Library for SAP Hybris Marketing on SAP Help Portal at http://help.sap.com/mkt. Choose a release and then .
Note
The /SAP/CUAN/CUAN_RECOMMEND
Representational State Transfer service (RESTful service) is no longer available.
If you choose to overwrite customizing entries when running the BC sets during the upgrade process, the following changes to standard delivery algorithm names will occur:
Old Algorithm Name | New Algorithm Name |
---|---|
Often Bought Together (Apriori Lite) | Often Bought Together (SAP ERP / Apriori Lite) |
Often Bought Together Across Transactions (Apriori Lite) | Often Bought Together Across Transactions (SAP ERP / Apriori Lite) |
Often Bought Together | Often Bought Together (SAP ERP) |
Often Bought Together Across Transactions | Often Bought Together Across Transactions (SAP ERP) |
Often Bought Together (FP-Growth) | Often Bought Together (SAP ERP / FP-Growth) |
Often Bought Together Across Transactions (FP-Growth) | Often Bought Together Across Transactions (SAP ERP / FP-Growth) |
Top-N Interactions | Top Viewed |
The following additional standard delivery algorithms are now available in SAP Hybris Marketing Recommendation (including Manage Recommendations
):
Algorithm Name | Algorithm Description |
---|---|
Often Bought Together (Interactions) | This algorithm uses records from the data source SAP Hybris Marketing Interactions. The records are grouped by session ID using SQL. |
Often Bought Together Across Transactions (Interactions) | This algorithms use records from the data source SAP ERP Sales Document Items. The records are grouped by customer ID using SQL. |
Top Sellers (Interactions) | This algorithm returns top sellers from the data source SAP Hybris Marketing interactions. |
Remove Items Already Purchased (SAP ERP) | This algorithm uses records from a transaction data source, for example SAP ERP sales document items. The algorithm identifies items that have already been purchased and removes them from the results that are returned at runtime from the other algorithms within the model. |
Remove Items Already Purchased (Interactions) | This algorithm uses records from an interactions data source, for example SAP Hybris Marketing. The algorithm identifies items that have already been purchased and removes them from the results that are returned at runtime from the other algorithms within the model. |
You can now define independent generation refresh rates for each algorithm that is contained in a model. For more information, see the following:
Manage Recommendations
now allows you to filter scenarios and models using an Error
status tile to identify errors that occurred during model generation.
The validity of an offer has been extended. The start and end date have been removed from the Basic Data
tab. Instead the Validity
tab was added to define the validity date ranges. You can now define single and recurring time periods and validity periods, during which the offer is either visible only or visible and valid. These periods allows the marketer to control when a consumer is able to see or get an offer and when a consumer can consume or redeem the offered product or service.
Product Version | SAP Hybris Marketing Recommendation 1602 |
---|---|
Area |
|
Country Dependency | Valid for all countries |