Skip to content

Conversation

@golja
Copy link
Contributor

@golja golja commented Dec 12, 2025

  • Ensure shipGroupSeqId is correctly set in context and passed to the template.
  • Display order items quantities for the selected ship group.
  • Make Order ID and Ship Group ID read-only fields and remove Shipment ID field in the Receive Against PO screen, because the screen is one of the sub-tabs of the shipment screen.
  • Add logic to filter shipment receipts by ship group, in order to properly display receive quantity in the Receive Against PO screen, in case of order items split into multiple ship groups.
  • Fix bug that causes creation of shipment receipt records with shipment id, but no shipment item sequence id

Explanation: various bugs were discovered when receiving an order item split into more than one ship group, by means of the Receive Against PO screen. The PR fixes those regarding the correct determination and visualization of quantities per ship group, e.g., 'order', 'received', etc.
There are still outstanding bugs in the trunk, such as the 'Force Complete Purchase Order' that still doesn't support order items split into multiple ship groups, wrong invoice creation, etc.

…ipment ID field in the Receive Against PO screen, because the screen is one of the sub-tabs of the shipment screen.
…to properly display receive quantity in the Receive Against PO screen, in case of order items splitted in multiple ship groups.
…shipment id, but no shipment item sequence id
@sonarqubecloud
Copy link

@JacquesLeRoux JacquesLeRoux changed the title Fix various bugs in receive against po Fixed: various bugs in receive against purchase orders (OFBIZ-13327) Dec 13, 2025
@JacquesLeRoux
Copy link
Contributor

I have created https://issues.apache.org/jira/browse/OFBIZ-13327 related to this PR

As I said there not sure there will be subtasks or not

This Jira issue is created as either an umbrella task with later subtasks or possibly a simple bugs fixes issues in relation with PR-932

@golja
Copy link
Contributor Author

golja commented Dec 13, 2025

Thank you, @JacquesLeRoux (Hi @gilPts !)

Let me know if you need any clarification on the changes.

Anahita

@JacquesLeRoux
Copy link
Contributor

Hi Anahita,

I tested the Receive Against PO screen and the result in the main order screen and I did not find any issues. I received respectively 8 on 10 (shipment 2) and 5 on 7 (shipment 1). Of course I did not use the 'Force Complete Purchase Order' as we known it's deficient.

I just want to mention that https://issues.apache.org/jira/browse/OFBIZ-9592 Paul is working on an enhancement of the main order screen. There should not be any interaction at this stage, just mentioning.

Copy link
Contributor

@JacquesLeRoux JacquesLeRoux left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That sounds OK with me to push

@golja
Copy link
Contributor Author

golja commented Dec 16, 2025

Hi Jacques,

thank you for the test and the review. And thank you for pointing out Paul's work.

Just so you know, I'm already working on fixing the 'Force Complete Purchase Order' button behavior and I'm almost done.
As soon as this pull request will be merged, I'll submit another PR for that fix.

Have a good day

Anahita

@golja
Copy link
Contributor Author

golja commented Dec 24, 2025

Hi @JacquesLeRoux,

do you know if @gilPts is willing to review the PR?

Thanks and happy holidays
Anahita

@JacquesLeRoux
Copy link
Contributor

Hi Anahita,

No I don't know. I guess he will get the message and answer himself. BTW, did you ask for his review or did he pick it himself?

Have fun too 😄 ❄️.

@golja
Copy link
Contributor Author

golja commented Dec 24, 2025

Hi Jacques,
I didn't request Gil's review. From the logs above it seems that you added him as a reviewer 2 weeks ago.
Anahita

@JacquesLeRoux
Copy link
Contributor

Thanks Anahita,

I guess I clicked on the wrong line then. I remove.

@JacquesLeRoux JacquesLeRoux removed the request for review from gilPts December 24, 2025 12:31
@JacquesLeRoux
Copy link
Contributor

Do you need more time before pushing this PR?

@golja
Copy link
Contributor Author

golja commented Dec 24, 2025

No, Jacques, thank you. I have already thoroughly tested the changes, and I am comfortable with them.

@JacquesLeRoux JacquesLeRoux merged commit 1100016 into apache:trunk Dec 25, 2025
7 checks passed
asf-gitbox-commits pushed a commit that referenced this pull request Dec 25, 2025
…932)

- Ensure shipGroupSeqId is correctly set in context and passed to the
template.
- Display order items quantities for the selected ship group.
- Make Order ID and Ship Group ID read-only fields and remove Shipment
ID field in the Receive Against PO screen, because the screen is one of
the sub-tabs of the shipment screen.
- Add logic to filter shipment receipts by ship group, in order to
properly display receive quantity in the Receive Against PO screen, in
case of order items split into multiple ship groups.
- Fix bug that causes creation of shipment receipt records with shipment
id, but no shipment item sequence id

Explanation: various bugs were discovered when receiving an order item
split into more than one ship group, by means of the Receive Against PO
screen. The PR fixes those regarding the correct determination and
visualization of quantities per ship group, e.g., 'order', 'received',
etc.
There are still outstanding bugs in the trunk, such as the 'Force
Complete Purchase Order' that still doesn't support order items split
into multiple ship groups, wrong invoice creation, etc.
aditya-kadiyala-nubes pushed a commit to aditya-kadiyala-nubes/ofbiz-master-copy that referenced this pull request Dec 29, 2025
…pache#932)

- Ensure shipGroupSeqId is correctly set in context and passed to the
template.
- Display order items quantities for the selected ship group.
- Make Order ID and Ship Group ID read-only fields and remove Shipment
ID field in the Receive Against PO screen, because the screen is one of
the sub-tabs of the shipment screen.
- Add logic to filter shipment receipts by ship group, in order to
properly display receive quantity in the Receive Against PO screen, in
case of order items split into multiple ship groups.
- Fix bug that causes creation of shipment receipt records with shipment
id, but no shipment item sequence id

Explanation: various bugs were discovered when receiving an order item
split into more than one ship group, by means of the Receive Against PO
screen. The PR fixes those regarding the correct determination and
visualization of quantities per ship group, e.g., 'order', 'received',
etc.
There are still outstanding bugs in the trunk, such as the 'Force
Complete Purchase Order' that still doesn't support order items split
into multiple ship groups, wrong invoice creation, etc.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants