topic Re: Update Termination on BCST_SU in Application Development and Automation Discussions

Update Termination on BCST_SU

Former Member — Sun, 10 Jul 2011 03:57:18 GMT

Hi All,

We are running a Scheduled Background Job on a Batch User (MM) which deletes the Reservations and sends an email notification to concerned persons.

However, on thursday we observed that there was a UPDATE TERMINATION on this Job with a message DUPLICATE RECORD INSERTION INTO BCST_SU.

We observed that all the reservations have been successfuly deleted and there is nothing went wrong. This table BCST_SU is related to (BCS: Folder for Semantic and Technical SAP User Key).

I was wondering what is the use of this table BCST_SU and what it does?? and in what scenario it will have entires in it?

If someone can help me in understanding it, we may be able to analyse our UPDATE TERMINATION in a better manner.

Thank you all in advance for your help.

Cheers,

Lakshmi

Re: Update Termination on BCST_SU

Clemenss — Sun, 10 Jul 2011 12:28:30 GMT

Hi Lakshmi,

according to SAP notes 770038 and 1444380 it could be assumed that this error may have happened with a newly created user (check the dump for the record that caused the DUPLICATE RECORD error.

If your e-mail sending program uses outdated FM SO_DOCUMENT function module technology, if it sends more than one mail, if there is any parallel processing involved, may be that's a reason.

SAP note 1444380 recommends to start the report RSBCSTSU to prevent the termination from occurring in the case of users that have already been created.

Furthermore that note says about the table that when you send a message for the first time, the system writes data about the sender to the database that is then used at runtime by the Business Communication Service (BCS) for the administration of the SAPusers.

Regards,

Clemens

Re: Update Termination on BCST_SU

Former Member — Mon, 11 Jul 2011 04:56:35 GMT

Hi Clemens,

Thanks a lot for guiding me in Right Direction... Yes, these notes do point to the issue (I am still wondering why this happend only this time as we have this SAP BATCH USER set up a YEAR AGO) and we will try to implement them.

Hopefully, they will resolve the issue once and forever.

Thanks once again.

Lakshmi