Meter Replacement Scenario

Key steps in the meter replacement process facilitated by the FSM Connector include:

•  Prefilled Checklist for Meter Replacement: Guides the technician with meter-related data.

•  Meter Removal: The FSM Connector triggers the initiation of the meter removal process in SAP IS-U, updating relevant data, meter readings, and statuses.

•  New Meter Installation: Once the old meter is removed, the FSM Connector facilitates the installation of the new meter, ensuring proper data updates and posting meter readings.

Configuration Steps

1. Configure Posting Framework

2. Create a checklist template

3. Configure generation of prefilled checklist

4. Configure movement type for posting goods issue

1. Configure Posting Framework

Cluster view /PACG/ECM_FRMDEF

In the first level of the cluster the scenario and its description can be created:

Open

In the next level the class can be assigned. The class is a space where different steps (methods) or actions should be defined :

Open

In the lower level, the steps (methods from a class specified before) and their sequence can be defined. Additionally, the optional fields FrmwErrSta and FrmwUsrSta are available. If they are filled with some value, then after completing the step, the service order user status will be updated with the relevant value.

In the next node: company assignment, the scenario can be linked with the applicable company.

In the trigger assignment the template ID and its version are linked with the framework structure along with the set of conditions for processing. The conditions should be based on checklist’s content. If conditions are met, then the actions should be taken.

Framework structure can be created in Scenario builder or in ABAP Dictionary. It should include the fields that are chosen to be mapped to the checklist fields. Please note that /PACG/ECM_FRMWD table serves as a template for structure creation.

The condition definition below means that for a given checklist template id, version and structure the checklist field EQOLD can not be empty. One can also define more sophisticated conditions by providing specific values or ranges of values for a chosen checklist field by using standard options: Sign (Include/Exclude), Options pushbutton (Single value, Greater than, Less than, Range etc), Lower limit and Upper limit.

In the next level: checklist mapping the checklist positions are mapped to the the fields from the defined structure. Similarly to /PACG/ECM_VCLCNZ - New Checklist Mapping Customizing instead of position numbers, specific position names of a checklist are used.

After the checklist is filled with data and submitted and the required conditions are met, the framework is started and defined steps are processed.

Below is the sample data entered in the exchange meter checklist. Note the dismantled and installed meter information as well as their meter readings.

After submitting the checklist, the results can be viewed in the new transaction Posting Framework - Logs Viewer /PACG/ECM_FRMW_LOGS which displays the logs for each processed step for the specific checklist document number, order number and so on. On the resulting ALV there is also an option to manipulate the data by manually setting a step as done.

For the example meter replacement order one can see the general confirmation that processing was successful along with more detailed information about each step.

2. Create a checklist template

The template will serve the following purposes:

• [SAP ECC/S4 → SAP FSM] It will be used to automatically generate a checklist instance for the technician - prefilled with device serial number, register code, the value of the previous meter reading.

• [SAP FSM → SAP ECC/S4] A technician will use the checklist instance to enter new meter serial number and meter reading values for relevant device.

Since the structure (T_MEASURE_PTS_ISU) used for mapping of register data with checklist template fields in prefilled checklist configuration is a table structure, the corresponding fields in a checklist template must be part of a series or a table. The example series ‘Meter Reading’ consists of the following fields:

Open

Configure generation of prefilled checklist

Checklists can be prefilled with register data of the operation's equipment, or if not found, the service order header’s equipment. The technician can use a series of meter reading data to easily post readings of device replacement within a checklist.

Use transaction /PACG/ECM_CL_PREF -Checklist prefilling configuration to customize generation of prefilled checklists. Structure T_MEASURE_PTS_ISU is used to map measuring point data with checklist template fields:

Prerequisites

Apart from the prerequisites described on the following page: /PACG/ECM_CL_PREF - Checklist prefilling configuration | Preconditions, it is crucial that the activity’s operation has equipment assigned (if not found, equipment is searched on the service order header level). Please remember that prefilled checklists will be generated only for activities with a technician assigned.

The checklist template has conditions assigned and is set as active for prefilled checklist generation:

4. Configure movement type for posting goods issue

Use transaction /PACG/ISU_PARAM ISU Add-on parameters to configure plant, storage location and movement type for the posting goods issue of the new meter