Does anyone know why an otherwise fully fulfilled/...
# general
n
Does anyone know why an otherwise fully fulfilled/completed Sales Order will change it's header-level Status to 'Closed' if one outstanding line is closed? And if there is a way to resolve this?
s
Closed is the status that is used when one or more lines is closed
c
I guess your issue is now that you can't invoice it?
Anyway, the docs say what to do.
Copy code
Reopening a Closed Sales Order
If you close a sales order in error, you can reopen it.
To reopen a closed sales order:
1. On the sales order record, click Edit.
2. In the Closed column of any line item, click once to show the box, then clear the box.
3. Click Save.
The status of the sales order changes to Pending Fulfillment.
s
along the same line, how do you close Work Order? without the "Close Work order" transaction. I have users closing Work order but I don't even see the option to close the work order and when I ask them to reproduce they are like I don't know what I did.
n
Thanks @CD, though the issue is not re-opening the Sales Order. Maybe an unreasonable one, but the expectation is that if you have 1 line which completely unfulfilled and unbilled is closed (because retrospectively you find out you dont want it) and another which is fully fulfilled and invoiced. The sentiment is that the Order is "Complete", not "Closed". Yes, if you closed all lines you may say it was "Closed".
In the particular instance I have described I have been able to gain the outcome I was looking for by changing Quantity of the closed line from 1 to 0 - only then does the header-level Status change from "Closed" to "Fully Billed"
c
I guess they allude to it in the docs, but don't explicitly spell it out: "If you are going to manually close a partially fulfilled line item on sales order, you must bill the sales order BEFORE you close the line. When all line items on a sales order are fulfilled or closed manually, the sales order is removed from the billing queue and the receiving queue."
Agree that it's rubbish though! Especially if your downstream ETL is using the statuses