Note: this idea is associated with case 2605060040005241

When you have intercompany return orders in a "created" state, they cannot be canceled when the in-between PO has a confirmation journal posted because this introduces a version history constraint. Since this transaction has no inventory or financial obligation currently, it seems this should be allowed. The ideal operation would be to cancel the original return order, and all downstream transactions would then be canceled. The current workaround is to disconnect the PO and intercompany return order, which then allows the original and derived return orders to be canceled independently.