Unable to save data via Input schedule or load transaction data via flat file

[former_member339201]

Hi experts,

Currently we are facing a weird situation where we try to input any data through input schedule or upload transaction data via the flat file, we are getting the same error as below :

500 SAP Internal Server Error

ERROR: 40000 cannot be interpreted as a number (termination: RABAX_STATE)

Please suggest.

Regards,
SHUBHAM

[former_member186338 · Accepted solution]

Please show screenshot of the input form with full explanation.

[former_member339201 · Accepted solution]

Hi Vadim ,

I am attaching the screen shots of the error and the SAP standard code where it gets the error.

I cant show the Input form , but the issue is when you input data whether via some input schedule or via flat file.

The program where the code ends when you save the data is :

PROGRAM: CL_UJO_WRITE_BACK=============CP

METHOD: UPDATE_PARAM_TABLE

Do we need to apply some note to fix this.

Regards,
SHUBHAM

[former_member186338 · Accepted solution]

First - I see no reason to avoid posting the input form   You can always hide some sensitive info.

Second - do you have any write back badi or validation badi?

[former_member186338 · Accepted solution]

P.S. Also check BPC parameters in SPRO may be you have incorrect package size.

[former_member339201 · Accepted solution]

Hi Vadim,

The package size is fine, when we debugged into the program we found 40000## value.

We went to SPRO and checked the PACKAGE_SIZE parameter under Model Parameters.

The value 40000 was with space. We removed the space and it works fine now!!

Thanks,
SHUBHAM

[former_member339201 · Accepted solution]

No There is no validation or write back code used during saving the data.

It was a simple case of saving data via input schedule or upload via the flat file using /CPMB/IMPORT process chain.

SHUBHAM

[former_member339201 · Accepted solution]

No There is no validation or write back code used during saving the data.

It was a simple case of saving data via input schedule or upload via the flat file using '/CPMB/IMPORT' process chain.

SHUBHAM

[former_member186338 · Accepted solution]

My answer was exactly about the value stored in spro. And it was not fine