The following are example modules for Achieving Excellence in Customer Service training for front-line workers and first-line supervisors. Module 1 – Compassion for the Customer. As a result of this training module, participants will be better able to: Identify customers and what they value. SAP Sales and Distribution module is a part of SAP Logistics module that manages customer relationship starting from raising a quotation to sales order and billing of the product or service. This module is closely integrated with other modules like SAP Material Management and PP. Key Components in SAP SD.
The complete work order cycle in the SAP R/3 system includes notifications, work orders, assignment of labor, assignment of materials, completion confirmation (possibly involving the Cross- Application Time Sheet, CATS), settlement, and business completion of the work order. The cycle may extend to the analysis of reactive maintenance work so that preventive maintenance can be scheduled to reduce the amount of reactive/ breakdown maintenance.
Although, technically speaking, it is possible to use work orders without notifications, or notifications without work orders, in the R/3 Plant Maintenance system, to omit either will mean a loss of information. Notifications can maintain statistical information, such as mean- time- between- failures, that can be important in reducing breakdown maintenance work. Work orders maintain the essential integration with other modules, including cost information.
In addition, the relationship between notifications and work orders provides a method for approval of requested work. Determine, along with controlling and/or finance personnel, the method by which work orders will be settled. SAP allows work orders to be settled to variety of receivers, including cost centers, projects, internal orders, other work orders, and so on. If equipment has been assigned to the appropriate cost centers, for example, work orders created for that equipment would, by default, settle to those cost centers.
Notifications
A notification in the SAP R/3 system is typically used to notify someone that some work is required, is requested, or was already done. Those three typical uses define the three default notification types for PM, although other notification types are available for QM (Quality Management) and CS (Customer Service), formerly SM (Service Management). Non-PM notification types should not be deleted without determining that other modules will never use them.
A notification in the SAP R/3 system is typically used to notify someone that some work is required, is requested, or was already done. Those three typical uses define the three default notification types for PM, although other notification types are available for QM (Quality Management) and CS (Customer Service), formerly SM (Service Management). Non-PM notification types should not be deleted without determining that other modules will never use them.
Notifications, in addition to the functionality listed above, track and compile statistical information and history regarding the objects against which they were created. A notification, however, retains no cost information and has no significant integration with other modules.
A malfunction report notification is, as the name suggests, a report that malfunction has occurred. Usually, a malfunction report is used where it might be beneficial to record breakdown information such as mean-time between-failures or mean-time-to-repair. The relevant piece of equipment may be completely stopped or its performance may be reduced.
A maintenance request notification is usually used to request maintenance work on a piece of equipment that may be functioning satisfactorily, but whose operator, for example, may see a potential problem. An activity report notification is normally used to record work that has already been performed in order to maintain complete statistical history for the relevant equipment.
Although other notification types may be defined, the majority of implementations should find that the three default notification types described above would suffice. Since notifications can be identified as assigned to a particular plant, there is certainly no need to create different notification types for each plant, nor is there any need to specially number (“smart” number) the notifications for each plant.The historical information recorded through the use of notifications is best done with the use of catalogs, which are described in the section on catalogs, below.
Catalogs
In the SAP R/3 system, catalogs represent a method of providing standard codes for damage, cause of damage, activities, and so on. The advantage of using standard codes and descriptions instead of allowing free-form descriptions is that when the information is summarized, it is possible to see how many times a particular problem has occurred with a particular piece of equipment within a specific time frame and how many times each maintenance activity was performed to resolve the problem. Further analysis allows the tracking of problems to a particular manufacturer, if manufacturer data is recorded for equipment. Without standard codes it would be difficult, at best, to summarize such information into a usable format.
In the SAP R/3 system, catalogs represent a method of providing standard codes for damage, cause of damage, activities, and so on. The advantage of using standard codes and descriptions instead of allowing free-form descriptions is that when the information is summarized, it is possible to see how many times a particular problem has occurred with a particular piece of equipment within a specific time frame and how many times each maintenance activity was performed to resolve the problem. Further analysis allows the tracking of problems to a particular manufacturer, if manufacturer data is recorded for equipment. Without standard codes it would be difficult, at best, to summarize such information into a usable format.
A catalog profile provides a means of grouping catalog codes that are relevant to a particular function, for example. The codes within a catalog profile are made available to notifications based on the object (piece of equipment, for example) against which the notification is written. If a piece of equipment has a catalog profile assigned to it, only the codes within that catalog profile will be available to notifications written for that piece of equipment. A catalog profile, therefore, can be a method of reducing the number of codes to those relevant for an object.
Within a catalog profile are code groups, which can be used to further reduce the quantity of codes from which to choose. Codes can be grouped into equipment types, for example, so that the types of damage for pumps are contained in a separate code group than the types of damage for motors. The two main factors for separating the codes are:
- to avoid the use of codes that are not relevant to the object, and
- to restrict the choices to a manageable number. The more choices available in a list, the longer it will take to make a choice and the chance of a wrong choice being made will increase.
Finally, the codes within each code group are defined. Ensure that the codes are relevant to the group. Ideally, the number of code groups from which to choose should be minimized, as should the number of codes within each code group. In some situations, particularly where the use of codes is regulated, it may not be possible to minimize the number of codes. For Plant Maintenance purposes, the catalogs typically used are damage, cause of damage, object part, activities, tasks, and sometimes coding. Other catalogs, if required, may be defined, but bear in mind that the catalog code can only be one character or digit. Since SAP reserves the right to use all the digits and the characters A to O inclusive, only the codes P to Z may be used to define other desired catalogs.
The information accumulated on notifications by means of using catalogs can be reported using the Plant Maintenance Information System(PMIS), a subset of the Logistics Information System (LIS), which is described in a later section.
Work Orders
A work order in the SAP R/3 system is typically used to plan work that is required, assign the work to resources who will perform the necessary work, accumulate labor and material costs, and track completion of the work. A sequence of tasks (or operations) can be included on the work order.
A work order in the SAP R/3 system is typically used to plan work that is required, assign the work to resources who will perform the necessary work, accumulate labor and material costs, and track completion of the work. A sequence of tasks (or operations) can be included on the work order.
Labor and materials that will be required to complete the work are defined on the work order while it is in the planning stage. This provides planned labor and material costs. If planned materials are purchased independently of work orders and are kept in stock, the work order will generate a reservation for such materials. If planned materials are not kept in stock and must be purchased specifically for the work order, the work order will generate a purchase requisition for such materials.
Planned labor can be performed by internal resources (employees) or by external resources (contractors). This will be discussed in more detail later. During completion of the work, goods (materials) are issued to the work order, which causes actual material costs to accumulate on the work order. Confirmations of labor, either through the Human Resources module or directly in the Plant Maintenance module, cause actual labor costs to accumulate on the work order. The three basic steps to complete and close a work order consist of technical completion, which usually indicates that all of the work has been completed, settlement, during which the accumulated costs on the work order are settled to a cost center or other cost receiver, and business completion(close).
A work order in SAP R/3 can be generated from a notification, it can be created independently, or it can be generated from a maintenance plan. As with notifications, there are several work order types provided with the R/3 system by default. Many find that the default work order types are adequate for their needs, but additional order types can be defined if required. Since work orders can be identified by plant, there is no need to “smart” number the work orders to identify them by plant. Unless there are circumstances requiring that work orders be manually numbered, it is usually recommended that the system assign work order numbers automatically. This is referred to as “internal” numbering. Seethe section on “Number Ranges” for further information.
Back to the Implementation Guide (IMG)— Maintenance and Service Processing
The step-by-step discussion of the Maintenance and Service Processing section of the implementation guide is continued below:
Basic Settings
Maintain Authorizations for Processing
Maintaining authorizations, a security function of the SAP R/3system, is best done in co-operation with the individual(s) whose responsibility it is to maintain security for the system. See the section “Security: Authorizations and Roles” for more information.
Maintain Authorizations for Processing
Maintaining authorizations, a security function of the SAP R/3system, is best done in co-operation with the individual(s) whose responsibility it is to maintain security for the system. See the section “Security: Authorizations and Roles” for more information.
Planning of Background Jobs for PDC
PDC, Plant Data Collection, can be used to automatically update information in the SAP system, possibly saving time and effort entering repetitive data into the SAP system. However, since there is more than one specific method by which to accomplish the automation, it is not possible to determine beforehand what these settings should be. The third-party data collection system and the method by which it will be interfaced with the SAP system will determine what the settings in this configuration step will be. Since there may be some significant time involved in getting two systems to “talk” to each other and transfer data reliably, ensure that the scope of the implementation includes the integration of a plant data collection system and SAP R/3.
PDC, Plant Data Collection, can be used to automatically update information in the SAP system, possibly saving time and effort entering repetitive data into the SAP system. However, since there is more than one specific method by which to accomplish the automation, it is not possible to determine beforehand what these settings should be. The third-party data collection system and the method by which it will be interfaced with the SAP system will determine what the settings in this configuration step will be. Since there may be some significant time involved in getting two systems to “talk” to each other and transfer data reliably, ensure that the scope of the implementation includes the integration of a plant data collection system and SAP R/3.
Define Download Parameters for PDC
As with the previous configuration step, this step also relates to the automatic collection and transfer of data from an external system to the SAP R/3 system. If this is required, work closely with the developers or programmers to determine how these settings should be set to meet the needs of the Plant Maintenance module in relation to the methods used to interface the two systems.
As with the previous configuration step, this step also relates to the automatic collection and transfer of data from an external system to the SAP R/3 system. If this is required, work closely with the developers or programmers to determine how these settings should be set to meet the needs of the Plant Maintenance module in relation to the methods used to interface the two systems.
Define Plant Sections
This setting is typically used to represent individuals responsible for certain areas of a plant based on production responsibility. The intent is that, should a problem occur in a certain area of the plant, the person responsible can be determined and notified. This IMG entry is a duplicate of entries in the “Technical Objects” and “Maintenance Plans” areas.
This setting is typically used to represent individuals responsible for certain areas of a plant based on production responsibility. The intent is that, should a problem occur in a certain area of the plant, the person responsible can be determined and notified. This IMG entry is a duplicate of entries in the “Technical Objects” and “Maintenance Plans” areas.
Define Planner Groups
This setting is also a duplicate of settings in the “Technical Objects” and “Maintenance Plans” areas. A maintenance planner group may be composed of one or more people who have the responsibility for planning maintenance work. A maintenance planner group that has been defined for a piece of equipment, for example, will by default appear on work orders related to that piece of equipment.
This setting is also a duplicate of settings in the “Technical Objects” and “Maintenance Plans” areas. A maintenance planner group may be composed of one or more people who have the responsibility for planning maintenance work. A maintenance planner group that has been defined for a piece of equipment, for example, will by default appear on work orders related to that piece of equipment.
Define ABC Indicators
One more duplicate of settings in the “Technical Objects” and “Maintenance Plans” areas, The ABC Indicator field can be used as a means of categorizing equipment. There is no definite use for the field, but it is typically used to represent the importance or criticality of a technical object. Although the values A, B and are provided by default, more may be added or any may be deleted as required.
One more duplicate of settings in the “Technical Objects” and “Maintenance Plans” areas, The ABC Indicator field can be used as a means of categorizing equipment. There is no definite use for the field, but it is typically used to represent the importance or criticality of a technical object. Although the values A, B and are provided by default, more may be added or any may be deleted as required.
Define Shop Papers, Forms and Output Programs
This configuration step controls which shop papers, such as notifications and work orders, are available for printing. Within the configuration step, shop papers specific to notifications maybe defined as well as shop papers specific to work orders. If accustom work order print form has been developed, that form must be defined in this configuration step (or another similar, later configuration step) in order to be available for printing.
This configuration step controls which shop papers, such as notifications and work orders, are available for printing. Within the configuration step, shop papers specific to notifications maybe defined as well as shop papers specific to work orders. If accustom work order print form has been developed, that form must be defined in this configuration step (or another similar, later configuration step) in order to be available for printing.
Define Printer
This heading consists of three settings as follows:
This heading consists of three settings as follows:
- Set User-Specific Print Defaults. If a specific user (or a member of a specific planner group or planning plant)requires a different default printer, language, number of copies, etc., these settings may be made here.
- Define Print Diversion. If a specific shop paper must be printed on a different printer than the default printer, perhaps because it contains sensitive information, the setting for a different printer may be made here.
Print Diversion According to Field Contents
If a specific printer must be used, depending on the value of a particular field, then that setting may be made here.
If a specific printer must be used, depending on the value of a particular field, then that setting may be made here.
Activate Printing in Online Processing
It may be necessary, during the programming of shop papers, totes the functionality during online processing rather than from the update program. The setting to do so may be made here. This setting should be made individually in the instance (system)in which the testing is required, and the setting should note transported. The checkbox should not be checked in the production system.
It may be necessary, during the programming of shop papers, totes the functionality during online processing rather than from the update program. The setting to do so may be made here. This setting should be made individually in the instance (system)in which the testing is required, and the setting should note transported. The checkbox should not be checked in the production system.
Download
The two settings contained in this heading, “Define Destination and Database for PC Download” and “Download Structures top, ” are used to define the method by which notifications and/or work orders (shop papers) may be downloaded to a Microsoft Access database. The online documentation in the Implementation Guide provides further information. Note that, since this setting is grouped under Print Control, The download of a notification or a work order is considered a printout and, as such, the status of the notification or work order will indicate that it has been printed.
The two settings contained in this heading, “Define Destination and Database for PC Download” and “Download Structures top, ” are used to define the method by which notifications and/or work orders (shop papers) may be downloaded to a Microsoft Access database. The online documentation in the Implementation Guide provides further information. Note that, since this setting is grouped under Print Control, The download of a notification or a work order is considered a printout and, as such, the status of the notification or work order will indicate that it has been printed.
![Modules Modules](/uploads/1/2/5/6/125658453/889638996.jpg)
General Order Settlement
This group of configuration steps should not be changed without the involvement of CO (Controlling) or FI/CO personnel. This section is a duplicate of that found in CO configuration, so any changes made here will be reflected in the CO module.
This group of configuration steps should not be changed without the involvement of CO (Controlling) or FI/CO personnel. This section is a duplicate of that found in CO configuration, so any changes made here will be reflected in the CO module.
Maintain Settlement Profiles
This setting provides some integration with the CO (Controlling)module in the R/3 system. Although there are some reasonable defaults provided by SAP, review the defaults to determine whether any changes are required. The default settlement profile most often used by the PM module is “40- Maintenance measure.” Do not make changes to, and do not delete, any of the other settlement profiles without consulting with a person responsible for the configuration or maintenance of the CO module or any other module that may be affected (such as those responsible for the QM(Quality Management) module in the case of “70- QM order”).
This setting provides some integration with the CO (Controlling)module in the R/3 system. Although there are some reasonable defaults provided by SAP, review the defaults to determine whether any changes are required. The default settlement profile most often used by the PM module is “40- Maintenance measure.” Do not make changes to, and do not delete, any of the other settlement profiles without consulting with a person responsible for the configuration or maintenance of the CO module or any other module that may be affected (such as those responsible for the QM(Quality Management) module in the case of “70- QM order”).
In the default settlement profile 40, for example, it is presumed that work orders will be settled. If, for some reason, work orders are not to be settled, the provision for this is contained here. The default object type is “CTR, ” which is a cost center. This presumes that the majority of Plant Maintenance work orders will be settled to a cost center. If this is not the case, the default settlement object type can be changed here.
Among the other settings contained here is a list of valid receivers. This determines whether the user may (or must) settle the work order to types of receivers. While in the majority of cases the receiver may be a cost center, orders can also be settled to a fixed asset, where work performed on the asset may increase the value of the asset, or the settlement may be made to a WBS element, where the work performed in the work order pertains to a Work Breakdown Structure element in a project in the PS(Project Systems) module. Other receivers may be allowed or disallowed as required.
Maintain Allocation Structures
This setting allows the assignment of costs to receiver types. Once again, this setting should only be changed by, or after consulting with, a person responsible for the CO module.
This setting allows the assignment of costs to receiver types. Once again, this setting should only be changed by, or after consulting with, a person responsible for the CO module.
Maintain PA Transfer Structure
This setting allows the definition of cost allocation related to profitability analysis. This is mostly related to sales orders and projects and should only be changed by, or after consulting with, a person responsible for the CO module.
This setting allows the definition of cost allocation related to profitability analysis. This is mostly related to sales orders and projects and should only be changed by, or after consulting with, a person responsible for the CO module.
Assign Value Fields
These value fields are assigned to the PA Transfer Structure. If no changes were made to the PA Transfer Structure in the previous configuration step, then no changes are likely to be made in this configuration step. If changes are required, allow a person responsible for the CO module to make the changes, or do it after consultation with that person.
These value fields are assigned to the PA Transfer Structure. If no changes were made to the PA Transfer Structure in the previous configuration step, then no changes are likely to be made in this configuration step. If changes are required, allow a person responsible for the CO module to make the changes, or do it after consultation with that person.
Define Number Ranges for Settlement Documents
Do not change this setting unless you are also responsible for the configuration of the CO module. It is unlikely that any Plant Maintenance requirements would require a change to the number ranges for settlement documents.
Do not change this setting unless you are also responsible for the configuration of the CO module. It is unlikely that any Plant Maintenance requirements would require a change to the number ranges for settlement documents.
Settings for Display of Costs
This group of configuration steps is relevant to the Plant Maintenance Information System (PMIS) and, if applicable, the Customer Service Information System (CSIS).
This group of configuration steps is relevant to the Plant Maintenance Information System (PMIS) and, if applicable, the Customer Service Information System (CSIS).
Cost elements are used to group costs related to a specific purpose, internal labor for example. A value category can be defined (there/3 system has a few defined by default) to reflect one or more cost elements. For example, if internal labor costs are actually reported through several cost elements, those cost elements can be grouped into a value category, perhaps called “Internal Labor.”Value categories can display the breakdown of costs in the cost display of a work order and are also used to report costs in the PMIS.
Maintain Value Categories
This setting simply allows the definition of value categories, and whether they are related to costs or revenues. Keep in mind, when defining value categories, that they may also be used byte Project Systems (PS) module.
This setting simply allows the definition of value categories, and whether they are related to costs or revenues. Keep in mind, when defining value categories, that they may also be used byte Project Systems (PS) module.
Assign Cost Elements to Value Categories
Cost elements may be assigned to the appropriate value categories here. It may be necessary to work with personnel representing the CO module to determine the cost elements that make up a value category, although the CO Representatives maybe unfamiliar with the term “value category.” Either one cost element or a range of cost elements can be assigned directly to value category. If the appropriate cost elements have not bee nnumbered sequentially, that is, there may be inappropriate cost elements in between the relevant cost elements, the appropriate cost elements must be grouped in a cost element group. The cost element group can then be assigned to the value category.The creation of cost element groups, if required, is usually performed in the CO module.
Cost elements may be assigned to the appropriate value categories here. It may be necessary to work with personnel representing the CO module to determine the cost elements that make up a value category, although the CO Representatives maybe unfamiliar with the term “value category.” Either one cost element or a range of cost elements can be assigned directly to value category. If the appropriate cost elements have not bee nnumbered sequentially, that is, there may be inappropriate cost elements in between the relevant cost elements, the appropriate cost elements must be grouped in a cost element group. The cost element group can then be assigned to the value category.The creation of cost element groups, if required, is usually performed in the CO module.
Check Consistency of Value Category Assignment
After configuring value categories and assigning cost elements to the value categories, this step can be used to evaluate the assignments.It is not restricted to Plant Maintenance-specific assignments,so it may take a few minutes to run, depending on several factors. Use this analysis to determine whether any appropriate cost elements have not been assigned, that the appropriate cost elements are assigned properly, and that cost elements have not been assigned more than once (unless intended, for some reason).
After configuring value categories and assigning cost elements to the value categories, this step can be used to evaluate the assignments.It is not restricted to Plant Maintenance-specific assignments,so it may take a few minutes to run, depending on several factors. Use this analysis to determine whether any appropriate cost elements have not been assigned, that the appropriate cost elements are assigned properly, and that cost elements have not been assigned more than once (unless intended, for some reason).
Define Version for Cost Estimates for Orders
This setting allows cost estimates to be entered for value categories on work orders. There is usually no need to change the default setting that was provided. In any case, only one cost estimate version can be maintained here.
This setting allows cost estimates to be entered for value categories on work orders. There is usually no need to change the default setting that was provided. In any case, only one cost estimate version can be maintained here.
Define Default Values for Value Categories
This setting controls the value categories that are displayed by default on the “Costs” tab within the “Costs” tab (yes, they both have the same name) on a work order. Other categories may be added when viewing the actual work order.
This setting controls the value categories that are displayed by default on the “Costs” tab within the “Costs” tab (yes, they both have the same name) on a work order. Other categories may be added when viewing the actual work order.
Quotation Creation and Billing for Service Orders
This group of configuration steps is related to Customer Service(formerly Service Management) and is not covered here. Nothing in this group is required for configuration of non-Customer Service Plant Maintenance.
This group of configuration steps is related to Customer Service(formerly Service Management) and is not covered here. Nothing in this group is required for configuration of non-Customer Service Plant Maintenance.
Maintenance and Service Notifications
Overview of Notification Type
This item contains numerous options related to notifications .However, the following two sections, “Notification Creation” and “Notification Processing” are best completed before reviewing the options in this step. The options contained here are based on some of the settings available in the following sections.
Overview of Notification Type
This item contains numerous options related to notifications .However, the following two sections, “Notification Creation” and “Notification Processing” are best completed before reviewing the options in this step. The options contained here are based on some of the settings available in the following sections.
The options available in this configuration item are as follows:
- Screen Areas in Notification Header. This allows the definition for the basic layout and information in the notification header. With this option, it is possible to provide a notification layout suitable for maintenance notifications, service notifications (CS module), or quality notifications (QM module). It is also possible to restrict the type of object (functional location, equipment,and/or assembly) for which the notification is created. In addition, certain custom-defined screen areas can be assigned to the notification type.
- Screen Structure for Extended View. This option allows control over which tabs appear on a notification, based on the notification type. Further, by selecting a tab and clicking the magnifying glass icon (“Details”), specific screen areas (groups of fields) can be assigned to a tab, deleted from a tab, or the order of screen areas on a tab can be changed. The name of the tab can be changed and an icon can be assigned to the tab. Any particular tab can be made active or inactive by using the checkbox.
- Screen Structure for Simplified View. This option can be used to defined a simple notification screen, usually with no tabs, and containing only the screen areas(groups of fields) that are entered here. In a later configuration step, “Defined Transaction Start Values, ” the simplified view can be assigned instead of the extended view to a specific transaction (Create, Change, or Display). This setting is also based on notification type.
- Catalogs and Catalog Profiles. Specific catalogs, which usually define damage, cause, activities, etc. available for notifications, can be assigned to the notification. Different sets of catalogs may be defined for different types of notifications. Catalog definition can be performed in the Implementation Guide under the“Notification Content” section, or outside of the Implementation Guide.
- Format Long Text. Long text control can be managed here. There is an option to log changes to long text in notifications as well as an option to prevent changes to long text in notifications. In addition, formatting of long text can be forced through the other options on this screen, which may be more of interest if long text is exported to other applications outside of SAP.
- Priority Type. There may be more than one priority type(which is not the same as priority level) defined in the system. For example, one priority type might apply to work orders, while another priority type might apply to notifications, or one type for maintenance notification sand another type for service notifications. Each priority type may contain a different set of priorities than other priority types. For example, the priority type for maintenance notifications might have only 1 to 3 (high,medium, and low) defined, while the priority type for service notifications might have 1 to 4 (emergency,high, medium, low) defined. This option allows a single notification type to be assigned to a notification type.
- Partner Determination Procedure. The SAP R/3 system is delivered with a default partner determination procedure for PM. Unless a different partner determination procedure has been defined for Plant Maintenance use,the setting here should be “PM” for Plant Maintenance-related notification types.
- Partner Functions, Approval. This option contains settings that can be used to control an approval process for a notification type. Partners can be defined for responsibility,and links to workflow processes can be defined (if Workflow is being used). There is a checkbox that should not be checked if an approval process is not required for notifications.
- Standard Output. Also referred to as “Standard text, ”this option can be used to define text that should appear on notifications by specifying the code of the standard text. This is particularly useful when printing notifications (or later, for work orders). Standard text itself is not defined within the Implementation Guide,but is defined in the SAP system in the menu Tools →Form Printout → SAP Script → Standard Text
- Status Profile. If user-defined statuses are to be used(and have already been defined) in addition to system statuses for notifications, the profile for the appropriate statuses can be specified here, for both the notification itself as well as for tasks in the notification, if required.User statuses, discussed later, can be defined when the SAP-provided system statuses are not sufficient.
- Response Time Monitoring. Used primarily for Customer Service, if response monitoring has been defined, this option can be used to assign a response profile to a notification type.
- Allowed Change of Notification Type. This option can bemused to specify whether a notification can be changed from one notification type to a different notification type,and to specify the original notification types and target notification types for which this action will be permitted.
Notification Creation
This group of configuration steps consists of information relative to the creation of a notification.
This group of configuration steps consists of information relative to the creation of a notification.
Define Notification Types
Three Plant Maintenance-related notification types are delivered by default with the SAP R/3 system. These are:
Three Plant Maintenance-related notification types are delivered by default with the SAP R/3 system. These are:
- Breakdown Report. This notification type provides means to report that an object, such as a piece of equipment, has broken down or failed in some manner. Usually, mean- time- between- failure and meantime-to-repair statistics are associated with this type of notification.
- Maintenance Request. This notification type provides means to request maintenance, often for a non-breakdown situation, although the “Breakdown” indicator is still available.
- Activity Report. This notification type is often used to report activity that has already been performed, in order to track statistical history. Because the activity may have already been performed, this notification type is sometimes created from a work order, while work orders are often created from the other two default notification types.
While additional notification types can be created in this configuration step, it is often found that the original three notification types delivered with the R/3 system by default are adequate for Plant Maintenance.Note that there are additional notification types for Customer Service(Service Management) and Quality Management.
Set Screen Templates for the Notification Type
This configuration step allows some flexibility in the way that notification screen is organized and in which data it includes.At least a notification type must be specified in the initial window that is displayed. The resulting screen will display an overview of the information that the notification type currently contains on its screen. Those items whose “Register” begins with a 10 will appear as tabs on the main notification screen for that notification type.
This configuration step allows some flexibility in the way that notification screen is organized and in which data it includes.At least a notification type must be specified in the initial window that is displayed. The resulting screen will display an overview of the information that the notification type currently contains on its screen. Those items whose “Register” begins with a 10 will appear as tabs on the main notification screen for that notification type.
Items whose “Register” begins with a 20 appear as tabs within the “Items” tab in the system as delivered .A tab (register, in this case) can be selected, and its settings viewed, by using the “Details” (magnifying glass) icon. The title for that tab can be changed from this screen and, if desired, an icon can be added to the tab in addition to, or instead of, the tab description.
Some tabs consist of screen areas that can be changed. A screen area consists of fields that are usually grouped on the screen,often within their own “box.” On some tabs, these screen areas are set and cannot be changed. On tabs where the screen area scan be changed, it is possible to remove groups of fields entirely from the tab, add other screen areas to a tab, or move screen areas from one tab to another. There are restrictions, however,on which tabs to which screen areas can be moved.
Each tab contains a checkbox which, when checked, activates that particular tab. When the checkbox is not checked, that tab will not appear for that notification type. So, it is possible foursome tabs and screen areas to appear for one notification type,but not another.
Define Long Text Control for Notification Types
In addition to the short, 40 character field available to describe notification, a “long text” field is available for longer descriptions.The primary purpose of this configuration step is to either prevent changes to the long text of a notification type or to log any changes to the long text of a notification type.
In addition to the short, 40 character field available to describe notification, a “long text” field is available for longer descriptions.The primary purpose of this configuration step is to either prevent changes to the long text of a notification type or to log any changes to the long text of a notification type.
Set Field Selection for Notifications
As with the other configuration steps that address field selection,this step allows fields on the notification screen to be hidden,highlighted, display only, and so on. The fields can have different attributes, if desired, based on notification type, priority,or several other “influencing” values. With the ability to change field attributes combined with the ability to change screen areas (groups of fields), a considerable amount of manipulation is possible with the notification screens.
As with the other configuration steps that address field selection,this step allows fields on the notification screen to be hidden,highlighted, display only, and so on. The fields can have different attributes, if desired, based on notification type, priority,or several other “influencing” values. With the ability to change field attributes combined with the ability to change screen areas (groups of fields), a considerable amount of manipulation is possible with the notification screens.
Define Number Ranges
See the section on Number Ranges for more details regarding number ranges. This configuration step allows the assignment of number ranges to notification types. It is possible to assign every notification type. to the same number range, it is possible to assign each notification type. its own number range, and it is also possible to combine notification types into number ranges.
See the section on Number Ranges for more details regarding number ranges. This configuration step allows the assignment of number ranges to notification types. It is possible to assign every notification type. to the same number range, it is possible to assign each notification type. its own number range, and it is also possible to combine notification types into number ranges.
As with other number ranges, internal (system assigned) and external (user specified) number ranges can be defined. Generally, external number ranges for notifications are discouraged, particularly where multiple people will be using the system,although there are always exceptions. A couple of reasons to let the system assign numbers to notifications are that it takes more time to enter a number than to let the system do it, and it can be difficult to determine the next valid number if more than one person is responsible for creating notifications.
The overall notification number range is shared with the QM(Quality Management) and CS (Customer Service) modules. Consider the requirements of those modules, whether they are used now or ever may be used in the future, when defining notification number ranges.
If several ranges are to be defined, ensure that the quantity of numbers is much more than adequate. Consider possibilities such as the acquisition of additional plants, etc. If there is even the slightest doubt, spread out the number ranges to allow expansion, if ever required.
The use of the configuration step is not necessarily intuitive. Define the number ranges first. To assign a notification type to an umber range, double-click on the notification type(s), select the number range (check the box), and then click the “Element/Group” button.
Define Transaction Start Values
When a transaction is performed to create, change or display notification, a specific screen appears first, along with a suggested notification type. This configuration allows the default screen and notification type to be changed, if required. The default values are often acceptable for this setting.
When a transaction is performed to create, change or display notification, a specific screen appears first, along with a suggested notification type. This configuration allows the default screen and notification type to be changed, if required. The default values are often acceptable for this setting.
Assign Standard Texts for Short Messages to Notification Types
This configuration step is completely optional. It is possible to define a “standard text” for each notification type. This standard text can be used on notifications of that type simply by specifying the code for that standard text, instead of having to type the entire text each time it is required. The standard text obviously must be defined before it can be assigned to a notification type.The standard text itself is defined elsewhere, not in the implementation Guide, but in the standard SAP Easy Access menu under Tools → Form Printout → SAP script → Standard text Note that in versions of R/3 earlier than Enterprise (4.7), the menu path will likely differ from that shown hereAfter any standard texts have been defined, this configuration step can be used to assign the standard texts to notification types.
This configuration step is completely optional. It is possible to define a “standard text” for each notification type. This standard text can be used on notifications of that type simply by specifying the code for that standard text, instead of having to type the entire text each time it is required. The standard text obviously must be defined before it can be assigned to a notification type.The standard text itself is defined elsewhere, not in the implementation Guide, but in the standard SAP Easy Access menu under Tools → Form Printout → SAP script → Standard text Note that in versions of R/3 earlier than Enterprise (4.7), the menu path will likely differ from that shown hereAfter any standard texts have been defined, this configuration step can be used to assign the standard texts to notification types.
Allowed Change of Notification Type
This configuration step can be used to specify that a notification can be changed from one notification type to another. Only those changes will be permitted that are specified here.
This configuration step can be used to specify that a notification can be changed from one notification type to another. Only those changes will be permitted that are specified here.
Assign Notification Types to Order Types
This configuration step can only be performed after order type shave been defined, which occurs a little later in the implementation Guide. Once order types have been defined, this configuration step can be used to associate notification types with a default work order type. This is not a restriction, but can save a small amount of time when creating a work order from a notification.
This configuration step can only be performed after order type shave been defined, which occurs a little later in the implementation Guide. Once order types have been defined, this configuration step can be used to associate notification types with a default work order type. This is not a restriction, but can save a small amount of time when creating a work order from a notification.
Define Order Types and Special Notification Parameters
This configuration step is only relevant to Customer Service(Service Management) module notifications. It allows a sales order to be created from a service notification and is not required for non-Customer Service-related notifications.
This configuration step is only relevant to Customer Service(Service Management) module notifications. It allows a sales order to be created from a service notification and is not required for non-Customer Service-related notifications.
Notification Content
This group of configuration steps consists of information relative to catalogs,their contents, and how they are related to notification types. Catalogs contain information relative to damage, cause of damage, activities, etc.
This group of configuration steps consists of information relative to catalogs,their contents, and how they are related to notification types. Catalogs contain information relative to damage, cause of damage, activities, etc.
Maintain Catalogs
Catalogs are used to encourage the recording of information that can be analyzed later. The information gathered through the use of catalogs is best analyzed over a period of time(months, for example) and the Plant Maintenance Information System, discussed later, provides a means of reporting the information.
Catalogs are used to encourage the recording of information that can be analyzed later. The information gathered through the use of catalogs is best analyzed over a period of time(months, for example) and the Plant Maintenance Information System, discussed later, provides a means of reporting the information.
The information recorded can be used to identify patterns of damage, cause of damage, maintenance costs associated with types of damage, maintenance costs associated with a particular manufacturer’s equipment, and so on. The SAP R/3 system as delivered contains several catalogs by default In most cases, these catalogs are sufficient, but their contents are not. A catalog has been predefined for each of the cataloger that usually appear on the notification screen.
If the temptation to create additional catalogs arises, be advised that the catalog ID field is limited to one character, and SAP has reserved the characters A through O as well as the digits 0through 9. That leaves only 11 possible additional catalogs that may be defined. Work with the default catalogs, if possible,before attempting to define other catalogs.
Creating and editing catalogs can also be performed outside of the implementation Guide. SAP recommends that the creation and editing of catalogs be performed in the productive system rather than being transported to the productive system. Currently, however,it is still possible to perform this step either in the implementation Guide or outside the Implementation Guide, and manually transport the catalogs individually. That means that,while editing a specific catalog, the menu Table View →Transportcan be used to generate a change request for transport.
Although the creation of catalogs, code groups and codes can be performed outside of the Implementation Guide, the following steps, “Define Catalog Profile” and “Change Catalogs and Catalog Profile for Notification Type, ” must still be performed in the Implementation Guide. With the delivered SAP R/3 system, the following catalog codes are most relevant to Plant Maintenance:
- A—Activities
- B—Object Parts
- C—Overview of Damage
- D—Coding
- 2—Tasks
- 5—Causes
Some of the other default catalogs are more relevant to QM(Quality Management) module use. However, other existing catalogs can be configured for use with Plant Maintenance notification sand, as previously discussed, a limited number of additional catalogs can also be defined if required.With a little imagination, some other uses can be discovered and invented for using catalogs, code groups and codes. This discussion will be limited to those catalogs listed above and for basic purposes.The Activities catalog should usually contain a list of activities that could have been performed to repair a piece of equipment,solve a problem, etc. For example, “Welded, ” “Rewound, ” and“Replaced” are activities. The activities can be grouped as desired. An example of an activity grouping is to arrange the valid activities for a specific type of equipment into a group that reflects that equipment type.
The Object Parts catalog can be used to contain sections, parts,or areas of a piece of equipment for which to track damage and cause. If there is an interest in keeping track of damage to (or because of ) a part of a piece of equipment, a list of Object Part scan be maintained. Often, the grouping of Object Parts is by the type of equipment, since the parts will vary depending on the equipment type. Note that Object Parts should not be confused with replacement parts, spares, parts used to repair the equipment,and so on, although there may be some overlap. This field is not used to keep track of the parts that were used during the maintenance of a piece of equipment.
The Overview of Damage catalog usually contains a list of possible damages. Examples of damage could be “Bent, ” “Cracked, ”“Melted, ” and so on. There are different methods of grouping damage codes. The best method of grouping damage codes will vary, depending on ease of use and the needs of the business.One example of grouping damage codes is, once again, by type of equipment.
The Tasks catalog is sometimes not used, since its most appropriate use is to provide a sequence of steps to perform the required or requested maintenance. Since, for many SAP R/3Plant Maintenance implementations, the required sequence of steps is contained in the work order itself, entering a sequence of steps in the notification may be redundant. Of course, there are exceptions, and for some implementations, the Tasks catalog may be beneficial and even required, especially if the Plant Maintenance system is to be used without work orders. On the other hand, maintaining a catalog for tasks enables the creator of the notification to identify steps to be performed from a standard list. This can, where appropriate, save some time. If used,the Tasks catalog could, in some cases, almost match the Activities catalog, except for the “tense” (future tense, past tense)of the catalog entries. For example, the Tasks catalog could contain
the entries “Weld, ” “Rewind, ” and “Replace, ” while the Activities catalog could contain the entries “Welded, ”“Rewound, ” and “Replaced.” Again, the catalog can be grouped as best suits the requirements of the implementation.
the entries “Weld, ” “Rewind, ” and “Replace, ” while the Activities catalog could contain the entries “Welded, ”“Rewound, ” and “Replaced.” Again, the catalog can be grouped as best suits the requirements of the implementation.
The Causes catalog can be used to contain a list of the possible causes of damage. Some examples of causes of damage could be“Impact, ” “High Temperature, ” “Vandalism, ” and so on.
Causes can be grouped in a number of ways, including by type of equipment. Three of the basic catalogs are used on the standard notification screen in the “Item” screen area (this being on the notification transaction screen while creating, changing, or displaying a notification,not in the Implementation Guide). These are the“Object part, ” “Damage” and “Cause” catalogs.
The two fields beside each of those catalogs are for a code group and a code, respectively. Ideally, the three fields, “Object part, ”“Damage, ” and “Cause” will flow together to make a sentence. For example, the casing (Object part) was cracked (Damage)because of an impact (Cause). It is important to note that the catalog/code structure is not exactly hierarchical. The codes for each catalog are arranged by code groups, but additional levels or groupings (groups of groups, for example) are not possible.
Ideally, it might be desirable to plan and organize the groups and codes in such a way that the list of groups would be short enough to all appear on the screen without scrolling and, likewise, the list of codes in each group would be short enough to all appear on the screen without scrolling. However, real-life requirements often overshadow convenience. Try to provide enough codes for meaningful reporting and analysis, but not so many that it is difficult for the user to select the most appropriate code.
Display Catalog Directory with All Sub-Items
There is nothing to configure here. This step simply provides an overall view of the catalogs, groups and codes selected.
There is nothing to configure here. This step simply provides an overall view of the catalogs, groups and codes selected.
Define Catalog Profile
Catalog profiles can be assigned to functional locations, equipment and other objects. This configuration step provides means of assigning a different selection of codes to different types of equipment, for example.
Catalog profiles can be assigned to functional locations, equipment and other objects. This configuration step provides means of assigning a different selection of codes to different types of equipment, for example.
If two different sets of code groups had been created, one group with the code group ID beginning with “PM” (PM0001,PM0002, etc.) and the other with the code group ID beginning with “QA” (QA0001, QA0002, etc.), the PM code groups can be assigned to a PM catalog profile and the QA code groups can be assigned to a QA catalog profile. The appropriate catalog profile can then be assigned to the appropriate pieces of equip mentor other object. A notification created for a piece of equipment will inherit the catalog profile assigned to that piece of equipment (or from the notification type), so when the damage,cause and other codes are accessed, only the codes relevant to that catalog profile will be displayed.
This configuration can also be used by the QM (Quality Management) module and the CS (Customer Service) module,so assign the appropriate code groups to at least one relevant Plant Maintenance-related catalog profile.
Change Catalogs and Catalog Profile for Notification Type
In this configuration step, the appropriate catalog profile previously created can be assigned to one or more notification types.In addition, the appropriate catalogs can be assigned to notification types. If a different catalog was previously defined for a specific use, the catalog can be associated with one or more specific notification types here. Any catalogs that are definitely not desired on the notification screen can be removed here.
In this configuration step, the appropriate catalog profile previously created can be assigned to one or more notification types.In addition, the appropriate catalogs can be assigned to notification types. If a different catalog was previously defined for a specific use, the catalog can be associated with one or more specific notification types here. Any catalogs that are definitely not desired on the notification screen can be removed here.
In Summary:
- Determine which catalogs to maintain (Object part,damage, cause, tasks, activities).
- Create a selection of groups and codes for each catalog(can take some time).
- Assign the catalogs and groups to one or more catalog profiles.
- Assign the catalogs and profiles to notification types
Define Partner Determination Procedure and Partner Function
In SAP terminology, a partner is an entity that can be associated with an object in any way. In this instance, the object is a notification. For most implementations, the default settings for this configuration step will provide the required functionality.
In SAP terminology, a partner is an entity that can be associated with an object in any way. In this instance, the object is a notification. For most implementations, the default settings for this configuration step will provide the required functionality.
Regardless of whether changes are made to partner determination procedures, review this configuration step to ensure that the PM (Plant Maintenance) partner determination procedure(or a different partner determination procedure, if more appropriate)is assigned to the relevant PM-related notification types,particularly if additional notification types have been defined.
Review the partner functions that have been assigned to the notification types if changes are required. If desired, an approval process can be assigned to notifications. To use the approval process function, check the “Approval required” checkbox and press the “Enter” key on the keyboard. The additional fields will appear. Do not check the “Approval required” checkbox if this type of approval process is not required.
Field Selection for List Display of Partner Data
This configuration section can be used to control which data appears in lists of various partners. For example, when a list of vendor data is displayed, the vendor-relevant fields that appear are those specified in this configuration setting. Some defaultsare provided.
This configuration section can be used to control which data appears in lists of various partners. For example, when a list of vendor data is displayed, the vendor-relevant fields that appear are those specified in this configuration setting. Some defaultsare provided.
Notification Processing
This group of configuration steps consists of information relative to the processing of a notification.
This group of configuration steps consists of information relative to the processing of a notification.
Response Time Monitoring
This configuration section is more suited to use with the CS(Customer Service) module rather than with standard Plant maintenance functionality. The first setting, also found elsewhere in the IMG, allows the creation and assignment of priority types and priorities. The second setting allows the definition of a sequence of tasks to be performed within a specific time period that can be proposed on a notification.The sequence of tasks is based on a response profile.
This configuration section is more suited to use with the CS(Customer Service) module rather than with standard Plant maintenance functionality. The first setting, also found elsewhere in the IMG, allows the creation and assignment of priority types and priorities. The second setting allows the definition of a sequence of tasks to be performed within a specific time period that can be proposed on a notification.The sequence of tasks is based on a response profile.
Additional Functions
This configuration section is primarily suited for workflow functionality. These settings provide a gateway to additional functions that can be performed with notifications, some provided by SAP, others that can be added as required. If workflow functionality. is not required, no changes to these settings are required. Since workflow functionality is not discussed in this publication, changes to these configuration settings will depend on workflow requirements. If, by default, the “Action box” appears on notification screens,it can be adjusted or removed by changing the settings in this section of configuration.
This configuration section is primarily suited for workflow functionality. These settings provide a gateway to additional functions that can be performed with notifications, some provided by SAP, others that can be added as required. If workflow functionality. is not required, no changes to these settings are required. Since workflow functionality is not discussed in this publication, changes to these configuration settings will depend on workflow requirements. If, by default, the “Action box” appears on notification screens,it can be adjusted or removed by changing the settings in this section of configuration.
Notification Print Control
This configuration section can be used to define and control which “shop papers” can be printed and where.
This configuration section can be used to define and control which “shop papers” can be printed and where.
Define Shop Papers, Forms and Output Programs
If the standard default SAP R/3 notifications are being used, this setting will contain some default shop papers that can be printed from notifications. Whether or not the default notifications are used, additional and/or alternate shop papers can be defined.
If the standard default SAP R/3 notifications are being used, this setting will contain some default shop papers that can be printed from notifications. Whether or not the default notifications are used, additional and/or alternate shop papers can be defined.
If interested in printing notifications, review the shop papers that are available by default. If the default shop papers are not adequate,determine the layout that will be required. The development of the shop papers is usually performed by programmers.
If non-default shop papers are created, the shop papers can be made available (linked) from the notification with these settings .Within this setting, it is also possible to link specific shop papers to specific notification types, if there is a reason to do so. In addition, shop papers can be set to print by default when the print functionality is accessed from a notification.
Define Printer
This configuration setting contains three sub-settings:
This configuration setting contains three sub-settings:
- User-Specific Print Control. This setting can be used to control which shop papers are printed on which printer(s) based on the user ID and the shop paper. Additional print options can be set.
- Define Print Diversion. This determines whether print diversion (directing a shop paper to a different printer)is active for specific shop papers.
- Print Diversion According to Field Contents. This setting can be used primarily to control whether a shop paper is diverted to a different printer based on the value contained in a specified notification field. For example, if the notification contains a specific equipment numbering the equipment field, a specific shop paper can be diverted to a different printer than usual. Print diversion,when it applies, overrides user-specific settings.
User Status for Notifications
The configuration settings contained in this section need not be changed unless the system statuses for notification are not adequate.
The configuration settings contained in this section need not be changed unless the system statuses for notification are not adequate.
Define Status Profile
This configuration setting can be found in several places throughout Plant Maintenance configuration as well as configuration for other modules. A default profile may already exist for notifications. If an additional profile is created, prefix the status profile with the letter Z. Although conflicts with SAP named objects are rare, beginning configuration objects with the letter Z guarantees that there will be no current or future conflicts with SAP named objects.
This configuration setting can be found in several places throughout Plant Maintenance configuration as well as configuration for other modules. A default profile may already exist for notifications. If an additional profile is created, prefix the status profile with the letter Z. Although conflicts with SAP named objects are rare, beginning configuration objects with the letter Z guarantees that there will be no current or future conflicts with SAP named objects.
Determine what statuses are required before proceeding further. Then determine whether only one status at a time will be permitted and which status will be the initial user status when notification is created. From this point, there are two methods of defining status profiles. One allows a single status at a time, while the other allows multiple statuses to be active at the same time.
To limit the user status field on a notification to one status at a time, use the “Lowest” and “Highest” fields. These fields refer to the status numbers, the first field on the list of user statuses. From any given user status, the only other user status that can beset is determined by the “Lowest” and “Highest” fields. Refer to“Figure 10: User Status Profile Configuration.”
For example, if the user status “Completed” (status number 5) has the “Lowest” and “Highest” fields both set to 5, no other user status can be set. However, if the “Lowest” field is set to 4 and the“Highest” field is set to 5, then the user status can be changed to 4(“Active, ” for example) or remain at 5 (“Completed”).
If multiple user statuses are required at the same time, the“Position” and “Priority” fields must be used instead of the“Highest” and “Lowest” fields. There is enough space in the user status field on a notification to contain several user statuses. Each status that appears at the same time occupies a “position.” The leftmost position in the status field is Position 1, the next status occupies Position 2, and so on. In this configuration step, one or more user statuses can be assigned to position 1, one or more to position 2, etc.If more than one status is assigned to position 1, which one is displayed on the notification screen is determined by its Priority and whether or not it has been set by the user.
User status profile configuration.
Regardless of which method is used, some time should be taken to organize the statuses and determine the combinations and the order in which statuses will be set. Test the settings to ensure that the user statuses will function as required.
In addition, an authorization code can be set for each status. This can be used to control who can change a user status, but must be defined in co-operation with SAP security. The security person/team must ensure that the specified authorization codes are included in the authorizations for the appropriate users.There is one additional step to be performed in this configuration setting. This is to assign the user status profile to the appropriate notification types. Note that, if required, status profiles can be assigned in this step to notification tasks as well as to the notifications themselves.
Create Authorization Keys for User Status Authorizations
This configuration step can be used to create the authorization code/key as previously mentioned. This is only required when only specific users should be permitted to change user statuses on notifications.
This configuration step can be used to create the authorization code/key as previously mentioned. This is only required when only specific users should be permitted to change user statuses on notifications.
It is possible that only those responsible for security will be permitted to set this configuration. If this configuration is not restricted, work with those responsible for security to at least ensure compatibility with security standards and procedures.
Maintain Selection Profiles
This configuration setting can be used to define a combination of statuses for use in searching for, in this case, notifications. On the “List display” or “List change” screens, there is a field to specify a selection profile. If a selection profile has been defined here, that selection profile can be specified instead of the user being required to determine and specify each desired status.
This configuration setting can be used to define a combination of statuses for use in searching for, in this case, notifications. On the “List display” or “List change” screens, there is a field to specify a selection profile. If a selection profile has been defined here, that selection profile can be specified instead of the user being required to determine and specify each desired status.
Object Information
The Object Information window can be configured with the settings in this section. The Object Information window is available from the notification and work order screens and contains information relative to the object(equipment or functional location, for example) for which the notification or work order were created. The Object Information window can also be configured to appear automatically when notifications or work orders recreated. see below.
The Object Information window can be configured with the settings in this section. The Object Information window is available from the notification and work order screens and contains information relative to the object(equipment or functional location, for example) for which the notification or work order were created. The Object Information window can also be configured to appear automatically when notifications or work orders recreated. see below.
The “Object Information” window.
The Object Information window can show recent notifications and/or work orders for the same object within a specified time period. It can also draw attention to thresholds that have been met or exceeded, such as number of breakdowns, number of orders created, etc. within the specified time period. For example, if more than three breakdowns have been reported for the same piece of equipment over the past 90 days, attention will be drawn to that statistic, if the Object Information window has been configured as such.
The Object Information window, does not appearing the Implementation Guide. The configuration settings in the Implementation Guide control whether or not the Object Information window appears automatically, under what conditions, and what information is displayed in the window. The window itself, as shown, appears during the creation of a notification or a work order, for example.
Two benefits of the Object Information window is that duplicate reporting of a problem for which a notification has already been created can be reduced, as well as attention being drawn to an object that seems to have recurring problem.
Define Object Information Keys
A default Object Information Key, PM, is provided for Plant Maintenance purposes. If the Object Information window seems useful, the default Object Information Key can be modified as required. An alternate Object Information Key can be created to use instead of the default provided and, if desired,multiple Object Information Keys can be created for various purposes and assigned to different notification types.
A default Object Information Key, PM, is provided for Plant Maintenance purposes. If the Object Information window seems useful, the default Object Information Key can be modified as required. An alternate Object Information Key can be created to use instead of the default provided and, if desired,multiple Object Information Keys can be created for various purposes and assigned to different notification types.
If the Object Information window does not seem useful, confirm that the “automatically” checkbox is unchecked in this configuration step. The Object Information window will still be available on demand by clicking a button on the notification or work order screen, but will not appear automatically.The other areas in this configuration step are as follows:
- Reference for notification and class selection.— Specify whether the information contained in the Object Information window pertains to the object itself, the object and its superior object, or to the object’s structure(presuming one exists).
- Info. System--time frame and threshold values. Specify the num