21,306 bytes added,
16 June {{UnderConstructionStart}}
== MRO Material Management ==
<div style="border-left: 4px solid #36c; background-color: #f8f9fa; padding: 10px 12px; margin: 12px 0;">
'''Summary:''' The MRO material management concept describes how materials are defined, requested, reserved, and used in maintenance workflows. It explains the relationship between material-related objects such as <span style="font-family: Consolas, 'Courier New', monospace; color: #202122; background-color: #f8f9fa; border: 1px solid #c8ccd1; border-radius: 3px; padding: 1px 4px; white-space: nowrap;">Material</span>, <span style="font-family: Consolas, 'Courier New', monospace; color: #202122; background-color: #f8f9fa; border: 1px solid #c8ccd1; border-radius: 3px; padding: 1px 4px; white-space: nowrap;">Material Master</span>, and <span style="font-family: Consolas, 'Courier New', monospace; color: #202122; background-color: #f8f9fa; border: 1px solid #c8ccd1; border-radius: 3px; padding: 1px 4px; white-space: nowrap;">Reservation</span>, and how these objects are connected to tasks or work packages.
</div>
MRO material management is used to support maintenance work with the required spare parts, consumables, tools, or other material items.
In a maintenance workflow, users may need to know:
* which material is required for a task or work package
* whether the required material is available
* how much material is required
* how much material has already been reserved
* whether the material can be used
* whether a reservation is still open, fulfilled, or no longer relevant
The material management concept separates the general definition of a material from its actual usage in maintenance work.
A material can be defined centrally as master data and then used in different tasks, work packages, or reservations.
== Basic concept ==
The material management feature is built around the following main concepts:
{| class="wikitable"
! Concept
! Purpose
! Typical usage
|-
| <span style="font-family: Consolas, 'Courier New', monospace; color: #202122; background-color: #f8f9fa; border: 1px solid #c8ccd1; border-radius: 3px; padding: 1px 4px; white-space: nowrap;">Material Master</span>
| Defines the master data of a material.
| Used as the central reference for material identity, description, unit, and related master data.
|-
| <span style="font-family: Consolas, 'Courier New', monospace; color: #202122; background-color: #f8f9fa; border: 1px solid #c8ccd1; border-radius: 3px; padding: 1px 4px; white-space: nowrap;">Material</span>
| Represents a material item used in the MRO context.
| Used to describe material that can be assigned, requested, or consumed in maintenance workflows.
|-
| <span style="font-family: Consolas, 'Courier New', monospace; color: #202122; background-color: #f8f9fa; border: 1px solid #c8ccd1; border-radius: 3px; padding: 1px 4px; white-space: nowrap;">Reservation</span>
| Represents a request or reservation for a certain quantity of material.
| Used to reserve material for a task, operation, or work package.
|-
| Task or Work Package
| Represents the maintenance work that requires material.
| Material requirements and reservations are linked to the maintenance execution object.
|}
<div style="border-left: 4px solid #f0ad4e; background-color: #fff8e5; padding: 10px 12px; margin: 12px 0;">
'''Note:''' The exact object names, relation names, and property names may differ depending on the MRO configuration. This page describes the concept and should be aligned with the actual implementation before it is published as final technical documentation.
</div>
== Object overview ==
The following simplified overview shows how the material-related objects are typically connected.
{| class="wikitable"
! Object
! Related to
! Description
|-
| <span style="font-family: Consolas, 'Courier New', monospace; color: #202122; background-color: #f8f9fa; border: 1px solid #c8ccd1; border-radius: 3px; padding: 1px 4px; white-space: nowrap;">Material Master</span>
| <span style="font-family: Consolas, 'Courier New', monospace; color: #202122; background-color: #f8f9fa; border: 1px solid #c8ccd1; border-radius: 3px; padding: 1px 4px; white-space: nowrap;">Material</span>
| Provides the master data for a material.
|-
| <span style="font-family: Consolas, 'Courier New', monospace; color: #202122; background-color: #f8f9fa; border: 1px solid #c8ccd1; border-radius: 3px; padding: 1px 4px; white-space: nowrap;">Material</span>
| Task or Work Package
| Describes which material is needed or used for the maintenance activity.
|-
| <span style="font-family: Consolas, 'Courier New', monospace; color: #202122; background-color: #f8f9fa; border: 1px solid #c8ccd1; border-radius: 3px; padding: 1px 4px; white-space: nowrap;">Reservation</span>
| Material and Task or Work Package
| Reserves a specific quantity of material for a specific maintenance activity.
|}
== Material Master ==
=== Purpose ===
The Material Master represents the central master data record for a material.
It describes the material independently from a specific maintenance task or work package.
The Material Master is used to provide consistent information about materials across the MRO system.
This can include, for example:
* material number
* material name
* material description
* base unit of measure
* material group
* manufacturer information
* external ERP or SAP reference
* default storage or warehouse information
* default status information
<div style="border-left: 4px solid #36c; background-color: #f8f9fa; padding: 10px 12px; margin: 12px 0;">
'''Concept:''' The Material Master should be understood as the reusable definition of a material. It does not by itself describe that material is required for a specific task. The concrete usage is handled by material assignments, requirements, or reservations.
</div>
=== Typical responsibilities ===
The Material Master is typically responsible for:
* identifying a material uniquely
* providing the default description of the material
* defining the base unit in which the material is handled
* providing references to external systems
* allowing users to select the correct material when planning maintenance work
=== Example ===
A maintenance team regularly needs a specific oil filter.
The oil filter is defined once as a Material Master.
{| class="wikitable"
! Field
! Example value
|-
| Material number
| OF-10045
|-
| Name
| Oil Filter Type A
|-
| Description
| Standard oil filter for Pump Series A
|-
| Base unit
| Piece
|-
| Material group
| Spare Parts
|}
When a task or work package requires this oil filter, the task does not define the oil filter again from scratch. Instead, it references the existing Material Master or a material object based on it.
== Material ==
=== Purpose ===
A Material represents a material item used in MRO workflows.
Depending on the implementation, the Material object may either represent:
* a concrete material based on a Material Master
* a material requirement assigned to a task or work package
* a material item available for planning, reservation, or consumption
The Material object is used to bring material information into the maintenance workflow.
=== Relationship to Material Master ===
A Material is typically based on or linked to a Material Master.
The Material Master provides the general definition.
The Material object provides the MRO-specific usage context.
{| class="wikitable"
! Aspect
! Material Master
! Material
|-
| Main purpose
| Defines the material as master data.
| Uses the material in an MRO context.
|-
| Scope
| General and reusable.
| Workflow-specific or MRO-specific.
|-
| Example
| Oil Filter Type A.
| Oil Filter Type A required for Work Package 4711.
|}
=== Typical material information ===
A Material object may contain or reference information such as:
* material master reference
* material number
* name or description
* required quantity
* available quantity
* reserved quantity
* unit of measure
* material status
* storage location or warehouse
* reference to a task or work package
<div style="border-left: 4px solid #f0ad4e; background-color: #fff8e5; padding: 10px 12px; margin: 12px 0;">
'''Implementation check required:''' This page should be aligned with the actual MRO data model to clarify whether quantity fields are stored directly on the Material object, calculated from related Reservation objects, or received from an external system.
</div>
== Reservation ==
=== Purpose ===
A Reservation represents a request to reserve a specific quantity of material for maintenance work.
It connects material demand with a task, operation, or work package.
A reservation is used when material should be set aside or requested before the maintenance work is executed.
=== Typical reservation information ===
A Reservation usually contains:
* reference to the material
* reference to the task or work package
* requested quantity
* reserved quantity
* open quantity
* unit of measure
* reservation status
* requested date or required date
* storage location or warehouse
* external reservation number, if synchronized with an external system
=== Relationship to tasks or work packages ===
Reservations are created for maintenance work.
Depending on the workflow, a reservation may be linked to:
* a task
* an operation
* a work package
* a work order
* a work package template, if material requirements are predefined
The reservation allows users to see which material has been requested or reserved for the maintenance activity.
<div style="border-left: 4px solid #36c; background-color: #f8f9fa; padding: 10px 12px; margin: 12px 0;">
'''Example:''' A work package for pump maintenance requires two oil filters. A reservation is created for quantity 2 of the oil filter material. The maintenance team can then see that the material is required and should be available for the work package.
</div>
== Material quantity concepts ==
=== Material quantity ===
Material quantity describes how much of a material is required, available, reserved, or consumed.
The meaning of a quantity depends on the context in which it is used.
{| class="wikitable"
! Quantity concept
! Meaning
! Example
|-
| Required quantity
| Quantity needed to execute the task or work package.
| 2 oil filters are needed for pump maintenance.
|-
| Reserved quantity
| Quantity that has already been reserved for the task or work package.
| 2 oil filters are reserved for the work package.
|-
| Available quantity
| Quantity currently available for use or reservation.
| 15 oil filters are available in the warehouse.
|-
| Consumed quantity
| Quantity actually used during execution.
| 1 oil filter was used during the maintenance work.
|-
| Open quantity
| Quantity still missing or not yet reserved.
| Required quantity 5, reserved quantity 3, open quantity 2.
|}
=== Reserved quantity ===
Reserved quantity describes the amount of material that has been reserved for a task, operation, or work package.
It answers the question:
<div style="border-left: 4px solid #36c; background-color: #f8f9fa; padding: 10px 12px; margin: 12px 0;">
'''Question:''' How much of the required material has already been reserved for this maintenance work?
</div>
Example:
{| class="wikitable"
! Required quantity
! Reserved quantity
! Result
|-
| 5
| 0
| No material has been reserved yet.
|-
| 5
| 3
| The reservation is partially fulfilled.
|-
| 5
| 5
| The required material quantity is fully reserved.
|-
| 5
| 7
| More material is reserved than required. This may require review, depending on the business rules.
|}
<div style="border-left: 4px solid #d33; background-color: #fff5f5; padding: 10px 12px; margin: 12px 0;">
'''Potential issue:''' If the reserved quantity is greater than the required quantity, the case should be checked against the business rules. It may be valid in some workflows, but it can also indicate an incorrect reservation quantity.
</div>
== Material status ==
=== Purpose ===
Material status describes whether a material can currently be used in the maintenance workflow.
The material status can help users understand if a material is available, blocked, obsolete, or otherwise restricted.
=== Typical material statuses ===
The following statuses are examples and must be aligned with the actual MRO implementation.
{| class="wikitable"
! Status
! Meaning
! Effect
|-
| Available
| The material can be used or reserved.
| Users can select and use the material in maintenance workflows.
|-
| Reserved
| The material or part of its quantity is reserved.
| The material is already assigned to one or more maintenance activities.
|-
| Blocked
| The material must not be used.
| Users should not use the material for new reservations or work packages.
|-
| Obsolete
| The material is no longer intended for use.
| The material should be replaced by another material or removed from active workflows.
|-
| Out of stock
| No available quantity exists.
| The material cannot be fulfilled until stock is replenished.
|}
<div style="border-left: 4px solid #f0ad4e; background-color: #fff8e5; padding: 10px 12px; margin: 12px 0;">
'''Note:''' The exact status values must be taken from the actual MRO status model. This section should not introduce status values that do not exist in the implementation.
</div>
== Reservation status ==
=== Purpose ===
Reservation status describes the current state of a material reservation.
It helps users understand whether a reservation is still open, partially fulfilled, fulfilled, cancelled, or completed.
=== Typical reservation statuses ===
The following statuses are examples and must be aligned with the actual MRO implementation.
{| class="wikitable"
! Status
! Meaning
! Typical situation
|-
| Open
| The reservation has been created but not yet fulfilled.
| Material has been requested, but no quantity has been reserved yet.
|-
| Partially Reserved
| Only part of the required quantity has been reserved.
| Required quantity is 5, reserved quantity is 3.
|-
| Reserved
| The full required quantity has been reserved.
| Required quantity is 5, reserved quantity is 5.
|-
| Issued
| The material has been handed out or issued for execution.
| The maintenance team has received the material.
|-
| Consumed
| The material has been used during execution.
| The material usage has been confirmed.
|-
| Cancelled
| The reservation is no longer required.
| The work package was cancelled or the material is no longer needed.
|}
=== Status calculation ===
Depending on the implementation, the reservation status may be:
* set manually by the user
* calculated from quantity values
* updated by the system during workflow transitions
* synchronized from an external ERP or warehouse system
Example status calculation:
{| class="wikitable"
! Condition
! Possible reservation status
|-
| Reserved quantity is 0
| Open
|-
| Reserved quantity is greater than 0 and lower than required quantity
| Partially Reserved
|-
| Reserved quantity is equal to required quantity
| Reserved
|-
| Reservation was cancelled
| Cancelled
|}
<div style="border-left: 4px solid #f0ad4e; background-color: #fff8e5; padding: 10px 12px; margin: 12px 0;">
'''Implementation check required:''' The final wiki page should document whether reservation status is calculated in MRO, entered manually, or imported from an external system.
</div>
== Usage in tasks or work packages ==
=== Purpose ===
Tasks and work packages represent maintenance work.
Material management is used to define and track which materials are required for this maintenance work.
Material usage can occur during different phases of the maintenance process.
{| class="wikitable"
! Phase
! Material handling
! Example
|-
| Planning
| Required materials are selected and planned.
| The planner adds two oil filters to the pump maintenance work package.
|-
| Preparation
| Required materials are reserved or requested.
| A reservation is created for two oil filters.
|-
| Execution
| The maintenance team uses the material.
| One oil filter is installed during the task.
|-
| Completion
| Actual material usage is confirmed.
| The consumed quantity is recorded.
|}
=== Material requirements on work packages ===
A work package may contain one or more material requirements.
Each material requirement describes which material is needed and in which quantity.
Example:
{| class="wikitable"
! Work package
! Material
! Required quantity
! Unit
|-
| Pump Maintenance WP-4711
| Oil Filter Type A
| 2
| Piece
|-
| Pump Maintenance WP-4711
| Lubricating Oil
| 5
| Liter
|}
=== Material requirements on tasks ===
If material is linked to individual tasks, the material requirement can be more precise.
Example:
{| class="wikitable"
! Task
! Material
! Required quantity
! Unit
|-
| Replace oil filter
| Oil Filter Type A
| 1
| Piece
|-
| Refill oil
| Lubricating Oil
| 5
| Liter
|}
This allows the system and users to understand exactly which material is required for each task.
=== Reservations for work packages ===
A reservation may be created for a complete work package.
This is useful when the material should be prepared for the whole maintenance activity.
Example:
A work package contains three tasks.
The planner creates one material reservation for all required material of the work package.
The warehouse prepares the material before the work package starts.
=== Reservations for tasks ===
A reservation may also be created for a specific task.
This is useful when material usage should be tracked at task level.
Example:
Task: Replace oil filter
Required material: Oil Filter Type A
Required quantity: 1
Reservation: 1 Oil Filter Type A
== Example workflow ==
=== Scenario ===
A pump requires planned maintenance.
The work package contains one task for replacing an oil filter.
=== Step 1: Material Master exists ===
The oil filter is defined as a Material Master.
{| class="wikitable"
! Field
! Value
|-
| Material number
| OF-10045
|-
| Name
| Oil Filter Type A
|-
| Base unit
| Piece
|}
=== Step 2: Material is assigned to the task ===
The task requires one oil filter.
{| class="wikitable"
! Task
! Material
! Required quantity
|-
| Replace oil filter
| Oil Filter Type A
| 1
|}
=== Step 3: Reservation is created ===
A reservation is created for the required material.
{| class="wikitable"
! Reservation
! Material
! Required quantity
! Reserved quantity
! Status
|-
| RES-90001
| Oil Filter Type A
| 1
| 1
| Reserved
|}
=== Step 4: Material is used during execution ===
During execution, the oil filter is installed.
The consumed quantity is recorded, if supported by the implementation.
{| class="wikitable"
! Material
! Reserved quantity
! Consumed quantity
! Result
|-
| Oil Filter Type A
| 1
| 1
| Material was fully used.
|}
=== Step 5: Work is completed ===
The task or work package is completed.
The material reservation can then be considered completed, consumed, or closed, depending on the workflow.
== Important rules and open implementation points ==
<div style="border-left: 4px solid #f0ad4e; background-color: #fff8e5; padding: 10px 12px; margin: 12px 0;">
'''Open point:''' The final documentation should be aligned with the real object model. In particular, relation names, property names, status values, and quantity calculation rules should be verified before the page is published.
</div>
The following information is required to finalize this page precisely:
{| class="wikitable"
! Topic
! Required information
! Why it matters
|-
| Object names
| Exact class names for Material, Material Master, and Reservation.
| Needed to document the real data model instead of generic concepts.
|-
| Relation names
| Exact relation names between Material, Material Master, Reservation, Task, Work Package, and Work Order.
| Needed for technical accuracy.
|-
| Quantity properties
| Exact property names for required quantity, reserved quantity, available quantity, consumed quantity, and open quantity.
| Needed to explain where quantities are stored and how they are calculated.
|-
| Status properties
| Exact property names and allowed values for Material status and Reservation status.
| Needed to avoid inventing unsupported status values.
|-
| Status logic
| Whether statuses are manual, calculated, workflow-driven, or imported from an external system.
| Needed to explain system behavior correctly.
|-
| ERP integration
| Whether materials and reservations are synchronized with SAP or another ERP system.
| Needed to document external references, synchronization rules, and ownership of data.
|-
| Usage level
| Whether material is assigned to tasks, operations, work packages, work orders, or multiple levels.
| Needed to describe the actual workflow correctly.
|-
| Reservation creation
| Whether reservations are created manually, automatically, from templates, or by an external system.
| Needed to explain the user workflow and automation.
|-
| Consumption handling
| Whether consumed quantities are recorded in MRO.
| Needed to document execution and completion behavior.
|-
| Validation rules
| Rules such as required quantity must be greater than 0, reservation cannot exceed available stock, or blocked material cannot be reserved.
| Needed to document important restrictions and error cases.
|}
{{UnderConstructionEnd}}