Inventory

A per-(site, item) stocking configuration.

INV_ITM_QueryApi.getSiteItemMandatory returns the SiteItem row for a (site, item) pair, raising a business exception when the row does not exist. Used by every flow that needs to know how the item is stocked at the site (stock issue, receipt, replenishment plan, …​).

SiteItemWriterService.copyAndPersistSiteItems clones every SiteItem row of an existing item and re-persists it under a new item, preserving the planning configuration (order system / policy / sourcing type), label count, location reference, and material team. Used by INV_ITM_CommandApi.copyAndPersistSiteItems when an item is duplicated at the catalogue level.

Read-side facade.

Write-side facade.

Other inventory submodules consume the QuantityRecord, QuantityRecord2, SimpleQuantityRecord, and EconomicQuantityRecord value types from this package directly — they are not entities and they are not exposed through the query/command API.

The submodule defines a view model for SiteItem but does not declare any custom UI actions.

title: "Sites and Warehouses (LOC)" ---

A physical operations location.

A storage facility.

A storage spot inside a warehouse.

A class of storage spot.

A link between a location type and a container type that may sit in it.

A per-(warehouse, container-type) capacity figure.

INV_LOC_QueryApi exposes two thin lookups: warehouse capacity for a (warehouse, container type) pair, and a warehouse location by (warehouse, location code). Both return null when not found — callers decide whether absence is an error.

HasInventoryTransaction is the seam every inventory-touching entity in the ERP implements. It standardises the question "what does this row do to inventory?" — exposing the transaction type, address, optional warehouse location, partner, inventory unit, pieces, internal quantity, and optional external UoM/quantity. Modules like inv.unt, acc.jrn, and the trade modules code against this interface so they don’t depend on the concrete entities.

InventoryPostingType is a small enum (POST_TO_INVENTORY / UNDO_POST_TO_INVENTORY) used by inventory-posting flows to indicate whether the operation is a forward post or its reversal. The reversal flag is exposed via isReversal().

Read-side facade.

This submodule does not provide a command API class. Sites, warehouses, locations, location types, and capacity rows are maintained through the standard CRUD pages.

Cross-module seam every inventory-posting entity implements. Methods: getInventoryTransactionType, getInventoryAddress, getWarehouseLocation, getPartner, getInventoryUnit, getQuantityPcs, getQuantityInt, getQuantityUom, getQuantityExt.

The submodule defines view models for Site, Warehouse, WarehouseLocation, LocationType, LocationTypeContainer, and WarehouseCapacity but does not declare any custom UI actions.

title: "Lots (LOT)" ---

A manufacturer-side lot of an item.

The 1-to-1 link from an inventory unit to its lot.

A supplier-side lot reference.

This submodule does not provide query- or command-API classes. Other modules read the lot entities through the standard generated readers and create lot rows as part of inbound and production flows.

The submodule defines view models for ItemLot, LotUnit, and SupplierLot but does not declare any custom UI actions.

title: "Inventory Units (UNT)" ---

A single identity-tracked physical thing.

A validation rule enforces that the cost unit’s item equals the supplier lot’s item.

A reference status code with two derived flags.

A timestamped record of a status change. Implements the framework IsEvent interface.

A timestamped record of a unit moving between warehouse locations.

InventoryLocationTransactionActionWriter.addInventoryLocationTransaction records a fresh InventoryLocationTransaction for a unit (and optional bundle) moving to a target location, in Draft state. The from location is captured from the unit’s currentLocation at the time of recording.

processInventoryLocationTransaction is the seam invoked by the confirm action on the move event. It looks up the unit’s on-hand inventory line through inv.lev, raises a business exception if there is no on-hand stock or if there is more than one on-hand line (an integrity invariant), updates the unit’s currentLocation, rolls the bundle along when one is present, and marks the transaction Processed.

changeBundleLocation is the bundle-side counterpart used when a whole bundle moves. It records and processes a single transaction per affected unit while keeping the bundle/unit relationship in sync.

InventoryUnitStatusEventActionWriter is the action handler for the confirm and confirmUndo actions on a InventoryUnitStatusEvent. Confirming the event applies the new status to the unit (recomputing biStatusBlocked, biStatusInspect, and the derived biAvailabilityStatus); confirmUndo reverts to the previous state. The unit entity recalculates biAvailabilityStatus whenever a status flag changes (__setBiStatusBlocked and friends).

This submodule does not provide a query API class. Other modules read units, statuses, status events, and location transactions through the standard generated readers.

Write-side facade. All three methods delegate to InventoryLocationTransactionActionWriter.