Sunteți pe pagina 1din 15

Functional Specification

Functional Specification
Document Control
Document Identification:
The following is current information about the document: (Maintain all relevant section)

Document ID

ZFSHRPDE0007

Document Description
Version
Creation Date
Author
SAP Version
Development Type

Document Change and Revision History:


Version

Date

Author

Section/Page

Summary of Changes

Related Documents:
Document ID
ZFSHRPDE0007

Document Name

Document Location

SCI_HCM_PD_FS_APPRAISAL_WORKFLOW_SETUP_FOR_SCI_STAFF

Approval / Sign-off:
Name

Role

Date

Signature

Page 2 of 15

Functional Specification
Table of Contents
1

REQUIREMENT DETAILS ............................................................................................................................. 5


1.1
1.2
1.3
1.4
1.5
1.6
1.7
1.8
1.9
1.10
1.11
1.12

BUSINESS DRIVER ..................................................................................................................................... 5


CURRENT FUNCTIONALITY ......................................................................................................................... 5
DESIRED FUNCTIONALITY / FUNCTIONAL DESCRIPTION ........................................................................... 5
PROCESS FLOW ......................................................................................................................................... 5
SCOPE ........................................................................................................................................................ 8
OUT OF SCOPE ........................................................................................................................................... 9
PROCESSING AND VALIDATION REQUIREMENTS ....................................................................................... 9
ERROR HANDLING / EXCEPTION HANDLING .............................................................................................. 9
ASSUMPTIONS ............................................................................................................................................ 9
CONSTRAINTS ............................................................................................................................................ 9
PERFORMANCE CRITERIA .......................................................................................................................... 9
APPLICATIONS AFFECTED.......................................................................................................................... 9

OPEN ISSUES ................................................................................................................................................ 10

REQUIRED DATA .......................................................................................................................................... 11


3.1
3.2
3.3
3.4
3.5

FORM / REPORT DESIGN ........................................................................................................................... 13


4.1
4.2
4.3

GENERAL.................................................................................................................................................. 14
REQUIRED SCREENS ............................................................................................................................... 14
SCREEN LAYOUTS ................................................................................................................................... 14

ADDITIONAL INFORMATION ..................................................................................................................... 15


7.1
7.2
7.3
7.4

GENERAL.................................................................................................................................................. 14
DEPENDENCIES ........................................................................................................................................ 14
SCHEDULING CONSIDERATIONS .............................................................................................................. 14

ENHANCEMENT / MODIFICATION DESIGN ........................................................................................... 14


6.1
6.2
6.3

GENERAL.................................................................................................................................................. 13
SELECTION CRITERIA............................................................................................................................... 13
OUTPUT LAYOUT...................................................................................................................................... 13

CONVERSION / INTERFACE DESIGN ...................................................................................................... 13


5.1
5.2
5.3

INPUT DATA.............................................................................................................................................. 11
OUTPUT DATA .......................................................................................................................................... 11
DATA MAPPING ........................................................................................................................................ 12
LEGACY FILE DETAILS ............................................................................................................................. 12
TABLES USED ........................................................................................................................................... 12

TEST PLAN ............................................................................................................................................... 15


BACKUP / RECOVERY .............................................................................................................................. 15
SECURITY PROFILE & AUTHORIZATION ................................................................................................... 15
AUDIT / CONTROL .................................................................................................................................... 15

CHANGE CONTROL ..................................................................................................................................... 15

Page 3 of 15

Functional Specification

Section I: Justification
Area ( Module):

HCM-PD

Date
(dd/mm/yyyy):

Requested by:

Prem Prakash

Brief description:

Workflow Development for SCI Staff

Program type: (select


the check box)

Conversion

Batch Interface

Online Interface

Report

Form

Enhancement

Extension

Dialog

Modification

Unknown

Others

BAPI

ALE/ IDOC

Application Development

Charateristics

Drill Down

Priority:

High/mandatory

Only for Interfaces:

07.01.2010

ALV

Others (pl specify) Form


Medium/recommended

Low/optional

Not Applicable

Type of interface:

Real-Time

Batch

Direction of interface:

Inbound

Outbound

Both

Frequency:

Daily

Weekly

Monthly

Biweekly

Other:

Only for Reports: Not Applicable


1. The report will be created via:

Report Painter

Report Writer

ABAP Program

Info System

2. Requested characteristics:

Drill-down

Pushbuttons

3. Proposed execution is
online/background

Entry files

Others:

ABAP Query

Sort

4. Any Authority checks are required


5. If any LDB is available? if yes,
which screen to use

Page 4 of 15

Functional Specification
1

Requirement Details
1.1

Business Driver
To set-up appraisal workflow process for SCI staff.

1.2
Current Functionality
Describe the current functionality.
Currently appraisal process is done manually.

1.3

Desired Functionality / Functional Description


As per the requirement appraisal form should flow to respective supervisors using workflow to
complete the appraisal process

1.4

Process Flow

1.4.1

1.4.2

As-Is Process Flow


Appraisal is done manually.

To-Be Process Flow


Following below is the appraisal workflow process for SCI staff.

Page 5 of 15

Functional Specification

Page 6 of 15

Functional Specification

Page 7 of 15

Functional Specification

1.5

Scope

Appraisal will be carried out using workflow for SCI staff


Page 8 of 15

Functional Specification

1.6

Out of scope
N/A

1.7

Processing and validation Requirements

N/A
1.8

Error Handling / Exception Handling


N/A

1.9

Assumptions
N/A

1.10 Constraints
N/A

1.11 Performance Criteria


There will be a very limited number of users involved in this process. No special performance
issues exist.
N/A
1.12 Applications Affected
List of the application areas being changed or affected by this design.
SAP Module
HCM-PD
NON-SAP
System

Impact/Change Description
Appraisal workflow for SCI staff
Impact/Change Description

Page 9 of 15

Functional Specification

Open Issues

Issue
No

Description

Assigned
To

Status

Impact

Resolution

Page 10 of 15

Functional Specification

Required Data
3.1
Input Data
Describe the data required to support the development. Where possible include input field
definition (Structure or Table Name, Field Name, Field Description, Format, Values). Include this
information when there is no data mapping or corresponding legacy data file.
N/A

From System
Name

Structure or
Table Name

Structure or Table Location

Field Name

Field Description

Expected
Volume
Format

Values

3.2
Output Data
Describe the data created from this development. Where possible, include output field definition
(Structure or Table Name, Field Name, Field Description, Format, Values). Include this information
when there is no data mapping or corresponding legacy data file.
N/A
To System
Name
Field Name

Structure or
Table Name

Structure or Table Location

Field Description

Expected
Volume
Format

Values

Page 11 of 15

Functional Specification

3.3
Data Mapping
SAP fields are mapped to non-SAP (legacy) fields in the field map. The required field map rules
should be described in the field map to ensure the appropriate mapping are done. This information
is required for conversions.
N/A
3.4
Legacy File Details
Include details about all legacy data files used for input or output. This information is pertinent for
conversions and file-based interfaces. For each one, specify the following information wherever
applicable.
N/A

File Location and Name:


Logical File Name:
Variants:
Legacy File Description:
Sort Requirements:
Legacy File Layout:
Indicate precise layout of data file. Indicate field names, key, starting position, length and format.
Field names should match those indicated in under data mapping. Also indicate any required
filtering.
Record
Ref Name

Field
Name

Field Lengt
Key Type h

Starting
Position Format

Comments

3.5
Tables used
Indicate the standard or specific tables or data bases that have to be used for this process and their
contents.
For a specific table, state: the name of the fields, the length, data element, description and key
areas:

N/A
Field name

Key

Type

Format or data element Description

Page 12 of 15

Functional Specification

Form / Report Design


N/A
4.1

General

N/A
SAP Menu Path: Accounting> Financial Accounting>Account payable>periodic
payments
Output Determination:
Output Type:
Mode of Execution:
Program Name:
Layout Set Name:
Standard Text:
Special Printing/Media Requirements:
Sort Criteria:
Logo:
Bar Codes:
Distribution/Volume:

processing>

4.2
Selection Criteria
Specify all parameters to the form or report.
N/A

Field
Name

Table Field /
Checkbox /
Radio Button

Select-Option (S) Comments (Range, Single/Multiple


Default
or Parameter (P) Selection, Patterns, Mandatory, etc.) Value

4.3
Output Layout
Attach a form or report layout. Include field layout, spacing, header/footer details. Indicate whether
times should indicate local or system time. Specify paper format and paper size if not indicated in
media requirements.
N/A

Conversion / Interface Design


Complete this section for conversion or interface development.
N/A

Page 13 of 15

Functional Specification
5.1
General
Describe the required functionality. Specify the following information wherever applicable.
N/A
Inbound/Outbound:
Frequency:
Volume:
Legacy Data Source:
Legacy Contact:
Method of Execution:
Mode of Handling:
Data Cleansing Process:
Reconciliation Process:
Data Consistency Check:
Error Handling Method:
Interface Process Log Details:
Post Execution Notification Details:
5.2

Dependencies

N/A
5.3
Scheduling Considerations
Describe any scheduling considerations. Specify the following information wherever applicable.
N/A
Synchronous/Asynchronous:
Load Balancing/Parallel Processing:
Other System Loads at Time of Process Run:
Time Window for Execution:
Triggering Mechanism/Process:

Enhancement / Modification Design


N/A
6.1

General

N/A
6.2
Required Screens
List all required screens. Describe their purpose and flow.
N/A
6.3
Screen Layouts
Complete the following attachment for each screen.
N/A

Page 14 of 15

Functional Specification
7

Additional Information
7.1
7.1.1

Test Plan
Related Business Scenario and Business Transactions
Identify the business scenario and business transactions this development will be tested
with.
Business Scenario/Business Transaction

7.1.2

Target Test Date


dd-mmm-yyyy

Test Data
Identify the test data requirement and the date it is required
System
ID

Data
ID

Data Name

Data Provider

Date Required
dd-mmm-yyyy
dd-mmm-yyyy

7.2
Backup / Recovery
This section should define the general recovery strategy for this design.
7.3
Security Profile & Authorization
This section should define the general security administration for this design.
What user profile is required to invoke this function.
Profile
Required
7.4
Audit / Control
This section should define any audit solution for this design.

Change Control

Section

Date

Change details

Page 15 of 15

S-ar putea să vă placă și