Locations

Locations

Purpose and when to use this record

BriskMaintain storesphysical locationsbin, asaisle, partyard, ofor shelf identifiers used to locate inventory within operations.

At a glance

• Identify it by: Name.

• Check its business context: Warehouse.

• Why care: Warehouse, item, unit, quantity, and cost must describe the inventorysame module.physical Thismovement. generatedA referencewrong warehouse or unit can make availability and valuation misleading.

Before you begin

You need the Brisk permission for the action you are taking on locations. If a Create, Edit, or Delete control is awaitingabsent, workflowdo review.not work around it with another user’s account; ask an administrator to review your role.

Create a recordlocation

TheCreate evidencea packetlocation identifiesafter searching for the viewperson, organization, item, location, or resource under alternate names and identifiers. Merge or correct an existing master record instead of creating a duplicate.

1. Select the business context first: Warehouse.

2. Enter the required identifying and operational values: Name.

3. Review Description against the source document or approved setup decision.

4. Save the location, then confirm Name on its detail page before continuing.

After saving: Verify this location forin Items before staff build new activity on it; correct ownership, classification, and active state now rather than after transactions accumulate.

Delete a location

Delete this action.location Confirmonly user-facingif stepsit beforeis approvingan unused duplicate or setup mistake. Once other records refer to it, preserve that history and make the value inactive when the screen provides that option.

Before confirming, check for related Items. Brisk may refuse deletion when another record depends on this page.one; resolve the duplicate or use the supported correction workflow instead of breaking the trail.

On the confirmation page, verify Name. After confirmation, return to the Locations list and make sure only the intended location was removed.

ViewReview recordlocation details

The evidence packet identifiesUse the viewdetail page as the shared record of what this location currently means. Verify Name, Description, and sourceWarehouse before relying on it for a decision.

Follow Warehouse to determine whether the issue is on this location foror on one of those linked records.

Next check: Verify this action.location Confirmin user-facing stepsItems before approvingstaff build new activity on it; correct ownership, classification, and active state now rather than after transactions accumulate.

Edit an existing location

Edit this location to keep the same real-world party, item, location, or resource accurate. Do not repurpose it for a different entity after activity is attached.

1. Open the detail page. Compare Warehouse with the supporting document or approved request.

2. Recheck Warehouse. These values are most likely to change warehouse availability, replenishment, quantities, and valuation.

3. Save the change, return to the list, and confirm that the location now appears under the expected Name.

After the change: Verify this location in Items before staff build new activity on it; correct ownership, classification, and active state now rather than after transactions accumulate.

Find and review recordslocations

The evidence packet identifiesUse the viewLocations list to find the correct record before opening or changing it. Compare Name. Records with similar names or numbers can still belong to different Warehouse.

• The initial order emphasizes Name. Select a column heading when you need a different comparison.

Open the location whose Name match the task. If it is missing, clear the list filters and sourcerecheck locationthe identifying information shown on the screen rather than creating a replacement immediately.

Fields and business rules

Brisk stores 3 user-relevant fields for this action.location, Confirmincluding user-facing1 stepslinked-record beforeselection approvingand 0 controlled-choice fields. Create and edit screens may hide calculated or workflow-managed values from this page.full reference.

Editanexistingrecord

The

evidencetheviewandsourcelocation Confirmuser-facingsteps

Field	Required	What packetit identifiescontrols
Name	Yes	Human-readable name for this action.location.
Description	No	Description of this location.
Warehouse	No	The warehouse associated with this location.

What happens next

Verify this location in Items before approvingstaff thisbuild page.new activity on it; correct ownership, classification, and active state now rather than after transactions accumulate.

DeleteCommon mistakes and troubleshooting

• The record will not save: Recheck Name and any message beside the field. A required related record may also be inactive or unavailable to your role.

• The values look right but the result is wrong: Open Warehouse from the detail page. Correct the specific relationship that is wrong instead of forcing a recordtotal

  Theor evidencestatus packetto identifies the view and source locationcompensate for this action. Confirm user-facing steps before approving this page.it.