Why IF_INBOUND_EXIT_BCS~PROCESS_INBOUND not called when email is received

简介: Sent: Mittwoch, 11. März 2009 04:44

Sent: Mittwoch, 11. März 2009 04:44

I just created a test class "ZTEST" in Q2Q, implemented both methods according to the document,

image.png


and I also do the needed configuration in tcode SCOT

image.png


And I write a report in Q2Q named ZOUTPUT1 to send a email ( attached with one PDF which can be uploaded in the report ) to my email address: jerry.wang@sap.com.


After I run the report, I did successfully get the email with PDF attached, but neither ZTESTIF_INBOUND_EXIT_BCSCREATE_INSTANCE nor IF_INBOUND_EXIT_BCS~PROCESS_INBOUND is called although the class is registered to my email address.


Why it is not called when email is received? Because I also find some SRM class in SCOT, so I guess the system should be working well.

There's a special way to debug these SAPConnect inbound processes and if you do not follow it you can not stop with a "normal" breakpoint, that you set before sending the mail.


Do the following instead

go to transaction SCOT enter 'dbg+' into the transaction field and press enter -> inbound process debugging is started

send the mail (in your case by starting your report)

go to transaction sm50 and search for the waiting process in class CL_SMTP_EXT_SAPCONNECT========CP to debug it (mark it and navigate to administration > program > debugging)

debugger opens and you can set breakpoint in your class, leave the endless loop by setting cursor to line 54 and press Shift+F12, let the debugger run with F8 and you will stop next in you class

debug whatever you want :)

!!! After finishing you have to stop inbound process debugging in scot again by entering 'dbg-' and pressing enter !!! (this can also already be done when you found your process in step 3)


相关文章
【已解决】kex_exchange_identification: Connection closed by remote host fatal: Could not read from
【已解决】kex_exchange_identification: Connection closed by remote host fatal: Could not read from
|
6月前
|
应用服务中间件 nginx Windows
[emerg] 15060#200: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket ......
[emerg] 15060#200: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket ......
179 0
|
6月前
|
Java Python
【已解决】RuntimeError Java gateway process exited before sending its port number
【已解决】RuntimeError Java gateway process exited before sending its port number
284 0
|
12月前
|
Docker 容器
Bind for 0.0.0.0:8080 failed: port is already allocated
Bind for 0.0.0.0:8080 failed: port is already allocated
508 0
|
消息中间件 网络架构
OpenStack报错:MessagingTimeout: Timed out waiting for a reply to message ID
OpenStack报错:MessagingTimeout: Timed out waiting for a reply to message ID
1368 0
|
网络协议
Job for named.service failed because the control process exited with error code.
Job for named.service failed because the control process exited with error code.
794 0
|
网络协议 Java
filebeat:Failed to publish events caused by: write tcp 5044: write: connection reset by peer
filebeat:Failed to publish events caused by: write tcp 5044: write: connection reset by peer
643 0
filebeat:Failed to publish events caused by: write tcp 5044: write: connection reset by peer
|
网络协议
Job for named.service failed because the control process exited with error code.怎么解决
本篇内容记录了如何解决Job for named.service failed because the control process exited with error code.的问题。
3565 0
Job for named.service failed because the control process exited with error code.怎么解决
|
Android开发
【错误记录】前台进程报错 ( Bad notification for startForeground invalid channel for service notification )
【错误记录】前台进程报错 ( Bad notification for startForeground invalid channel for service notification )
1398 0
【错误记录】前台进程报错 ( Bad notification for startForeground invalid channel for service notification )
oModel.create will also send to backend directly
Created by Wang, Jerry, last modified on Jun 02, 2016
110 0
oModel.create will also send to backend directly