Appearance
Sales Teams and Areas
| Backlog field | Value |
|---|---|
| Story ID | AP-SAL-015 |
| Epic | Sales |
| Story type | Master data / configuration |
| Review status | Draft - business analyst and business owner review required |
| Source evidence | AppsPortal.Apis controller, application command/query handlers, validators, domain entities, and matching MFE workflow where available |
| Last source review | 2026-07-10 |
User story
As sales administrators, I want to maintain salespeople, teams, areas, and assignments so that ownership, targets, and reporting follow the sales organization.
Acceptance criteria
- Only authorized users can view or execute the feature's actions.
- Required business data, active dependencies, tenant/branch scope, and current document state are validated.
- Invalid requests return actionable validation errors without applying a partial change.
- Search, list, view, print, and export operations use the same authorized business scope.
- Material create, edit, status, approval, posting, reversal, and integration actions are auditable where applicable.
- Financial or stock effects are applied atomically and no more than once.
Business rules
Required
Localized identity, active state, and valid salesperson/team/area hierarchy assignments are required.
Optional or conditional
Manager, targets, territories, credit limits, and dates are optional/conditional.
Action behavior
Save changes future ownership, credit, and reporting; posted documents retain salesperson snapshot.
Blocking rule or downstream effect
Assignments cannot create conflicting active ownership where exclusivity is required.