Coexistance of CHARM & QA?

[Former Member]

Hi all,

I want to activate CHARM, but we have not the common 3-system-landscape

Dev > Q > Prod). We use the QA-procedure, and thus have a kind of 4-

system-landscape:

Dev > Q > QA > Prod

...where QA is only a virtual system with an own transport buffer, where

basis team authorizes the changes manually to production. As it is a

productively used system landscape, we can not simply disable QA and

replace it by CHARM.

I need to activate both in parallel before QA can be disabled later.

<a href="http://img86.imageshack.us/my.php?image=systemlandscapelt3.jpg">http://img86.imageshack.us/my.php?image=systemlandscapelt3.jpg</a>

The normal STMS transport routes are configured and work fine.

But when I try to enable CHARM for this transport domain, the log

complains that there is "No export system for P01-001"! It simply

doesn't recognize the virtual QA-system as a system, probably because in

SMSY no system number can be read (as it is virtual).

I already tried to give the QA-system the "Production" role (via system

role assignment), but as it has no system number this is refused.

Is it basically possible to combine these two "approval procedures" (QA

& CHARM)?

And how can CHARM be enabled with the virtual QA system in the transport

route?

Many thanks for your help!

Christoph Schuhwerk

[Former Member]

maybe this note will help??? https://service.sap.com/sap/support/notes/1056026

[Former Member]

The following answer came from the SAP OSS support:

<i>basically, also a 4-system-landscape is possible within the CHARM

scenario and also the use of virtual systems is supported.

There are some prerequisites, which must be fulfilled:

All virtual systems to be used, must be added also to the according

logical component in SMSY. For the data in SMSY getting updated also

for these systems, please use the button "read system data remote".

A system role has a role type, this role type must fit to the definition

in TMS.

Furthermore single import strategy must be set up in TMS (also the

parameter CTC must have the value 1 assigned) and a client specific

standard transport layer must be defined.

Concerning virtual systems please check also attached notes no.

1004569 "Virtual systems in Change Request Management" and

1007217 "SMSY(SLD): Do not read TMS systems"!</i>