[
https://issues.apache.org/jira/browse/OFBIZ-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ean Schuessler updated OFBIZ-4173:
----------------------------------
Attachment: ean.vcf
I believe ORDERED is correct. My concern is that a sales order comes in,
a requirement is generated, the requirement becomes an order and that
order is later canceled. When a subsequent requirement comes in the
ORDERED requirement attached to the CANCELED order will be counted as if
it is going to change the ATP, which it will not.
Another possible solution is that canceling a PO with associated
requirements would change the associated requirement status to REJECTED
via an ECA. Would that make more sense?
--
Ean Schuessler, CTO
[hidden email]
214-720-0700 x 315
Brainfood, Inc.
http://www.brainfood.com> ATP requirement generation should look for ORDERED requirements attached to CANCELLED order items.
> --------------------------------------------------------------------------------------------------
>
> Key: OFBIZ-4173
> URL:
https://issues.apache.org/jira/browse/OFBIZ-4173> Project: OFBiz
> Issue Type: Improvement
> Components: order
> Reporter: Ean Schuessler
> Priority: Minor
> Attachments: ean.vcf
>
>
> The createATPRequirementsForOrder method currently subtracts any PENDING requirements from the amount needed to fulfill orders before creating additional requirements. It seems like it would also be useful for this method to look for ORDERED requirements that are associated with CANCELLED order items. This would prevent the system from generating additional requirements for stock that is actually available for allocation to new orders. Is there some kind of race condition or other problem I'm not seeing here?
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Locked
