Skip to main content
Question

Copy Costs to cost set one, cost message


Forum|alt.badge.img+1

Hello Community!
When copying costs to cost set one, IFS informs: “ Part not copied. Check calculation dates”. Which dates we must check? Via rightmousebutton we can click “check calculation date” but we are not able to solve out what happens. Any tips? (IFS9)

Forum|alt.badge.img+2
  • Do Gooder (Customer)
  • May 3, 2024

Hi,

You can check the Part Cost → Cost Message Log Tab to find the linked Parts which Copy Costs to Cost Set One process are not properly synchronized.


Forum|alt.badge.img+1
  • Do Gooder (Customer)
  • June 28, 2024

Hello
Our problem is that we have messages basically in all parts, and we can’t figure out the reason. We do not know what we are doing differently than earlier. We need to clarify what dates we should follow


Forum|alt.badge.img+14
  • Hero (Employee)
  • June 30, 2024

Hyvää päivää Päivi

 

Actually there is a small Cost Message log probem in Apps9 that has been fixed in Apps10 and later.

System does following check:

If the part has been calculated at a later date in another tree compared to the branch node it is currently looking at, and if that "later calculation" was copied into cost set one, then system will NOT:
- copy this node old calculation into PartCost
- and Not set a new inventory value

And it will create this Cost Message “Part Not Copied”

Okay

The problem in Apps9 is that we also create this warning message if it finds same component in a different tree (or another branch within the same tree) with SAME or later calculation date. And in most cases it is the same calculation date, and then system creates this message for you... and of course you get nervous. But in most cases there is no problem...

We don’t correct bugs in Apps9 anymore.

I assume this must be annoying for you.

 

Hope my comment helps to some extent.

Cheers,

Mats


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