Show TOC

 Utilities, Functional Enhancement Due to Customer Feedback

 

Technical Data

Technical Name of Business Function

ISU_LOC_CI_4A

Type of Business Function

Industry Business Function

Available As Of

SAP Enhancement Package 4 SP13 for SAP ERP 6.0

Technical Usage

Utilities/Waste&Recycling/Telco

Application Component

SAP Utilities (IS-UT)

Directly Dependent Business Function Requiring Activation in Addition

Not relevant

This business function provides new functions that have been created as part of the Customer Connect initiative. As part of this initiative, numerous SAP for Utilities customers have submitted improvement requests, which have been implemented by SAP.

Using this business function offers you the following improvements:

Reallocate Point of Delivery or Installation to New Premise

Technical master data may be allocated incorrectly, for example if an installation is allocated to the wrong premise. This requires a large quantity of data and references to be corrected according to the subsequent processes to be executed for this installation. You can use the transaction Reallocate Connection Object: Initial Access (ES64) to reallocate the point of delivery or installation to another premise. All relevant database tables are updated.

For more information, see the application help Reallocate Point of Delivery/Installation to the New Premise.

Device Modification in Future

Time-to-market is becoming increasingly important for utilities companies. This in turn requires processes in the IS-U system to be more flexible. You can use the Device Modification in Future function provided with this business function to modify IS-U devices including those for periods in the future. This was only previously possible for device information records.

This function is controlled by the Customizing parameter EG42DEVFM under Start of the navigation path Industry Component Utilities Industry Next navigation step Device Management Next navigation step Installation Next navigation step Basic Settings Next navigation step Define System Parameter for Installation/Removal/Replacement End of the navigation path.

Change Logging for EDM Objects

Settlement-relevant master data is sensitive data. Therefore, it is important to be able to track manual changes made to this data.

This business function logs changes for various EDM objects.

  • Change Documents

    Changes to settlement units regarding header data, hierarchy and point of delivery allocation are logged in change documents. You can display them in the transaction Create/Change/Display Settement Units in the menu under Start of the navigation path Extras Next navigation step Change Documents End of the navigation path.

  • Administrative Data

    Creation data (created on/by, changed on/by) and field changes are logged for the following transactions:

    • Settlement Unit

    • Allocation of Point of Delivery to Settlement Unit

    • Allocate Profile to Register

    • Allocate Load Profile to Installation

  • Validate Consumption Factor

    For the validation of manual changes to the consumption factor, as well as for the validation of changes to the consumption factor that are a result of billing, you can use a BAdI implementation for your specific project to have the system issue a warning message when a certain limit is exceeded.

    For more information, see also the system documentation for the class to be implemented in the example implementation CL_ISU_LPASSLIST_UF_VAL.

Text Field for Profile Versions

To store information about profile versions, such as reasons for manual changes to profile values, you can use the editable text field in the version overview in the transaction Change Profile Values(EEDM01).

Additional Authorization for Installation Facts

You can prevent installation facts being edited using an authorization check and the new authorization object for installation facts (E_INSTFACT). This enables you to manage authorizations at operand category level.

The authorization is executed using the Business Add-In Check Authorization for Installation Facts (ISU_INSTLN_FACTS_AUTHORIZATION). By default, the BAdI is inactive. You can activate your own implementation or use the implementation of the example class as a template. For more information, see the BAdI documentation and the example class documentation in the system.

You can use the customer exit EBIA0027 to execute additional checks at operand level.

You can use the value help (F4) in the transactions for the installation, contract and premise to select values in the field Authorization Group. To use the value help, proceed as follows:

  1. Assign basic search helps (such as ISU_BEGRU) to the following collective search helps:

    • ISU_BEGRU_INSTLN

    • ISU_BEGRU_CONTRACT

    • ISU_BEGRU_PREMISE

  2. To provide values for the search help, maintain authorization object groups and authorization objects in Customizing.

  3. Check the entries for the field Authorization Group using the implementation of the following customer exits:

    • EMDI0001 - IS-U: Installation

    • EMDK0001 - IS-U: Contract

    • EMDP0001 - IS-U: Premise

Upload Price Data to the SAP IS-U System

In utility companies, pricing information is often managed in Excel files, and then transferred manually to the SAP IS-U system. Now it is possible to upload pricing data from an Excel file directly into the IS-U system from where you can subsequently process this data. The data structure used here has been kept simple on purpose.

For more information, see the application help Upload Pricing Data.