Sequences

Backlog field	Value
Story ID	AP-GS-009
Epic	General Settings
Story type	Business workflow
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 administrators, I want to configure document numbering by screen and scope so that business documents receive unique controlled numbers.

Acceptance criteria

1. Only authorized users can view or execute the feature's actions.
2. Required business data, active dependencies, tenant/branch scope, and current document state are validated.
3. Invalid requests return actionable validation errors without applying a partial change.
4. Search, list, view, print, and export operations use the same authorized business scope.
5. Material create, edit, status, approval, posting, reversal, and integration actions are auditable where applicable.
6. Financial or stock effects are applied atomically and no more than once.

Business rules

Required

Module/screen, scope, format, next/last value, effective period, and uniqueness are required.

Optional or conditional

Prefix/suffix, padding, reset schedule, and manual override are optional/permissioned.

Action behavior

Next number is consumed according to transaction save/post policy; reset/set-last validates collision risk.

Blocking rule or downstream effect

Existing document codes never change after sequence edits.