You are on page 1of 7

Technical Specification Document

AATP report should cover the records where the capacity is reserved at customer level through CRP.

Author: Akanksha Jain

Version: 1.0

Date: 4-Jan-2011

Document History

Version Date Modifications Prepared by / Revised by


1.0 4-Jan-2011 Draft Akanksha Jain

Contents
1 Introduction.........................................................................................................................................4
2 System Features..................................................................................................................................4
<Project Name> Technical Specification Document

2.1 Feature Statement 1....................................................................................................................4


2.2 Feature Statement 2....................................................................................................................4
3 Non-Functional Requirement..............................................................................................................5
3.1 Overview......................................................................................................................................5
3.2 Reliability.....................................................................................................................................5
3.3 Availability...................................................................................................................................5
3.4 Security........................................................................................................................................5
3.5 Maintainability.............................................................................................................................5
3.6 Portability....................................................................................................................................5
3.7 User Documentation....................................................................................................................6
3.8 Data Migration.............................................................................................................................6
3.9 Performance Requirements.........................................................................................................6
3.10 Safety Requirements...................................................................................................................6
3.11 Security Requirements.................................................................................................................6
3.12 System Capacity and Scalability Requirement.............................................................................6
3.13 Disaster Recovery Requirements.................................................................................................6
3.14 Failover Requirements.................................................................................................................7
4 External Interface Requirements.........................................................................................................7
4.1 User Interface Requirements.......................................................................................................7
4.2 Hardware Interface Requirements..............................................................................................7
4.3 Software interface Requirements................................................................................................7
4.4 Communication interfaces...........................................................................................................7
5 As-Is Process Definition.......................................................................................................................7
6 Functional dependencies.....................................................................................................................7
6.1 Logical Data Model......................................................................................................................7
6.2 Data Structure.............................................................................................................................7
6.3 Format of Data Structure.............................................................................................................7
6.4 Common Routines with brief explanation...................................................................................7
6.5 Input Formats..............................................................................................................................7
6.6 Validations...................................................................................................................................8
6.7 Output Formats...........................................................................................................................8

Page | 2
<Project Name> Technical Specification Document

6.8 Function Key Standards...............................................................................................................8


6.9 Event Flow...................................................................................................................................8
6.9.1 <Event Flow Name>.............................................................................................................8
6.10 Architecture Diagram...................................................................................................................9
6.11 Transaction Mapping...................................................................................................................9
6.12 Business Rules..............................................................................................................................9
6.13 Schemas.......................................................................................................................................9
6.14 Data Mapping............................................................................................................................10

Page | 3
<Project Name> Technical Specification Document

1 Introduction
This requirement is to prepare the report which shows the DM forecast, NET forecast, and SPP plan
at customer, PI and month level for both DM and PM modules.

2 System Features
1. The following two new tables need to be modified in PM.
 M_T_SLS_ALLOCS_EXRACT
 M_T_SLS_ALLOCS_LOAD

3 Non-Functional Requirement
3.1 Overview
N/A

3.2 Reliability
N/A

3.3 Availability
N/A

3.4 Security
N/A

3.5 Maintainability
N/A

3.6 Portability
N/A

3.7 User Documentation


N/A

3.8 Data Migration


N/A

3.9 Performance Requirements


State specific performance requirements for various system operations, like, specify number of
transactions per second to be supported, response times, computational accuracy and timing
relationships of real time systems. Memory and disk space requirements, concurrent user loads, or the

Page | 4
<Project Name> Technical Specification Document

maximum number of rows stored in the database tables could also be possible examples to be specified
here.

Activity/Transaction Response Time

mapping execution time < 2 minutes

3.10 Safety Requirements


N/A

3.11 Security Requirements


N/A

3.12 System Capacity and Scalability Requirement


N/A

3.13 Disaster Recovery Requirements


N/A

3.14 Failover Requirements


N/A

4 External Interface Requirements


N/A

4.1 User Interface Requirements


N/A

4.2 Hardware Interface Requirements


N/A

4.3 Software interface Requirements


N/A

4.4 Communication interfaces


N/A

Page | 5
<Project Name> Technical Specification Document

5 As-Is Process Definition

6 Functional dependencies
6.1 Logical Data Model

6.2 Data Structure

6.3 Format of Data Structure

6.4 Common Routines with brief explanation


DM:
 M_T_SLS_ALLOCS_EXRACT
Steps: The data is extracted from the salesprodalloc table of the order promising where
engine_id=0. The same data is then pulled in load table enabling the start schema functionality.

6.5 Input Formats


N/A

6.6 Validations
N/A

6.7 Output Formats


N/A

6.8 Function Key Standards


N/A

6.9 Event Flow


N/A

6.9.1 <Event Flow Name>


N/A

6.10 Architecture Diagram


N/A

6.11 Transaction Mapping

6.12 Business Rules


 M_T_SLS_ALLOCS_EXRACT
The following business rules need to be modified for this mapping:

Page | 6
<Project Name> Technical Specification Document

Mapping Name Field Name Transformation Description

M_T_SLS_ALLOCS_E TR_ROUTER_SALES_PROD Group 2(Domestic) the


XTRACT _ALLOC following condition should
be there:
(SAELSCHANNEL='Dome
stic' OR
SAELSCHANNEL='Servic
eCenter')and
SALESLEVEL != 'L3'

And Group
4(Domestic_L4):
(SAELSCHANNEL='Dome
stic' OR
SAELSCHANNEL='Servic
eCenter') and
SALESLEVEL='L4'

6.13 Schemas

6.14 Data Mapping

Page | 7

You might also like