Functional Requirement Specification

< Project Name >

Functional Specifications Document

<Project Id-FD-R-000>

< Version No. >

Prepared By Reviewed By Approved By

NAME :

DESIGNATION :

SIGNATURE :

DATE :

Page : 1 of 7
 Functional Requirement Specification

Revision History

Version Date Change By Brief Description of change

No

About the Report Requester

Requester’s Name Request date

Department/Team/ R/3 release for report

Group/Cost Center development

Report user if different Signature(s)

Functional consultant Technical

Consultant

Request Details/Issue
Details/CR

About the Report

Priority or need for this report (check one) High Medium Low
If you answered “High,” briefly
explain why you set this
priority:
Complexity of this report (check one) High Medium Low
If you answered “High,” briefly
explain why you set this
priority:
Date report needed by
1 Report name: Enter a suggested name for the report you want.
Note that for custom reports, the assigned name will appear in the system.

2 Short description: Enter a short description of the desired report (including the benefit of
the report). Note: For custom reports, the short description is included in the documentation.

Page : 2 of 7
 Functional Requirement Specification

Technical Specifications

4 Business data source(s): Enter the name of the application(s) or data area(s) of the
report. Examples: SD-shipping, FI-accounts payable, HR-payroll, and so on.

5 Tables or fields: Specify tables or fields in the desired report. Recommendation: Consult
with the report developer or a user who understands the technical aspects of the application
areas.

Table Name: Refer Sections 13, 16 & 17

Fields: Refer Sections 13, 16 & 17

6 Similar reports in the R/3 System: List any standard R/3 reports you found that are
similar to the one you have requested. Discuss why the standard report does not fit your
needs. Hint: If you find a report that contains some—if not all—of the fields, enter its name
below.
Title of the Report Description of report; special Program name
features; features that you do not transaction/ot
want to include her

Page : 3 of 7
 Functional Requirement Specification

7 Reporting tools evaluated: Based on your survey of the reporting tools, indicate:
 Which reporting tools (for example, Report Painter, ABAP Query, etc.) have you
considered?
 Which reporting tool (if any) do you prefer more than the others?
 In your view, are there any tools that are not appropriate for this report?
Use the table on the following page and if necessary, the space below the table.

Reporting tool or Check if Preferred tool for this Reasons why

Data collector considered? report preferred
ABAP Query
LIS Standard Analyses
LIS Flexible Analyses
Report Painter
Report Writer
Drilldown

8 Other resources: Have you considered any external resources (for example, OSS, ASUG,
SAPnet) to find the report? Include any message numbers you received from these or other
sources.
NA
9 Long description: Enter a detailed description of the report. Include the following
information:
 Business reason (or requirement) for the report
 Layout and screen information (for example, weekly, monthly, or quarterly data; column
and row headings, and document data, etc.)
 References to any legacy system reports considered from which this report can be found
(with attachments, listings, or screenshots, if possible)

Other Technical Considerations

10 Authorizations

Page : 4 of 7
 Functional Requirement Specification

Indicate below
the level of authorization control you want to exercise:
Should restrictions be placed on who may use this report? Yes No
Should restrictions be placed on who may see the report output? Yes No
Should certain fields be hidden from certain users? Yes No

Other comments or instructions:

Clarifications (If yes)

NA

11 Upgrades
Are there potential consequences of upgrading this report to a Yes No
newer release of the R/3 System? If yes, use space below to
explain.
Is the development of this report based on function modules Yes No
used in existing reports?
NA

12 Development Considerations and Notes

Are there special internal tables that need to be accessed? Yes No
Are there any other key people in the company who could offer Yes No
additional information or perspectives on this report?
Would other divisions in the company need such a report? Yes No
Have other divisions in the company already created the same (or Yes No
similar) report?
Clarifications (If yes)
NA

13. Report Selection Screen Criteria

Sr. Field Text on Field Names Table Default Value
No Selection Screen Name
1
2

Page : 5 of 7
 Functional Requirement Specification

3
4
5
6
7
8

Desired screen design layout (selection possibilities):

NA

14. Validation for Selection Screen

NA

15. Z-Table involved in Report Generation

Sr. Field Table
No Description Field Names Name Remarks

NA

16. Report Layout Criteria

Sr. Table Total/ Sub Total
No Field Text on Report layout Field Names Name field

Refer Processing Logic for Details against each of the Fields in the Report

Desired report layout:

 Report Header Should Display the Selection Parameters
 Report Footer should display the Run-Date & Run-Time

Page : 6 of 7
 Functional Requirement Specification

 ALV Report

17. Processing Logic

Eg.
 Select the Work Centre
 Select the Confirmed Order Operations against the Work Centre
 Select the Activity Type and the corresponding Actual Work in the Operation Confirmations
 Select the Activity Price and calculate the Costs for the corresponding Activity
Types based on the conditions

16.1 Select CRHD-ARBPL when CRHD-OBJID = AFRU-ARBID

16.2 Select CRTX-KTEXT_UP when CRTX-OBJID = AFRU-ARBID
16.4A Select VIAUF_AFVC-INGPR when VIAUF_AFVC-ARBID=AFRU-ARBID
16.5 If AFRU-LEARR has NT
16.6 (Value in Row 5) x (COST-TOF0XX) [Select COST-TOF0XX If
COST-WRTTP=04, COST-TARKZ=007, COST-OBJNR has ‘CRCO-KOSTL’ and ‘NT’
Where CRCO-OBJID = AFRU-ARBID] {0XX is posting period of the posting date,
i.e. AFRU-BUDAT (use Function Module = DETERMINE_PERIOD)}

18. Required Download

MS-Excel

19. Performance Criteria (i.e. Extent of data loading on server while processing).

Selection may be restricted to 1 Plant at a time

20. Usage frequency

As required. Monthly at the very minimum. Must be part of month-end report suite.

Page : 7 of 7