Symptom
In SM37, jobs in the "Released" status are not executed on the scheduled date because they never change to the 'Active' status. The following entries are noted in the developer traces on ST11:
- MAKE_TBTCY: ATTENTION: TBTCY already exists <job name> <job ID>
- MAKE_TBTCY: ATTENTION: TBTCY already exists <job name> <job ID>
- MAKE_TBTCY: ATTENTION: TBTCY already exists <job name> <job ID>
Additionally, in SM65, navigating to Goto -> Consistency Check will show the following information:
==> No matching entry found in TBTCO for the following TBTCY entries:
- <job name> <job ID>
- <job name> <job ID>
- <job name> <job ID>
Read more...
Environment
ABAP Platform
SAP NetWeaver Application Server for ABAP
Product
Keywords
SM37, TBTCY, Inconsistencies, System refresh, cannot be locked, ENQUEUE_ESTBTCO, SAPLSENA, No free batch work processes available, batch jobs, SAPMSSY2 , 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.
SAP Knowledge Base Article - Preview