xmlportSales & Receivablesofficial - Microsoftderived - from the source, no model textobsolete - pending

XMLport 1600 "Sales Invoice - PEPPOL 2.1"

Base Application · Microsoft.Sales.Peppol

Across versionsobsolete pending since 26.0

  1. BC23-24present
  2. BC254 events added
  3. BC26declaration changed
  4. BC27-28unchanged
  5. BC29-30not present

Neighbourhood 2 connected objects and pages

Codeunit 6458 "Serv. PEPPOL Management" (event subscribers, 4 links)Serv. PEPPOL ManagementCodeunit 1605 "PEPPOL Management" (calls, 3 links)PEPPOL Management

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
Caption Sales Invoice - PEPPOL 2.1
ObsoleteState Pending
ObsoleteTag 26.0
ObsoleteReason PEPPOL 2.1 is no longer supported.

Events published

  • OnGetTotals(SourceRecRef: RecordRef; var SalesLine: Record "Sales Line"; var TempVATAmtLine: Record "VAT Amount Line" temporary; ProcessedDocType: Enum "PEPPOL Processing Type") + BC25 (integration)
  • OnInitialize(SourceRecRef: RecordRef; var ProcessedDocType: Enum "PEPPOL Processing Type"; var IsHandled: Boolean) + BC25 (integration)
  • OnFindNextInvoiceRec(Position: Integer; var SalesHeader: Record "Sales Header"; var Found: Boolean) + BC25 (integration)
  • OnFindNextInvoiceLineRec(Position: Integer; var SalesLine: Record "Sales Line"; var Found: Boolean) + BC25 (integration)

Procedures

  • GetTotals()
  • Initialize(DocVariant: Variant)

Plus 6 local procedures.

Calls

From the extracted call graph of BC28 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.

Deprecations

  • object: Pending 26.0 (#if not CLEAN26), “PEPPOL 2.1 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). The call sections above are our own, per object, from the BC28 call graph. 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: "xmlport", object_name: "Sales Invoice - PEPPOL 2.1"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources