This question was asked to me in Quora.com and below was my answer:
I’m writing here about transitioning functional skills from EBS to cloud. I am writing from the perspective of an EBS functional person who worked on EBS projects and wants to know how their role will change.
Despite Oracle really pushing Cloud there are not a huge number of big implementations yet, so information is not that easy to come by.
A few things we know about Cloud that affect skills used:
* No customizations
* Integrations limited (compared to EBS) but improving
* Hosted in Oracle infrastructure
EBS Oracle Functional Skills
A functional consultant working on projects should strive to acquire 6 key skills; Objectives, Requirements, Design, Build, Test and Transition. These 6 key skills are the bedrock for a successful career; you will not likely be asked to do anything outside these 6 tasks as a functional consultant. These 6 key skills are also the key phases of an Oracle project, in that sequence.
6 Key Functional Consulting skills – 6 key Oracle project phases
Oracle Cloud Functional Skills
Taking the six key EBS skills as a template, which ones will change, and which are now greatly reduced?
Capturing business Objectives is about the high-level goals of a business. An example might be allow recording and submission of VAT.
The requirements phase changes as EBS was requirements-led, and Cloud is solution led. In the EBS world any and all customer requirements were captured and a customization/integration was written. In many clients where I the majority of customer requirements/changes were approved.
Cloud is completely different. Cloud is solution-led, so the functional consultant chooses from the existing feature list, and the business must adjusts its processes to meet the available options.
The Cloud feature set is more expansive compared to EBS, and Oracle promises that many of the integrations and customizations created during their implementations have been replicated by Oracle in libraries that are standard. Oracle also promise access to Visual Builder to enhance the implementation.
Configuration options would seem to be a large part of the functional role now, selecting configuration options to meet business requirements. Design of enhancements is a probability as the business teams generally want something outside standard features.
In EBS world, this meant helping developers build robust customizations and interfaces that would be useful in later testing phases. In Cloud this may change to helping the construction of “enhancements” or supporting integrations with external systems.
Testing should still contain consideration of testing requirements, testing strategy, system(integration) testing, user acceptance testing. Unless you have an experienced cloud implementation team or partner you can see a lot of emphasis in this phase as nobody has a huge amount of Cloud experience.
With Cloud having a series of mandatory feature releases, Testing the new features of each mandatory release means Testing will form part of the ongoing functional responsibilities.
Those taking advantage of Oracle SOAR automated migration should have a smooth experience; all of the configuration and data will be “upgraded” to Oracle Cloud. Without SOAR an experienced Cloud team is needed to ensure that the solution meets requirements when its turned on.
You may be interested in a post + video I wrote on how to become an Oracle Consultant, here: How to Become an Oracle Consultant – I Love Oracle