web
You’re offline. This is a read only version of the page.
close
  • Same batch selection should be possible for BOM/Formula-lines too

    in one of our customer projects we have the following requirement: Item A = Finished good Batch number tracked Item B = Semifinished good Bacth number tracked (Product type = Formula) Item A has Item B as a BOM-line Some customers require, that they only want to receive one unique Batch for Item A (no Problem activating "Same batch selection" in the associated Item model group for Item A) but now - and that's the question - the semifinished good (Bulk) must have even one unique Batchnumber Here is the Link to the Yammer Post https://www.yammer.com/dynamicsaxfeedbackprograms/#/threads/show?threadId=538746187153408

  • Project management and accounting/Setup/Line properties/Line Properties

    For each Line property you can decide if it is Chargebale Yes or NO - using a Line property in order type "Item requirement" system changes to status invoiced as soon as the delivery has been taken in full. However using the order type "order" for a project related order and delivery has been taken in full, the status of the appropriate Line is "Delivered" - and as it is per design, Lines with Line property Chargeable "No" will not appear in an invoice proposal - so those lines (and even the whole Sales order) will remain in Status delivered in all eternity! The system should handle the property line exactly the way Chargebale Yes (Invoice proposal necessary to change status to Invoiced) Chargeable NO (with delivery status changes to Invoiced) not regarding which Order type was used for the appropriate Project order - please correct it to that behavior otherwise the radio button Chargeable YES/NO does not make any sense at all. Important to know: I raised therefore a support request #2012110050000556 however Microsoft is in the opinion "It works as designed" - However in this case no Month closing/Year end closing will be possible because all those order lines will never get a financial date!
  • TMS Load Building Workbench & Load planning workbench - update orders/lines with Route dates to Confirmed ship date

    Using the Load Building Workbench to propose/create loads for a Scheduled Route and changing the 'Shipping date from' from the default value from the route to an earlier date, proposes the correct orders/lines, but doesn't update those orders/lines "Confirmed ship date" field once the load is created from the workbench. Same should be done using the Load Planning workbench.


    And here the Mail conversation with Nicole Gump

    Going further on – I select a scheduled route – doing this the “Shipping date to” is greyed out and it populates the shipping date of the scheduled route – using the field “Shipping date from” I can search for SO-Lines with an earlier shipping date – however if I do this I would assume, that after I create the Loads (Propose loads and then Create loads) system will bring back those shipping date to the according SO-Lines (Field “Confirmed ship date) but it does not! Please clarify your steps here. I’m assuming that after selecting the scheduled route, you are (1) entering/selecting an earlier date in the ‘Shipping date from’ field and (2) clicking “Propose loads”, expecting the system to return all SO lines within the new date range.

    HAU: Your assumptions are correct – and yes it works fine – but when I do accept the proposed loads, system generates the Load with the shipment date of the scheduled route – and that’s the point where I expected that the Shipment date of the scheduled route will be put back to the appropriate SO-Lines and as the Shipment dates of the Sales line do not match the Shipping date from the Load they should be stored in the confirmed shipping dates of the SO-Lines so that the next MRP will recognize the delay of delivery.[NG]: I believe this is a limitation of the current design as you referenced from Oleksiy below. As far as I can tell, this is neither on the Ideas portal or in the Engineering team’s backlog. You can try logging it as a bug for the product team to review, but I would also suggest creating an idea for it: Ideas List (dynamics.com).