06-15-2022 1:22 PM - edited 02-04-2024 3:41 AM
Hi,
We are using the SAP Public Cloud (Multi-Tentant) solution and are seeing a major problem with the Manage Your Solution / Configure Your Solution App. It seems that when you press the Proceed to Run Phase button in MYS, all changes that have been done in the Q system are then included on a transport and release to be sent to the Production system regardless of the Status of the configuration item itself.
We have talked with SAP about this and they say that while this is "not ideal" it is the way it is, and they are not investing in this area at all, since by the start of 2024 (2 years from now) we will all be moved to the 3 System Landscape and Central Business Configuration anyway.
I'm wondering if any SAP Customers have had experience with this situation and possibly have a process that they could describe that works reasonably well to handle a large project going n at the same time as Production Support activities are happening.
Thanks
Hi Jeff,
I have a lot of experience with S/4HANA Cloud and transporting and managing change projects in the current Manage Your Solution/Configure Your Solution structure and I used ECC too in the past. S/4HC is a different animal completely in that you don't own and manage the backend, but it isn't difficult to manage build work movement in my experience (I currently have 47 localizations and multiple business streams).
With S/4HANA Cloud I've found the most effective methods for management are:
I would encourage you to check out the SAP Activate roadmap for some additional tips and what the operation rules/requirements (https://go.support.sap.com/roadmapviewer/#/group//roadmapContentPage/IMPS4HANACLDENMGMT:901B0E6D3F501EE6ABB4713604755B4A)
With any change project and transport process communication and documentation is key. Emergency transports will happen, but not all build work is break/fix or should be treated as an emergency. Changes with GL accounts as an example can be managed outside of a change project as can extensibility. You also have the ability to import a change project faster than the daily SAP scheduled job using the Import Collection app when needed.
Hope that helps,
Ryan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@anholme - transition of existing customers to CBC is in the roadmap but is not available today. If they were to completely restart their program, including commercials, then and only then could they take advantage of CBC for their S/4HANA Cloud. Trust me when I say that I am EAGER for all of our S/4HANA Cloud customers to have CBC capabilities. 🙂
Thanks for responding on this community.
Greg
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Jeff,
Same issue here, projects vs support activities. There is too much that requires a change project rather than access by an administrator to change.
There is no real process except for planning the projects and hoping nothing comes up. In the last two weeks I've done 3 change projects for production support. I have a scope item to have activated that will require a change project and I am planning on doing that next week.
On the bright side - at least the updates are fewer now, that was also limiting factor.
Thanks,
Tricia
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
91 | |
8 | |
7 | |
4 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.