IF_INBOUND_EXIT_BCS gives smtp undeliverable message intermittently .

[Former Member]

Hello All,

We have implemented code in create_instance and process_inbound meathod's of IF_INBOUND_EXIT_BSC for handling certain business scenarios. Although the business functionality is executed completely sometimes the person approving or rejecting the work item receives undeliverable email back from SAP. Below is a sample email which we have received:

Your message did not reach some or all of the intended recipients.

Subject: Rejected-XXXXXXXXXXXXX

Sent: 8/27/2009 9:38 PM

The following recipient(s) cannot be reached:

XXXXXXXXXXX on 8/27/2009 9:38 PM

The e-mail system was unable to deliver the message, but did not report a specific reason. Check the address and try again. If it still fails, contact your system administrator.

< XXXXXXXXXXXXX #5.0.0 SMTP; 554 Cannot process message in SAP System>

As said earlier in all cases the business transaction, either approval or rejection of the work item is completed in SAP but users "mostly" still get above emaill .

I have reviewed the code in the meathod process_inbound and the developer is essentially calling SWE_EVENT_CREATE function module followed by a COMMIT WORK based on business scenario. I almost want to say that problem is not in the custom code because else we would have received this error every time.

We activated a trace and after certain lines found following error:

08/27/2009 21:37:35 if_smtp_extension~handle_request G Inbound Processing Terminated with Errors. Exact Error:

08/27/2009 21:37:35 if_smtp_extension~handle_request G An exception with the type CX_OS_OBJECT_NOT_FOUND occurred, but was neither hand

08/27/2009 21:37:35 if_smtp_extension~handle_request G led locally, nor declared in a RAISING clause

Looked the the meathod if_smtp_extension and we have standard SAP code.

Has anyone else faced this issue and/or has ideas what can be tried?

Thanks

[njpennington]

Hello,

I am getting the same intermittent response even though the inbound message seems to be processed correctly.

Did you ever find out what the issue was and how to resolve it?

Thanks in advance.

Nick

[njpennington]

Solve it.

Just make sure you Catch the appropriate Exception classes after your main processing :

E.g

• system error

CATCH cx_os_object_not_found

cx_alert_recipient_unknown

cx_document_bcs

cx_send_req_bcs

cx_address_bcs.

endtry.

[njpennington]

False alarm. No it didn't resolve it.