How to delete Remittance Advice through FB01 - which User exit or BADI?

Question

I have created a BDC program for transaction FB01 to create an FI posting.  During this BDC session, i need to delete the associated remittance advice using the function REMADV_DELETE.
Is there a user exit or BADI that i can use to call REMADV_DELETE once the FI posting is successful?
Thanks,
Jay

Answer 1

Jay,
In BTE there are two types of exit - Publish and Subscribe (P&S) and Process.  Generally P&S give access to read data from a transaction and trigger your own processing as a result, while Process give access to change parts of the data in the SAP transaction.  For what you want, P&S probably gives the functionality you need.
You need to copy the sample function to a Z function in a Z function Group.  Put in your code, and activate the function and function group.  As an initial test just a break-point in the code is useful to see when the exit executes and what data is available.
Then in transaction FIBF you need to insert customising to link in and activate the exit.
In the FIBF transaction, go to menu option Settings>Products>Of a Customer.  Select New Entries and create a Z... entry with appropriate text. Leave other fields at this time and save.
Go to Settings>P/S Modules>Of a Customer. Select New Entries and create an entry for the relevant event number with the Z product you just created and add your function module name. Country and Appl can be filled or left blank for "All". Save the entry.
Go back to the Settings>Products>Of a Customer entry and selct the activate check box and save the entry.
Your function should now get executed at the relevant point.  Remember this will get executed in all posting transactions, so include appropriate checks for your transaction code, document type, etc.
One note.  Transaction FB01 performs some of its updates using "IN UPDATE TASK" so some records may not be created at the time some exits are executed.  In the old style debugger a commit is performed when you debug so the update is triggered, but then when you run without the debugging things work differently.  The new style debugger lets you debug these exits without the commit and thus gives a better picture of what will really happen.
Andrew