Hi,
If i understand you requirement correctly, you have made some customization to a standard program's PBO/PAI. This customization updates some Z Tables. Now the flow is such that your customization executes before Standard program has completed its validations and there is a possibility that an error might be thrown later in the program validation and in such cases you do not want your changes to be committed to the Z tables.
If my understanding is correct, i can think of below solutions.
1) Since you are customizing the standard code, look for a EXIT/BADI which get triggered on SAVE and add your code here.
If you have tried this already and didn't find a suitable enhancement, then try with the below solution.
Create an FM with the processing type as an "Update Module" (attribute tab of the FM in SE37), and pass the data that needs updated in the Z table to this FM, inside this FM you can have your custom validations and code to update the Z table.
Now call this FM "CALL "FM" IN UPDATE TASK" in the PBO/PAI of your customization.
With this what you will achieve is that, the update modules will be called only if the original transaction was committed successfully.
Regards,
Chen
Edited by: Chen K V on Jun 3, 2011 12:59 PM
Bluesky
