Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Dump due to Message_type_x (PGI)

Former Member

‎05-30-2014 10:33 AM

0 Kudos

Hi Experts,

Hope you are doing good.

I am currently facing one shortdump in Function Module MB_POST_GOODS_MOVEMENT when calling VL01.

Message ID sy-msgid Type X number sy-msgno with     "385830

I checked the Note 385380, and found that this note has replaced the previous message issuer with above.

Kindly let me know which Note I need to implement to solve the above issue.

Currently our  SAP version EHP 6.

Regards,

Praveen Kumar G.V.S

6 REPLIES 6

FredericGirod
Active Contributor

‎05-30-2014 10:43 AM

0 Kudos

Hi,

message type X means the error can't be solved.

You didn't give us the exact error message.

And if you find an OSS note you have to contact SAP, not SCN. SCN is just people like you, we don't manage OSS notes and standard modification

regards

Fred

raymond_giuseppi
Active Contributor

‎05-30-2014 10:55 AM

0 Kudos

As Frédéric  wrote you must first identify the error message which should not have happened (so SAP protected database intergity with the A then X error message type) -> ST22 look for SY-MSGID, SY-MSGNO, SY-MSGV1..4 values. Then look at message definition with SE91.

Regards,

Raymond

Former Member

‎05-30-2014 11:27 AM

0 Kudos

Hi,

Thanks for your replies.

Above is the error analysis.

the dump came from background jobs.

Regards,praveen

Preview file
72 KB

Former Member
In response to Former Member

‎05-30-2014 11:42 AM

0 Kudos

Hi Praveen,

Inside one of the the MB_DOCUMENT_BADI implementation error message(ZSD01100) is rising that causing the dump.

Its clearly mentioned in SAP Note - 1315985.

Thanks & Regards,

Arun

raymond_giuseppi
Active Contributor
In response to Former Member

‎05-30-2014 12:07 PM

0 Kudos

This is a customer message raised in a BAdI or other enhancement, somehow too late and SAP (385830 - Inconsistencies with goods movements in the background) triggers a dump to protect database.

Could you analyze the actual lock. As a solution you could try to lock some required record (ENQUEUE FM with _WAIT parameter set) before calling the BAPI or if the lock is triggered by a previous step, use some COMMIT AND WAIT and similar tool to prevent the lock.

Regards,
Raymond

Former Member

‎05-30-2014 11:35 AM

0 Kudos

Hi Praveenkumar,

Dump could be because of incorrect implementation of BADI MB_DOCUMENT_BADI  Check any inconsistency causing statements like commit, Rollback etc are present in the BADI implementation.

Please go through SAP Note 1315985 - FAQ: BAdI MB_DOCUMENT_BADI