ME_PROCESS_PO_CUST - Method PROCESS_HEADER not triggered

[Former Member]

Hello,

I've two questions:

1. In our system the method PROCESS_HEADER of the Badi ME_PROCESS_PO_CUST is not triggered, when I change the purchase group in ME21N?

2. I'm displaying a warning on item level depending on certain purchase groups on header level -> How can I delete this warning, if purchase group is changed?
For example: If purchase group YYY is used on header level I'm displaying a warning message (I'm using MMPUR_MESSAGE_FORCED in PROCESS_ITEM and this works fine). When the purchase group YYY is changed to ZZZ the warning message on item level should disappear.

Thanks
Daniel

Message was edited by: Daniel Brack  Regarding 1: I just implemented note 1401871, but the PROCESS_HEADER method still isn't triggered when I change the purchase group in ME21N.

Message was edited by: Daniel Brack

[former_member585060]

Hi,

    Check on this SAP note, it might be some useful.

SAP Note 663650 - BAdI ME_PROCESS_PO_CUST: Fields are not transferred.

Thanks & Regards

Bala Krishna

[Former Member]

The note 663650 is regarding release 4.70, but we are on 6.00 (SAP APPL 600 SAPKH60017).

[Former Member]

I can't believe it. I tried it again a few minutes ago and suddenly the method is triggered. I had a similar issue few weeks ago, where the debugger didn't stop at a certain BREAK-POINT statement and suddenly it worked without making any changes.

However, it seems question 1 is answered, but question 2 is still pending.

Thanks & Regards

Daniel

[former_member585060]

Hi,

    Have you tried using ME21N transaction, instead of ME21.

Thanks & Regards

Bala Krishna

[Former Member]

I meant ME21N, was just a mistake by me writing ME21. I've corrected it in the original post.

I can't believe what is going on. Today I tried it again and  it doesn't work again (and I didn't change anything). The debugger stops at the "BREAK-POINT" for the first time in ME21N and when I change the pruchase org. or the purch. group the method doesn't seem to be triggered.

That's my first time trying out Badis and I guess I'll switch back to the good old user-exits as it seems that the Badi technique is not yet stable enough for a productive use .

Message was edited by: Daniel Brack

[former_member585060]

Hi,

    Have u tried implementing the Badi

ME_CHECK_ALL_ITEMS :- Run Through Items Again in the Event of Changes in EKKO.

Thanks & Regards

Bala Krishna

[Former Member]

Ok, tried this also, but neither PROCESS_HEADER of Badi ME_PROCESS_PO_CUST nor RECALCULATE_ITEMS of Badi ME_CHECK_ALL_ITEMS are triggered when I change the PO org. or the PO group.