CHaRM : unable to create Task List

[Former Member]

Hi All,

we are trying to configure Charm in our Solman 7.0 sp16.

when i create a project and and click on "Create Task List" under SystemLandscapte>>ChangeRequests Tab

error "The Project is not released. Hence cycle cannot be released.

Now when i click on the check button. the following errors are displayed

Check Logical Components

No Consolidation System found for XXX-XXX(SM2-200) (Project Charm_Test)

+No Tract for Project Charm_test with log. system SM2/200

Check Consistency of project CHARM_TEST

+ CTS Projects in production systems for project CHARM_TEST+

can anyone help me out here.

Thanks!

Regards,

Pradeep L

[Former Member · Accepted solution]

Hi Pradeep,

This issue is because of Solution Manger TMS is not configured properly.

Use this blog for STMS configuration: /people/dolores.correa/blog/2008/07/26/first-steps-to-work-with-change-request-management-scenario

OR

Better use SPRO to configure STMS, Just follow SPRO step by step process.

SPRO->SAP Solution Manager->Configuration->Scenario-Specific Settings->Change Management

->Change Request Management->Standard Configuration->Transport Mnaagement System(TMS)

1. Do you try to activate ChaRM for any satellite system landscape(DEV->QAS->PRD?

OR

2. Do you try to test ChaRM in Solution Manager itself(SM100(DEV)->SM200(QAS)->SM300(PRD)?

If your test belongs to point 2, then follow the blog that i mentioned above. It gives a step by step details.

Note:

1. For anycase, DEV to QAS should be consolidation route and QAS to PRD should be delivery route.

2. SM TMS should have SAP transport layer as well as atleast one customized transport layer.

3. ChaRM supports only client specific transport management system.

Let me know if you need more help on this.

Regards,

Sanjai

[Former Member · Accepted solution]

Hi Sanjai,

we are trying the second scenario i.e

Dev(SM2/200)>Qua(SM2/300)>Prd(SM2/400)

i did follow the steps provided in the blog to configure this..

then i faced the issues mentioned above.

Regards,

Pradeeep L

[Former Member · Accepted solution]

Hi Pradeep,

1. Can you double check that you have done all SPRO steps for TMS. (RFC generation for client 000)

Note: You have to Configure SM TMS configuration at Client 000.

Also did you generate RFC connections for client 200 and 300. i.e., Step 3

2. Does your SM TMS look same as mentioned in the blog? i.e., Step 2

Let me know these details.

Regards,

Sanjai

[Former Member · Accepted solution]

Hi Sanjai,

Thanks a Lot for your reply.

I have done all the SM TMS configuration..

but am really not sure if i have done it on Client 000... i will check that and update in the same thread..

one question: i have copied client 000 to 200, 300 and 400.

why should TMS be configured on client 000??

Regards,

Pradeep L

[Former Member · Accepted solution]

Hi Pradeep,

Client copy will be done from 000 only.

However, TMS will be controlled from client 000 for any R3 system.

The user who imports the transports should have account in client 000 as well as proper authorization.

Check your SM TMS configuration in client 000. It should be same as mentioned in the blog.

Regards,

Sanjai

[Former Member · Accepted solution]

Thanks Sanjai. Issue Solved!