SAP Installed Base Equipment ABAP SELECT Generator (EQUI)
OEMs that track delivered machines as equipment in SAP need a quick installed base list by model and build year. This generator produces an ABAP report skeleton that reads the EQUI table and lists matching records.
Fill in
ABAP report
REPORT ZR_INSTALLED_BASE_LIST.
PARAMETERS: p_herst TYPE equi-herst DEFAULT 'ACME MACHINERY',
p_typbz TYPE equi-typbz DEFAULT 'PRESS-500',
p_year TYPE equi-baujj DEFAULT '2015'.
START-OF-SELECTION.
SELECT equnr, matnr, sernr, serge, herst, typbz, baujj, inbdt
FROM equi
WHERE herst = @p_herst
AND typbz = @p_typbz
AND baujj >= @p_year
ORDER BY baujj, serge
INTO TABLE @DATA(lt_equi)
UP TO 500 ROWS.
IF sy-subrc <> 0.
WRITE: / 'No equipment found for the selection'.
RETURN.
ENDIF.
LOOP AT lt_equi INTO DATA(ls_equi).
WRITE: / ls_equi-equnr, ls_equi-matnr, ls_equi-serge, ls_equi-baujj, ls_equi-inbdt.
ENDLOOP.Uses inline declarations and the @ host variable syntax, which need ABAP 7.40 SP05 or higher. Field names are from the equipment master table EQUI (EQUNR equipment number, MATNR material, SERNR serial number, SERGE manufacturer serial number, HERST manufacturer, TYPBZ model, BAUJJ construction year, INBDT start up date). Verify field lengths and any customer enhancements in SE11 on your system. Extend with joins to EQUZ or ILOA for plant and location data. Test in a sandbox before production.
Installed base without custom ABAP
Optional: a review of read-only, natural language access to equipment and service data.
Optional. The tool and every export work without this. No spam.
How to use the generator
Fill the manufacturer, model and build year fields, set a maximum row count, and copy the code into transaction SE38. Activate the program and run it with F8. The selection screen shows your defaults and allows overrides. Start with a low row limit so a broad selection does not return the full table on a large system.
- Create the report in a Z namespace package
- Use SE11 to confirm field names
- Raise the row limit only after a test run
- Add authority checks before moving to production
What the query reads
EQUI holds the equipment master general data: the equipment number, the material and serial number it was created from, the manufacturer fields and the construction year. Location and plant data sit in related tables such as EQUZ and ILOA. This skeleton stays on EQUI so it runs everywhere, and you extend it with joins for the fields your service team uses.
Reading results
Each row is one piece of equipment. Matching on manufacturer serial number (SERGE) is useful for warranty and recall searches, while MATNR plus SERNR ties back to the delivered material. A blank start up date means the machine was never marked as commissioned in SAP, which is a data quality issue worth cleaning before warranty tracking.
Common mistakes
Manufacturer names are free text, so slight spelling differences hide records. Consider using a range or pattern in the selection. Another trap is the construction year being a character field, so comparisons are textual. Finally, do not export large lists without authority checks, since equipment may carry customer data.
Frequently Asked Questions
Which table holds SAP equipment data?
EQUI holds the equipment master general data. EQUZ holds time dependent data such as location assignments, and ILOA holds location and account assignment details. Descriptions are in EQKT.
Will this run on ECC?
Only if the system is on ABAP 7.40 SP05 or higher, because it uses inline declarations and escaped host variables. On older releases, rewrite the SELECT without the at signs and declare the internal table explicitly.
Can I use it for customer equipment?
Yes, but customer ownership is usually held in partner records. Join to the relevant partner table, or use the customer equipment in your service module, to filter by sold-to.
Is there a standard report instead?
Yes. IH08 lists equipment with many selection fields and IBase reports in service modules exist. Use a custom report only when standard selections or output do not meet the need.
If you need an installed base and warranty view across SAP and other systems without writing ABAP, we can discuss a read-only ERP query layer.
Related Tools
Installed Base Warranty Expiry SQL Query Generator
Build a T-SQL query that finds machines whose warranty ends within a chosen window, ready for service contract outreach.
Industry TemplatesOEM Aftermarket and Service Readiness Assessment
Ten questions that show whether your installed base data, spares, contracts and field service are ready to grow aftermarket revenue.
Compliance & ContractsMachinery Safety Standards Reference (Type A, B, C)
Quick lookup of the core machine safety standards, what each covers and where it fits in the A, B, C hierarchy.