Customizing in SAP S/4HANA Asset Management PDF

S4133 Customizing in SAP S/4HANA Asset Management.. PARTICIPANT HANDBOOK INSTRUCTOR-LED TRAINING. Course Version: 14 Course Duration: 3 Day(s) e-book Duration: 7 Hours 50 Minutes Material Number: 50152967 SAP Copyrights, Trademarks and Disclaimers © 2020 SAP SE or a...

S4133 Customizing in SAP S/4HANA Asset Management.. PARTICIPANT HANDBOOK INSTRUCTOR-LED TRAINING. Course Version: 14 Course Duration: 3 Day(s) e-book Duration: 7 Hours 50 Minutes Material Number: 50152967 SAP Copyrights, Trademarks and Disclaimers © 2020 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see http://global12.sap.com/ corporate-en/legal/copyright/index.epx for additional trademark information and notices. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. This course may have been machine translated and may contain grammatical errors or inaccuracies. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions. Typographic Conventions American English is the standard used in this handbook. The following typographic conventions are also used. This information is displayed in the instructor’s presentation Demonstration Procedure Warning or Caution Hint Related or Additional Information Facilitated Discussion User interface control Example text Window title Example text © Copyright. All rights reserved. iii © Copyright. All rights reserved. iv Contents vi Course Overview 1 Unit 1: UI Configuration 2 Lesson: Configure SAP Fiori Launchpad 13 Lesson: Summarizing Customizing Settings - UI 17 Unit 2: Organization 18 Lesson: Plants 24 Lesson: Maintenance Work Centers 28 Lesson: Summarizing Customizing Settings - Organization 33 Unit 3: Notifications 34 Lesson: Notification Type 42 Lesson: Summarizing Customizing Settings - Notifications 49 Unit 4: Orders 50 Lesson: Order Type 58 Lesson: Material Planning 63 Lesson: Scheduling 67 Lesson: Printing 70 Lesson: Completion Confirmation and Technical Completion 73 Lesson: Summarizing Customizing Settings - Orders 83 Unit 5: Controlling 84 Lesson: Calculation 94 Lesson: Settlement 102 Lesson: Summarizing Customizing Settings - Controlling © Copyright. All rights reserved. v Course Overview TARGET AUDIENCE This course is intended for the following audiences: Project Manager Super / Key / Power User © Copyright. All rights reserved. vi  UNIT 1 UI Configuration Lesson 1 Configure SAP Fiori Launchpad 2 Lesson 2 Summarizing Customizing Settings - UI 13 UNIT OBJECTIVES Check Architecture Check roles, catalogs, and groups (FES) Check roles (BES) Summarizing Customizing Settings © Copyright. All rights reserved. 1  Unit 1 Lesson 1 Configure SAP Fiori Launchpad LESSON OBJECTIVES After completing this lesson, you will be able to: Check Architecture Check roles, catalogs, and groups (FES) Check roles (BES) Architecture Figure 1: SAP S/4HANA and User Experience (UX) SAP S/4HANA is a new product that aims to achieve a modern, state-of-the-art UI technology with its simplified, browser-based approach of SAP Fiori. This is true for both deployment options: cloud and on premise. Cloud In this context, the client type SAP Fiori Launchpad (FLP) is the first choice. Within SAP Fiori Launchpad different UI technologies can be used: SAPUI5, Web Dynpro ABAP and SAP GUI for HTML. On premise © Copyright. All rights reserved. 2  Lesson: Configure SAP Fiori Launchpad For the on premise deployment model, the client type SAP Fiori Launchpad (FLP) also is the first choice. However, it is also possible to run SAP S/4HANA On Premise together with the traditional SAP GUI for Windows. As an alternative to SAP Fiori Launchpad and SAP GUI for Windows the SAP Business Client can also be used. Note: In this document the abbreviation FLP is used instead of SAP Fiori Launchpad. Figure 2: SAP Fiori Launchpad SAP Fiori Launchpad (FLP) is designed to be the central entry point for all deployment models. FLP is a role-driven frontend and consists of Tile Groups which can be flexibly put together based on Tile Catalogs. Which tile catalogs are available for which user is determined via the role assignment on the Frontend Server (FES). This means that SAP S/4HANA On Premise has a 3–tier architecture: FLP running in a browser as the frontend for the user Frontend Server (FES) with Fiori roles Backend Server (BES) with backend roles © Copyright. All rights reserved. 3 Unit 1: UI Configuration Figure 3: FLP Architecture FLP runs in almost all browsers that are available on the market. Please check the SAP documentation for supported versions. When logging on to FLP, the user first connects to the frontend server (FES). The FES acts as sort of hub for one or several backend systems and contains the Fiori-specific apps, roles, and services. Communication between the FLP and the FES is based on the HTTPS protocol, as well as on a set of OData services. Therefore the required OData services must be activated on the FES. Note: Open Data Protocol (OData) is a Web protocol for querying and updating data, applying and building on Web technologies, for example, HTTP, to provide access to information from a variety of applications and services. Because OData services are easily utilized on different platforms, you can use this service to build cross- platform Web and mobile applications. When clicking on a tile in the FLP, the user executes an application. The code of these applications in many cases is located on the backend system (BES). Therefore the user must be able to log on to the backend system and must be authorized to run the application. Communication between the FES and the BES is based on Remote Function Call (RFC). Therefore, the user needs certain RFC authorizations. © Copyright. All rights reserved. 4  Lesson: Configure SAP Fiori Launchpad Figure 4: Application Types Each tile has a specific application type with a specific UI technology: Transactional apps: Usage of ABAP to provide the classic approach for functions of a business system Analytical apps: Usage of analytical capabilities of SAP HANA to provide insights in business data Fact Sheet apps: Usage of enterprise search capabilities of SAP HANA to provide search results All tiles are delivered via SAP Fiori catalogs located on the FES. Which tiles are actually displayed in FLP is determined via Fiori tile groups. Fiori catalogs and Fiori tile groups need to be assigned to PFCG roles on the FES. These roles will then be assigned to the user. Most applications in SAP S/4HANA Asset Management are transactional apps. However, there is a variety of transactional apps using different UI technologies: Transactional/SAPUI5: These are the new apps relying on SAPUI5 apps and OData services located on the FES. Transactional/WDA: WDA stands for Web Dynpro ABAP and relies on Web applications that must be activated via business functions (BF) on the BES. Transactional/SAP GUI: These apps execute a traditional transaction on the BES – displayed in FLP via SAP GUI for HTML. © Copyright. All rights reserved. 5 Unit 1: UI Configuration Figure 5: Software The following steps on the FES are necessary for work with Fiori apps: Install backend component Install product-specific UI component on the backend Install frontend component on the frontend server Implement necessary SAP Notes Activate OData services on the frontend server Activate SAPUI5 apps on the frontend server Check/create roles containing Fiori catalogs and Fiori tile groups Assign roles to users Assign OData service authorizations (backend / frontend) The following steps on the BES are necessary for work with Fiori apps: Install the required software components/products Implement app on the back end (additional steps might be required, for example, create selection variants, activate workflow tasks, assign responsible employees, link SAP user and personnel number, etc.) Check/create roles containing transactions, WDA (Web Dynpro ABAP) apps, and their authorizations Assign roles to users Activate business functions for WDA apps Business functions The functionality of SAP EAM WDA is shipped with the following business functions: © Copyright. All rights reserved. 6  Lesson: Configure SAP Fiori Launchpad LOG_EAM_SIMPLICITY LOG_EAM_SIMPLICITY_2 LOG_EAM_SIMPLICITY_3 LOG_EAM_SIMPLICITY_4 LOG_EAM_SIMPLICITY_5 LOG_EAM_SIMPLICITY_6 LOG_EAM_SIMPLICITY_7 LOG_EAM_SIMPLICITY_8 Roles, Catalogs, and Groups (FES) Figure 6: Frontend Roles Fiori catalogs and Fiori tile groups can be created or modified using the SAP Fiori launchpad designer. Customers can create their own catalogs and tile groups. Fiori catalogs contain all the apps that a certain user or group of users should have access to. These apps are not necessarily displayed in the FLP from the start, but they are available for personalization by the user. Fiori tile groups consist of a headline and a set of tiles. The actual FLP interface for a given user at a given time is made up of a sequence of tile groups. Each tile group represents a kind of a menu and is displayed automatically in FLP if it is assigned to a role. In addition, the user can create his or her own tile groups during personalization. Tile groups can either be organized in a separate role (separate from catalogs) or they can be part of the roles containing the catalogs, as is the case in the standard roles. © Copyright. All rights reserved. 7 Unit 1: UI Configuration Fiori catalogs and Fiori tile groups are assigned to PFCG roles on the FES. You can copy the standard roles to create your own role. Standard roles in SAP S/4HANA Asset Management are: SAP_BR_EMPLOYEE_MAINTENANCE – Employee SAP_BR_MAINTENANCE_PLANNER – Maintenance Planner SAP_BR_MAINTENANCE_PLANNER_RSH – Maintenance Planner - Resource Scheduling SAP_BR_MAINTENANCE_TECHNICIAN – Maintenance Technician Once your roles are defined, they are assigned to the user on the FES. Figure 7: SAP Fiori Launchpad Designer Fiori catalogs, Fiori tile groups, and individual tiles can be viewed and modified using the SAP Fiori launchpad designer. A catalog contains the complete set of tiles that is available for a given area. A group contains a set of tiles to be displayed for a certain user. You can add tiles to groups from catalogs. You can also edit the properties of a group. You can specify that a group cannot be personalized by the end user. A tile contains a so-called target mapping in which the application type and the application to be used are specified. © Copyright. All rights reserved. 8  Lesson: Configure SAP Fiori Launchpad Note: SAP provides predefined tile groups for SAP S/4HANA Asset Management with the following technical naming convention: SAP_EAM_BCG_... Personalization of a group includes the ability to delete or move tiles, and to add tiles to the group. To assign tiles to a tile group, proceed as follows: 1. Provide tiles via a catalog. 2. Change an existing tile group or create a new tile group, if necessary. 3. Add a new tile by selecting it via a catalog. Figure 8: Personalize SAP Fiori Launchpad You can personalize the SAP Fiori Launchpad based on the Fiori catalogs that are assigned to your user on the FES. Roles (BES) Backend Roles © Copyright. All rights reserved. 9 Unit 1: UI Configuration Figure 9: Backend Roles The same user who is configured on the FES must also be configured on the BES. First, you need to create PFCG roles on the BES that contain the necessary transactions, Web Dynpro ABAP (WDA) apps, and other app types if necessary – as well as the necessary authorizations. As on the FES, you can copy the available standard roles to create your own roles and modify them as needed. The standard roles starting with SAP_PM_ contain the traditional transactions. The following standard roles provide all WDA apps for SAP S/4HANA Asset Management: SAP_COCKPIT_EAMS_GENERIC_FUNC2 – Generic EAM Functions SAP_COCKPIT_EAMS_MAINT_WORKER2 – Maintenance Worker Bear in mind that the WDA apps and their roles need to be activated via the business functions starting with LOG_EAM_SIMPLICITY – as explained earlier in this unit. This is not necessary for the traditional transactions. © Copyright. All rights reserved. 10  Lesson: Configure SAP Fiori Launchpad UI Adaption Figure 10: Adapting UI Technologies Depending on the UI technology used, there are different UI tools that can be used to customize or adapt the apps: SAPUI5 can be adapted using SAP Web IDE WDA/FPM can be customized via Web Dynpro Customizing WDA/FPM can be adapted via the Flexible UI Designer or SAP Screen Personas Dynpro/SAP GUI can be customized via the traditional IMG (SPRO) Dynpro/SAP GUI can be adapted using SAP Screen Personas The UI Theme Designer can be used to adapt theming and branding of all of SAP’s key UI technologies © Copyright. All rights reserved. 11 Unit 1: UI Configuration Figure 11: Customizing Web Dynpro Note: An example of WDA customizing will be shown in the Notifications unit. LESSON SUMMARY You should now be able to: Check Architecture Check roles, catalogs, and groups (FES) Check roles (BES) © Copyright. All rights reserved. 12  Unit 1 Lesson 2 Summarizing Customizing Settings - UI LESSON OBJECTIVES After completing this lesson, you will be able to: Summarizing Customizing Settings Summarizing Customizing Settings - UI Figure 12: Customizing UI Menu Paths for Fiori Apps Customizing Settings Access to Customizing On the SAP Menu screen, choose Tools Customizing IMG Execute Project Goto SAP Reference IMG Menu Paths for UI Customizing Settings. The following table provides menu paths for Fiori Apps Customizing settings. Field Name or Data Type Path Define Overall Status Plant Maintenance and Customer Service Maintenance and Service Processing Fiori Apps for Maintenance Processing General Settings Define Overall Status Assign Notification Types to Planning Plants Plant Maintenance and Customer Service Maintenance and Service Processing Fiori Apps for Maintenance Processing General Settings Assign Notification Types to Maintenance Planning Plants © Copyright. All rights reserved. 13 Unit 1: UI Configuration Define Checking Rules for Availability Check Plant Maintenance and Customer Service Maintenance and Service Processing Fiori Apps for Maintenance Processing General Settings Define Checking Rules for Availability Check Configure Print Control for Job Card Plant Maintenance and Customer Service Maintenance Roles Maintenance Work- er Configure Print Control for Job Card LESSON SUMMARY You should now be able to: Summarizing Customizing Settings © Copyright. All rights reserved. 14  Unit 1 Learning Assessment 1. What is the preferred client type for SAP S/4HANA? Choose the correct answers. X A SAP GUI for Windows X B SAP Business client for HTML X C SAP Fiori launchpad X D SAP GUI for HTML 2. Which element is responsible for the layout of the SAP Fiori launchpad? Choose the correct answers. X A Fiori tile catalog X B Fiori tile group 3. To run apps in SAP Fiori launchpad you must assign the user... Choose the correct answers. X A Only the business roles on the frontend server X B Only the business roles on the backend server X C Roles on frontend and backend servers X D Only the OData services on the frontend server © Copyright. All rights reserved. 15  Unit 1 Learning Assessment - Answers 1. What is the preferred client type for SAP S/4HANA? Choose the correct answers. X A SAP GUI for Windows X B SAP Business client for HTML X C SAP Fiori launchpad X D SAP GUI for HTML 2. Which element is responsible for the layout of the SAP Fiori launchpad? Choose the correct answers. X A Fiori tile catalog X B Fiori tile group 3. To run apps in SAP Fiori launchpad you must assign the user... Choose the correct answers. X A Only the business roles on the frontend server X B Only the business roles on the backend server X C Roles on frontend and backend servers X D Only the OData services on the frontend server © Copyright. All rights reserved. 16  UNIT 2 Organization Lesson 1 Plants 18 Lesson 2 Maintenance Work Centers 24 Lesson 3 Summarizing Customizing Settings - Organization 28 UNIT OBJECTIVES Name the most important parameters when setting up a plant Maintenance Work Centers Summarizing Customizing Settings © Copyright. All rights reserved. 17  Unit 2 Lesson 1 Plants LESSON OVERVIEW This lesson shows how to set up plants from a maintenance perspective. LESSON OBJECTIVES After completing this lesson, you will be able to: Name the most important parameters when setting up a plant Plants Business Scenario You are going to implement SAP S/4HANA Asset Management and therefore you need to configure the already existing logistic plants from an Asset Management perspective. Figure 13: Step Sequence to Define Organizational Levels Step 1: SAP S/4HANA Asset Management (application component: Plant Maintenance) is often only implemented after other components, such as Financial Accounting (FI), Controlling (CO), or Materials Management (MM) have been implemented. This means that the company structure is, for the most part, predefined in the system. Now, the existing structure must be analyzed from a Plant Maintenance perspective and extended to include the maintenance-specific parts. Step 2: After an in-depth analysis, the organizational units relevant for Plant Maintenance are defined in the system. Maintenance plants (which usually already exist as logistical plants) © Copyright. All rights reserved. 18  Lesson: Plants and maintenance planning plants (planning plants for short) are defined in the company structure. Step 3: In this step, the maintenance planner groups are assigned to planning plants, and maintenance work centers are assigned to maintenance plants. Figure 14: Plant Structure The organizational levels are structured as follows: Client The client is the highest-level element of all the organizational units. It corresponds to a corporate group with several subsidiaries. Within a client, the system always accesses the same database. The subsidiaries, with their own financial statements and balance sheets, are defined as company codes. Controlling area From the Controlling perspective one or several company codes are assigned to a controlling area to have common Controlling/Management Accounting over several subsidiaries. Company codes The subsidiaries, with their own financial statements and balance sheets, are defined as company codes. Maintenance plant In Logistics, the plant is one of the most important organizational units. It usually represents a production unit of a company. The plant at which the operational systems of a company are installed is called the maintenance plant. Maintenance planning plant © Copyright. All rights reserved. 19 Unit 2: Organization A maintenance planning plant is the organizational unit in which maintenance requirements are planned. These requirements can either come from your own plant or from another maintenance plant assigned to this maintenance planning plant. If maintenance work is planned at this plant, the maintenance plant is also the maintenance planning plant (planning plant for short). Locations subdivide a maintenance plant according to location-based criteria, such as site, buildings, and coordinates. A maintenance plant can also be subdivided into plant sections based on responsibility for production. The person responsible for the plant section is the contact person who coordinates production and maintenance (the plant engineer). Maintenance work centers The units of capacity in plant maintenance are managed as maintenance work centers. Maintenance work centers are assigned to the respective maintenance plant as workshops. Maintenance planner groups The planners of a maintenance planning plant are defined as maintenance planner groups. Organizational unit The organizational unit (org unit) is one of the building blocks in Human Resources (HR) to build up an organizational structure. An organizational unit can be assigned to a maintenance work center. This allows you to specify different teams both from a logistical and HR perspectives. Personnel number The personnel number is the business object used in HR to describe an employee with all its different data. Business partner The business partner in SAP S/4HANA is the mandatory approach to create master data such as persons, groups of persons, and organizations. Examples are customer, vendor, personnel number, and so on. Each personnel number has a mandatory business partner assigned. SAP user To log on to an SAP system, every user needs an SAP user, which holds the different logon parameters, the roles combined with access rights, and so on. The SAP user is coupled with the personnel number (and the business partner). So, when a user logs on to an SAP S/ 4HANA system, all different perspectives and data views of this user are covered. © Copyright. All rights reserved. 20  Lesson: Plants Figure 15: Cross-Plant Maintenance Plant-specific planning maintenance plant = maintenance planning plant In most organizational structures, one finds the scenario in which the maintenance requirements are planned in the same plant where the maintenance requirements occur. Additionally, the workshops are assigned to the same plant where the work needs to be carried out. The warehouse is also assigned to the same plant (for example, plant 1010) Cross-plant planning Multiple maintenance plants are assigned to a planning plant. For example, in a plant (for example, plant 1020) are needs for maintenance because a technical system there requires maintenance (maintenance plant). All further functions (maintenance planning, order execution, and spare parts storage) are, however, the responsibility of another plant (plant 1010). Other options Other options are also conceivable. The planning of a plant's maintenance measures (for example, plant 1030) and the spare parts procurement take place in another plant (plant 1010). However, the tasks are performed by workshops that are available locally. © Copyright. All rights reserved. 21 Unit 2: Organization Figure 16: Define a Plant Even if the plants usually have already been defined when implementing SAP S/4HANA Asset Management, the most important steps in defining a plant are as follows: 1. Define plants 2. Define planning plant 3. Define planner groups 4. Maintain storage location of a plant 5. Assign plant to company code 6. Assign purchasing organization to plant 7. Assign standard purchasing organization to plant 8. Assign maintenance planning plant to maintenance plant 9. Quantity/value updating for material types 10. Define account determination > valuation grouping code 0001 for valuation areas 11. Define plant parameters for inventory management 12. Define plant parameters for consumption-based planned 13. Activate/configure split valuation > condition-based material valuation (C) 14. Define valuation of goods received (> refurbishment) © Copyright. All rights reserved. 22  Lesson: Plants LESSON SUMMARY You should now be able to: Name the most important parameters when setting up a plant © Copyright. All rights reserved. 23  Unit 2 Lesson 2 Maintenance Work Centers LESSON OVERVIEW In this lesson, you will learn how to create a work center. LESSON OBJECTIVES After completing this lesson, you will be able to: Maintenance Work Centers Maintenance Work Centers In this lesson, we will discuss the use of work centers in plant maintenance. Figure 17: Maintenance Work Centers Use and Function of Work Centers A work center is an organizational unit that defines where and when an operation must be performed. Work centers can be machines, people, and production lines. Work centers are used to execute operations for task lists and maintenance orders. Work center data forms the basis for cost calculation, capacity planning, and scheduling for the work to be performed. You can use work center data to help with the following: © Copyright. All rights reserved. 24  Lesson: Maintenance Work Centers Define which machines or personnel should be used for the operations Calculate costs, capacities, and target dates for the operations Use and Function of Work Centers A work center is an organizational unit that defines where and when an operation must be performed. Work centers can be machines, people, and production lines. Work centers are used to execute operations for task lists and maintenance orders. Work center data forms the basis for cost calculation, capacity planning, and scheduling for the work to be performed. You can use work center data to help with the following: Define which machines or personnel should be used for the operations Calculate costs, capacities, and target dates for the operations Work Center Data Work center data is used for the following business functions: Basic data Contains the description, work center category (for example, Plant Maintenance), and task list usage (which routings the work center may be used for). Default values For example, a default control key. Capacity Available capacity is usually entered as the standard available capacity with the specifications—factory calendar, work start and end, level of individual capacity (number of people) and operating time per capita. The available capacity can be restricted according to time, or can be organized in shifts differing from the standard available capacity. Scheduling The operation dates are calculated on the basis of lead times (duration of operation), starting from the basic start or end dates. Costing Internal personnel costs are assigned on the basis of the activity types defined in Controlling. The activity types contain the assignment to an hourly rate. Activity types are assigned indirectly using a cost center, not directly to the work center. Personnel data In addition to defining available capacity, people (personnel numbers from human resources) or positions can be assigned in the work center. Capacities Available capacity refers to the capacity available within a specific period. Available capacity is determined by: © Copyright. All rights reserved. 25 Unit 2: Organization Work starting and finishing times Length of breaks Capacity utilization level of the capacity units The number of individual capacity units that make up total capacity The system saves the time worked and the daily available capacity for each work center. Figure 18: Available Capacity in the Work Center The standard available capacity is valid if no interval of available capacity has been defined. The standard available capacity is defined using the shift start and finish times, break lengths, and number of individual capacity. The system uses this data to calculate a capacity unit working time. The period for which the standard available capacity is valid has no limit. If you have specified validity periods for available capacity, these are referred to as intervals of available capacity. This is the capacity available within a specific period of validity. To define an interval of available capacity, you can determine shift programs that will also be valid for all work centers for a fixed time period. Start, finish, and break times are specified for work centers in a shift. © Copyright. All rights reserved. 26  Lesson: Maintenance Work Centers PM-PP Integration Figure 19: PM-PP Integration Work centers are not just used in maintenance but in other areas too, for example, production work centers. If a maintenance order has been written for a machine being used as a production work center, production planners should be able to see all pending maintenance orders and the production orders for this work center on their planning boards. To display maintenance orders for a production work center, the number of the PP work center must first be entered in the technical object's location data. The maintenance order must also have a system conditionat the header level. LESSON SUMMARY You should now be able to: Maintenance Work Centers © Copyright. All rights reserved. 27  Unit 2 Lesson 3 Summarizing Customizing Settings - Organization LESSON OBJECTIVES After completing this lesson, you will be able to: Summarizing Customizing Settings Summarizing Customizing Settings - Organization Access to Customizing On the SAP Menu screen, choose Tools Customizing IMG Execute Project Goto SAP Reference IMG Menu Paths for Organization Customizing Settings. The following tables provide menu paths for Organization Customizing settings. Figure 20: Customizing Plant Table 1: Plant Parameters Field Name or Data Type Path © Copyright. All rights reserved. 28  Lesson: Summarizing Customizing Settings - Organization Define Plant Enterprise Structure Definition Logis- tics - General Define, copy, delete, check plant Define Planning Plant Enterprise Structure Definition Plant Maintenance Maintain maintenance plan- ning plant Assign Planning Plant Enterprise Structure Assignment Plant Maintenance Assign maintenance plan- ning plant to maintenance plant Define Planner Groups Plant Maintenance and Customer Service Master Data in Plant Maintenance and Customer Service Technical Objects General Data Define Planner Groups Storage Location Enterprise Structure Definition Logis- tics - General Define Location Purchasing Organization Enterprise Structure Assignment Mate- rials Management Assign purchasing or- ganization to plant — / Assign standard pur- chasing organization to plant Quantity and Value Update for Material Logistics - General Material Master Ba- Types sic Settings Material Types Define At- tributes of Material Types Account Determination Materials Management Valuation and Ac- count Assignment Account Determination Account Determination Without Wizard Group Together Valuation Areas Inventory Management Materials Management Inventory Manage- ment and Physical Inventory Plant Param- eters Consumption-based Planning Materials Management Consumption- Based Planning Plant Parameters Car- ry Out Overall Maintenance of Plant Parame- ters Split Valuation (Refurbishment) Materials Management Valuation and Ac- count Assignment Split Valuation Acti- vate Split Valuation — / Configure Split Valu- ation Valuation of Goods (Refurbishment) Production Shop Floor Control Integra- tion Define Valuation of Goods Received © Copyright. All rights reserved. 29 Unit 2: Organization Figure 21: Customizing Work Centers Table 2: Work Centers Field Name or Data Type Path Work Center Category Plant Maintenance and Customer Service Maintenance Plans, Work Centers, Task Lists and PRTs Work Centers General Data Define Work Center Types and Link to Task List Application Field Selection Plant Maintenance and Customer Service Maintenance Plans, Work Centers, Task Lists and PRTs Work Centers General Data Define Field Selection Screen Sequence Plant Maintenance and Customer Service Maintenance Plans, Work Centers, Task Lists and PRTs Work Centers Config- ure Screen Sequence for Work Center Default Work Center Plant Maintenance and Customer Service Maintenance Plans, Work Centers, Task Lists and PRTs Work Centers General Data Create Default Work Center LESSON SUMMARY You should now be able to: Summarizing Customizing Settings © Copyright. All rights reserved. 30  Unit 2 Learning Assessment 1. A maintenance planning plant... Choose the correct answer. X A Can only be assigned to one maintenance plant X B Can be assigned to various maintenance plants X C Is the organizational unit to which work centers are assigned X D Is only relevant for cross-plant planning 2. Which of the following statements about work centers are correct? Choose the correct answers. X A They are organizational units that define when and where an operation must be performed. X B They can be machine, production lines, or people. X C They form the basis for cost calculation, capacity planning, and scheduling. X D They are only used in maintenance. © Copyright. All rights reserved. 31  Unit 2 Learning Assessment - Answers 1. A maintenance planning plant... Choose the correct answer. X A Can only be assigned to one maintenance plant X B Can be assigned to various maintenance plants X C Is the organizational unit to which work centers are assigned X D Is only relevant for cross-plant planning 2. Which of the following statements about work centers are correct? Choose the correct answers. X A They are organizational units that define when and where an operation must be performed. X B They can be machine, production lines, or people. X C They form the basis for cost calculation, capacity planning, and scheduling. X D They are only used in maintenance. © Copyright. All rights reserved. 32  UNIT 3 Notifications Lesson 1 Notification Type 34 Lesson 2 Summarizing Customizing Settings - Notifications 42 UNIT OBJECTIVES Configure a notification type Assign priorities and object information to notifications Assign catalogs and catalog profiles to notification types Configure notifications in FLP Summarizing Customizing Settings © Copyright. All rights reserved. 33  Unit 3 Lesson 1 Notification Type LESSON OVERVIEW In this lesson, you will learn how to configure notification types and notification screens. LESSON OBJECTIVES After completing this lesson, you will be able to: Configure a notification type Assign priorities and object information to notifications Assign catalogs and catalog profiles to notification types Configure notifications in FLP Notification Category and Notification Type Figure 22: Notification Category and Notification Type In maintenance processing, you use a notification to collect maintenance requirements. A company should have its own notification type for requirements set up. A company can customize their own notification types for the collection of requirements. You can use maintenance notifications (notification category 01, notification type M1 or M2) to enter and process requirements and malfunctions. Alternatively, you can create a general notification (notification category 05, notification type G0, for example), which is initially created under the Central Functions menu. © Copyright. All rights reserved. 34  Lesson: Notification Type General notification uses a simple entry screen for entering the requirement into the system. You do not have to define the type (for example, malfunction, request, complaint, internal problem notification). You can decide the type in the second step by changing notification type General Notification to the specific notification type (for example, Malfunction Report). In the subsequent notification, the maintenance planner adds all the missing details. The advantage of using general notifications is that you can make a central, coordinated entry for any kind of requirement. The person making the entry does not have to be a trained maintenance planner. In the Enterprise system, the notification type is assigned to an application such as customer service, quality management, or plant maintenance. You can use the individual notification types to define different classes of maintenance notifications and then use these classes when making selections. You can use the notification type to define the use of the maintenance notification for particular business processes. In the standard system, notification types are structured according to functional criteria (malfunction notification, maintenance request, activity report). Settings for Notification Types Figure 23: Settings for Notification Types Notification Types Settings Long text control This setting allows you to lock a text and add a line to the log (changed by, date of change, and so on). Notification origin This defines the basic character of a notification (for example, requirement or malfunction report). Reference time © Copyright. All rights reserved. 35 Unit 3: Notifications The reference time is the proposed time for the completion of the notification. Once the time is set, it identifies the historical reference for completion. Order type A default order type can be specified when creating an order from a notification. Number assignment The number range used. Priority/priority type This setting allows you to prioritize notifications in connection with date proposals. Partners Contact persons who should be available in notification and order processing (supplier, customer, and so on). Object information Information concerning the reference object of the notification or order and that can be displayed from the notification or the order. Field selection Identifies what fields of data in the notification are required, optional for entry, display only, or hidden from view. Catalog/catalog profile A variety of catalogs can be assigned to a notification, such as the object part, damage, cause of damage, task, and activity catalogs. The catalog profile limits the selection of available code groups referring to specific subject areas (car type, data processing, production machines, and so on). General Settings for Maintenance Notifications In this section, we will look at the settings that can be applied to all types of maintenance notifications. Maintenance Notifications Settings The following settings can be used for all types of notification: Field selection The field selection for notifications allows you to control certain fields together for all notification types (for example, light color for the notification from and notification date fields). List editing You can set up list processing for notifications in Customizing so that it contains standard values for selection screens, field selection, and the display variant. The system condition indicator The system condition indicator defines the conditions that a technical system can have (operational, out of order, and so on). These settings are defined at client level and are not dependent on the notification type. Transaction start values © Copyright. All rights reserved. 36  Lesson: Notification Type The transaction start values for a notification transaction define whether an initial screen should be displayed and which default notification type should be used. Initial Screen must be selected if you want to access the initial screen with the field for the notification number and notification type. You can also define which screen should be the first detail screen. The notification header screen is the initial screen in the standard system, but this can be changed. Notification Screen Configuration Figure 24: Configuration of Screen Layout The notification interface can be configured to meet the needs of your organization. You can configure tabs for each notification type. A total of 26 different tab pages are available (22 notification-based, 4 item-based). You can define a simple view or an enhanced view for each notification type. This means that a simple screen appears for the person entering the notification and a detailed appears for the person processing it. The type of transaction determines the view displayed: The plant maintenance transactions IW24 (Malfunction Report), IW25 (Activity Report), and IW26 (Request) access the enhanced view. Transaction IQS21 accesses the basic view. You can define screen areas (sub-screens) for each tab. 21 different screen areas are available. You can assign the tabs their own internal heading and a graphical symbol, if required. You can easily activate or deactivate predefined tabs. Within a notification type, you can also specify different layouts for the notification screen, for example, to distinguish between display mode and change mode. You might want only the core data to be visible in display mode, and all data to display in change mode. This is controlled using activity categories (create, change, and display). © Copyright. All rights reserved. 37 Unit 3: Notifications Priorities Figure 25: Priorities A priority can be assigned to each maintenance notification and order. This priority defines the required start and end dates for the notification or order, relative to the creation date. During maintenance processing, you can work with internal priority types for notifications and orders. Since you can define an unlimited number of priorities for each priority type, it is easier to use the same priority types for notifications and orders. The same priority keys have the same meaning. Object Information The object information provides summarized core data on a technical object, which can be used to support processing of a maintenance task (for example, last active notification, last active order, or next maintenance). Object information is available at the following locations: In the master record for the technical object In the notification In the order Object Information Key Controls automatic display of object information Controls reference to object information Controls number of days in the past to search for PMIS info and notifications Controls the display of characteristics for the reference object The object information key defines how the object information is displayed in notifications and orders. If the Automatically indicator is set, the system automatically displays the object information in the notification as soon as the reference object is entered or changed. The reference specifies whether the object information should relate only to the reference object, to the reference object and all superior objects in the technical hierarchy, or to all objects in the reference object structure. © Copyright. All rights reserved. 38  Lesson: Notification Type You can specify the number of days in the past (from the time of the query) the system should search for the statistics from the information system (breakdowns reported, notifications created, and so on). You can enter such a search period for finding notifications. You can also define whether the system should display completed or outstanding notifications, and not only notifications with the status In processingor Outstanding. If the indicator for characteristics is set, the characteristics of the reference object are displayed, provided it has been assigned to a class. Catalogs and Catalog Profile Figure 26: Catalogs A cross-application catalog system is used for reporting maintenance notifications. This catalog system has a hierarchical structure. The first level of the catalog system is the catalog type. Each catalog type represents a certain directory. Each catalog type can be further subdivided using code groups. You can define individual codes in each group. The following catalog types are provided as standard for Plant Maintenance: Catalog 2 for tasks Catalog 5 for causes of damage Catalog A for activities Catalog B for object parts Catalog C for damage Catalog types R to Z are reserved for user-defined catalog types © Copyright. All rights reserved. 39 Unit 3: Notifications In the catalogs, you assign each unit of information a unique alphanumeric code and an explanatory text. The text appears in the notification item as keywords for the respective catalog displayed. Notifications in SAP Fiori Launchpad Figure 27: Create Notifications via SAP Fiori Launchpad There are various possibilities to create a maintenance notification via the SAP Fiori launchpad. For instance, you can use the Request Maintenance SAPUI5 app to create a simplified maintenance notification. Alternatively, you can choose the Create Maintenance Notification WDA app. A third option would be to create your own tile with a target mapping for a transaction such as IW21. For processing multiple notifications via the Fiori Launchpad the following apps are available: Manage Notification List Find Maintenance Notification Web Dynpro Customizing If you want to go beyond personalization and customize the layout of your notifications (and all other business objects) you have to distinguish between central settings and UI-specific settings on the one hand and the different UI technologies on the other hand. Central settings such as notification type, priority types, catalog profiles, and so on are defined in the backend system in IMG. UI-specific settings can be made using the corresponding tools: © Copyright. All rights reserved. 40  Lesson: Notification Type SAPUI5: Changes are made via Web IDE. WDA: Changes are made via WDA customizing, flexible UI designer, or SAP Screen Personas. SAP GUI: Changes are made via customizing in IMG. Figure 28: Customizing Web Dynpro ABAP Because many apps for SAP S/4HANA Asset Management are based on Web Dynpro ABAP, you can use Web Dynpro Customizing to make adjustments such as hiding sub-screens, buttons, or fields. LESSON SUMMARY You should now be able to: Configure a notification type Assign priorities and object information to notifications Assign catalogs and catalog profiles to notification types Configure notifications in FLP © Copyright. All rights reserved. 41  Unit 3 Lesson 2 Summarizing Customizing Settings - Notifications LESSON OBJECTIVES After completing this lesson, you will be able to: Summarizing Customizing Settings Summarizing Customizing Settings - Notifications Figure 29: Customizing Notification Menu Paths for UI Customizing Settings Access to Customizing On the SAP Menu screen, choose Tools Customizing IMG Execute Project Goto SAP Reference IMG Menu Paths for Notification Customizing Settings. The following table provides menu paths for Notification Customizing settings. Field Name or Data Type Path Overview of notification type Plant Maintenance and Customer Service Maintenance and Service Processing Maintenance and Service Notifications Overview of Notification Type © Copyright. All rights reserved. 42  Lesson: Summarizing Customizing Settings - Notifications Action box Plant Maintenance and Customer Service Maintenance and Service Processing Maintenance and Service Notifications Notification Processing Additional Functions Define Action Box General notification Cross-Application Components Notifica- tion System condition Plant Maintenance and Customer Service Maintenance and Service Processing Maintenance and Service Notifications Notification Processing Define System Conditions Catalog profile Plant Maintenance and Customer Service Maintenance and Service Processing Maintenance and Service Notifications Notification Creation Notification Con- tent Define Catalog Profile Screen templates Plant Maintenance and Customer Service Maintenance and Service Processing Maintenance and Service Notifications Notification Creation Notification Types Set Screen Templates for the Notification Type Allowed change of notification type Plant Maintenance and Customer Service Maintenance and Service Processing Maintenance and Service Notifications Notification Creation Notification Types Allowed Change of Notification Type Field selection Plant Maintenance and Customer Service Maintenance and Service Processing Maintenance and Service Notifications Notification Creation Notification Types Set Field Selection for Notifications Integration notification/order (long text Plant Maintenance and Customer Service transfer, object list control) Maintenance and Service Processing Maintenance and Service Orders Func- tions and Settings for Order Types Define Notification and Order Integration Catalogs Plant Maintenance and Customer Service Maintenance and Service Processing Maintenance and Service Notifications Notification Creation Notification Con- tent Maintain Catalogs etc © Copyright. All rights reserved. 43 Unit 3: Notifications Long text control Plant Maintenance and Customer Service Maintenance and Service Processing Maintenance and Service Notifications Notification Creation Notification Types Define Long Text Control for Notifi- cation Types List editing Plant Maintenance and Customer Service Maintenance and Service Processing Maintenance and Service Notifications Notification Processing List Editing Notification type Plant Maintenance and Customer Service Maintenance and Service Processing Maintenance and Service Notifications Notification Creation Notification Types Assign notification types to order types Plant Maintenance and Customer Service Maintenance and Service Processing Maintenance and Service Notifications Notification Creation Notification Types Assign Notification Types to Order Types Number ranges Plant Maintenance and Customer Service Maintenance and Service Processing Maintenance and Service Notifications Notification Creation Notification Types Define Number Ranges Object information Plant Maintenance and Customer Service Maintenance and Service Processing Maintenance and Service Notifications Notification Processing Object Infor- mation Partner determination procedure Plant Maintenance and Customer Service Maintenance and Service Processing Maintenance and Service Notifications Notification Creation Partners Priorities Plant Maintenance and Customer Service Maintenance and Service Processing Maintenance and Service Notifications Notification Processing Response Time Monitoring Define Priorities Response profile Maintenance and Customer Service Main- tenance and Service Processing Mainte- nance and Service Notifications Notifica- tion Processing Response Time Monitor- ing Define Response Monitoring © Copyright. All rights reserved. 44  Lesson: Summarizing Customizing Settings - Notifications Transaction start values Plant Maintenance and Customer Service Maintenance and Service Processing Maintenance and Service Notifications Notification Creation Notification Types Define Transaction Start Values Settings for Fiori Apps – Notification Type Plant Maintenance and Customer Service Planning Plant Maintenance and Service Processing Fiori Apps for Maintenance Process- ing Assign Notification Types to Mainte- nance Planning Plants Settings for Fiori Apps – Define Overall Sta- Plant Maintenance and Customer Service tus Maintenance and Service Processing Fiori Apps for Maintenance Process- ing Define Overall Status LESSON SUMMARY You should now be able to: Summarizing Customizing Settings © Copyright. All rights reserved. 45  Unit 3 Learning Assessment 1. Which of the following statements about configuring the notification screen are correct? Choose the correct answers. X A You can choose from 27 different tab pages for each notification type. X B You can apply a simple view or an enhanced view to each notification type. X C You can define only one screen area per tab. X D You can assign internal headings and symbols to tabs. 2. A priority defines the required start and end dates for an order or notification. Determine whether this statement is true or false. X True X False 3. In which of the following locations can object information be found? Choose the correct answers. X A In a master record for the technical object X B In an order X C In a document X D In a notification 4. Match the catalog type to the relevant directory. Match the item in the first column to the corresponding item in the second column. Catalog 2 Activities Catalog 5 Damage Catalog A Tasks Catalog B Causes of damage Catalog C Object parts © Copyright. All rights reserved. 46  Unit 3 Learning Assessment - Answers 1. Which of the following statements about configuring the notification screen are correct? Choose the correct answers. X A You can choose from 27 different tab pages for each notification type. X B You can apply a simple view or an enhanced view to each notification type. X C You can define only one screen area per tab. X D You can assign internal headings and symbols to tabs. 2. A priority defines the required start and end dates for an order or notification. Determine whether this statement is true or false. X True X False 3. In which of the following locations can object information be found? Choose the correct answers. X A In a master record for the technical object X B In an order X C In a document X D In a notification © Copyright. All rights reserved. 47 Unit 3: Learning Assessment - Answers 4. Match the catalog type to the relevant directory. Match the item in the first column to the corresponding item in the second column. Catalog 2 Tasks Catalog 5 Causes of damage Catalog A Activities Catalog B Object parts Catalog C Damage © Copyright. All rights reserved. 48  UNIT 4 Orders Lesson 1 Order Type 50 Lesson 2 Material Planning 58 Lesson 3 Scheduling 63 Lesson 4 Printing 67 Lesson 5 Completion Confirmation and Technical Completion 70 Lesson 6 Summarizing Customizing Settings - Orders 73 UNIT OBJECTIVES Define and configure order types Assign notifications to orders Add a document to an order using SAP Document Management Configure Material Availability Check Customize SAP 3D Visual Enterprise Set the scheduling parameters Customize print settings Customize completion confirmation and technical completion settings Summarizing Customizing Settings © Copyright. All rights reserved. 49  Unit 4 Lesson 1 Order Type LESSON OVERVIEW In this lesson, you learn how to set up order types. LESSON OBJECTIVES After completing this lesson, you will be able to: Define and configure order types Assign notifications to orders Add a document to an order using SAP Document Management Configure the Basic Settings of an Order Type Figure 30: Order Category and Order Type Order category determines the application component to which an order belongs. It is usually used as a program-internal selection criterion and to all intents and purposes does not appear to users. The order categories for the respective applications are fixed in the system. You can freely define the order types within an order category for each application. The order type represents business segments (repair, maintenance, refurbishment, investment) that differ in the way they are processed and therefore have different system settings. © Copyright. All rights reserved. 50  Lesson: Order Type Setting Up an Order Type (1) Figure 31: Setting Up an Order Type (1) Different order types should be used for different business situations because many system control functions depend on the order type. A distinction is made here between parameters that depend directly on the order type and those that are assigned to a combination of order type and planning plant. Parameters for order type: Settlement profile Specifies possible settlement recipients, the default receiver, and additional parameters (for example, allocation structure) Budget profile (optional) Summarizes the budgeting control parameters (time frame, display, availability checks, currency conversion) Residence time Residence time 1: Specifies the period of time (in calendar months) that must elapse between when the deletion flag is set (step 1) and when the deletion indicator is set (step 2) Residence time 2: Specifies the period of time (in calendar months) that must elapse between when the deletion indicator is set (step 2) and the reorganization (step 3) Screen for reference object Specifies which input masks should be used for the reference object Number range Specifies which number range interval is used for each order type Planning plant Assigns order types to the maintenance planning plant © Copyright. All rights reserved. 51 Unit 4: Orders Costing variants: actual + planned Contains control parameters for planned and actual calculations in the order Settlement rule Defines the start time for creating the settlement rule Maintenance activity type Subdivides tasks within an order type and serves evaluation purposes (inspection, routine maintenance, preventive maintenance, refurbishment, cleaning, and so on) Not to be confused with CO activities, which are assigned to the cost center and enable work valuation during operation Planning indicator Performs selection and statistical evaluation in the plant maintenance and customer service information systems (planned, unplanned, immediate orders) Scheduling parameters Contain parameters such as the scheduling type and requirement date for materials. For details see lesson Scheduling. Maintenance Activity Types Figure 32: Maintenance Activity Types The maintenance activity type is the key for the type of maintenance activity executed (repair, shutdown, periodic tasks, and so on). In cost evaluations (total costs, number of orders per technical object), you can classify the data using the maintenance activity type (distinction made between maintenance activities and costs). The permitted activity types are assigned to each order type. © Copyright. All rights reserved. 52  Lesson: Order Type Basic Order View Figure 33: Basic Order View You can define a basic order view for certain user groups (such as maintenance technicians). You do this by assigning a view profile containing only the most important screen areas on the smallest possible number of tab pages. View profiles can be defined for the basic order view and multiple tab pages can be assigned to each view profile. Configure Further Settings of an Order Type Figure 34: Setting up an Order Type (2) © Copyright. All rights reserved. 53 Unit 4: Orders Parameters for order type: Default value profile Contains default values for external procurement or for general settings. Step-by-step operations/change documents/MRP relevance A customizing step that contains a series of settings, such as the increment for numbering operations, the creation of change documents, the MRP relevance of reservations (when creating or releasing the order), and so on. Priority type with priorities (as with notifications) Object information (as with notifications) Default control key A control key can be proposed by the order type. Partner determination procedure/determination of address data The partner determination procedure makes contact persons available for order processing. This assignment also links to the central address management. Special Order Types Order types for Refurbishment, Investments or Operation Account Assignment are basically created in the same way as standard order types. However, each special order type will be assigned a special indicator. Default Value Profile Figure 35: Set Up Order Type – Profile Assignment Profiles for external processing During external processing, a distinction is made between the external procurement of material and the assignment of complete operations to external companies. © Copyright. All rights reserved. 54  Lesson: Order Type Since both of the procurement processes generally require different data for purchasing (different purchasing groups or different cost elements), you should define different profiles. The profiles can be defined centrally for each order type in Customizing. Alternatively, these settings can be set as user-specific with the user default values. The user values override the Customizing settings. Profile for general order data You can assign a default profile for general order data to obtain default values for a network profile, operation parameters, order parameters, and graphic parameters. Control Keys for Operations The control key in an operation controls the following parameters: Capacity planning Scheduling operations Capacity requirement Costing Service Printing time tickets Printing confirmation slips Printing operations Completion confirmations External processing The system controls the processing of individual operations using the operation control key. You use the capacity planning indicator to ensure that the operation is scheduled and capacity load records are created for it. By setting the costing indicator, you ensure that the operation is taken into account during costing. You use the external processing key to define that the operation is executed by an external company. You use the completion confirmation indicator to specify whether the operation can be confirmed and what type of completion confirmation applies. The print parameters specify whether time tickets, confirmation slips, and so on should be printed for this operation. Mass Changes in Operations List In this section, we will look at the mass change function. Mass Changes You can use the Perform Mass Change function in list editing to change the field contents of different fields for several order operations at the same time. You can execute this mass change directly or in the background. © Copyright. All rights reserved. 55 Unit 4: Orders On various tab pages that correspond to the tab pages from the notification or order processing, you select the fields that you want to change and specify the new value. Hint: To keep an overview, form small logical units of fields that you want to change. Notification and Order Integration Figure 36: Integration of Notification and Order Assigning Notifications to an Order Notifications can be assigned to an existing order or one that is newly created. If the notification is assigned to a task list, then the operations of the task list can be transferred to the order object list. A prerequisite for doing this is to have a Customizing setting (notification and order integration). Four new fields are available in the order object list: functional location, equipment, notification, and plan date. The notifications assigned to an order are then placed in the order's object list. Object List Entries In the order type settings, you can specify how entries in the order object list affect the order operation list if, for example, several notifications that have a task list are grouped into one order. You have the following options: Assignment of operations to object list entries inactive (default) Assignment of operations only for notifications with task lists called from maintenance plans Assignment of operations to all notifications © Copyright. All rights reserved. 56  Lesson: Order Type Assignment of operations to all object list entries (for example, also equipment, functional locations) Delete Notifications or Operations If a notification is deleted from the order's object list, then all operations transferred by the notification's task list will also be deleted. Likewise, if all of a notification's operations are deleted from an order's task list, the notification will also be removed from the object list. Header Notification If an order is created from a single notification, it then becomes the header notification for the order (the notification is attached to the object list). The relationship between order and object list can be deleted. If several notifications are assigned in one existing order, then this can become the header notification (only if the contract does not have one). The subsequent assignment of a header notification can also be reversed again. Note: You can delete the assignment of a notification to an order header only via SAP GUI. Notification Long Text If an order is created from a notification, the long text of the notification can be transferred as the order's long text (only when the order is first created). This must be activated in Customizing for all types of notification. Documents in Orders You can attach documents, containing information about equipment or repair instructions, from the document management system to a maintenance order header or maintenance operation. Documents in Orders You can allocate documents to orders as follows: Allocate existing documents to maintenance orders and operations. Create new documents and attach these to the maintenance order or operation. Display documents that are attached to the functional location, equipment, and assembly. Display documents attached to a notification from the o