Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics AX (Archived)

Postpone Action on Planned order

Posted on by 155

Can some one give an example in what Scenario i will get a Planned order with Action Postpone

*This post is locked for comments

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Postpone Action on Planned order

    Junaid Idrees I have just tried putting in advance & postpone margins but it doesn't seem to work? I've added in 7 to both fields to indicate I don't want messages within a week. I have only run MRP against those particular items rather than a full mrp run. Would this be the problem?

  • Suggested answer
    Junaid Idrees Profile Picture
    Junaid Idrees 12,746 on at
    RE: Postpone Action on Planned order

    Hi Nvbt,

    When we select "Postpone" message against any planned order (Purchase/Production), system generate action messages to move order to later date. We have "Postpone margin field", we can specify there maximum number of days between receipt and issue without postpone action to avoid generating message.

    For example: I dont want system to generate postpone message in which the difference between the supply and demand is 10 days or less.

  • nvbt Profile Picture
    nvbt 5 on at
    RE: Postpone Action on Planned order

    hi Yashpal,

    I agree with you, system should just create a new planned order on the action date rather than postpone a planned order

    It's a planned order so it's not a big deal if system deletes the old one and creates a new one

    None of the reponses answers your question

    Cheers

  • guk1964 Profile Picture
    guk1964 10,877 on at
    RE: Postpone Action on Planned order

    One factor is configuration i.e. you have the message turned on in the coverage group. Another configuration that affects this the In the "Futures message" fast tab, field  "Use futures date as requirement date."  This field automatically updates the requirement date of the planned order (which type of order depends on which of the fields you enable) to the futures date.. Negative and positive days and tie fences also affect whether messages are generated. for date related messages calendars and order dates, led times, and policies drive messages.

    In the mrp session log Master planning”–>”Setup”–>”Plans”–>”Master plans” and clicking the “Session log” button you can see the stages it goes through/ first it 'gets ready. basically to decide what needs to be planned ant ends up with records in the Reqtrans table.

    Next the coverage stage creates planned orders.based on Reqtrans.

    Then if Action messages are configured there is another phase to review whether the orders planned can be 'improved'.  The action messages are calculated in sequence after the planned orders are generated. It’s not until the action messages look at the whole requirement profile – planned orders included – that AX can see that it might make sense to change a planned order.  It may be that one message in isolation does not make sense, a cancel message for one planned order might trigger a postpone message on an another. 

    So in the session log you are looking at these steps:

    1. Preparation – meta data; consistency checks (BOM circularity; BOM level)
    2. Demand collection (updates) – transactions and collect demand (sales/safety stock/physical supply – on-hand/orders) direct demand + available supply
    3. Demand coverage (coverage) – matches supply and demand; creates planned orders to cover this demand; explosion; scheduling
    4. Delays calculation (futures) – reviews planned orders and calculate delays expected
    5. Actions –  creates recommendations
    6. Clean up – when run separately as a batch task (no impact on performance

    However, there is another twist to the tale, here are two ways to start MRP and they use different classes and depending on which you run you might get some differences in planned orders and messages. n case of Item MRP, the system calculates action/futures only for receipt net requirements which were actually used in the current MRP session (at least one record in coverage was created for these receipt net requirements). In case of Full MRP,  the system calculates action/futures for all net requirements which hves the same itemid+coverage dimensions combination as any of the requirement used in the current planning session. So we can expect different messages.

    • MRP from Master Planning->Periodic->Master planning; which is optimized for a multi-threaded scheduling of large number of net requirements
    • Master Planning->Periodic->Master planning  in Requirement Profile form. which is  optimized for ascheduling of only one item, and it has good caching mechanisms, so it might work much faster sometimes.

    Consider an item with four sales orders in the same period. Each sales order plans a production order. If the mrp policy is requirement, then a period policy of weekly or period might wan to group orders, but mrp will also see that some of the planned order supply is then ahead of demand.That then then blows sot many components each of which ma have different planning polices. Delete req trans and the last master plan and try some scenarios with different policies, different negative days etc in a test system look at the session log and the Explanation tab and the messages will then make more sense. 

    There have been several hotfixes in this region for example an old one is https://support.microsoft.com/en-us/help/2697476/reqpo-records-that-have-corresponding-reqtrans-records-are-created-dur

  • fpilotyash Profile Picture
    fpilotyash 155 on at
    RE: Postpone Action on Planned order

    Hi, thanks you for your response, i think i was not able to convey my issue properly.

    My question is , in what Scenario a Planned order (Not Actions), will have gave Action as Postpone

    pastedimage1565039443092v1.png

  • Suggested answer
    guk1964 Profile Picture
    guk1964 10,877 on at
    RE: Postpone Action on Planned order

    Action messages are generated by the master planning calculation in response to changed requirements.

    For example, the ship date or quantity may have changed on a sales order for which you have already created a purchase order to fulfill the demand. In this case, one or multiple action messages  generated by the master planning calculation.

    If there is mismatch between your demand date and a later dated planned supply because of lead time or other settings like a time fence, then mrp is advising that its done the best it can and that your order data and mrp planning rules/leadtimes are at odds, so based on the coverage settings it generates messages to advise the master scheduler who then needs to   either expedite the supply or to delay, i.e. to postpone, the demand, or just live with the fact his order promise will not be met because he prefers to se the actual requirement date to ensure the order is expedited.  

  • André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 291,280 Super User 2024 Season 2 on at
    RE: Postpone Action on Planned order

    Hi Yashpal,

    You can find a blog which explains a certain scenario: community.dynamics.com/.../master-planning-messages-in-dynamics-ax-2012

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,235 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans