Functional and Technical Design

Specification

FTDS-Release Audit Report

Prepared by: SD Team

Document Information

Document Name: FTDS_Release Audit Report

Document
Author/Owner:
Author/Owner Contact
Info
Electronic Location:

Document Revision History

Document Revision Date Author Revision Description

Version #

1.0 11/11/2013 Initial Version

Functional Specification Acceptance Sign-off

Role: Name: Signature/Electronic Reference Date

Business Process
Owner/ Requestor
Functional Team
Lead
Technical Lead
PMO

Table of Contents

FTDS_SD_R_221_Release Audit Report Page 2 of 25

1 Attributes ............................................................................................................................................... 5
2 Business Requirements ....................................................................................................................... 6
2.1 Overview ......................................................................................................................................... 6
2.2 Business Users (requested by) ...................................................................................................... 6
2.3 Benefits / Alternatives/ Assumptions .............................................................................................. 6
2.4 Comments ...................................................................................................................................... 6
2.5 Related Documents (Ref BPDD No.) ............................................................................................ 6
3 Functional Specifications .................................................................................................................... 7
3.1 Functional Design ........................................................................................................................... 7
3.1.1 Reference the existing WRICEF ......................................................................................... 7
3.1.2 Real Time / Batch / FTP and Frequency............................................................................. 8
3.1.3 Dependencies ..................................................................................................................... 8
3.1.4 Classification of Object Development ................................................................................. 8
3.1.4.1 Reports and Forms ............................................................................................................... 8
3.1.4.2 Interfaces .............................................................................................................................. 9
3.1.4.3 Conversions .......................................................................................................................... 9
3.1.4.4 Enhancement ....................................................................................................................... 9
3.1.4.5 Workflows ............................................................................................................................. 9
3.1.4.6 WebDynpros ......................................................................... Error! Bookmark not defined.
3.1.5 Field Validations .................................................................................................................. 9
3.1.6 Data Sources and Selection Criteria ................................................................................... 9
3.1.7 Logic Flow / Processing Required .................................................................................... 10
3.1.8 Calculations / Formulae against the fields if required ...................................................... 10
3.1.9 Sort/Control and Report Totals ......................................................................................... 10
3.1.10 Output Fields/ Report Layout ............................................................................................ 10
3.1.11 Interactive Report/Drilldown Processing ........................................................................... 10
3.1.12 Data Volume ..................................................................................................................... 10
3.1.13 Error Handling ................................................................................................................... 10
3.1.14 Security – .......................................................................................................................... 10
3.1.15 Comments ......................................................................................................................... 10
4 Business Requirements Testing ....................................................................................................... 11
5 Technical Documentation .................................................................................................................. 12
5.1 Documentation of the Development Objects ................................................................................ 12
5.1.1 Overall Design Strategy .................................................................................................... 12
5.1.2 Performance Considerations ............................................................................................ 12
5.1.3 Recovery Procedures........................................................................................................ 12
5.1.4 Special Considerations / Exceptions ................................................................................. 12
5.1.5 Set up / Operating Procedures ......................................................................................... 12
5.1.6 General Program Objects Created ................................................................................... 12
5.1.7 SAP Objects Modified ....................................................................................................... 13
5.1.8 New Development Object Attributes ................................................................................. 13
6 Technical Documentation - Report ................................................................................................... 14
[Appendix A refers to the objects which won’t be used regularly. If the type of application is not listed
here, check the appendix A and update the required information.] ...................................................... 14
6.1 Documentation of Report .............................................................................................................. 14
6.1.1 Report Overview ............................................................................................................... 14
6.1.2 Selection Screen ............................................................................................................... 14
6.1.3 Data Selection ................................................................................................................... 14
6.1.4 Screen Flow ...................................................................................................................... 15
6.2 Technical Assumptions ................................................................................................................. 15
6.3 Function Group and Modules ....................................................................................................... 15
6.4 Data Dictionary Objects ................................................................................................................ 16
6.5 FORMS ......................................................................................................................................... 17

FTDS_SD_R_221_Release Audit Report Page 3 of 25

 6.6 Message Types ............................................................................................................................ 17
6.7 Message Class and Texts ............................................................................................................ 17
6.8 Pseudo Code ................................................................................................................................ 18
Program Structure ......................................................................................................................... 18
7 Error Handling, Security. ................................................................................................................... 20
7.1 Documentation of Error Handling, Security. ................................................................................. 20
7.1.1 Error Handling ................................................................................................................... 20
7.1.2 Security ............................................................................................................................. 20
8 Development Unit Testing (please include the negative test cases also) .................................... 21
9 Post Production Modifications.......................................................................................................... 22
9.1 <Date of Change> – Change Request 9999 <brief description> ................................................. 22
Appendix A Object Templates ................................................................................................................. 23

FTDS_SD_R_221_Release Audit Report Page 4 of 25

1 Attributes
The attributes should be taken from the final WRICEF list. This section serves as a summary. Checkmark
the appropriate WRICEF object attributes:

System(s) ECC 6.0 EP 7.0

Impacted BI 7.0 Other: _________________
Program type: Conversion Interface Report
Enhancement Form Workflow
EDI Other – R/3 Dev Legacy / Bolt-On
Priority High/Mandatory Medium/Recommended Low/Optional
Complexity Low (<2wks) Medium (3-5wks) High (6-8wks) Very High (>9wks)
ROM Rough Order of Magnitude = ______ days

[Type here]
2 Business Requirements
2.1 Overview
There is a need for a “Release Audit Report”. The report whould show how the data was maintained in a
Sales Scheduling Agreements and Customer Orders. Updated by EDI, Manully maintained by a user,
etc.

The out put of this report can be generated for a given date range, sales organization, distribution channel
and sales documents( Sales scheduling agreements, customer orders).

2.2 Business Users (requested by)

Plant Controller, Materials Manager

2.3 Benefits / Alternatives/ Assumptions

List out any maintenance to Scheduling Agreements and Sales Orders showing the before image and the
after image and by who and when the document was maintained.

2.4 Comments

The input date field will be a mandatory entry.

2.5 Related Documents (Ref BPDD No.

[Type here]
3 Functional Specifications
3.1 Functional Design

A new report will be developed for this requirement.

The report will have a transaction code that can be executed to generate the report.

This report will have the following fields as input fields.

1) Sales Organisation ( optional entry with single value)

2) Distribution Channel ( optional entry with multiple value)

3) Sales scheduling agreement/ customer order number ( optional entry with multiple value)

4) Sales scheduling agreement/ customer order date ( Mandatory entry with date range)

When directly the list of sales document (Sales scheduling agreement/ customer order) numbers were
given in the input then date field will not be a mandatory field.

The output of this report generates the following data

1) Sales scheduling agreement/ customer order numbers

2) Sales scheduling agreement/ customer order date

3) Changed by ( EDI or Manual)

4) Release type ( whether order or Forecast dly schedule or JIT dly schedule etc)

The output of this report can be downloaded in to an excel file.

3.1.1 Reference the existing WRICEF

The format for this report is defined in the excel spread sheet below.

FTDS_221_Audit
release report.xlsx

table 3-1
If T Code exist, please specify below.

[Type here]
 Transaction Code (Existing Report Name New Transaction Code
Report)

Audit release report TBD

3.1.2 Real Time / Batch / FTP and Frequency

This report would be run on demand as required.

3.1.3 Dependencies

none

3.1.4 Classification of Object Development

3.1.4.1 Reports and Forms

1. See Excel Spreadsheet in section 3.1.1 for the layout.

2. 8.5 X 11 portrait

Sample Table 3-2

Field Title Type* Size Mandatory Wild Range SAP Source Field
Cards? Required?

Sales agreement/ N 10 Y VBLB-VBELN

Customer order
number See logic below
Sales agreement/ D Y VBLB-ABRDT
Customer order date
Changed by C 10 Y Check the value in
VBLB-DOCNUM. If it is
blank then display
“MANUAL”. If not blank
display as “ EDI”.
Release type C Y Pick the value from
VBLB-ABART and
display here.

Type*
A Alpha only X Checkbox
N Numeric R Radio Button
C Alphanumeric D Date
T Time
LOGIC

Input Scenario 1:

[Type here]
If in the input “Sales organization” and “date” were given – first pass date value to VBLB – ABRDT and get
the list of VBLB-VBELN. Then pass the VBLB – VBELN value to VBAK-VBELN and also pass the sales org
value in to VBAK-VKORG. Display the resultant list.

Input Scenario 2:

If in the input “Sales organization”, “Distribution channel” and “date” were given – first pass date value to
VBLB – ABRDT and get the list of VBLB-VBELN. Then pass the VBLB – VBELN value to VBAK-VBELN
and also pass the sales org value to VBAK-VKORG and distribution channel value to VBAK-VTWEG.
Display the resultant list.

Input scenario 3:

If in the input “date” was given – first pass date value to VBLB – ABRDT and get the list of VBLB-VBELN
and other values as given in the excel sheet.

Input Scenario 4:

If in the input “SA/SO number” alone was given then pass them to VBLB – VBELN and all the other values
as given in the excel sheet.
Make the date field non mandatory for this scenario.

3.1.4.2 Interfaces

3.1.4.3 Conversions

3.1.4.4 Enhancement

3.1.4.5 Workflows

3.1.4.6 Forms

3.1.5 Field Validations

Date field should accept only date entry

3.1.6 Data Sources and Selection Criteria

Refer the excel spread sheet in section 3.1.1

[Type here]
3.1.7 Logic Flow / Processing Required

Ref.the functional Design above

3.1.8 Calculations / Formulae against the fields if required

N/A

3.1.9 Sort/Control and Report Totals

3.1.10 Output Fields/ Report Layout

Refer the excel spread sheet in section 3.1.1

3.1.11 Interactive Report/Drilldown Processing

N/A

3.1.12 Data Volume

While there is no upper limit set for the no of records to be handled by this report, it is better to process
the report for a year or few years.

3.1.13 Error Handling

N/A

3.1.14 Security –

N/A

3.1.15 Comments

N/A

[Type here]
4 Business Requirements Testing
Detail the specific business scenarios that should be tested as a part of this Development. Detail what the
expected result of each scenario is.

Business Test Scenario Expected Result

Test the report for a given sales organization and date

range
Test the report for a given distribution channel and date
range

Test the report for a given list of document ( sales

scheduleing and customer order) numbers
Test the report for a given date ( delivery schedule
date) range.
Test the report for a combination of Sales organization
and distribution channel

[Type here]
5 Technical Documentation
5.1 Documentation of the Development Objects
5.1.1 Overall Design Strategy

If required, describe the overall design strategy. This is required for more complex
developments. If this section is not required as the development is a simple one, delete
the section.

5.1.2 Performance Considerations

Note here anything that may impact on the performance of the program or which is
relevant to performance in general. If a particular option to improve performance was
considered, yet proved ineffective, describe this here. This will ensure that other
programmers do not waste time going down the same track at a later date. Use the
runtime analysis and SQL trace features of SAP to check and compare the performance of
the program.

5.1.3 Recovery Procedures

This section MUST be completed. It is most important for any programs that update SAP.
Outline the procedure that must be followed in the even of program failure {Example:
what happens if the program terminates or is cancelled midway through?}. Recovery
Procedures must also be added to on-line documentation. If the program is just a report,
simple state that “This program is only a report and can be cancelled during processing if
required”

5.1.4 Special Considerations / Exceptions

List anything that should be taken into consideration when executing this program. Eg.
report cannot be run in background, screen size must be set to a special size, hard
coding of values etc.

5.1.5 Set up / Operating Procedures

Describe how the development should be run. Describe any procedures that must be
completed before running the program and any general cautions and warnings that apply
to the task.

5.1.6 General Program Objects Created

Document all objects that you created for this Development. If the SAP Object type is not
included in the table below, add in a new row. Some additional objects that may need to
be added include Searchhelps, Lock Objects, Enhancement Project Names, Number
Ranges, GUI Titles, Parameter ID’s, Data Elements and Domains. To obtain a complete
list of the objects you created, look in the object list of the transport.

[Type here]
 SAP Objects Name Description

Programs
Include Files
Functions
Layout Set
Menus
Transaction Code
Tables
Structures
View
Authorization
Object Used

5.1.7 SAP Objects Modified

General Information Description

Object Name
Object Type
Object Description
Purpose
Description of Change
Add additional entries depending on the
object created

5.1.8 New Development Object Attributes

Data Descriptions: Describe the attributes of programming objects such as reports, functions, and ABAP OO, etc.
and attributes of data dictionary objects such as tables, structures, domains, data elements, etc. and changes to the
existing repository objects. If you have multiple objects of one type than copy the appropriate table as many times as
needed.

Please refer to the object templates in the Object Templates for Programs, Forms, Transactions,
Screens, GUI Title, Screen Status, Function Group, Function Module, ABAP Class, ABAP Method,
Message Class, LSMW, Tables and Structures, Views, Domains, Data Elements, Lock Objects,
Search Helps, and many other objects.

[Type here]
6 Technical Documentation - Report
[Appendix A refers to the objects which won’t be used regularly. If the type of application is not listed here,
check the appendix A and update the required information.]

6.1 Documentation of Report

6.1.1 Report Overview

REPORT SECTION:

For Report Only

Provide all requested information and check all attributes that apply

Name of Report:
Assigned Transaction:
Interactive Report: Yes No
Report Layout: No Yes – Filename:______________
Run Mode: Foreground Background Both
The report will be created via: Report Painter Report Writer ALV
ABAP Program Info System Other: __________

Data Volume (Records): Date test data is to become available:

6.1.2 Selection Screen

Selection Screen: Describe the selection screen of the program. Specify fields for selection and what
checks are needed after the user has entered their criteria

Screen Name/Number
Select Options / Field name Default Values Validation
Parameters / Radio From – To (Required / Optional)
Buttons/ Check Boxes

Note: All the selection screen fields should be checked against the check tables where exist. Also, make
sure if it has F1 help. If not, make sure to verify with Functional team if any process on help required.

6.1.3 Data Selection

Data Selection: Identify the data the report should select only. Remaining pseudo code should be
written in section 6.1.6 Include tables, join conditions, etc.

[Type here]
 6.1.4 Screen Flow

Screens and Screen Flow: Describe the screens and the screen flow. Insert screen prints and flow of
screens, if applicable. This is important when you have an interactive report that allows you to see the
report from different angles and different hierarchy levels.

6.2 Technical Assumptions

1.3 Technical Assumptions: Describe special issues and assumptions, which might impact the overall
design or implementation of the software. Include any business product line considerations that will
impact the manner in which the software is to be designed, implemented or tested.

6.3 Function Group and Modules

This should be 6.2

Function Group Attributes: Provide relevant attributes for function group

Name
Description
Development Package

Function Module Attributes: Provide relevant attributes for the function module

Name
Function Group
Description
Processing Type
Update mode (if
applicable)
Import Parameters: Provide the required attributes for function’s import parameters. Insert more lines into table
when needed
Parameter Typing Associated Default Optional Pass Description
Name. Type Value (Y/N) Value
(Y/N)

[Type here]
 Note: Specify the parameters starting “im_” “ex_”, “t_” for import, export and tables parameters.
BADIs or Enhancements

OO ABAP ClassUserExit Attributes: Provide relevant attributes for the OO ABAP Class/Interface

Name
Description
Development Package
Interface Yes No
Instantiation
Class Type
Final Yes No
Only Modeled? Yes No
Super Class
Interface: Provide the required attributes for class interface definitions. Insert more lines into table when
needed
Interface Abstract Final Modeled Description
(Y/N) (Y/N) only
(Y/N)

Enhancements: Provide the required information for User Exits.

Enhancement Function Type Project Description
Module

6.4 Data Dictionary Objects

Table/Structure Attributes:

Name:
Short Text:
Type Transparent Pooled Cluster
Structure APPEND CI Customer include
Development Package
Delivery Class:
Table Maintenance:
Data Class:
Size:
Buffering:
Table Locking:

[Type here]
 Authorization Group:
Tables and Structures Fields: Provide all fields that are new, changed, or deleted. Highlight the key fields and
provide information if the field has been added, changed or deleted
Table/Structure: Expected Size:

Field Name Data Element Domain Description (Change, Add,

Delete, Key, etc)

6.5 FORMS

Form Attributes: Provide relevant attributes based on form type

Name
Description
Development Package
Page Format: DIN A4 Letter Other ________________
Languages English French Other ________________

6.6 Message Types

OO ABAP ClassUserExit Attributes: Provide relevant attributes for the OO ABAP Class/Interface

Name
Description
Development Package

6.7 Message Class and Texts

Message Class Attributes: Provide relevant attributes for the message class

Message Type
Idoc Type
enhancement of
segments
Inbound/Outbound
Partner Type
Receiving & Sending
System
Process Code

[Type here]
 Change Pointers (if
applied any)
Customer Distribution
Model
Filters (if created any)
Specify the field &value

6.8 Pseudo Code

Program Structure

Program Structure and processing pseudo-code (if required): Describe the program structure and how
it selects, processes, and outputs the data. (Add additional rows to table if text becomes too long or to
separate different development objects)

Run Procedure: Describe how to run the applicatio such as which transaction to call, which variant to
use, special considerations for the selection screen, etc.

[Type here]
 Restart Procedure: Describe how to restart the application in case it fails to run successfully

[Type here]
7 Error Handling, Security.
7.1 Documentation of Error Handling, Security.
7.1.1 Error Handling

Error Handling: Describe the scenarios where processing errors can occur and how they should be
handled

7.1.2 Security

Security Details: Describe processing required to address Security Requirements defined in the
Functional Specification.

[Type here]
8 Development Unit Testing (please include the negative test cases also)

Test Scenario Description Expected Result Pass / Comments

Fail

[Type here]
9 Post Production Modifications
9.1 <Date of Change> – Change Request 9999 <brief description>

Client Contact: <Name of person who requested the change.>

Provide details of exactly what the change was and how it affects the program.

[Type here]
Appendix A Object Templates

Program Attributes: Provide relevant program attributes

Name
Description
Logical Database
Development Package
Editor Lock Yes No
Start using variant; Yes No
Fixed Point Arithmetic: Yes No
Unicode Yes No
HR Report Category Master Data ____________________ Master data rep. class
(if applicable) or
Payroll Cluster ____________________ Payroll report category

Transaction Attributes: Provide relevant attributes based on transaction type

Name
Description
Development Package
Type
Program/Transaction
Screen Number
Variant
Class
Method
Update mode
Classification
GUI Support
Default Values
Describe other attributes

Screen Attributes: (Provide a description of each screen include fields, possible User actions and any
Processing that should happen)

Program Name
Description
Development Package
Screen Type
Field Definition:
Screen Field Type(Field, Field Format Input List of Possible Validation
No. Name Push Button, Text Masks Values and Error
Context Actions
Or Table Control) Sensitive Help

[Type here]
 Screen Logic PBO Provide the modules needed for the process before output. Do not provide the coding here,
but the steps that need to be performed such as “Set GUI STATUS and TITLE, Initialize Data, etc.

Screen Logic PAI Provide the modules needed for the process after input. Do not provide the coding here, but
the steps that need to be performed such as “Verify Input, Process OK-Code, etc.

Screen GUI Title: Provide relevant GUI Title attributes for the screen

Program Name
Title Code
Description

Screen Status: Provide relevant attributes for Screen Status

Program Name
Status Name
Description
Status Type
Menu Bar: Provide the menu list and sub-menu with the corresponding menu items. If for a menu item you
have a sub-menu, then write first the main menu, then sub-menu and as function code write “SUB”. For the sub-
menu write the sub-menu, then the menu item, and then the function code representing the menu item
Menu/Sub-menu Sub-menu/Menu Function Code Description
Item

Application Toolbar: Provide the required attributes for application toolbar items. Insert more lines into table
when needed
Item Number Function Code Description

Function Keys: Provide the required attributes for application toolbar items
Function Key Function Code Description

LSMW Attributes: Provide relevant attributes for the LSMW

Name
Description

Lock Object Attributes: Provide relevant attributes for the lock object

Name

[Type here]
 Description
Development Package
Primary Table:
Primary Lock Mode
Secondary Lock Tables: Provide information about secondary tables
Name Lock Mode

Lock Parameters: Provide information about the lock parameters

Lock Parameter wanted Lock Parameter Name Table Field

Search Help Attributes: Provide relevant attributes for the search help

Name
Description

[Type here]