I have a task that is supposed to return the error messages in the event of a failure. I'm using temporary errors so that it will retry a couple of times before giving up.<br><br>When it fails I would like to know what that error message was and then send a mail to the user with details of the error. The error step is modeled and I'm using a bapiret message to pass around the information. The strange thing is that the return messages are never filled after the temporary exception is raised.<br>
<br>The problem is that it seems that after <span><span class="L0S52">RAISE</span> EXCEPTION <span class="L0S52">TYPE</span> cx_bo_temporary the return values aren't moved back to the container. I know the container bindings are all ok because if I remove the raise exception everything proceeds as expected and the bapiret is filled.<br>
<br></span><span>I've tried checking through various oss notes and the sap help but no
luck. The background step is synchronous so I would expect that on
completion OR temporary error the container is updated. <br><br></span><span>My question is: is this normal behaviour for no return parameters to be filled if there is a temporary exception? i.e. is this a bug or a feature? I don't remember if this is the same if done with the older business objects when an exception is raised.<br>
<br>A simplified version of the code is just:<br><br>ex_bapiret = lx_bapiret. " both are type bapiret2_tab and lx_bapiret has a single line in it<br>raise exception type cx_bo_temporary.<br><br>Otherwise does anyone know a good method to create a custom temporary message and use it to pass data to the next task? I couldn't see a simple way to bind the results of a temporary error to the container values.<br>
<br>Thanks and have a good new year,<br><br>-Alex<br></span>