Skip to Content

     The System landscapes most of the time might involve virtual system/s.  ChaRM activation in SOLMAN 7.1 is quite easy for ABAP systems like ECC which involve Virtual target systems. But when Non-ABAP systems / Java Systems are created as Virtual systems in STMS then an error related to Communication system for the Virtual system is issued out during creating the task list in the Project set up.

Let me explain the problem statement in detail-

A virtual Non-ABAP system in defined in STMS. You define the Solution Manager system as the Communication system for the Virtual Non-ABAP System.

STMS-P42.PNG

STMS-P42-2.PNG

You add this virtual system to the Logical component and include the Logical component to the Project Landscape for which Change Request Management is being activated. After entering all other details when the Activate Change Request Management is being enabled an error is issued that the Virtual system does not have a communication system (Example Screen shot of the error shown below). This comes even after providing the communication system in STMS. It prevents the Create Task List.

Project Error.PNG

So what is missing and how to overcome this??

The Virtual systems when created for ABAP systems and  when Product systems are assigned to the Product and version, the SMSY settings for the system identifies it as Virtual system and marks it as such (Like the example shown below).

Virtual in SMSY.PNG

But the same does not happen in the case of the Virtual systems defined for NON-ABAP type in STMS. When the Project checks are done it fails to identify it as a Virtual system and looks for a communication system or RFC connections.

The Solution goes like this…

Include the ‘Application server ABAP’  product instance as RELEVANT in the Product system definition for the Virtual non-ABAP system.

SMSY-Virtual non-ABAP systems.PNG

By doing so the Virtual system will be identified as a ABAP type of system and also as a Virtual system (hence no RFC Connections are required) and the Project check does not fail. This is the Workaround. Neglect any other errors issued on ‘Client specific Transport control’. There are no Clients applicable for Non-ABAP systems and this check and the corresponding error message can be safely ignored.

P42-non-abap.PNG

Proceed further and Create a Task list. ‘Create task list’ would be successful.

Follow the instructions in the SAP Note 1687980 – Virtual transport system in SMSY 7.1 when the systems are available as real systems in the landscape.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply