Test Specification

Functional Specification

FS-DM-Disconnection Processing Variants and Device Removal on Disconnection

Document History

Techincal Specification

Section I: Object General Information

Title (GAP ID):Date: 05.06.2015

Short description:Disconnection Processing Variants and Device Removal on Disconnection

To-Be/ GAPAutomatic removal of devices in case of disconnection for full disconnection cases.

SAP Module/Team:DM

SAP- ObjectDisconnection \ Reconnection

Functional Contact:Monis Shakeel

Category:A

Complexity LevelMedium

Program typeEnhancement

Status Completed

Reviewer

RoleNameSignatureDate

SAP ISU Device Management ConsultantMonis Shakeel05.06.2015

Table of Contents

1.Overview and Scope41.1.Functional Description41.2.Assumptions41.3.Transaction Volume41.4.Frequency & Timing41.5.Processing Type41.6.Output Type42.Detailed Functional Requirements52.1.Functional Specification for Enhancements52.1.1.Processing logic:52.2.Error Handling----62.3.Security and Authorization62.4.Processing and Operational Considerations62.4.1.Performance62.4.2.Batch Requirements62.4.3.Others63.Appendix63.1.Glossary of Terms63.2.Additional Reference Documentation74.Section 4 : Test Case and Test Related Result specification8

Overview and ScopeFunctional 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.

Assumptions 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 DailyProcessing Type ManualOutput Type

NA

Detailed Functional RequirementsFunctional Specification for EnhancementsProcessing logic:Logic for Selection of processing variantThe 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 removal3. DC03 - Temporary Disc. without device removal4. DC04 - Temporary Disc. with device removal5. DUNN Standard processing variant for dunning related disconnection

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

Transaction code: SWE2. Create new entry as given below:Object category: BOR Object TypeObject Type: DISCONNECTEvent: DISCONENTEREDReceiver Type: DUMMY

Choose function module in receiver call. Create a custom function module and assign it to the receiver typefunction module. Enable the linkage activation. Object key will be the disconnection document number whichwill be passed into the function module.

2) The program will first check whether the disconnection reason EDISCDOC-DISCREASON=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.

Error Handling----Error MessageError Handling Procedure

NAIn case a failure message has been received that device removal is not successful, the device will have to be removed manually using transaction EG32.

Security and Authorization Authorization for performing disconnection will be provided only to authorized business users.Processing and Operational ConsiderationsPerformanceNABatch Requirements NAOthersNAAppendixGlossary of TermsTermDefinition

NANA

Additional Reference Documentation NACopyright@2015 Accenture. All rights reserved

Section 4 : Test Case and Test Related Result specification

Number: Prepared on: 04.04.2014

Test CasesExpected Results

Carry out disconnection using processing variantDisconnection should be carried out successfully with device removal

Carry out disconnection using processing variantDisconnection should be carried out successfully with device removal

Carry out disconnection using processing variantDisconnection should be carried out successfully and device should not be removed.

Carry out disconnection using processing variantDisconnection should be carried out successfully and device should not be removed.