• MRP should regard session date.

    In Dynamics AX 2012, we can run MRP regarding session date.

    [For investigation of mistake in the past]
    End users sometimes take mistakes.
    They had an experience of lost the order regarding the mistakes.
    Obviously, this was a critical issue for them.

    For preventing that situation, the root cause analysis is demanded.
    Using MRP in the past, they would like to investigate the issue.
    If the result of MRP is correct, user missed while confirming, shipping/receiving or invoicing order.
    If the result of MRP is incorrect, initial orders were wrong.

    For achieving the investigation, they would like to change the execution date of MRP as same as Dynamics AX 2012.

    [For future estimation]
    At same time, for the future date, the functionality is also useful.
    They can create rough plan of keeping resource in future with MRP if it regards session date.

  • MRP should solve the Delay with resource group

    We can set Quantity on Resource load in Route for using resources effectively.

     

    However, the setting is not sufficient for the scenario which has "peak" orders.

    For example,

    - 10 quantities are created per 1 day by 1 resource.

    - 1st April: 1 order with 3 quantities.

    - 2nd April: 1 order with 4 quantities.

    - 3rd April: 1 order with 4 quantities.

    - 4th April: 1 order with 100 quantities.

    - 5th April: 1 order with 4 quantities.

     

    For this scenario, there are no problem for 1st, 2nd, 3rd, 5th.

    But at 4th April obviously there are lack of resources.

    Then "Delay" was occurred for the order 4th April.

    For resolving "Delay", we need to modify the Route before running MRP.

    (Adding resources to the Resource group in Route and change Quantity on Resource load.)

    In this way, we can resolve Delay but we need "Re-modify" the Route to the old setting.

    It does not make sense as we always need to monitor the all of demand orders.

     

    The Idea:

    MRP should automatically solve the "Delay" using resources in Resource group.

    Or we should edit the Route manually in planned order after created by MRP.

  • LCS: Notification after planned maintenance window completed

    Regarding https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/lifecycle-services/planned-maintenance-window-faq?toc=dynamics365/unified-operations/fin-and-ops/toc.json
    Planned maintenance window are defined below. PlannedmaintenancewindowFAQ-FinanceandOperations,Enterprise|MicrosoftDocs

    • NAM: 2 AM to 10 AM
    • SAM: 12 AM to 8 AM
    • EMEA: 6 PM to 2 AM
    • CAN: 2 AM to 10 AM
    • APAC: 12 PM to 9 PM

    We can use the system after the window.

    But the notification after completing the maintenance should be announced.

    Because we need to wait until the maintenance window passed even if the maintenance already finished.

    For increasing the time to use system more, the notification which is sent to members after planned maintenance window completed, should be implemented.

  • Decimal for quantity should be changed regarding unit.

    All of decimal for quantity should be changed regarding unit. Example: Unit : ea or pcs -> no decimal Unit : kg -> has decimal Context: For example, we count 1, 2, 3... for book. We never count 1.00, 2.00 or 3.00. But in Dynamics 365 for Finance and Operations, all of fields for quantity has decimal. When the unit is pcs for an item, decimal for quantity of the item should be removed from display.
  • Decimal of Amount should be changed regarding currency

    For currency in Japan and Korea, it is not necessary decimal in Amount. Customers in Japan are familiar with entering amount without decimal. Decimal for Amount should be removed from display, regarding currency. Note: decimal is needed for prices. I mention only for Amount.