[E-Document Formats][OIOUBL] Migrate NAV PR 247162 into BCApps

[Groenbech96]

Migrates internal NAV PR 247162 (OIOUBL structured E-Document reader) into BCApps, mirroring ALAppExtensions #29056 (Invoice + CreditNote only). Follows the same pattern as the PINT A-NZ / Factura-E migration (#9426).

Changes

OIOUBL format (src/Apps/DK/EDocumentFormatOIOUBL)

• E-Document OIOUBL Handler (codeunit 13913) — new IStructuredFormatReader.ReadIntoDraft implementation parsing OIOUBL Invoice/CreditNote XML into the purchase draft staging tables (E-Document Purchase Header/E-Document Purchase Line). Vendor lookup via VAT reg. no., GLN, or PEPPOL participant id.
• OIOUBL EDoc Read into Draft (enumext 13911) — registers the handler on "E-Doc. Read into Draft".
• New test app (E-Document Format for OIOUBL Tests) with structured integration tests, validation codeunit and an OIOUBL invoice test resource.

E-Document Core (src/Apps/W1/EDocument)

• Grant internalsVisibleTo to the new OIOUBL test app.

Adaptations from the NAV source

• Uses the public E-Document PEPPOL Utility helper (BCApps) instead of NAV's EDocument XML Helper; View() uses temporary buffer records for the now-public SetBuffer.
• Test app depends on E-Document Core Tests; NAV's duplicate format-mock files (would clash with the existing 6160 "Mock" value) and NAV-only Eng/Core/Build registrations are not mirrored.

Verification

Every referenced type, field, procedure, enum value, namespace and object ID verified against main; implementation mirrors the already-merged PINT A-NZ handler pattern.

Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com

Work item

• Follow-up reminder support: AB#634900

[github-actions]

$\textbf{🟡\ Medium\ Severity\ —\ Style}$

Four namespace-URI Labels (CommonAggregateComponentsTok, CommonBasicComponentsTok, DefaultInvoiceTok, DefaultCreditNoteTok) are declared inside ReadIntoDraft's procedure-local var block instead of the codeunit's top-level var block. The sibling FacturaE and PINT A-NZ handlers in this same E-Document module declare their equivalent namespace-URI Labels (FacturaENamespaceTok, DigitalSignatureNamespaceTok, etc.) at object scope, which is the supported pattern for translation-pipeline discovery and reviewer visibility. Move these four Labels to the codeunit's top-level var block alongside GLNTok, InvoiceLineTok, and CreditNoteLineTok.

Knowledge:

• microsoft/knowledge/style/labels-declared-at-object-scope.md

_{👍 useful · ❤️ especially valuable · 👎 wrong - reply with why · AL review agent v1.13.4}

[github-actions]

$\textbf{🟡\ Medium\ Severity\ —\ Style}$

DKCVRTok is declared inside ParseAccountingSupplierParty's procedure-local var block instead of the codeunit's top-level var block, the same anti-pattern as the namespace Labels in ReadIntoDraft. Declare it at object scope alongside the codeunit's other Locked tokens (GLNTok, InvoiceLineTok, CreditNoteLineTok).

Knowledge:

• microsoft/knowledge/style/labels-declared-at-object-scope.md

_{👍 useful · ❤️ especially valuable · 👎 wrong - reply with why · AL review agent v1.13.4}

[github-actions]

$\textbf{🟡\ Medium\ Severity\ —\ Testing}$

In AssertPurchaseDocument, the Assert.AreEqual check compares PurchaseLine.Description against the literal 'Bicycle', but the failure message built by StrSubstNo reports the expected value as Item."No." instead of 'Bicycle'. If this assertion ever fails, the diagnostic message will show the wrong expected value, misleading whoever investigates the failure. This looks like a copy-paste artifact from the following line, which correctly uses Item."No." for its own comparison.

Recommendation:

• use 'Bicycle' as the third StrSubstNo argument, matching the value actually asserted.

Suggested change

	Assert.AreEqual('Bicycle', PurchaseLine.Description, StrSubstNo(MockDataMismatchErr, PurchaseLine.FieldCaption(Description), PurchaseLine.TableCaption(), Item."No.", PurchaseLine.Description));
	Assert.AreEqual('Bicycle', PurchaseLine.Description, StrSubstNo(MockDataMismatchErr, PurchaseLine.FieldCaption(Description), PurchaseLine.TableCaption(), 'Bicycle', PurchaseLine.Description));

_{Agent judgement — not directly backed by a BCQuality knowledge article.}

_{👍 useful · ❤️ especially valuable · 👎 wrong - reply with why · AL review agent v1.15.4}