Page 4766 "Warehouse Module Setup"

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

Properties

Property	Value
Caption	Warehouse Module Setup
Extensible	false
SourceTable	Warehouse Module Setup
PageType	Card
ApplicationArea	All

Fields on this page

Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).

Group	Control	Shows	ToolTip
Locations	Location Bin	Location Bin	Specifies the code of the location for the Basic Location scenarios.
	Location Adv Logistics	Location Adv Logistics	Specifies the code of the location for the Simple Logistics scenarios.
	Location Directed Pick	Location Directed Pick	Specifies the code of the location for the Advanced Logistics scenarios.
	Location In-Transit	Location In-Transit	Specifies the code of the location for the Advanced Logistics scenarios.
Master Data	Customer No.	Customer No.	Specifies the customer number to use for the scenarios.
	Vendor No.	Vendor No.	Specifies vendor number to use for the scenarios.
	Item 1 No.	Item 1 No.	Specifies the main number to use for the scenarios.
	Item 2 No.	Item 2 No.	Specifies extra item number to use for the scenarios.
	Item 3 No.	Item 3 No.	Specifies extra item number to use for the scenarios with item tracking.

Triggers

OnOpenPage

Relations

source table Table 4764 “Warehouse Module Setup”

Called by

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 5140 “Warehouse Module” (1 call: RunConfigurationPage → (object))

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