• State Verified Answer
  • Locked Locked
  • Replies 5 replies
  • Subscribers 94 subscribers
  • Views 7687 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

DB-Scheduler-Task vid_DBSchedulerTaskFill

Martin.Guckes
over 8 years ago

Hi there

i'm searching through the procedures to find the root cause of the calculation which changes Granted PWOs to Assigned PWOs. Yesterday PWOs which where ValidFrom 00:00 where assigned at 14:00

I found out out that the Procedure vid_DBSchedulerTaskFill which is used in vid_DBScheduler uses the view vi_DBSchedulerTaskView_0 to generate the viShoppingRackCheckValid, but i cannot find the cause why the Procedure VID_DBSchdulerTaskFill is called by the VID_DBScheduler. There has to be a defined ExecLevel but how the ExecLevel is set?

So what is the cause that PWO that are valid from 00:00 are not assigned at this time?

Thx in Advance,

Martin

Parents
  • 0 over 8 years ago

    Hi Andreas,

    i think the payload or eiter the DialogSchedules are for closing requests that has reached the validuntil-date or to Inform owners over closing  requests in the next xx days or requests that has to be approved.

    In my special case the requests are set to a validfrom-date in the future which was reached at 00:00 this day. In this special case i think the DBScheduler is the component which will handle this calculation.

    At this day the DB-Scheduler was very busy. So this was the main reason. But i would like to understand if this problem whas caused on the Sortorder of the tasks or if there is some kind of logic that will only create these kind of DB-QueueTasks if the DBQueue is empty. A look at the SQL shows some logic of the Variable ExecLevel. But i did/do not understand how this variable is handled/set. 

    So it would be nice to get a hint how this work to bring some light into Scheduler-darkness ;-)

    And 2nd more generic question: Is there any possibility to monitor the DBQueue-Calculations over a timeslot by default or either has anybody done this in a project and would like to share the experience.

    Version is 6.1.3.

    Thx.

Reply
  • 0 over 8 years ago

    Hi Andreas,

    i think the payload or eiter the DialogSchedules are for closing requests that has reached the validuntil-date or to Inform owners over closing  requests in the next xx days or requests that has to be approved.

    In my special case the requests are set to a validfrom-date in the future which was reached at 00:00 this day. In this special case i think the DBScheduler is the component which will handle this calculation.

    At this day the DB-Scheduler was very busy. So this was the main reason. But i would like to understand if this problem whas caused on the Sortorder of the tasks or if there is some kind of logic that will only create these kind of DB-QueueTasks if the DBQueue is empty. A look at the SQL shows some logic of the Variable ExecLevel. But i did/do not understand how this variable is handled/set. 

    So it would be nice to get a hint how this work to bring some light into Scheduler-darkness ;-)

    And 2nd more generic question: Is there any possibility to monitor the DBQueue-Calculations over a timeslot by default or either has anybody done this in a project and would like to share the experience.

    Version is 6.1.3.

    Thx.

Children
No Data