error in Schedule Background Job for Deadline Monitoring of swu3

[Former Member]

While Auto Customization swu3 i am getting error message 'Output device "" not known' in 'Schedule Background Job for Deadline Monitoring'

Please advice what could be cause of it

[Former Member · Accepted solution]

Hi Prabhakar,

It seems that the thread link u gave is not very help full to me as it is related to working of workflow (work item ). in my case i am facing some issues with SWU3 the background related checks are red .

though the verification WF is working fine .

Thanks for your help but it did not worked .. please see if u can help me in this scenario ..

[martin_nooteboom · Accepted solution]

I have never encountered this error, but you could check if there is a wrong output device selected in your user-id (or the user executing SWU3) or in WF-BATCH.

Regards,

Martin

[Former Member]

output device of user wf-batch was changed

[Former Member]

the earlier problem of background job was solved by changing the output device assigned to user wf-batch .

regarding the transport request :

when i was trying to execute the step : "Schedule bakgrd for missed deadlines " MANUEL it was giving me an option of SAVE AND SCHEDULE . which was creating the transport request . but when i executed it automatically it worked fine without asking a request to me ... i don't know why )-: ... probablly we can specify a different interval then the standard of three minutes and which will be transported (it's just a guess) . i have executed it automatically ...

well thanks all for u r help

[Former Member]

so martin u mean that we will create a request and would not transport the request to another client (QAT & PRD) . instead go and run swu3 on all the client's .and leave the transport request as it is . or shal i ask the basis team to change their settings to not to create the request's in swu3 . can u advice from where we can change these settings

[martin_nooteboom]

Preferably I would change the settings. Basis will know where they are. If the setting is not changed Then create the transport and then delete afterwards.

Regards,

Martin

[KKilhavn]

Hmmm... now you got me curious, Martin. Why would you not release the transport that is created by customizing? As far as I recall it only includes information such as the prefix, so it shouldn't hurt importing it to all systems. But then again, my memory is a little rusty sometimes, so I may not recall everything that was included.

Perhaps Brajesh can tell us what gets included in the transport.

[martin_nooteboom]

Hi Kjetil,

The reason I said that is because he said he needed to create a transport request for the jobs. I have never encountered this, but I don't think this would work when you transport it. And because you still would have to execute SWU3 on the other clients I don't see a need to transport it. I agree with you that it shouldn't be a problem to import it, but as I have never done it I couldn't be certain.

But it would help if we knew what is in the transport.

Regards,

Martin

[Former Member]

HI Martin,

It helped me , it was due to the printer of user wf-batch .

i need some more help .

when i am executing step scheduling background jobs for missed deadlines it asks me for transport request . what i have heard is we need to run SWU3 on every client then what about these request .. if u want i will create another thread for it .. please advice

[martin_nooteboom]

Hi Brajesh,

Is this the only job which asks for a transport request? I think there is a setting done on the system which asks for transport requests for customizing or something. You do need to run SWU3 on every client and system, so I wouldn't transport the job.

Regards,

Martin

[Former Member]

yes user wf-batch is created properly and is not locked also .. no problems in RFC destination

[Former Member]

the verification mail worked fine but the steps

1) Schedule Background Job for Condition Evaluation

2) Schedule Background Job for Work Items with Errors

3) Schedule Background Job for Missed Deadlines

4) Schedule Background Job for Deadline Monitoring

are red and the reason for all is same : "Output device "" not known"

[former_member184112]

Hi,

Can you check the same question:

Thanks and Regards,

Prabhakar Dharmala

[former_member184112]

Hi,

Make sure User as WF-BATCH

Thanks and Regards,

Prabhakar Dharmala