Sei sulla pagina 1di 5

FUNCTIONAL SPECIFICATION

REPORTS
Section I: Request
Area (SAP System
components):

F&T

Date:

26/05/2004

Requested by:

Jean Upton

Tel no:

Title:

Aged Blocked Invoices Report

Short description:

Report of invoices blocked for payment for control and KPI purposes

Priority:
Volume of data:

High/mandatory

Medium/recommended

Data records

Low/optional

Date available from:

26/;05/2004

Interface specification
1. Report created using:

2. Characteristics required:

Report Painter

Report Writer

SAP Query

ABAP program

Info system

R/3

BW

Crystal Reports

Drilldown

Buttons

Sort

Entry file

Others:

General information:
Results if no conversions are created:

Legal requirements not fulfilled


Lack of essential business information
Lack of functions compared to legacy system
Others:

Approx. duration of development work:


Is there an alternative in the standard system?

Days
Yes

No

Description of alternative:
Reasons why alternative is not acceptable:

Performance problems

Complexity

Others:
Project cost:

Cost approved by:

Date of project
management approval:

301059418.doc

Charge cost to:


Date of steering committee
approval:

1 of 5

Section II: Detailed functional description


When an invoice has been processed via transaction MIRO it maybe blocked for Payment. This
means that it is not available for selection by the payment program F110. The invoices are
blocked due to quantity or price differences that are outside predefined tolerance levels.
There is a standard report RM08RELEASE which displays these blocked invoices. A copy of this
Report is required in order to manage these blocked invoices by grouping them by date into
30/60/90/120+ days old. The output will need to be altered to the format under section Desired
Report Design
Selection Criteria
Same as standard
Report Output fields
Invoice Number

BELNR

Baseline date

ZFBDT

Document Value

WRBTR

Plant

WERKS

Total By Plant
Default total by plant in ALV.
Age bucket logic:
Calculate the difference between system date & baseline date and put in appropriate age buckets
No additional authorization checks are required
No non standard R/3 data to be included
Will be run once a week
This report is not display time critical

301059418.doc

2 of 5

Report
Relevant
tables:

Description
of report
selection:

Description
of report
outcome:

Desired screen design (selection possibilities):

As per original Report.

Desired report design:


Days
Over due
Document Number Baseline Date

Plant

47000000

01.01.04 UK10

4700000050

01.03.04 UK10

Total

0-30

30

60

90

120+

100.00
56.00
56.00 100.00

301059418.doc

3 of 5

Section III: Functional test


Program:

ZFO0001

Test date:

Developer:

Tel no:

Team member responsible for testing:


1. Test file(s): (optional)
2. Is the program in line with the functional specification?
Yes

No

If Yes, sign the form in the appropriate section below. If necessary, add some comments in
the General comments section.
If No, describe the errors in the program here.

Developer responsible:
3. Describe the solution(s):

4. New completion date:

Comments after second test (if the program contained errors after first test):
Date: //

General comments:

301059418.doc

4 of 5

Names and signatures:


_____________________________________________________________________________________
Application consultant
_____________________________________________________________________________________
Developer

301059418.doc

5 of 5

Potrebbero piacerti anche