Skip to content

Purchase General Settings ​

Backlog fieldValue
Story IDAP-PUR-002
EpicPurchase
Story typeMaster data / configuration
Review statusDraft - business analyst and business owner review required
Source evidenceAppsPortal.Apis controller, application command/query handlers, validators, domain entities, and matching MFE workflow where available
Last source review2026-07-10

User story ​

As purchasing administrators, I want to configure purchase defaults, accounts, and policies so that purchase workflows behave consistently.

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 ​

Enabled purchase workflows require default accounts, taxes, warehouses, payment terms, sequences, and policy switches they consume.

Optional or conditional ​

Unused defaults and optional tolerances are not required.

Action behavior ​

Save affects future orders/invoices/returns; posted documents retain snapshots.

Blocking rule or downstream effect ​

Missing consumed settings blocks Post with an actionable configuration error.

Frontend page coverage ​

The following UI coverage is sourced from the pulled MFE route configuration. A Module-level supporting artifact mapping is evidence of a reachable screen, but requires BA confirmation that it belongs to this story rather than a more specific feature story.

Route/pageComponentModeRoute permission/guardMapping confidenceSource
general-settingsGeneralSettingPurchaseComponentList/navigationPermission: AppPurchasePermissions.PurchaseGeneralSettings_View , AppPurchasePermissions.PurchaseGeneralSettings_Edit; Guards: PolicyAuthGuardFeature token matchapps/purchase/src/app/remote-entry/purchase/purchase.module.ts:159

Observed frontend fields and validation ​

ComponentControlObserved frontend ruleComponent source
GeneralSettingPurchaseComponentdefaultWarehouseIdVisible control; optional or API-dependentapps/purchase/src/app/remote-entry/purchase/pages/general-setting-purchase/general-setting-purchase.component.ts

Observed frontend actions ​

ComponentClick action/handlerBusiness review requirementComponent source
--No direct (click) handler was found; review shared toolbar/table commands and form submission bindings.Route sources above

Page-specific frontend acceptance criteria ​

  1. general-settings - List/navigation: Load an authorized paged/searchable list or navigation page; preserve filters/sort/paging and expose only permitted row and bulk actions. Security observed: Permission: AppPurchasePermissions.PurchaseGeneralSettings_View , AppPurchasePermissions.PurchaseGeneralSettings_Edit; Guards: PolicyAuthGuard

Internal Documentation — Microtec