Creditmemo for an order that contains only one configurable product is not generated correctly

[leonhelmus]

Preconditions and environment

• Magento version 2.4.4
• php 8.1

Functionality to check if its the last creditmemo does not work correctly. It's a similar issue like:
#31143

Steps to reproduce

1. Add configurable product to cart
2. Create order
3. Create invoice
4. When refunding add some custom code to check if it is the last creditmemo.

When calling the function isLast() to check if this is the last creditmemo:
https://github.com/magento/magento2/blob/2.4-develop/app/code/Magento/Sales/Model/Order/Creditmemo.php#L562

It also checks the dummy items while this should be skipped. This is the same issue as described in #31143 same resolution also works for creditmemo.

Expected result

if all products of configurable are refunded it the function isLast() should return a true.

Actual result

if all products of configurable are refunded it the function isLast() should return a false, because of the dummy items.

Additional information

Patch to resolve the issue. Same resolution can be found here:
#31472

diff --git a/vendor/magento/module-sales/Model/Order/Creditmemo.php b/vendor/magento/module-sales/Model/Order/Creditmemo.php
--- a/vendor/magento/module-sales/Model/Order/Creditmemo.php	
+++ b/vendor/magento/module-sales/Model/Order/Creditmemo.php	(date 1673357465659)
@@ -563,6 +563,11 @@
     {
         $items = $this->getAllItems();
         foreach ($items as $item) {
+            $orderItem = $item->getOrderItem();
+            if ($orderItem->isDummy()) {
+                continue;
+            }
+
             if (!$item->isLast()) {
                 return false;
             }

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]

Hi @leonhelmus. Thank you for your report.
To speed up processing of this issue, make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

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.

⚠️ 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.

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant]

Hi @engcom-November. 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).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components 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-November]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @engcom-November. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @engcom-November, here is your Magento Instance: https://5beb5ba2d681cafd8b3ec0530ac4dbd7.instances.magento-community.engineering
Admin access: https://5beb5ba2d681cafd8b3ec0530ac4dbd7.instances.magento-community.engineering/admin_b691
Login: f7e58552
Password: 085ecc98b38f

[engcom-November]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @engcom-November. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @engcom-November, here is your Magento Instance: https://5beb5ba2d681cafd8b3ec0530ac4dbd7.instances.magento-community.engineering
Admin access: https://5beb5ba2d681cafd8b3ec0530ac4dbd7.instances.magento-community.engineering/admin_3b77
Login: 46169417
Password: b7601e9338d7

[engcom-November]

Verified the issue on Magento 2.4-develop instance and the issue is reproducible with the steps mentioned in the description. Hence confirming this issue.
The credit memo is not treated as the last one. function isLast() is returning false.

[github-jira-sync-bot]

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

[m2-assistant]

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

[github-jira-sync-bot]

❌ You don't have permission to export this issue.

[leonhelmus]

@engcom-November thanks for confirming the issue as soon as you did!

[hostep]

Closed without explanation why?

Probably fixed by BUG#7632: Creditmemo for an order that contains only one configurable product is not generated correctly