Functional Specification

FS-DM-Disconnection Processing Variants

and Device Removal on Disconnection

Copyright@2015 Accenture. All rights reserved

Document History
Techincal Specification
Section I: Object General Information
Title (GAP ID):
Short description:
To-Be/ GAP

Date: 05.06.2015
Disconnection Processing Variants and Device Removal on
Disconnection
Automatic removal of devices in case of disconnection for full
disconnection cases.

SAP Module/Team:

DM

SAP- Object

Disconnection \ Reconnection

Functional Contact:

Monis Shakeel

Category:

Complexity Level

Medium

Program type

Enhancement

Status

Completed

Reviewer
Role

Name

SAP ISU Device

Management
Consultant

Monis Shakeel

Copyright@2015 Accenture. All rights reserved

Signature

Date
05.06.2015

Table of Contents
1.

2.

3.

4.

Overview and Scope

1.1.
1.2.
1.3.
1.4.
1.5.
1.6.

4
4
4
4
4
4

Functional Description
Assumptions
Transaction Volume
Frequency & Timing
Processing Type
Output Type

Detailed Functional Requirements

2.1. Functional Specification for Enhancements

2.1.1. Processing logic:
2.2. Error Handling---2.3. Security and Authorization
2.4. Processing and Operational Considerations
2.4.1. Performance
2.4.2. Batch Requirements
2.4.3. Others

5
5
6
6
6
6
6
6

Appendix

3.1. Glossary of Terms

3.2. Additional Reference Documentation

6
7

Section 4 : Test Case and Test Related Result specification

Copyright@2015 Accenture. All rights reserved

1.

Overview and Scope

1.1.

Functional Description

Business need in IGL is to capture different types of disconnections.

These Disconnections will be of the following various types:
(a) Permanent disconnection with device removal.
(b) Permanent disconnection without device removal.
(c) Temporary disconnection with device removal.
(d) Temporary disconnection without device removal.
(e) Disconnection through Dunning.
To meet these requirements, customized processing variants, catering to the above types
will be configured. Users will have an option to select the variant in a pop up in transaction
for creating disconnection document. Based on the selected variant in the pop up,
disconnection will be carried out.
All the variants which have device removal, should automatically remove meters installed on
completion of disconnection displaying a success message after disconnection entry.

1.2.

Assumptions

1.3.

1.4.

Standard variant will be used for disconnection through dunning. Dunning will
automatically create the disconnection document with processing variant
DUNN.
Device removal will not take place in variant DUNN.

Transaction Volume

Transaction volume will be directly proportional to number of requests

received for disconnection in CRM.

Expected number would be 500 per month.

Frequency & Timing

Daily

Copyright@2015 Accenture. All rights reserved

1.5.

Processing Type

1.6.

Manual

Output Type

NA

2.

Detailed Functional Requirements

1.7.

Functional Specification for Enhancements

1.7.1.

Processing logic:

Logic for Selection of processing variant

The following processing variants below will be configured and the user will have an option
to select these in Transaction EC86.
The reason for disconnection for all these processing variants will be 03 customer
requested disconnection
1. DC01 - Permanent Disc. without device removal
2. DC02 - Permanent Disc. with device removal
3. DC03 - Temporary Disc. without device removal
4. DC04 - Temporary Disc. with device removal
5. DUNN Standard processing variant for dunning related disconnection

The user will perform the disconnection entry, enter the meter reading for disconnection and
save the
transaction( Transaction Code EC86).
On saving of disconnection entry, standard SAP event can be used. Below details to be
configured(suggested).

Copyright@2015 Accenture. All rights reserved

Transaction code: SWE2. Create new entry as given below:

Object category: BOR Object Type
Object Type: DISCONNECT
Event: DISCONENTERED
Receiver Type: DUMMY
Choose function module in receiver call. Create a custom function module and assign it to
the receiver type
function module. Enable the linkage activation. Object key will be the disconnection
document number which
will be passed into the function module.
2) The program will first check whether the disconnection reason EDISCDOCDISCREASON=03 (customer request) EDISCDOC-STATUS=21 (disconnection carried out).
If both the condition is satisfied, go to nextstep, else exit.
3) Get the installation number (ANLAGE) from the table EDISCDOC passing the
disconnection document number.
4. The device will be fetched from table EGERH passing the installation number and
fetching the logical register number. (EGERH-LOGICNR) where bis is equal to 31.12.9999.
5. The value of EGERH-EQUI will also be fetched and passed in table EQUI to fetch the
EQUI-SERNR (Device).
6. The values for device, installation and date will be passed to the custom function module
to remove the device automatically.
7. On removal of device, a success or failure message should be passed to the screen.

1.8.

Error Handling---Error Message

Error Handling Procedure

NA

In case a failure message has been

received that device removal is not
successful, the device will have to be
removed manually using transaction
EG32.

Copyright@2015 Accenture. All rights reserved

1.9.

Security and Authorization

Authorization for performing disconnection will be provided only to authorized
business users.

1.10. Processing and Operational Considerations

1.10.1. Performance
NA
1.10.2. Batch Requirements

NA

1.10.3. Others
NA

3.

Appendix

1.11.

Glossary of Terms
Term

Definition

NA

NA

1.12. Additional Reference Documentation

NA

Copyright@2015 Accenture. All rights reserved

Test Specification

4.

Section 4 : Test Case and Test Related Result specification

Number:

Prepared on: 04.04.2014

Test Cases
Carry out disconnection using processing
variant
Carry out disconnection using processing
variant
Carry out disconnection using processing
variant

Expected Results
Disconnection should be carried out
successfully with device removal
Disconnection should be carried out
successfully with device removal
Disconnection should be carried out
successfully and device should not be
removed.
Disconnection should be carried out
successfully and device should not be
removed.

Carry out disconnection using processing

variant

Copyright@2015 Accenture. All rights reserved