Harden FR Factur-X test setup against orphaned VAT posting groups

[Copilot]

The FR unit test job was failing in Factur-X CII XML Tests before XML assertions ran. Test customer creation could inherit a VAT Bus. Posting Group code from shared test-library setup that did not exist in the FR test company.

• Problem

  • FacturXCIIXMLTests relied on shared library-created posting setup data being internally consistent.
  • In the failing environment, customer setup referenced a missing VAT Business Posting Group, causing customer validation/posting to fail across the entire Factur-X suite.

• Change

  • Added a small test-local guard in FacturXCIIXMLTests to ensure the referenced VAT Business Posting Group record exists before:
    • validating the customer’s VAT posting group
    • applying the G/L account’s VAT posting group during document setup
  • Extended test permissions to allow seeding the missing group record.
  • Seeded Description alongside Code so the inserted test record is minimally complete.

• Why here

  • This keeps the fix scoped to the failing FR test setup.
  • No production behavior changes; only the test codeunit is hardened against incomplete shared setup data.

• Example

  local procedure EnsureVATBusinessPostingGroupExists(VATBusPostingGroupCode: Code[20])
  var
      VATBusinessPostingGroup: Record "VAT Business Posting Group";
  begin
      if (VATBusPostingGroupCode = '') or VATBusinessPostingGroup.Get(VATBusPostingGroupCode) then
          exit;
  
      VATBusinessPostingGroup.Init();
      VATBusinessPostingGroup.Code := VATBusPostingGroupCode;
      VATBusinessPostingGroup.Description := VATBusPostingGroupCode;
      VATBusinessPostingGroup.Insert();
  end;