/support/notes/service/sap_logo.png){kind=logo}
SAP Knowledge Base Article - PublicSymptom
Following dump happens when running PUST tcode
Category ABAP Programming Error Runtime Errors MOVE_CAST_ERROR Except. CX_SY_MOVE_CAST_ERROR ABAP Program SAPLHRST2 Application Component PY-XX-TL ---------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------- |Short Text | | Dynamic type conflict during the assignment of references. | ---------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------- |What happened? | | Error in the ABAP Application Program | | | | The current ABAP program "SAPLHRST2" had to be terminated because it has | | come across a statement that unfortunately cannot be executed. | ---------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------- |Error analysis | | An exception has occurred which is explained in more detail below. The | | exception is assigned to class 'CX_SY_MOVE_CAST_ERROR' and was not caught in | | procedure | | "CHECK_WAITINGPOINT" "(FORM)", nor was it propagated by a RAISING clause. | | Since the caller of the procedure could not have anticipated this | | exception, the current program was terminated. | | The reason for the exception is: | | During the 'CAST' operation ('?=' or 'MOVE TO') an attempt was made to | | assign a reference to a reference variable. | | The current content of the source variable is not compatible with the | | target variable however. | | Source type: \CLASS=CL_HR_PM_PW_PROCESS_PROG | | Target type: "\CLASS=CL_HR_PM_PW_PROCESS_WAIT" | ---------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------- |How to correct the error | | The exception must either be prevented, caught in procedure | | "CHECK_WAITINGPOINT" "(FORM)", or | | the possibility of it occurring must be declared in the RAISING clause | | in the procedure. | | | | | "MOVE_CAST_ERROR" CX_SY_MOVE_CAST_ERROR | | "SAPLHRST2" or LHRST2F02 | | "CHECK_WAITINGPOINT" | | If you cannot solve the problem yourself, please send the following | | information to SAP: | | | | 1. This description of the problem (short dump) | | To do this, choose System -> List -> Save -> Local File (unconverted) | | on the screen you are in now. | | | | 2. A suitable system log | | To do this, call the system log in transaction SM21. Restrict the time | | interval to ten minutes before the short dump and five minutes after | | it. In the display, choose System -> List -> Save -> Local File | | (unconverted). | | | | 3. If these are programs of your own, or modified SAP programs: Source | | code of these programs | | To do this, choose More Utilities -> Upload/Download -> Download in | | the Editor. | | | | 4. Details regarding the conditions under which the error occurred or | | which actions and input caused the error. | ---------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------- |User and Transaction | | Transaction......... PUST | | Program.............. SAPLHRST2 | | Screen.............. SAPMPUST 1001 | ---------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------- |Information on where terminated | | The termination occurred in ABAP program "SAPLHRST2", in "CHECK_WAITINGPOINT". | | The main program | | was "SAPMPUST". | | | | In the source code, the termination point is in line 282 of (Include) | | program "LHRST2F02". | | The termination is due to exception "CX_SY_MOVE_CAST_ERROR" occurring in | | procedure "CHECK_WAITINGPOINT" "(FORM)". | | This exception was not handled locally or declared in the RAISING | | clause in the procedure's signature however. | | The procedure is in program "SAPLHRST2". The source code begins in line 240 of | | (include) program "LHRST2F02". | ---------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------- |Source Code Extract | ---------------------------------------------------------------------------------------------------- |Line |SourceCde | ---------------------------------------------------------------------------------------------------- | 252| l_children TYPE pay_pm_object_tab, | | 258| l_tmp_parents TYPE pay_pm_object_tab WITH HEADER LINE, | | 259| l_all_parents TYPE pay_pm_object_tab. | | 260| | | 261| p_wait = ' '. | | 276| EXCEPTIONS | | 277| no_model = 1 | | 278| OTHERS = 2. | | 279| IF sy-subrc <> 0. ENDIF. | | 280| | | 281| l_process = cl_hr_pm_pw_process=>get_process( p_52sps-processid ). | |>>>>>| l_wait ?= l_process->get_step( p_52sps-stepid ). | | 283| l_children = l_model->get_children( l_wait->step ). | | 284| LOOP AT l_children INTO l_object. | | 285| l_step ?= l_object. | | 286| l_type = l_model->get_type_of_step( l_step ). | | 287| | | 288| IF l_type = status_step-stop. | | 289| l_next_gen = l_model->get_children( l_step ). | | 290| APPEND LINES OF l_next_gen TO l_children . | | 291| CONTINUE. | | 292| ELSEIF l_type = status_step-wait. | | 293| READ TABLE global_t52sps WITH KEY processid = p_52sps-processid | | 294| stepid = l_step->stepid. | | 295| IF sy-subrc NE 0. | | 296| l_next_gen = l_model->get_children( l_step ). | | 297| APPEND LINES OF l_next_gen TO l_children . | | 298| ENDIF. | | 299| CONTINUE. | | 300| ENDIF. | | 301|* find the correct wait point | ----------------------------------------------------------------------------------------------------
Cause
Inconsistencies
Resolution
In your test system, go to transaction PEST and change the number in your model.
You can do that from the menu, Process Model, Reassign number.
Then test the change by creating a new process ID and let me know.
Keywords
KBA , PY-XX-PYP , Payroll Control Center , Problem
Product
SAP SuccessFactors HXM Suite Core 2205
/support/notes/service/facebook.svg)
/support/notes/service/twitter.svg)
/support/notes/service/youtube.svg)
/support/notes/service/linkedin.svg)
/support/notes/service/instagram2.svg)