Design question for asynchronous message error handling via PI 7.1
We are implementing 7.1 and have come to a spot were any help or thoughts would be appreciated. We are trying to figure out what to do for errors that happen asynch with user data.
For example we expose an asynch service to update a work order from an outside system, there could be times that an data could be out of sync or an order is closed etc. When the user submits from handheld it comes to PI.
If an error happens we were trying to brainstorm what would be the most efficient way to handle possible errors we could recieve.
1. Use IDOC's this is good as the process can be rerun, but the user interface is hard to read etc and users might not really understand layout etc
2. Use Bapi's write a wrapper that would call the bapi and if an error code is returned open a BDC session for the user to try, thus saving the data and giving the user more of a user friendly ui
3. Use a wrapper and do a call transaction thus a BDC would always be created.
Has anyone faced this type of questions before and if so what did you do that made sense, any thoughts on the three options or others.
Thanks in advance and I do award points