Skip to main content
Version: 2.4

Stock Module

Stock in tSM is the operational module for physical materials and equipment used in delivery and field operations. It controls stock locations, item balances, movement history, and responsibility assignment.

From architecture perspective, Stock is a business module built on top of the same low-code platform patterns:

  • dynamic attributes via chars (TsmChars),
  • code-table governance for types and statuses,
  • process integration for reservation/issue/return flows,
  • API-level integration with fulfillment, ERP, and finance systems.

Scope and Responsibility​

Stock is responsible for:

  • stock-level ownership and stock-type classification (Stock, StockType),
  • assignment of shared responsibility for stocks (SharedResponsibility),
  • item-level material records (StockItem, StockItemType),
  • movement and storno tracking (StockMovement, StockMovementType),
  • status governance for stock, items, and movements.

Detailed Subdocuments​

Configuration Model​

Stock follows the tSM configuration-first model:

  • technical registries (StockType, StockItemType, StockMovementType) drive behavior,
  • dynamic payloads are stored in chars, config, registry, and dataTags,
  • validity windows govern temporal responsibility and register usage,
  • optional transient processingData enables processing context without schema extension.

In practice:

  1. Configure stock/item/movement type registers.
  2. Create stocks and ownership model.
  3. Create stock items and bind them to stock and item type.
  4. Execute and audit movements (including storno paths).
  5. Integrate movement outcomes with WFM/ERP/finance processes.

TM Forum Governance​

Stock sits primarily in operational support around resource and fulfillment domains:

  • TMF639 Resource Inventory context for technical/physical asset visibility,
  • TMF641/TMF622 fulfillment context where order realization consumes materials,
  • implementation-specific warehousing semantics for movement and ownership control.

tSM applies pragmatic alignment: stock entities are internal operational records, while TMF APIs are used at integration boundaries.