Inventory Items on Service Orders (SiteLocationID)

Hi ​@bencrooks ! Looked into how the location field behaves on service order lines.

Short answer: the Location (the bin within the warehouse) has no default source of its own — it can't come from the customer, and the warehouse default only affects it indirectly.

Here's how it works:

1. You pick the inventory item on the line.
2. That sets the Warehouse on the line (from the item's default, the branch location default, etc.).
3. Once the warehouse is set, the system looks up the item's Default Issue Location for that item + that warehouse, and inserts it into the Location field.

So the Location is item-and-warehouse driven. If the item doesn't have a Default Issue From location configured for that warehouse, the Location simply stays blank — which is exactly the behavior you're seeing.

To your specific questions:

• Can the Location default from the customer? No. There's no customer-based defaulting for it at all. Customer drives things like warehouse, terms, and price — never the bin location.
• Is the branch location the source? Not directly. The branch location default feeds which warehouse lands on the line; the Location then follows from that warehouse. So the branch location sits one step upstream — it influences the warehouse, and the warehouse influences the location.

On the contract-schedule generation issue: when lines get created through schedule generation, they don't go through the same sequence that happens when you key a line by hand on the Service Order screen. So the Location step never runs, and the generated lines come through with the Location empty.

What I'd check first:

1. On Item Warehouse Details (IN204500), make sure a location is set on Default Issue From for those items at the warehouse the contract resolves to.  If it's blank there, nothing will populate the Location on either path — manual or generated.
2. If that default issue location is set and the Location still comes through blank only on the generated lines, then it's the generation process not running the lookup — which is more of a behavior/code question, and worth raising with Acumatica Support.