Question:
Hi there,
I am having a problem with one particular role I am trying to SCC1 from our development-config client to our development - test client. I made a change to a role, regenerated the authorisations and had everything look good. Added it into a transport request and used SCC1 to copy over.
In the copied over version, the profile is not generated, and the name/description of the profile are blank. When I go into the authorisation details, all the values are populated correctly just like the config client. I've tried the following:
1 - releasing the transport and recopying (no result)
2 - regenerating the test client profile which worked fine but when I recopied over, it turned back to ungenerated.
3 - making a slight change to the role, saving, changing back, regenerating and inserting into a new transport request, then copying: again, back to ungenerated.
I've looked into the transport request contents and it appears to be fine - I can see role and profile name/values inserted fine, and when I compare it with other transport requests that have worked, again it looks similar/the same (obviously not identical as they're for different roles - but all table entries are there and the same).
I've also thought about just transporting to Acceptance systems to see what happens but I'd rather not just yet.
I could just be going a bit mental here - but does anyone have any bright ideas? Anything at all? I'm going to talk to BASIS next but I was wondering if there was anything obvious that I should be checking that I haven't - you never know!
Thanks in advance
Di
Answer:
Working as designed,
Use a real transport in Se10 and release it and inport it with STMS.
The transport for the Roles do not load all the data until you release the transport nor does it house all the keyed records the SCC1 needs. SAP uses a xxxx ( I forgot the word they use, but it is basically a marker that tells the released transport to go get a host of data not listed in the key of an unreleased transport.).