Sales order item table, qty_backordered not set for configurable products

[dverkade]

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.

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.

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”.

[m2-assistant[bot]]

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:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: 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.

[m2-assistant[bot]]

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: :point_down:

• [ ] 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]

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.

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.

[dverkade]

@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]

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.

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]

@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]

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.

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.

[github-jira-sync-bot]

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

[m2-assistant[bot]]

:white_check_mark: 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.

[engcom-Bravo]

Hi @dverkade,

Thanks for your reporting and collaboration.

We have tried to reproduce the issue in Latest 2.4-develop instance and the issue is still reproducible.Kindly refer the screenshots.

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.

[github-jira-sync-bot]

:x: Cannot export the issue. This GitHub issue is already linked to Jira issue(s): https://jira.corp.adobe.com/browse/AC-10862