Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
Showing results for 
Search instead for 
Did you mean: 

eMail confirmation using BCS and SO_NEW_DOCUMENT_ATT_SEND_API1

Former Member
0 Kudos


we have used SO_NEW_DOCUMENT_ATT_SEND_API1 to send eMails to an external user. For confirmations we have used the flags NOTIF_DEL, NOTIF_READ and NOTIF_NDEL.

The confirmation settings in SCOT are activated.

So we are able to activate/deactivate the confirmation by setting or removing the flags from NOTIF_DEL, NOTIF_READ and NOTIF_NDEL. This works fine.

E.g. for external useres like vendors we need a confiramartion but for internal users we needn't a confiration.

If we set NOTIF_READ = 'X' we get a READ confirmation. If we set NOTIF_READ = space no confirmation is created. Perfect !!


Now we want to use BCS to send eMails. In this case we have problems with the confirmation. It doesn't work in the same way as it works using SO_NEW_DOCUMENT_ATT_SEND_API1.

We use cl_send_request_bcs=>create_recipient_from_soos1 and the flags ...-READ = 'X' and ...-DELIVER = 'X'.

Our problem is that we can not deactivate the confirmation e.g. it makes no difference if the READ flag is set or not.

But we need still the possibility to decide for which receiver we need a confirmation (vendor) and for which receiver we needn't a confirmation.

The next problem is uing distribution lists. We can us distribution list with BCS but we do not know how to set confirmation settings to a distribution list.




Former Member
0 Kudos

Call method "set_status_attributes" on your cl_bcs instance with the argument i_requested_status = 'E'. This will suppress the receipt confirmation for all recipients. I don't know of a way to set this per recipient under BCS.

0 Kudos

It works fine.