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

Syntax error in CL_HCM_TIMESHEET_MAN_MPC_EXT for timesheet V2

I am trying to implement SAP Fiori apps myTimesheet V2 and approve Timesheet V2 on an SAP ECC Ehp6 Backend.

We have installed SAP Fiori for SAP ERP HCM 1.0, and can register odata service from gateway for Timesheet approval (HCM_Timesheet_approve_srv) and trigger succesfully.

However when trying with service HCM_Timesheet_man_srv, registering is ok but triggering returns error code 500 and then we can find dump in st22 due to syntax error in program CL_HCM_TIMESHEET_MAN_SRV_MPC_EXT as shown in dump file extract below.

Does anyone have any idea about how to resolve this issue.
Same dump occurs when calingl Odata Service and when checking data model in spro (Gateway Service enablement ...-> Maintain Model) for HCM_TIMESHEET_MAN_MDL

Of course I started an oss message already but awaiting for hints at this stage.

Regards,

Frank

|Short text                                                                                        | |    Syntax error in program "CL_HCM_TIMESHEET_MAN_MPC_EXT==CP ".                                  | ----------------------------------------------------------------------------------------------------  ---------------------------------------------------------------------------------------------------- |What happened?                                                                                    | |    Error in the ABAP Application Program                                                         | |                                                                                                  | |    The current ABAP program "/IWBEP/CL_MGW_MED_DEF_BADI====CP" had to be                         | |     terminated because it has                                                                    | |    come across a statement that unfortunately cannot be executed.                                | |                                                                                                  | |    The following syntax error occurred in program                                                | |     "CL_HCM_TIMESHEET_MAN_MPC_EXT==CP " in include                                               | |     "CL_HCM_TIMESHEET_MAN_MPC_EXT==CO " in                                                       | |    line 5:                                                                                       | |    "La méthode "DEFINE_COMPLEXTYPES" ne doit pas être déclarée ou héritée "                      | |    "dans la classe "CL_HCM_TIMESHEET_MAN_MPC_EXT"."                                              | |    " "                                                                                           | |    " "                                                                                           | 
Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Jan 12, 2016 at 06:38 PM

    Dear all,

    After further analysis, we found that class CL_HCM_TIMESHEET_MAN_MPC_EXT contains effectively error as shown on below screenshot.

    So It looks like some redefined complextypes entry was added partially under methods, can anyone check on his/her system and let me know if this is missing definition, or abusive entry.

    1. So can we simply delete redefined complextypes entry or activate it, or is there something missing in my system.
    2. If I delete the entry do I need further action to have it taken into account in the Odata Service ?

    Thank you for your help

    Best Regards,


    screenshot.png (195.7 kB)
    Add a comment
    10|10000 characters needed characters exceeded

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.