[
https://issues.apache.org/jira/browse/OFBIZ-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14365595#comment-14365595
]
Christian Carlow commented on OFBIZ-6163:
-----------------------------------------
Thanks Pierre,
You've confirmed as I discovered that shipmentReceipts are unnecessary for
sales shipments. However, the original reason for the creation of this issue
which is to relate returns to something representing a receipt still seems
necessary. After analysis, it seems the shipmentId can serve as the receipt.
Would you agree? I haven't had time to analyze the POS yet to see how it
generates order receipts. If shipmentId is used to represent a sales order
receipt, does it make sense to add shipmentId to the ReturnItem entity so that
returns always relate back to a receipt rather than the more general order
item. The issue is that ReturnItemBilling cannot be related back to a
shipGroupSeqId the way OrderItemBilling can because of its relation to
ItemIssuance.
> Create ShipmentReceipt for sales shipment during auto-invoice process
> ---------------------------------------------------------------------
>
> Key: OFBIZ-6163
> URL: https://issues.apache.org/jira/browse/OFBIZ-6163
> Project: OFBiz
> Issue Type: Improvement
> Components: accounting, product
> Reporter: Christian Carlow
>
> ShipmentReceipts seem to only be created for purchase shipments but are also
> needed for sales shipments. I propose adding functionality to automatically
> create ShipmentReceipts during the auto-invoicing functionality that happens
> when Sales Shipment statusId changes to PICKED or PACKED. It also seems more
> correct to base sales returns on the receiptId rather than the orderId,
> orderItemSeqId, and orderAdjustmentId. shipmentReceiptId already exists in
> OrderItemBilling but probably needs to be added to orderAdjustmentBilling
> also for handling adjustment returns as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
