cancel
Showing results for 
Search instead for 
Did you mean: 

Error in phase XPRAS_UPG -- Write_to_offset_negative

Former Member
0 Kudos

Hi

While upgrading the SAP EHP2 to SAP EHP4 , i m facing the runtime error as Write_to_offset_negavtive as checked in SM37 the job RDDEXECL terminated with mentioned runtime error in Downtime phase.

Even i have reinitialized and repeat the same but still the same errors occurs. So pls suggest me some necessary actions for further processings..

Regards

Shilpa

Accepted Solutions (0)

Answers (1)

Answers (1)

markus_doehr2
Active Contributor
0 Kudos

please post the first pages of the dump.

Markus

Former Member
0 Kudos

Runtime Errors WRITE_TO_OFFSET_NEGATIVE

Date and Time 17.05.2010 12:17:12

Short text

Program error: WRITE TO contains a negative offset in the program "RGIMOVV0".

What happened?

Error in the ABAP Application Program

The current ABAP program "RGIMOVV0" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

What can you do?

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system

administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look

at and manage termination messages, and you can also

keep them for a long time.

Error analysis

In a "WRITE src TO dest+off[(len)] [INDEX i]" statement,

"off" contains a negative target field offset ("-2").

This is not allowed.

How to correct the error

Probably the only way to eliminate the error is to correct

the program.

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"WRITE_TO_OFFSET_NEGATIVE" " "

"RGIMOVV0" or "RGIMOVV0"

"APPEND-C"

Regards,

Shilpa

markus_doehr2
Active Contributor
0 Kudos

I'd open an OSS call (BC-UPG) for this error, I haven't found anything in notes beside that this seems to belong to FI-GL.

Markus

Former Member
0 Kudos

Markus,

We have opened an OSS call and found that it was our mistake. Actually we have just created a shell system from existing system and upgraded the support patches which is required to start the Installation of EHP4, but we forgot that we need to copy the SAP_ALL profile of 000 which is mandatory in SHell Creation, so now we dont have data in client 000, and we cannot import the data as system is locked and in downtime status. So do you have any idea that is it possible now to perform the client import on this stage or we have to do everyhting from scratch.

This is a demo System so dont have any constraints.

Regards,

Shilpa

markus_doehr2
Active Contributor
0 Kudos

Oh - so you were using TDMS? We did our fist upgrade try the same way but we filled some data in the system (several months) to actually see what's happening with the data after the upgrade.

Since you're very far in the upgrade it's not possible to reset it. Delete the system and start from scratch.

Markus