Understanding and using Logical Components for Managed System configuration

[Former Member]

Experts.....

I am embarking on a fresh installation of SolMan 7 EhP1 SPS25 and after a few bugs along the way, I am finally nearing the end of including the first Managed System. Somewhat related to {forum:id=10293771] I am hoping I can get some advice, but specifically with regards to Logical Components.

General question - I have a slide from SAP that shows a picture from Product->System->Instance->Logical System (client)->Logical Component. I am confused because it shows that Client 100 of a given ABAP system could be assigned to Logical Component A, whereas Client 200 of the same system could be assigned to Logical Component B. This seems wrong to me?

I am at the last step of the managed systems configuration wizard : "create logical components" and only want to ensure that I set things up to hopefully ensure that later usages (Maintenance Optimizer, etc) will handle things correctly!!!

- Our SAP landscape is not very complex

1. only ERP and EP (Dev/Test/Prod).

2. We are utilizing HR Self Service (XSS).

3. The ERP ABAP systems are on Netweaver 7.01.

4. EhP4 has been installed, however we only activated the HCM business functions. Therefore SAP_HR is on 604 whereas SAP_APPL is on 600. I think this might be driving some of the confusion in SMSY

For the DEV ABAP system I am trying to configure:

1. The system is showing up in two products : "SAP ERP" and "SAP ERP Enhancement Package" with the header data for both showing "EHP4 FOR SAP ERP 6.0 / NW7.01" and "SAP ERP 6.0"

2. Under "SAP ERP" the "product instance selection" shows only "SAP NW - Adobe Docu. Service" and "SAP ECC Server" as relevant

3. Under ""SAP ERP Enhancement Package" the "product instance selection" shows only "Human Capital Mgmt" as relevant by default. I manually flagged the development portal system as "relevant" for "SAP XSS (Self Services)"

4. The RCA DBA Cockpit system is complaining "No data available for extractor activation. Please check product mapping and Software Components in SMSY"

5. In the Managed System wizard, there is no logical component for any of the "EHP4 FOR SAP ERP 6.0 / NW7.01" selections

From what I can tell, I think this is correct:

1. Create a Z_EHP4 logical component and assign the DEV/QAS/PRD systems to them

2. Also assign the DEV/QAS/PRD to the existing SAP logical component "SAP ERP ECC SERVER"???

3. For the Solutions, my plan is to create

a. Non-Production ERP : with the dev/test erp/ep systems, but test system as the leading system

b. Production ERP with the prod erp/ep systems only

Thanks for any advice/guidance to help me avoid future problems!!

Edited by: Eric Poellinger on Jun 15, 2011 6:32 PM

[Former Member · Accepted solution]

General question - I have a slide from SAP that shows a picture from Product->System->Instance->Logical System (client)->Logical Component. I am confused because it shows that Client 100 of a given ABAP system could be assigned to Logical Component A, whereas Client 200 of the same system could be assigned to Logical Component B. This seems wrong to me?

Client 100 could be assigned to any number of logical components, client 200 could be assigned to those same ones or none of them. A logical component is just a grouping of systems used to accomplish some task in SolMan.

For example with ChaRM you could have 2 logical components.

ZCHARM_DEV development (100) -> QA (200) -> prod (300)

ZCHARM_SEC security (900) -> QA (200) -> prod(300)

One is used to show the path for moving development changes to prod, the other for security changes. 200 belongs to both, but 100 only to one.

Set them up in whatever way meets you needs. It looks like for you, you could just use the default one and assign your clients to the various system roles. Not all functionality in SolMan uses the logical components though.

[Former Member · Accepted solution]

I think my confusion is likely stemming from the Product / Product Instance / Relevant pieces and the inter-play with logical components.

It is disheartening that SAP solman requires such care & feeding to get the systems (from SAP!