Proxy method - commit work

[Former Member]

Hi,

For Tcode MB1A, i want to send inv. updates to PI after save. But as no enhancement point is available calling proxy method before Commit work of main program SAPMM07M.So just wanted to know is their any need to put Coomit Work after we call proxy method.In this case i may need to pass more than one record. Can we pass all record at a time or record by record.

Please help me.

Regards,

Jaya

[Sm1tje]

Ok, there is no enhancement point available, but what about (classic) BAdI's of user exits?

A few things to consider here:

1. Is commit work really necessary for proxy method?

2. If you already call the proxy method before the actual COMMIT is done, then have all the checks already been done (meaning: no errors will occur)? Because if it fails, and you have already sent the data to PI, this will lead to inconsistencies.

3. If you add COMMIT work, which is 'never' a smart thing to do within a standard transaction of which you do not really know the implecations. You might update database, even though (perhaps) not all (standard) checks have been done yet.

Maybe you can start a workflow, after SAVE (Create or update) event. Then you are sure data has been commited and no errors exist.

[Former Member]

Hi Micky,

Thanks for the information.

Actually i need to find out common BADI for tcodes MIGO,MB1A,Mb1B,MB1C. Their is BADI 'MB_DOCUMENT_BADI' but in that in before_update account doc.number is not generated.

In my requirement i want that number. So searching other options.

Right now, i am going for approach of custom BADI & call that in Enahancement spot.

Regards,

Jaya