Symptom
In SM37, jobs in "Released" status are not executed in the scheduled date because they never change into 'Ready' status.
The following entries are created in developer traces on ST11:
L MAKE_TBTCY: ATTENTION: TBTCY already exists <job name> <job ID>
L MAKE_TBTCY: ATTENTION: TBTCY already exists <job name> <job ID>
L MAKE_TBTCY: ATTENTION: TBTCY already exists <job name> <job ID>
Also, in SM65 -> Goto -> Consistency Check -> The following information will appear:
==> No matching entry found in TBTCO for following TBTCY entries:
<job name> <job ID>
<job name> <job ID>
<job name> <job ID>
Read more...
Product
Keywords
SM37, TBTCY, Inconsistencies, System refresh. , KBA , BC-CCM-BTC-RUN , Runtime Environment for Background Processing , Known Error
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.