Location Master

1Fields & behaviour #

• Name is the location or group name and must be unique across all locations; it is the record's key, so renaming it here also updates every child location that sits under it.
• Primary Group ? marks the record as a top-level group when on. Turn it off to make this location a member of another group, which reveals the Under Group field.
• Under Group is the parent and is required only when Primary Group is off. Any existing location can be the parent — primary or itself nested — it just cannot be this location. Missing it? Use the dropdown's ＋ Create new location group footer (full page only) — it opens this master and selects the new location as the parent automatically.
• Description is a free note about the location (up to 50 characters).
• Default Storage Space is the warehouse / storage space picked into transactions for this location by default; leave it blank for none. Missing one? Use the dropdown's ＋ Create new storage space footer (full page only) — it opens the Warehouse master and selects the new space automatically.
• Default Employee is the employee ledger account responsible for this location by default; leave it blank for none. Use the dropdown's ＋ Create new employee ledger footer (full page only) — it opens the Ledger Account master with Treat this ledger as employee already ON and locked, and selects the new ledger automatically.
• Branch Sharing Option appears only in the ERP edition. All makes the location visible to every branch; Selective reveals the branch checklist below.
• Selective Branch List (ERP, shown when sharing is Selective) is the set of branches allowed to see and use this location.
• Toolbar: Find (F2) loads a location, Add (F3) starts a new one, Modify (F4) edits the loaded one, Save (F5) commits, Esc cancels.

2Step by step #

Locations name places — routes, areas, sites — that parties and vouchers can be tagged with for reporting.

1. Press Add (F3) , type the location name and its details, save with F5 .
2. Tag party contacts and vouchers with it; location-wise reporting follows.

3Business rules & integrity #

• Hierarchy rules (database-enforced): Primary Group must be Y or N; a non-primary location's parent must exist, can't be blank, and can't be the location itself — a save breaking any of these is rolled back with the database's message.
• Rename cascade: renaming a group automatically updates the Under Group of every location beneath it (one group at a time — bulk renames are refused).
• Branch sharing (ERP): with Selective , only the ticked branches see and use the location in their transactions; All (or blank) shares it everywhere.
• Defaults in use: the default storage space and default employee are proposed automatically when this location is picked on transactions (e.g. fixed-asset transfers).
• Delete is refused while other locations are still under this one — reassign them first. Deleting a location also clears its document links, and user permissions (_PERM triggers) can refuse a save or delete entirely.
• Under Group lists every existing location (a parent need not be primary). Storage Space / Employee / Branches come from their masters.