Describing Stocks Master Data

The image shows a scenario description for a lesson. It states that the user is responsible for defining the equipment authorizations for military units as part of the Table of Organization and Equipment (TOE). The lesson will cover the Defense and Security master data for this process and how to create and maintain it using the Defense and Security applications. The image also contains a visual representation of a military hierarchy, with different sized groups of people symbolizing the organizational structure.

In this lesson, we will complete the equipment part of the TOE.

The image explains that an FMPO (Force Management Planning Object) is a unique Defense and Security object used for planning the authorized materials of a force element or position as part of the Table of Organization and Equipment (TOE) or Mission Essential Equipment List (VEEL). It states that an FMPO is more generic than a specific material number, as it describes material on a capability level rather than referring to a specific product or NSN. The image also lists the key characteristics of an FMPO, including its structure, variants, hierarchy, and status-controlled nature.

A 5-ton truck is an example of an FMPO. The functional / operational requirement for a '5-ton truck' can be satisfied by multiple types of trucks, each with own material number.

When defining authorizations for 3 x '5-ton truck', the planner does not have to specify the make and model.

The decision (that is, what material will be issued to the unit) is only made during later steps of the logistic process.

The image shows a software application called Manage Flexible Material Planning Object that is used for creating and maintaining the FMPO (Force Management Planning Object) master data. The application displays a list of FMPO IDs and their descriptions, as well as other related information such as Interchangeability Code, FMPO Variant Description, and FMPO NSN Description. The user has the option to create new FMPO entries using the Create button.

The Manage Flexible Planning Object app provides filtering options for searching for existing FMPO and allows you to create a new FMPO.

A typical target user of this application is a material (category) owner - for example, Combat Land Mobility branch in Army Materiel Command.

The image shows a software application screen displaying details of a Force Management Planning Object (FMPO) with the ID 1000000013. The screen includes general information about the FMPO, such as its description, interchangeability code, and administrative details like creation and change dates. It also shows the variants associated with this FMPO, including their descriptions and status. The screen provides a comprehensive view of the FMPO master data, which is used for planning authorized materials as part of the Table of Organization and Equipment (TOE) or Mission Essential Equipment List (MEEL).

FMPO is created and maintained by the Manage Flexible Planning Object app.

FMPO ID can be created by the system, or be assigned manually by the user.

RIC ID is selected from a pre-defined list of NATO Reportable Item Codes.

Interchangeability Code is designed to reflect DODIC (for ammunition).

Sensitivity defines access rights to the FMPO.

The image shows a software application interface for displaying and managing Reportable Item Codes, which are used to classify different types of military equipment and materials. The application displays a hierarchical view of the Reportable Item Codes, organized by Main Group, Main Category, Functional Cat, Subcategory, Type, and Subtype. The image also includes a reference table that explains the different attributes associated with each Reportable Item Code, such as the Main Group, Main Category, Functional Cat, Subcategory, Type, and Subtype, along with example values for each attribute and the corresponding Reportable Item Code.

Reportable Item Code (RIC) is a formal NATO grouping of materials.

It is used for material reporting across different nations that may have different weapons and equipment that have the same functionality and provide the same outcome.

The RIC itself can be viewed in Display Reportable Item Code app and maintained in Change Reportable Item Code app.

The image explains that an FMPO refers to the functionality of an object from a planning perspective, and different products (materials) can provide this functionality. The key points about FMPO models are: a product may only be a model in one FMPO, a model must have a material master record, and models are used in logistic processes. The image shows an example FMPO for a Truck, 5 ton with three different models.

A product can be a model of only one FMPO.

One FMPO can have multiple models (for example, models can be differentiated by OEM and year of production, but share the same operational capability).

Models can be added or deleted from an active FMPO:

Adding a model means that actual inventory of that product will be counted against the authorization of the FMPO. This will be done when a new material is added (for example, a new model of laptop)
Deleting a model means that the inventory of that product will not be counted against the FMPO authorization anymore. This will be done when that model is obsolete, or in case the planner wants to assign that product as a model of another FMPO.

The image explains a Flexible Material Planning Object (FMPO), which represents an object's functionality for planning. FMPOs provide a rough planning level and summary of different models (products) that can fulfill the same functionality, such as a medium-sized truck. The models shown have detailed planning, material masters, inventory-management, and specific serial numbers/equipment IDs.

One FMPO can have multiple models.

Every model can have multiple equipment or serial numbers:

Authorizations are defined on FMPO level.
Purchase Requisitions, Purchase Orders and Stock Transfer Orders are typically done on the product (=model) level.
Actual inventory is managed on product or Serial Number level.

The image shows a command interface for a system called HMMWV, which appears to be related to some kind of vehicle or product management system. The table displays a list of products or models, including their product ID, description, list price, default planning, material status, moving average price, and standard price.

Although the models are maintained in the FMPO Variant facet, when a model is added for one of the variants, it is immediately replicated to all the other variants.

The price and other product attributes are taken from the Material Master.

The image is a diagram showing the components of an FMPO (Field Maintenance Parts Order) for a Heavy Expanded Mobility Tactical Truck (HEMTT). The diagram includes the HEMTT model, Mandatory Products, Optional Products, Mandatory FMPOs, Optional FMPOs, Mandatory ACPs, Optional ACPs, and Products ACPs. The diagram illustrates the relationship between these different components and how they are allocated together.

An FMPO may have the following:

Models, and / or
Mandatory accompanying parts of type FMPOs, and / or
Optional accompanying parts of type FMPOs, and / or
Mandatory accompanying parts of type Products, and / or
Optional accompanying parts of type Products.

At least one of the above must be filled.

The image shows a diagram explaining the concept of FMPO (Field Maintenance Parts Order) variants. It highlights that FMPO variants can have the same list of models but different lists of Accompanying Parts (ACPs). A component may also be included in multiple FMPO variants. The image also shows how FMPO variants enhance planning flexibility by allowing different sets of ACPs for different types of missions, geography, and gradual engineering changes, as well as supporting different platform configurations.

FMPO Structures are implemented through FMPO Variants. Although the models are identical across all the variants of the FMPO, every variant may have a different list of Accompanying Parts.

When you are adding a model in one variant, the system ensures that it is copied to all other variants of that FMPO.

It is possible to update the models and ACPs after the FMPO is active and assigned to force elements and positions. However, changes to ACPs do not impact existing assignment of the FMPO variant. See more details in the next lessons.

The image explains the responsibility of an FMPO (Field Maintenance Parts Order) and how it can be assigned to different organizational objects, such as Organizational Units, Positions, and Persons. It defines the Responsible Planner as the FE/Position/Person responsible for assigning the FMPO as authorized material, and the Material Owner as the FE/Position/Person responsible for maintaining the FMPO Master Data. The image also shows the relationships between the FMPO, Position, and Person, as well as a Force Element.

Responsibilities for FMPO include the responsibility to maintain FMPO master data (for example, the decision whether a new product is to be attributed as a model to an existing FMPO) and the responsibility to authorize the FMPOs to units and positions (for example, which unit will be authorized to the new 5.56 mm close-combat rifle). The former is modeled as the "Material Owner", while the latter is called "Responsible Planner".

FMPO as a Product

The image shows a detailed view of a product variant called HMMWV - Reconnaissance within a system. It displays information about the Responsible Planner and Material Owner, as well as details about the product such as Variant ID, Status, Product Group, and Ext. Product Group. The image also shows options to Deactivate and Generate Product for this variant.

The FMPO Variant can be used for the Purchase Requisition Process.

To enable that, the user has to explicitly generate a product for the FMPO Variant.

The product is not generated by default.

FMPO can be used to create a Purchase Requisition, and the planner does not have to specify the model (product) at this stage.

You only has to specify the product when you are converting the PREQ to an Order.

To enable the creation of the Purchase Requisition (PREQ) on FMPO level, a product (material master) should be created for that FMPO.

This STR item cannot be converted to a Purchase Order (PO) or Stock Transfer Order (STO), and must be swapped to one of the models, which is a real inventory managed item.

Note

Unlike the DFPS functionality, there is no automatic generation of the FMPO-Product in Defense and Security. It needs to be generated explicitly by the user.

Packing Instructions

Packing instructions are relevant when the FMPO is used as an Equipment Package (EPA) → More details in the relevant lesson.

The image shows the components of two FMPO (Field Maintenance Parts Order) variants for a HEMTT (Heavy Expanded Mobility Tactical Truck). Each variant has a lead end item (the HEMTT truck), as well as Mandatory and Optional accompanying parts and FMPOs. The image displays the different configurations of these components across the variants.

FMPOs can be grouped with or without a lead item. The grouping of FMPOs without a lead item (as can be seen in variants D, E, and F) can represent a set of loosely-coupled materials typically authorized together (former material containers). This becomes the basis for further planning processes in which that FMPO is to be used to quickly assign recurring groups of FMPOs.

The image explains that a Mandatory/Optional accompanying FMPO (Field Maintenance Parts Order) can have a complex structure of its own. The system is designed to handle combined and complex structures. The example provided is an Ambulance, which has a variety of Mandatory and Optional materials, FMPOs, and models. The structure illustrates how the FMPO relates to the different components, with Mandatory and Optional elements at each level.

Each FMPO ACP is an FMPO by itself, and can have a complete structure with its own optional and mandatory ACPs.

This is a recursive structure, and these FMPO ACPs can have their own structure as well.

The image explains the concept of Accompanying Parts (ACPs) and how they are assigned to FMPO (Field Maintenance Parts Order) variants. It states that ACPs are assigned together with the lead FMPO variant to simplify planning and ensure completeness. The authorized quantity specifies the quantity of an ACP-FMPO that should be allocated per FMPO-Variant assignment. Mandatory ACP FMPOs are automatically assigned by the system, while Optional ACP FMPO is a list of potential FMPOs that the planner can select from. The content of the ACP FMPO list can be changed after the FMPO is already assigned, but existing assignments will not be impacted.

Further facts about FMPO Accompanying Parts:

List of FMPOs that should be authorized automatically by the system when the FMPO-Variant is assigned to Force Element / Positions.
Each FMPO in this list can have a structure of its own.
The FMPO can often be mandatory (that is, must be authorized with the FMPO-Variant) or optional (can be selected by the planner as part of the FMPO-Variant assignment).

The image explains that ACP (Accompanying Parts) products are allocated together with the FMPO-Variant. Mandatory Products are automatically assigned by the system, while Optional items can be added by the user during the assignment process. The intent is to use these ACP-Products for consumables, hence the assignment parameters are Initial Required Quantity and Reorder Point. The image also shows a table with different FMPO-Variant details.

Facts about Products Accompanying Parts:

List of products that should be authorized automatically by the system once the FMPO-Variant is assigned to Force Element / Positions.
Each line can be mandatory or optional.
The initial required quantity and reorder point are parameters for the initial supply (see unit 3 lesson Y).

The image shows details about the HMMWV - Command product, including information about its Force Elements and Weights and Measurements. The Force Elements section lists an item called 11th Tank Battalion with a status of Planned and valid period from 22.06.2021 to 31.12.9999. The Weights and Measurements section provides details about two High Mob Multipurpose Wheeled Vehicles, including their net weight, weight unit, gross weight, length, width, and height.

Force Elements Assignments - the list of Force Elements to which this FMPO-Variant is assigned.

Weights and Measurements: data from the material master.

The image shows details related to the HMMWV - Command product, including its Work Breakdown Structure Elements, Network Activities, and Attachments. The Work Breakdown Structure lists a Zetland Force element, and the Network Activities section indicates no data is found. The Attachments section shows a Wiki-HMMWV attachment that was uploaded by GETZCVICH on 27-06-2021. The Classification section indicates that no classes have been assigned.

Further details are as follows:

Project System: An FMPO can be linked to WBS (for example, for cost collecting or analysis).
Classification: An FMPO Variant can have user defined attributes using the standard SAP Classification system.
Attachments: A simple facet is provided to attach documents like specifications to the FMPO variants. The documents are uploaded to SAP DMS (Document Management Server).

The image shows a workflow diagram for a process with various states and transition actions. The main states are Plan, Submitted, Approved, Rejected, Deactivated, and Active. The actions between these states include Submit, Approve, Reject, Deactivate, Resubmit, and Activate. The image also includes a table that summarizes the transitions between states based on the action taken.

An FMPO Variant must be set to an active status before it can be assigned to Force Elements or Positions.

The FEs or Positions themselves may be in any status.

The image explains how different DFPS planning objects, such as the Material Planning Object (MPO), Material Container (MC), Provisions Package (PPA), and Equipment Package (EPA), can be mapped into the new D&S FMPO object. It states that a simple MPO with 1 or more models became an FMPO with no ACPs, the operational and individual parts of a complex MPO are mapped into the FMPO Accompanying Parts section, the MPOs of a Material Container are mapped into the mandatory FMPO ACP section without Models, and the PPA list of materials is mapped into the FMPO mandatory/optional products ACP list.

FMPO is a superposition of the existing DFPS planning objects: Material Planning Object (MPO), Material Container (MC), Provisions Package (PPA) and Equipment Package (EPA).

The image shows details about an INFANTRY WEAPONS (MC) product, including its FMPO information, Accompanying Parts, and Mandatory Material Planning Objects (MPOs). The FMPO has only FMPO ACPs and no Models. The image also includes a table listing the Mandatory Material Planning Objects, their Descriptions, and other details.

The FMPO has two variants - one for a squad and the other for a platoon.

Each variant may have different FMPO ACPs with different quantities, and no Models.

The image shows details about an INFANTRY AMMO PACKAGE (PPA) product, including its FMPO information and Accompanying Parts. The FMPO has only Product ACPs and no Models or FMPO ACPs. The image also includes a table listing the Variants for this product.

The FMPO has two variants - one for a squad and the other for a platoon.

Each variant may have different Products ACPs with different quantities.

The image explains that FMPO (Flexible Material Planning Object) can be arranged in a hierarchy, especially during initial planning when multiple FMPOs need to be considered. It provides an example of an FMPO hierarchy for different types of ground effect vehicles, motor vehicles, trailers, and cycles. The image also states that the FMPO hierarchy is nation-defined and can be different from the NATO Reportable Item Code (RIC) hierarchy.

Managing FMPO Hierarchy is done using Manage Flexible Planning Object Hierarchy app.

While RIC is defined by NATO, FMPO hierarchy is master data that is defined by each nation, and can be arranged by own logic.

In this example, the split of Cargo Trucks over 20 ton is different:

RIC lists all the trucks in the same level.
The FMPO hierarchy example provides a first split based on mobility and a second one based on winch.

The FMPO hierarchy can be altered (that is, change to grouping concept) and the assignment of actual FMPOs to the parent can be adjusted.

Describing Stocks Master Data

Defense and Security: Master Data

FMPO as a Product

Packing Instructions