A) Training documentation for Solman
Below the useful links about the training :
Important : case of Urgent Change with ECC dev and impact with Monthly Release
Documentation about Charm 2.0 (technical dataflow)
+ link to template roll-out for the release of developments on production
below the template :
About CAB :
A-1) SolMan flow for Change BI
B) Request new access to Solman
Below the link to give the acces to Solman :
B-1) Request new access for new requester in Solman (new person not done as requester in Solman)
Below one example :
C) How to use Solman with our organisation and process and new way to work within
RFC project Requestor and Change manager could be the IS Reporting Coordinator of each stream or Techno if it is a general dev.
RFC maintenance to be defined.
Without BAR approval ? any time ?
Split of Transport request so need more Urgent Change to manage well the release between 2 environnements
D) Tips about Solman for BW
Comment 1 :
Dear BW developers, the usage of Downgrade protection before the release of your task to check the dependencies is desactivated on PS1, see below one example, to avoid any regression on production server.
If Solman detect a conflit, please inform the another BW developer about it to check with him the release on production or what he was done with the object.
If you take the choice to ignore, you can generate regression for another change document.
You need to check deeply your TR because we have more checkings with this new Solman.
Tips 1:
You need to create a new BW query on WBD, please move on the TR all information and assign the new objects on packages if not it will be no possible to move the TR on WBQ.
You can used the program below to check your TR about the dependancies :RSO_TLOGO_CHECK_REQUEST
Example : solution send by Q&P support team :
->
This is a BW specific error. Please run the report RSO_TLOGO_CHECK_REQUEST to calculate consistency check errors in BW.
Many dependencies are missing:
Once those dependencies are solved I guess the TMS will be allowed to transport the request.
After integration of all missing elements the release od TR on QAS (WBQ) are done well.
2) Check dependancies with a tcode