[
https://issues.apache.org/jira/browse/OFBIZ-4540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14227484#comment-14227484
]
Divesh Dutta commented on OFBIZ-4540:
-------------------------------------
Verified this issue on latest OFBiz trunk. Followed following steps:
1) Created sales order taking GZ-BASKET-PICK product.
2) Then clicked on "Quick Ship Entire Order" button on Order view page to quick
ship the order
3) Order was completed successfully.
4) Checked OrderItem, ShipmentItem, OrderShipment, ItemIssuance tables. All the
records are created as per the expectation. i.e OrderItem that is a
MARKETING_PKG_PICK have N ShipmentItem rows, one for each of the products that
make up the bundle and multiple OrderShipment rows for the particular
orderId/orderItemSeqId are also created.
So this might be fixed under https://issues.apache.org/jira/browse/OFBIZ-4386
, as mentioned by Paul Foxworthy. So, we are good to close this issue. Thanks
Mohit Gupta for your research on this issue and sharing it with me.
> Item Issuance does not work with MARKETING_PKG_PICK order items
> ---------------------------------------------------------------
>
> Key: OFBIZ-4540
> URL: https://issues.apache.org/jira/browse/OFBIZ-4540
> Project: OFBiz
> Issue Type: Bug
> Components: order, party
> Affects Versions: Trunk
> Reporter: Craig Ambrose
>
> There is a problem when I "quick ship" an order that contains one or more
> MARKETING_PKG_PICK. I used the product in the eCommerce demo data,
> GZ-BASKET-PICK. When I submit the order and then do a "quick ship" I end up
> without an OrderShipment entity even though the OrderItemShpGrpInvRes rows
> are removed, the ItemIssuance rows are created, the OrderItem rows are marked
> completed and other data is affected.
> I believe the problem is with the "issueOrderItemShipGrpInvResToShipment"
> service. It doesn't seem to know that an OrderItem can represent multiple
> ShipmentItems and it tries to determine, wrongly, that the OrderShipment
> needs to be removed and will be replaced.
> What I expect to happen is that an OrderItem that is a MARKETING_PKG_PICK
> would end up as N ShipmentItem rows, one for each of the products that make
> up the bundle. And that would end up with multiple OrderShipment rows for the
> particular orderId/orderItemSeqId two-ple
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
