Difference between revisions of "MRO Material Management"

Revision as of 06:37, 19 June 2026

MRO Material Management

MRO material management is used to support maintenance work with required spare parts, consumables, tools, or other material items.

Users can see which material is required for a task, where the material is stored, how much material is available, how much material is reserved, and which reservation status applies.

Basic concept

Object overview

MaterialMaster

Purpose

MaterialMaster represents the material master or catalogue entry.

It stores item-level master data that can be referenced by material instances in MRO.

Important properties

Material type

Known values of MaterialType are:

• SpareParts
• Consumables
• Tools

Material

Purpose

Material represents a material instance or stock entry in MRO.

It inherits from GoodsMovement and therefore uses the inherited QUANTITY property as its material quantity.

A material links to:

• a material master via LK_MATERIAL_MASTER
• a storage location via LK_STORAGE_LOCATION

Important properties

Material status

The material status is stored in MATERIAL_STATUS and exposed through MaterialStatus.

The property is managed by the user or administrator. The system does not change it automatically.

Reserved quantity

RESERVED_QUANTITY is calculated at read time.

The calculation uses reservations where:

• LK_MATERIAL points to the current material
• STATUS is ReservationStatus.Confirmed

The calculated value is the sum of QTY_PLANNED of these confirmed reservations.

Available quantity

The available material quantity is calculated by AvailableQuantity().

Delete behavior

Material.InternalDeleteAllowed() prevents deleting a material if it still has quantity or active reservations.

Deletion is only allowed if:

• QUANTITY is lower than or equal to 0
• HasActiveReservation() returns false

Reservation

Purpose

Reservation represents a manually created material reservation for a task.

It links:

• a task via LK_TASK
• a material via LK_MATERIAL

It stores the planned reservation quantity in QTY_PLANNED and the actually issued or consumed quantity in QUANTITY.

Important properties

Reservation status

Known values of ReservationStatus are:

Status change rules

Status changes are controlled by AllowStatusChange(int newStatus).

The following rules are applied:

• no status change is allowed when the current status is Issued
• changing from Confirmed back to Planned is not allowed
• other status changes are allowed by this method

Planned quantity validation

The setter of QTY_PLANNED validates changes through AllowQuantityPlanned(double).

A new planned quantity is only allowed if:

• Status is ReservationStatus.Planned
• LK_MATERIAL is assigned
• the new quantity is greater than 0
• the new quantity is lower than or equal to LK_MATERIAL.AvailableQuantity()

Actual quantity validation

The overridden QUANTITY setter validates changes through AllowQuantity(double).

A new actual quantity is only allowed if:

• the new quantity is greater than 0
• the status is either Planned or Confirmed

Link editing rules

The setters of LK_TASK and LK_MATERIAL are guarded by reservation status.

The links cannot be changed when the reservation is:

• Issued
• Confirmed

StorageLocation

Purpose

StorageLocation is a related object used to represent a physical storage location.

A material can reference a storage location via LK_STORAGE_LOCATION.

Important properties and values

GoodsMovement

GoodsMovement is a technical base class.

It provides the common QUANTITY property for material-related objects such as Material and Reservation.

Relations

Quantity concepts

Reservation workflow

Creating or editing a reservation

Reservations are created manually by the user.

A reservation links a material to a task.

For a reservation to define its planned quantity correctly:

1. LK_MATERIAL must be set.
2. LK_TASK must point to the task requiring the material.
3. Status must still be Planned.
4. QTY_PLANNED must be greater than 0.
5. QTY_PLANNED must not exceed LK_MATERIAL.AvailableQuantity().

Confirmed reservations

When a reservation is confirmed, it contributes to the material's reserved quantity.

This affects the available quantity of the material.

Finishing a task

When a task is finished, the task logic calls CloseReservations().

The method processes active reservations for the task:

• if a reservation has status Confirmed, it is set to Issued
• otherwise, it is set to Cancelled

Usage in tasks

Reservations are the central link between material handling and task execution.

A reservation connects:

• the required material through LK_MATERIAL
• the task through LK_TASK
• the planned quantity through QTY_PLANNED
• the actually issued or consumed quantity through QUANTITY
• the reservation state through Status

This means that material usage is tracked at task level.

Example workflow

Step 1: Material master exists

A spare part is defined as a MaterialMaster.

Step 2: Material exists in a storage location

A Material object references the material master and a storage location.

Step 3: Reservation is created for a task

A user manually creates a Reservation and links the material to the task.

Step 4: Reservation is confirmed

The reservation status is changed to Confirmed.

After confirmation, the material's reserved quantity includes the reservation's planned quantity.

Step 5: Actual quantity is entered

The actually issued or consumed quantity is stored in Reservation.QUANTITY.

Step 6: Task is finished

When the task is finished, CloseReservations() is called.

The confirmed reservation is changed to Issued.

Validation and business rules

See also

• MRO (Plugin)
• MRO Objects (Client)
• MRO Implemented Objects
• MROMaintenancePlans