LESSON INFO
Audience
- Facility admins
- Operations supervisors
- Implementation team members supporting go-live and change control
- End users who need to select the correct customer during scheduling, receiving, and shipping
Prerequisites
- You can log in to Themis-Trace.
- You have permissions to view and maintain customers (Customer Viewer/Editor/Creator or equivalent).
- You understand how facility context can affect what customer records you can see or select in Themis-Trace.
Skills you’ll build
- You can create a minimum viable customer record (required fields only).
- You can manage customer address types (Ship-To, Sold-To, Bill-To) without breaking downstream selection.
LESSON OUTLINE
Concept
- Customers are a facility-scoped configuration
- Customers are maintained under Administration → Customers Maintenance → Customers.
- The Customers grid shows active records by default.
- Customer vs address types
- Customer maintenance includes multiple address types:
- Ship To
- Sold-To
- Bill-To
- Address types can be maintained from the customer edit form tabs, and Ship-To/Bill-To/Sold-To also have their own maintenance screens under Customers Maintenance.
- Customer maintenance includes multiple address types:
- Key constraints
- Customer Name is required and must be unique in the system.
- Customer Code should be populated with the Customer DUNS number.
- Deleting is typically blocked when other records reference the customer.
Create a customer
- Go to Administration → Customers Maintenance → Customers.
- Select New.
- Enter the required fields (marked with a blue left border):
- Name
- Line 1
- City
- Country
- Optional: add Code (used for synchronizing data between systems).
Note: Customer Code, which is populated with a given Customer’s DUNS number, is necessary for the completion & creation of EDI transactions.
- Select Save & Close.
- Immediate verification (low risk):
- Confirm the customer appears in the Customers grid.
- Confirm the customer is Active.
Add a Ship-To address and validate selection rules
- Go to Administration → Customers Maintenance → Ship-To Addresses.
- Select New.
- Provide the required inputs (marked with a blue left border):
- Customer (must be active)
- Name
- Alias Name
- Address fields including Line 1, City, and Country
- Select Save & Close.
- Immediate verification:
- Confirm the Ship-To appears in the grid.
- Confirm the Ship-To is Active.
- Confirm the Ship-To can be selected in the downstream screen(s) where it is expected.
- If the screen requires additional context (for example, selecting a Sold-To first), set that context and re-check.
Activate, deactivate, or delete
- Deactivate (recommended for most change control)
- Use when you want to stop future use while keeping history intact.
- Activate
- Use to restore selection in downstream workflows.
- Delete (use sparingly)
- Completely removes the customer from the Themis-Trace database.
- Deletion may be blocked if other records reference the customer.
COMMON ISSUES
-
Likely cause: Wrong facility context, or the customer is deactivated.
Checks:
Confirm you are working in the correct facility.
Confirm the customer is Active in the Customers grid.
Fix: Switch facility context or activate the customer.
-
Likely cause: Missing required fields.
Checks: Confirm required fields (Name, Line 1, City, Country) are filled.
Fix: Complete missing fields and save again.
-
Likely cause: Ship-To deactivated or wrong customer selected.
Checks:
Confirm Ship-To is Active.
Confirm the correct Customer is selected.
Fix: Activate the Ship-To, choose the correct Customer/Sold-To, or create the correct Ship-To.
-
Likely cause
The customer is referenced by downstream records (for example, receiving, shipping, inventory, scheduling, printouts), and server-side delete protection is blocking deletion.
Checks
Assume the customer already has dependent records.
If an error message is shown, capture the exact message and identify the dependent workflow.
Fix
Prefer Deactivate to prevent future selection while preserving history.
If deletion is required, remove or reassign dependent records first, then retry.