Defer the cut off of ‘Classic’ Self-Service until more functionality is available in RSSP
Summary:
The user experience of RSSP is known to be vastly different to the classic version. To allow as much time as possible to support users in the transition we had planned to implement RSSP as early as possible, the goal being early August.
RSSP configuration has been in two of our development environment for 4 weeks. During this time it has been reviewed, tested and assessed to ensure it is fit for purpose. Based on our findings and experience, a decision to defer the implementation of RSSP until the Oracle 25A Quarterly Release has been made.
There is some functionality that won’t be available if we implemented now that we could introduce work-arounds for, however the following ‘yet to be developed’ functionality would cause significant disruption, confusion and resource impacts in the purchasing process.