Locations¶

A location is a network node. In Demand Planning, it represents where demand is observed or assigned.

Path in the platform¶

Data > Data Operations > Master Data > Materials / Locations > Locations > Locations

Granularity and key¶

Granularity: one row per location.
Key: a unique, stable id.

Required fields¶

Field	Meaning
`id`	Unique location identifier

Optional fields¶

Field	Meaning	Default Value When Not Provided
`description`	Human-readable description	Blank
`active`	Participation in planning	`true`
`locationType`	Location Type	`Internal`
`country`, `state`, `city`	Geography	Blank
`latitude`, `longitude`	Coordinates	No coordinates registered
`availableInProductionPlanningBook`	Visibility in production views	`true`
`availableInSupplyPlanningBook`	Visibility in supply views	`true`
`defaultSNPUomId`	Location-specific default Supply Planning unit	Default Supply Planning unit (global fallback: `UN`)
`referenceLocationForProductLocationParameters`	Reference location for parameters	The location itself
`orderFulfillmentTimeDays`	Demand fulfillment time	`0` days
`valueByCharacteristic`	Planning characteristics	No classification characteristics

Blank units in sales

The uomId fallback for sell-out and sell-in comes from Global Planning Parameters, not from defaultSNPUomId.

Choosing the demand location¶

The level should represent how demand is observed and decided. It may be a customer, store, city, region, consolidated channel, or logical combination. Consolidation simplifies forecasting but reduces the information available for disaggregation, deployment, and service analysis.

Dependencies¶

Location Type.
Units of Measure for location-specific quantitative settings.
Geography and planning characteristics used by filters, maps, or clusters.
The location table itself when referenceLocationForProductLocationParameters is filled.
Planning calendar, working days, and holidays when country, state, and city determine which holidays apply.

Used by¶

Supply Planning data model;
originLocationId in Sell-out;
originLocationId and destinationLocationId in Sell-in;
Forecast Clusters;
series definition in the Demand Planning Execution Profile;
Demand Plan rows;
location scope and material-location keys in Prices and COGS;
fixed, storage, handling, transfer, and tax valuation in Logistics and location costs;
Supply Planning, DRP, inventory, production, transportation, cost, and geographic analysis.
geographic matching of national, state, and city holidays in the operational calendar.

Checks¶

consistent location type;
standardized geography when used;
units and flags compatible with the process;
no duplicate IDs for the same node;
stable meaning throughout the historical series.