First-Time Setup
Chapter 1 — Base Configuration

Setting up your facilities

Complete & Continue Next Lesson Learn More

LESSON INFO

Audience

  • Facility admins
  • Implementation team members supporting go-live and change control

Prerequisites

  • You can log in to Themis-Trace.
  • You have Facility Editor permissions for the target facility.

Skills you’ll build

  • You can create and maintain facilities without breaking downstream workflows.
  • You can validate a facility change with a low-risk test.

LESSON OUTLINE

Concept

  • Facilities are a master configuration used by most downstream workflows
    • Facilities are maintained from Administration → Facilities Maintenance → Facilities.
    • A facility record includes core identity and address details such as Name, Code, Line 1, City, Country, and an Active flag.
      • The Code field should be populated with the facility’s DUNS number.
  • Facility vs facility context
    • A facility is a master record.
    • Facility context is a user’s current working facility selection that affects what can be created, viewed, and selected.
    • Facility context is typically chosen during the creation of operational records (for example: Receiving Orders, Schedule Items, and Inventory Items).

Edit a facility safely

  1. Open the facility from the grid (Edit).
  2. Correct an address field by clicking on the text box.
  3. Select Save or Save & Close.
  4. Verification checklist:
    • Reconfirm the facility is still Active.
    • If the change impacts printed/label output for that facility, validate with a small test print.

Activate & Deactivate

  1. Select one or more facilities via the grid checkboxes.
  2. Select Activate or Deactivate.
  3. Confirm when prompted.
  4. Re-test any workflow that depends on selecting that facility.

Where facility work usually continues

  • Inventory Locations
    • Inventory locations are configured under Administration → Facilities Maintenance → Inventory Locations.
    • Locations can be structured or unstructured, and are used across multiple workflows.

COMMON ISSUES

    • Likely cause: Facility is deactivated, or you are working in the wrong facility context.

    • Checks:

      • Confirm the facility is Active (not deactivated).

      • Confirm you are working in the correct facility context (facility selection is often made during creation of operational records).

    • Fix: Activate the facility or switch facility context to the intended facility.

    • Likely cause: Missing required fields, a uniqueness constraint violation, or a value exceeding a maximum length.

    • Checks:

      • Re-check all required fields (marked with blue left borders on the form).

      • If you changed identity fields (like Name or Code), confirm you are not violating length or uniqueness rules.

    • Fix: Fill required fields, choose a unique value, and shorten any values that exceed limits, then save again.

    • Likely cause: The facility is referenced by downstream records, and server-side delete protection is blocking deletion.

    • Checks:

      • Assume the facility is already referenced by downstream records.

      • If possible, identify the dependent records/workflows (for example, receiving, shipping, scheduling, inventory).

    • Fix: Use Deactivate to prevent future selection while avoiding broken references.