Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sales order item table, qty_backordered not set for configurable products #38319

Open
5 tasks
dverkade opened this issue Dec 27, 2023 · 9 comments
Open
5 tasks
Labels
Area: Product Component: DB Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: ready for dev Reported on 2.4.6-p2 Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch

Comments

@dverkade
Copy link
Member

Preconditions and environment

  • 2.4.6-p2

Steps to reproduce

  • Have a configurable product with simple products
  • Make sure the simple products allow backorders and do not have stock
  • Place an order in Magento
  • The qty_backordered field in the sales_order_item table is only set / filled for the simple products, while it's not set on the configurable product, see screenshot.
  • Other fields like qty_ordered, etc are set on the simple product as well as the configurable product.
    image

Expected result

The expected result is that the qty_backordered field is stored in the sales order item table for the configurable product as well.

Actual result

  • The qty_backordered field in the sales_order_item table is only set / filled for the simple products, while it's not set on the configurable product, see screenshot.
  • Other fields like qty_ordered, etc are set on the simple product as well as the configurable product.
    image

Additional information

No response

Release note

No response

Triage and priority

  • Severity: S0 - Affects critical data or functionality and leaves users without workaround.
  • Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
  • Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
  • Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
  • Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.
Copy link

m2-assistant bot commented Dec 27, 2023

Hi @dverkade. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:


Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

Copy link

m2-assistant bot commented Dec 27, 2023

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

  • 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
  • 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
  • 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
  • 4. Verify that the issue is reproducible on 2.4-develop branch
    Details- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
    - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
  • 5. Add label Issue: Confirmed once verification is complete.
  • 6. Make sure that automatic system confirms that report has been added to the backlog.

@engcom-Bravo engcom-Bravo added the Reported on 2.4.6-p2 Indicates original Magento version for the Issue report. label Dec 27, 2023
@engcom-Bravo
Copy link
Contributor

HI @dverkade,

Thank you for reporting and collaboration.

Verified the issue on Magento 2.4-develop instance and the issue is not reproducible.Kindly refer the screenshots.

Steps to reproduce

  • Have a configurable product with simple products
  • Make sure the simple products allow backorders and do not have stock
  • Place an order in Magento
  • The qty_backordered field in the sales_order_item table is only set / filled for the simple products, while it's not set on the configurable product, see screenshot.
  • Other fields like qty_ordered, etc are set on the simple product as well as the configurable product.

Screenshot from 2024-01-12 17-11-22

qty_backordered field is stored in the sales order item table for the configurable product as well.

Kindly recheck the behaviour on Magento 2.4-develop instance and elaborate steps to reproduce if the issue is still reproducible.

Thanks.

@engcom-Bravo engcom-Bravo added the Issue: needs update Additional information is require, waiting for response label Jan 12, 2024
@m2-community-project m2-community-project bot moved this from Ready for Confirmation to Needs Update in Issue Confirmation and Triage Board Jan 12, 2024
@dverkade
Copy link
Member Author

@engcom-Bravo , the screenshot doesn't show column names. However I see that the example only shows the "simple" product and not the configurable product as I have shown in my screenshot.

@engcom-Bravo
Copy link
Contributor

Hi @dverkade,

Thanks for your update.

Verified the issue on Magento 2.4-develop instance and the issue is not reproducible.Kindly refer the screenshots.

Steps to reproduce

  • Have a configurable product with simple products
  • Make sure the simple products allow backorders and do not have stock
  • Place an order in Magento
  • The qty_backordered field in the sales_order_item table is only set / filled for the simple products, while it's not set on the configurable product, see screenshot.
  • Other fields like qty_ordered, etc are set on the simple product as well as the configurable product.

Screenshot from 2024-01-16 14-16-04

Screenshot from 2024-01-16 14-15-06

It looks like an expected behaviour of Magento since we have enabled backorders for only child products of the configurable product so we will get data for only simple products,Could you please let us know if we are missing anything.

Thanks.

@dverkade
Copy link
Member Author

@engcom-Bravo It's not expected behaviour. If what you're saying is the case the other fields like qty_ordered, qty_invoiced, etc. should also only be set on the simple products. That's not the case, for those fields it's set for the simple as well as the configurable product. See my screenshot only the field "qty_backordered" is not set on the configurable product only on the simple product. It should be consistent all fields should populate on the simple as well as the configurable products.

@engcom-Bravo
Copy link
Contributor

Hi @dverkade,

Thanks for your update.

Verified the issue on Magento 2.4-develop instance and the issue is reproducible.Kindly refer the screenshots.

Steps to reproduce

  • Have a configurable product with simple products
  • Make sure the simple products allow backorders and do not have stock
  • Place an order in Magento
  • The qty_backordered field in the sales_order_item table is only set / filled for the simple products, while it's not set on the configurable product, see screenshot.
  • Other fields like qty_ordered, etc are set on the simple product as well as the configurable product.

Screenshot from 2024-01-18 11-47-01

Screenshot from 2024-01-18 11-47-22

The qty_backordered field in the sales_order_item table is only set / filled for the simple products, while it's not set on the configurable product.

Hence Confirming the issue.

Thanks.

@engcom-Bravo engcom-Bravo removed the Issue: needs update Additional information is require, waiting for response label Jan 18, 2024
@m2-community-project m2-community-project bot moved this from Needs Update to Ready for Confirmation in Issue Confirmation and Triage Board Jan 18, 2024
@engcom-Bravo engcom-Bravo added Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. labels Jan 18, 2024
@m2-community-project m2-community-project bot moved this from Ready for Confirmation to Confirmed in Issue Confirmation and Triage Board Jan 18, 2024
@m2-community-project m2-community-project bot added this to Dev In Progress in High Priority Backlog Jan 18, 2024
@github-jira-sync-bot
Copy link

✅ Jira issue https://jira.corp.adobe.com/browse/AC-10862 is successfully created for this GitHub issue.

Copy link

m2-assistant bot commented Jan 18, 2024

✅ Confirmed by @engcom-Bravo. Thank you for verifying the issue.
Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Product Component: DB Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: ready for dev Reported on 2.4.6-p2 Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch
Projects
High Priority Backlog
  
Ready for Development
Development

No branches or pull requests

3 participants