Skip to content

Asset Transfers

Backlog fieldValue
Story IDAP-FA-007
EpicFixed Assets
Story typeBusiness workflow
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 asset custodians, I want to move assets between locations or responsibility contexts so that custody and location history remain traceable.

Posting reference: AppsPortal Posting Ledger explains debit/credit construction. Delegation and Interaction Contracts explains module ownership, delegated commands, linked records, commit boundaries, and reversal propagation.

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.

Posting details

  1. Asset Transfer Post usually creates no GL entry because it changes location/custody rather than asset value.
  2. Validate Draft, transfer date, different source/target location/custody, and each asset's current eligible status/location.
  3. Record previous and target assignment, update asset custody/location history, and mark transfer Posted.
  4. Commit all asset assignments and transfer status together.
  5. Unpost restores the previous assignment only if no later transfer, sale, disposal, or other lifecycle action changed the asset.

General ledger posting

ConditionDebitCreditResult
Normal asset transfer--No GL entry because value does not change.

Other module and document effects

AreaEffectConditional/no effect
Asset registerUpdates location/custodian and preserves prior assignment history.Cost, accumulated depreciation, NBV, inventory, customer/vendor, and cash remain unchanged.
LifecycleLater transfer/sale/disposal sees new assignment.Later activity can block unpost.

Core acceptance scenarios

  1. Given a Draft transfer and assets still in the recorded source location, when the custodian clicks Post, then asset location/custody history and transfer status update together.
  2. Given a later lifecycle action changed the asset after transfer, when the operation is attempted, then Unpost is rejected.
  3. Given the same Post request is retried after success, when the source is no longer Draft, then no duplicate journal, stock, balance, payment, or lifecycle effect is created.

Transfer requires Draft, date, source and different target location/custody, and eligible assets not locked by another lifecycle operation. Post updates asset location/custody history and marks the transfer Posted; it creates no value change unless the configured transfer type requires accounting. Unpost requires the current asset state still matches the posted transfer target, restores prior assignment, and marks Unposted. Later transfers or disposal/sale block unpost.

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
(module default)TransferListComponentList/navigationPermission: AppFixedAssetsPermissions.AssetsTransfer_List; Guards: PolicyAuthGuardExplicit frontend feature ruleapps/fixedAssets/src/app/remote-entry/transactions/assets-transfer/assets-transfer-routing.module.ts:20
(module default)TransferMainComponentList/navigationPermission: AppFixedAssetsPermissions.AssetsTransfer_List; Guards: PolicyAuthGuardExplicit frontend feature ruleapps/fixedAssets/src/app/remote-entry/transactions/assets-transfer/assets-transfer-routing.module.ts:12
addTransferAddComponentAddPermission: AppFixedAssetsPermissions.AssetsTransfer_Add; Guards: PolicyAuthGuardExplicit frontend feature ruleapps/fixedAssets/src/app/remote-entry/transactions/assets-transfer/assets-transfer-routing.module.ts:30
assets-transferLazy-loaded routeList/navigationNo route-level permission/guard found in source windowExplicit frontend feature ruleapps/fixedAssets/src/app/remote-entry/transactions/transactions-routing.module.ts:62
edit/:idTransferEditComponentEditPermission: AppFixedAssetsPermissions.AssetsTransfer_Edit; Guards: PolicyAuthGuardExplicit frontend feature ruleapps/fixedAssets/src/app/remote-entry/transactions/assets-transfer/assets-transfer-routing.module.ts:40
sequenceSequenceComponentSequenceNo route-level permission/guard found in source windowExplicit frontend feature ruleapps/fixedAssets/src/app/remote-entry/transactions/assets-transfer/assets-transfer-routing.module.ts:60
view/:idTransferViewComponentView/detailPermission: AppFixedAssetsPermissions.AssetsTransfer_View; Guards: PolicyAuthGuardExplicit frontend feature ruleapps/fixedAssets/src/app/remote-entry/transactions/assets-transfer/assets-transfer-routing.module.ts:50

Observed frontend fields and validation

ComponentControlObserved frontend ruleComponent source
TransferHeaderComponentactivationDateRequired in component validatorapps/fixedAssets/src/app/remote-entry/transactions/assets-transfer/component/transfer-header/transfer-header.component.ts
TransferHeaderComponentdefaultToLocationIdVisible control; optional or API-dependentapps/fixedAssets/src/app/remote-entry/transactions/assets-transfer/component/transfer-header/transfer-header.component.ts
TransferHeaderComponentdescriptionVisible control; optional or API-dependentapps/fixedAssets/src/app/remote-entry/transactions/assets-transfer/component/transfer-header/transfer-header.component.ts
TransferHeaderComponentreferenceNoVisible control; optional or API-dependentapps/fixedAssets/src/app/remote-entry/transactions/assets-transfer/component/transfer-header/transfer-header.component.ts
TransferHeaderComponenttransferDateRequired in component validatorapps/fixedAssets/src/app/remote-entry/transactions/assets-transfer/component/transfer-header/transfer-header.component.ts

Observed frontend actions

ComponentClick action/handlerBusiness review requirementComponent source
TransferBodyComponentonDeleteRowAvailable only in deletable states with Delete permission; identify the record in confirmation, call delete once, remove/refresh the list row on success, and retain the row with the API reason on failure.apps/fixedAssets/src/app/remote-entry/transactions/assets-transfer/component/transfer-body/transfer-body.component.ts
TransferBodyComponentopenDialogOpen the item/lookup/tracking dialog with the current warehouse, item, UOM, and remaining quantity context; accepted values must return to the correct line and cancel must not mutate it.apps/fixedAssets/src/app/remote-entry/transactions/assets-transfer/component/transfer-body/transfer-body.component.ts
TransferHeaderComponentopenAttachmentsDocument the enabled state, permission, input context, resulting API or navigation effect, success refresh, and concrete failure behavior for this handler.apps/fixedAssets/src/app/remote-entry/transactions/assets-transfer/component/transfer-header/transfer-header.component.ts
TransferListComponentonDeleteAvailable only in deletable states with Delete permission; identify the record in confirmation, call delete once, remove/refresh the list row on success, and retain the row with the API reason on failure.apps/fixedAssets/src/app/remote-entry/transactions/assets-transfer/pages/assets-transfer-list/assets-transfer-list.component.ts
TransferListComponentonEditOpen the identified editable record only with Edit permission; posted/locked records remain blocked by route or action state and list context must be recoverable on return.apps/fixedAssets/src/app/remote-entry/transactions/assets-transfer/pages/assets-transfer-list/assets-transfer-list.component.ts
TransferListComponentonPostAvailable only for a postable Draft and Post permission; confirm the document, prevent a second submission, call the posting API, and refresh status, journal/stock links, and row actions. Failure must keep the pre-post state.apps/fixedAssets/src/app/remote-entry/transactions/assets-transfer/pages/assets-transfer-list/assets-transfer-list.component.ts
TransferListComponentonPrintOutGenerate the printout for the selected record and authorized branch/tenant; use posted/current values and surface print, template, ZATCA/ETA, or popup failures without changing transaction state.apps/fixedAssets/src/app/remote-entry/transactions/assets-transfer/pages/assets-transfer-list/assets-transfer-list.component.ts
TransferListComponentonUnPostAvailable only for a postable Draft and Post permission; confirm the document, prevent a second submission, call the posting API, and refresh status, journal/stock links, and row actions. Failure must keep the pre-post state.apps/fixedAssets/src/app/remote-entry/transactions/assets-transfer/pages/assets-transfer-list/assets-transfer-list.component.ts
TransferListComponentonViewOpen the authorized record in view mode with its status, totals, lines, source and generated-document links; handle deleted, forbidden, and missing records without exposing stale data.apps/fixedAssets/src/app/remote-entry/transactions/assets-transfer/pages/assets-transfer-list/assets-transfer-list.component.ts
TransferViewComponentopenAttachmentsDocument the enabled state, permission, input context, resulting API or navigation effect, success refresh, and concrete failure behavior for this handler.apps/fixedAssets/src/app/remote-entry/transactions/assets-transfer/pages/assets-transfer-view/assets-transfer-view.component.ts

Page-specific frontend acceptance criteria

  1. (module default) - 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: AppFixedAssetsPermissions.AssetsTransfer_List; Guards: PolicyAuthGuard
  2. add - Add: Render permitted fields, required indicators, defaults, dependent lookups, validation, Save/Cancel, loading, success, and API-error states. Security observed: Permission: AppFixedAssetsPermissions.AssetsTransfer_Add; Guards: PolicyAuthGuard
  3. assets-transfer - 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: No route-level permission/guard found in source window
  4. edit/:id - Edit: Load the identified record, enforce state/permission field locks, preserve concurrency identity, validate changes, and return without losing filters. Security observed: Permission: AppFixedAssetsPermissions.AssetsTransfer_Edit; Guards: PolicyAuthGuard
  5. sequence - Sequence: Show current numbering scope and permit only authorized, valid sequence configuration without retroactively renumbering posted documents. Security observed: No route-level permission/guard found in source window
  6. view/:id - View/detail: Load an authorized immutable/detail representation with status-aware actions, linked records, print/export where exposed, and not-found/forbidden handling. Security observed: Permission: AppFixedAssetsPermissions.AssetsTransfer_View; Guards: PolicyAuthGuard

Internal Documentation — Microtec