tableInventoryofficial - Microsoftderived - from the source, no model text

Table 5857 "Direct Trans. Line"

Base Application · Microsoft.Inventory.Transfer

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25-27unchanged
  4. BC2815 fields changed
  5. BC29-30unchanged

Neighbourhood 18 connected objects and pages

Table 14 "Location" (relates to, 2 links)LocationTable 349 "Dimension Value" (relates to, 2 links)Dimension ValueTable 7354 "Bin" (relates to, 2 links)Table 251 "Gen. Product Posting Group" (relates to)Gen. Product Posting GroupTable 27 "Item" (relates to)ItemTable 480 "Dimension Set Entry" (relates to)Dimension Set EntryTable 5401 "Item Variant" (relates to)Item VariantTable 5404 "Item Unit of Measure" (relates to)Table 5722 "Item Category" (relates to)Item CategoryTable 5740 "Transfer Header" (relates to)Transfer HeaderTable 94 "Inventory Posting Group" (relates to)Inventory Posting GroupPage 30211 "APIV2 - P. Dir. Trans. Lines" (pages and codeunits on it)Page 6782 "Posted Direct Transfer Subform" (pages and codeunits on it)Posted Direct Transfer SubformTable extension 20523 "Subc. DirectTrans. Line Ext" (extended by)Subc. DirectTrans. Line ExtCodeunit 20541 "Subc. Transfer WIP Posting" (event subscribers)Subc. Transfer WIP PostingCodeunit 20548 "Subc. DirectTransferLine Ext." (event subscribers)Subc. DirectTransferLine Ext.Codeunit 408 "DimensionManagement" (calls)DimensionManagementCodeunit 6503 "Item Tracking Doc. Management" (calls)

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.Inventory.Transfer · captioned “Direct Transfer Line” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Direct Transfer Line
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 Document No. Code[20] —
2 Line No. Integer —
3 Item No. Δ BC28 Code[20] Specifies the number of the item. TableRelation Table 27 “Item”
4 Quantity Δ BC28 Decimal Specifies how many units of the record are processed.
5 Unit of Measure Δ BC28 Text[50] Specifies the name of the item or resource’s unit of measure, such as piece or hour.
7 Description Δ BC28 Text[100] Specifies the description associated with this line.
8 Shortcut Dimension 1 Code Δ BC28 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)))
9 Shortcut Dimension 2 Code Δ BC28 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)))
10 Gen. Prod. Posting Group Code[20] — TableRelation Table 251 “Gen. Product Posting Group” (Gen. Product Posting Group)
11 Inventory Posting Group Code[20] — TableRelation Table 94 “Inventory Posting Group” (Inventory Posting Group)
12 Quantity (Base) Δ BC28 Decimal —
14 Qty. per Unit of Measure Δ BC28 Decimal —
15 Unit of Measure Code Δ BC28 Code[10] Specifies how each unit of the item or resource is measured, such as in pieces or hours. By default, the value in the Base Unit of Measure field on the item or resource card is inserted. TableRelation Table 5404 “Item Unit of Measure” (“Item Unit of Measure”.Code where(“Item No.” = field(“Item No.”)))
16 Gross Weight Δ BC28 Decimal —
17 Net Weight Δ BC28 Decimal —
18 Unit Volume Δ BC28 Decimal —
21 Variant Code Δ BC28 Code[10] Specifies the variant of the item on the line. TableRelation Table 5401 “Item Variant” (“Item Variant”.Code where(“Item No.” = field(“Item No.”)))
22 Units per Parcel Δ BC28 Decimal —
23 Description 2 Text[50] —
24 Transfer Order No. Code[20] — TableRelation Table 5740 “Transfer Header” (Transfer Header)
25 Posting Date Date —
29 Transfer-from Code Code[10] — TableRelation Table 14 “Location” (Location where(“Use As In-Transit” = const(false))); not editable
30 Transfer-to Code Code[10] — TableRelation Table 14 “Location” (Location where(“Use As In-Transit” = const(false))); not editable
31 Item Shpt. Entry No. Integer —
33 Item Rcpt. Entry No. Integer —
480 Dimension Set ID Integer — TableRelation Table 480 “Dimension Set Entry” (Dimension Set Entry)
5704 Item Category Code Code[20] — TableRelation Table 5722 “Item Category” (Item Category)
7300 Transfer-from Bin Code Δ BC28 Code[20] Specifies the code for the bin that the items are transferred from. TableRelation Table 7354 “Bin” (Bin.Code where(“Location Code” = field(“Transfer-from Code”), “Item Filter” = field(“Item No.”), “Variant Filter” = field(“Variant Code”)))
7301 Transfer-To Bin Code Code[20] — TableRelation Table 7354 “Bin” (Bin.Code where(“Location Code” = field(“Transfer-to Code”), “Item Filter” = field(“Item No.”), “Variant Filter” = field(“Variant Code”)))

Keys

  • Key1: Document No., Line No. (clustered)
  • Key2: Transfer Order No., Item No., Posting Date

Events published

Procedures

  • CopyFromTransferLine(TransferLine: Record "Transfer Line")
  • ShowDimensions()
  • ShowItemTrackingLines()

Relations

Pages and codeunits on this table

Extended by

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.

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: "table", object_name: "Direct Trans. Line"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources