cancel
Showing results for 
Search instead for 
Did you mean: 

Charm - No automatic transport to test system in SDHF

Former Member
0 Kudos

Hi,

We are setting up the charm process in a new Solution Manager system (ehp1 for SAP NetWeaver 7.0). We have a standard three SAP system landscape. The normal correction is working ok, but we have a strange issue with the urgen-t correction (SDHF). Problem appears when the developer has finished his changes in dev, released his task and changes the status to "Pass Correction to Test". Then the import should be done to test system automatically, but this doesn't happen. The import has to be done manually.

Also the log on to test from Solution Manager is not possible.

We wonder if this could be due to the fact there is no quality assurance system visible in the task list for the urgen-t correction. Shouldn't it be there as it is in the normal correction?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Yes that is the reason. Odd that the QA system is being created for the normal correction. Check the logs in the task list and run an overall check on your project, post the results

Former Member
0 Kudos

Thanks for your answer SolManiac,

We have gone through Project settings and also all other I can think of. Everything looks like it is according to standard. I guess we are looking for the "trigger" that create the task list. Hopefully it will be possible to find the answer there. Do you know where that would be?

RajeevP
Advisor
Advisor
0 Kudos

Hi,

Please have a look at the SPROSAP Solution MAnagerScenario Specific SettingsChange Request MAagementExtended Configuration--Schedule Manager. There u check for the condition assigned for ur task. Ur task should be of type O. Please read the documentation provided there for more details..

Rajeev.

Former Member
0 Kudos

Hi Rajeev,

We have double checked also this setting, but it is SAP standard even here (Variant=SAP0).

Any other ideas?

Thanks!

/Christer

RajeevP
Advisor
Advisor
0 Kudos

Hi,

As per ur post, ur normal correction is working fine. But for the transaction type SDHF, 2 actions are not working fine. 1. Pass Correction to Test 2. Logon to System. You couldn't find any issues with the task definition. Please dont just skip the checking although u find it SAP standard?

How u activated ur ChaRM? Was this trhough BC sets?

I also faced a similiar issue with the action Login to the System. There wasn't any issue with the configuration. The issue got resovled by deleteing the action from the transaction type SDHF and recreating the same. This was suggested by SAP and I wonder what could be the logic behind this.

If ur issue is similiar, u can try this one. But do remember to take the screen shot of whatever u r deleting.

Regards,

Rajeev.

Former Member
0 Kudos

Hi Rajeev,

You wrote:

"I also faced a similiar issue with the action Login to the System. There wasn't any issue with the configuration. The issue got resovled by deleteing the action from the transaction type SDHF and recreating the same. This was suggested by SAP and I wonder what could be the logic behind this."

I would like to try this but I'm not sure I find the correct place in the IMG. Could you provide the path as well?

Thanks!

/Christer

RajeevP
Advisor
Advisor
0 Kudos

HI,

Ok. Please call tcode SPPFCADMSelect CRM_ORDERSelect Define Action Profile and Actions.Then select ur Action profile, say SDHF, and doubel click on Action Definition. Select ur action there and double click on it. Now take the screen shot of ur action as well as the Processing type of the action. Note down the parameter assocaited with that. For a safe side, take a copy of that action also. Then delete and recreate the same.

Rajeev.

Former Member
0 Kudos

Hi /Christer.

Just in case you have not resolved this issue yet, please try checking the authorisation of the developer in the satellite system. I remember having this issue last year when we had the UAT testing for the CHARM implemention. The import of normal correction using the maintenance cycle task list is ok because I'm using the IT Operator account which is defined with correct authorisations but I use a different account (developer account) to import SDHF using action "Pass Correction to Test", and this account does not have proper authorisation. I fix this by adding the auth code "S_RFCACL" in the developer's account in the satellite dev system/client (where transport request is created). Also, the developer should exist in the satellite dev system (client 000) with proper authorisation unless you are using a single account (i.e. TMSADM user) for importing to the Test system.

The auth code "S_RFCACL" will also fix your issue with action "Login to system".

I hope this helps.

Regards,

Tess

Former Member
0 Kudos

Hi Rajeev and Tess,

Thank you both for your answers and input on our problem. Unfortunately none of your suggestions has solved the problem. I have now sent the problem to SAP and will let you know when it has been solved.

/Christer

Former Member
0 Kudos

Hi Christer,

in your initial message, you said that no QA system is present in the tasklist of your UC. That seems odd to me... Can you provide details about what systems you can see in the tasklist of your UC and your TMS configuration ? I think you're right saying the problem could come from the lack of QA system in the tasklist.

Regards,

Stéphane.

Former Member
0 Kudos

Hi Stéphane (and others),

Thanks for the interest you are showing in our problem.

We have an ongoing discussion with SAP and we will also do som rework on the TMS. I will update this thread as soon as I have some more news or if I still require some input from you guy's.

Thanks!

/Christer

Former Member
0 Kudos

Hi,

The initial answer from SAP was to check and change the "System Role Assignment" in SOLAR_PROJECT_ADMIN (System Landscape / Systems tab). This might very well solve some problems but what really solved the problem for us was a reconfiguration of the transport landscape in STMS. The thing is that the u-rgent correction will take the shortest route from Dev to Prod. And we did not have any test system between the two previously. However this has been taken care of now and everything is working as it should.

Best regards,

Christer

Answers (0)