Codeunit 1611 "Exp. Sales CrM. PEPPOL BIS3.0"
Base Application · Microsoft.Sales.Peppol
Across versionsobsolete pending since 29.0
- BC23-28present
- BC29declaration changed
- BC30unchanged
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.Sales.Peppol · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| TableNo | Record Export Buffer |
| ObsoleteState | Pending |
| ObsoleteTag | 29.0 |
| ObsoleteReason | Replaced by PEPPOL App |
Procedures
GenerateXMLFile(VariantRec: Variant; var OutStr: OutStream): Generates an XML file in PEPPOL BIS 3.0 format for the sales credit memo.
Triggers
OnRun
Relations
- runs on Table 62 “Record Export Buffer”
Calls
From the extracted call graph of BC29 (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.
- Codeunit 1620 “PEPPOL Validation” (1 call:
OnRun → CheckSalesCreditMemo)
Deprecations
- object: Pending 29.0 (#if not CLEAN29), “Replaced by PEPPOL App”
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 BC29 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: "codeunit", object_name: "Exp. Sales CrM. PEPPOL BIS3.0"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.