Skip to Content
author's profile photo Former Member
Former Member

Error while creating Single role -BRM - Uncaught Exception CX_FDT_INPUT

Hi,

I am trying to create Single role and getting error when i click Save or Save and continue.

Version I am using is:

This is occurring when I go to Owners/Approvers tab and as 'Add' button is disabled, I am clicking 'Save' as shown below.

The error I am getting is:

From the tcode ST22, the info i got is: (error is in line 33, red in color)

----------------------------------------------------------------------------------------------------

Category ABAP Programming Error

Runtime Errors UNCAUGHT_EXCEPTION

Except. CX_FDT_INPUT

ABAP Program CL_GRFN_AC_BRFP===============CP

Application Component GRC

Short text

An exception occurred that was not caught.

What happened?

The exception 'CX_FDT_INPUT' was raised, but it was not caught anywhere along

the call hierarchy.

Since exceptions represent error situations and this error was not

adequately responded to, the running ABAP program

'CL_FDT_FUNCTION===============CP' has to be terminated.

Error analysis

An exception occurred that is explained in detail below.

The exception, which is assigned to class 'CX_FDT_INPUT', was not caught in

procedure "EXECUTE_BRF_RULE" "(METHOD)", nor was it propagated by a RAISING

clause.

Since the caller of the procedure could not have anticipated that the

exception would occur, the current program is terminated.

The reason for the exception is:

An exception because of wrong method interface usage occurred

Missing RAISING Clause in Interface

Program CL_GRFN_AC_BRFP===============CP

Include CL_GRFN_AC_BRFP===============CM005

Row 1

Module type (METHOD)

Module Name EXECUTE_BRF_RULE

Trigger Location of Exception

Program CL_FDT_FUNCTION===============CP

Include CL_FDT_FUNCTION===============CM00D

Row 33

Module type (METHOD)

Module Name LOAD_BUFFER

Source Code Extract

Line SourceCde

3 DATA: lts_version TYPE if_fdt_admin_data=>ts_version,

4 ls_message TYPE if_fdt_types=>s_message,

5 lt_message TYPE if_fdt_types=>t_message,

6 lv_version TYPE if_fdt_types=>version,

7 lv_no_version TYPE abap_bool,

8 lv_timestamp_string type string,

9 lv_i type i.

10

11 FIELD-SYMBOLS <ls_version> TYPE if_fdt_admin_data=>s_version.

12

13 ASSERT NOT ( iv_timestamp IS SUPPLIED AND iv_version IS SUPPLIED ). ">>>

14

15 IF iv_timestamp IS NOT SUPPLIED AND iv_version IS NOT SUPPLIED.

16 * when we have the last version we can read from the buffer

17 IF mv_ms_buffer_loaded EQ abap_false.

18 * load the buffer with the last version

19 ms_buffer = load_buffer_db( ).

20 mv_ms_buffer_loaded = abap_true.

21 ENDIF.

22 rs_buffer = ms_buffer.

23 RETURN. ">>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

24 ELSEIF iv_timestamp IS SUPPLIED. "get the right version for the tmstmp

25 if_fdt_admin_data~get_active_version(

26 EXPORTING iv_timestamp = iv_timestamp

27 IMPORTING ev_version = lv_version

28 ev_no_version = lv_no_version ).

29 IF lv_no_version EQ abap_true.

30 cl_fdt_services_internal=>get_date_and_time_utc( EXPORTING iv_timestamp = iv_timestamp

31 IMPORTING ev_utc_date_time_string = l

32 MESSAGE x006(fdt_core) WITH lv_timestamp_string INTO ls_message-text.

>>>>> message_exception ls_message lt_message cx_fdt_input.

34 ENDIF.

35 ELSEIF iv_version IS SUPPLIED. "use this version

36 lv_version = iv_version.

37 ENDIF.

38

39 * do we have a valid version now?

40 if_fdt_admin_data~get_versions( IMPORTING ets_version = lts_version ).

41 READ TABLE lts_version ASSIGNING <ls_version>

42 WITH TABLE KEY version = lv_version.

43 IF sy-subrc NE 0.

44 MESSAGE x002(fdt_core) WITH iv_version INTO ls_message-text.

45 message_exception ls_message lt_message cx_fdt_input.

46 ENDIF.

47

48 lv_i = lines( lts_version ).

49 READ TABLE lts_version INDEX lv_i ASSIGNING <ls_version>.

50 IF <ls_version>-version EQ lv_version.

51 * when we have the last version we can read from the buffer

52 IF mv_ms_buffer_loaded EQ abap_false.

----------------------------------------------------------------------------------------------------

I performed all the configuration steps required.

I cannot proceed further and your help is much required.

Regards

Ashok

Error.jpg (79.5 kB)
Version.jpg (49.1 kB)
Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Best Answer
    Posted on Dec 20, 2014 at 12:42 PM

    Hi Ashok

    What have you configured for role methodology BRF+ in the IMG? The first time you press save on a new role will trigger execution of the BRF+ rule to determine role methodology. Have you full configured that? After it has been executed, the approver screen should be modifiable.

    Please check IMG for BRF+ steps to configure this (bad timing, I'm working a document for methodology configuration but it's not ready yet to share with SCN)

    Regards

    Colleen

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Santosh,

      Please check your system date. I hope it will be the current date.

      By default always the system date will be the current date and if working on client system we even do not have access to change it.

      For Ashok, his system date is not same as current date.

      Regards

      Raj

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.