employee maintenance v1.0

SAP Implementation at PIL

Online Programming - Functional

specification

Note: As this is a case study that simulates a real life development object, some fields will be marked as TBD and highlighted in Blue. These fields should be having real values, in customer development specifications

Functional Specification – Online ProgrammingEmployee Details Maintenance

Document Reference: TBDVersion: 1.0 Document Status: Signed off

Author: Avra K Guha

Last Revision Date: 21-Nov-2006Date Created: 21-Nov-2006Date Printed: 21-Nov-2006

FS_Employee_Maintenance_v1.0 21-Nov-06 of 12

SAP Implementation at PIL Online Programming - Functional

specification

Document Control

Business Area Cross-Application

GAP ID TBD

FS Definition Form ID TBD

SAP R/3 Version ECC 5.0

Global / Market TBD

Approval and Distribution

Approved by Name Role Signature DateProcess Team Lead

TBD TBD TBD TBD

Development team Lead

TBD TBD TBD TBD

Document History

Version Reason for change Date1.0 Initial version 21-Nov-061.11.21.3



specification

Table of Contents

1. GENERAL INFORMATION.............................................................................................................42. BUSINESS NEEDS & REQUIREMENTS..........................................................................................53. ISSUES......................................................................................................................................54. SELECTION SCREEN DETAILS.....................................................................................................55. CURRENT FUNCTIONALITY..........................................................................................................66. DESIRED FUNCTIONALITY...........................................................................................................67. TECHNICAL DETAILS...................................................................................................................6

7.1.EXTRACT DATA RELATIONSHIP DIAGRAM...........................................................................68. STARTING CONDITIONS..............................................................................................................89. SECURITY REQUIREMENTS/ AUTHORIZATION DETAILS..................................................................910. DATA MAPPING TABLES.............................................................................................................9

10.1. DESIRED REPORT DESIGN/LAYOUT:.................................................................................1010.2. REPORT EXAMPLE:..........................................................................................................11

11. CUSTOM TABLES/STRUCTURE IN SAP......................................................................................1212. RECOVERY AND RESTART........................................................................................................1213. LANGUAGE OF TEXTS...............................................................................................................1314. CURRENCY AND UNITS OF MEASURE........................................................................................1315. ASSUMPTIONS..........................................................................................................................1316. ERROR HANDLING....................................................................................................................1417. Testing Scenarios..................................................................................................................14



specification

1. General Information

Area (SAP System components): Cross Application Date: 21-Nov-2006

Short description: Employee Maintenance

Requested by: TBD Tel no: TBD

Author: Avra K Guha Tel no: TBD

Program Transaction code: ZEMP_DET

Task ID/Demand Number: TBD

Project Name: SAP Implementation at PIL

Priority: High/mandatory Medium/recommended

Low/optional

Complexity: High Medium Low

Volume of data: Medium DATE AVAILABLE FROM: TBD

Mode: Online Background

Frequency: Daily Weekly Monthly Biweekly Others (Specify) : On Demand

Technical information:

1. Report created using:

2. Characteristics required:

Report Painter Report Writer SAP Query ABAP program Info system R/3 BW Crystal Reports

Drilldown Buttons Sort ALV Grid ALV List Entry file Others: Online Programming

General information:

1. Results if no Reports are created:

Legal requirements not fulfilled Lack of essential business information Lack of functions compared to legacy system Others (Specify):

DURATION OF DEVELOPMENT WORK

(IN MAN-DAYS):3 days (Coding+Documentation+Testing)

Is there an alternative in the standard system?

Yes No

Description of alternative:

Reasons why alternative is not acceptable:

Performance problems Complexity Others (Specify) :



specification

2. Business Needs & Requirements

Power India Limited started its operation in the year 1965. From its humble beginning in a small town of Maharashtra called Ranjangaon PIL has achieved several milestones and today it is one of the largest manufactures of storage batteries in India. Currently the company is having seven production facilities in India namely Ranjangaon, Pune, Nashik, Chennai, Hosur, Gurgaon and Durgapur respectively.

Power India Limited, the flagship company of the Oscar group is the market leader in the storage battery industry. It manufactures wide range of batteries from 2 Ah capacities to 10500 Ah to cover the broadest spectrum of applications.

The SAP Implementation at Power India Limited (PIL) will achieve the following:1. Standardize and streamline the business process2. Establishing an Integrated information repository3. Improvement in the area of Planning4. Complete visibility of stock

The requirement is to develop a custom module pool program to maintain the details of employees. The details of employees are maintained in a custom table having employee number as the key field. The module pool program shall have three screens: the first screen allows the user to enter an employee number; if the employee number is present in the employee table, the details are displayed in the next screen. The user can modify the details in this screen and save the modified entry. The third screen displays a list of all employees.

3. Issues

NoneIssue

#Issue owner

Date Raised

Issue Description Issue Resolution Resolved By & Date

4. Selection Screen DetailsNot Applicable

Name Table-Field / Check Box /

Radio Button – with group

Parameter (P) / Select-option (S)

Comments (Range, Single/Multiple

selection, Patterns, Mandatory etc.)

Default Value



specification

Name Table-Field / Check Box /

Radio Button – with group

Parameter (P) / Select-option (S)

Comments (Range, Single/Multiple

selection, Patterns, Mandatory etc.)

Default Value

Desired screen design (selection possibilities):(use attachment if necessary):

5. Current Functionality No custom table or development to manage specific employee details

6. Desired Functionality

Users should be able to maintain a custom employee table using a custom transaction that is required to be developed.

7. Technical Details

A module pool program for maintaining details of employees is required to be developed as per the following specifications:

The details of the employees are maintained in a custom table.

The designs of the screens are as follows:

Screen 1:

The user should be able to enter an employee number on this screen and navigate to the next detail screen hitting either ‘Enter’ OR a ‘Next’ Button which shall be developed in the application toolbar.

The user can also navigate to the ‘Employee List’ screen hitting the ‘List’ button.

For navigation to other screens, two new buttons shall be developed on the application tool-bar.i) Next button : To navigate to Screen 2



specification

ii) List button : To navigate to Screen 3

If an incorrect employee number is entered, an error message should be displayed as ‘Employee Number does not exist’ and the above field should remain open for input.

The user should be able to exit this screen using the ‘Back’, ‘Exit’ or ‘Cancel’ buttons.

Screen 2:

The second screen should display all the fields of the employee table. The employee number field should be ‘display’ only while the rest of the fields should be open for input.

The details of the employee whose employee number had been entered in the previous screen is displayed here. The user can change the details and hit the ‘Save’ button to save the updated entries in the employee custom table.


Screen 3:



specification

Details of all employees are displayed in this screen.


7.1.Extract Data Relationship Diagram

Not applicable

8. Starting Conditions

The program would be run on demand.



specification

9. Security Requirements/ Authorization DetailsNone

10. Data Mapping Tables

Not applicable


SAP Implementation at PIL Online Programming - Functional Specification

10.1. Desired Report Design/Layout: (use attachment if necessary):

Not applicable

10.2. Report Example: (use attachment if necessary):



Specification

11. Custom Tables/Structure in SAP

Table Name ZEMPLOYEEShort text Employee DetailsSize category 0Table maintenance allowed

Yes

Data class APPL0Buffering NoTable maintenance generator

Yes

Authorization Group NAField Name

Data Element Domain Type Length Check Table-Field

Key Field

Foreign Key

Description

MANDT MANDT MANDT CLNT 3 N Y N ClientZEMPNO ZZEMPNO CHAR6 CHAR 6 N Y N Employee NumberZEMPNAME

ZNAME_EMP CHAR20

CHAR 20 N N N Employee Name

ZEMPORG ZEMPORG CHAR10

CHAR 10 N N N Employee Organization

ZBAND ZBAND CHAR2 CHAR 2 N N N Employee BandZEMAIL ZEMAIL CHAR3

0CHAR 30 N N N Employee e-mail

Comments

12. Recovery and Restart

If the program fails half way it will not have any impact on any other processes or programs. It should be simply re-started by the user.

13. Language of texts

The texts for the program should be displayed in User’s logon language.



Specification

14. Currency and Units of Measure

None

15. Assumptions

The custom employee table is accurately maintained.

16. Error Handling

Screen 1:If employee number entered does not exist in the custom table following error message should be issued:

- Employee Number does not exist.

If no employee number is entered on the first screen, the following error message should be issued. - Please enter employee number.

17. Testing ScenariosThe custom table needs to be populated with a few employee records for unit testing.

Normal Functionality - test cases that ensure the report functions as it should. ID Description1 A valid employee number is entered and employee details are updated in the next screen2 User navigates away from screen 1 using the ‘EXIT’ or ‘BACK’ or ‘CANCEL’ button.3 User navigates away from screen 2 using the ‘EXIT’ or ‘BACK’ or ‘CANCEL’ button.4Exception - special logic or exceptions (e.g. report shold exclude certain specific condition)

56Error Handling - functionality in case of errors (e.g. Error Message or Error Log )

7 An invalid employee number is entered

8


employee maintenance v1.0

Documents