[
https://issues.apache.org/jira/browse/OFBIZ-13247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacopo Cappellato updated OFBIZ-13247:
--------------------------------------
Description:
In the Requirements tab, in the Order module when a purchase order is created
from an approved *product* requirement, it does not update the requirement’s
status from “Approved” to “Ordered,” even though the corresponding requirement
is linked to the purchase order. This bug creates confusion for procurement
teams who rely on the status to track order progress, forcing them to manually
verify PO creation. More critically, it disrupts the Material Requirements
Planning (MRP) engine as the system deflates the incoming quantity of the
product to be ordered.
For example, if the system has both: an approved requirement and a PO for an
item, and then a new sales order (SO) arrives. The MRP engine will assume that
the previous ‘approved requirement’ is supposed to fulfill the newly arrived
SO, thus failing to generate a respective new requirement for the SO. This
leads to incorrect inventory planning, as the system does not account for the
new item to be ordered via PO. Such conflicts cause inefficiencies, risks of
duplicate orders, stock shortages, and delayed workflows, especially in
high-volume manufacturing.
To fix this, the system should:
* Update the requirement status to “Ordered” the moment the purchase order
creation service runs.
* Preserve the existing commitment link between the requirement and the
purchase order.
* Reflect the status change accurately in the UI and database for reliable
tracking.
These changes will enhance visibility for procurement teams, reduce errors, and
streamline workflows.
was:
In the Requirements tab, in the Order module when a purchase order is created
from an approved internal requirement, it does not update the requirement’s
status from “Approved” to “Ordered,” even though the corresponding requirement
is linked to the purchase order. This bug creates confusion for procurement
teams who rely on the status to track order progress, forcing them to manually
verify PO creation. More critically, it disrupts the Material Requirements
Planning (MRP) engine as the system deflates the incoming quantity of the
product to be ordered.
For example, if the system has both: an approved requirement and a PO for an
item, and then a new sales order (SO) arrives. The MRP engine will assume that
the previous ‘approved requirement’ is supposed to fulfill the newly arrived
SO, thus failing to generate a respective new requirement for the SO. This
leads to incorrect inventory planning, as the system does not account for the
new item to be ordered via PO. Such conflicts cause inefficiencies, risks of
duplicate orders, stock shortages, and delayed workflows, especially in
high-volume manufacturing.
To fix this, the system should:
* Update the requirement status to “Ordered” the moment the purchase order
creation service runs.
* Preserve the existing commitment link between the requirement and the
purchase order.
* Reflect the status change accurately in the UI and database for reliable
tracking.
These changes will enhance visibility for procurement teams, reduce errors, and
streamline workflows.
> Update status of Requirement from “Approved” to "Ordered" when Purchase Order
> (PO) is created for that.
> -------------------------------------------------------------------------------------------------------
>
> Key: OFBIZ-13247
> URL: https://issues.apache.org/jira/browse/OFBIZ-13247
> Project: OFBiz
> Issue Type: Improvement
> Components: manufacturing, order
> Affects Versions: Upcoming Branch
> Reporter: Yashwant Dhakad
> Priority: Minor
>
> In the Requirements tab, in the Order module when a purchase order is created
> from an approved *product* requirement, it does not update the requirement’s
> status from “Approved” to “Ordered,” even though the corresponding
> requirement is linked to the purchase order. This bug creates confusion for
> procurement teams who rely on the status to track order progress, forcing
> them to manually verify PO creation. More critically, it disrupts the
> Material Requirements Planning (MRP) engine as the system deflates the
> incoming quantity of the product to be ordered.
> For example, if the system has both: an approved requirement and a PO for an
> item, and then a new sales order (SO) arrives. The MRP engine will assume
> that the previous ‘approved requirement’ is supposed to fulfill the newly
> arrived SO, thus failing to generate a respective new requirement for the SO.
> This leads to incorrect inventory planning, as the system does not account
> for the new item to be ordered via PO. Such conflicts cause inefficiencies,
> risks of duplicate orders, stock shortages, and delayed workflows, especially
> in high-volume manufacturing.
> To fix this, the system should:
> * Update the requirement status to “Ordered” the moment the purchase order
> creation service runs.
> * Preserve the existing commitment link between the requirement and the
> purchase order.
> * Reflect the status change accurately in the UI and database for reliable
> tracking.
> These changes will enhance visibility for procurement teams, reduce errors,
> and streamline workflows.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
