cancel
Showing results for 
Search instead for 
Did you mean: 

SAP GRC10 - Error while submitting Access Request

Former Member

Hello All,

<<Removed>>

While submitting the request ...getting below mentioned error on the page

Error while processing your query

What has happened?

The URL call http://<<removed>>/sap/bc/webdynpro/SAP/GRAC_GAF_ACC_REQ_WITH_REQ_REF was terminated because of an error.

Note

The following error text was processed in system GD1 : Conversion of type h to type N not supported.

The error occurred on the application server blrkec220748d_GD1_00 and in the work process 1 .

The termination type was: RABAX_STATE

The ABAP call stack was:

Method: GET_DUE_DATE of program CL_GRAC_ACCESS_REQUEST_UTIL===CP

Method: GET_DUE_DATE of program CL_GRAC_MODEL_ACCESS_REQUEST==CP

Method: IF_GRFN_API_MODEL~SAVE of program CL_GRAC_MODEL_ACCESS_REQUEST==CP

Method: SAVE of program CL_GRFN_API_SESSION===========CP

Method: CREATE of program /1BCWDY/Z3TZZFT9CG8486P2AANU==CP

Method: IF_COMPONENTCONTROLLER~CREATE of program /1BCWDY/Z3TZZFT9CG8486P2AANU==CP

Method: PROCESS_EVENT of program /1BCWDY/Z3TZZFT9CG8486P2AANU==CP

Method: IWCI_IF_FPM_UI_BUILDING_BLOCK~PROCESS_EVENT of program /1BCWDY/Z3TZZFT9CG8486P2AANU==CP

Method: CALL_UIBB_PROCESS_EVENT of program CL_FPM========================CP

Method: PROCESS_EVENT of program CL_FPM========================CP

What can I do?

If the termination type is RABAX_STATE, you will find more information on the cause of termination in system GD1 in transaction ST22.

If the termination type is ABORT_MESSAGE_STATE, you will find more information on the cause of termination on the application server blrkec220748d_GD1_00 in transaction SM21.

If the termination type is ERROR_MESSAGE_STATE, you cansearch for further information in the trace file for the work process 1 in transaction ST11 on the application server. <<Removed>>

. You may also need to analyze the trace files of other work processes.

If you do not yet have a user ID, contact your system adminmistrator.

Error Code: ICF-IE-http -c: 400 -u: 163554 -l: E -s: GD1 -i: blrkec220748d_GD1_00 -w: 1 -d: 20111005 -t: 195025 -v: RABAX_STATE -e: OBJECTS_MOVE_NOT_SUPPORTED -X: 1078D28404571EE0BBEBA3BBD9492C36_1078D28404571EE0BBEBA40E1A426C36_1 -x: 1D5DEFE0CADEF14FAC361078D2840457

HTTP 500 - Internal Server Error

Your SAP Internet Communication Framework Team

============================================================

Please find below error Log from SLG1

Config Error,Function Module is not maintained for Plug-in

Thanks,

Jagat

Edited by: Matt on Jan 25, 2012 3:24 PM

Accepted Solutions (1)

Accepted Solutions (1)

Former Member

Appreciate if some help or guide me on this issue.

Thanks in Advance,

Jagat

Former Member
0 Kudos

Hi Jagat,

Have you defined BRF+ rule for calculating Due date ?

From the error it looks like that the BRF rule is not correct and is returning wrong value . Can you try removing BRF rule for due date from IMG and try again ?

Best Regards,

Aman

Former Member
0 Kudos

Hello Aman,

Thanks for the reply.

In BRF i have mentioned request type and employee type in condition table ....I have not mentioned calculating Due date etc.

Can you please let me know in IMG from where we can remove the BRF rule.

Thanks,

Jagat

Edited by: JagatBir Singh on Oct 7, 2011 10:01 AM

Former Member
0 Kudos

Hello Aman,

Please find Below Dump Details downloaded from ST22

Category ABAP Programming Error

Runtime Errors OBJECTS_MOVE_NOT_SUPPORTED

ABAP Program CL_GRAC_ACCESS_REQUEST_UTIL===CP

Application Component GRC-AC

Date and Time 07.10.2011 10:47:56

Short text

Conversion of type "h" to type "N" not supported.

What happened?

Error in the ABAP Application Program

The current ABAP program "CL_GRAC_ACCESS_REQUEST_UTIL===CP" had to be

terminated because it has

come across a statement that unfortunately cannot be executed.

Error analysis

You attempted to move one data object to another.

This is not possible here because the conversion of a data object

of type "h" to type "N" is not supported.

Trigger Location of Runtime Error

Program CL_GRAC_ACCESS_REQUEST_UTIL===CP

Include CL_GRAC_ACCESS_REQUEST_UTIL===CM018

Row 59

Module type (METHOD)

Module Name GET_DUE_DATE

Source Code Extract

Line SourceCde

29

30 *-get function id from application & process id

31 CALL METHOD cl_grac_access_request_util=>get_appl_mapping_data

32 EXPORTING

33 iv_application_id = lv_application_id

34 iv_process_type = iv_process_id

35 IMPORTING

36 et_application_data = lt_application_data.

37

38 *only 1 record would exist in appl data table for appl id & process id

39 READ TABLE lt_application_data INTO ls_application_data

40 INDEX 1.

41 lv_fdt_uuid = ls_application_data-functionid.

42 *--

43 IF it_brftab IS NOT INITIAL

44 AND lv_fdt_uuid IS NOT INITIAL.

45

46 *-execute brf+ rule

47 TRY.

48 CALL METHOD cl_grfn_ac_brfp=>execute_brf_rule

49 EXPORTING

50 iv_func_uuid = lv_fdt_uuid

51 it_data = it_brftab

52 IMPORTING

53 et_data = lr_result.

54 CATCH cx_grfn_exception .

55 ENDTRY.

56

57 IF lr_result IS BOUND.

58 ASSIGN lr_result->* TO <lr_result>.

>>>>> lv_sla_id = <lr_result>.

60 ENDIF.

61

62 READ TABLE lt_sla INTO ls_sla

63 WITH KEY sla_id = lv_sla_id.

64 IF sy-subrc EQ 0.

65 ev_sla_id = ls_sla-sla_id. "sla id

66

67 *calculate due date

68 CALL FUNCTION 'END_TIME_DETERMINE'

69 EXPORTING

70 duration = ls_sla-sla_days

71 unit = '10'

72 IMPORTING

73 end_date = ev_due_date " due date

74 CHANGING

75 start_date = sy-datum

76 start_time = sy-uzeit

77 EXCEPTIONS

78 factory_calendar_not_found = 1

Active Calls/Events

No. Ty. Program Include Line

Name

26 METHOD CL_GRAC_ACCESS_REQUEST_UTIL===CP CL_GRAC_ACCESS_REQUEST_UTIL===CM018 59

CL_GRAC_ACCESS_REQUEST_UTIL=>GET_DUE_DATE

25 METHOD CL_GRAC_MODEL_ACCESS_REQUEST==CP CL_GRAC_MODEL_ACCESS_REQUEST==CM00Y 47

CL_GRAC_MODEL_ACCESS_REQUEST=>GET_DUE_DATE

24 METHOD CL_GRAC_MODEL_ACCESS_REQUEST==CP CL_GRAC_MODEL_ACCESS_REQUEST==CM004 420

CL_GRAC_MODEL_ACCESS_REQUEST=>IF_GRFN_API_MODEL~SAVE

23 METHOD CL_GRFN_API_SESSION===========CP CL_GRFN_API_SESSION===========CM004 11

CL_GRFN_API_SESSION=>SAVE

22 METHOD /1BCWDY/Z3TZZFT9CG8486P2AANU==CP /1BCWDY/B_Z3TZZFT9CG8486P2AAU5 3404

CL_COMPONENTCONTROLLER_CTR=>CREATE

Web Dynpro Component GRAC_UIBB_ACCESS_REQUEST

Controller COMPONENTCONTROLa

21 METHOD /1BCWDY/Z3TZZFT9CG8486P2AANU==CP /1BCWDY/B_Z3TZZFT9CG8486P2AAU5 159

CLF_COMPONENTCONTROLLER_CTR=>IF_COMPONENTCONTROLLER~CREATE

Web Dynpro Component GRAC_UIBB_ACCESS_REQUEST

Controller COMPONENTCONTROLLER

20 METHOD /1BCWDY/Z3TZZFT9CG8486P2AANU==CP /1BCWDY/B_Z3TZZFT9CG8486P2AAU5 7374

CL_COMPONENTCONTROLLER_CTR=>PROCESS_EVENT

Web Dynpro Component GRAC_UIBB_ACCESS_REQUEST

Controller COMPONENTCONTROLLER

19 METHOD /1BCWDY/Z3TZZFT9CG8486P2AANU==CP /1BCWDY/B_Z3TZZFT9CG8486P2AAU5 534

CLF_COMPONENTCONTROLLER_CTR=>IWCI_IF_FPM_UI_BUILDING_BLOCK~PROCESS_EVENT

Web Dynpro Component GRAC_UIBB_ACCESS_REQUEST

Controller COMPONENTCONTROLLER

18 METHOD CL_FPM========================CP CL_FPM========================CM00G 46

CL_FPM=>CALL_UIBB_PROCESS_EVENT

17 METHOD CL_FPM========================CP CL_FPM========================CM005 46

CL_FPM=>PROCESS_EVENT

16 METHOD CL_FPM========================CP CL_FPM========================CM00C 34

CL_FPM=>RUN_EVENT_LOOP

15 METHOD CL_FPM========================CP CL_FPM========================CM00O 8

CL_FPM=>RAISE_EVENTS

14 METHOD /1BCWDY/Z3TZZFT9CG847SKLEJYU==CP /1BCWDY/B_Z3TZZFT9CG847SKLEK56 2997

CL_CNR_VIEW_CTR=>ONACTIONBUTTON_PRESSED

Web Dynpro Component FPM_GAF_COMPONENT

Controller CNR_VIEW

13 METHOD /1BCWDY/Z3TZZFT9CG847SKLEJYU==CP /1BCWDY/B_Z3TZZFT9CG847SKLEK56 382

CLF_CNR_VIEW_CTR=>IF_WDR_VIEW_DELEGATE~WD_INVOKE_EVENT_HANDLER

Web Dynpro Component FPM_GAF_COMPONENT

Controller CNR_VIEW

12 METHOD CL_WDR_DELEGATING_VIEW========CP CL_WDR_DELEGATING_VIEW========CM006 6

CL_WDR_DELEGATING_VIEW=>INVOKE_EVENTHANDLER

11 METHOD CL_WDR_ACTION=================CP CL_WDR_ACTION=================CM00A 38

CL_WDR_ACTION=>IF_WDR_ACTION~FIRE

10 METHOD CL_WDR_WINDOW_PHASE_MODEL=====CP CL_WDR_WINDOW_PHASE_MODEL=====CM00U 95

CL_WDR_WINDOW_PHASE_MODEL=>DO_HANDLE_ACTION_EVENTS

9 METHOD CL_WDR_WINDOW_PHASE_MODEL=====CP CL_WDR_WINDOW_PHASE_MODEL=====CM002 82

CL_WDR_WINDOW_PHASE_MODEL=>PROCESS_REQUEST

8 METHOD CL_WDR_WINDOW=================CP CL_WDR_WINDOW=================CM00V 12

CL_WDR_WINDOW=>PROCESS_REQUEST

7 METHOD CL_WDR_MAIN_TASK==============CP CL_WDR_MAIN_TASK==============CM00I 76

CL_WDR_MAIN_TASK=>EXECUTE

6 METHOD CL_WDR_MAIN_TASK==============CP CL_WDR_MAIN_TASK==============CM00U 6

CL_WDR_MAIN_TASK=>IF_WDR_RUNTIME~EXECUTE

5 METHOD CL_WDR_CLIENT_ABSTRACT_HTTP===CP CL_WDR_CLIENT_ABSTRACT_HTTP===CM01C 100

CL_WDR_CLIENT_ABSTRACT_HTTP=>HANDLE_REQUEST

4 METHOD CL_WDR_MAIN_TASK==============CP CL_WDR_MAIN_TASK==============CM00J 95

CL_WDR_MAIN_TASK=>IF_HTTP_EXTENSION~HANDLE_REQUEST

3 METHOD CL_HTTP_SERVER================CP CL_HTTP_SERVER================CM01B 388

CL_HTTP_SERVER=>EXECUTE_REQUEST_FROM_MEMORY

2 FUNCTION SAPLHTTP_RUNTIME LHTTP_RUNTIMEU02 1155

HTTP_DISPATCH_REQUEST

1 MODULE (PBO) SAPMHTTP SAPMHTTP 13

%_HTTP_START

Thanks,

Jagat

Former Member
0 Kudos

Hello All,

Please help me on this issue.

Thanks,

Jagat

Former Member
0 Kudos

Hello,

Even we are facing the same issue...

SLG1 shows error : Function Module is not maintained for Plug-in GRC .

Also we are unable to delete the rule result for Initiator rule in step 3 .

Is there any way to delete rule results which now belong to older MSMP workflow version ??

e.g. we are now on version 7 and the old eule result is on version 5 .

Please suggest.

Regards,

Victor

Former Member
0 Kudos

Hi guys,

Over a week ago, I had created a custom initiator rule in BRF+ and it was working and I was able to demonstrate the workflows were functioning as intended.

Today, when creating a new request (i.e. clicking "Access Request" in NWBC), the request page fails to load up and times out. I found this odd and when I reviewed SLG1, I found the following error entry

28.11.2011 ; 08:16:33 KVASTAN 2 GRC - Governance, Risk and Compliance Access Control Repository Dialog processing 00000000000000002438

Problem class Other

@5C\QError@ Config Error,Function Module is not maintained for Plug-in

Reading some of the forum posts, people are suggesting that the issue is due to the use of custom rules, which does not make sense as it was functioning correctly only a few days ago and no changes were made to the settings. Last week Support Pack 6 was implemented, but as I have stated earlier, the Access Request functionality was working fine even after SP06 was implemented.

I have also attempted in creating a new initiator rule and generated a new MSMP process, but still no luck in resolving the issue.

I would appreciate it if somebody has a good idea about the root cause of this issue and if they could share any workaround or fix in detail.

Many thanks

Answers (1)

Answers (1)

Former Member
0 Kudos

Still getting error

Former Member
0 Kudos

Hi ,

Delete an entry of 'Service Level Agreement' BRF rule from IMG and then try again ..

'Governance, Risk and Compliance->Access Control->Maintain AC Applications and BRFplus Function Mapping'

Best Regards,

Aman