Managing the Energy Data Management Profiles

Profile values can be imported using two procedures:

• BAPIs (Business Application Programming Interface): Importing measurement data via a synchronous communication path (for example, a function call such as RFC).
• IDocs (Intermediate Document): Importing data via an asynchronous communication path (for example, electronic data exchange).

During profile value import, registers are identified by the following objects:

• Point of delivery ID

  For example, DE2367093

• Register code

  For example, EDM_TEST 1

• Role category of a profile allocation

  For example, Measurement ( = 01)

• Role of a profile allocation

  For example, Consumption measured ( = 0001)

You can use the File Upload app (via Point of Delivery) or File Upload via Profile app to import the profile data.

The following file types are available for profile value import:

• ASC: ASCII
• BIN: Binary
• DBF: DBASE format
• IBM: ASCII with IBM code page conversion (DOS)
• WK1: Spreadsheet format
• DAT: ASCII Data table with column tab

• ISUPROFILE. Upload:

  You can use this BAPI to import profile values for a profile.

• ISUPROFILE. Import:
  • You can also use this BAPI to import profile values.

  • The profile to be filled is determined by means of the point of delivery ID, the register code, the role, and the role category.

• ISUPROFILE.Get:

  You can export a profile's values from the Energy Data Repository using this BAPI.

• ISUPROFILE.GetfromPoD:

  You can also export profile values from the Energy Data Repository using this BAPI. Here, though, you can specify additional selection categories such as point of delivery, point of delivery ID, role, and role category.

Once the import process is complete, you can view the import status in the Profile Value Monitor app. A message informs the user whether or not the import was successful.

Information on the profile value import includes data about errors, such as corrected profile values, data about date and time, import data, for example, IDoc number and external reference, profile information, such as the Point of Delivery ID, and data about replacement value.

The following image shows examples of the data recorded:

Consistency checks check the profile values as they are imported into the system. Examples are:

• Missing values
• Out of range values
• Overlapping values

• Consistency checks are allocated to consistency check groups.
• Consistency check groups are allocated in the profile header.
• Profiles with missing values or periods can be imported if:
  • The missing values have the value "0" or
  • When a replacement value procedure group is specified in the profile header, the missing values are replaced with replacement values using the corresponding replacement value procedure
• The missing values can be imported at a later date. The "0" values or the replacement values are overwritten with the actual values.

The example above shows three consistency check groups to which the following consistency checks are allocated:

• Consistency check group 1: Performs the following check during profile value import:

  Overlapping values

• Consistency check group 2: Performs the following two checks during profile value import:

  Missing values and out of range values

• Consistency check group 3: Performs the following three checks during profile value import:

  Overlapping values, missing values, and out of range values

The Customizing path is as follows:

During the replacement value procedure, profile values are created to replace missing values.

• The replacement value procedure is used for the following reasons:
  • Profile values do not exist for a certain time period (for example, due to a device breaking down or communication error).
  • To perform billing simulations for future time periods or for the creation of forecast schedules
• First of all, the replacement value procedures are defined in Customizing. These replacement value procedure are then allocated to replacement value procedure groups. Replacement value procedure groups are allocated to a profile (in the profile header). This defines the replacement value procedures that are used to generate values for the allocated profile.
• The replacement value group can be changed in the profile header after the profile header has been created.
• Only the intervals with missing values are replaced. For example, if some intervals have values and others do not, the existing values are not overwritten.
• It is only possible to generate replacement values for values with the status Value does not exist. (If the value is 0.00 but has a valid status, the value is NOT replaced.)
• It is possible to delete values with the status Manually changed/extrapolated/interpolated using the Maintaining Profile Values app so that replacement values can be regenerated for these intervals.

Replacement value procedures are defined using the following input parameters:

• Reference period
• Reference profile
• Profile role
• Historical values: A time period is defined and historical values are taken from this period. These values can either come from a profile that requires values or from another profile (reference profile).

Error codes are defined for each replacement value procedure. These define all possible errors that can result from the procedures (for example, no historical data in the period required).

These replacement value procedures are allocated to replacement value procedure groups.

Replacement values are generated in the following scenarios:

Automatic interpolation during profile value import: You can activate the automatic interpolation of profile values during profile import. The procedures can also be activated from the Monitor Import of Profile Values screen (Menu: Edit -> Generate Replacement Values). Alternatively, use the button ....

• Manual replacement of missing values using the profile values transaction
• Interpolation and extrapolation can be executed using Execute mass changes in the profile values transaction
• Automatic extrapolation using billing simulation
• In the context of IS-U-Billing, it is possible for interval customers to execute a billing simulation based on the extrapolated profile values.
• Replacement values can only be generated for the profile categories Quantity or Demand.

If the interpolation of missing profile values was executed automatically after the import of profile values, the event ReplacementValuesRequired for BOR object ISUPROFILE is issued. You use the replacement value event to define your own replacement value workflows, so that you can inform the person responsible that the interpolated profile values have to be checked or released, for example.

The following image shows examples of the Replacement Value procedure:

There are eight replacement value procedures predefined by SAP. For profiles with only small amounts of data missing, values can be determined from the immediate environment (this means, the values before and after the missing values).

• Linear replacement procedure: The difference between the last known value before the missing values, and the first known value after the missing values is distributed across the total number of missing intervals.
• Maximum value replacement procedure: The missing values are replaced with the maximum value from the last known value before the missing values and the first known value after the missing values.
• Minimum value replacement procedure: The missing values are replaced with the minimum value from the last known value before the missing values and the first known value after the missing values.

CONTROL: Copy values from the profile of the control meter

Multiple replacement value procedures can be allocated to a replacement value procedure group.

The replacement value procedures in a replacement value procedure group are prioritized, whereby the replacement value procedure with the highest priority is called first. If this replacement value procedure cannot replace the missing values (for example, due to missing environment data or data missing from a control meter), the replacement value procedure with the next highest priority is called (1 = highest priority, 9 = lowest priority).

The replacement value procedures in a replacement value procedure group are valid for a certain number of missing values.

If the number of values to be replaced lies between 1 and 3, for example, the values are replaced using the appropriate procedure.

The following parameters define replacement value procedures:

• Replacement value procedure (mandatory)
• Function module for replacement value creation: Replacement value procedures are implemented as function modules. Each replacement value procedure is allocated to a function module that creates replacement values. All function modules that you enter here must have the same interface as function module ISU_EDM_REP_METH_LINEAR.
• Function module for determination of reference period: This function module is called during the replacement value procedure and determines reference periods for the profile such as seasons, day groups, and TOU groups. The function module provided by the customer allocates the profile from the RTP interface to the replacement procedure. An interface is defined in the sample function module: ISU_EDM_REF_TIME_SAMPLE.
• Reference profile: This is a reference profile for the replacement value procedure.
• Profile allocation role of the reference profile: This is a profile role for the replacement value procedure. You can allocate reference profiles indirectly using roles. During the replacement value procedure, the profile that is allocated to the interval meter with the specified role is transferred to the procedure.

• Start of reference period: If the procedure is based on a historical profile, the values used come from the start of this reference period (yesterday, last week, last month, and so on).
• Duration of reference period: Self-explanatory
• Reference period corresponds to replacement period: If you select this field, the duration of the reference period corresponds to the duration of the replacement period. If you select this field, entries in the Duration of Reference Period field do not take effect.
• Replacement value procedure valid for consumption/demand profiles: Every procedure must be valid for either consumption profiles or demand profiles or both.
• Procedure valid for interpolation/extrapolation of profile values: Every procedure must be valid for interpolation or extrapolation or both.
• Manual entries required for replacement value procedure: If you select this field, this replacement value procedure cannot be used for profile value import or billing simulation.
• Description of replacement value procedure: Self-explanatory
• Error codes for replacement value procedure: Defines the possible types of error that can occur when replacement values are created.

Each replacement value procedure group contains interpolation and/or extrapolation processes. The following parameters define replacement value procedures:

• Definition of replacement value procedure group
  • Replacement value procedure group after profile value import: The procedure group is automatically called if the system determines that values are missing after a profile value import.
  • Replacement value procedure group valid for consumption/demand profiles: Every procedure group must be valid for either consumption profiles or demand profiles or both.
  • Description of replacement value procedure group
• Allocation of replacement value procedure to group
  • Replacement value process: Interpolation or extrapolation of profile values
  • Priority of replacement value procedure (RVP) in RVP group: This field defines the priority of a replacement value procedure in a replacement value procedure group. The replacement value procedure with the highest priority is always called first (1 = highest priority, 9 = lowest priority).
  • Minimum/maximum number of values: Minimum/maximum number of values that can be replaced using values from this procedure.
  • Replacement value procedure

Error codes for replacement value procedures are defined by process

• Description of Error Code for Replacement Value Procedure: This field describes the type of error that may occur during replacement value creation.
• Actions for Error Codes for Replacement Value Procedures

  Exit processing; do not save values

  Exit Processing, save values (This means, save all values - even if only half of the values were generated.)

  Continue processing, delete values

  Continue processing, use values

• The Continue processing actions should not be used if there are no more procedures. This is because the last known values are always saved and these could potentially all be zero.

Synthetic profiles (standard load profiles) are used in some energy markets if customer consumption is not determined using an interval reading.

In Germany, for example, the German Electricity Association (VDEW) has a number of different customer groups. In the USA, customers are grouped together based on their consumption patterns. In order to do this, interval meters are installed at a representative customer from each group for a specific period of time. Overall consumption patterns are then calculated using these sample measurements.

A Synthetic Profile is a profile that contains values generated on the basis of predefined periods (defined by day and season groups) and corresponding day and annual profiles. It is used when no interval readings are available to classify the consumption patterns of groups of customers. Customers groups (those customers with similar consumption patterns) are assigned the same synthetic profile.

Two further characteristics of a synthetic profile that will be discussed in this unit are:

• Dynamic modification factors
• Usage factors

Synthetic profiles can be made up of hierarchy structures. Components within this hierarchy are:

• Season groups
• Day groups
• Profiles

Season, day, and time-of-use groups can be adjusted in Customizing for SAP Utilities under Energy Data Management→Basic Settings

You must make day, season, and TOU settings before you can generate synthetic profiles.

• Season types describe a recurring period within a year. Season periods are allocated to a season type. In the example above, the following season types have been customized:
  • Season type Summer (0001) describes the season period from April 1st to September 30th.
  • Season type Winter (0002) describes the season period from October 1st to Decemeber 31st. (consecutive number 1) and the period from January 1st to March 31st. (consecutive number 2).
• Season groups describe the division of the year into season types.
  • The season periods allocated to the season types in the season group must total one year (January 1st to December 31st) and cannot overlap.
  • For example, to divide a year into summer and winter, define a season group that contains the season types summer (to which you allocate the season period April 1st to September 30th)and winter (to which you allocate the season periods October 1st to December 31st and January 1st to March 31st).

Day types define days based on the factory calendar.

In the Factory Calendar, Monday through Friday are defined as working days and Saturday, Sunday, and public holidays are defined as non-working or weekend days. A factory calendar is based on a public holiday calendar.

In the example above, the week is divided into weekdays and weekend days and the following day types are defined:

• Weekday with reference to the workdays in factory calendar 01, this means Monday through Friday.
• Weekend with reference to the public holidays in factory calendar 01, which means Saturday, Sunday, and public holidays.
• Other day types can also be customized.

Day groups contain different day types.

• Day group 1 includes weekdays (day type 0001) and weekends (day type 0002).
• Day group 2 includes all days (day type 0003).

You can define exceptions for day types so that regional or company-specific non-working days can be taken into account.

The day type exceptions are also allocated to day groups and can be selected for synthetic profiles or in the RTP interface at installation level.

Time of Use Groups consist of Time of Use Types.

Time of Use Types are defined and assigned to a Time of Use Group. For example:

• The TOU period from 08:00:00 to 17:59:59 is allocated to TOU type 0001 (on-peak rate period)
• TOU periods from 00:00:00 to 07:59:59 and 18:00:00 to 23:59:59 are allocated to TOU type 0002 (off-peak rate period)

In order to set up the TOU Group, the Time of Use Types On-Peak and Off-Peak are allocated to a TOU Group. In the above example, TOU Group On-Off Peak consists of on- and off-peak time periods as defined in the TOU type.

Synthetic profile values are determined using reference measurements or statistical methods and are saved as a day profile in the Energy Data Repository.

Based on the allocation of season, day and TOU groups, a synthetic profile structure is generated.

During the generation of the synthetic profile, the day profiles (standard load profiles) are determined according to the hierarchy. The profile values are then transferred to the synthetic profile according to the hierarchy settings.

As an alternative to day profiles, you can also allocate year or elementary profiles to a synthetic profile. Once a profile has been allocated to a synthetic profile and the synthetic profile has been generated, the day profile, year profile, or elementary profile can no longer be changed manually or by means of a mass change.

However, if an elementary profile is allocated to the synthetic profile, and the elementary profile is provided profile values on a regular basis from an automated meter reading system, the synthetic profile is generated automatically.

Dynamic Modification Factors are used to modify a customer or customer group's synthetic profile to represent the temperature impacts throughout the year. This process is known as dynamic modification and guarantees a typically stable load shape.

Dynamic modification factors are generated in EDM.

You can find this function in Customizing under SAP Fiori app: Home page→User Profile icon→App Finder→SAP Menu→Search in SAP Menu→Customizing – Execute Project→SAP Reference IMG→SAP Utilities→Tools→System Modifications→User-Defined Enhancements for Energy Data Management→Dynamic Modification Function for Synthetic Profiles→Define Functions for Calculating Dynamic Modification Factors.

Synthetic profile values can be normed in relation to a given consumption amount, or a fixed reference value, for a given time period of time. In this way a total consumption is used to create a synthetic profile based on the day profiles attached to it.

Normalization is possible for one year or one month. You can norm a synthetic profile for a year, for example, where the sum of the values is 1000 kWh (reference value) over the period.

Synthetic profiles are allocated to the installation using profile roles.

Multiple synthetic profiles can be allocated to one installation. For example, synthetic profiles can be used for both billing and settlement.

The usage factor represents the relationship between customer consumption and normed consumption values from the synthetic load profile.

In the example above, the synthetic profile is normed at 1000 kWh. The actual consumption of the customer is 900 kWh. The usage factor is automatically determined by dividing the customer consumption by the normed value of the synthetic profile:

Usage factor = 900 kWh / 1000 kWh = 0.9

Usage factor is updated:

Usage factors are automatically calculated and updated by means of consumption quantity determination in IS-U Billing. The billing period in which the consumption accumulates is taken into consideration. It is possible to specify for each synthetic profile of the installation whether or not the consumption quantity determination updates the usage factor.

Select the Load Profile button in the Display/Change app.

• Choose Create.
• Enter a start and end validity date for the allocation.
• Enter the load profile to be allocated.
• Enter the usage factor.

You can access the Display/Change Profile Values app for displaying and maintaining profile values in the Energy Data Management

• You can display profile values in table form or as a graphic.

• The changeover to summer-time is taken into account in EDM.

  If profile values are managed in 15-minute intervals, you have the following scenario:

  • In Spring, there are four fewer time intervals on the day of changeover, because 03:00 directly follows 01:45 (therefore, the time intervals 02:00 to 02:45 are missing).
  • In Autumn, there are four more time intervals on the day of changeover. This is because there are two intervals for 02:00, 02:15, 02:30, and 02:45.
• The changeover to other time zones is also taken into account in EDM.The database stores all values in Universal Time Coordinated (UTC). When the local system time is set to Greenwich Mean Time (GMT), for example, the system displays the UTC time + 1 hour to show the GMT time.
• When you display the profile values in a graphic, there are numerous formatting options. Right-click the mouse on the graphic to access the different diagram options.
• In the Change Profile Values app, you can change values in one of two ways:
  • Single value change
  • Mass change

  In this example, the profile value on 01.01.2005 was changed manually at 07:00:00 from 12.04 to 15.00. As a result, the status of the profile value has changed. The new status specifies that the values was changed manually.

  As a result, the status of the profile value has changed. The new status specifies that the values was changed manually.

  
• In the Carry Out Mass Change transaction, you can change several profile values at once by making the following settings:
  • To be executed:
    • Add, subtract, multiply, divide, replace
    • Delete values, protect values, undo value protect, lock values, release values, interpolate values, extrapolate values
  • With value: Enter the value here that must be used to carry out the mathematical operation (for example, add value x to the previous profile values or multiply the previous profile values by value x).
  • To values from and to: Here, you enter the period (date and time) for which the profile values are to be changed.

  In the following image, a mass change took place for the profile values on January 1st 2005 between 00:00:00: and 10:00:00, in which the value 10 was added to each of the original profile values. As a result, the status of the profile values has also changed. The new status specifies that the values have been manually changed

• 
• You can define how the status of profile values is displayed in tabular and graphical form. Make the settings in Customizing for Energy Data Management under SAP Fiori appHome Page→User Profile icon→App Finder→SAP Menu→Search in SAP Menu→Customizing - Execute Project→SAP Reference IMG→SAP Utilities→Energy Data Management→Profile Management→Display Function→Define System Status Display for Profile Values.
• You define the status display using the following parameters:
  • Status: ID of the status predefined by SAP
  • Status symbol for tabular display: Here you define which symbol is used to display the status of a profile value for the tabular display. You can use the input help function to select a symbol, or you can define your own.
  • Priority of status for profiles displayed as tables and graphics: Here you define which status is displayed when a profile value has more than one status. You can use the input help function to find out the permissible value range for the priority allocation (1 = highest priority, 99 = lowest priority).
  • Color of status for graphical profile display: Here you define the color in which the status of a profile value is displayed for the graphical profile display. You can use the input help function to find out the color numbers of the red, green, blue values (RGB values). You can use the input help function to find out the permissible value range for the color number allocation.
• You can define reasons for creating profile versions.

  To do this, you must make the settings in Customizing for Energy Data Management under SAP Fiori app:

  Home page→User Profile icon→App Finder→SAP Menu→Search in SAP Menu→Customizing - Execute Project→SAP Reference IMG→SAP Utilities→Energy Data Management→Profile Management→Profile Versions→Define Creation Reason for Profile Versions.
• You can also define the creation of a version based on the profile type. You can define, for example, that if the values of a Historical profile type are changed, then a version is always created, and if the values of a Forecast profile type are changed, then a version is never created.

  You make these settings in Customizing for Energy Data Management under SAP Fiori app: Home page→User Profile icon→App Finder→SAP Menu→Search in SAP Menu→Customizing - Execute Project→SAP Reference IMG→SAP Utilities→Energy Data Management→Profile Management→Profile Versions→Define Creation of Profile Version

  These settings are only applied when you change profile values manually using the Change Profile Values app.

  
• If versions of profile values exist, you can display them using the Display/Change Profile Values app. In doing so, you can display several versions in parallel. You can select or hide versions.

Formula profiles contain values that were determined on the basis of a calculation rule.

• The calculation rule is mapped in a formula.
• You can use the formula profiles to map constant dependencies for profiles on a long-term basis.

Formula profiles, like all other profiles, are created using the Create Profile Header app. You must choose the Formula profile type in the profile header. You can then enter the appropriate details that are needed for formula profiles.

A formula is a calculation rule that converts the different input parameters (profile values) into output parameters (formula profile values), according to a mathematical algorithm.

Formulas:

• form the basis of the profile calculation, in which the mathematical dependencies are mapped. Are implemented as function modules and allocated in the profile header.
• have input and output parameters, the amount and category of which are defined in the formula definition.
• are delivered by SAP and can be adjusted in Customizing.
• are used in the interface for billing.

You can create your own formulas and write the documentation for them. In Customizing, you can define formulas in addition to those predefined by SAP:

Parameter definitions:

• Parameter number: Defines the number of input and output parameters in the formula.
• Parameter type: Input or Output Parameters
• Parameter ID: Description of the formula parameter
• Profile value category: Classifies values that you manage in the profile.
• ID Formula variable: After you allocate a variable, you have the option to determine variable values from the IS-U environment and to use these in the formula profile calculation.

• Example Formula: LIMIT01
• Input parameters:
  • I01: Measured load profile: Quantity
  • I02: First baseline value: Quantity
  • I03: Second baseline value: Quantity
• Output parameters:
  • 001: Portion below first baseline: Quantity
  • 002: Portion above first baseline: Quantity
  • 003: Portion above second baseline: Quantity
  • 004: Demand above baseline: Demand
• Function module:

  ISU_EDM_FORMULA_0004

• Formula description: Value determination above and below a demand baseline.

The following prerequisites apply for the use of different interval lengths of input and output parameters in the formula allocation:

• All output parameters must have the same interval length
• Interval lengths must be equidistant.
• Parameter "Number of Influential Intervals" for input and output parameters must be equal to zero.
• Interval lengths for input and output parameters must be an exact multiple of each other.

If you use day value profiles, the following prerequisites also apply:

• Input and output parameters permit only the combination of the interval length types, DAY and MINUTES.
• If you use more than one day value profile in the formula allocation, the day offset must be the same in all input and output parameters of the type Day Value Profile.
• If you use at least two day value profiles in the formula allocation, the time zone must be the same in all input and output parameters of the type Day Value Profile.

The four most important elements of the formula profile are:

• Formula
• Status group
• Input parameter
• Output parameter

Profiles are allocated to the input and output parameters within the formula profile.

When you create a formula profile using the Create Profile Header app, you must allocate the status group. Status groups define the status of the input parameters when converted into output parameters.

Within the status group, the status and priority determine which business process (action) to use. Once the status has been determined - with the highest priority for the output parameters of a formula - the action allocated to this status is determined and executed.

The meaning of the individual status group elements:

Status refers to the status of the input parameter (for example, no value, value is valid, value is estimated, and so on).

External status of a measured value: Status provided by an external system (AMR, for example). The MSCONS status (46=supplied quantity, 99=estimated quantity, and so on) could also be interpreted as an external status.

• Internal status of a measured value: Status with which a measured value is maintained in the EDM system
• Business process: The SAP system contains central table of business processes that are valid for all applications and can be used by all applications. These business processes are maintained by SAP and cannot be changed.
• Information on user statuses: You should only define a user status if the number of system statuses or the level of detail of the system statuses is not sufficient, or if you want to add more information to the profile values.

You make enhancements in SAP Basis Customizing using transactions BS12, BS32, and BS22.

In the example above, the formula profile is allocated to the IMPORT status group. The status groups are set up in Customizing.

The following tables shows the IMPORT status group contains the following statuses, priorities, and actions:

Because the status ‚Value is Valid, has the highest priority, the action‚Import Valid Value, is performed.

In this Customizing activity, you define and prioritize statuses and actions and arrange them into status groups. Status groups are used in profile calculation. When the status is determined for the result value of a formula, the action with the highest priority of all input parameters is determined.

Customizing:

• Status group description
• Status for status group
  • Status: Key that informs you of the current status of an object
  • Status priority: Defines which status of a status group is determined for the result value of a formula
  • Action: Defines which business action is to be executed on the basis of the priority and status

For each profile allocated to the input and output parameters in the formula, specify the following information:

• No calculation: If you select this field, the formula allocation is not calculated, although calculation-triggering events (such as changed profile values) have taken place.
• No status: If you select this field, the statuses of this input parameter are not taken into account for status determination for the values of the output profile (this means the formula profile).
• Consecutive number
• Profile number
• Validity period (from-to) of parameter allocation

When a formula has multiple output parameters, each formula profile must be defined individually for the corresponding output parameter. This means that a separate profile header is created for each output parameter.

A formula from the same category can exist more than once in the system. The number of the formula allocation is used to differentiate between the individual formulas.

When you create a formula profile header, a formula allocation number is automatically generated. When there are multiple output parameters defined in the formula, you must create a formula profile for each output parameter.

You can use the input help (F4) function for formula allocation to display all formula allocations that do not yet have output parameters, and have the same interval lengths.

In the above example, formula COPY01 is used to copy one profile into two output profiles:

• Formula COPY01 has an input parameter, to which a consumption profile (load shape) is allocated
• Formula COPY01 has two output parameters
  • Output parameter 1 is allocated a copy of the consumption profile
  • Output parameter 2 is allocated a profile, in which the consumption values have been converted into demand averages

You can create complex formula allocation hierarchies that are taken into account in the formula calculation. The calculation mechanism takes into account lower-level formula allocations in the hierarchy when higher-level allocations are flagged for calculation by the calculation-triggering events.

You can use the Calculation Workbench to present formula allocation hierarchies in a graphic.

The EDM Calculation Workbench app is the gateway to calculating, processing and monitoring formula profile calculations.

Process formula allocation:

• Display formula allocation button: shows the allocation via the Display profile header screen.
• Calculate formula allocation button (synchronous calculation): You can calculate a formula allocation synchronously for a certain period. This also includes all inactive, dependent formula allocations with triggering functions. Enter the formula allocation and choose Calculate Formula Allocation. Selected formula allocation and all inactive formula allocations beneath it in the hierarchy are calculated. This allows the user to make single formula calculations. After the profile has been calculated, in the profile header, Details tab page, you can see the calculated-to date, which shows the last date the formula was calculated.
• Flag for calculation button: generates a calculation trigger
• Hierarchy display button: allows the user to see the formula allocation in a graphic, to better understand the relation between the profiles

The following applies to the Calculation trigger:

• It must be compressed to run the formula calculations.
• Because only completed formula allocations and not individual profiles are calculated, the temporary triggers are compressed at the level of the total formula allocation. Compression of the calculation trigger is a prerequisite for asynchronous calculation of formula allocation.
• The calculation triggers are compressed regarding the formula allocation number, and the from- and to-date.
• Authorized users can delete calculation triggers.
• To calculate formula allocations that are connected as regards time and hierarchy in parallel, without causing locks, the data must first be put into an appropriate form as regards time and hierarchy.
• Unlock Compression: The compression is locked while the calculation trigger is being compressed, so that no other compression can be started at the same time. If errors occur during the process, compression remains to locked. You can, however, remove the lock manually.
• Monitoring calculation triggers: Allows user to monitor the compression.

The following applies to Asynchronous Calculation:

• Asynchronous Calculation is the scheduled calculation of formula profiles. The calculation run considers all formula allocations, for which calculation triggers exist.
• Formula profile calculation analyzes the dependent formula allocations based on the compressed calculation triggers, and starts parallel calculation of the profiles
• It is executed in the background on the specified servers as many times as the number of jobs you have selected per server
• It is performed on several servers and processors per server for optimum system performance
• It is locked for other users while a calculation run is taking place. If a calculation run has not been successfully completed, the lock is not removed from the calculation run. When monitoring the calculation, you can remove the lock and restart the calculation run.

The following applies to Current Calculation Run:

• Display information about the current calculation run
• Header data:

  Calculation run number, Restart number, Creation date, User ID of creator

• Status: Monitor status of the run, or manually change the status of the calculation run
• Parallel processing:

  Interval length or number of intervals, server name, and number of jobs

• For more information on the calculation run, choose Job Overview or Action Log.

You can archive profile values that are no longer required online. Profile values are deleted from the database and written to archive files. You can display these archived values.

You can also archive profiles that belong to the formula profiles category (see unit Formula Profiles). In the process, a check takes place during formula profile calculation to determine whether the calculation period is smaller than or equal to the archive-to date in the profile header of the input and output profiles.

The profile header information remains. The last archiving date is displayed in the profile header (field: Profile Values Archived to).

Customizing:

• Before you start the archiving run for the first time, you must first activate the archive information structures for the individual document types (in this case, the document type is EDM profile values). You make these settings in Customizing for SAP Utilities under Tools→Archiving→Activate Info Structure for Archiving.
• Archive information structure SAP_ISU_PROFV

You want to archive profile values after a certain amount of time (retention period in system). To do this, you define the retention period of profile values in Customizing for SAP Utilities under Tools→Archiving→Define Retention Period for Archiving Objects.

Profile values are analyzed to find out whether or not they can be archived. This analysis is as follows:

1. Profile value selection: First you must restrict the amount of profile values to be archived. To do this, enter the profile values that you want to archive.
2. Determination of the final date for archiving:

   The system determines the final date for archiving from the retention period defined in days in Customizing. This means that only those documents that are older than the retention period in Customizing (documents that have been in the system for longer) can be archived. To determine the final date for archiving profile values, the retention period of archiving object ISU_BILL (billing document header) is also used. You can only archive the profile values if the billing of the associated installation is complete, and the billing document can no longer be reversed.