Skip to main content
Question

How are Work task linked to code parts

  • December 2, 2025
  • 2 replies
  • 19 views

Forum|alt.badge.img+6

We see that when we use one of the code part named as work task, it validates the actual work task, we are not using work task for all entity. But when we try to save any supplier invoice with work task from code part value it checks the Work task sequence on work tasks without considering the company/site logic. Is this standard application behavior? Do we have any possibility to remove the mapping for Work tasks and code part? if yes where can we do that?

2 replies

Forum|alt.badge.img+19
  • Superhero (Employee)
  • December 3, 2025

Hi, 

Generally speaking, code parts / code part values are financial representations of operational data. This is not a firm / fixed link from an attribute (work task) to a code part. 

Code parts are user defined.  Only the account code part (A) is mandated.   So… Obviously someone associated with Finance set up, chose to define work task, as a code part.   IMO it would be extremely rare to have a need / solution where work task was a code part.  Type of work can be a code part, then you would use some flavor of control types to populate the finance interpretation of type of work, via posting controls.   If the expectation was to copy the actual IFS work task ID to the Finance code part as a code part value, first the work task numbers would need to be entered as code part values.  Then you need some mechanism (posting control and control type) that interprets (derives) the finance code part value from the work task. Pre-posting is probably the only option for that scenario. 

What is the real need / desired outcome?  

Best regards, 

Thomas


Forum|alt.badge.img+6
  • Author
  • Sidekick (Partner)
  • December 4, 2025

Hi, 

Generally speaking, code parts / code part values are financial representations of operational data. This is not a firm / fixed link from an attribute (work task) to a code part. 

Code parts are user defined.  Only the account code part (A) is mandated.   So… Obviously someone associated with Finance set up, chose to define work task, as a code part.   IMO it would be extremely rare to have a need / solution where work task was a code part.  Type of work can be a code part, then you would use some flavor of control types to populate the finance interpretation of type of work, via posting controls.   If the expectation was to copy the actual IFS work task ID to the Finance code part as a code part value, first the work task numbers would need to be entered as code part values.  Then you need some mechanism (posting control and control type) that interprets (derives) the finance code part value from the work task. Pre-posting is probably the only option for that scenario. 

What is the real need / desired outcome?  

Best regards, 

Thomas

Thanks for this answer, I was able to identify that it was a customization which was linking this. Just wanted to be sure that I am not missing anything new on IFS cloud. Thanks ​@Thomas Peterson