[16.0][ADD] purchase_line_receipt_status: Compute receipt status on purch… #2874
+1,198
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lmignon
force-pushed
the
16.0-add-puchase_line_receipt_status
branch
2 times, most recently
from
a3c1102 to
b314fa7
Compare
…ase order line In standard Odoo, the `purchase.order` model provides a `receipt_status` field to track the reception of purchase orders. This field is computed based on the associated pickings: - None: No pickings created or all pickings cancelled - `pending`: Not received yet - `partial`: Some pickings done - `full`: All pickings done (even if some are cancelled) However, there is **no equivalent status at the purchase order line level**. This module introduces the missing `line_receipt_status` field on purchase order lines, using the same logic as the standard PO `receipt_status`. It complements OCA modules such as `purchase_reception_status` without modifying their quantity-based logic. This module preserves the original picking-based status computation, ensuring consistency with Odoo’s standard behavior.
lmignon
force-pushed
the
16.0-add-puchase_line_receipt_status
branch
from
b314fa7 to
81e6fa4
Compare
lmignon
changed the title
1 task
luisDIXMIT
reviewed
Nov 17, 2025
Contributor
luisDIXMIT
left a comment
luisDIXMIT
left a comment
There was a problem hiding this comment.
I have 2 received lines, but the filter doesn’t seem to be working:
Is there something wrong, or am I missing something?
luisDIXMIT
reviewed
Nov 17, 2025
Contributor
luisDIXMIT
left a comment
luisDIXMIT
left a comment
There was a problem hiding this comment.
On the other hand, is this a substitute for purchase_reception_status_line? From my point of view, it looks like two different ways of doing the same thing.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…ase order line
In standard Odoo, the
purchase.ordermodel provides areceipt_statusfield to track the reception of purchase orders. This field is computed based on the associated pickings:pending: Not received yetpartial: Some pickings donefull: All pickings done (even if some were cancelled)However, there is no equivalent status at the purchase order line level. This module introduces the missing
line_receipt_statusfield on purchase order lines, using the same logic as the standard POreceipt_status.It complements OCA modules such as
purchase_reception_statuswithout modifying their quantity-based logic. This module preserves the original picking-based status computation, ensuring consistency with Odoo’s standard behavior.One may wonder about the formulation of possible values for the
line_receipt_statusfield. The semantics do not truly reflect the concept of auditing outstanding logistics operations. However, to maintain consistency with the standard field declared at the purchase order level and having the same meaning, I decided to keep the same values.