# SAP Functional Location Structure Template > Source: https://netray.co/tools/sap-functional-location-structure-template > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Document your SAP PM functional location hierarchy, structure indicator and labeling rules in one clean design document. ## Category sap ## Erp SAP ECC / S/4HANA ## Audience - SAP PM consultant - Maintenance planner - Reliability engineer ## Tool **Kind:** template **Output:** document **Fields:** #### Company **Key:** company **Type:** text **Default:** Acme Precision Ltd #### Plant **Key:** plant **Type:** text **Default:** 1000 #### Prepared by **Key:** author **Type:** text **Default:** SAP PM lead #### Date **Key:** date **Type:** date **Default:** 2026-10-20 #### Structure indicator **Key:** indicator **Type:** text **Default:** ACME #### Edit mask **Key:** mask **Type:** text **Default:** XX-XXX-XXXX-XXX #### Level 1 meaning **Key:** level1 **Type:** text **Default:** Site or plant (e.g. 10) #### Level 2 meaning **Key:** level2 **Type:** text **Default:** Area or production line (e.g. MCH) #### Level 3 meaning **Key:** level3 **Type:** text **Default:** System or machine (e.g. P001) #### Level 4 meaning **Key:** level4 **Type:** text **Default:** Sub system or component group (e.g. DRV) #### Example label **Key:** example **Type:** text **Default:** 10-MCH-P001-DRV #### Functional location category **Key:** cat **Type:** select **Options:** - Plant location - Production line - Building - Utility - Other **Default:** Production line #### Naming rules **Key:** rules **Type:** textarea **Default:** Upper case only. No spaces. Codes are unique within the parent. Never reuse a retired code. **Blocks:** #### Functional Location Structure Design **Body:** Company: {{company}} Plant: {{plant}} Prepared by: {{author}} Date: {{date}} #### Structure indicator and edit mask **Body:** Structure indicator: {{indicator}} Edit mask: {{mask}} Maximum label length: 40 characters including separators Default category: {{cat}} Example label: {{example}} #### Hierarchy levels **Table:** **Columns:** - Level - Meaning - Example - Owner **Rows:** **0:** 1 **1:** {{level1}} **2:** 10 **3:** Plant maintenance manager **0:** 2 **1:** {{level2}} **2:** MCH **3:** Area engineer **0:** 3 **1:** {{level3}} **2:** P001 **3:** Reliability engineer **0:** 4 **1:** {{level4}} **2:** DRV **3:** Maintenance planner #### Naming and coding rules **Body:** {{rules}} #### Master data fields to maintain in IL01 **Table:** **Columns:** - Field - Rule - Mandatory - Source **Rows:** **0:** Description **1:** Short text, maximum 40 characters **2:** Yes **3:** Planner **0:** Functional location category **1:** Per this design **2:** Yes **3:** Design **0:** Structure indicator **1:** {{indicator}} **2:** Yes **3:** Design **0:** Superior functional location **1:** Parent label **2:** Yes below level 1 **3:** Hierarchy **0:** Planning plant **1:** {{plant}} **2:** Yes **3:** Plant **0:** Planner group **1:** Per area **2:** Recommended **3:** Planning **0:** Main work center **1:** Responsible craft **2:** Recommended **3:** Planning **0:** Cost center **1:** Owner of operating cost **2:** Yes **3:** Finance **0:** ABC indicator **1:** Criticality A, B or C **2:** Recommended **3:** Reliability #### Approvals **Signatures:** - Maintenance manager - SAP PM lead - Finance controller **Notes:** A functional location label can be up to 40 characters, and the edit mask and levels are defined in Customizing for the structure indicator. Confirm limits, category settings and authorizations in your own system. Check master data rules with your data owner before mass loading. ## Content **Intro:** The functional location hierarchy is the backbone of SAP Plant Maintenance. Every order, notification, task list and cost report hangs on it, so getting the structure right before load saves months of rework. This template gives you a clean design document to agree it. **Sections:** #### How to use the template **Body:** Fill in the plant, structure indicator, edit mask and what each level represents. The document updates as you type, and you can export it to Word or PDF for sign off. Start with the levels, not the codes. Agree what the business wants to report on: cost by area, downtime by line, backlog by system. Then decide the mask. The example label field helps stakeholders see what a real label looks like. Add the naming rules in plain words so the rules survive staff turnover. #### Design principles behind a good structure **Body:** A functional location represents a place or function in the plant, not a physical machine. Equipment is installed at it and can be replaced without losing the history of the location. Keep the hierarchy shallow enough to navigate, typically three to six levels. Use codes that carry meaning to the people who read them but never encode data that changes, like a cost center or a person. If you need to report by something that changes, use a classification, a field on the master record or a partner, not the label. **Bullets:** - One structure indicator per distinct plant type unless the mask truly differs - Do not put equipment serial numbers in the label - Reserve code ranges for future lines or expansions - Decide early whether the structure follows process, location or both #### Reading the mask and labels **Body:** The edit mask uses placeholders for each level, with separators between them, such as XX-XXX-XXXX-XXX. SAP uses the mask to check the label as you enter it and to derive the hierarchy automatically from the label if you set that up. Because the mask controls what can be entered, change it carefully after go live. Existing labels do not change when the mask changes, which can leave you with mixed formats. Test with two or three real lines before you load thousands of locations. #### Common mistakes **Body:** Frequent errors are building the hierarchy to mirror the org chart, which changes every reorganization, and putting one equipment per functional location without considering that functional locations exist to carry history across replacements. Another is leaving cost center and planner group blank, which breaks reporting and routing later. Finally, mass loading before the structure is approved turns every later change into a data migration. **Cta:** If you are migrating technical objects to SAP or cleaning up an existing hierarchy, Netray can help profile your source data and validate a load file before it reaches IL01. **Faq:** #### What is a functional location in SAP PM? **Answer:** A functional location is a technical object that represents a place or function in a plant, such as a line, system or process step. Equipment is installed at it, and the maintenance history stays with the location when the equipment is replaced. #### How long can a functional location label be? **Answer:** The label can be up to 40 characters including separators. The exact structure and edit mask are defined in Customizing by the structure indicator, so check your own settings before you design codes. #### How many levels should the hierarchy have? **Answer:** Most plants use three to six levels. Too few and you cannot report by area or system. Too many and planners struggle to navigate. Start from the reports and cost views your business needs, then add levels only where they answer a question. #### Which transaction creates a functional location? **Answer:** IL01 creates a functional location, IL02 changes it and IL03 displays it. For mass changes, IL05 provides a list display and edit view, and mass loads normally use a migration tool or LSMW. ## Search terms sap functional location structure, sap functional location template, sap pm functional location hierarchy, sap functional location edit mask, il01 create functional location, sap structure indicator, sap technical object hierarchy design --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json