1.

0 Business Requirement
Business needs a report indicating the,
o Consumption of last 30 months
o Receipt of last 12 months
o Future requirements of next 6 months
This report is required,
o For past consumption in order to create the new PIR to upload each week
o Inventory classification ( obsolete , slow moving , active )

2.0 Impact Analysis

2.1

2.2

Understanding
Based on the input parameters, system will generate list indicating material numbers in a plant,
its 30 months past consumption, 12 months past receipts and 6 months future requirements
Solution

2.2.1.1

Impacted Areas & dependencies

2.2.1.2

Functional Solution

2.2.1.3

Screen Changes

2.2.1.4

Database Changes

2.2.1.5

Navigational Changes

3.0 High Level Design

3.1

Detailed Description
A custom transaction and associated program will needs to be developed, (similar to std
transaction MC44 i.e. inventory turnover)

3.2

Design Approach
For the custom transaction, following is layout of the initial screen,

Selection screen
layout.xlsx

Output screen of the report should display the following columns,

report Output
screen.xlsx

For the past consumption /goods issues, find out the total of goods issues for the consumption
period entered on the initial selection screen (by default it is past 30 months). These details
can be fetched using the same logic used by the stock movement analysis done in the MC44
screen. See the following screenshot indicating the place where in MC44 it is seen,

Note :- Summation of all these goods issues should be put into the Past Consumption/Goods
Issue column of the output screen

For the past goods receipts, find out the total of goods receipts for the receipts period entered on
the initial selection screen (by default it is past 12 months). These details can be fetched using
the same logic used by the stock movement analysis done in the MC44 screen, See the following
screenshot indicating the place where in MC44 it is seen,
Note: - Summation of all these goods receipts should be put into the Past Goods Receipts
column in the output screen
For the future requirements, gather the requirements for the future 6 months (or the period entered on the
selection
screen).
To
gather
the
future
requirements
function
module,
MD_STOCK_REQUIREMENTS_LIST_API can be used. Gather the requirements for the

Note: - Summation of all these future requirements should be put into the Requirements
column in the output screen

3.3
3.3.1

Configuration Requirement
SAP Configuration Requirement
NA

3.3.2

Field

Custom table creation: List each tables and File structure----NA

Short Text

Data Element
/ Field Type

Field Length

Additional info

3.3.3

Standard SAP configuration

No

3.4

Data Requirement

Test data for the FXIA plant is attached herwith,

3.5

Screen

3.5.1

Parameter / Select options (selection-screen)

<Enter your contents in the table given below>

Screen Name
TYPE

Field

Field Validations

Radio Groups

Check Boxes

3.5.2

Field description

Table

Mandatory /
Nonmandatory

Push Buttons for Drilldown reports on different levels

<Enter your contents in the table given below>

Button

Field name

Drilldown from

Drilldown To

Match Code
required (Y / N)

3.5.3

Screen Layout (In case of Transactions)

3.5.4

Navigation Diagram (or Screen flow)

3.6

Layout and Presentation

3.6.1

Sort Options

3.6.2

Report or file Layout (In case of Reports)

3.6.3

SAP Script Layout (In case of SAP Scripts)

3.6.4

Logo for SAPScript in case of non-pre-printed stationary

3.6.5

Printing of SAPScript

3.7

Non-EDI Interfaces / Data Mapping

3.8

EDI Interfaces

3.9

Error Control and Handling

What errors may occur and how they should be treated.

Message
Referenc
e
Number

Type
[I,E,W]

Stop
Program
(Yes/No)

999

Yes

Message Text

{ e.g. Account group

excluded }

Message
Display
[Selection
screen,
Popup, etc.]
End of report

Conditions Where the Message

Should Occur

{ e.g. If the group is excluded }

4.0 Assumptions / Limitations

5.0 Security Requirements
5.1

Authorization Groups / Authorization Objects

Please refer to the functional specification for the appropriate security levels.

ABAP considerations:
Do any of the programs need special authorization groups, if so, explain?
Do the users need special security profiles to execute the enhancement, if so, explain?

{E.g. The transaction program will verify that the user has the correct authority on transaction entry.}