Post

EPLAN Form Components Reference

A beginner-friendly overview of the structure and components of EPLAN form files (`.f??`), including the anatomy of a form page and the meaning of common property placeholders.

EPLAN Form Components Reference

EPLAN Electric P8 — Form Components Reference

Software: EPLAN Electric P8 Topic: Form file structure, anatomy, and property placeholders Level: Beginner Overview


What is a Form in EPLAN P8?

A form in EPLAN P8 is a template file that defines how an auto-generated report page looks and what data it displays. Think of it as a page layout blueprint — it tells EPLAN where to put data, how to format it, and which properties to pull from the project database.

1
2
3
4
Project Data  +  Form Template  =  Generated Report Page
(your devices,    (.f?? file)       (terminal list, BOM,
 terminals,                          cable diagram, etc.)
 cables, etc.)

Forms are separate from your schematic data. You can change a form without touching your project, and the next time you generate reports, the output will look different — but the underlying engineering data stays the same.


Form File Naming Convention

EPLAN form files use the .f?? extension where the number indicates the report type:

ExtensionReport Type
.f00Title page / Cover sheet
.f01Table of contents
.f04Cable diagram / Cable overview
.f05Summarized parts list
.f06Device tag list
.f08Structure identifier overview
.f10Terminal-strip overview
.f11Terminal diagram
.f17Connection list
.f22PLC diagram
.f30P&ID / Piping overview
.f31Pre-planning: Pipe class overview
.f32Pre-planning: Planning object overview
.f33Pre-planning: Loop diagram
.f34Pre-planning: Substance overview

The number in the extension is fixed by EPLAN — it determines which type of data the form can access. A .f11 form can only be used for terminal diagrams; it cannot be assigned to a parts list report.

File Location

1
%APPDATA%\EPLAN\Electric P8\{version}\Forms\

Form files are part of the EPLAN master data, not the project itself. They can be shared across multiple projects.


Form File Anatomy

A form file is made up of several visual and logical components arranged on a page canvas inside the Form Editor.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
┌──────────────────────────────────────────────────────┐
│                    FORM PAGE                         │
│  ┌────────────────────────────────────────────────┐  │
│  │              HEADER / TITLE BLOCK              │  │
│  │  Project name | Drawing number | Revision      │  │
│  └────────────────────────────────────────────────┘  │
│  ┌────────────────────────────────────────────────┐  │
│  │                TABLE HEADER ROW                │  │
│  │  Tag | Description | Article No. | Qty         │  │
│  └────────────────────────────────────────────────┘  │
│  ┌────────────────────────────────────────────────┐  │
│  │              ROW TEMPLATE (repeating)          │  │
│  │  %D  |  %T        |  %BN          |  %MC       │  │
│  └────────────────────────────────────────────────┘  │
│  ┌────────────────────────────────────────────────┐  │
│  │                   FOOTER                       │  │
│  │  Page %P of %PT  |  Date %DA  |  Scale         │  │
│  └────────────────────────────────────────────────┘  │
└──────────────────────────────────────────────────────┘

The Four Main Areas

1. Title Block (Header) The border frame around the page containing project metadata. Usually appears at the bottom or right edge of the page. Contains static labels (text you type) and dynamic placeholders (variables that fill in automatically).

2. Table Header Row A static row of column labels — e.g., “Device Tag”, “Description”, “Article Number”. This text is fixed and does not change between projects.

3. Row Template (Data Row) The most important part of a report form. This is the repeating row that EPLAN copies once for each data record (each terminal, each cable, each device). It contains property placeholders that are replaced with real values when the report is generated.

4. Footer Optional area at the bottom of the page for page numbers, dates, revision marks, and company information.


Form Components in Detail

Static Text

Plain text labels you type directly onto the form canvas. These never change — they are the same on every generated page.

1
Example:  "Device Tag"   "Description"   "Article No."

Lines and Borders

Graphical elements (horizontal lines, boxes, frames) used to create the table structure and title block border. Drawn using the line tools in the Form Editor.

Property Placeholders

The dynamic elements of a form. These are special codes written as %XX or <property name> that EPLAN replaces with real data from the project when generating the report. See the full reference in the next section.

Special Areas

Defined regions on the form that tell EPLAN where to place the repeating data rows, where the header ends, and where the footer begins. These boundaries are set using area markers in the Form Editor.

Area MarkerPurpose
Row areaDefines the repeating data row template
Header areaContent above the data rows
Footer areaContent below the data rows
Title block areaThe page border frame

Property Placeholders (Variables)

Property placeholders are codes embedded in the form that EPLAN replaces with real project or device data during report generation. They are the core of what makes a form dynamic.

How They Look in the Form Editor

In the Form Editor, placeholders appear as text elements with a special code:

1
2
3
%D          →  becomes  →  =GB1+ET1-K1     (device tag)
%T          →  becomes  →  Main contactor  (description)
%P          →  becomes  →  5               (page number)

Common Placeholder Reference

Project-Level Placeholders

These pull data from the project properties (same value on every page).

PlaceholderPropertyExample Output
%PNProject nameEPLAN_Sample_Project_Education
%CNCompany nameAcme Engineering GmbH
%DACurrent date11.03.2026
%CRCreated byJ. Smith
%APApproved byM. Mueller
%RERevisionRev. 03

Page-Level Placeholders

These pull data specific to the current page.

PlaceholderPropertyExample Output
%PCurrent page number7
%PTTotal page count24
%PDPage descriptionTerminal diagram X1
%PPPage name / designator=GB1+ET1/7
%SCDrawing scale1:1

Device / Component Placeholders

Used in the row template of device lists, parts lists, and tag lists. Repeated once per device.

PlaceholderPropertyExample Output
%DDevice tag (full)=GB1+ET1-K1
%TDescription / function textMain contactor 11kW
%BNArticle / part number3RT2026-1AP00
%BHManufacturerSiemens
%MCQuantity5
%FTDevice typeContactor

Terminal Placeholders

Used in terminal diagram and terminal-strip overview forms (.f10, .f11).

PlaceholderPropertyExample Output
%TNTerminal designationX1:5
%TCTerminal typeCLIPLINE 2.5
%TTTarget (connection to)=GB1+ET1-K3:14
%TWWire colorBK (Black)
%TCSWire cross-section1.5 mm²
%TCNCable nameW5

Cable Placeholders

Used in cable diagram and cable overview forms (.f04).

PlaceholderPropertyExample Output
%CNCable designationW1
%CTCable typeNYCWY 3×1.5mm²
%CLCable length15 m
%CFCable from (source)=GB1+ET1-X1:1
%CTOCable to (destination)=GB2+MCC-X2:3
%CSHShieldedYes

PLC Placeholders

Used in PLC connection diagram forms (.f22).

PlaceholderPropertyExample Output
%PAPLC addressI0.0
%PSSignal nameEmergency_Stop_S1
%PCCard designationDI 32×24VDC
%PSLSlot number2
%PCHChannel number0

Placeholder Syntax Rules

  1. Case sensitive%D and %d may behave differently depending on context
  2. Must be inside a text element — placeholders only work when placed as text on the form canvas, not in graphical elements
  3. Row template context — device/terminal/cable placeholders only work inside the defined row area of the form
  4. Project placeholders — work anywhere on the form including the title block
  5. Unresolved placeholders — if a placeholder has no matching data, EPLAN leaves it blank or shows a ? depending on settings

Simple Example: Parts List Row

A row template in a summarized parts list form (.f05) might look like this in the Form Editor:

1
| %D          | %T                  | %BN           | %BH      | %MC  |

When EPLAN generates the report, each device becomes one row:

1
2
3
| =GB1+ET1-K1 | Main contactor 11kW | 3RT2026-1AP00 | Siemens  |  5   |
| =GB1+ET1-F1 | Motor circuit breaker| 3RV2021-4AA10 | Siemens  |  1   |
| =GB1+ET1-Q1 | Main isolator       | 3LD2203-0TK53 | Siemens  |  1   |

How to View and Edit a Form

  1. In EPLAN P8, go to Utilities → Forms → Open
  2. Browse to %APPDATA%\EPLAN\Electric P8\{version}\Forms\
  3. Select the .f?? file you want to inspect
  4. The Form Editor opens — a graphical canvas where you can see all text elements, placeholders, lines, and area markers
  5. Double-click any text element to see or edit its placeholder code
  6. Save and close, then regenerate reports to see the effect

⚠️ Always keep a backup copy of the original form before making changes.


Summary

ConceptWhat It Is
Form file (.f??)Template that defines a report page layout
File extension numberDetermines which report type the form belongs to
Static textFixed labels that never change
Property placeholder%XX code replaced with real data on generation
Row templateRepeating area — one copy per data record
Title blockPage border with project metadata
Form EditorEPLAN tool used to view and modify form files

FileDescription
eplan_p8_project_structure.jsonFull metadata for all 16 project report folders
README.mdGeneral project structure reference
README_Interactive_vs_AutoGenerated.mdInteractive vs. auto-generated page types
README_Form_Components.mdThis file

EPLAN Electric P8 — Engineering Reference Documentation

This post is licensed under CC BY 4.0 by the author.