Functional/technical specification

Table of Contents 3

1.FUNCTIONAL SPECIFICATION 15

1.1.General Object Overview 15

1.1.1.Purpose 15

[This section should briefly describe the purpose of the software and identify the intended audience.] 15

Business Driver/Purpose 15

1.1.2.Definitions, Acronyms, and Abbreviations 15

1.1.3.Description 15

1.1.4.Assumptions 16

1.1.5.Issues 16

1.1.6.Detailed Process Description 16

1.1.6.1.Requirements/Detail 16

Detailed Process Description 16

Current Functionality 16

Required Functionality 16

Process Description 16

Considerations 16

1.1.6.2.Configuration Requirements 16

[Enter if applicable.] 16

1.1.7.Control/Audit Processing Requirements 16

1.1.8.Authorization Requirements 16

1.2.Enhancement- Enter Enhancement Name 17

1.2.1.High Level Logic 17

High Level Logic 17

[Specify detailed logic.] 17

1.2.2.Object Details 17

Object Definition 17

Object Type: 17

☐ SAP User Exit 17

☐ Function Exits 17

☐ Field Exit 17

☐ Menu Exit 17

☐ Screen Exit 17

☐ BADI 17

☐ Other: 17

1.2.1.1SAP User Exit 17

1.2.1.2Function Exits 17

1.2.1.3Field Exits 17

1.2.1.4Menu Exits 17

1.2.1.5Screen Exits 17

1.2.1.6BADI 17

1.2.1.7Other 18

[Enter additional information.] 18

1.3.Workflow 18

Workflow Process Overview 18

(Include Flow Chart) 18

Workflow Triggering Conditions 18

(Specify Triggering events/start conditions.) 18

Workflow Termination Conditions 18

(Specify terminating events to stop workflow.) 18

Workflow Restart 18

Workflow Step Detail – Approval Step 1 18

(Step type, agent determination, possible deadline escalations.) 18

Step Type 18

☐ Dialog Executable (Change/display object 18

☐ Background (Post/reject document) 18

☐ Decision Task (Show approve/reject) 18

☐ Condition/ Logical Step (Check document type) 18

Business Object Used 18

Agent Determination 18

Work Item Description 18

Conditions before executing/Possible actions afterwards 18

Deadline Escalation 18

Level 18

Escalation Period 18

(No. of days/hrs) 18

Escalation Notification 18

(Subject/Body – Include word document) 18

Escalation Agent Determination 18

Workflow Step Detail – Approval Step 2 (Must have reference to workflow chart) 19

(Step type, agent determination, possible deadline escalations. Copy this section for each workflow step.) 19

Step Type 19

☐ Dialog Executable (Change/display object 19

☐ Background (Post/reject document) 19

☐ Decision Task (Show approve/reject) 19

☐ Condition/ Logical Step (Check document type) 19

Business Object Used 19

Agent Determination 19

Work Item Description 19

Conditions before executing/Possible actions afterwards 19

Deadline Escalation 19

Level 19

Escalation Period 19

(No. of days/hrs) 19

Escalation Notification 19

(Subject/Body – Include word document) 19

Escalation Agent Determination 19

Workflow Step Detail – Approval Step 3 (Must have reference to workflow chart) 19

(Step type, agent determination, possible deadline escalations. Copy this section for each workflow step.) 19

Step Type 19

☐ Dialog Executable (Change/display object 19

☐ Background (Post/reject document) 19

☐ Decision Task (Show approve/reject) 19

☐ Condition/ Logical Step (Check document type) 19

Business Object Used 19

Agent Determination 19

Work Item Description 19

Conditions before executing/Possible actions afterwards 19

Deadline Escalation 19

Level 19

Escalation Period 19

(No. of days/hrs) 19

Escalation Notification 19

(Subject/Body – Include word document) 19

Escalation Agent Determination 19

1.3.1.Other 20

[Enter additional information.] 20

1.4.Reports 20

1.4.1.Requirements Overview 20

1.4.2.As Is Screen Capture or Mockups 20

1.4.2.1.Report #1 20

1.4.2.2.Report #2 20

1.4.2.3.Report #3 20

1.4.3.Data Fields/Report Layout (Excel Template) 21

Report 21

Field List/Field Specification File Path 21

1.4.4.Predecessor and/or Dependencies 21

1.4.4.1.Predecessor 21

Description 21

RICEFW ID 21

Related Document(s) 21

1.4.4.2.Dependencies 21

Description 21

RICEFW ID 21

Related Document(s) 21

1.4.5.Special Requirements 21

1.4.6.User/User Groups 21

1.4.7.Source Systems 22

1.4.8.Other 22

[Enter additional information.] 22

1.5.Forms 22

Type of Development: (What kind of report development is this?) 22

☐ Modification of Standard SAP Report/Form 22

Name of Standard Report/Form: 22

☐ Custom Form 22

Have you looked at possible standard Reports/Forms? ☐ Yes ☐ No 22

1.5.1.Layout Information 22

Form/Report Layout 22

Sample Layout 22

High Level Logic 22

1.6.Interfaces 23

1.6.1.Interface Summary 23

Interface Type (Inbound/Outbound) 23

Interfacing Systems 23

Frequency (Real time/Batch) 23

Batch Frequency 23

☐ Batch ☐ Online 23

Any Encryption/ Decryption Requirements 23

☐ Annually 23

☐ Quarterly 23

☐ Monthly 23

☐ Weekly 23

☐ Daily 23

☐ Real Time 23

☐ Ad-Hoc 23

☐ Other (specify): 23

Expected Volume 23

1.6.2.Configuration requirements 23

1.6.3.Data Mapping Template 23

23

1.6.4.Control and Audit Requirements 23

Control/Audit Processing Requirements 23

1.7.Conversions 23

1.7.1.Conversion Summary 23

Source System 23

Approximate Volume 23

1.7.2.Legacy Data Extraction Process 24

Legacy Data Extraction Process 24

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. ) 24

[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). 24

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

Note: Please contact the Legacy Team Developer for the following items: 24

Batch Program 24

Legacy File Name 24

Target Name of Text file] 24

1.7.3.Risk Assessment 24

Data Quality Risk Assessment 24

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. 24

1.7.4.Data Cleansing Assessment 24

Data Cleansing Assessment 24

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

1.7.5.Data Validation Requirements 24

Data Validation Requirements 24

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

1.7.6.Manual Conversion Contingency 24

Is Manual Conversion Possible? If so please describe approach 24

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

1.7.7.Sequence of Conversion Activities (including dependencies) 25

Sequence of Conversion Activities 25

Please list step by step activities for performing the conversion from the extraction activity through SAP data validation. Please include all associated dependencies. 25

The following sequence will be followed for this conversion: 25

1. 25

2. 25

3. 25

1.7.8.Data Mapping Template 25

1.7.9.Control and Audit Requirements 25

Control/Audit Processing Requirements 25

25

2.TECHNICAL SPECIFICATION 26

2.1.General Object Overview 26

[Enter information about type of object, overall design] 26

2.2.Report / Interface/ Dialog Program Information 26

Program Information 26

Type of Program 26

(Report, Interface, Dialog Program) 26

Transaction code 26

Transaction Description 26

Program Name 26

Screen Number 26

What SAP transaction(s) do this involve? 26

Menu path for transaction(s) 26

Provide Selection - options & Parameters (if applicable) 26

Selection Option(s) Description 26

Field Name 26

Default (Mandatory, Value, etc.) 26

2.2.1.Screen validations/ Screen flow logic 27

2.2.2.Output layout 27

2.3.Class Information 27

Class Details (Interface Framework) 27

Class Name 27

Super Class Name 27

Global Attributes 27

Attribute Name 27

Type/Visibility 27

Default Value 27

Methods 27

Method Name 27

Description 27

Method Parameters (Name/Type/Visibility) 27

Flow Logic: 27

Flow Logic: 27

Flow Logic 27

Events 27

Event Name 27

Description 27

Event Parameters 27

Event Handler Method Name 27

2.4.Process Flow 28

Process Flow 28

2.5.Program Structure 28

Program Structure 28

2.6.Enhancements/User Exits 28

Object Definition 28

Object Type: 28

☐ SAP User Exit 28

☐ Function Exits 28

☐ Field Exit 28

☐ Menu Exit 28

☐ Screen Exit 28

☐ BADI 28

☐ Other: 28

2.7.Data Conversion 28

Object Definition 28

Conversion Method: 28

☐ LSMW 28

☐ ABAP Program 28

☐ Test Tool (eCATT, etc.) 28

☐ Other (specify): 28

Conversion Approach 29

Object Details 29

[Custom program will be outlined in section 2.1. For all other objects describe details of conversion methodology here.] 29

Data Mapping/Translation using the data mapping template outline in Section 1.7.8 29

Error Correction Mechanism 29

Audit Reporting 29

Error Reconciliation Process, if any 29

2.8.Forms 29

2.8.1.Type of Form 29

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

Form Name 29

Form Attributes 29

Page Properties 29

Page Layout (Windows and Logic) 29

Window Name: 29

Name of Element 29

Format Options 29

Logic 29

Window Name: 29

Name of Element 29

Format Options 29

Logic 29

Window Name: 29

Name of Element 29

Format Options 29

Logic 29

2.9.Custom Development 30

[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. 30

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. 30

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

Table Name 30

Short Text 30

Size Category 30

Table Maintenance Allowed 30

Data Class 30

Buffering 30

Table Maintenance Generation 30

Authorization Group 30

Field Name 30

Data Element 30

Domain 30

Type 30

Length 30

Check Table Field 30

Key Field 30

Foreign Key 30

Description 30

Comments 30

3.TESTING 31

3.1.Data Requirements 31

3.2.Unit Test Plan/Expected Results/Actual Results 32

3.3.Unit Test Follow-up Required 33

3.4.Functional Testing 33

3.4.1.Use Cases 33

[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] 33

3.4.2.Validation and Testing Scenarios 33

Directory: uploads -> FileLinks
uploads -> The Case Against the nypd’s Quota-Driven ‘Broken Windows’ Policing What Is It?
uploads -> For want of a nail
uploads -> Ownership Models There are two different types of ownership models
uploads -> Police Militarization
uploads -> City of rising star regular meting thursday, july 14, 2016
uploads -> Township of winfield
uploads -> Stop Militarizing Law Enforcement Act of 2014
uploads -> The Black Panther Party’s Ten-Point Program What We Want Now!
FileLinks -> Db levels of Some Recreational/Environmental Noises