A saved VAT Number is not displayed when placing an order by Admin on a Customer behalf

[github-jira-sync-bot]

Preconditions:

• Magento EE 2.4.0, EE 2.4.1-beta1 is installed
• A Customer without Billing and Shipping addresses is created
• Go to ther Magento Admin panel > CUSTOMERS > All Customers
• Select the created Customer
• Click the “Edit” link
• Click the “Addresses” vertical tab
• Click the “Add New Address” button
  Default Billing Address = Yes
  Default Shipping Address = Yes
  Street Address = 24 Grosvenor Square
  Country = United Kingdom
  City = London
  ZIP = W1A 1AE
  Phone Number = 1234567
  VAT Number 584451913
• Click the “Save” button
• Go to the Storefront as the created Customer > My Account > Address Book
• Make sure that the VAT Number value is displayed

(see the attached file EE 2.4.1-beta1.VAT ADRESSES STOREFRONT.png)

Steps to Reproduce:

• Go to Magento Admin panel again > SALES > Orders
• Click the “Create New Order” button
• Select the created Customer
• Scroll down the page to the “VAT Number” input field of the “Address Information” section

(/) Expected results:

“VAT Number” input fields of both Billing Address and Shipping Address should be filled with a previously entered value (584451913)

(x) Actual results:

“VAT Number” input fields of both Billing Address and Shipping Address are empty

(see the attached EE 2.4.1-beta1.VAT ADMIN ORDER.png)

[github-jira-sync-bot]

The issue was exported from the internal JIRA. The link to the original JIRA issue: https://jira.corp.magento.com/browse/MC-37657

[m2-assistant]

Hi @github-jira-sync-bot. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

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

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• 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, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

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

[m2-assistant]

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