Skip to main content
Answer

Background Job Message

  • August 3, 2021
  • 3 replies
  • 130 views

Forum|alt.badge.img+8

We recently ran across this backgound job message and I am not familiar with it.

 

COMPANY101PROJECT_IDADSCDORCHEEXCLUDED_STATUS1 EXCLUDED_STATUS2 EXCLUDED_STATUS3 SUB_PROJECT_IDACTIVITY_SEQ

 

Any help is appreciated!

Best answer by Dumeesha Wanigarathna

Hi @Tenecia.Seeley ,

 

This background job is from Project side. However I have done a bit if knowledge search and noted below information from one of a bug description -  bug 145168

The given database procedure (Activity_Element_API.Upsert_Refresh_Data) is called when we do RMB > Copy Sub Project . This procedure updates the summary data (the data displayed in Cost, Revenue, Hours tabs in Activity/Sub Project/Project levels in Project Navigator). Since this is more time consuming the above bug has done changes to  update summery data as a background job. 

 

Therefore I believe this background job was created from that. You may check whether you have performed that kind of action (copy sub project) in your environment.

This topic has been closed for replies.

3 replies

Dumeesha Wanigarathna
Superhero (Partner)
Forum|alt.badge.img+16

Hi @Tenecia.Seeley ,

 

It is good if you can add a screen print of the background job. You have added only the parameter set. We cannot get any clue from that to answer


Forum|alt.badge.img+8
  • Author
  • Do Gooder (Customer)
  • August 3, 2021

 


Dumeesha Wanigarathna
Superhero (Partner)
Forum|alt.badge.img+16

Hi @Tenecia.Seeley ,

 

This background job is from Project side. However I have done a bit if knowledge search and noted below information from one of a bug description -  bug 145168

The given database procedure (Activity_Element_API.Upsert_Refresh_Data) is called when we do RMB > Copy Sub Project . This procedure updates the summary data (the data displayed in Cost, Revenue, Hours tabs in Activity/Sub Project/Project levels in Project Navigator). Since this is more time consuming the above bug has done changes to  update summery data as a background job. 

 

Therefore I believe this background job was created from that. You may check whether you have performed that kind of action (copy sub project) in your environment.