BC Observatoryunofficial, made by waldo
codeunitIntegration & APIsofficial - Microsoftderived - from the source, no model text

Codeunit 6130 "E-Doc. Shipment Export To XML"

EDocument · Microsoft.EServices.EDocument.Format

Open in Claude6130.mdSource on GitHub

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 1 connected objects and pages

Table 110 "Sales Shipment Header" (relates to)Sales Shipment Header

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.

EDocument · Microsoft.EServices.EDocument.Format · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
TableNo Sales Shipment Header

Procedures

  • GetShipmentXml(var TempBlob: Codeunit "Temp Blob") (internal): Gets the XML document as a temporary blob.
  • SetGeneratePDF(GeneratePDFValue: Boolean) (internal): Controls whether a PDF document should be generated and included as an additional document reference.

Plus 9 local procedures.

Triggers

OnRun

Relations

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: "E-Doc. Shipment Export To XML"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources