CHARM: SDHF_04 auths failure

Question

I am testing ChaRM and an incorrect authorisations failure has occurred.
The scenario is as follows;
Using the Developer user, have successfully created Normal Corrections
and processed them.
Now trying to create Emergency Corrections the process fails at the
action "Set to In Development", the error produced is "An action was
terminated due to an exceptional siutation"
Having then run SU53 an authorisation failure is detected.
The failure is on Auth Obj B_USERSTAT, for BERSL SDHF_04 - this is
completely incorrect - this BERSL would allow the developer to approve
for production, the current action is to simply set to in development.
The configuration is clear that the Authorisation required for this
action is BERSL SDHF_01 which the user has got through the
SOCM_DEVELOPER role.
Based on the documentation
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/45/51fbdbd4941803e10000000a1553f7/frameset.htm
We have given the developer the correct roles, also based on our
experience with the normal correction the role is correct. - I realise that Emergency & normal corrections are processed differently, however my statement is based on the configuration & the required auths in the Developer role.
The only user who should have the access being requested is the
production manager - this role has the requested access as detailed in
the documentation.
Why is the action of "Set to in development" for an emergency correction
require SDHF_04? Or in fact anything other than SDHF_01 as detailed in
the configuration.
I would appreciate any pointers on where I should look to see why this auth check is happening.
Thanks in advance
Marina

Answer 1

Hi
In the standard behavior, after a Change Manager creates an urgnt correction by authorizing a change request,
the MC links will be added to the document flow area.
Check this document flowin your urg. correction. If the cycle assignment is still empty,  that means their change manager has not fully authorized this urg correction
As a result, since the link to MC is still missing,  it is required to assign the urg correction to a cycle when you shift its
phase to "In developmnt". That's the reason why you receive such kind of an error.
And it explains why change manager's role is needed here.
If this role is also done according to the documentation, there could be an issue in the actions executed.
Sometimes some inconsistencies in the customizing are the reason why PPF actions are not automatically executed.
if this is your case reactivation of BCSet SOLMAN40_CHARM_BASICFUNC_001 may be helpful.
Kind regards,
Marta