Realization phase in Template/Implementation project

[Former Member]

Hello!

We have completed our blueprinting in SM40 on a project which was created as a template project. Now to kick-off realization phase, should we create a new implementation project out of the template..or ..just configure the project as a template itself...

What are the pros and cons? What is the right way of doing it..

Appreciate any advise/inputs.

Thanks.

-

Mike

[Former Member]

Hi Mike,

in the template project every customizing element has the attribute global / harmonized / local.

Even if a rollout directly with the template project is possible (never heard of that), you would loose one of the greatest advantages of the global rollout functionality:

When copying the template project into an implementation project, all customizing elements set as global are "locked" and can not be changed by the local support teams. The ones with attribute "local" can (details see attribute specification). Thus you ensure that local settings can be applied and global processes remain as defined.

Next step is to centrally develop a new version of the template for roll-out, while your maintenance teams can work with the implementation project(s).

Another decision is to use one Implementation project for all roll-out candidates (pro: all relevant documentation in one project; con: documents need to be well arranged for not to loose track) or several Implemenation projects for each roll-out candidate (con: scattered documentation; pro: easy overview per roll-out candiate).

Hope this clarifies a bit...

Regards

Christoph

[Former Member]

Any advise folks? I am in the same situation too.

Thank you

Mark