Skip to main content
Solved

Script Cost update for Inventory Part

  • November 3, 2021
  • 1 reply
  • 210 views
C
Superhero (Customer)
Forum|alt.badge.img+17

Hello All, 

I am curious if it is possible to script a cost value update from one site to another? Currently we have a production site and an estimating site. The estimating site has a copy of our component parts, which we use to create customer quotations. The issue we face is that part 12345 in the production site may change from $5 to $7, but the PN 12345 in the estimating site is not updated, unless the user manually updates the cost. 

Is it possible to create a scheduled task to routinely perform an update from the production to estimating to keep the costs identical? Thank you!

Best answer by ShawnBerk

Yes, we do this via migration jobs. 

We do a similar costing update between a main service distribution site and hub sites that are for field inventory.  We have a nightly migration job to look for new parts and costs from the main site, download as an extract then upload via a different migration job to the other sites to the estimated material cost.  Altogether, it is something like 3 migration jobs for down, update to a table, upload to the other site, then several scheduled tasks to kick off the migration jobs and another to do a weekly cost calculation on the hub sites to keep the standard cost updated.

We have other versions that are script driven when a new cost is added and a sales part is created in one site, it sends the parts to sister sites to set them up, cost them and create the sales part info.  That version is more complex but also possible.

Out of the box a single SDT to do what you want however is not really possible, too many parameters to track really.

View original
Did this topic help you find an answer to your question?
This topic has been closed for comments

1 reply

S
Superhero (Customer)
Forum|alt.badge.img+28
  • ShawnBerk
  • Superhero (Customer)
  • 1482 replies
  • Answer
  • November 3, 2021

Yes, we do this via migration jobs. 

We do a similar costing update between a main service distribution site and hub sites that are for field inventory.  We have a nightly migration job to look for new parts and costs from the main site, download as an extract then upload via a different migration job to the other sites to the estimated material cost.  Altogether, it is something like 3 migration jobs for down, update to a table, upload to the other site, then several scheduled tasks to kick off the migration jobs and another to do a weekly cost calculation on the hub sites to keep the standard cost updated.

We have other versions that are script driven when a new cost is added and a sales part is created in one site, it sends the parts to sister sites to set them up, cost them and create the sales part info.  That version is more complex but also possible.

Out of the box a single SDT to do what you want however is not really possible, too many parameters to track really.

H
1 person likes this
  • H
    Hashini Kodippili
Terms & ConditionsCookie settings

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