Title: dealer wise SO

Status
Development ID
Number:
Type:
Module : PP
Sub-module
Criticality
Frequency of
:execution
Data Volume
Process Team Owner:
Technical Team
Owner:
Issue Date:
Status:

Document Control
Change
No.

Rev. No. inc.

change

Originator
of change

Date of
change

Description of change

Tested and Approved by:

Name of Business
Process Owner

Turanya Functional Specification

Sign of

Core Team Member

1 of 3

Sign of

22-Dec-15

Program Information

1.
1.1.

Description: Predefined requirements

(If any)
Program Title:
Program Name:
Transaction
Code:
Message Class:
Program Type:
Authorization
Group:
Menu Path
Layout Name
Font / Layout
type / etc.
1.2.

Input / Dependencies (If Any)

1.3.
1.4.
1.5.

Required Functionality
Donor / Target System details / requirements (Interface only)
Donor / Target System data volume / frequency. (Interface only)

1.6.
Security / Authorization requirements.
1.7.
Execution parameters.
1.8.
Detailed Requirements Program LogicAdditional Comments /
Requirements / Notes

1.9.

Table / File data used / produced.

Turanya Functional Specification

2 of 3

22-Dec-15

4. Input

5. Output
Output

1.

Test Scenarios

2.

Technical Specifications

Turanya Functional Specification

3 of 3

22-Dec-15