cancel
Showing results for 
Search instead for 
Did you mean: 

Process Chain schedule changes switches on its own

Former Member
0 Kudos

Hello gurus...  I have a process chain that has been running on a weekly basis for over a year.  In this case, it should run Monday evening at 10pm.  Last month, it changed to Friday evening at 10pm without any user input.  I'm the only BW admin in our instance.  No one else would even know how to change it.  The schedule just changed.  I will also mention that nothing else is scheduled to run at that time so there should be no interference from another chain.  All of my process chains run Monday evening.

This has happened before but it was early on in my experience with BW and I thought I must have accidentally done something wrong.  Given that it has happened again, I don't think it's user error.  I looked in OSS but I'm not sure that I searched correctly.  I mostly get "how to"s about scheduling and other process chain functions.  Anyone have any solutions to preventing this?

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member215845
Active Participant
0 Kudos

Hello Micah,

You can get some clues as follows;

Check when the start process is scheduled for and which user is the job creator.  You can search in SM37 for "released" jobs with job name BI_PROCESS_TRIGGER.

Usually the user who schedules the process chain is the job creator. If the process chain is scheduled in the after import method then the BW background user is the job creator.

Best Regards,

Vincent

Former Member
0 Kudos

yes, it does create a new released job under the BW background user.  i still can't explain why the system would change the schedule on its own.  is it possible that the system gets confused after a long period of time and needs to be reset?

former_member215845
Active Participant
0 Kudos

Hello Micah,

If it creates a new job with those settings, then it sounds like the process chain was transported into the system with a new start time.  You could check in se03 using "Search for Objects in Requests/Tasks".

Best Regards,

Vincent

Former Member
0 Kudos

that's entirely possible.  however, the last time this process chain and it's components were transported in was a year ago.  also, i don't schedule loads in our dev environment.  i keep them on demand until they move to prod; then i schedule them appropriately.  any other thoughts?  should i just chalk this up to be the "ghost in the machine"?

Former Member
0 Kudos

Hi Micah,

The scheduling has changed abruptly means either it's due to a scheduler ( third party scheduling tool ) or due to transport.

You have mentioned that the last transport was not happened recently and you didn't mentioned that you have employed any scheduling tool for process chain running.

I would suggest you to create a copy chain in your production environment and create a new scheduling for this new chain.

Br,

H

Former Member
0 Kudos

we don't use a 3rd party tool and there hasn't been a transport on any of the objects associated with this chain since 2011 so i'm not sure what to do.

thanks for your suggestions.  maybe there's some issue with the process chain itself.  if this happens again, i'll recreate it from scratch and transport to prod.

Former Member
0 Kudos

Hi Micah,

My suggestion is to create a process chain in prod environment itself, cos it can be modified in future if there is any need for it. Cos, these process chains can be deleted and re-created as and when required.

This will avoid redundant process chains in prod environment.

If you are doing it from dev, you have to delete it from dev and capture it in a tr and has to moved to higher environments which is really cumbersome.

Br,

H