Christine_Chavez_6412

SAP Job fails with BAPI_XBP_JOB_START_IMMEDIATELY in the job report

Discussion created by Christine_Chavez_6412 on Dec 16, 2016

You'll see the following in the job report: 
2016-12-14 09:52:43 - U02004058 Job 'MY_SAP_JOB' is duplicated, new RunID '0XXXXXXX' 
Immediate start not currently possible 
2016-12-14 09:52:43 - U02004081 Error in function 'BAPI_XBP_JOB_START_IMMEDIATELY': 'Immediate start not currently possible', Type: 'E', ID:'XM', number: '066' 2016-12-14 09:52:43 
This is an issue on the SAP side. The error EXM066 message is msg_no_immediate_start_poss. This suggests that you have a lot of SAP Control-M jobs on the SAP server, and your SAP box is out of process.

Per this article - http://ithowtoit.blogspot.com/2012/10/bapi-returned-exm066-immediate-start.html
You can either increase your SAP process or put your SAP job in ASAP (sap tab) in place of IMMEDIATE.

Please note: you will need to check with your SAP administrator as this error is outside Automic.

Outcomes