BC Observatoryunofficial, made by waldo
codeunitSales & Receivablesofficial - Microsoftderived - from the source, no model textobsolete - pending

Codeunit 1602 "Export Sales Inv. - PEPPOL 2.0"

Base Application · Microsoft.Sales.Peppol

Open in Claude1602.mdSource on GitHub

Across versionsobsolete pending since 26.0

  1. BC23-25present
  2. BC26declaration changed
  3. BC27-28unchanged
  4. BC29-30not present

Neighbourhood 1 connected objects and pages

Table 62 "Record Export Buffer" (relates to)Record Export Buffer

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

Base Application · Microsoft.Sales.Peppol · BC23-28 · source at d6dc01d0 · facts from BC28

Properties

Property Value
TableNo Record Export Buffer
ObsoleteState Pending
ObsoleteTag 26.0
ObsoleteReason PEPPOL 2.0 is no longer supported.

Procedures

  • GenerateXMLFile(VariantRec: Variant; var OutStr: OutStream)

Triggers

OnRun

Relations

Deprecations

  • object: Pending 26.0 (#if not CLEAN26), “PEPPOL 2.0 is no longer supported.”

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

Ask your agent

Procedure bodies are not stored here (D10). For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "codeunit", object_name: "Export Sales Inv. - PEPPOL 2.0"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources