on 04-04-2009 3:43 PM
We configured CHARM in our system ... but we are now faceing an issuse regaring to login to the QUA server .
the It_tester have to log in to the QUA server to test the Correction , but it is not working ......
Edited by: vish menon on Apr 5, 2009 1:14 PM
Hello vish menon,
could you provide more information when you are not able to logon to satellite systems? I guest that, trusted RFC is not correctly setup in system landscape defination (SMSY). Could you check it first?
Best regards,
Jett
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello vish,
I'm not quite understand your quesiton. Based on my experience, these kinds of problems should be related to transport request. Not the "log on to the qua server"... Could you describe your steps more detailedly for reproduce the error?
To eliminate the error, my suggestion is to check the import history of the transport request, there should be some error.
Free to reply when you got further information.
Thanks, Jett
OK --
We have configured CHARM SYS Management & it was working correctly .....
But we got some database error IN QUA & We rectified it .But after that ....we are not able to log in QUA ...
The scenario in CHARM is:
Requestor put a request to change manager ,,
change manager pass it to the developer ..
developer logon to the development sys ..& do the necessary change ...Then log out from there ....
Change manager log on to SOLMAN & release the request to QUA . ,,,,,,
Then the TESTER have to log on to QUA to check the change
BUT HERE WE ARE AUTOMATICALLY LOG ON TO Dev SYSTEM INSTEAD OF LOG ON TO qua ,
Vish
let me make the scenario descripton; once your developer has developed his change and put that to a transport your CR approver puts his approval for unit testing in QA System. Than your Developer is reasling it in DEV and than he has to login manually to QA and do the transport and you want this to be automated?
Check SAP Note #881553 for ChaRM related Roles that you need for this activity
Nesimi
Hi vish menon,
This is because incorrect status of correction or phase of the maintenance cycle.
Normal correction status should be "Development Completed" or the maintenance cycle shoule be in "Test" phase.
This is how the action "Log on System"(for QAS) works:
Maintenance Cycle - "Development With Release" Phase
1. Create transport request
2. Now, if you execute action "Log on System" then it will log into DEV system.
3. Then Change the code and release the task
4. Test Transport.(Do not use Release transport request).
This action will create a transport copy and releases as well imports the changes to QAS by a
scheduled backround job.
5. Now, Developer logs into QAS and does a unit test.(this step is manual, not by "Log on System").
6. If the unit test is OK, then developer executes "Complete procedure(Development Completed)".
7. Now, if tester executes action "Log on System", now it will log into QAS system.
The changes will be available in QAS and he can test the imported changes.
8. Confirm successful test.
9. Change manager or IT operator has to change the phase of maintenance cycle to "Test".
(OR)
Maintenance Cycle - "Test" Phase
Steps 1, 2 and 3 are same.
4. Release transport request.(Do not use Test Transport)
5. Complete procedure(Development Completed).
6. Then IT operator import the changes into QAS.
Steps 7, 8 and 9 are same.
Regards,
Sanjai
VIsh
you might want to check the TMS RFC and the trusted RFC between SolMan and your satellite System
Nesimi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
95 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.