Manufacturing and SKU

AlexWileyAlexWiley Member Posts: 230
Has anyone used or created a work around for using manufacturing with SKUs? I'm dealing specifically where the SKUs have different standard cost, so when it is made in location A it should cost $10 and when made in location B it should cost 15. Obviously this is not natively supported, but if someone has used a work around I would like to know if it is better than what we are currently doing. Thanks for the input, as always!

Comments

  • kiwilambkiwilamb Member Posts: 18
    Following up on an old post but has anyone been able to implement a solution for this requirement?
    I see that this functionality is still not available in the 2013 version.
  • AlexWileyAlexWiley Member Posts: 230
    kiwilamb wrote:
    Following up on an old post but has anyone been able to implement a solution for this requirement?
    I see that this functionality is still not available in the 2013 version.

    This came up again for a client last year and we created a solution that worked well. We moved all of the manufacturing related costing fields from the item card to SKU (overhead rate, etc), then modified the cost roll routine to calculate based on the SKU card, and finally changed the costing for the manufacturing to post the variance between actual and standard based on the standard cost on the SKU card not the item card.
  • Alex_ChowAlex_Chow Member Posts: 5,063
    kiwilamb wrote:
    Following up on an old post but has anyone been able to implement a solution for this requirement?
    I see that this functionality is still not available in the 2013 version.

    This function will be available in a near future release from what I'm told. How near is anyone's guess.
  • kiwilambkiwilamb Member Posts: 18
    Thanks for the two replies, sounds like the solution you've proposed should be taken on board by Microsoft. It sounds like a reasonably large modification to make, any idea of the time to do this and any learning’s?
  • AlexWileyAlexWiley Member Posts: 230
    kiwilamb wrote:
    Thanks for the two replies, sounds like the solution you've proposed should be taken on board by Microsoft. It sounds like a reasonably large modification to make, any idea of the time to do this and any learning’s?

    It's not too major, it should be less than 40 hours if you have a good developer. You may want to buffer some time for costing testing if the client isn't going to do it. Just keep in mind that you're not making any changes to the Adjust Cost Item Entries report.
Sign In or Register to comment.