Run Time Error - ASSIGN_LENGTH_0 in the results recording

[former_member408658]

Dear Gurus

I have got the Dump error - Run Time Error - ASSIGN_LENGTH_0 in the results recording from QE11,There is an SAP note available - 1027884 for solving the Dump error.

But my Question is what are all the possible reasons for the occurrence of the above Dump error.

Thanks for the possible reply if received....

Regards

Subramanian.C

[former_member408658]

Dear Sujit

Can u please confirm whether the number range problem belongs to inspection lot or something else because as there is no problem noticed in inspection lot number range.

pls reply

Regards

Subramanian.C

[Former Member]

Had it been issue with number range of inspection lot ,same error would have came during creation of lot itself.

It came during result recording means...Its either related to seial number ,physical sample number etc.

As I said dump of this problem can explain your where the issue is.

You can also debugg the program with the help of Abaper.

[former_member408658]

It came during result recording means...Its either related to seial number ,physical sample number etc.

THERE IS NO NUMBER RANGE PROBLEM NOTICED IN SL.NO & PHYSICAL SAMPLE NUMBER

As I said dump of this problem can explain your where the issue is.

ERROR AREA ATTACHED BELOW :

000360 IF T_OPTIPOS-VISLENGTH > '22'.

000370 T_OPTIPOS-VISLENGTH = 22."max. Länge in FLOAT->CHAR

000380 ENDIF.

-

-

---

ASSIGN E_STRING(T_OPTIPOS-VISLENGTH) TO <CHAR_FELD>.

000400

You can also debugg the program with the help of Abaper.

DUMP REMAINS ONLY IN ONE INSPECTION LOT& NOT REPEATED IN THAT ALSO ,SO IT IS NOT POSSIBLE TO DEBUGG THE SAME

PLEASE HAVE YOUR REPLY

Regards

Subramanian.C

[former_member42743]

I'm not sure but it seems to me as if one of your characterisitcs in the inspection lot somehow got created with zero characters. I.e. normally we define a characteristic with some type of character format such as 6 characters with two decimal places. Or a catalog with 10 char format.

How it would happen that the system thought it was a zero length I have no idea. But it sounds like SAP did if they gave you a note to resolve the dump error. That means that it was probably some very weird occurrance where a value got reinitialized to null in the program and never got populated with the next new value. I.e. in a situation where they are looping through a series of characterisitics and reiniitializing after each characteristic.

FF

[Former Member]

May be related to Number range .Dump can only tell you exact reason.