Some problems within CHaRM

[Former Member]

Hi!

We are implementing ChaRM and have the following problems. Perphaps some one of you can help us to solve one or other problems.

1) No normal corrections (SDMJ) are visible within the tcode "DSWP"

2) The Developer cannot set the urgent correction in Test, because of the transport task of transport request in DEV system is open. Should the Developer each time release manually the transport task in DEV system or does this function possible within task plan?

3) No systems are visible under /n/TMWFLOW/CMSCONF

It means it is not possible to set any system as mandatory

(We have currently one valid maintenance project for one system with 3 clients)

4) The import of transport reguest of the urgent correction from QAS into PRD system can be done without to be log in in PRD system, but also from QAS system. Therefor no authorization to PRD system will be requeired.

Thank you very much!

regards

Thom

[Former Member]

Hi Thom.

To give you a few hints:

1) Check customizing if you are really using SDMJ. Maybe old SDMI is still set up.

2) The task should be released by developer. The request will be released by change request action.

3)There are several things necessary to make the system appear in this transaction (/N/TMWFLOW/CMSCONF)

You need:

- a smi project

- a logical component assigned to that project which contains your systems

- at least one system within your logical component of type "developement system" (especially for tab: critical obejcts)

- the project needs to be released for change request management (tx: solar_project_admin, "activate change request management")

4) Not sure if I got you right.

can be done without to be log in in PRD system

How is it done? Via task plan?

but also from QAS system.Therefor no authorization to PRD system will be requeired

Via TMS import queue?

Hope this helps.

/cheers

[Former Member]

Hi Christian,

thank you very much for your response.

1) I have compered the this problem with other SAP Solution Manager. There in tcode "CRM_DNO_MONITOR" the normal corrections are under "SDMI" and there are visible under "DSWP".

How can I switch this assigment? (tcode, table, report, customizing...)

2) Will the task relised by developer via task plan in SOLMAN-ChaRM or manually in DEV-system?

3) All the prerequisites you mentioned are fulfilled, nevertheless we do not see there any systems/clients.

We have implemented 1 system with 3 clients.

4) Exactly, via task plan. We do not generate any Trusted RFC for productive system/client. It means when we execute the steps in task plan for productive systems ("Log in in PRD system", "Import transport") we get the log in screen from QAS system. When we go to QAS system it is possible to import the transport request into productive system without to log in into productive system.

Thank you very much!

regards

[Former Member]

Hi Thom.

1.) Check:

Note 935060 - Information about the transaction type - validated correctio

Note 1022823 - Normal correction (SDMJ) copy control

2.) We usually have the developer do this in DEV system.

3.) Hmm.. do you get any errors in tx: /TMWFLOW/CHARMCHK ?

4.) So you jump into QAS, go to TMS import queue and import requests manually? You can prevent this by assigning transport requests to projects, setting this assignment mandatory and setting project switches accordingly (no import allowed). This way you won't be able to import manually but using the task list.

/cheers

[Former Member]

Hello Christian,

thank you very much for your response.

Could you perhaps help to answer the following questions:

a) Are Trusted RFC and Trusted/Trusting relationship (SMT1, SMT2) must for usage of ChaRM. If Yes, in which clients and with wich users?

b) When we have -besides of course standard transport route- several own transport layers and routes how can we be sure which one does use ChaRM?

Thank you!

Thom

[Former Member]

Hi Thom,

a) I do not think it is a must but honestly I did not try without yet.

At least a trusted is needed for action "Logon to system" used within a change document so developers/testers do need to authenticate themselves in the target system.

b) ChaRM uses each system/clients' default transport layer.

Regards

[former_member137336]

Hello Thom,

Trusted RFCs are must for ChaRM to work and it should be established to all the systems and clients involved in the CHaRM maintenance project.

Regards

Farzan

[Former Member]

Hi!

Have you ever seen some official SAP document for this?

Thank you!