Top Lessons Learned from a Completed S/4HANA Brownfield Project from a REALTECH Technical Consulting
REALTECH has been doing SAP technical consulting focused on migrations for over 29 years, this has included 1000’s of SAP migrations for fortune 500 companies without a single failure with a 100% success rate going back to 1994. We understand technically how to do an S/4HANA Migration Project specifically focusing on brownfield technical migrations. We have also teamed up with the best functional partner in the market making us the best partner in the ecosystem, we would make your S/4 transformation stress-free and the lowest risk possible.
Below are lessons that we have put together based on our years of SAP experience focused on this niche:
• Have a project plan created before the project distributed to all teams and reviewed weekly
• If working with multiple Solution integrators, Ensure the Functional team picked have completed a S/4 project and this includes experience in the testing phase.
• Implement a proper change mgmt solution for the purpose of tracking changes in the systems, work orders, spreadsheets and emails are not sufficient enough for this important project (JIRA,SNOW, RT are some of the ones we use for projects)
• When a system is copied, be sure to track all system changes or transports using a automation solution. spreadsheets and emails are not sufficient enough for this important project (JIRA,SNOW, RT are some of the ones we use for projects)
• BASIS team are the experts for the technical work – these migrations take time and the 1st ones are used as a guide for the Production systems. Ensure that SAP best practices and standards are followed.
• Ensure proper planning for these tasks and If one is taking longer then expected there should be a small buffer built in the project plan.
• Make sure you have an experienced S/4 PMO team that supports you and they want success from all teams collaboratively.
• Implement an SAP Transport solution for auditing and tracking of transports in all systems – This is a MUST, so there is no confusion when another team sends email to implement transports that aren’t supposed to go in until a later time but then Basis is blamed, don’t laugh it happens, a transport automation solution would have eliminated this risk and have audit tracking!
• A project SOW must be clearly defined and agreed upon, so tasks are crystal clear especially adding resources to a projects to eliminate any confusion.
• There are several key decisions in a project and going live is the biggest- don’t just go live and then months of hypercare to meet a date- makes absolutely no sense from a business perspective or a basis perspective – to ensure success, proper planning and testing are HUGE before go live, ensure this is done before any go live date is set or targeted and plan for it, in the end its about your customer/business from our basis perspective and if they aren’t happy and your constantly on a fire drill fixing things then the project won’t be a success!
Contact us to learn more how we can help you transition to S/4 with the SAP Basis Experts @ firstname.lastname@example.org or you can contact me at David.Milano@realtech-us.com or call @ 856-689-2929