Skip to main content
Question

Database Task Schedule - Recurring Service Request Generation - Service Delivery Unit


Forum|alt.badge.img+2

Hi,

We are trying to setup a Database Task Schedule for Recurring Service Request Generation.  We get a background job Error everytime we run the job.

The fault message is:

Argument SERVICE_DELIVERY_UNIT_ must have a value, because default value do not exist.    

Can’t get to the bottom of this issue.  We have a default Service Delivery Unit.

 

 

Screenshot of Database Task Schedule

 

Screenshot of background job

 

Should this be raised as a bug, or am I missing something.

 

Thank you,

Ed

5 replies

Alexander Heinze
Superhero (Employee)
Forum|alt.badge.img+23

I would file it as a bug. There were other places where the SDU was mandatory even though it shouldn’t be.


Forum|alt.badge.img+5
  • Do Gooder (Employee)
  • 35 replies
  • April 9, 2025

Hi, We have introduced the SDU as a parameter in the database schedule task from 25R1 onwards.

Best Regards,

Pubudika


Forum|alt.badge.img+7
  • Sidekick (Partner)
  • 57 replies
  • April 29, 2025

Hello ​@PubudikaW ​@Alexander Heinze, I have seen that there are two database tasks for request generation from recurring services. For the other one, there is the parameter for service delivery unit, but it doesn’t do nothing in my case. Do you know which is the difference between the database tasks? 

 


Forum|alt.badge.img+5
  • Do Gooder (Employee)
  • 35 replies
  • April 29, 2025

Hello ​@Iulia Petrin, in which environment are you experiencing this? I am unable to observe this in our RnD environments.

As far as I know, we introduced the Recurring Service Request Generation database task only.

 

/Pubudika


Forum|alt.badge.img+7
  • Sidekick (Partner)
  • 57 replies
  • April 29, 2025

Hello ​@PubudikaW, thank you for the reply. We just solved the issue. We used the database task from the screenshot below, changed the order of the parameters and then created a schedule for it and it worked. I find it strange, since we used the same parameters as before, but at least it worked..


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings