As anticipated in the previous blog “SAP ReX – first customer went live with SAP Retail Execution” here I am to explore different technical aspects of the solution analyzing some interesting and strange behaviors.
During the implementation project, Sybase Unwired Platform (SUP) has been a key component but I would say it was not so evident during the day by day life.
Even if everybody is aware of SUP, it is like if it operates in a kind of silent mode.
About SUP, from the project prospective, one of the few and most interesting thing to know is that to boost performances, it caches data that comes from the back-ends (e.g. SAP CRM).
Why the new Product is not download?
At the top of the FAQ document we filled during the project there is the question “Why the new Product is not download?”.
Here the business case is that the SAP CRM business administrator performs changes to the active Listing adding for example a new Product X-100.
The strange behavior is that the item X-100 will be visible in SAP ReX only some minutes later (max 10, avg 5).
Only after some minutes, the Sync will download the fresh version of the Listing including item X-100.
Deep diving into this case, it’s important to note that per each Mobile Business Object (MBO), it’s possible to check and optimize the type of cache and the related refresh interval time via SUP Control Center.
Did you got the point?
Thus the cache related to the Products MBO is set by default to 10 minutes.
It means that a Sync request reads fresh data from the back-end only the refrsh interval expires. Otherwise it reads from an SUP local cache that keeps the last version of the data to be faster providing it back to the device.
In DEV and QAS, it may be a good idea to lower the refresh interval to 2 minutes. 😉