TS - W000 - Module SAP Workflow Technical Design
TS - W000 - Module SAP Workflow Technical Design
<Project Name>
Date: mm/dd/yyyy
Version: vx.x
Page 1 / 19
Revision History
Page 2 / 19
Template instructions
Text marked in blue needs to be deleted, as it contains instructions and guidance to the author only
Text marked in red is showing an example how to fill in the template and needs to be replaced by the
final content
Text marked in black (the rest of the document) needs to be kept as this provides the framework and
chapters of the template.
Page 3 / 19
TABLE OF CONTENTS
Page 4 / 19
7.2 Request Mechanism/Trigger ........................................................................................................... 13
7.3 Configuration (optional) ................................................................................................................... 13
7.4 Pseudo code .................................................................................................................................... 13
7.5 ABAP Development ......................................................................................................................... 13
7.5.1 Workflow ............................................................................................................................... 13
7.5.2 Dialog Program .................................................................................................................... 14
7.5.3 Custom Table Development ................................................................................................. 14
7.5.4 Table Validation Rules ......................................................................................................... 14
7.5.5 User Exit ............................................................................................................................... 15
7.5.6 Field Exit ............................................................................................................................... 15
7.5.7 Technical Design Constraints .............................................................................................. 15
7.5.8 Programmers Notes ............................................................................................................. 16
8 Testing Requirements .................................................................................................17
8.1 Key Unit/Assembly Test Conditions ................................................................................................ 17
9 Outstanding Issues .....................................................................................................18
10 Appendix ......................................................................................................................19
10.1 Glossary of Terms ........................................................................................................................... 19
10.2 Additional Supporting/Reference Documentation ........................................................................... 19
Page 5 / 19
1 Technical Design
Page 6 / 19
2 Sign-off Checklist
Use the following checklist to guide your completion of the Functional Design Document
Design
Has the report development technique been identified?
Has an example of existing RICEF object been included?
If the report is of type modification (custom development), has it been approved?
Have all areas of impact been identified?
Performance
Have the performance implications, metrics and targets been documented?
Has the performance and volume usage of the report development been considered?
Additional information
Has security been considered (e.g. authority checking considered, target group of users who should be
given access to the report etc)?
Are the test conditions sufficiently detailed to enable a full test of all required functionality?
Page 7 / 19
3 Document History
3.1 Revision History
The following have been nominated as quality reviewers for this Product:
Page 8 / 19
4 Development Overview
4.1 Requirements Summary
<< Provide a high-level description of the development requirement that will be addressed.>>
4.2 Assumptions
<< Describe any assumptions made in the process of completing this design. What functionality is expected of
configuration or other developments that pass information to this development and/or retrieve the information
processed by it (e.g., performance, triggers, exceptions, etc.)?>>
4.6 Standards
<< Detail any programming, error handling and archiving standards, which will be utilized in development of
the extension.>>
Page 9 / 19
5 Detailed Technical Specifications
5.1 Technical Flow Diagram
<<Insert a technical flow diagram depicting the extension procedure including screen sequences, any drill
down options, and navigation through the extension screens.>>
5.3 Workflow
< Provide detailed description for the workflow. e.g., purchase order approval process and authority levels
etc.>
Workflow
WRIC Description Business / Data Object (Sales Engaged Parties Owner
EF-ID Order)
XX-xx-
W001
[Please provide the details if any concerning the transaction or other batch programs that will trigger the
workflow]
[Please provide the details about any special condition that has to be met for the workflow to initiate ]
[Please provide the standard rules to which the workflow will abide by]
Page 10 / 19
[Please provide details about other rules for example Latest End, Latest Start, Requested End and Requested
Start]
5.12 Dependencies
<<Provide details of any dependencies for the extension to process correctly and perform at its
optimum.>>
Submission
Scheduling Considerations
Run Frequency
Start Date
Start Time
Estimated Volume Per Run
Parameters / File Dependencies
Job Dependencies
Constraints
Variant Required
o Field Text
o Suggested Value
o Description
5.18 Other
Page 11 / 19
6 Technical Requirements
6.1 Database Tables
<<Detail all database tables that will be accessed.>>
6.5 Program ID
<<Name of Development ID to be defined .>>
6.7 Module
<<Name of relevant module of report .>>
Page 12 / 19
7 Detailed Design
7.1 SAP Objects
<<List the program name, function module, transactions, etc. created for this development (e.g.,
workflow, business object, and standard task).>>
INITIALIZATION.
START-OF-SELECTION.
END-OF-SELECTION.
SELECTION-SCREEN-VALIDATION
TOP-OF-PAGE.
END-OF-PAGE.
AT USER-COMMAND.
AT LINE-SELECTION. (Point at the user selects a line)
TOP-OF-PAGE DURING LINE-SELECTION. (top-of-page for 2ndary lists)
AT PFNN. (Point at which the user presses the function key with the function code PFnn key with the
function code PFnn.)
(Add other events as required)
7.5.1 Workflow
<<Include a high-level description of the program broken down into relevant sections depending
on development type being used. Use pseudo code to explain each step in detail.>>
Import Parameters
Page 13 / 19
Export Parameters
Container Elements
Transactions Called
Exception Conditions
Workflow Task Breakdown
INITIALIZATION.
START-OF-SELECTION.
END-OF-SELECTION.
SELECTION-SCREEN-VALIDATION
SCREEN NO. XXXX
Detail the field definition used in the development. The following table is the table definition for the
table ZBT001.
Prior to Update
Page 14 / 19
A check is performed in Form chk_chged_sip_data_reset to see if the user has updated an
existing Dateto, on the table. If they have an information message (Message Class ZDA -
Message number 015) is output. Text of the message is as follows:
‘You are not allowed alter the entries in table ZBT001 using this method ’.]
Cardinality[Detail the dictionary objects used in the table development if necessary. Ensure
adherence to the development standards see document TD.SD ABAP Coding Standards]
Maintenance Strategy
Page 15 / 19
7.5.8 Programmers Notes
Page 16 / 19
8 Testing Requirements
8.1 Key Unit/Assembly Test Conditions
Unit Testing.xls
Page 17 / 19
9 Outstanding Issues
Page 18 / 19
10 Appendix
10.1 Glossary of Terms
Term Definition
Page 19 / 19