Solved: MIGO- Dump when posting (in "%_BEFORE_COMMIT")

Former Member · ‎2013 Oct 30

Hi everyone

I met a strange dump problem when MIGO posting for Purchase Order receiving, the detail of dump message as below, and I didn't do any change(Config or Develop) about MIGO before the error occurred, so I don't know what it caused by, please help me hurry up, thanks.

The current application program has detected a situation that should

not occur. A termination with short dump has therefore been triggered

by the key word MESSAGE (type X).

Short text of the error message:

在 ON COMMIT 或 ON ROLLBAC 期间的 COMMIT WORK

Long text of the error message:

Technical information about the message:

Message class....... 00

Number.............. 085

Variable 1..........

Variable 2..........

Variable 3..........

Variable 4.......... " "

SAP Release..... 740

SAP Basis level 0002

Application server... DEV

Network address...... 192.168.1.219

Operating system... Windows NT

Release.............. 6.1

Hardware type....... 4x AMD64 Level

Character length..... 16 Bits

Pointer length........ 64 Bits

Work process number... 6

Shortdump setting. full

Database server... DEV

Database type..... DB6

Database name..... DEV

Database user ID SAPDEV

Terminal.......... ThinkPad-PC

Character set C

SAP kernel....... 740

Created on....... Aug 16 2013 23:46:18

Created at....... NT 6.0 6002 x86 MS VC++ 16.00

Database version DB6_81

Patch level....... 31

Patch text.......

Database............. , , DB6 10.*

SAP database version. 740

Operating system... , , , , Windows NT 6.2

Memory consumption

Roll.... 0

EM...... 27498208

Heap.... 0

Page.... 57344

MM used. 1190240

MM free. 65808

Client................. 300

User.................. HUSH

Language key.......... 1

Transaction......... MIGO

Transaction ID...... 914A41E35EE5F14AA654E61F13AAC303

EPP whole context ID...... E61F13AAC3031EE390A93723F5BE8654

EPP connection ID........ 00000000000000000000000000000000

EPP call counter......... 0

Program.............. SAPMSSY0

Screen.............. SAPMS380 0100

Screen line.......... 3

Active debugger..... "none"

The termination occurred in ABAP program "SAPMSSY0", in "%_BEFORE_COMMIT". The

main program

was "SAPMS380 ".

In the source code, the termination point is in line 196 of (Include)

program "SAPMSSY0".

184 * ---------------------------------------------------------------------

185 * FORM %_BEFORE_COMMIT

186 * called from RSYN commit.rs1

187 * ---------------------------------------------------------------------

188 form %_before_commit. "#EC *

189 data: l_oncom like sy-oncom.

190 data: txend type c.

191

192 * forbid COMMIT if already in ON ROLLBACK handling

193 * allow COMMIT during ON COMMIT for backward compatibilty

194 call 'GET_SWITCH_TXEND' id 'STATE' field txend.

195 if txend = 'R'.

>>>>> message x085(00).

197 endif.

198

199 * COMMIT during CALL DIALOG/SUBMIT, POC, Update task

200 * or End Transaction event?

201 check sy-oncom <> 'N' and sy-oncom <> 'P' and

202 sy-oncom <> 'E' and sy-oncom <> 'V'.

203 * change sy-oncom to avoid recursion

204 l_oncom = sy-oncom.

205 sy-oncom = 'E'. "E = Event Handling

206

207 * no escape out off this form other than ENDFORM

208 system-call state_limit set.

209 * Hook for Process Information Infrastructure

210 call function 'SPI_AGENT_COMMIT'.

211 * Raise event 'Commit Requested' for Object Manager

212 call method cl_os_transaction_end_notifier=>raise_commit_requested.

213 * restore sy-oncom

214 sy-oncom = l_oncom.

Former Member · ‎2013 Nov 11

Hi,

Did you get this issue resolved? I am having the same issue while doing Goods Receipt for a Production Order.

Thanks,

Birla.

Former Member · ‎2013 Nov 11

Hi,

Did you get this issue resolved? I am having the same issue while doing Goods Receipt for a Production Order.

Thanks,

Birla.

Former Member · ‎2013 Nov 14

Yes，I have resolved,

Please refer notes 1843441 - Optimizing error prevention mechanism from SAP Note 1776835

It's a bug because SAP didn't show the correct exception when program dump, and it can make underlying error causing display if you implement this note

the real reason of this issue is just so funny that because FI document number range haven't be assigned, and you will do a material document with FI document by transaction MIGO

Glad to help you

Former Member · ‎2014 Mar 27

Hey could you kindly help me ..... I'm also facing Same issue

gimeno_sus · ‎2013 Nov 13

I have the same problem since we have implemented SEPA notes.

Former Member · ‎2013 Nov 13

Check this SAP notes:

1098491

1041122

Regards Nico

gimeno_sus · ‎2013 Nov 14

Thanks Nico, but I think this notes don´t apply for me because there are for less support package level than we have.

We are in SAPKH60414 support package for SAP_APPL, and SAPKA70114 s.p. for SAP_ABA.

Regards

Susana

Former Member · ‎2013 Nov 14

It have been done, pls refer to my comments

Former Member · ‎2014 Sep 02

WHre is document....please share it.....

Former Member · ‎2014 Nov 20

It's already marked in the up there, scan it carefully

BTW: the ture reason is some number range of the FI Doc haven't defined by your FI consultant

By Category

Related Content

Activity Groups

Industry Groups

Influence and Feedback Groups

Interest Groups

Location Groups

Customer Only Groups

Forums

Related Resources

Products

Learning and Support

About

My SAP Profile

My SAP Profile

MIGO- Dump when posting (in "%_BEFORE_COMMIT")