Functional Specification
PROJECT IDENTIFICATION
Project Name
SANKALPA
Customer Name
KRISHNA TISSUE PVT LTD.
Project Manager Customer Project Manager
BISHWANATH MAITRA
Version Number: 1.1 Date: 22-Dec-2011
Page 1 of 7
Functional Specification KTPL_FS_MM_03
TABLE OF CONTENT
1.0 PURPOSE------------------------------------------------------------------------------3
2.0 ROLE-----------------------------------------------------------------------------------3
3.0 TEMPLATE FOR CAPTURING FUNCTIONAL SPECIFICATION---------3
3.1 HEADER----------------------------------------------------------------------3
SPECIFICATION NAME---------------------------------------------------------------------3
FUNCTIONAL MODE------------------------------------------------------------------------3
3.2 OBJECT VERSION HISTORY-------------------------------------------3
3.3 INPUT/HEADER/SUB-HEADING/OBJECT BODY-----------------4
3.3.1 Object Name: ---------------------------------------------------------------4
3.3.2 Heading: ----------------------------------------------------------------------4
3.3.3 Sub-heading (if any) --------------------------------------------------------4
3.4 Program Functions-----------------------------------------------------------4
3.4.1 Input fields--------------------------------------------------------------------4
3.4.2 Field information (for Object) ---------------------------------------------5
3.4.3 Field information (for Object) ---------------------------------------------7
3.5 Program logic-----------------------------------------------------------------8
3.6 Assumptions/Dependencies/Checks/Filters/Hard coded fields---------8
4.0 OPTIONS FOR PROGRAM(to be ticked)-----------------------------------------9
4.1 Output: A) List---------------------------------------------------------------9
4.2 Execution A) Foreground--------------------------------------------9
B) Background
4.3 Test Cases for unit testing -------------------------------------------------9
4.4 SAMPLE OBJECT (if any, to be mentioned) --------------------------10
5.0 PRODUCTION CHECK LIST-----------------------------------------------------10
1.0 Purpose
Page 2 of 7
Enhancement in Purchase Requisition Screen
2.0 Role
A new tab will shown in PR screen called “PO Details” item details, in this it will show the
last three PO details regarding particular material entered by user.
3.0 Template for capturing Functional specifications
3.1 Header
Specification Name KTPL_FS_MM_03
Specification number KTPL_FS_MM_03_V1.0
Specification date
Specification Type(Report/Module Enhancement
pool/Interface/BDC/SAP
script/Dictionary/Enhancement)
Functional Module MM
Priority(H/M/L) H
Functional Consultant Name SOUMYA & RITA
Technical Consultant Name
Functional / Technical Estimated Persons
days
For Modification, Name of current report /
Object
Golive Critical Yes
3.2 Object Version History
(To be filled in by the programer after the Development or Modification is completed)
Object Created / Modified New Version Previous Date of
Version Change
Program Name :
Development class :
Transaction code :
Completion date :
Actual Person Days :
Page 3 of 7
3.3 Input / Header / Sub-Heading / Object Body
3.3.1 Object Name: Enhancement in Purchase Requisition Screen
3.3.2 Heading: KTPL Production No Po Details
3.4 Program Functions
User Exit: MEREQ001
Function Module: EXIT_SAPLMEREQ_003/ EXIT_SAPLMEREQ_005
3.4.1 Input Fields
Input Fields Table Field Mandatory Default Values Selection Screen Notes
Reference Type(Single/Range)
(Y/N)
Y NA Range NA
3.4.2 Field Information (for Output)
Sequence Report Field SAP Table- Output Remark & Logic
Field Length
1. PO No EKPO- MARA-MATNR with EKPO-
EBELN MATNR And pick the EKPO-
Page 4 of 7
EBELN.
2. PO Date EKKO- Go to the table EKKO-
BEDAT BEDAT.
3. Net Price EKPO- MARA-MATNR with EKPO-
NETPR MATNR And pick the EKPO-
NETPR.
4. Vendor Name EKKO- Go to table EKKO-LIFNR.
LIFNR
3.5 Program logic:
When users put the material code from the PR screen then pick MARA-MATNR from there then link it
with EKPO-MATNR. With reference to EKPO – MATNR pick the EKPO – EBELN and then match it
with EKKO – EBELN. Pick the EKKO – BEDAT (purchase order date) with reference to EKKO –
EBELN. And then sort the EKKO - BEDAT in descending order. From there pick last 3 PO Date (EKKO
– BEDAT) and regarding this show the details of PO (PO No., PO Date, Net Price, Vendor Name).
3.6 Assumptions/Dependencies/Checks/Filters/Hard coded fields:
Assumptions : NA
Dependencies : NA
Checks : NA
Filters : NA
Hard coded fields: Applicable
4.0 Optional for program (to be ticked)
4.1 OUTPUT:
A) List
B) Grid Display
C) Interactive
D) Direct Download
4.2 EXECUTION:
A) Foreground
B) Back ground
4.3 Test Cases for Unit Testing (document attached separately)
Page 5 of 7
Identification type of test case as a separate section and give a brief description. Also specify the expected
and actual behavior and the status. The actual behavior and the status shall be filled during testing.
Test Case ID Test Case Expected Actual Behavior Status
Description Behavior
(Pass/Fail)
Note:To include test date/inputs the actual behavior and the status shall be filled while performing testing.
4.4 SAMPLE OBJECT (if any, to be mentioned)
5.0 Production checklist
Item Check Notes (Names of reports,
Transaction code etc.)
(Yes/No)
User sign off after Testing
Program documentaion done by ABAP
programmer
Authorization Profiles to which the
Transaction Code is to be attached
All components related to the
development released
Transaction Requested Number
generated
Test Case attached
Test results Dev/Qual/Prod(to be
attached)
Page 6 of 7
---------------------------------
Prepared by (Core Team)
--------------------------- --------------------------
Functional Consultant Technical Consultant
Page 7 of 7
