SAP for Public Sector Discussions
Foster conversations about citizen engagement, resource optimization, and service delivery improvements in the public sector using SAP.
cancel
Showing results for 
Search instead for 
Did you mean: 

Make Message no. GRANTMGMT517 a hard error

Former Member
0 Kudos

Message no. GRANTMGMT517 (G/L account/cost element xxxxxxxxxx/ has not been set up for updating in grants)

is causing lots of problems. It is currently a warning message and this allows users to hit "enter" to bypass the warning but at the point of posting if fails (just as the system response says it will do).

If this message could be made a hard error and immediately stop users thus making it necessary to update GM settings (GM_UPD_SETTINGS) before continuing it would prevent lots of problems in payroll postings and workflow.

Is it possible to make it a hard error?

3 REPLIES 3

Lukas_Weigelt
Active Contributor
0 Kudos

What Programm/FM/Application is throwing this error? If it comes down to modification, you can alter this in my opinion. Search inside the code and change the hardcoded message type to E (so it'll be an error message); supposing it was W or S before..

Can you provide the Program name?

regards, Lukas

0 Kudos

It appears that the program is SAPMF05A.

0 Kudos

Couldn't make out your message in this program, probably because it's nested way too hard. I checked where the message is being used globally, I only found these two repository objects:

CL_GM_SERVICES->CHECK_GM_RELEVANT

IF sy-subrc <> 0.
    ex_is_relevant = space.
    IF sy-subrc EQ 3.
      MESSAGE ID 'GRANTMGMT' TYPE 'W' NUMBER '517'
             WITH im_account im_cost_element RAISING account_not_set_up.
    ELSEIF sy-subrc EQ 4.
      RAISE co_integration_missing.
    ENDIF.
    EXIT.
  ENDIF.

and GM_GET_UPDATE_DETAILS (function module)

IF sy-subrc = 0.
          e_value_type = x_gmfiupd-value_type.
          e_stats      = x_gmfiupd-stats.
          e_derive     = x_gmfiupd-derive.
        ELSE.
          MESSAGE w517 WITH i_hkont RAISING account_not_set_up.
        ENDIF.

So I'd advise you to set external breakpoints at these two coding points, reproduce your warning and see which one is being used. So bottom line, yes, it seems to be hard-coded and you might only have a chance modifying the standard code and replace the message Type W which is used at both points with E so the application terminates. Then again, since these are Methods and FMs, you won't know 100% what impact this will make on other programs/applications.

Cheers, Lukas