As anticipated in the previous blog "SAP ReX - first customer went live with SAP Retail Execution" here I am to tell something more about the new ways to run implementation projects.
During the time it became clear that Mobile has strong impacts also on the ways the implementation project runs.
The new interaction model is relevant also for most the project members like key-users, functional specialists, developers and system administrators. Things happen while commuting, jogging, riding bicycles and even during lunch time. System Design and also Unit Testing occurs anywhere and unfortunately at any time.
Some examples follow.
Alternative Unit of Measurements
07:15 am Alessandro Lavazzi takes a break from his running workout. Switching from RunKeeper to SAP ReX, he verifies the doubt about the list of alternative unit of measurements per each material and figures out the solution.
In the morning a new enhancement is defined and implemented. The list of alternative UoM are now configurable via a custom table that support filters per Sales Org or even per item.
Activity Journals and Surveys
06:45 am (as well as during several times in the airports) @Maurizio the CRM leader, verifies three new Activity Journals and two new Surveys prepared in the CRM backend by other colleagues. In a brief eMail he explains how to improve the solution.
Arrived at customer site, @Maurizio presents the proposal that is appreciated by key-users.
SoldTo : ShipTo
19:15 pm @Andrea calls Daniela Consonni asking to check that posting a Sales Order with a certain SoldTo and ShipTo combination, it’s not more allowed by the system. While commuting home on the Milan underground, Daniela Consonni confirms everything works as expected.
The day after, the Master Data design is finalized introducing an enhancement and for specific business scenarios swapping ShipTo with SoldTo.