# Mass Equipment Master Upload and Functional Location Installation Program

> A custom program that creates hundreds of equipment records from an Excel or CSV file with manufacturer, model, serial number, location and account assignment data when a new line or site goes live, and installs them at a functional location if requested. It checks everything in test mode first and stops duplicate serial numbers.

- Type: Program, Custom development, Mass upload
- Module: PM
- Estimated effort: M (4–6 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/programs/mass-equipment-master-data-upload-program/


## Why is the standard not enough?

IE01 creates one equipment; IL01 and IK01 are separate dialogs for functional locations and measuring points. When a new line goes live, hundreds of equipment records have to be created with serial number, manufacturer, location and installation data. LSMW recordings need technical skills and are not recommended in S/4HANA; the Migration Cockpit is meant for the initial data migration. Ongoing commissioning needs a templated upload with a test mode that the maintenance team can run on its own.

### Closest standard alternatives

- IE01: Creates one equipment; it does not read files or install in bulk.
- LSMW: Can load from files but needs technical setup; not recommended in S/4HANA.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| EQUI | Equipment general data: category, object type, manufacturer, model, serial number | Write | - | ECC + S/4 |
| EQKT | Equipment description (per language) | Write | - | ECC + S/4 |
| EQUZ | Time segment: planning plant, planner group, installation | Write | - | ECC + S/4 |
| ILOA | Location and account assignment: functional location, cost center | Write | - | ECC + S/4 |
| IFLOT | Check of the functional location for installation | Read | - | ECC + S/4 |

## BAPIs and functions used

- BAPI_EQUI_CREATE: Creates the equipment for each row
- BAPI_EQUI_INSTALL: Installs the equipment at the functional location
- BAPI_OBJCL_CREATE: Writes optional classification characteristics
- BAPI_TRANSACTION_COMMIT: Saves successful rows permanently
- BAPI_TRANSACTION_ROLLBACK: Rolls back changes in test mode and after an error

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| P_FILE | Upload file (XLSX or CSV) | Single value | - | Yes |
| P_TEST | Test mode (check without posting) | Checkbox | - | No |
| P_INSTAL | Install when a functional location is given | Checkbox | - | No |
| P_DUPSER | Duplicate check on manufacturer + serial number | Checkbox | - | No |

## Input file columns

| Column | Target field | Required |
|---|---|---|
| Equipment (blank = internal number) | EQUI-EQUNR | No |
| Equipment category | EQUI-EQTYP | Yes |
| Description | EQKT-EQKTX | Yes |
| Object type | EQUI-EQART | No |
| Manufacturer | EQUI-HERST | No |
| Model number | EQUI-TYPBZ | No |
| Manufacturer serial number | EQUI-SERGE | No |
| Construction year | EQUI-BAUJJ | No |
| Start-up date | EQUI-INBDT | No |
| Maintenance planning plant | EQUZ-IWERK | Yes |
| Planner group | EQUZ-INGRP | No |
| Cost center | ILOA-KOSTL | No |
| Functional location (installation) | ILOA-TPLNR | No |

## Result list columns

| Column | Source |
|---|---|
| Row | Calculated: Row number in the file |
| Equipment | EQUI-EQUNR |
| Functional location | ILOA-TPLNR |
| Status | Calculated: From the BAPI return messages: created, created and installed or error |
| Message | Calculated: First error or success message from the BAPI return table |

## How does the program work?

1. The file (XLSX or CSV) is read; the first row is skipped as the header.
2. Every row is checked: equipment category, object type, maintenance planning plant, planner group and cost center must exist in the system. When a functional location is given, it exists in IFLOT and allows equipment installation. If the same manufacturer and serial number already exist in EQUI, the row is stopped as a duplicate.
3. The equipment is created with BAPI_EQUI_CREATE: general data (description, object type, manufacturer, model, serial number, construction year, start-up date), location and account assignment (planning plant, planner group, cost center). When the equipment number is blank, an internal number is assigned.
4. When the functional location is filled, the equipment is installed there with BAPI_EQUI_INSTALL; a new time segment is opened in EQUZ and the location data in ILOA can be inherited from the functional location.
5. In test mode the BAPIs are called and rolled back with BAPI_TRANSACTION_ROLLBACK; in a real run BAPI_TRANSACTION_COMMIT is called after every successful row. If classification characteristics are needed, they are added to the template and written with BAPI_OBJCL_CREATE.
6. The result list shows the created equipment number, the functional location it was installed at and the message; failed rows can be downloaded as a separate file.

## Authorization objects

- I_SWERK: Technical object maintenance authorization by maintenance plant
- I_BEGRP: Authorization by technical object authorization group

## Frequently asked questions

### Can functional locations and measuring points be loaded as well?

Yes. Functional location (BAPI_FUNCLOC_CREATE) and measuring point uploads can be added as separate tabs with the same template logic, so the structure of a new line is built from one program in sequence. Each extra object increases the effort range.

### Can existing equipment be updated?

Yes. When the equipment number is filled and exists in the system, the row can be processed as an update with BAPI_EQUI_CHANGE; this option is enabled during installation.

### Can it be used on S/4HANA?

Yes. BAPI_EQUI_CREATE and BAPI_EQUI_INSTALL are supported on S/4HANA as well. The Migration Cockpit is recommended for the initial migration; this program is for the ongoing need during commissioning.

---
Let us build this program for your system: https://nekuhub.com/en/request-a-quote/?report=pm-equipment-master-upload
