FUNCTIONAL SPECIFICATION
DOCUMENT IDENTIFICATION
DOCUMENT DETAILS
Program Name
Track
Business Scenario
STAR
FC&A
Accounts Receivable
Track Lead RIL
Track Lead SAP
Process Owner RIL
Sanjay Kumar Saxena
V Subramaniam
Process Number
Process Name
Accounts Receivable
Development Object ID
Development Object Description
DOCUMENT HISTORY
AUTHORS AND PARTICIPANTS
Role
Name(s)
Functional Consultant
Soumik Basu (EY)
RIL Business Process Owner
Uttam Sharma,Ramesh Subramanian
SAP Solution Architect
REVIEWED AND APPROVED BY
Name
Title
Gaurav Jain
SAP Track Lead
Malolan Pathanki
RIL Business Process Owner
Narayanan VS
RIL Track Lead
SAP PMO
RIL PMO
Date
Approved
ASAP IMPLEMENTATION METHODOLOGY
TABLE OF CONTENTS
Document Identification........................................................................................................................... 1
Document History .................................................................................................................................... 1
Table of Contents .................................................................................................................................... 2
1.
Purpose of this document ........................................................................................................... 3
2.
General Object Overview ............................................................................................................ 4
2.1.
Process Requirements Reference .......................................................................................... 5
2.1.1.
Blueprint ID ...................................................................................................................... 5
2.1.2.
Requirement Description ................................................................................................. 5
2.1.3.
Gap to be addressed ....................................................................................................... 5
2.1.4.
Alternative Standard SAP Solution ................................................................................. 5
2.2.
General WRICEF descriptions ................................................................................................ 6
2.2.1.
Justification ...................................................................................................................... 6
2.2.2.
Transaction Volume ........................................................................................................ 6
2.2.3.
Frequency and Timing .................................................................................................... 6
2.2.4.
Dependencies ................................................................................................................. 6
2.2.5.
Authorization Requirements ............................................................................................ 7
2.2.6.
Related Documentation ................................................................................................... 7
3.
3.1.
Object Specific Design ................................................................................................................ 8
Enhancements ........................................................................................................................ 8
3.1.1.
Enhancement Overview .................................................................................................. 8
3.1.2.
Functional Design............................................................................................................ 8
3.1.3.
Error Handling ................................................................................................................. 9
4.
Test Conditions ........................................................................................................................... 9
4.1.
Test Scenarios ........................................................................................................................ 9
4.2.
Test Data Specifications ....................................................................................................... 10
Copyright 2010 SAP AG. All rights reserved
ASAP IMPLEMENTATION METHODOLOGY
1.
PURPOSE OF THIS DOCUMENT
1. The Specification is the basis for the developments that will be done by SAP. RIL has to verify and
approve it formally. Realization starts only after approval.
2. Within the SAP Custom Development Methodology, the Specification is the link between the
business requirements (normally given in the solution proposal) and the technical design (a separate
document). It has the following goals:
1.1. Reference to the business requirements (customer requirements) given in the solution
proposal.
1.2.
Show the mapping into standard SAP products.
1.3.
Describe the solution from an external (user or customer) point of view.
3. Implementation details (database model, report names, and so on) are generally NOT part of the
Specification.
Copyright 2010 SAP AG. All rights reserved
ASAP IMPLEMENTATION METHODOLOGY
2.
GENERAL OBJECT OVERVIEW
Object Overview
Object ID
Object Type
Enhancement
Object Title
Schedule master
Object Description
Creation and maintenance of schedule master and its assignment to
material master in customised screen of material master.
Required
[ ]
C1
[ ] C2
15MAY12
Development
[X ]
C3
[ ] C4
Completion Date
Priority
[ ]
D1
[X ] C1
[ ] Predecessor for
other
[ ]
D2
[ ] C2
developments
[ ]
D3
SAP Program Name
Cycle of Testing
Complexity of Object
SAP Transaction
Name
Similar SAP
Transaction
FS Control
Functional
Consultant
Planned Date of FS
Completion
Other Contact
Similar SAP Program
Soumik Basu
Copyright 2010 SAP AG. All rights reserved
RIL Process Owner
Narayanan VS
Actual Date of FS
Completion
Other Contact
ASAP IMPLEMENTATION METHODOLOGY
2.1. PROCESS REQUIREMENTS REFERENCE
2.1.1. BLUEPRINT ID
Blueprint ID
Blueprint Document Name
2.1.2. REQUIREMENT DESCRIPTION
User to scan the copy of customer transaction statement after signing the statement received or
issued and store it in DMS with referance no of period and fiscal year with a customer number.
2.1.3. GAP TO BE ADDRESSED
The statndard SAP system does not have the place the holder the details required by the business for
tracking the business forms.
2.1.4. ALTERNATIVE STANDARD SAP SOLUTION
Alternate solution for capturing of required document during DMS of the form is not posibble using
standard SAP functionality.
Copyright 2010 SAP AG. All rights reserved
ASAP IMPLEMENTATION METHODOLOGY
2.2. GENERAL WRICEF DESCRIPTIONS
2.2.1. JUSTIFICATION
[ ] Preservation of digital chain
[X ] Automation of process/
Reduction in manual interventions
[X ] Other RIL-specific Requirement
(Please Specify)
[ ] Other (Please Specify)
2.2.2.
TRANSACTION VOLUME
2.2.3. FREQUENCY AND TIMING
Frequency
[ ] Ad-hoc
[ ] Daily
[ ] Weekly
[ X ] Monthly
[ ] Other
(Specify)
Timing Considerations
The screen for the document capturing to be design once with all the required place holders,
2.2.4.
DEPENDENCIES
2.2.4.1. Blueprint Dependencies
S No Dependency Description
1
2
Blueprint ID
Dependency
Owner
Configuration
object status
Dependency
Owner
Development
object status
Dependency
Owner
FC&A AR track
2.2.4.2. Configuration Dependencies
S No Dependency Description
1
2
3
2.2.4.3. Development Dependencies
S No Dependency Description
Development
object ID
1
2
3
Copyright 2010 SAP AG. All rights reserved
ASAP IMPLEMENTATION METHODOLOGY
2.2.5.
AUTHORIZATION REQUIREMENTS
2.2.6. RELATED DOCUMENTATION
Attachment Document Name
Copyright 2010 SAP AG. All rights reserved
Version
Brief Description
ASAP IMPLEMENTATION METHODOLOGY
3.
OBJECT SPECIFIC DESIGN
3.1. ENHANCEMENTS
ENHANCEMENT OVERVIEW
Enhancement
WRICEF ID
3.1.1.
Description
Data object
Functional
gap
Alternative
SAP
standard
Reason
Owner
FUNCTIONAL DESIGN
3.1.1.1. Flow
In this business process, customer has sign the letter with all the details of transaction has happen in
respective month.
Master to be maintain:
1) In transaction code from OBA7 we can validates the new document type of DMS docs type,Create
a DMS three digit document to be maintained in document type field in transaction process CV01N.
2) In CV01N transaction process document part and document version will automatically updates
from system.
3 )In the CV01N transaction process Customer Code will be incorporated
4) In the CV01N transaction process Code date will be incorpoarted
5) Save the data in DMS server in the name of date & customer name identification .
6)These feild will be mandatory feild when the retriving the data from the DMS server.
Imput screen for Data Managment system.
Document
Document Type
Document Part
Document Version
Customer Number
Date
Copyright 2010 SAP AG. All rights reserved
ASAP IMPLEMENTATION METHODOLOGY
Variants
.
3.1.1.2. Design
Any corrospondance in form of hard copy with customer happen along with the acknowledgement of
that document or hard copy like signature,received status, stamp.
1) Configuring the 3 digit new document type in the DMS system
2) Need to be uploaded in DMS securities so for all account receivable document to be stored in
different document type of DMS.
3) In that we need to incorporate two additional field (that need to be modified apart from standard)
name customer code and date.
4) After adding 2 relevent feild called code and data which will be captured at the time of saving the
data in DMS server will be saved.
5) These 2 feild in the screen will be mandatory feild for imput for uploading the data in DMS server.
6) For retriving the data with the help of the 2 mandatory feild for search the DMS PDF document.
3.1.1.3. Validation
Error Handling
Possible Error
Reaction
Message
Other Actions
Test Conditions
Test Scenarios
Copyright 2010 SAP AG. All rights reserved
ASAP IMPLEMENTATION METHODOLOGY
Scenario #
Input Selection Criteria
Expected Result
Test Data Specifications
S No
Object
Value/ ID
Attribute
Copyright 2010 SAP AG. All rights reserved
Value/ ID
For Test
Scenario #
10
