Added the company and VAT Number values at OPC address

[engcom-Charlie]

Description (*)

As mentioned in PR raised this new PR.

Now the company and VAT Number values are getting displayed at OPC address.

Related Pull Requests

magento/partners-magento2b2b#538

Fixed Issues (if relevant)

1. Fixes magento/magento2#<issue_number>
   Issue

Manual testing scenarios (*)

1. Set Store->Configuration->Customer Configuration->Name and Address Options->Show Company to 'Optional'
2. Set Store->Configuration->Customer Configuration->Create New Account Options->Show VAT Number on Storefront to 'Optional'
3. Save config
4. Run: bin/magento cache:clean
5. Open registration page /customer/account/create/
6. Create the customer with the company name and add VAT Number (admin->Customers->edit created customer->Addresses->Add/Update Address)
7. Add any product to the cart and go to the shipping step

Before: ✖️ Company name and VAT Id are not visible

After: ✔️ Company name and VAT Id are visible

Questions or comments

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
• All automated tests passed successfully (all builds are green)

[m2-assistant]

Hi @engcom-Charlie. Thank you for your contribution
Here are some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento give me test instance - deploy test instance based on PR changes
• @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

1. Database Compare
2. Functional Tests CE
3. Functional Tests EE,
4. Functional Tests B2B
5. Integration Tests
6. Magento Health Index
7. Sample Data Tests CE
8. Sample Data Tests EE
9. Sample Data Tests B2B
10. Static Tests
11. Unit Tests
12. WebAPI Tests
13. Semantic Version Checker

You can find more information about the builds here

ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.

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

⚠️ According to the Magento Contribution requirements, all Pull Requests 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 Pull Requests 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

[ishakhsuvarov]

Closing this for now as it seems abandoned.

Please feel free to reopen if needed.