Functional Specification Report

Rev 0.5
4-Mar-2004

Report/Form ID: 70-DI

Report/Form Name: Inventory Detail by Location

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 13, 2004

0.1

Arthur
Zheng

Adding three columns to the standard SAP

report, transaction code LX03

Feb 17, 2004

0.2

Arthur
Zheng

Update field names.

0.3

Kurt
Eckman

Clarification that HU & SU are only valid for WM

sites that first implement in Gen2, blank columns
for IM sites. Clarified source for Storage Bin.

Feb 26, 2004

0.4

Arthur
Zheng

Eliminated two columns (Quantity and Expiration

Date) from the previous version. The two
columns are available on the standard report
(they are hidden)

March 3, 2004

0.5

Kurt
Eckman

Provided further clarity to what is needed in Gen

1 vs. Gen 2

Feb 25, 2004

Page 2 of 10

Page 3 of 10

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.........................................................................................................................6
6.1
6.2
6.3
6.4
6.5
6.6
6.7
6.8

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

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

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

Error Handling............................................................................................................8

10

Dependencies.........................................................................................................8

11

Additional Information.............................................................................................8

12

Issues......................................................................................................................8

Page 4 of 10

1 Request Details
Type
Report/Form Description
Functional Team

Report
(ID) 70-DI
Inventory Detail by Location
OTC

(RDD) 0068

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

N/A

Data History Requirements

N/A

Data Volume (No. of pages)

N/A

3 Functional Requirements
3.1

Description

This is the standard LX03 report with the addition of three new fields. Its purpose is to list items and their
quantities by plant, storage location and storage bins.
Please provide a detailed description of the requirement

Page 5 of 10

3.2

Business Justification

To list items and their quantities by plant, storage location and storage bins.
Is there an alternative in the
LX03
standard system? Please list any
standard Report/form that is
available.
Description of alternative
N/A
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

Generation 1: IM Sites Only We need:

Old Material Number or Product Number (TBD)
Serial Number
Generation 2: IM and WM Sites We need in addition to Gen 1:
Handling Unit and or Storage Unit (TBD) (If Handling Unit = Serial Number, then do not show)
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 (which one is TBD) 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 # (TBD).
Please list any assumptions here

Page 6 of 10

4 Selection Screen

5 Processing Logic
Step 1
Use transaction code LX03
Step 2
Input in Standard Selection Screen
Step 3
Standard output with the additional columns requested.
Please describe the detail information that will appear in the Report/Form

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

6.1

Layout

Attach Sample Here

"RDD0068
output.doc"

Page 7 of 10

Narrative Flow
Generation 1: IM Sites Only We need:
Old Material Number or Product Number (TBD): This column needs to be at the immediate left of
Material column.
Serial Number: If available, to the right of Batch #
Generation 2: IM and WM Sites We need in addition to Gen 1:
Handling Unit and or Storage Unit (TBD) (If Handling Unit = Serial Number, then do not show):
These 2 columns need to be at the immediate right of Batch column.
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

Comment

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.

6.5 Line Item (In JDE this would be Column)

Field Name
Field Description
Sort
LAGP-LGNUM
LAGP-LQTPY
LAGP-LGPLA
MARD-LGPBE

Warehouse
Storage Type
Storage Bin

1
2
3

LIPS-WERKS

Plant

Page 8 of 10

Comment
Storage Bin to come from this WM
table/field if that WM file/field exists
(doesn't for IM sites), if not available
there then get Storage Bin from Material
Master's Storage Bin field if populated.

Field Name

Field Description

Sort

MARA-BISMT

Old Material Number or

Product Number

Comment

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
No need to calculate Subtotal.

Please specify grouping details in the comment column

6.8

Exceptions and Conditions

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

9 Error Handling
NA
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?

Page 9 of 10

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

11 Additional Information
LX03 to initiate the report.
Old Material Number MM03 Basic Data 1 Tab
Handling Unit, Storage Unit, Serial Number LS33
Storage Bin LS04 & MM03
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

The decision on Handling unit and/or
Storage Unit is TBD.
The decision on long UPN as material
identifier will determine whether to add
Old Material # or Product #

Name
Arthur Zheng
Arthur Zheng

Please list all items that are TBD.

Page 10 of 10

Phone No
901-3440696
901-3440696

Date
2/13/04

Status
open

2/13/04

open