cancel
Showing results for 
Search instead for 
Did you mean: 

Best practices using CHARM along with Focused build in S/4 HANA project

Saikumar
Participant
0 Kudos

Hello Experts ,

We have a scenario that Phase 1 ( developments) of our S/4 HANA project going live following Focused build process managements concepts . Post go-live we would like to use CHARM for change & release management for maintenance . However Phase 2 ( developments) of project would still run using Focused build ( go-live at later point of time) along with CHARM (For Operations on phase 1) . Could you share best practices considering this scenario . Like... Should we continue using same branches ? How about changes to the documentation ? What challenges we might encounter with this setup ?

Thank you ,

Regards,

Sai

Accepted Solutions (0)

Answers (2)

Answers (2)

VigneshPrabhu99
Contributor
0 Kudos

Hello saikumarm

As per Focused Build open SAP course, it is possible to have Focused Build and CHARM working in the same Solution Manager system.

You don't need to worry about documentation as Focused Build as well as CHARM will use the same BPML hierarchy defined in Solution Documentation.

You might get some conflicts if the same document has been edited/modified by CHARM or Focused Build transaction types at the same time.

But trust me, it won't have any impact on Solution Documentation documents.

For a safer side, maybe you can have some different document naming convention for CHARM and Focused Build, or you can use a custom attribute to mark whether the document is part of PHASE 1 development or PHASE 2 development.

Thanks,

Vignesh

JSULLIVAN
Participant
0 Kudos

I don't think you will find a "Best Practice" on the topic that will result in you knowing what to do. The different Development and Maintenance branches better allow for long term changes vs short term changes for both documentation and transports. I would suggest you ask a few questions...

1. Will the development and management of the documentation for Focus Build be considerably longer than documentation adjustment for Operations? If yes, then you might want Development, Maintenance, and Production branches.

2. Will there be a new set of systems for the continued Focus Build work vs Operations? If yes, then you may want Development, Maintenance, and Production branches. (Note: that different cycles for Focus Build vs Operations together with Cross-System Object Lock can keep you from needing a new set of systems in many cases).

Best regards,

-John Sullivan