topic Re: MIGO BAdi or User-Exit after Database Commit in Application Development and Automation Discussions

MIGO BAdi or User-Exit after Database Commit

Former Member — Tue, 12 Oct 2010 11:05:13 GMT

Hi all,

I'm looking for a BAdI or user-exit after database commit for MIGO posting. I want to create a MM document after MIGO posting.

I already tried MB_DOCUMENT_BADI / MB_DOCUMENT_UPDATE but doesnt seem to be triggering. I have put a piece of code but and doing a Update debugging but it doesnt stop there. How can i do that?

Best regards,

Munur

Re: MIGO BAdi or User-Exit after Database Commit

former_member404244 — Tue, 12 Oct 2010 11:33:30 GMT

Hi,

Check these enhancements MB_CF001 and MBCF0005.

Regards,

Nagaraj

Re: MIGO BAdi or User-Exit after Database Commit

Former Member — Tue, 12 Oct 2010 11:57:56 GMT

Hi Nagaraj,

I tried to debug. İt was not stopet to enhancement. Are there any suggestions?

Munur

Re: MIGO BAdi or User-Exit after Database Commit

former_member404244 — Tue, 12 Oct 2010 12:02:56 GMT

Hi,

While doing MIGO actually "MB_DOCUMENT_BADI" and use method MB_DOCUMENT_BEFORE_UPDATE should work.. also you can check MB_MIGO_BADI.

The other work around is once the migo postings are done for a perticular day , you can write a custom program to read the material documents and then post it as per your requirement..This should be a scheduling job.

Regards,

Nagaraj

Re: MIGO BAdi or User-Exit after Database Commit

Former Member — Tue, 12 Oct 2010 13:10:44 GMT

Hi Munur,

MB_DOCUMENT_UPDATE is called in update task so if you are debugging it in normal way it will not go in debugging

you have to switch on update debugging from your debugger. Go to Old debugger and switch on Update debugging and system debugging available under settings tab.

And For your issue I suugest you to create one update function module ( Put your whole logic in function module and give this FM type as Update in attribute select update radiobutton) and call this FM in BADI implematation by using

Call function Zfunction in update task. Read the F1 help for the same.

Regards,

Pawan

Re: MIGO BAdi or User-Exit after Database Commit

Former Member — Tue, 12 Oct 2010 15:20:18 GMT

Hi Pawan,

I coded all your suggestions but error occurs below. But there was no lock.!

"The plant data of the material 130860 is locked by the user MEBCIOGLU"

Best regards,

Munur

Re: MIGO BAdi or User-Exit after Database Commit

eduardo_hinojosa — Wed, 13 Oct 2010 11:26:58 GMT

Hi, Munur,

I suggest you that avoid these enhancements. Read Note 92550 - Stock inconsistency due to customer enhancement (exit, BAdI) to understand the reasons and the problems that you have in debug (because it is called with an FM in UPDATE TASK), and perhaps the same problems with locks.

If you go on thinking in use it, avoid call function modules, messages, lock/unlocks and call your z* in UPDATE TASK.

Regards,

Eduardo

Re: MIGO BAdi or User-Exit after Database Commit

Former Member — Tue, 19 Oct 2010 15:30:01 GMT

Thanks