Skip to Content
0

How to mass replace logical component group in solution documentation

Jan 19, 2017 at 02:41 PM

721

avatar image

Hi there!

I need to replace the logcial component group in a few hundred executables in solution documentation of Solution Manager 7.2 but cannot find any function to do so.

Any idea?

Cheers!

10 |10000 characters needed characters left characters exceeded

I am also looking for answer on this topic

0

In our situation we have initially created LCG with a specific naming convention but we want to replace that with a new LCG with a naming convention that is more understandable for our end users to select when creating solution documentation.

Both LCG contain the same technical systems.

0
* Please Login or Register to Answer, Follow or Comment.

4 Answers

Andreas Diebold
Feb 02, 2017 at 10:08 AM
0

Hi Ulrich,

there is no way to do this in 7.20. There should be no need for replacing logical components. Can you give me some background?

Kind Regards

Andeas

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

Hi Andreas

I am working on a scenario where landscapes are changed (after Content Activation) due to the client deciding to split the business into regions, each responsible for running 'their own' SAP environment, meaning we have to 'unscramble' the SAP omelette. The SAP DMLT team will handle the ERP systems split, but managing Solution Manager throughout this process is not well documented.

One of the issues we're facing (having chosen to stay with a single 'Solution' for now), is that all the processes in one part of the business are pointing to the wrong Logical Component Group. (We had to create a separate LCG, else the change Control Landscape in ChaRM couldn't be isolated). We chose to stay with one 'Solution', because we needed to use the Processes (the old Project Blueprint structure) in Test Management.

I am working on a document that describes the "Practical Implications of the 'Solution Design' is version 7.2", but it's a work in progress and ready for general distribution yet. I would love to hear you views on some of these aspects.

Regards, Rob

0

Hi Rob,
for this setup you can create a site for each business region in SOLADM. Than you can use the same logical component group for each site but assign site specific systems to it.
Kind Regards
Andreas

0

Hi Andreas
We tried that, but it turns out that we then couldn't use Test Management, as Test Suite doesn't support testing by site (in SP05 anyway) yet.

I haven't yet found the one solution that works for Test Management, ChaRM and SolDoc - so far I have found a solution that works for each component in isolation.
Kind regards, Rob

0

Hi Rob,

as of SP07 also Test Management fully supports sites. You can create test plans per site.

Kind Regards
Andreas

0
Ulrich Köller Mar 01, 2017 at 04:39 PM
0

Hi there,

it is finally possible to mass change the LCG.

Just go to list view in SOLDOC mark the process steps you want to change.

Switch to edit mode and change the LCG.

Cheers!

Share
10 |10000 characters needed characters left characters exceeded
Ulrich Köller Mar 01, 2017 at 04:39 PM
0

Hi there,

it is finally possible to mass change the LCG.

Just go to list view in SOLDOC mark the process steps you want to change.

Switch to edit mode and change the LCG.

Cheers!

Share
10 |10000 characters needed characters left characters exceeded
Andreas Diebold
Mar 02, 2017 at 01:01 PM
0

It is possible when the logical component is not part of a unique key. This is the case with stepsm but not with most executables. You cannot change the LCG of a transaction.

What K. Lai is looking for is more a renaming of LCGs. This would be possbile if testing wouldn't be involved. The problem with testing is, that in a Test Data Container the LCG name is stored instead of the LCG GUID like everywhere else. LCGs have a GUID as internal ID just as solutions and branches to be able to rename them. A conversion exit displays the name at the UI but on the database there is a GUID. However Test Data Containers store the name instead of the GUID. So it is not possible to rename an LCG without getting inconsistent Test Data Containers. Therfore we had to remove the renaming functionality from SOLDOC UI.

Share
10 |10000 characters needed characters left characters exceeded