ale-dp/sap-fiori-apps huggingface dataset:
Create Settlement Unit
Application component: Energy Data Management
App type: SAP GUI
Description:   Settlement units allow you to control, which points of delivery are selected for settlement. The result of a settlement consists of at least one result profile (with the consumption values per interval) being updated for each settlement unit within the settlement period.
Change Settlement Unit
Application component: Energy Data Management
App type: SAP GUI
Description:   Settlement units allow you to control, which points of delivery are selected for settlement. The result of a settlement consists of at least one result profile (with the consumption values per interval) being updated for each settlement unit within the settlement period.
Display Settlement Unit
Application component: Energy Data Management
App type: SAP GUI
Description:   Settlement units allow you to control, which points of delivery are selected for settlement. The result of a settlement consists of at least one result profile (with the consumption values per interval) being updated for each settlement unit within the settlement period.
Create Selection Variant
Application component: Energy Data Management
App type: SAP GUI
Description:  You use this app to create, change, and display selection variants.
Change Selection Variant
Application component: Energy Data Management
App type: SAP GUI
Description:  You use this app to create, change, and display selection variants.
Display Selection Variant
Application component: Energy Data Management
App type: SAP GUI
Description:  You use this app to create, change, and display selection variants.
Change Inspection List
Application component: Processing
App type: SAP GUI
Description:   You create the inspection list for inspection planning. You cannot access the inspection list as a whole, but rather via campaigns for a specific period. A technical installation or piece of equipment can only be contained in one campaign. Otherwise you can include the objects in another campaign if the inspection is completed in the first campaign. This means if the completion date is set.  On the basis of the campaign, you have the following options: Create/enhance the inspection list  You create and enhance the inspection list on the same screen. You can use different selection criteria, such as divisions. When you create the inspection list, you can determine whether you want to include only technical installations or only equipment. When you enhance an existing inspection list, you can also determine the other current objects. When you create and enhance the inspection list, you can directly enter a technical installation or a piece of equipment.  Change the inspection list You can delete technical installations or equipment without a work order/notification from the list. You can technically complete work orders or notifications.   You also set the last inspection date at the same time. You can only complete an inspection that is bundled with other inspections in a work order or a notification, if the other inspections are also completed. Display the inspection list
Create Inspection List
Application component: Processing
App type: SAP GUI
Description:   You create the inspection list for inspection planning. You cannot access the inspection list as a whole, but rather via campaigns for a specific period. A technical installation or piece of equipment can only be contained in one campaign. Otherwise you can include the objects in another campaign if the inspection is completed in the first campaign. This means if the completion date is set.  On the basis of the campaign, you have the following options: Create/enhance the inspection list  You create and enhance the inspection list on the same screen. You can use different selection criteria, such as divisions. When you create the inspection list, you can determine whether you want to include only technical installations or only equipment. When you enhance an existing inspection list, you can also determine the other current objects. When you create and enhance the inspection list, you can directly enter a technical installation or a piece of equipment.  Change the inspection list You can delete technical installations or equipment without a work order/notification from the list. You can technically complete work orders or notifications.   You also set the last inspection date at the same time. You can only complete an inspection that is bundled with other inspections in a work order or a notification, if the other inspections are also completed. Display the inspection list
Display Inspection List
Application component: Processing
App type: SAP GUI
Description:   You create the inspection list for inspection planning. You cannot access the inspection list as a whole, but rather via campaigns for a specific period. A technical installation or piece of equipment can only be contained in one campaign. Otherwise you can include the objects in another campaign if the inspection is completed in the first campaign. This means if the completion date is set.  On the basis of the campaign, you have the following options: Create/enhance the inspection list  You create and enhance the inspection list on the same screen. You can use different selection criteria, such as divisions. When you create the inspection list, you can determine whether you want to include only technical installations or only equipment. When you enhance an existing inspection list, you can also determine the other current objects. When you create and enhance the inspection list, you can directly enter a technical installation or a piece of equipment.  Change the inspection list You can delete technical installations or equipment without a work order/notification from the list. You can technically complete work orders or notifications.   You also set the last inspection date at the same time. You can only complete an inspection that is bundled with other inspections in a work order or a notification, if the other inspections are also completed. Display the inspection list
Create Work Orders and Notifications
Application component: Processing
App type: SAP GUI
Description:   You use this function on the basis of a campaign to create inspection orders or notifications for technical installations or equipment. You can enter an explicit start or end date that is used as the scheduling date instead of the next inspection date.  
Key features:   The following functions exist in Customizing for inspection periods:  If you have created a specific order or notification code it is used for the creation of the order or notification. If you have not created a code, one of the following codes is used for the creation of the order or notification: INSP (Bundling at equipment level)   Either a work order or notification is created for each piece of equipment or technical installation. The technical installation or piece of equipment is the reference object. INS2 (Bundling at connection object level)  Either a work order or notification is created for each connection object. The equipment or technical installations are allocated, according to the code, to a work order or notification via the object link. The equipment or technical installations in the work order are also in the object list.   During migration you can provide an overriding order or notification code for the objects, which corresponds to the technical installations equipment in the SAP system. This code is used for order or notification creation instead of the code set in Customizing. It is saved in internal table EWMOBJINSP.
Create Register Group
Application component: Device Management
App type: SAP GUI
Description:   This component groups together the registers of one device category or one device, including technical data (such as number of digits and type of display) and billing data (such as rate usage type). Registers meter consumption and demand. Registers can be actual physical devices or displays in electronic devices.  
Key features:   You can manage registers of different division categories in one register group. You can allocate a main division category to the register group. At least one register of the register group must be in the main division category.
Change Register Group
Application component: Device Management
App type: SAP GUI
Description:   This component groups together the registers of one device category or one device, including technical data (such as number of digits and type of display) and billing data (such as rate usage type). Registers meter consumption and demand. Registers can be actual physical devices or displays in electronic devices.  
Key features:   You can manage registers of different division categories in one register group. You can allocate a main division category to the register group. At least one register of the register group must be in the main division category.
Display Register Group
Application component: Device Management
App type: SAP GUI
Description:   This component groups together the registers of one device category or one device, including technical data (such as number of digits and type of display) and billing data (such as rate usage type). Registers meter consumption and demand. Registers can be actual physical devices or displays in electronic devices.  
Key features:   You can manage registers of different division categories in one register group. You can allocate a main division category to the register group. At least one register of the register group must be in the main division category.
Create Input/Output Group
Application component: Device Management
App type: SAP GUI
Description:  You can use this app to group together the inputs and outputs that are valid for a device category or a device and describe their technical data. Inputs and outputs are interfaces for devices. In the case of remote meters for example, there are several impulse inputs and an interface to the modem.
Change Input/Output Group
Application component: Device Management
App type: SAP GUI
Description:  You can use this app to group together the inputs and outputs that are valid for a device category or a device and describe their technical data. Inputs and outputs are interfaces for devices. In the case of remote meters for example, there are several impulse inputs and an interface to the modem.
Display Input/Output Group
Application component: Device Management
App type: SAP GUI
Description:  You can use this app to group together the inputs and outputs that are valid for a device category or a device and describe their technical data. Inputs and outputs are interfaces for devices. In the case of remote meters for example, there are several impulse inputs and an interface to the modem.
Create Command
Application component: Device Management
App type: SAP GUI
Description:  You can use this app to define commands and combine them as groups. A command is a signal sent by the utilities company, which triggers the ripple control receiver (ARCR) to start a switching procedure.
Change Command
Application component: Device Management
App type: SAP GUI
Description:  You can use this app to define commands and combine them as groups. A command is a signal sent by the utilities company, which triggers the ripple control receiver (ARCR) to start a switching procedure.
Display Command
Application component: Device Management
App type: SAP GUI
Description:  You can use this app to define commands and combine them as groups. A command is a signal sent by the utilities company, which triggers the ripple control receiver (ARCR) to start a switching procedure.
Create Command Group
Application component: Device Management
App type: SAP GUI
Description:  You can use this app to define commands and combine them as groups. A command is a signal sent by the utilities company, which triggers the ripple control receiver (ARCR) to start a switching procedure.
Change Command Group
Application component: Device Management
App type: SAP GUI
Description:  You can use this app to define commands and combine them as groups. A command is a signal sent by the utilities company, which triggers the ripple control receiver (ARCR) to start a switching procedure.
Display Command Group
Application component: Device Management
App type: SAP GUI
Description:  You can use this app to define commands and combine them as groups. A command is a signal sent by the utilities company, which triggers the ripple control receiver (ARCR) to start a switching procedure.
Create Device Group
Application component: Device Management
App type: SAP GUI
Description:   In this component you can group together devices that form a logical unit. All devices in a device group must currently either be installed or not installed.  If you install or remove a device in a device group , all other devices in the group are automatically drawn for removal or installation. This ensures that devices that belong together are not accidentally installed or removed. You must confirm the replacement of each device in a device group.  
Key features:   You can:  Maintain and display the history of the device group  When you do this, you can change the current time slice. You can decide whether the device group is to be prorated to the change date, that is, whether you wish to start a new time slice. You can display change documents and creation data. Inspect the device group  The system checks the device group for general and special restrictions. For more information, see the online help for the following fields: Device group Group type Group category  Terminate the device group.  When you terminate a device group, all devices are removed from the group. The device group is empty and can be used for new devices. Delete the device group.  When you delete a device group, it is deleted from the system entirely.
Change Device Group
Application component: Device Management
App type: SAP GUI
Description:   In this component you can group together devices that form a logical unit. All devices in a device group must currently either be installed or not installed.  If you install or remove a device in a device group , all other devices in the group are automatically drawn for removal or installation. This ensures that devices that belong together are not accidentally installed or removed. You must confirm the replacement of each device in a device group.  
Key features:   You can:  Maintain and display the history of the device group  When you do this, you can change the current time slice. You can decide whether the device group is to be prorated to the change date, that is, whether you wish to start a new time slice. You can display change documents and creation data. Inspect the device group  The system checks the device group for general and special restrictions. For more information, see the online help for the following fields: Device group Group type Group category  Terminate the device group.  When you terminate a device group, all devices are removed from the group. The device group is empty and can be used for new devices. Delete the device group.  When you delete a device group, it is deleted from the system entirely.
Display Device Group
Application component: Device Management
App type: SAP GUI
Description:   In this component you can group together devices that form a logical unit. All devices in a device group must currently either be installed or not installed.  If you install or remove a device in a device group , all other devices in the group are automatically drawn for removal or installation. This ensures that devices that belong together are not accidentally installed or removed. You must confirm the replacement of each device in a device group.  
Key features:   You can:  Maintain and display the history of the device group  When you do this, you can change the current time slice. You can decide whether the device group is to be prorated to the change date, that is, whether you wish to start a new time slice. You can display change documents and creation data. Inspect the device group  The system checks the device group for general and special restrictions. For more information, see the online help for the following fields: Device group Group type Group category  Terminate the device group.  When you terminate a device group, all devices are removed from the group. The device group is empty and can be used for new devices. Delete the device group.  When you delete a device group, it is deleted from the system entirely.
Run Full Replacement
Application component: Device Installation
App type: SAP GUI
Description:  This process enables you to replace devices. Example You replace a double-rate meter as part of a periodic replacement or due to damage. Note You can replace devices that have different measuring types. However, you may have to change the measuring types in the device allocation data.
Run Full Installation
Application component: Device Installation
App type: SAP GUI
Description:  You can use this app to install devices in the following ways: Technical installation only, for example if a meter is not to be billed. This would apply in the case of a control meter or a meter that belongs to the utility company.First technical, then billing-related installation, for example if   Meters in an apartment building are installed first and assigned to apartments later   Both steps are carried out by different agents   One technical installation and several billing-related installations exist. This would apply in the case of a pressure regulator or an ARCR that controls several installations.   Full installation, as in the case of a single-family home.
Run Full Removal
Application component: Device Installation
App type: SAP GUI
Description: You can remove devices in the following ways: Technical removal only, if a device (such as a control meter) has undergone technical installation only. Billing-related removal only, if a device in an installation is no longer to be included in billingFirst billing-related and technical removal later, for example if billing and technical areas at a utilities company are managed by different employees.One billing-related and several technical removals. This would apply in the case of a pressure regulator or an ARCR that controls several installations. Full removal, for example in the case of a single-family home that is dismantled.
Run Technical Installation
Application component: Device Installation
App type: SAP GUI
Description:  You can use this app to install devices in the following ways: Technical installation only, for example if a meter is not to be billed. This would apply in the case of a control meter or a meter that belongs to the utility company.First technical, then billing-related installation, for example if   Meters in an apartment building are installed first and assigned to apartments later   Both steps are carried out by different agents   One technical installation and several billing-related installations exist. This would apply in the case of a pressure regulator or an ARCR that controls several installations.   Full installation, as in the case of a single-family home.
Run Billing-Related Installation
Application component: Device Installation
App type: SAP GUI
Description:  You can use this app to install devices in the following ways: Technical installation only, for example if a meter is not to be billed. This would apply in the case of a control meter or a meter that belongs to the utility company.First technical, then billing-related installation, for example if   Meters in an apartment building are installed first and assigned to apartments later   Both steps are carried out by different agents   One technical installation and several billing-related installations exist. This would apply in the case of a pressure regulator or an ARCR that controls several installations.   Full installation, as in the case of a single-family home.
Run Billing-Related Removal
Application component: Device Installation
App type: SAP GUI
Description: You can remove devices in the following ways: Technical removal only, if a device (such as a control meter) has undergone technical installation only. Billing-related removal only, if a device in an installation is no longer to be included in billingFirst billing-related and technical removal later, for example if billing and technical areas at a utilities company are managed by different employees.One billing-related and several technical removals. This would apply in the case of a pressure regulator or an ARCR that controls several installations. Full removal, for example in the case of a single-family home that is dismantled.
Run Technical Removal
Application component: Device Installation
App type: SAP GUI
Description: You can remove devices in the following ways: Technical removal only, if a device (such as a control meter) has undergone technical installation only. Billing-related removal only, if a device in an installation is no longer to be included in billingFirst billing-related and technical removal later, for example if billing and technical areas at a utilities company are managed by different employees.One billing-related and several technical removals. This would apply in the case of a pressure regulator or an ARCR that controls several installations. Full removal, for example in the case of a single-family home that is dismantled.
Change Device Information Record
Application component: Device Installation
App type: SAP GUI
Description:   When carrying out billing functions, the complete IS-U Device Management (IS-U-DM) does not have to be used. Instead, you can create a device information record that only manages device data required for billing, for example, rate data, device allocations, register relationships and maintenance of logical registers.  About AMI-relevant device information records  If you are working within an advanced metering infrastructure, you can indicate that device information records are AMI-relevant. In this case the devices and device information records have additional attributes: For more information, see Advanced Metering Infrastructure .   Remote disconnection and reconnection processes also apply to device information records.However, you can prevent remote disconnection or reconnection by implementing a validation within the BAdI ISU_AMI_DISCONNECT .
Modify Device
Application component: Device Installation
App type: SAP GUI
Description:  This function allows you to change device data and register data. This function does not allow you to change device categories, however. 
Business roles: Billing Specialist (Utilities)| Meter Data Specialist (Utilities)
Meter Data Specialist (Utilities) : 
Is responsible for providing accurate and complete utilities measurement data (register readings, load profiles) in time. Works in the back-office. Organizes and supervises the acquisition of measurement data.

Billing Specialist (Utilities) : 
Is responsible for providing accurate and complete utilities bills for the end customers in time. Works in the back-office. Supervises the billing, invoicing and bill print processes.
Display Device Information Record
Application component: Device Installation
App type: SAP GUI
Description:   When carrying out billing functions, the complete IS-U Device Management (IS-U-DM) does not have to be used. Instead, you can create a device information record that only manages device data required for billing, for example, rate data, device allocations, register relationships and maintenance of logical registers.  About AMI-relevant device information records  If you are working within an advanced metering infrastructure, you can indicate that device information records are AMI-relevant. In this case the devices and device information records have additional attributes: For more information, see Advanced Metering Infrastructure .   Remote disconnection and reconnection processes also apply to device information records.However, you can prevent remote disconnection or reconnection by implementing a validation within the BAdI ISU_AMI_DISCONNECT .   
Business roles: Billing Specialist (Utilities)| Meter Data Specialist (Utilities)
Billing Specialist (Utilities) : 
Is responsible for providing accurate and complete utilities bills for the end customers in time. Works in the back-office. Supervises the billing, invoicing and bill print processes.

Meter Data Specialist (Utilities) : 
Is responsible for providing accurate and complete utilities measurement data (register readings, load profiles) in time. Works in the back-office. Organizes and supervises the acquisition of measurement data.
Create Device Information Record
Application component: Device Installation
App type: SAP GUI
Description:   When carrying out billing functions, the complete IS-U Device Management (IS-U-DM) does not have to be used. Instead, you can create a device information record that only manages device data required for billing, for example, rate data, device allocations, register relationships and maintenance of logical registers.  About AMI-relevant device information records  If you are working within an advanced metering infrastructure, you can indicate that device information records are AMI-relevant. In this case the devices and device information records have additional attributes: For more information, see Advanced Metering Infrastructure .   Remote disconnection and reconnection processes also apply to device information records.However, you can prevent remote disconnection or reconnection by implementing a validation within the BAdI ISU_AMI_DISCONNECT .
Reverse Installation/Removal/Replacement
Application component: Device Installation
App type: SAP GUI
Description:  You use this function to reverse a technical installation, removal or replacement. If you carried out both a billing-related and a technical installation, removal or replacement, see also: Reversing Device Removals  Reversing Device Installations  Reversing Device Replacements  
Key features:  Full installation, removal or replacement This function does not make changes to the data of the following objects: Register relationships and reference values Statistics records Device allocations for controlling devices Blocked devices Device groups Note The reversal does not take into account any device transfers you have carried out.  Reverse Installation When you perform an installation reversal, the following is changed: Technical installation in the Utilities Industry (IS-U) and Plant Maintenance and Service Management (PM) components are canceled. A removal is carried out in PM at the time of installation. The allocations of controlled devices (such as those controlled by ripple control receivers) are terminated. The device location that you created during installation is not deleted.  Reverse Removal A removal reversal results in the termination of a technical removal in the Utilities Industry (IS-U) and Plant Maintenance (PM) components. An installation is carried out in PM at the time of removal.  Reverse Replacement A reversal replacement results in the termination of a device replacement in the Utilities Industry (IS-U) application component In the Plant Maintenance and Service Management (PM) component, the old device is automatically re-installed and the current device is removed.  Meter Data Unification and Synchronization (MDUS) System Notification for AMI Devices If you work within an advanced metering infrastructure (AMI) environment, the system notifies the MDUS system as soon as you reverse an installation, replacement or removal of an AMI device (for example, a smart meter or advanced meter).
Reverse Installation
Application component: Device Installation
App type: SAP GUI
Description:  This procedure enables you to cancel device installations
Reverse Technical Replacement
Application component: Device Installation
App type: SAP GUI
Description:  This procedure enables you to reverse device replacements.
Reverse Technical Removal
Application component: Device Installation
App type: SAP GUI
Description:  This procedure enables you to cancel device removals.
Change Logical Register Number
Application component: Device Installation
App type: SAP GUI
Description:  The logical register number creates the connection between the technical register, which actually exists and the logical register, which is ultimately dependent on the rate data and ultimately on billing. The allocation of the technical register to the logical register occurs implicitly during a technical device installation. You must maintain the logical register number again if you replace devices using the separate installation and removal functions instead of the device replacement function. 
Key features:  The logical register number is maintained historically. Time slices in periods that have already been billed can no longer be changed. These time slices can only be displayed. However, you can divide one time slice into two slices and maintain them. If you do this, the selected registers for one key date and the registers for the previous day are displayed on one screen. The register is then allocated by copying the logical register number for a different register. The logical register number is represented by a four-digit dummy number.
Display Logical Register Number
Application component: Device Installation
App type: SAP GUI
Description:  The logical register number creates the connection between the technical register, which actually exists and the logical register, which is ultimately dependent on the rate data and ultimately on billing. The allocation of the technical register to the logical register occurs implicitly during a technical device installation. You must maintain the logical register number again if you replace devices using the separate installation and removal functions instead of the device replacement function. 
Key features:  The logical register number is maintained historically. Time slices in periods that have already been billed can no longer be changed. These time slices can only be displayed. However, you can divide one time slice into two slices and maintain them. If you do this, the selected registers for one key date and the registers for the previous day are displayed on one screen. The register is then allocated by copying the logical register number for a different register. The logical register number is represented by a four-digit dummy number.
Maintain Rate Data
Application component: Device Installation
App type: SAP GUI
Description:   The rate data of a device provides the basis for billing the device in an installation. Rate data exists at the device and register levels. Rate data at the device level is required for device rental prices. Rate data at the register level is required for settlement of consumption and demand.  Rate data is divided into multiple-installation data and installation-specific data. Multiple-installation data is unique for all installations to which the device is allocated. Installation-specific data is maintained independently of the installation. Multiple-installation data might include the thermal gas billing procedure and the linear and percentage consumption portion. Installation-specific data might include the indicator for relevance to billing, the rate type and the price class. 
Key features:   Rate data is maintained historically.  Time slices in periods that have already been billed can no longer be changed. These time slices can only be displayed. However, you can divide one time slice into two slices and maintain them. Multiple-installation data is displayed on one line with the installation-specific data. If you change multiple-installation data, this affects all installations to which the register is allocated. If you must maintain the rate data of a register in several installations at once, then you can only enter multiple-installation data in the first line of the register. In the subsequent lines for the register that apply to other installations, the multiple-installation data is only displayed.
Display Rate Data
Application component: Device Installation
App type: SAP GUI
Description:   The rate data of a device provides the basis for billing the device in an installation. Rate data exists at the device and register levels. Rate data at the device level is required for device rental prices. Rate data at the register level is required for settlement of consumption and demand.  Rate data is divided into multiple-installation data and installation-specific data. Multiple-installation data is unique for all installations to which the device is allocated. Installation-specific data is maintained independently of the installation. Multiple-installation data might include the thermal gas billing procedure and the linear and percentage consumption portion. Installation-specific data might include the indicator for relevance to billing, the rate type and the price class. 
Key features:   Rate data is maintained historically.  Time slices in periods that have already been billed can no longer be changed. These time slices can only be displayed. However, you can divide one time slice into two slices and maintain them. Multiple-installation data is displayed on one line with the installation-specific data. If you change multiple-installation data, this affects all installations to which the register is allocated. If you must maintain the rate data of a register in several installations at once, then you can only enter multiple-installation data in the first line of the register. In the subsequent lines for the register that apply to other installations, the multiple-installation data is only displayed.
Maintain Device Allocation
Application component: Device Installation
App type: SAP GUI
Description:   This function enables you to allocate devices to one another and store additional attributes.  A distinction is made between controlled devices, such as meters, and controlling devices, such as a transformer switched in series. 
Key features:   Device allocation is historical.  Time slices in periods that have already been billed can no longer be changed. These time slices can only be displayed. However, you can divide one time slice into two slices and maintain them. Example  Time slice: 01/01/1996 to 12/31/1999 Period already billed: 01/01/1996 to 12/31/1999 The time slice is divided into two time slices: 01/01/96 to 12/31/1996 and 01/01/1997 to 12/31/9999. The unlimited time slice is not in the period billed and therefore can be maintained.  It is also possible to define an allocation without an allocated device in order to store the attributes of the device allocation. For example, measured pressure can be stored in a pressure regulator allocation although the pressure regulators do no exist in the system.  The attributes measured pressure for the pressure regulator allocation or billing factor for transformer allocations are relevant to billing and mandatory for gas meters or meters that do not measure directly.   Device allocations can be defined at the register or device level of the controlled device. Metering devices (meaning devices with registers) are allocated at the register level. Devices without registers are always allocated at the device level. The controlling device is always entirely allocated to the controlled device. It is possible that a controlling device (such as a ripple control receiver) has been replaced during the time slice of the device allocation. In this case, the device that is valid at the beginning of the time slice is displayed. You must also set the TM indicator (device not valid for the entire period). You can double-click on this indicator to display the valid devices with corresponding validity periods. You can also display these devices by selecting the appropriate line and choosing Extras  History   It is also possible to define your own allocation types. To do this, you add new entries to the table of allocation types. These allocations are not relevant to billing, however. 
Business roles: Billing Specialist (Utilities)| Meter Data Specialist (Utilities)
Meter Data Specialist (Utilities) : 
Is responsible for providing accurate and complete utilities measurement data (register readings, load profiles) in time. Works in the back-office. Organizes and supervises the acquisition of measurement data.

Billing Specialist (Utilities) : 
Is responsible for providing accurate and complete utilities bills for the end customers in time. Works in the back-office. Supervises the billing, invoicing and bill print processes.
Display Device Allocation
Application component: Device Installation
App type: SAP GUI
Description:   This function enables you to allocate devices to one another and store additional attributes.  A distinction is made between controlled devices, such as meters, and controlling devices, such as a transformer switched in series. 
Key features:   Device allocation is historical.  Time slices in periods that have already been billed can no longer be changed. These time slices can only be displayed. However, you can divide one time slice into two slices and maintain them. Example  Time slice: 01/01/1996 to 12/31/1999 Period already billed: 01/01/1996 to 12/31/1999 The time slice is divided into two time slices: 01/01/96 to 12/31/1996 and 01/01/1997 to 12/31/9999. The unlimited time slice is not in the period billed and therefore can be maintained.  It is also possible to define an allocation without an allocated device in order to store the attributes of the device allocation. For example, measured pressure can be stored in a pressure regulator allocation although the pressure regulators do no exist in the system.  The attributes measured pressure for the pressure regulator allocation or billing factor for transformer allocations are relevant to billing and mandatory for gas meters or meters that do not measure directly.   Device allocations can be defined at the register or device level of the controlled device. Metering devices (meaning devices with registers) are allocated at the register level. Devices without registers are always allocated at the device level. The controlling device is always entirely allocated to the controlled device. It is possible that a controlling device (such as a ripple control receiver) has been replaced during the time slice of the device allocation. In this case, the device that is valid at the beginning of the time slice is displayed. You must also set the TM indicator (device not valid for the entire period). You can double-click on this indicator to display the valid devices with corresponding validity periods. You can also display these devices by selecting the appropriate line and choosing Extras  History   It is also possible to define your own allocation types. To do this, you add new entries to the table of allocation types. These allocations are not relevant to billing, however.
Create Register Relationships
Application component: Device Installation
App type: SAP GUI
Description:  This function allows you to map the relationship between two or more registers. You can find the transactions for register relationships in the Utilities Industry menu under Device Management  Installation  Installation Structure  Register Relationships.
Change Register Relationships
Application component: Device Installation
App type: SAP GUI
Description:  This function allows you to map the relationship between two or more registers. You can find the transactions for register relationships in the Utilities Industry menu under Device Management  Installation  Installation Structure  Register Relationships.
Display Register Relationships
Application component: Device Installation
App type: SAP GUI
Description:  This function allows you to map the relationship between two or more registers. You can find the transactions for register relationships in the Utilities Industry menu under Device Management  Installation  Installation Structure  Register Relationships.
Create Sample Lot
Application component: Device Management
App type: SAP GUI
Description:   You can use an official lot in order to certify several devices via the sampling procedure.  You can use an internal lot in order to carry out company inspections on devices that by law are not subject to certification or inspection.
Change Sample Lot
Application component: Device Management
App type: SAP GUI
Description:   You can use an official lot in order to certify several devices via the sampling procedure.  You can use an internal lot in order to carry out company inspections on devices that by law are not subject to certification or inspection.
Display Sample Lot
Application component: Device Management
App type: SAP GUI
Description:   You can use an official lot in order to certify several devices via the sampling procedure.  You can use an internal lot in order to carry out company inspections on devices that by law are not subject to certification or inspection.
Compile Sample Lot
Application component: Device Management
App type: SAP GUI
Description:   This function enables you to allocate devices to a lot or remove devices from a lot.  
Key features:   You use selection criteria to allocate devices to an existing lot. You can either specify each device separately, or you can use the device category and other selection criteria to determine multiple devices and allocate them to the lot.  You can also remove single devices or devices of a specific device category from the lot.
Determine Lot Devices
Application component: Device Management
App type: SAP GUI
Description:   This function determines all devices that are allocated to a lot and writes these devices to an internal table. This internal table is used as a starting point for drawing sample devices.  
Key features:   With the appropriate customizing settings you can include warehouse devices when determining lot devices. This is controlled via an indicator on the initial screen of the transaction.
Create Periodic Replacement List
Application component: Device Management
App type: SAP GUI
Description:   This function enables you to:  Create periodic replacement lists Extend periodic replacement lists Add devices with an advanced replacement year to periodic replacement lists  When a periodic replacement list is created, all installed devices are included whose periodic replacement year is before or the same as the specified periodic replacement year. The periodic replacement year is then obtained by adding the last certification year (in the device master record) and the calibration validity (in the device category master record). If a device is allocated to an official lot, the periodic replacement year of that device is specified when the lot is terminated. If a device has been allocated to an internal lot, this is not taken into account during determination of the periodic replacement year for that device. SAP recommends that you create periodic replacement lists in background jobs. You can select this option before you create a list. 
Key features:   When you create a periodic replacement list, the list for the current year is always cleaned up first. This means that all devices are removed from the list that have not yet been removed or for which no orders or notifications have been created yet. Subsequently, all devices with the periodic replacement year in question are included in the list. If desired, you can create the list only for devices of a specific division category.  When you extend the list for a year, you use additional specifications (see below). You can combine these two steps if you make additional specifications when you create the list. You can also specify the following: Device category with/without replacement year and/or last certification year Company area (processor ID) Lot  Within one line, these specifications restrict one another (logical AND). Several lines have the effect of an extension (logical OR). If you add devices to the list that have an advanced replacement year, you cannot use additional specifications. Adding such devices to the list is only a manual extension. Before you create or extend a list, a saved variant must exist. A variant contains all parameters for executing the function. If devices belong to an official lot and the lot is terminated before the replacement list is created, then the devices of that lot are automatically included in the list. However, if the lot is terminated after the periodic replacement list is created and the lot devices for this year are to be included in the list, then you must add those devices after the list has been created. A statistics or error log is created when a list is created or extended. You can also display these logs after executing Transaction SLG1 (Object: IUEG, Sub-Object REP_STAT or REP_ERROR).
Create Certification
Application component: Device Management
App type: SAP GUI
Description:   This component manages individual certifications of devices. If a device functions in accordance with legally prescribed standards, it is certified for a certain period of time and can be installed (or reinstalled).
Create Winding Group
Application component: Device Management
App type: SAP GUI
Description: This component groups together windings that apply to one device or device category. Windings define the transformation ratio (of transformers, for example) and are divided into primary and secondary windings. A winding contains at least one primary and one secondary winding.When defining a device category from the basic device category transformer is assigned to the device type for a winding group. For more information, seeDevice Category.Define a text field to specify winding demand in Customizing under Define Winding Demand.You can switch off the checks within a winding group for the maximum and minimum voltage and current data in Customizing under Technology  Winding Group  Define System Parameters for Winding Groups.
Change Winding Group
Application component: Device Management
App type: SAP GUI
Description: This component groups together windings that apply to one device or device category. Windings define the transformation ratio (of transformers, for example) and are divided into primary and secondary windings. A winding contains at least one primary and one secondary winding.When defining a device category from the basic device category transformer is assigned to the device type for a winding group. For more information, seeDevice Category.Define a text field to specify winding demand in Customizing under Define Winding Demand.You can switch off the checks within a winding group for the maximum and minimum voltage and current data in Customizing under Technology  Winding Group  Define System Parameters for Winding Groups.
Display Winding Group
Application component: Device Management
App type: SAP GUI
Description: This component groups together windings that apply to one device or device category. Windings define the transformation ratio (of transformers, for example) and are divided into primary and secondary windings. A winding contains at least one primary and one secondary winding.When defining a device category from the basic device category transformer is assigned to the device type for a winding group. For more information, seeDevice Category.Define a text field to specify winding demand in Customizing under Define Winding Demand.You can switch off the checks within a winding group for the maximum and minimum voltage and current data in Customizing under Technology  Winding Group  Define System Parameters for Winding Groups.
Compliance Requirement Pattern: Content Base Requlation
Application component: Product Compliance - Dangerous Goods
App type: Web Dynpro
Business roles: Dangerous Goods Specialist - Product Compliance| Product Stewardship Specialist - Product Compliance
Master Data Specialist - Product Compliance : 
Requests compliance information from customers and suppliers.

Dangerous Goods Specialist - Product Compliance : 
Monitors the activities of the organization that involve dangerous goods, prepares accident reports, and the annual dangerous goods report.

Product Stewardship Specialist - Product Compliance : 
Manages the day-to-day operations that help ensure compliance for chemical products. Maintains chemical compliance data and performs checks to ensure correctness and completeness.