1.

Functional specifications are prepared for the gap's that are identified in the business which canot be mapped
directly in SAP.

2.Functional spec's are prepared for the reports as well for the business transactions.

3.Normally these T Codes starts with Z,say ZCS15,ZMFBF.

4.Before preparing the fucntional spec's understand the exact business requirement.

5.A Functional Spec' will be having the requester name,version,input format,detailed logic of the spec's or
requirements and the

output format.

6.A Functional spec can use a table,a fucntional module,BAPI,BADI or a recording.

Generally this falls during Realization,final preparation, stage and also during support that is after Go-Live.

Functional specification

in simple words

if Cilent wants a a report which is not available in Std SAP

then we need to create a Z-report to satisfy client requirment

Now for this functional point of View ( if the report is related to BOM )
then we ( PP ) people should give all the tables of BOM ( required tables for z-report ) to Abaper
then he will develop a z-report in SE38

so the above all , tables Logic for report everything with will be in Std Company template
u can say as this Std template containing all required info to develop Z-report is Functional Specification

o
HI,
When u do a implementation u need to write functional specificatios for technical consultants.
1.In this u explain what purpose u need it.
2. what is logic required for achieving the end result
3.What are the tables and fields which has to taken into consideration.
1.Forms-Purchase order,Sales order,delivery note,order confirmation,good receipt
2.Reports-If new reports are required functional spec has to be given with the table & Field names
3.Interface-In this if u have third party system it has to be linked with SAP to bring the data into SAP
(e-g-Barcoding).
4.Workflow-(e-g)To specify when the print procedure starts, you define a triggering event. To specify
how a document is printed, you define a standard task. To specify which document is printed, and the
circumstances under which the document is printed, you use the workflow definition to formulate
complex rules.
5.Enhancements allow you to add additional functions to the SAP standard.
6.Conversion-Is nothing but like converting PO into PDF format & converting the dat from standard SAP
to excel sheets etc.
regards
murugan
Alert Moderator

Re: RICEFW

Manish Kumar Agarwal Jun 5, 2009 6:58 AM (in response to Nikhil Bhumkar)

Like (1)

A functional specification is a documetn which a functional consultant prepares so that a technical

person( or anyone else) can understand the business requirement. If you have to do some
development which is not supported by standard SAP, an ABAPer needs to do some coding to make it
work. But a functional person can best describe what is required and translate the business
requirements into SAP terminology.Any new development of the Form, report, interface or conversions
and enhancement is documented in Funct. Spec. and the ABAPer or the tech. consultant do the
development with the help of the FS
For example, in a very simple example, if you have to make a new report which displays a list of POs
with scheduled and delivered quantities, you make a functional spec to decribe the problem and then
tell the ABAPer (for example) which fields to take from which tables, what will be theinput for the
report, what will be the output, how the report will look like and so on..
Hope it helps!
Also open the below link to undersatnd the FS in SAP:
http://www.sap-img.com/general/what-are-functional-specification-in-sap.htm

How to prepare functional specification document in SAP?

To speak at macro level that is at project manager or at senior levels. The Functional
Spec (Specification) which is a comprehensive document is created after the (SRS)
Software Requirements Document. It provides more details on selected items
originally described in the Software Requirements Template. Elsewhere organizations
combine these two documents into a single document.
The Functional Specification describes the features of the desired functionality. It
describes the product's features as seen by the stake holders, and contains the technical
information and the data needed for the design and development.
The Functional Specification defines what the functionality will be of a particulate
area that is to be precise a transaction in SAP terminology.
The Functional Specification document to create a detailed design document that
explains in detail how the software will be designed and developed.
The functional specification translates the Software Requirements template into
a technical description which:
a) Ensures that the product feature requirements are correctly understood before
moving into the next step, that is the technical development process.

b) Clearly and unambiguously provides all the information necessary for the technical
consultants to develop the objects.
At the consultant level the functional specs are prepared by functional consultants on
any functionality for the purpose of getting the same functionality designed by the
technical people as most of the times the functionality's according to the requirements
of the clients are not available on ready made basis.
Let me throw some light on documentation which is prepared before and in a project:
1) Templates
2) Heat Analysis 3) Fit Gap or Gap Analysis
4) Business Process Design
5) Business Process Model
6) Business Change & Impact
7) Configuration Design, which is just 5 % of Total SAP- have different names 8) Future Impact & Change Assessment
9) Functional Design (Module Wise)
10) Risk Assessment
11) Process Metrics and Many More-- Which has impact on Business and its work
flow
Notes:
This documents are prepared in Vanilla SAP Standards -- Things differ from one
implementation to another, and it always depends on the type of business which is
opting for SAP.
How to write functional specification in SAP?
Functional specification comes next only to configuration when it comes to functional
consultants job and without mastering it your SAP experience is incomplete. A poorly
written functional spec creates big communication issue between technical and SAP
functional consultant and the matter is further compounded when they are not sitting
at same location. You can only imagine the mess it will create if the functional spec is
not properly written and the technical guy is sitting in different country and worse still
his spoken English is not good (e.g. Chinese, French, Korean etc. ).

Functional specs are written when the standard SAP is not able to meet the client's
requirement. Based on the functional spec the ABAPer will write the technical design
doc. and then the functional guy will test the same in the system and document the
results in his test script.
We come across 3 situations which calls for functional specs to be written:
1. Enhancements /modifications. If business requires some special procedure.
2. Reports, Client's customized reports.
3. Interface, EDI interface involves ALE/IDOC.
Here are some tips to write great functional specs. The objective should be that the
technical guy should understand it in one go and to reduce any further clarification.
1. Understand the requirement completely. This will depend on your business
understanding. Make sure that the client's requirement cannot be met through standard
SAP before working on it. Please suggest the client if any alternative business process
which is supported by SAP and meets his requirement too.
2. In case of reports you must be competent to decide whether it's a R/3 or SAP
BW report. one example - if the report involves data analytics (like you do in pivot
table of excel) it will be a BW report. However its data collection will be done in R/3.
3. You must mention the business need and business value the report/enhancement
will add to the business. This is for future reference and also to convince the other
users.
4. Any legacy system changes to be done once the enhancement/report is run should
also be mentioned. You can mention changes regarding business process or data. This
may be an input for change management team and also for cut-over strategy.
5. In case of interface please do mention if it's a display or non display document.
6. Please do not write the structure in place of table and field. Make some effort and
find out in which field the data is stored. ABAPer will appreciate it.
7. Don't just write table and field name but also give the data pulling logic. This is
perhaps the most important part. At times it is really difficult to make the technical

guy understand how the data is getting pulled. Without understanding this he can't
proceed further. For example
Target quantity - PACKPO-TRGQTY needs to be transported to Rounding quantity
VBAP- ABLFZ
The data pulling logic for the same will as follows
VBAK-VBLEN doc cat E= VBAP-VBLEN
VBAP-MATNR= PACKPO-MATNR Item cat M
8. Be careful about the data volume while designing the input screen of a customized
report. You must very carefully decide which of these should be mandatory and
optional else it will create a performance issue at the time of load testing.
Please note that every implementation has its own unique format for writing
functional specs however the above mentioned points needs to be covered to make it
more communicative and effective.