Planned Purchase Order Delivery Date issue

(0) Share

Report

Posted on by Konrad U

804

We are running into an issue with changing the delivery date on planned purchase orders and wonder if there is anyway around it.

Three cases emerge. Two ok one ugh!

1. Changing the delivery date to the future on a vendor will advance the order date to the defined lead time. Good! We should not issue a purchase order before it is required.

2. Changing the delivery date moving it in will move the order date in as well in coordination with lead time. Good! We should order it earlier to get it in on time.

3. Changing the delivery date to a date that puts the lead time driven order date in the past changes the order date to today and recalculates the delivery date ignoring the delivery date we keyed.

Maybe...but it did save our delivery date it just does not show it, hitting refresh brings the keyed one back.

So how do we make this make sense? It clearly does not like case 3 but its change is ignored. It also gets the grid unhappy at times because it has unsaved changes when we change the delivery date and it changes the order date (twice) and resets the delivery date at lead time.

Any suggestions? I am not even sure what the behavior should be. Is there a setting to allow it to push dates in the past or have it not touch the order date?

Thanks!

KDU

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (0)

Konrad U 804 on at

Like (0)

Report

RE: Planned Purchase Order Delivery Date issue

Tim,

It is confusing. It does perform 2 updates. The first is the direct server side one in conjunction with the delivery date. It shows the changed date for a bit and it is in the database but when you move off the line the recalculate date routine takes place but it does not get saved however the new value the system assigns shows up. We usually get the Shift F5 to remove the change at that point.

Thanks for pointing out where the problem generates from. In code or otherwise it seems a pretty easy fix.

Konrad

Was this reply helpful? Yes No
Konrad U 804 on at

Like (0)

Report

RE: Planned Purchase Order Delivery Date issue

Steve,

Thanks for the heads up we will investigate that as well. From a perusal of all the issues in lifecycle services there is a lot of confusion about function and likewise in the code which bounces all over the place as well. I am still perplexed as to why they coded methods off of reqpo that simply return the YesNo value if No with no other code at all. It would seem to be better just to change or eliminate the calling code if the answer is known ahead of time.

In this case the lead times are setting pretty loose with the buyers expected to know the real lead times and manage the purchases accordingly. It could use a flag to emphasize a manual override. It would be frustrating to have a vendor on the phone agree to a delivery date and then have the system mess it up.

We also noticed that the same bug happens when grouping orders. If the system messes around with the dates the screen refresh with the revised order does not take place.

Konrad

Was this reply helpful? Yes No
Weaveriski 23,616 Moderator on at

Like (0)

Report

RE: Planned Purchase Order Delivery Date issue

Just to add to the fun we had a similar issue which you need to look at, which is what happens when you firm it after the change. We had the issue with CU10 (perhaps 9) that you altered the delivery date, it saved it, then you firmed it. The key was that you were firming within the lead-time (vendor confirms earlier delivery say). When you do this the header stores this date but the line recalculates and pushes it back out to the lead time.

This is the response we got:

I would like to confirm that Product team will not change this functionality in current version as escalated in Request for Hot fix:

TFS#3688805 - When Firming Planned purchase within with changed delivery date then delivery date is correctly update in header of PO but not in line

This issue was also registered by other partners but according to Product team it is intentional behaviour.

They state: "This has always been the intention. Firming code also has a method that is responsible to find the purchase price and this method reschedules the purchase order and this is what causes the date to be adjusted on the purchase order. This code hasn’t changed recently."

They advised us if we wanted it we should make the change in the code ourselves.

Was this reply helpful? Yes No
Tim Schofield on at

Like (0)

Report

RE: Planned Purchase Order Delivery Date issue

Hi Konrad, I agree it's a bug. I'm in the AX 2012 R 3 CU9 demo image. I see the behaviour you describe I the 'edit-in-grid' form when I change the delivery date to a date inside the lead time and simply click onto another record, but if I make the change and save and refresh the update is performed. Also if I click the edit button on the the planned order list page I can change the date without any problems.

In the master plan setup you have Futures message and Action message settings like 'Use Futures date as requirement date' in AX 2009 if this wasn't set your delivery date was set to your requirement date, and if the requirement date was inside your lead time then this meant that the order date was in the past. AX 2012 always seems to set the order date to today, and then sets a futures message on the planned order.

The edit in grid form shows the original requirement date though:

Was this reply helpful? Yes No
Konrad U 804 on at

Like (0)

Report

RE: Planned Purchase Order Delivery Date issue

Brandon,

I figured out the problem. It is bouncing a double update. It forces the delivery date on the client side to the server but then if the date is in the past it bounces the date forward again to the grid without committing. When you move to a new line it gets confused and wants the extra change backed out. I will check the hotfixes to see if they have addressed it. I already see some base changes that impact the grid and refreshing because of the attached methods surrounding planning.

Where did you configure to allow order dates in the past? I thought we had at one time and now forgot where it was.

Thanks

Konrad

Was this reply helpful? Yes No
Brandon Wiese 17,788 on at

Like (0)

Report

RE: Planned Purchase Order Delivery Date issue

What version of AX are you experiencing this issue on?

I was able to find more than a few hotfixes on LCS that relate to the delivery date on planned purchase orders. Which of them have you tried?

Using your description of the problem, I tried to reproduce it on AX 2012 R3 CU8, but was not able to. Specifically, when I hit Refresh the delivery date did not change in any scenario, but then my system is configured to allow orders dates in the past.

Was this reply helpful? Yes No