Aksha
Aksha
Business Software

Documentation

Sites

Sites maintains physical and operational locations below an Organization, optionally below a Branch, with Buildings, Floors, geofence and operating defaults used by downstream setup such as Cost Centers.

System administratorsImplementation teamsOperations administratorsHR and organization-setup administrators
Last updated: 15-08-2026

What Sites is for

Sites defines physical or operational business locations in AkshaERP.

A Site belongs to an Organization, can optionally belong to a Branch, and can contain Buildings and Floors. This location structure can be referenced by Cost Centers and other setup.

  • Maintain stable Site identity and Organization ownership.
  • Associate a Site with the appropriate Branch when required.
  • Classify Sites using configured Site Types.
  • Maintain Site Manager, Holiday Calendar, Default Shift and Time Zone.
  • Record address and optional geofence information.
  • Maintain Buildings and Floors.
  • Review Usage before restructuring or deactivation.
  • Activate or deactivate without deleting history.
  • Review Site change History.

Site structure

The location hierarchy is Organization, optional Branch, Site, Building and Floor.

  • Organization owns the Site.
  • Branch is optional and must belong to the Site Organization.
  • A Site can contain multiple Buildings.
  • A Building can contain multiple Floors.
  • Cost Centers can reference Site, Building and Floor information.

Find and open a Site

Open Access Management and choose Sites. The administration list can be searched, sorted and paged.

The list shows identity, Organization and Branch, Site Type, location, structural counts, active Cost Center usage and lifecycle Status.

Create a Site

Choose Create and enter Organization, Site Code and Site Name. Add the optional Branch and operating defaults needed by the location.

New Sites start Active.

Organization and Branch

Organization is required. Branch is optional.

When Branch is supplied, it must belong to the same Organization. An Active Site cannot use an inactive Organization or inactive Branch.

Site Type and operating defaults

Site Type comes from the configured SITE_TYPE values. Site Time Zone comes from the same APP_TIMEZONE configuration used by User preferences.

You can also assign a Site Manager, Holiday Calendar and Default Shift where required.

  • Site Type is controlled configuration rather than free text.
  • Time Zone is selected from configured IANA timezone choices.
  • For active use, the selected Manager must be a valid current Employee.
  • Holiday Calendar and Default Shift must resolve to existing setup when selected.

Address and geofence

Address is optional. Geofence supports a circular location using Latitude, Longitude and Radius in metres.

  • Latitude and Longitude must be entered together.
  • Latitude must be between -90 and 90.
  • Longitude must be between -180 and 180.
  • Geofence Radius cannot be negative.

Buildings

Use Buildings to maintain structures within the Site.

  • Building Code is required and unique within the Site.
  • Building Name is required.
  • A Building referenced by a Cost Center, or containing a referenced Floor, cannot be removed.

Floors

Select a Building and use Floors to maintain its Floor structure.

  • Floor Code is required and unique within the selected Building.
  • Floor Name is optional.
  • A Floor referenced by a Cost Center cannot be removed.

Usage

Usage helps administrators understand the effect of retiring or restructuring a Site.

  • Building count
  • Floor count
  • Total and active Cost Centers
  • Lifecycle blockers
  • Known Site, Building and Floor references

Activate and deactivate

Deactivate a Site when it should no longer be available as active setup. Active Cost Center dependencies block deactivation.

Activate returns a valid inactive Site to service after Organization, Branch, Site Type, operating defaults, dates and geofence are checked again.

Inactive Sites and historical records

Inactive Sites are removed from normal active Site lookups used for new setup.

Existing records can still resolve the Site identity they already store.

History

History records Site master events such as Create, Update, Activate and Deactivate with the available user, time and source.

Save, Apply and Close

Site page actions

ActionWhat happens
SaveValidate and save the Site, then return to the Sites list.
ApplyValidate and save the Site but keep the record open.
CloseLeave the Site screen without performing a new save.

Related pages

Frequently asked questions

Can I change the Site Code after creation?

No. Site Code is the stable Site identity and is permanent after creation.

Can I move a Site to another Organization?

Not through normal Site maintenance. Organization is permanent after creation so historical ownership is not silently changed.

Does every Site require a Branch?

No. Branch is optional, but when selected it must belong to the Site Organization.

How is Time Zone selected?

Site Time Zone is selected from the configured APP_TIMEZONE values rather than entered as unrestricted free text.

Why is a Branch rejected?

The Branch may belong to another Organization or may be inactive while the Site is Active.

Why can’t I remove a Building or Floor?

A Cost Center may still reference that location. Review Usage and correct the owning setup first.

Why can’t I deactivate a Site?

An active Cost Center still references it. Review Usage for the blocker.

Will deactivation remove old references?

No. Existing historical references remain unchanged.

Continue reading