Share
Report
801The past several years we have had the same workflow for handling sales orders for special order items. The salesperson specifies a sales line with the proper Purchasing Code, and defines the Planned Delivery Date that the customer expects the order. These are pulled into new purchase orders via the Requisition Worksheet.
Over the weekend our BC SaaS environment updated to BC 28 for our sandbox environments, and to BC 27.5 for our production environment. Today we noticed a change in behavior. Previously, these created purchase orders were defined with Order Date in the header being the current work date. Which is expected. Now I was able to duplicate this change of behavior in any of these environments. Here is an example scenario:
- A sales order created on 5/26/2026 has a single sales line defined with the proper Purchasing Code and a Planned Delivery Date of 6/26/2026.
- The Requisition Worksheet pulls in this sales line and creates a new purchase order for it via Carry Out Action Message.
- The purchase order is defined with an Order Date of Planned Delivery Date - 1 day. In this case, the Order Date is 6/25/2026. It should be 5/26/2026.
- The purchase line is defined with the Expected Receipt Date of 6/26/2026, matching that of the linked sales line.
Is there a place to configure BC to honor the previous behavior? In that the purchase orders have Order Date values of current work date. I don't recall seeing any announced change like this in the "what's new" articles, although perhaps I didn't study them deeply enough.
Categories:
I have the same question (0)
All responses (
Answers (
