Functional Specification

Functional specification
Version: Issue Date
(dd/mm/yyyy):
Specification No
Development No In Preparation Review

(To be filled by Technical Department) Approved Released

Revision History
Version Date Description of changes
To add one more field in purchase order printing source
inspection date at vendor end.
Responsible
For concept For Implementation

Section I: Justification
To add one more field in purchase order print source inspection date at vendor end
This is taken from QM module QI01 quality info record. Source inspection type and lead time days.
Delivery date in purchase order (MEPO1320_EEIND – QINF_VORLABN) = Source inspection Date
printed in Purchase order print.

Area ( Module): MM Date

(dd/mm/yyyy):

Requested by: Anandhakumar

Brief description: To add one more field (Inspection date at your end)

Program type: (select Conversion Batch Interface Online Interface Report

the check box)
Form Enhancement Extension Dialog

Modification Unknown Others BAPI

ALE/ IDOC Application Development

Charateristics Drill Down ALV Others (pl specify)

Priority: High/mandatory Medium/recommended Low/optional

Functional_specifications[1].doc Page 1 of 6
 Functional Specification

Only for Interfaces:

Type of interface: Real-Time Batch

Direction of interface: Inbound Outbound Both

Frequency: Daily Weekly Monthly

Biweekly Other: Ad-hoc

Only for Reports:

1. The report will be created via: Report Painter Report Writer ABAP Query

ABAP Program Info System

2. Requested characteristics: Drill-down Pushbuttons Sort

3. Praposed execution is Entry files Others:

online/background

4. Any Authority checks are required

5. If any LDB is available? if yes,

which screen to use

Sign off – Functional Specification

Prepared By Comments

Date

Team Lead Lead Consultant

Date Date
Approved Integration Manager / /
Approved by Project Management Team / /
(in case of Application development)

Received Team Lead/ Lead Consultant

Date / /

Section II: (a) Business Requirement (Please use this section for describing the business
requirement in detial preferably with flow diagram)

Functional_specifications[1].doc Page 2 of 6
 Functional Specification

I General Definition:
In purchase order printing some material have source inspection at supplier end. This is not
maintained in purchase order. Now we want to print the source inspection date in purchase order print
for India only with output type NEU. Calculation is delivery date – source inspection lead days = source
inspection Date at vendor end. For material type ROH and HALB
II Integrative
III Prerequisites/ master data
IV Processes, process-steps and flows

V Other Business related requirements

VI Reporting
VII User Interface
VIII Others
IX Other requirements
X Data security requirements
XI Performance requirements
XII Environmental requirements
XIII Architectural requirements
XIV Authorization requirements Authorization by the Transaction code, Company Code, Plant should be
provided.
Graphical representation (detailed flow chart)

(b) Detailed Functional Description Concept – Operational Requirements (describe in

detail)

Process Logic : The detailed Process Logic is given in Annexure

For Conversion
Tables
involved:

Functional_specifications[1].doc Page 3 of 6
 Functional Specification

For Interface
Fields Required From Source System:

Field Description Field Name in Source System Data Type

Fields Required From Traget System:

Field Description Field Name in Target System Data Type

Data Mapping:

Field Name in Source System Field Name in Target System

Validation:

Procession Logic:

Error Handling Requirements:

Functional_specifications[1].doc Page 4 of 6
 Functional Specification

SAP Input Screen (Data Mapping)

Transaction:

Screen R/3 Screen field Legacy field Remarks

number name

Online

Tables
involved:

Consistency checks that must be done:

Item Screen Field Description

1.
2.

Functional_specifications[1].doc Page 5 of 6
 Functional Specification

Forms
Tables
involved:

Design of desired form – Layout set:

Specify the default layout set if available

Specify page format

Standard Form Model:

Attach copy of existing form as sample. Explain here the detail requirement for Laout viz. usage/ data
volume/ Can it be standardise etc

If this form is a copy of a standard form or if there is a model in the legacy system, please include the
copy here. Include also the name of the standard form and path/transaction where it is in the SAP
System.

Desired output:
Give a pictorial view of the desired output

Enhancement:
Specify the available enhancement name, customizing path and details about what must be done. Please
ensure all customization done w.r.t. testing

Functional_specifications[1].doc Page 6 of 6