Skip to Content
0

How to handle template project in SAP Solution Manager 7.2 SP05

Oct 12, 2017 at 03:15 AM

180

avatar image

Hi ,

We are having 1 template project and 146 implementation projects in 7.1 version. we have 6 scenarios( 6 sectors) in template projects. How to migrate these projects in 7.2 SP05. we have to move all these project to one single solution or create template solution and operational solution in prepare activation and start the content activation. As per below link we need to create 2 solutions and doing export and import. But I am not clear about these full project .

https://wiki.scn.sap.com/wiki/display/SM/Deployments

Any experience on huge projects migration and template project conversion. In SP05 prepare activation allows template project in selection.

Rg,Karthik

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Andreas Diebold
Oct 12, 2017 at 01:38 PM
0

Hi Karthik,

I hope this discussion

https://answers.sap.com/questions/304846/deployments-in-solman-72.html

answers you question in parts.

Regards
Andreas

Show 6 Share
10 |10000 characters needed characters left characters exceeded

Hi Andreas,

Thanks for reply. I am planning to use single solution for all my 147 projetcs, charm, BPMon, BPCA project. How to handle in single solution.

Normally after content activation, all the projects and solutions are migrated to business processes -> folders and Libraries . Can you please give some tips to handle in single solution for template and implementation projects. like branches or folder ?

Rg,

Karthik

0

Hi Karthik,

my answer got attached to the next post below.

Kind Regards

Andreas

0

Dear Andreas,

Sorry. I am not get it. which post you are referring.

Rg,

Karthik

0

This one:
Hi Karthik,

unfortunately I cannot give you another documentation or PDF than the ones linked in the other post. I agree it is confusing and difficult. And you are right we suggested that you should create one solution as a rule for your solution if you are no service provider. And this is still the rule the Operations Solution contains all the former separated implementation prjects. You can have multliple deployments in the same solution. The Deployment contains a node logical component mapping and an element mapping. Each element that was imported from the template knows its corresponding template element. So when the template is imported in a second version, the operation solution element is updated in the import branch. Then you can decide if you release these changes to development and finally to production or if you keep the local version. The new Release view in SP06 shows you all ne and changed elements, just as compare and adjust did in 7.1. This works all fine as soon as you have the deployment mappings. The problem is, that this is not covered by standard content activation but has to provided in a second step which includes some programming on customer side. Customers that do not want to update their migrated implementation projects with a new version of the original template have no problem.

Kind Regards
Andreas

0

Dear Andreas,

As per last update, I need to create 2 solutions , first(Deployment Authoring Solution) for Template project and second (Operational)for entire implementation projects.

So when ever the template solution update, will do the export\import and update in the operational solution.

Which solution is best to use for other functionalities like BPCA-TBOMs, ChaRM, BPMon projects migration in 7.2?

Rg,

Karthik

0

Dear Karthik,
you should always use the operational solution for use cases like BPCA, ChaRM and BPMON. The template solution is only to prepare new functionality you want to deploy to the operation solution.

Regards
Andreas

0
Ramesh Anthony Oct 12, 2017 at 04:10 PM
0

Andreas - I read both the threads. There are snippets of info on Deployments but no procedures on how they can be leveraged as global design vs. local rollouts. It's also confusing - Does multiple deployments occur within the same solution or different? SAP has also repeatedly said to not create more than 1 solution. Can you point us to a PDF or documentation that elaborates on Deployments?

Thanks for your help.

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Hi Karthik,

unfortunately I cannot give you another documentation or PDF than the ones linked in the other post. I agree it is confusing and difficult. And you are right we suggested that you should create one solution as a rule for your solution if you are no service provider. And this is still the rule the Operations Solution contains all the former separated implementation prjects. You can have multliple deployments in the same solution. The Deployment contains a node logical component mapping and an element mapping. Each element that was imported from the template knows its corresponding template element. So when the template is imported in a second version, the operation solution element is updated in the import branch. Then you can decide if you release these changes to development and finally to production or if you keep the local version. The new Release view in SP06 shows you all ne and changed elements, just as compare and adjust did in 7.1. This works all fine as soon as you have the deployment mappings. The problem is, that this is not covered by standard content activation but has to provided in a second step which includes some programming on customer side. Customers that do not want to update their migrated implementation projects with a new version of the original template have no problem.

Kind Regards
Andreas

0