Skip to Content
0
Former Member
Sep 28, 2012 at 10:10 AM

Payslip Error in ESS

24 Views

Dear Experts,

I have made the necessary configuration for ESS Payslip in R/3

However when I am executing the "Customized Payslip", in R / 3 it is showing me the below error.

_______________________________________________________________________________________________________________________________

Category ABAP Programming Error Runtime Errors CONVT_NO_NUMBER Except. CX_SY_CONVERSION_NO_NUMBER ABAP Program ZTEST_PAYSLIP

Application Component Not Assigned

Date and Time 28.09.2012 13:02:12

Short text

Unable to interpret "26.09.2012" as a number.

What happened?

Error in the ABAP Application Program

The current ABAP program "ZTEST_PAYSLIP" had to be terminated because it has come across a statement that unfortunately cannot be executed.

Error analysis

An exception occurred that is explained in detail below. The exception, which is assigned to class 'CX_SY_CONVERSION_NO_NUMBER', was not caught in procedure "%_GET_PERNR" "(FORM)", 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 program attempted to interpret the value "26.09.2012" as a number, but since the value contravenes the rules for correct number formats, this was not possible.

ABAP Programming Error Runtime Errors CONVT_NO_NUMBER Except. CX_SY_CONVERSION_NO_NUMBER ABAP Program ZTEST_PAYSLIP

Application Component Not Assigned

Date and Time 28.09.2012 13:02:12

Short text

Unable to interpret "26.09.2012" as a number.

What happened?

Error in the ABAP Application Program

The current ABAP program "ZTEST_PAYSLIP" had to be terminated because it has come across a statement that unfortunately cannot be executed.

Error analysis

An exception occurred that is explained in detail below. The exception, which is assigned to class 'CX_SY_CONVERSION_NO_NUMBER', was not caught in procedure "%_GET_PERNR" "(FORM)", 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 program attempted to interpret the value "26.09.2012" as a number, but since the value contravenes the rules for correct number formats, this was not possible.

Need your Urgent assistance on the above query.

Regards,

DRC