Skip to main content
Question

The value XXXX used for the code part Cost Cent is either missing, is a budget/planning code part value or has invalid time interval.

  • December 11, 2024
  • 2 replies
  • 187 views

Forum|alt.badge.img+1
  • Do Gooder (Customer)
  • 3 replies

We have an error on the posting lines of a work task transaction that we can not solve.

We closed a accounting project, and after a while we had to reopen it due to a guarantee claim. We opened it, created a new work order and task. We created a Purchase order, We registerd the arrival and the supplier invoice.

After that the transaction state is “Overtaken” but the posting lines that should be in Status=Valid are in Status =”Error”

The error is “The value XXXX used for the code part Cost Cent is either missing, is a budget/planning code part value or has invalid time interval.” But when we reopened the accounting project we modified the dates on the porject and also on the activity. 

We have run the task “Check and update Accounting”, We have run the task “RErun Erroneus Work Task Postings”  and the “Transfer Work Task Reposting Transactions”  but the error does not disapear.

Do you have any suggestion for us?

Lucía

2 replies

Forum|alt.badge.img+19
  • Superhero (Employee)
  • 1021 replies
  • December 11, 2024

Hi, 

The first place to look is - code part values screen.   Look for that cost center RT something. Check the valid from / valid until.   The data range must include the transaction date.  

If that’s the issue, change the dates, and perform the same steps you would do for fixing.  


Forum|alt.badge.img+1
  • Author
  • Do Gooder (Customer)
  • 3 replies
  • December 11, 2024

Hi Thomas,

Thanks for answering. Yes we have checked that screen, the values valid from/Valid until are correct. We chagned the valid until date when we reopened the accounting poject.

 

Regards,

Lucía


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