SAP PM Equipment Master: How to Bulk Import Mine Site Assets
A practical guide to preparing mine-site equipment records for SAP PM Equipment Master import via LSMW or BAPI_EQUI_CREATE — including field mapping, category codes, and common errors.
SAP PM Equipment Master imports require a different approach to mine-site data than most EAM platforms. This guide covers the complete import process — from field mapping to functional location hierarchy to the exact format LSMW and BAPI_EQUI_CREATE expect.
Key Takeaways
- SAP PM uses a functional location hierarchy (FLOC) to represent the mine's physical structure — this must be created before equipment can be assigned to it.
- Equipment category codes (M=Machine, E=Electrical, I=Instrument, V=Vehicle) determine which fields and classification views are available.
- LSMW is the standard bulk import tool for SAP PM Equipment Master — it requires a recording of the IE01 transaction.
- BAPI_EQUI_CREATE is the programmatic alternative — suitable for large volumes and automated imports.
- Manufacturer part numbers (MANU_PART) must match SAP's Material Master if you want automatic spare parts linkage.
SAP PM's Data Model for Mine Sites
SAP PM structures mine-site assets differently from most EAM platforms. Understanding the data model before you start an import will save you significant rework.
Functional Locations (FLOCs) represent the physical structure of the mine. A typical mining FLOC hierarchy looks like: Mine Site → Pit → Level → Processing Plant → Crusher → Conveyor. FLOCs must be created before equipment can be assigned to them. If your mine site does not have a FLOC hierarchy in SAP, creating one is the first step — not the last.
Equipment represents individual assets installed at functional locations. An excavator, a haul truck, a crusher — each is an Equipment record. Equipment can be moved between functional locations over time, and SAP PM tracks the installation history.
Equipment Categories determine which fields and classification views are available for each equipment record. For mine sites, the most common categories are: M (Machine/Mechanical), E (Electrical), I (Instrument/Control), V (Vehicle). The category must be set correctly at creation — it cannot be changed after the fact.
Required Fields for Equipment Master Import
EQUNR — Equipment number. Can be internal (SAP-assigned) or external (your asset number). If using external numbering, ensure your asset numbers are unique across the SAP client.
EQTYP — Equipment category (M, E, I, V, etc.). Must be set correctly at creation.
TPLNR — Functional location. Must reference an existing FLOC in the system.
HERSTELLER — Manufacturer name. Should match a vendor record in SAP if you want automatic warranty and spare parts linkage.
HERST_TYPNR — Manufacturer model/type number.
SERGE — Serial number. Used for warranty tracking and duplicate detection.
EQKTX — Equipment short description (40 characters). This is the primary description field visible in most SAP PM reports.
Try Struktive on your own data
Upload your equipment register and get back a normalised, EAM-ready export in under 90 seconds. No account required.
LSMW Import Process
LSMW (Legacy System Migration Workbench) is the standard tool for bulk Equipment Master imports. The process:
- Create an LSMW project and object for Equipment Master (transaction IE01).
- Record a sample IE01 transaction to capture the field mapping.
- Define source fields in your CSV.
- Map source fields to SAP fields.
- Run the LSMW steps: Read Data → Convert Data → Import Data.
- Review the import log for errors.
LSMW is reliable for one-off migrations but requires SAP Basis access and a working knowledge of the tool. For large volumes or automated imports, BAPI_EQUI_CREATE is the better choice.
Using Struktive for SAP PM Imports
Struktive generates a SAP PM-ready CSV with all required fields pre-populated, equipment category codes mapped from mining equipment categories, and a pre-flight report showing exactly which rows will fail before you touch SAP. The output is formatted for direct use with LSMW — upload your messy equipment register, download the SAP PM import file, and complete a clean import in a single session.