FUNCTIONAL/TECHNICAL SPECIFICATION

FUNCTIONAL/TECHNICAL
SPECIFICATION
(Insert RICEFW Object Type Here, e.g. Workflow)
RICEFW #: Enter RICEFW Object Name

Bernalillo County 1
Review and Approve:

Functional Specification Review Functional Lead Date

Functional Specification Review Manager Date

Technical Specification Review Developer Date

2
 Table of Contents
1. FUNCTIONAL SPECIFICATION .......................................................................................................... 5
1.1. General Object Overview ................................................................................................................ 5
1.1.1. Purpose ........................................................................................................................................ 5
1.1.2. Definitions, Acronyms, and Abbreviations .............................................................................. 5
1.1.3. Description................................................................................................................................... 5
1.1.4. Assumptions................................................................................................................................ 6
1.1.5. Issues ........................................................................................................................................... 6
1.1.6. Detailed Process Description .................................................................................................... 6
1.1.6.1. Requirements/Detail ............................................................................................................... 6
1.1.6.2. Configuration Requirements .................................................................................................. 6
1.1.7. Control/Audit Processing Requirements .................................................................................. 6
1.1.8. Authorization Requirements ...................................................................................................... 7
1.2. Enhancement- Enter Enhancement Name .................................................................................... 7
1.2.1. High Level Logic ......................................................................................................................... 7
1.2.2. Object Details .............................................................................................................................. 7
1.2.1.1 SAP User Exit .......................................................................................................................... 7
1.2.1.2 Function Exits .......................................................................................................................... 7
1.2.1.3 Field Exits ................................................................................................................................ 7
1.2.1.4 Menu Exits ............................................................................................................................... 7
1.2.1.5 Screen Exits ............................................................................................................................. 7
1.2.1.6 BADI .......................................................................................................................................... 8
1.2.1.7 Other ......................................................................................................................................... 8
1.3. Workflow .......................................................................................................................................... 8
1.3.1. Other ........................................................................................................................................... 10
1.4. Reports ........................................................................................................................................... 10
1.4.1. Requirements Overview ........................................................................................................... 10
1.4.2. As Is Screen Capture or Mockups ........................................................................................... 10
1.4.2.1. Report #1 ................................................................................................................................ 10
1.4.2.2. Report #2 ................................................................................................................................ 10
1.4.2.3. Report #3 ................................................................................................................................ 11
1.4.3. Data Fields/Report Layout (Excel Template) .......................................................................... 11
1.4.4. Predecessor and/or Dependencies ......................................................................................... 11
1.4.4.1. Predecessor ........................................................................................................................... 11
1.4.4.2. Dependencies ........................................................................................................................ 11
1.4.5. Special Requirements ............................................................................................................... 11
1.4.6. User/User Groups ..................................................................................................................... 12

3
1.4.7. Source Systems ........................................................................................................................ 12
1.4.8. Other ........................................................................................................................................... 12
1.5. Forms ............................................................................................................................................. 12
1.5.1. Layout Information .................................................................................................................... 12
1.6. Interfaces ....................................................................................................................................... 13
1.6.1. Interface Summary .................................................................................................................... 13
1.6.2. Configuration requirements ..................................................................................................... 13
1.6.3. Data Mapping Template ............................................................................................................ 13
1.6.4. Control and Audit Requirements ............................................................................................. 13
1.7. Conversions................................................................................................................................... 13
1.7.1. Conversion Summary ............................................................................................................... 13
1.7.2. Legacy Data Extraction Process ............................................................................................. 13
1.7.3. Risk Assessment ...................................................................................................................... 14
1.7.4. Data Cleansing Assessment .................................................................................................... 14
1.7.5. Data Validation Requirements ................................................................................................. 14
1.7.6. Manual Conversion Contingency ............................................................................................ 14
1.7.7. Sequence of Conversion Activities (including dependencies) ............................................ 15
1.7.8. Data Mapping Template ............................................................................................................ 15
1.7.9. Control and Audit Requirements ............................................................................................. 15
2. TECHNICAL SPECIFICATION........................................................................................................... 16
2.1. General Object Overview .............................................................................................................. 16
2.2. Report / Interface/ Dialog Program Information ......................................................................... 16
2.2.1. Screen validations/ Screen flow logic ..................................................................................... 16
2.2.2. Output layout ............................................................................................................................. 16
2.3. Class Information .......................................................................................................................... 16
2.4. Process Flow ................................................................................................................................. 17
2.5. Program Structure ........................................................................................................................ 17
2.6. Enhancements/User Exits ............................................................................................................ 17
2.7. Data Conversion ............................................................................................................................ 18
2.8. Forms ............................................................................................................................................. 18
2.8.1. Type of Form.............................................................................................................................. 18
2.9. Custom Development ................................................................................................................... 19
3. TESTING ............................................................................................................................................. 20
3.1. Data Requirements ....................................................................................................................... 20
3.2. Unit Test Plan/Expected Results/Actual Results ....................................................................... 21
3.3. Unit Test Follow-up Required ...................................................................................................... 22
3.4. Functional Testing ........................................................................................................................ 22
3.4.1. Use Cases .................................................................................................................................. 22
3.4.2. Validation and Testing Scenarios............................................................................................ 22

4
1. FUNCTIONAL SPECIFICATION
1.1. General Object Overview
1.1.1. Purpose
[This section should briefly describe the purpose of the software and identify the intended audience.]

Business Driver/Purpose

1.1.2. Definitions, Acronyms, and Abbreviations

[This subsection should provide the definitions of all terms, acronyms, and abbreviations required to
interpret properly the FS.]

1.1.3. Description
Area (System modules,
components) Ex. ECC,
SRM, BI, PI, MDM
Program Transaction code
Short Description
Gap ID# Gap Description
Priority Complexity
Volume of data Date Available
Frequency
Processing Mode Batch Online
Impacted Software ECC SRM EDI Sub-system
Packages and Business
System BW Portal Other (Specify):
Technical information
1 RICEFW Type
2 Module/Sub-Module
3 Data Object
(Purchase Order,
Shopping
Cart)
4 Dependency
General Information
What will result if Legal requirements not fulfilled
enhancement is not
Lack of essential business information
created?
Lack of functions compared to legacy system
Others (Specify):

5
 What is the approximate
duration of development
work (8 hr work days)?
Is there an alternative in Yes If yes, describe the alternative:
the standard system?
No
Why is the alternative not Performance problems Complexity
acceptable?
Others (Specify):
Reference Document(s)

1.1.4. Assumptions

Assumptions

1.1.5. Issues
[This section should be used as a log during the creation of this document to outline any outstanding
issues that need to be resolved prior to continuing with the development work. Prior to sign-off there
should be no open issues remaining.]

Issu Issue Owner Date Issue Issue Resolved By Date

e# Raised Description Resolution
1
2
3
4
5
6

1.1.6. Detailed Process Description

1.1.6.1. Requirements/Detail
Detailed Process Description
Current Functionality

Required Functionality

Process Description

Considerations

1.1.6.2. Configuration Requirements

[Enter if applicable.]

1.1.7. Control/Audit Processing Requirements

Control/Audit Processing Requirements

6
1.1.8. Authorization Requirements
[Enter Authorization objects/ fields to be used and Specific user Groups.]

Security Requirements and Authorization Details

[Details on the Security & Authorization]

[Every authorization object needs to be documented to provide the security administrator information on the
purpose and use of the object.]

1.2. Enhancement- Enter Enhancement Name

[Enter a brief description of the Enhancement.]

1.2.1. High Level Logic

High Level Logic

[Specify detailed logic.]

1.2.2. Object Details

[Mention the technical details of the development. Fill the appropriate section.]

Object Definition
Object Type: SAP User Exit Function Exits Field Exit
Menu Exit Screen Exit BADI
Other:

1.2.1.1 SAP User Exit

Object Main Program Includes Form Routines

1.2.1.2 Function Exits

Object Main Program Logical Function Module Includes
Trigger Point Name

1.2.1.3 Field Exits

Object Main Function Field Ext. Id Screen Screen Conditions
Program Module Number Field Name for
Name Name Execution

1.2.1.4 Menu Exits

Object Menu Path Function / Transaction Code

1.2.1.5 Screen Exits

Object Main Program Name Screen Number Program Name & Sub
Screen Number

7
 Object Main Program Name Screen Number Program Name & Sub
Screen Number

1.2.1.6 BADI
Object Methods Comments

1.2.1.7 Other
[Enter additional information.]

1.3. Workflow
Workflow Process Overview
(Include Flow Chart)

Workflow Triggering Conditions

(Specify Triggering events/start conditions.)

Workflow Termination Conditions

(Specify terminating events to stop workflow.)
Workflow Restart

Workflow Step Detail Approval Step 1

(Step type, agent determination, possible deadline escalations.)
Step Type
Dialog Executable (Change/display object Background (Post/reject document)
Decision Task (Show approve/reject) Condition/ Logical Step (Check document type)
Business Object Used

Agent Determination

Work Item Description

Conditions before executing/Possible actions afterwards

Deadline Escalation

8
Workflow Step Detail Approval Step 1
(Step type, agent determination, possible deadline escalations.)

Level Escalation Period Escalation Notification Escalation Agent

(No. of days/hrs) (Subject/Body Include word Determination
document)

Workflow Step Detail Approval Step 2 (Must have reference to workflow chart)
(Step type, agent determination, possible deadline escalations. Copy this section for each workflow step.)
Step Type
Dialog Executable (Change/display object Background (Post/reject document)
Decision Task (Show approve/reject) Condition/ Logical Step (Check document type)
Business Object Used

Agent Determination

Work Item Description

Conditions before executing/Possible actions afterwards

Deadline Escalation

Level Escalation Period Escalation Notification Escalation Agent

(No. of days/hrs) (Subject/Body Include word Determination
document)

Workflow Step Detail Approval Step 3 (Must have reference to workflow chart)
(Step type, agent determination, possible deadline escalations. Copy this section for each workflow step.)
Step Type
Dialog Executable (Change/display object Background (Post/reject document)
Decision Task (Show approve/reject) Condition/ Logical Step (Check document type)
Business Object Used

Agent Determination

Work Item Description

Conditions before executing/Possible actions afterwards

Deadline Escalation

9
 Workflow Step Detail Approval Step 3 (Must have reference to workflow chart)
(Step type, agent determination, possible deadline escalations. Copy this section for each workflow step.)

Level Escalation Period Escalation Notification Escalation Agent

(No. of days/hrs) (Subject/Body Include word Determination
document)

1.3.1. Other
[Enter additional information.]

1.4. Reports
1.4.1. Requirements Overview

Report Operational Managerial Strategic Regulatory

Nature Others (explain):
Preliminary Webl BEx Web Xcelsius/Dashboard Crystal Reports
Report Type ABAP BOBJ Report Painter Unknown
Other (explain):
Report Use Internal External
Frequency of Daily Weekly Monthly Quarterly Annually
Usage/Data
Refresh Other (explain):

Report New Report Report Replacement

Replacement Transaction Program Name Description
Code (SE 38)

1.4.2. As Is Screen Capture or Mockups

1.4.2.1. Report #1
Report Name
Transaction Code
Program Name
Selection Screen

Report Output

1.4.2.2. Report #2
Report Name

10
 Transaction Code
Program Name
Selection Screen

Report Output

1.4.2.3. Report #3
Report Name
Transaction Code
Program Name
Selection Screen

Report Output

1.4.3. Data Fields/Report Layout (Excel Template)

[Attached Excel Report Data Fields specifies the following:
Fields required in the report
Field Details ( Type, Selection Screen, Default Values, Filters)]

Report Field List/Field Specification File Path

1.4.4. Predecessor and/or Dependencies

1.4.4.1. Predecessor
Description RICEFW ID Related Document(s)

1.4.4.2. Dependencies
Description RICEFW ID Related Document(s)

1.4.5. Special Requirements

History Data
Formatting
Printing
Data
Confidentiality &
Security
Broadcasting/
Distribution

11
 Graphs/Charts

1.4.6. User/User Groups

User Groups/Roles Special Authorization Requirements

1. 1.
2. 2.
3. 3.

1.4.7. Source Systems

Source System

T-Codes

1.4.8. Other
[Enter additional information.]

1.5. Forms
Type of Development: (What kind of report development is this?)
Modification of Standard SAP Report/Form Name of Standard Report/Form:

Custom Form Have you looked at possible standard

Reports/Forms? Yes No

1.5.1. Layout Information

Form/Report Layout
Sample Layout

High Level Logic

Calculations and Formulas (Fill out any Calculations or Formulas for this report)
Seq. Calculate Field Description Required Calculation and Source Field Format
# Fields
1
2
3

12
1.6. Interfaces
1.6.1. Interface Summary

Interface Type
(Inbound/Outbound)
Interfacing Systems
Frequency (Real
time/Batch)
Batch Frequency Batch Online
Any Encryption/ Annually Quarterly Monthly Weekly
Decryption
Requirements Daily Real Time Ad-Hoc Other
(specify):
Expected Volume

1.6.2. Configuration requirements

1.6.3. Data Mapping Template

DataMappingTemplat
e.xlsx

1.6.4. Control and Audit Requirements

[List all Control/Audit Processing requirements for the development of this object (this section must be
filled out for interfaces and conversions).]

Control/Audit Processing Requirements

1.7. Conversions
1.7.1. Conversion Summary

Source System
Approximate Volume

1.7.2. Legacy Data Extraction Process

Legacy Data Extraction Process

What is the process that the legacy team will use to extract data from the legacy systems (i.e. timing,
automated, manual, tools that will be used, etc. )

13
 [The extract file will need to be in a text format and will be for all valid assets to be converted. The data
extraction file will be saved on the Share Drive in text format, unless specified otherwise. The target name
will be the Object ID name (upper case)_Process appended with .txt (lower case) (Example:
ZMMDC3003_Extract.txt).

**The extraction will need to be done on a periodic basis to allow for extraction during integration and
cutover testing.

Note: Please contact the Legacy Team Developer for the following items:
Batch Program
Legacy File Name
Target Name of Text file]

1.7.3. Risk Assessment

Data Quality Risk Assessment

This section will refer to a matrix that discusses the various risks each conversion possesses. This
matrix will be contained in an excel spreadsheet outside of this document.

1.7.4. Data Cleansing Assessment

Data Cleansing Assessment

What is the process that will be used in order to cleanse the data before being loaded into SAP.

1.7.5. Data Validation Requirements

Data Validation Requirements

How will the team validate the integrity of the data once loaded into SAP.

1.7.6. Manual Conversion Contingency

Is Manual Conversion Possible? If so please describe approach

Please include who will load the data, number of resources needed, time necessary to load, etc.

14
1.7.7. Sequence of Conversion Activities (including dependencies)

Sequence of Conversion Activities

Please list step by step activities for performing the conversion from the extraction activity through
SAP data validation. Please include all associated dependencies.
The following sequence will be followed for this conversion:
1.
2.
3.

1.7.8. Data Mapping Template

DataMappingTemplat
e.xlsx

1.7.9. Control and Audit Requirements

[List all Control/Audit Processing requirements for the development of this object (this section must be
filled out for interfaces and conversions).]

Control/Audit Processing Requirements

15
2. TECHNICAL SPECIFICATION
2.1. General Object Overview
[Enter information about type of object, overall design]

2.2. Report / Interface/ Dialog Program Information

Program Information
Type of Program
(Report, Interface,
Dialog Program)
Transaction code
Transaction
Description
Program Name
Screen Number
What SAP
transaction(s) do
this involve?
Menu path for
transaction(s)
Provide Selection -
options &
Parameters (if
applicable)
Selection Option(s) Field Name Default (Mandatory, Value, etc.)
Description

2.2.1. Screen validations/ Screen flow logic

2.2.2. Output layout

2.3. Class Information

Class Details (Interface Framework)
Class Name
Super Class
Name
Global Attributes
Attribute Name Type/Visibility Default Value

16
 Methods
Method Name Description Method Parameters (Name/Type/Visibility)

Flow Logic:

Flow Logic:

Flow Logic
Events
Event Name Description Event Parameters Event Handler Method
Name

2.4. Process Flow

Process Flow

2.5. Program Structure

Program Structure

2.6. Enhancements/User Exits

Object Definition
Object Type: SAP User Exit Function Exits Field Exit
Menu Exit Screen Exit BADI
Other:

Enhancements (This section to be deleted if object does not belong to this classification)
Enhancement Name:

Name and type of SAP

Exits/ Objects that
need to be enhanced:
Describe
Enhancement:

Business Object Enhancement

17
 Business Object:

Name:
Program:
Events Created:

Methods Created:

2.7. Data Conversion

Object Definition
Conversion Method: LSMW ABAP Program Test Tool (eCATT, etc.)
Other (specify):

Conversion Approach
Object Details
[Custom program will be outlined in section 2.1. For all other objects describe details of conversion
methodology here.]
Data Mapping/Translation using the data mapping template outline in Section 1.7.8

Error Correction Mechanism

Audit Reporting

Error Reconciliation Process, if any

2.8. Forms
2.8.1. Type of Form

Form Type (SAP Script, Smart Form, or PDF Form Name

Form Attributes

Page Properties

18
 Page Layout (Windows and Logic)

Window Name:
Name of Element Format Options Logic

Window Name:
Name of Element Format Options Logic

Window Name:
Name of Element Format Options Logic

*If any print program is developed document that in section 2.2

2.9. Custom Development

[Functional details of custom transaction can be incorporated here. Number of screens required and flow
diagram can be included, provide the selection screen shot along with the table name and field name and
screen shot for the required output.

Only to be filled when creating a z-Table for your Enhancement. This section should detail the attributes
of any custom table used, and the properties of its fields.

Note: Existing SAP Data Elements and/or Domains should be used whenever possible when creating
custom table fields, in order to avoid unnecessary typos.]

Table Name
Short Text
Size Category
Table Maintenance
Allowed
Data Class
Buffering
Table Maintenance
Generation
Authorization
Group
Field Data Domain Type Length Check Key Foreign Description
Name Element Table Field Key
Field

Comments

New Tables

19
 New Tables
Table: Expected Size:

Table Field Name Data Element Domain Description Key Field

New Data Elements

Data Element Name Description Domain Field Labels

Describe the Update Method for Tables:

(Method, sequence, function modules, update processes, locking requirements)

3. TESTING
3.1. Data Requirements

Business Requirement Data Object Required Type (Master data, Description of Testing
Tested for Unit Testing Transaction Data, Dependency to
Historical Data) Business Requirement

20
3.2. Unit Test Plan/Expected Results/Actual Results
Business Unit Test Application System Test Type Master Data Transaction Historical Expected Actual
Requirement Description Component (Negative, Sample Data Sample Data Sample Results Results
Tested Tested Positive)

21
SRM 7.0 Bernalillo County
 FUNCTIONAL/TECHNICAL SPECIFICATION
3.3. Unit Test Follow-up Required
Follow Up Action Item Assigned to Status

3.4. Functional Testing

3.4.1. Use Cases

[Use case - How the RICEFW object will be used by the user or system. A use case is series of steps
showing how user will use this object]

Use Case 1 Description

Business process (steps)
Rules
Solution Approach
Standard(Y/N)
Enhancement Type (RICEFW)

3.4.2. Validation and Testing Scenarios

Validation Requirements
[List the data, totals, exceptions, etc. to be used for Report Validation.]

Testing Scenarios
Example:
ID Description
Normal Functionality test cases that ensure the conversion requirement as it should
1
2
3
Exception - special logic or exceptions
4
5
6
Error Handling - functionality in case of errors
7
8

SRM 7.0 Bernalillo County 22