CHARM: how to handle various normal correction at the same time?

[Former Member]

Dear all,

I have a concern with ChaRM. In our SAP ERP system we have a lot of "normal corrections" weekly, for FI, HR, MM, etc. With this in mind, what is the way ChaRM manages it? I mean, we would have only 1 maintenance project with 1 maintenance cycle, that cycle can be in only 1 phase at a time, so if we for example have a FI normal correction in test phase, other HR normal correction in development phase and other MM ready for production, what would be the phase of the maintenance cycle?? how it can manage concurrent corrections to the system??? :'(

Hope you can help because Im really lost with this!!

Thank you a lot!

Federico.

[prakhar_saxena · Accepted solution]

Hi

if you have changes going daily then why you create NC

create UC and move it without any restriction of phase changes

Regards

Prakhar

[Former Member · Accepted solution]

Thank you very much Prakhar!

We will have to use UC then, but still have a doubt about what is the real purpouse of NC?? Are this kind of documents being really used in maintenance activities?? Normal corrections for HR, FI, MM, etc must all be sinchronized so that all phases goes at the same time?

[Former Member · Accepted solution]

Hi Federico.

Are this kind of documents being really used in maintenance activities?? Normal corrections for HR, FI, MM, etc must all be sinchronized so that all phases goes at the same time?

Yes the Changes have to be normally aligned and moved at the same time, if you have only 1 maintenance cycle.

But, I would still encourage you to use NC for it has various options like to create the transport of copies, so that you can test the functionality with not releasing the request.etc and mainly aids on Large movement of Changes.

But i fear its not possible on UC for its mainly meant for Hotfixes or Immediate Changes, where you have no control on transport creation.

Regards

[prakhar_saxena · Accepted solution]

Federico,

What happens in a bigger project where you have multiple problem .....................................then you can use NC

because it gives an option to choose the satellite system where transport request is to be created

but UC will create transport request directly based upon the ibase it wont check if there are other system attach to the same maintenance cycle or multiple logical systems in the project etc.

So if you are makin small changes system wise no issues you can very well use UC without any problems.eg. Mention Ibase for ECC and TR will be creatd there similarly if u mention for BI etc TR will be created there and then go ahead with rest .

but for bigger scenario.. whch i have mentioned you can go for NC

hope all doubs clarfied

Regards

Prakhar

[Former Member · Accepted solution]

Thank you guys very much specially you Prakhar!

with your help im clearing up my concerns, still have some doubts but they are based on the fact I never worked in a big project so I cant understand pretty well the benefits of NC

Best regards and thank you very much again!