Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table

Lesson 1 of 5

Functional locations and the structure indicator

10 min

Listen to this lesson

0:00 / 8:21

A functional location is a hierarchical, multi-level structure that represents a technical system, a building or part of one. SAP's learning material lists three ways to structure it: by space (building 1, building 2), by technical criteria (press, press frame, press hydraulics) or by function or process (polymerization, condensation). Most manufacturing plants mix the first two. Contoso's Detroit plant goes plant, area, line, station.

The structure indicator

Labels are not free text. They follow a structure indicator, which has two parts. The edit mask controls which characters are allowed in each position and how they are grouped and separated. SAP uses A for alphabetic, N for numeric, X for alphanumeric and S for special characters. The hierarchy levels define where each level ends in the label and how many levels the structure can have. A label can be up to 40 characters, the maximum length of the edit mask.

Level 1: NNNN1710 — Detroit plant
Level 2: -AAA1710-ASM — assembly area; 1710-UTL — utilities
Level 3: -XX1710-ASM-L1 — rotor line 1; 1710-UTL-CA — compressed air
Level 4: -XXX1710-ASM-L1-W03 — winding station 3
Contoso's structure indicator CMCFL: edit mask NNNN-AAA-XX-XXX with four hierarchy levels.
The Sign-Off Table · thesignofftable.com/academy/sap-eam-201

Because the levels are defined in the mask, SAP can work out the superior functional location from the label itself: when Rosa creates 1710-ASM-L1-W03, the system knows its parent is 1710-ASM-L1, as long as that parent exists. Plan the mask carefully. SAP's documentation is clear that once a functional location exists for a structure indicator, its edit mask can no longer be changed. A conversion keeps Contoso's ECC structure indicators exactly as they are, so the decision was made years ago; a new plant, such as Wave 2's Monterrey plant 1910, would be a chance to use the same indicator consistently.

Creating a functional location

  1. Start IL01 (or create the location in the Manage Technical Objects app) and enter the structure indicator CMCFL.
  2. Enter the label, for example 1710-ASM-L1-W04. The system checks it against the edit mask.
  3. Fill in the General view: description, object type, class, manufacturer data where relevant.
  4. Fill in the Location view: maintenance plant, location, plant section.
  5. Fill in the Organization view: company code 1710, cost center, maintenance planning plant 1710, planner group, main work center.
  6. In the Structure view, confirm the superior functional location and whether equipment installation is allowed.
  7. Save, then check the hierarchy in the structural display IH01.
ViewKey fieldsWhy it matters later
GeneralDescription, object type, class, manufacturerSearch, reporting and classification
LocationMaintenance plant, location, plant sectionWho is physically responsible; address data
OrganizationCompany code, cost center, maintenance planning plant, planner group, work centerCopied into notifications and orders; drives settlement
StructureStructure indicator, superior functional location, installation allowedHierarchy and where equipment may be installed

Functional location master record views.

  1. Does the label match the edit mask?Yes → continue · No → the system rejects the label; check characters and separators
  2. Does the superior location exist?Yes → the new location is placed under it · No → create the higher levels first
  3. Should equipment be installed here?Yes → allow installation in the Structure view · No → leave it as a structural node only
Three questions when creating a new functional location.
The Sign-Off Table · thesignofftable.com/academy/sap-eam-201

Inheriting data from the level above

Because the label tells SAP where a new location sits, the system can copy data from the superior location when you create locations top-down: maintenance plant, cost center, planning plant and similar fields. SAP's classic documentation notes that this only works when the hierarchy is built from the top level downwards. After creation, the hierarchy is held in the superior functional location field of each master record, not re-read from the label. For testers, that means two checks: new locations should pick up the right defaults from their parent, and a location moved under a different parent must show the new parent in the structural display.

Building top-down lets each new location copy organizational data from its superior; the hierarchy is then held in the superior functional location field.
The Sign-Off Table · thesignofftable.com/academy/sap-eam-201

Name design is a business decision, not a Basis one. Before Monterrey's locations are built in Wave 2, Rosa wants the Mexican maintenance team to agree the area codes (ASM, UTL, and so on) with Detroit, so that one report can compare compressed air breakdowns across 1710, 1720 and 1910 by reading the same level of the label.

If every plant uses the same area codes at the same level, one report can compare compressed air breakdowns across Detroit, Chicago and Monterrey.
The Sign-Off Table · thesignofftable.com/academy/sap-eam-201

Fiori, GUI and the Public Edition

In SAP S/4HANA 2025, planners can work with technical objects in Fiori (Manage Technical Objects to create and change functional locations and equipment, Find Technical Object to search and navigate the structure) or in SAP GUI with the IL and IE transactions. The objects and tables are the same: functional locations in IFLOT (with texts and location data in related tables), equipment in EQUI, and time-dependent equipment data in EQUZ, which is where each usage period lives. In SAP S/4HANA Cloud Public Edition, the Fiori apps are the only way in, and structure indicators are set up through the configuration steps offered there rather than in the IMG.

What goes wrong in testingTypical causeCheck
Label rejected although it "looks right"Separator or character type does not match the edit mask (letter where N is defined)Compare the label position by position with the mask NNNN-AAA-XX-XXX
New location has no cost centerCreated bottom-up, so nothing was copied from the superior locationCreate the test structure top-down and check the Organization view
Location placed under the wrong parentSuperior location changed manually after creationRead the hierarchy in IH01, not the label
Monterrey labels do not fit the indicatorWave 2 team used a different area code lengthAgree the code list with Rosa before the Wave 2 build

Functional location defects and how to catch them.

Key points
  • Functional locations model places and systems in a hierarchy; Contoso goes plant, area, line, station.
  • The structure indicator combines an edit mask (A, N, X, S characters) and hierarchy levels; labels are up to 40 characters.
  • Once a functional location exists for a structure indicator, the edit mask cannot be changed.
  • Organization data on the location flows into orders and settlement.

Check your understanding · not graded

Lesson check

  1. 1. What two parts make up a structure indicator?

  2. 2. In an edit mask, what does the character N stand for?

  3. 3. Rosa wants to change the edit mask of CMCFL after Detroit's locations exist. What should she expect?

  4. 4. Which view of the functional location holds the cost center and maintenance planning plant?