IN Location Groups
Company Tracker action: implementation-setup-in-location-groups
Milestone: Inventory / Module Setup (milestone_id=14, core_milestone_id=2)
Order: 2
Estimated duration: 0.25–0.5 hours
Typical owner: Controller
Purpose
Group inventory locations so sites can share structure and, when needed, override GL accounts used for material postings at the group.
Prerequisites
- Know whether few locations share one group or each location gets its own group.
- Any group-level GL overrides identified (else location-level accounts carry the map).
Vista configuration article
See the detailed Vista guide:
Field meanings and form steps live there. Do not restate them on this page.
Implementation guidance
- Why groups matter: grouping multiple locations enables GL account overrides for how materials post for that set of sites.
- Typical pattern: a few locations → one shared location group; or one-to-one location↔group when each site needs its own override path.
- Decide / load / accept: create groups, assign locations (as locations are stood up), set overrides only where needed; accept with Controller.
Tips and gotchas
- Not just a reporting label — group is a GL override lever.
- Keep group design simple unless sites truly need different GL paths.
Done when
- Groups exist for go-live locations and membership/overrides match the accepted GL design.