Professional Documents
Culture Documents
Specification
Table of Contents
[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.4 Comments
[Type here]
3 Functional Specifications
3.1 Functional Design
The report will have a transaction code that can be executed to generate the report.
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.
4) Release type ( whether order or Forecast dly schedule or JIT dly schedule etc)
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)
3.1.3 Dependencies
none
Field Title Type* Size Mandatory Wild Range SAP Source Field
Cards? Required?
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
[Type here]
3.1.7 Logic Flow / Processing Required
N/A
N/A
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.
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.
[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.
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.
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”
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.
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.
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
Object Name
Object Type
Object Description
Purpose
Description of Change
Add additional entries depending on the
object created
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.]
REPORT SECTION:
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: __________
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.
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.
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.
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)
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:
6.5 FORMS
Name
Description
Development Package
Page Format: DIN A4 Letter Other ________________
Languages English French Other ________________
OO ABAP ClassUserExit Attributes: Provide relevant attributes for the OO ABAP Class/Interface
Name
Description
Development Package
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
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)
[Type here]
9 Post Production Modifications
9.1 <Date of Change> – Change Request 9999 <brief description>
Provide details of exactly what the change was and how it affects the program.
[Type here]
Appendix A Object Templates
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
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
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
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
Search Help Attributes: Provide relevant attributes for the search help
Name
Description
[Type here]