on 07-15-2010 8:55 AM
Hello all,
we want to close a maintenance project A and create a new maintenance project B. We have a lot of change request they aren`t finish, so we want to move them to the new maintenance project.
The following steps we have done:
1. Doing all phases of the maintenance cycle of project A.
2. Close maintenance cycle project A.
3. Create a new project B.
4. create a new maintenance cycle for project B.
Now, we have the problem, that all change request from project A and maintenance cycle A didn't move to the new project B and cycle B.
If you create a new maintenance cycle in project A, all open change requests move to the new cycle. But we want to move them to a new project and a new cycle.
Have anybody a suggestion how to do this?
Kind Regards
Marc
Hello Marc,
there are a couple of methods in a class that might help you if you DO have to do it... but SAP will not support you in case you have any problem.
you can take a look to methods of class CL_HF_HELPER.
Methods :
SET_BO_LINK_TO_CHNG_DOC is used to set link between SDMJ and SDMN
SET_BO_TASKLIST_OF_CHNG_DOC is used to set link between SDMJ and tasklist
as there are those methods, to create links SAP, provides some others that are supposed to break them (If i remember well they are not activated or finished but you can still have a look !!)
Those methods are
DELETE_BO_LINK_OF_CHNG_DOC
DELETE_BO_TASKLIST_OF_CHNG_DOC
RECREATE_BO_LINK_OF_CHNG_DOC
RECREATE_BO_TLIST_OF_CHNG_DOC
Hope this helps
One more time... be carefull with those methids... I think it s quite dangerous to handle those kind of things without SAP's support.
Also, one mote thing... since many many customers have asked for this functionality; SAP is trying to develop the whole thing (with adjustments of Checks functionalites of ChaRM) for the next releases. Maybe that will be part of the next release
Regards
Khalil
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Marc,
sorry but news are nt good. This functionality does not exists; because it would be too dangerous doing that so SAP did nt allow it; simply because all the consistency checks that SAP has implemented are based on the CTS projects created from Solman Projects. By letting people change CTS assignment... checks based on the CTS won't be OK anymore (for example the CTS dependency Check) !!
So you do not have any other option than recreating a cycle for the same project or finishing those transport requests life with classic STMS functionalities
Regards
Khalil
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
10 | |
9 | |
8 | |
6 | |
6 | |
6 | |
5 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.