cancel
Showing results for 
Search instead for 
Did you mean: 

UPdate terminated error in MIGO

Former Member
0 Kudos

Dear eexpDear experts

Haere while posting through Migo , i m getting dump error for material document.THat means system shows the material doc after clicking on posting but when i am goin to see that doc.system doesnot show that doc.I  have check the no rangr pf material doc in OMBT and change the current no equal to status but still showing the termination error

Accepted Solutions (1)

Accepted Solutions (1)

JL23
Active Contributor
0 Kudos

Why did you check the number range?

Have you checked the posting failure in SM13 or the dump in ST22? what info did it show?

Answers (2)

Answers (2)

former_member619089
Active Participant
0 Kudos

Hello,

This is happening due to changes in the overlap of number range. Check the number range of your document for example:

in you are making GR in MIGO then check for WE document type number range, accounting number number ranges, if WM is implemented at TR is automatically generating then the number ranges of TR. And all the other respective documents.

Thanks

former_member210560
Active Contributor
0 Kudos

Dear harshad81,

Please check if any custom print program in your system. You can check which Function module

caused this termination via SM13. Your dump behaviour usually caused by your own print program.

If so, you need to correct your own print program.

Regards,

ian Wong Loke Foong

Former Member
0 Kudos

Thansk for reply

Here i when i saw in ST22 , there is problem in insert the entry in JESTO table

INSERT jsto CLIENT SPECIFIED

                 FROM TABLE jsto_ins.

   ENDIF.

   DESCRIBE TABLE jsto_upd LINES sy-tabix.

   IF sy-tabix > 0.

     field-symbols <fs_jsto_line> like jsto_upd.

     loop at jsto_upd assigning <fs_jsto_line>.

       IF <fs_jsto_line>-chgnr = '000'.

         <fs_jsto_line>-chgnr = '999'.

       ENDIF.

* on change of status profile delete user status related to old profile

       IF <fs_jsto_line>-STSMA NE <fs_jsto_line>-STSMA_OLD.

         DELETE FROM JEST CLIENT SPECIFIED WHERE

                MANDT = <fs_jsto_line>-MANDT AND

                OBJNR = <fs_jsto_line>-OBJNR AND

                STAT  LIKE 'E%'.

         DELETE FROM JCDS CLIENT SPECIFIED WHERE

                MANDT = <fs_jsto_line>-MANDT AND

                OBJNR = <fs_jsto_line>-OBJNR AND

                STAT  LIKE 'E%'.

JL23
Active Contributor
0 Kudos

A dump usually explains in the pages before the code piece what the actual problem is.

Please provide exact info about that, then code piece alone does not really help.

Is it caused by a duplicate record?

former_member210560
Active Contributor
0 Kudos

Dear Harshad81,

The problem maybe due to conflict of the Current number in SNRO
EQUIP_NR and the last number in EQUI. Extended the equipment number

range might fixed the issue.

Regards,

ian Wong Loke Foong

Former Member
0 Kudos

it may be happening because your number range is exceeded and it has started from begining.

For e.g. if your number range for WE was 5000000 to 5199999, your current number would have already been 5199999 once and hence it would have reset itself to again 5000000, and hence when you are posting any new document it will check the system and will find that document already exist and will give you a dump.

if this is the issue, you should clear the current number and extend the number range to let us say 5999999 and set the current number to 5200000 for e.g.

Regards,

Dakshesh