Table 5854 "Invt. Shipment Header"

Base Application · Microsoft.Inventory.History · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Invt. Shipment Header
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
2	No. Δ BC28	Code[20]	Specifies the number of the involved entry or record, according to the specified number series.
3	Posting Description Δ BC28	Text[100]	Specifies any text that is entered to accompany the posting, for example for information to auditors.
5	Document Date Δ BC28	Date	Specifies the date when the related document was created.
6	Posting Date Δ BC28	Date	Specifies the entry’s posting date.
7	Location Code Δ BC28	Code[10]	Specifies the warehouse or other place where the involved items are handled or stored.	TableRelation Table 14 “Location” (Location.Code where(“Use As In-Transit” = const(false)))
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	Language Code	Code[10]	—	TableRelation Table 8 “Language”
11	Salesperson Code Δ BC28	Code[20]	Specifies the name of the salesperson who is assigned to the customer.	TableRelation Table 13 “Salesperson/Purchaser” (Salesperson/Purchaser)
12	Comment	Boolean	—	FlowField: exist(“Inventory Comment Line” where(“Document Type” = const(“Posted Inventory Shipment”), “No.” = field(“No.”))); not editable
14	No. Series	Code[20]	—	TableRelation Table 308 “No. Series” (No. Series); not editable
15	Posting No. Series	Code[20]	—	TableRelation Table 308 “No. Series” (No. Series)
16	External Document No. Δ BC28	Code[35]	Specifies a document number that refers to the customer’s or vendor’s numbering system.
20	Posting No.	Code[10]	—
23	Gen. Bus. Posting Group Δ BC28	Code[20]	Specifies the vendor’s or customer’s trade type to link transactions made for this business partner with the appropriate general ledger account according to the general posting setup.	TableRelation Table 250 “Gen. Business Posting Group” (Gen. Business Posting Group)
24	Shipment No.	Code[20]	—
27	No. Printed	Integer	—
30	Correction Δ BC28	Boolean	Specifies the entry as a corrective entry. You can use the field if you need to post a corrective entry to an account.
31	Format Region	Text[80]	—	TableRelation “Language Selection”.“Language Tag”
480	Dimension Set ID	Integer	—	TableRelation Table 480 “Dimension Set Entry” (Dimension Set Entry); not editable

Keys

Key1: No. (clustered)

Procedures

Navigate()
PrintRecords(ShowRequestForm: Boolean)
ShowDimensions()

Triggers

OnDelete

Relations

lookup page Page 6572 “Posted Invt. Shipments”
Salesperson Code: TableRelation Table 13 “Salesperson/Purchaser”
Location Code: TableRelation Table 14 “Location”
Gen. Bus. Posting Group: TableRelation Table 250 “Gen. Business Posting Group”
No. Series: TableRelation Table 308 “No. Series”
Posting No. Series: TableRelation Table 308 “No. Series”
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”
Comment: CalcFormula Table 5748 “Inventory Comment Line”
Language Code: TableRelation Table 8 “Language”

Pages and codeunits on this table

Page 30244 “APIV2 - P. Invt. Shipments” (source table)
Page 6570 “Posted Invt. Shipment” (source table)
Page 6572 “Posted Invt. Shipments” (source table)

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 229 “Document-Print” (1 call: PrintRecords → PrintInvtShipment)
Codeunit 408 “DimensionManagement” (1 call: ShowDimensions → ShowDimensionSet)
Codeunit 6500 “Item Tracking Management” (1 call: OnDelete → DeleteItemEntryRelation)

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: "Invt. Shipment Header"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.