cancel
Showing results for 
Search instead for 
Did you mean: 

MSS Home Page Dump ERROR: Type conflict when calling a function module

Former Member
0 Kudos

Hi Friends,

When I run the MSS Home Page I am getting error.

App Name: HRMSS_HOMEPAGE

Package: PAOC_MSS_HOMEPAGE_WDA

In the debug, thisis the function module where giving the dump.

METHOD get_pernr.

* This method will take the SY-UNAME of logged in user and returns his personnel number.

   DATA lv_name type sysid.

   lv_name = sy-uname.

   CALL FUNCTION 'RP_GET_PERNR_FROM_USERID'

     EXPORTING

       begda     = sy-datum

       endda     = sy-datum

       usrid     = lv_name

       usrty     = '0001'

     IMPORTING

       usr_pernr = ev_pernr

     EXCEPTIONS

       retcd     = 1

       OTHERS    = 2.

*--Code changes for Note 1706443

   IF sy-subrc <> 0.

      ev_result = sy-subrc.

      RETURN.

   ELSE.

      ev_result = 0.

   ENDIF.

ENDMETHOD.

From ST22 this is the error log:

rror analysis

   An exception occurred that is explained in detail below.

   The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_TYPE', was

    not caught in

   procedure "GET_PERNR" "(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:

   The call to the function module "RP_GET_PERNR_FROM_USERID" is incorrect:

   The function module interface allows you to specify only

   fields of a particular type under "USRID".

   The field "LV_NAME" specified here is a different

   field type

Thanks

Krish

   .

Accepted Solutions (0)

Answers (2)

Answers (2)

sahirn
Active Contributor
0 Kudos

Hello Krish Reddy,

There are several notes with symptoms of this issue ( .e.g. 2149758 - No exception handling in call to RP_GET_PERNR_FROM_USERID - causing dump)

Check for the missing notes and apply.

Hope this helps.

With regards,

Sahir.

Former Member
0 Kudos

Any one?

Thanks

Krish

Former Member
0 Kudos

Hi Krish,

Why don't you change the TYPE in your DATA: statement to P0105-USRID instead so it matches the type of the IMPORTING parameter.

Hope this helps!

Former Member
0 Kudos

Hi Sinai,

this is standard right? does it allow me to chagne? Prompting for access key if I try that.

Thanks

Krishna

Former Member
0 Kudos

The data declaration is within a standard program?  Sorry if i missed that...