You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Paul Foxworthy (JIRA)" <ji...@apache.org> on 2013/12/31 15:38:50 UTC

[jira] [Commented] (OFBIZ-5348) Add ability to edit and remove itemIssuances from shipments

    [ https://issues.apache.org/jira/browse/OFBIZ-5348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13859502#comment-13859502 ] 

Paul Foxworthy commented on OFBIZ-5348:
---------------------------------------

Hi Christian,

The quantity isn't an increment or decrement, it is the quantity that should be assigned to the shipment. If you enter a shipment, and then change the quantity to a lower amount, the issueOrderItemShipGrpInvResToShipment service recognises there has been a reduction.

See in particular the code at 

https://fisheye6.atlassian.com/browse/ofbiz/trunk/applications/product/script/org/ofbiz/shipment/issuance/IssuanceServices.xml?hb=true#to210

So I think it's OK.

Cheers

Paul Foxworthy

> Add ability to edit and remove itemIssuances from shipments
> -----------------------------------------------------------
>
>                 Key: OFBIZ-5348
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-5348
>             Project: OFBiz
>          Issue Type: Improvement
>    Affects Versions: Release Branch 12.04
>            Reporter: Christian Carlow
>
> Does anyone have a reason why itemIssuances should not be changed after being created?
> How are OrderItem quantities issued to shipments supposed to be corrected if entered incorrectly?
> If I issue 2 of an order item to a shipment but only meant to issue 1, how else would one go about correcting the issue quantity?
> Improving the Order Item page of the Facility -> Shipments app to allow negative quantities could provide issue correction functionality but then additional logic would be required to prevent canceling issue quantities of shipments already shipped.
> Anyone have any other ideas about how to solve this problem?



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)