You are on page 1of 9

Functional Specification Report

Rev 0.4
25-Feb-2004

Report/Form ID: 72-DI


Report/Form Name: Inventory Transaction Report

Approvals
Name

Intent of Signature

Signature

Date
(DD-MMM-YYYY)

Functional Specification is
complete

Matt Kenney
MDT Process Lead

All the information in the


functional specification is
sufficient for development

<Name>
MDT Technical Lead

Document History
Date Revised

Version Number

Revised By

Reason for Changes

Feb 9, 2004

0.1

Arthur
Zheng

Adding four columns to the standard SAP report,


transaction code MB51

Feb 17, 2004

0.2

Arthur
Zheng

Updated field names

Feb 20, 2004

0.3

Aren Mishra

Updated Positioning of batch field and


transaction description details

Feb 25, 2004

0.4

Kurt
Eckman

Clarification that HU & SU are only valid for WM


sites that first implement in Gen2, will be blank
columns for IM sites.

Page 2 of 9

Table of Contents
1

Request Details..........................................................................................................4

Report/Form Definition...............................................................................................4

Functional Requirements...........................................................................................5
3.1
3.2
3.3
3.4
3.5

Description................................................................................................................................. 5
Business Justification................................................................................................................. 5
Regulatory / Compliance Requirements.....................................................................................5
Special Requirements................................................................................................................ 5
Assumptions............................................................................................................................... 5

Selection Screen........................................................................................................6

Processing Logic........................................................................................................6

Output.........................................................................................................................7
6.1
6.2
6.3
6.4
6.5
6.6
6.7
6.8

Layout......................................................................................................................................... 7
Form Specific Information........................................................................................................... 7
Additional Header Information.................................................................................................... 7
Header Elements (Level Break).................................................................................................. 7
Line Item (In JDE this would be Column)...................................................................................8
Calculation Logic for Computed Fields.......................................................................................8
Subtotal...................................................................................................................................... 8
Exceptions and Conditions......................................................................................................... 8

Unit Test Requirements..............................................................................................8

Security / Authorization Requirements.......................................................................8

Error Handling............................................................................................................9

10

Dependencies.........................................................................................................9

11

Additional Information.............................................................................................9

12

Issues......................................................................................................................9

Page 3 of 9

1 Request Details
Type
Report/Form Description
Functional Team

Report
(ID) 72-DI
Inventory Transaction Report
OTC

(RDD) 0069

SubProcess / BPP

OTC Logistics Operations CORE

(BPP reference)

Phase / Priority
Complexity / Scope

Gen 1
Low

High
Global

2 Report/Form Definition
Basic Information
Form type

N/A

SAP Standard program

N/A

Report Type

Operational

Module

SD

Output medium

Online / Local Printer

Printer ID

N/A

Printer Location

N/A

Language requirement

Default English Change for Local Requirements

Paper requirement

Letter and A4

Suggested technique

Conventional Report

SAP System

R3

Initiation Process

Manually

Run Frequency

On-demand

Data Update Frequency

Other Specify

Data History Requirements

(Applicable for BW only. How far back should the data be available?)

Data Volume (No. of pages)

N/A

Page 4 of 9

3 Functional Requirements
3.1

Description

This is the standard MB51 Document Report with the addition of five new fields. Its purpose is to show
prior transactions from history to enable the user to do quality checks (I.e. check correctness of put way,
inventory moves, etc.) show lost, scrapped, etc.
Please provide a detailed description of the requirement

3.2

Business Justification

To make sure inventory transactions are done right (and who, when, qty, etc.)
Is there an alternative in the
MB51 but this does not show Old Material Number, Batch Number,
standard system? Please list any
Serial Number, Handling Unit and/or Storage Unit Number, or
standard Report/form that is
Transaction Description.
available.
Description of alternative
Standard MB51 report.
Reasons why alternative is not
acceptable
Please provide a business justification for this requirement.

3.3

Regulatory / Compliance Requirements

N/A
Please provide any Regulatory / Compliance requirements

3.4

Special Requirements

Five additional columns needed. #1 Old Material Number or Product Number. #2. Batch# #3. Serial # if
applicable. #4. Handling Unit# and/or Storage Unit# (TBD) #5. Transaction Description (i.e. Inventory
Transfer, Replenishment, Put Away, etc.)
Need user capability to export to Excel.
Please provide any special requirements country specific, Report Distribution, etc.
If there are special burst/bind requirements, please list them here.

3.5

Assumptions

The Old Material Number or Product Number will be the legacy part number once long UPN is used as
material identifier.
Handling Unit and/or Storage Unit will be used to capture serial # of products (TBD).
Please list any assumptions here

Page 5 of 9

4 Selection Screen

5 Processing Logic
Step 1
Use transaction code MB51
Step 2
Use the standard selection screen
Step 3
Report results reflect selection criteria, output include new columns requested.
Please describe the detail information that will appear in the Report/Form

Page 6 of 9

6 Output
Note: Please refer to the Report Layout Sample document in Ascendant before completing this
section.

6.1

Layout

Attach Sample Here

"RDD0069
output.doc"

Narrative Flow
#1 Old Material Number or Product Number. This column needs to be to the immediate left of Material
column.
#2. Batch# should be placed to the immediate right of Material Document
#3. Serial# if applicable should be placed to the immediate right of Batch#. #4. Handling unit # and/or
Storage unit # (TBD) immediately to the right of Serial #, HU & SU are only valid for WM sites that first
implement in Gen2, will be blank columns for IM sites.
#5. Transaction Description (i.e. Inventory Transfer, Replenishment, Put Away, etc.). This will be the last
column of the report (to the very right).
Please attach sample layout and example in PDF, XLS or DOC format. Please do not copy and paste. To
attach the file from the Menu go to the Insert -> Object -> Create from file tab -> Browse for file -> Check
the Display as Icon checkbox -> Click on the Insert Button.

6.2

Form Specific Information

Logo
N/A
Letterhead
N/A
Standard text
Other
Please attach sample Logo, Letterhead, etc.

6.3

Additional Header Information

Same as Standard
Report will contain the company name in the first line and Report title in the second line. We can specify
two more Lines in the Report Header. Please specify any additional header information for the report
which will appear in every page of report.

6.4 Header Elements (Level Break)


Field Name
Field Description
MARA-BISMT

Old Material Number or


Product Number

Comment
Level breaks between Old Material Number or Product
Numbers

To get the fieldname from the screen: Please press F1 and then click on the technical information
button and then take the screen field name from the technical information screen.
Please update the SAP transaction code(s) used to find these fields in Section 11. If multiple
transactions are used, or if it is more convenient, please use the comments column above.

Page 7 of 9

6.5 Line Item (In JDE this would be Column)


Field Name
Field Description
Sort
MARA-BISMT
MCHB-CHARG
RIPWO-SERNR
MKPF-BUDAT
NEW

Old Material Number or


Product Number

Batch
Serial

2
3

Posting Date
Transaction Description

Comment
Will use either Old Material Number or Product
Number from APO (TBD) but not both.

New field. It will display the Movement type text

Please include any hierarchy that is available and should be used in the Comments section..
If there are multiple fields, please describe the sort order numerically. All sorts are assumed as
ascending unless stated otherwise in the comments section.

6.6 Calculation Logic for Computed Fields


Calculation Logic
Field Name

6.7 Subtotal
Field Name
Field Description

Level

Comment
Current subtotal by Material is
acceptable.

Please specify grouping details in the comment column

6.8

Exceptions and Conditions

N/A
Describe any calculated exceptions (highlighting of out-of-range values) or conditions (display only those
records that meet condition criteria).This is mainly for BW.

7 Unit Test Requirements


Scenario
1

Description
Test the report with the new columns

Please provide any unit test scenarios from a business perspective that need to be performed

8 Security / Authorization Requirements


To be controlled by users transaction access.
Please describe any specific Security/Authorization requirements

Page 8 of 9

9 Error Handling
N/A
For example: A flag or error message is raised when data in a required field is missing. If no data is found
for a particular field, should a value be defaulted? If no data is found when the report is executed, should
there be a specific message?

10 Dependencies
N/A
Please provide any configuration and master data prerequisites. Include predecessor and successor
processes if any.

11 Additional Information
MB51 to initiate Inventory Transaction Report
Old Material Number MM03 Basic Data 1 Tab
Handling Unit, Storage Unit, Serial Number LS33
Please specify transaction codes used for identifying fields in the sections 4 and 6, any other
related transaction codes and data related information, screenshots for the required fields etc.
Please ensure that all transactions used for validating the fields are listed here.

12 Issues
No
1.
2.

Issue / Resolution Description


TBD - Decision on Handling unit # or
Storage unit # (only one of these but
which is TBD).
Decision on long UPN will determine
whether the Old Material # or Product #
column is needed.

Name
Arthur Zheng

Phone No
901-3440696

Date
2/11/04

Status
open

Arthur Zheng

901-3440696

2/12/04

open

Please list all items that are TBD.

Page 9 of 9

You might also like