Table 6105 "E-Document Line Mapping"

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

Properties

Property	Value
Access	Internal
DataClassification	CustomerContent

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	Specifies the entry number of the e-document.	TableRelation Table 6121 “E-Document” (“E-Document”.“Entry No”); DataClassification SystemMetadata
2	Line No.	Integer	Specifies the line number.	DataClassification SystemMetadata
3	Purchase Line Type	Enum “Purchase Line Type”	Specifies the type of entity that will be posted for this purchase line, such as Item, Resource, or G/L Account.	enum Enum 39 “Purchase Line Type”
4	Purchase Type No.	Code[20]	Specifies what you’re selling. The options vary, depending on what you choose in the Type field.	TableRelation Table 15 “G/L Account”, Table 5600 “Fixed Asset”, Table 5800 “Item Charge” (if (“Purchase Line Type” = const(” “)) “Standard Text” else if (“Purchase Line Type” = const(“G/L Account”)) “G/L Account” else if (“Purchase Line Type” = const(“Fixed Asset”)) “Fixed Asset” else if (“Purchase Line Type” = const(“Charge (Item)”)) “Item Charge” else if (“Purchase Line Type” = const(I…)
5	Unit of Measure	Code[20]	Specifies the unit of measure code.	TableRelation Table 204 “Unit of Measure” (Unit of Measure)
6	Deferral Code	Code[10]	Specifies the deferral code.	TableRelation Table 1700 “Deferral Template” (Deferral Template)
8	Shortcut Dimension 1 Code	Code[20]	Specifies the code for Shortcut Dimension 1, which is one of two global dimension codes that you set up in the General Ledger Setup window.	TableRelation Table 349 “Dimension Value” (“Dimension Value”.Code where(“Global Dimension No.” = const(1), Blocked = const(false)))
9	Shortcut Dimension 2 Code	Code[20]	Specifies the code for Shortcut Dimension 2, which is one of two global dimension codes that you set up in the General Ledger Setup window.	TableRelation Table 349 “Dimension Value” (“Dimension Value”.Code where(“Global Dimension No.” = const(2), Blocked = const(false)))
10	Item Reference No.	Code[50]	Specifies the item reference number.	TableRelation Table 5777 “Item Reference” (“Item Reference”.“Reference No.” where(“Unit of Measure” = field(“Unit of Measure”), “Variant Code” = field(“Variant Code”)))
11	Variant Code	Code[10]	Specifies the variant code.	TableRelation Table 5401 “Item Variant” (“Item Variant”.Code where(“Item No.” = field(“Purchase Type No.”)))
12	Dimension Set ID	Integer	—	TableRelation Table 480 “Dimension Set Entry” (Dimension Set Entry); not editable
50	E-Doc. Purch. Line History Id	Integer	Specifies the ID of the e-document purchase line history.	TableRelation Table 6140 “E-Doc. Purchase Line History” (“E-Doc. Purchase Line History”.“Entry No.”); DataClassification SystemMetadata

Keys

PK: E-Document Entry No., Line No. (clustered)

Procedures

InsertForEDocumentLine(EDocument: Record "E-Document"; LineNo: Integer)

Relations

Purchase Type No.: TableRelation Table 15 “G/L Account” (conditional)
Deferral Code: TableRelation Table 1700 “Deferral Template”
Unit of Measure: TableRelation Table 204 “Unit of Measure”
Shortcut Dimension 1 Code: TableRelation Table 349 “Dimension Value”
Shortcut Dimension 2 Code: TableRelation Table 349 “Dimension Value”
Dimension Set ID: TableRelation Table 480 “Dimension Set Entry”
Variant Code: TableRelation Table 5401 “Item Variant”
Purchase Type No.: TableRelation Table 5600 “Fixed Asset” (conditional)
Item Reference No.: TableRelation Table 5777 “Item Reference”
Purchase Type No.: TableRelation Table 5800 “Item Charge” (conditional)
E-Document Entry No.: TableRelation Table 6121 “E-Document”
E-Doc. Purch. Line History Id: TableRelation Table 6140 “E-Doc. Purchase Line History”
Purchase Type No.: TableRelation Table 7 “Standard Text” (conditional)

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 Line Mapping"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.