Edwin,
As far as I know there are monitoring tools based on if you are using CRM or ERP tied to BDocs that could be used to see if a message failed on the CRM side for example. I am not sure if this can be used for your purpose (Like retrying the transaction). But this really depends on the error produced by your user when they pressed transmit, right? By just re-running the same input parameters in the BAPI does not guarantee that the BAPI will run.
EX: Input Parameter --> BAPI --> Output Result -- Error.
So if the error occurs on the Client (Parameters/Inputs) -- Transmit --> SMP 3.0 (Error logs) --> Mobile AddOn (SMERP or SCRM) --> RFC --> SAP CRM/ERP
Where did the error come from? Did it come from the client? Bad input therefor bad output? So the SAP Monitoring tools that exist in SAP CRM/ERP could be too late already? So the Error Handling of AGentry needs to be smart enough to know what normally get nulled or blank during transmit and to either create a dummy or default variable as a temporary solution to proceed, right? This is where the consulting is needed to understand where to tweak it (i.e. Java, BAPI or Client).
I'll give an example below on at least the CRM part.
Or SAP transaction code (In CRM):
- SMWP (Monitoring Cockpit)
- SMW00 (Error Handler)
- SMW01 (Display Bdoc Messages)
- SMQ1 (Outbound Queue Monitor)
- SMQ2 (Inbound Queue Monitor)
- SMQR (Queue-In Scheduler)
- SMWT (Middleware Trace)
- R3AR3 (Monitor Request)
- SDIMA (Data Integrity Manager)
Those are some ideas but I am not an expert in those level of details on those toolset as I worked in Mobility side. There may be others who are experts in it in CRM or ERP. In the picture above it may be too late if the mobile client gave a bad input to the client. So special configuration needs to be done if you want the fix on the Java side (SAPWM.jar -extend it to do the processing fix in Java - this is where most of the exception handing is done in Work Manager, Service Manager) or if you want the fix to be done by Agentry error handling then design needs to be done there. But if you are already in ECC ERP then the error is already been made to the saving to the ERP is not completed so you may see red marks that it was not processed.
I hope this helps. I am speculating at the SAP side ERP/CRM it may be too late to handle unless you want to further customized the BADIs to improve it.
Best Regards,
Mark Pe
SAP Platinum Support Engineer