D365 Finance & Operations and Dynamics AX Forum

  • 1.  Production schedule

    Posted Sep 10, 2019 09:34 AM

    I am looking for some help with what we call our Production Schedule, this is a listing our production management team use so they know what parts they need to manufacture and for when. It is a spreadsheet that is updated through ODBC on a weekly basis. The report is basically a list of Sales orders (SO) with their due dates. We have sales orders for the same part that will multiple delivery dates e.g. SO1 is for 100 parts to deliver on 13/09/2019, SO2 is for 300 parts to deliver on 20/09/2019 and SO3 500 parts to deliver on 27/09/2019.

    To save time changing tooling on shopfloor machines our operations team would create a £0 value sales order on the system for 900 parts and create a works order for this Sales Order. This means on the Production Schedule the Production management can see that there is a "Corporate" order for 900 that will cover the 3 sales orders of 100, 300 and 500. Are you still with me.

    So what we have on the Production Schedule is 4 lines for the same part -
    • One line of zero value for 900 parts
    • One line for 100 parts with a cost per unit
    • One line for 300 parts with a cost per unit
    • One line for 500 parts with a cost per unit
    What this means though is that when the operations team report as finished some of the parts (e.g. 100 parts), they have to go to the zero value sales order and downgrade the 900 parts by 100 parts so that when the next production schedule is printed the production team can see there is still a works order for the remaining parts. This is a long winded and often human error causes issues but because I cannot link a works order for 900 parts to 3 separate Sales Orders I cannot think of another way of doing it that gives the Production management team the visibility they want.

    The additional lines for the "Corporate" orders also makes the Production schedule twice the size it needs to be.

    I appreciate this has been a bit of a story but if there are any clever people out there who can think of a better way of doing this then I will be forever in your debt. If you require anymore information please do not hesitate to contact me. We are moving from AX2009 to AX2012 R3.

    Fraser Kidd
    Livingston Precision Engineering (Ltd)

If you've found this thread useful, dive deeper into User Group community content by role