Functional Specification (Purchase Requistion)
Chase
PROJECT IDENTIFICATION
Project Name CPI/Project Number Project Type
(CBI, Implementation, CSS, Upgrade, Internal, other)
EKALABYA Implementation
Customer Name Customer Number Planned Start/Finish
SAP Customer Partner Project Sponsor Program Manager
DR. ACHYUTA SAMANTA PROFF. NIHAR BUERA
SAP Project Manager Customer Project Manager Partner Project Manager
SUSANTA PATRO RATNA KABIRAJ
How to use the Template
This document is intended to specify RICEFW object from a functional perspective. It will be followed by a technical
specification during Realization. A Functional Specification has three main sections
General Object information, to be filled in for all RICEFW objects
Object specific details
Test conditions and considerations
This document builds and refers to two preceding documents
Requirements - BPR
Solution design – BPD
In addition, all RICEFW object are consolidated in the RICEFW list
[Please note: The project manager and the quality manager have to revise this template before it is used for the project
and especially before it is given to the customer. Sometimes instructions, guidelines, explanations, hints, and tips are
provided. It should always be removed from the template for the project.
Top-level chapters may not be deleted or inserted; required additions should be made as sub-chapters to existing
chapters to provide a consistent representation of this document to the customer. ]
TABLE OF CONTENTS
How to use the Template.................................................................................................................1
General Object Overview................................................................................................................ 3
Process Requirements Reference.....................................................................................................4
Generic WRICEF Descriptions.......................................................................................................... 4
Object Specific Design....................................................................................................................6
Forms / Output................................................................................................................................... 6
Test Conditions................................................................................................................................8
Document History............................................................................................................................ 9
2
General Object Overview
OBJECT OVERVIEW
KIIT_BBP_MM_05
Business Return to Vendor Printout
Object ID
Process
SAP SAP Material Mangement
SAP Release
Module
( ) Report
( ) Interface
( ) Conversion
Object Type ( ) Enhancement
( X ) Form
( ) Workflow
Object Title Return to Vendor
Object Description Return to Vendor Printout
Mock Up ID / Name
Required
Cycle of Testing / C1 / C2 / C3 / C4 06.05.2014
Development
Sprint Cycle
Completion Date
Medium Medium
Complexity of Object Priority
SAP Transaction ZMM017 SAP Program ZRP_MM_RETURN_VENDOR
Name Name
Similar SAP N/A Similar SAP N/A
Transaction Program
FS CONTROL
<Customer>
Functional Consultant
Alisha Sadaphal Process Owner Supriya panda & Sumit Panda
– Author and Phone
and Phone
Number
Number
Planned Date of FS 06.05.2014 Actual Date of FS 04.06.2014
Completion Completion
Supriya & Sumit Panda 21.05.2014
FS Approved By FS Approval date
Other Contact and N/A Other Contact and N/A
Phone Number Phone Number
3
Process Requirements Reference
PROCESS REFERENCE
Requirement ID KIIT_FS_MM_05
Requirement Return to Vendor Printout
Description
Gap to be addressed N/A
Alternative SAP N/A
Standard Solution
Generic WRICEF Descriptions
JUSTIFICATION
If you accepted the goods conditionally, i.e. by posting them to goods receipt blocked
stock, you enter the return delivery with movement type 124 (return delivery from GR
blocked stock) instead of movement type 122 (return delivery to vendor).
FUNCTIONAL DESCRIPTION / DESIGN
This Smart form will show what quantity you are accepting and what quantity you are rejecting to the
vendor.
TRANSACTION VOLUME
N/A
FREQUENCY & TIMING
N/A
DEPENDENCIES
N/A
AUTHORIZATION REQUIREMENTS
4
N/A
RELATED DOCUMENTATION (ATTACH OSS NOTES, EMAILS, DOWNLOAD OF EXISTING
REPORT, ETC)
N/A
5
Object Specific Design
Forms / Output
SMARTFORM
OUTPUT
WRICEF-ID Description Data Object Outpu Frequency Volumes Owner
(Purchase t Type
order) (Form,
EDI,
etc.)
KIIT_FS_MM_05 PO 4500000003 & Form N/A N/A MM
Amendment 4500000104 Department
PROCESS FLOW DIAGRAM
1. CHALLAN DETAILS:
a. PO No. : EBELN from EKPO
b. Vendor Code : LIFNR from LFA1
c. Vendor Name : NAME1 from LFA1
d. PR No. : BANFN from EKPO
e. Make “Goods Receipt” field as ERFMG ERFME (i.e. Qty in Unit of Entry EA) from same
table MSEG.
f. Make “Return Quantity” field as ERFMG ERFME (i.e. Qty in Unit of Entry EA) from same
table MSEG.
2. Vendor Details :
a. Make “Quantity” field as ERFMG ERFME (i.e. Qty in Unit of Entry EA)
FORM LAYOUT
For layout Please refer the attachement
6
PRINTER REQUIREMENTS
Standard A4
LEGAL REQUIREMENTS
N/A
EXISTING SAMPLE FORMS
N/A
7
Test Conditions
BUSINESS TEST CONDITIONS (TO BE FURNISHED BY THE FUNCTIONAL CONSULTANT)
[
Scenario # Input Selection Criteria Expected Result
1 Print out
Purchase Order No
8
Document History
AUTHORS & PARTICIPANTS
Role Name
Business System Analyst
Project Process Owner Krishna
Business Unit Process Owner Sumit Panda
Consultant Alisha
Workshop Participant Rohit & Abhinas
REVISION HISTORY
Date Document Version Document Revision Author
Description
04.06.2014 1.0 Signed off Sumit Panda
REVIEWED AND APPROVED BY
Name Title Date Approved
Sumit Panda Project Process Owner
04.06.2014
Sumit Panda Business Unit Process
Owner 04.06.2014
<<NAME>> Corporate Process Owner
<<NAME>> Internal Audit
