Table 6102 "E-Document Header Mapping"

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

Properties

Property	Value
Access	Internal

Fields

Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

No.	Name	Type	Explanation	Notes
1	E-Document Entry No.	Integer	—	TableRelation Table 6121 “E-Document” (“E-Document”.“Entry No”); DataClassification SystemMetadata
2	Vendor No.	Code[20]	—	TableRelation Vendor.“No.”; DataClassification CustomerContent
3	Purchase Order No.	Code[20]	—	TableRelation Table 38 “Purchase Header” (“Purchase Header”.“No.” where(“Document Type” = const(Order))); DataClassification CustomerContent

Keys

PK: E-Document Entry No. (clustered)

Procedures

InsertForEDocument(EDocument: Record "E-Document")
GetEDocumentPurchaseHeader(): Record "E-Document Purchase Header" (internal)

Relations

Purchase Order No.: TableRelation Table 38 “Purchase Header”
E-Document Entry No.: TableRelation Table 6121 “E-Document”

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: "table", object_name: "E-Document Header Mapping"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.