Sm37 job problem

[Former Member]

Hi Gurus,

We are facing one issue in sm37, one job SAP_CCMS_MONI_BATCH_DP is canceled at once every day at 1:00 am, then it ill will ran successfully. Please find the below Job log.

You can only work in client 333, 333 is our production client.

Daily we have seen this failure at same time.Could you please some comment on this.

Thanks,

[Former Member]

checked in 000 client.

[Former Member]

Hello Venkata,

From your Syslog entries, i think this job runs under 000 client with DDIC user.

I would suggest you to investigate more details in that particular time frame.

Do you have any ABAP dumps for this failure?

Thanks,

Best Regards,

Shyam Dontamsetty

[anindya_bose]

Hi

As already replied by others a particular instant ( job which is running at 1 .00 am) of that job is running in Client 000.

You can be sure by checking the Execution Client of that instant of the job. In SM37 job overview screen, Press Ctrl + F7 button

and then select from the Change Layout dialog box check "Client" and transfer it from "Hidden Fields" to "Line 1" , Press "Copy"

Now you can see on which client that particular job has run. Then for the just from the Scheduled / Released job cancel that next occurrence of the job ( only for 1 am)

[former_member1190121]

Hi,

This job some time starts client specific methods.Yuor job is scheduled in 000 client.

This job is trying to start method in 333 client.

You have delete this job from 000 cleirnt and schedule this in 333 client to correct this error.

Thanks.

Nagarjun.

[MartinMaruskin]

Seem you have to schedule this job to be run in different client what clients do you have available in your landscape?

[Former Member]

We have only one client that is 333. please find the sm21 log for the same.

Time Ty. Nr Cl. User Tcod MNo Text

00:21:03 BTC 034 000 DDIC D01 Transaction Canceled BRAIN 009 ( 333 )

etails

ecording at local and central time........................ 26.01.2010 00:21:03

ask................ 26994 / Background Processor No. 34

ser................ DDIC

lient.............. 000

erminal............

ession............. 1

ransaction code....

rogram name........ RSAL_BATCH_TOOL_DISPATCHING

roblem class....... K SAP Web AS Problem

evelopment class... SDYN

odule name.........

ocation............

100................ BRAIN 009

arameters..........

Documentation for system log message D0 1 :

The transaction has been terminated. This may be caused by a

termination message from the application (MESSAGE Axxx) or by an

error detected by the SAP System due to which it makes no sense to

proceed with the transaction. The actual reason for the termination

is indicated by the T100 message and the parameters.

Additional documentation for message BRAIN 009

You can only work in client &

No documentation exists for message BR009

thanks,

Venkat.

[MartinMaruskin]

Hi Venkat,

according your log it seems the job is running in client 000.

Client.............. 000

Kindly re-check how the job is setup. Especially that the job is suppose to be run in client 333.

BR

m./

[Former Member]

If you had system copy , that can be the reason

You can delete that scheduled job and then reschedule fresh. Check what happens.

[Former Member]

I would suggest you to check job log and SM21 log for that time slot. Information provided you is not sufficient to suggest you the solution.