Start of Content Area

Background documentation Configuration of the Web Interface  Locate the document in its SAP Library structure

Parameters for the Extended Configuration Management (XCM) Configuration File

Parameters for controlling the Web interface are defined in the XCM configuration file. The following table provides a description of the individual parameters.

Parameter

Use

Function

startFilter

(default value: 8)

 

Meter reading entry

Move-in / move-out / move-in/out

 

During the meter reading entry, the system displays a table with all meter readings. As this table can be very large, you can use the following filter criteria:

Premise address

- Division

Entries with/without meter reading order

The parameter specifies the number of entries required before the filter is to appear.

countrySupplyArea

(default value: DE)

 

Move-in/move-out

If the system could not identify the premise, into which the customer is to move – for example, in the case of a customer typing error – the system checks whether the premise address is located in the service territory of the company. This parameter is used to define the country in which the service territory is located.

daysPast

(default value: 30)

 

Move-in / move-out / move-in/out

To avoid senseless data and typing errors, you can specify here how many days a move-in / move-out / move-in/out can lie before the current date.

daysFuture

(default value: 30)

Move-in / move-out / move-in/out

To avoid senseless data and typing errors, you can specify here how many days a move-in / move-out / move-in/out can lie after the current date.

dummyUserMoveIn

(default value: ESERVICE)

 

Move-in

To access the Internet services, the customer must logon using a user and password. When a new customer reports a move-in, he/she must not apply for a user beforehand, but is logged on using a dummy user. Only the move-in service is then available to the customer. The customer must logon using the page jsp/isuExtensions/ direct_logon_html.jsp, on which the user name and the password of the dummy user must also be defined. After the customer has logged on, the system compares the user name with the parameter value. If the values match, the system hides further menu options. The dummy user cannot refer to more than one business partner and/or contract account in SAP IS-U.

parkedDocumentVariant

(default value: 0001)

Move-in / move-out / move-in/out

The system creates a parked document for the services move-in, move-out, and move-in/out. Different company-specific values are defined in the parking variant. You use this parameter to maintain the name of the parking variant (IS-U table TECAMIOVAR).

tokenAutomaticDebit

(default value: E)

 

Move-in / move-out / move-in/out

The customer has a choice of three payment variants for the services move-in, move-out, and move-in/out. One of these options is automatic debit. At this point, you must define the value for the payment by automatic debit. This value was set in the implementation guide for the SAP IS-U system (IS-U table TFK042Z, transaction FQP1).

tokenCheck

(default value: F)

 

Move-in / move-out / move-in/out

The customer has a choice of three payment variants for the services move-in, move-out, and move-in/out. One of these options is payment by check. At this point, you define the value for the payment by check. This value was set in the implementation guide for the IS-U system (IS-U table TFK042Z, transaction FQP1).

tokenBankTransfer

(default value: G)

 

Move-in / move-out / move-in/out

The customer has a choice of three payment variants for the services move-in, move-out, and move-in/out. One of these options is bank transfer. At this point, you must define the value for the payment by automatic debit. This value was set in the implementation guide for the SAP IS-U system (IS-U/CCS table TFK042Z, transaction FQP1).

oneAccount

(default value: X)

 

Move-In/Out

The move-in/out service consists of the services, move-out and move-in. The move-out is processed using the recognized contract account. The contract account is unknown for the move-in. If you set the parameter ‘X’, the system uses the move-out contract account for the move-in. This means that there is only one payment method for the move-in and move-out. If you do not set this parameter, the system creates a new contract account, or uses a BAdI in the BD_MVE_INTERNET_MOVEIN function module to determine a contract account. This means that there is one payment method for the move-in and one for the move-out.

meterreadingFutureMoveIn

(Default value: Blank)

Move-in

Here, you can allow your customers to enter their meter readings when they move-in.

meterreadingFutureMoveOut

(Default value: Blank)

Move-out

Here, you can allow your customers to enter their meter readings when they move-out.

tokenElectricity

(Default value: 1)

Meter reading entry

Define the technical name of the Electricity division here according to the settings in your backend system.

tokenGas

(Default value: 2)

Mete reading entry

Define the technical name of the Gas division here according to the settings in your backend system.

tokenWater

(Default value: 3)

Mete reading entry

Define the technical name of the Water division here according to the settings in your backend system.

Required Entry Fields

Required entry fields are indicated on the SAP Utilty Customer E‑Services input screens by an asterisk (*) at the end of the name. Values must be entered in these data fields. To change normal fields to required entry fields, and vice versa, you must simply change the corresponding entry in the resource files. You can find these in the WEB-INF/lib/com/sap/fin/isu/resources directory.

A field name without a structure name preceding it is generally regarded as a required entry field. Field names with a structure name preceding them are, in contrast, only regarded as required entry fields for the screen in question.

Example

NAME1=Nachname* is, for example, a required entry field. S_OWNER_ADDRESS-NAME1=Nachname specifies that this field is an exception, and is not a required entry field for the input screen that uses the structure S_OWNER_ADDRESS. Which screens use which structures is defined for the respective service in the resource file in the WEBINF/lib/com/sap/fin/isu/resources directory.

Field Sequence

The field sequence can vary depending on the logon language. In Germany, for example, the sequence runs Street, House Number. In the USA, however, the sequence is usually House Number, Street. This is included in the resource files: All keys that end with .order specify a field order (for example, street.order=s12specifies the sequence Street, House Number, House Number Supplement). You can find the meanings of the values, and a more precise description of the services in the resource file, in the WEBINF/lib/com/sap/fin/isu/resources directory.

Inclusion of Additional Fields

If additional fields are to be displayed on an screen, you must enhance the export structure for the corresponding function module, and create a field with the same name in the corresponding JSP file (directory WEB-INF/jsp) and resource file (directory WEB-INF/lib/com/sap/fin/isu/resources).

 

End of Content Area