Table 4764 "Warehouse Module Setup"

ContosoCoffeeDemoDataset · Microsoft.DemoData.Warehousing · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Extensible	false
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	Primary Key	Code[20]	—	DataClassification SystemMetadata
2	Customer No.	Code[20]	Specifies the customer number to use for the scenarios. via Page 4766 “Warehouse Module Setup”	TableRelation Table 18 “Customer”
3	Vendor No.	Code[20]	Specifies vendor number to use for the scenarios. via Page 4766 “Warehouse Module Setup”	TableRelation Table 23 “Vendor”
4	Item 1 No.	Code[20]	Specifies the main number to use for the scenarios. via Page 4766 “Warehouse Module Setup”	TableRelation Table 27 “Item” (Item where(Type = const(Inventory)))
5	Item 2 No.	Code[20]	Specifies extra item number to use for the scenarios. via Page 4766 “Warehouse Module Setup”	TableRelation Table 27 “Item” (Item where(Type = const(Inventory)))
6	Item 3 No.	Code[20]	Specifies extra item number to use for the scenarios with item tracking. via Page 4766 “Warehouse Module Setup”	TableRelation Table 27 “Item” (Item where(Type = const(Inventory)))
7	Location Bin	Code[10]	Specifies the code of the location for the Basic Location scenarios. via Page 4766 “Warehouse Module Setup”	TableRelation Table 14 “Location” (Location where(“Use As In-Transit” = const(false)))
8	Location Adv Logistics	Code[10]	Specifies the code of the location for the Simple Logistics scenarios. via Page 4766 “Warehouse Module Setup”	TableRelation Table 14 “Location” (Location where(“Use As In-Transit” = const(false)))
9	Location Directed Pick	Code[10]	Specifies the code of the location for the Advanced Logistics scenarios. via Page 4766 “Warehouse Module Setup”	TableRelation Table 14 “Location” (Location where(“Use As In-Transit” = const(false)))
10	Location In-Transit	Code[10]	Specifies the code of the location for the Advanced Logistics scenarios. via Page 4766 “Warehouse Module Setup”	TableRelation Table 14 “Location” (Location where(“Use As In-Transit” = const(true)))

Keys

Key1: Primary Key (clustered)

Procedures

InitRecord() (internal)
InitWarehousingDemoDataSetup()

Relations

Location Adv Logistics: TableRelation Table 14 “Location”
Location Bin: TableRelation Table 14 “Location”
Location Directed Pick: TableRelation Table 14 “Location”
Location In-Transit: TableRelation Table 14 “Location”
Customer No.: TableRelation Table 18 “Customer”
Vendor No.: TableRelation Table 23 “Vendor”
Item 1 No.: TableRelation Table 27 “Item”
Item 2 No.: TableRelation Table 27 “Item”
Item 3 No.: TableRelation Table 27 “Item”

Pages and codeunits on this table

Page 4766 “Warehouse Module Setup” (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 5116 “Create Common Customer/Vendor” (2 calls: InitWarehousingDemoDataSetup → DomesticCustomer1, InitWarehousingDemoDataSetup → DomesticVendor2)

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: "Warehouse Module Setup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.