on 07-09-2009 10:24 AM
I don't know whether this is the right question in this forum but we are having one BSP application for which we have Logon data maintained in its SICF service.
When we transported the application (SICF service was included into the request), the logon data was not transported.
When we tried going to change mode and update the logon data it gave error "Changes to Repository or cross-client Customizing are not permitted".
Hence we tried to unlock the configuration through SCC4. Then when we tried in QA system it poped up for the request whcih we definietly don't want.
Is there any way we could avoid the same?
Thanks in advance.
regards
rajeev
We created the request in the target systems
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
the right way to transport logon info along with SICF service is to create an external alias for your BSP and maintain the logon info in the external alias.
other wise you have to open the production system for changes and change it , which may not be allowed.
Regards
Raja
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
could it be that you do not have the authorization to make changes in the system in SICF ?? I tried it in my test system and after asssigning it to a transport request, it works.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
82 | |
10 | |
10 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.