Functional Specification

Functional Specification
GR Blocked Stock Report

1/9
 Functional Specification

Document History

Techincal Specification
Section I: Object General Information

Title (RICEF No): Date: 28-July-2015

Inventory Report for GR Blocked Stock
Short description:

SAP Module/Team: Materials Management

Functional Contact: Subhojit Banerjee

Technical Contact GVS Praveen

Priority: 1
Complexity Level High
Program type F
Status InProgress

Reviewer

Role Name Signature Date

JSoft Mr. B.G.Basetty

Approver

Role Name Comments Received Date

JSoft Mr. B.G.Basetty

2/9
 Functional Specification

Table of Contents

1. Overview and Scope 5

1.1. Functional Description 5
1.2. Assumptions 5
1.3. Transaction Volume 5
1.4. Frequency & Timing 5
1.5. Processing Type 5
1.6. Output Time 5
1.7. Retention Requirements 5
1.8. Audience and Distribution 6

2. Detailed Functional Requirements 7

2.1. Functional Specification for Reports / Forms 7
2.1.1. Form Layout 7
2.1.2. Report / Form Fields 7
2.1.3. Selection Criteria 10
2.1.4. Functional Logic 10
2.1.5. Existing Sample Reports / Forms 10
2.2. Error Handling 10
2.3. Security and Authorization 10
2.4. Processing and Operational Considerations 10
2.4.1. Performance 10
2.4.2. Batch Requirements 11
2.4.3. Others 11

3. Testing Conditions/Requirements 11
3.1. Key Business related 11
3.2. Technical related 11

4. Appendix 11
4.1. Glossary of Terms 11
4.2. Additional Reference Documentation 11

3/9
 Functional Specification

1. Overview and Scope

1.1. Functional Description

This reports helps in analysis of GR Blocked Stock quantity and Release from Blocked
Stock quantity.
Receipts & Consumptions related transactions needs to be done to get the O/P

Transaction Volume   Based on this report Stores department will be able to know the data of
any given period, fund center wise, Material type wise receipt v/s consumption. Accordingly
Stores / User dept. can make the analysis of receipt v/s consumption for better Inventory
management.

From  the  output, concerned dept. will have the option to control the incoming materials to
avoid further blocking of working capital.

·         Stores department will be in a better position to furnish the required data to the management
in time.

1.2. Assumptions
Receipts & Consumptions related transactions needs to be done to get the O/P

1.3. Transaction Volume

The report can have more than 1.5 lakhs lines

1.4. Frequency & Timing

The report can be taken fortnightly..

1.5. Processing Type

The report will be taken real time basis.

1.6. Output Time

The output file to be in the Excel Format.

4/9
 Functional Specification

1.7. Retention Requirements

The report will be held as a spool file for 7 days, after which it should be cleared down.

1.8. Audience and Distribution

The authorized Person from stores department can run the report.

Audience Group Use/Distribution Estimated Number Users

Stores Report Execution 100

5/9
 Functional Specification

2. Detailed Functional Requirements

2.1. Functional Specification for Reports / Forms

This reports helps in analysis of GR Blocked Stock and Unrestricted ( Released from GR
Blocked Stock).

Transaction Volume   Based on this report Stores department will be able to know the data of
any given period, fund center wise, Material type wise receipt v/s consumption. Accordingly
Stores / User dept. can make the analysis of GR Blocked Stock v/s Unrestricted ( Released
from GR Blocked Stock) for better Inventory management.

From  the  output, concerned dept. will have the option to control the incoming materials to
avoid further blocking of working capital.

·         Stores department will be in a better position to furnish the required data to the management
in time.

Create a Z-Program and this program can be run through T-code (to be created)
“ZMM_GR_BLK_STK” with Description “Report on GR Blocked Stock”

2.1.1. Report Layout

GR Blocked Stock
Output Screen.xlsx

2.1.2. Report / Form Fields

Logic is given in the report layout.

Sl. Form Field SAP Ta- SAP SAP Tech- Data No of Char Rules/Notes
No ID ble Field nical Field Type
Name Name
1 JSW Logo
JSW Logo to be em-
bedded to the left
top of the form.

6/9
 Functional Specification

2.1.3. Selection Criteria

Name Table field / Check Select- Comments Default

Box / Radio But- Option( Value
ton S) or
Param-
eter(P)
Item Code EKBE-MATNR Parame
ter(P)
Plant EKBE-WERKS Range
From Date to EKBE-BUDAT Range Should be less or equal to the
Date sysdate

2.1.4. Functional Logic

2.1.5. Existing Sample Reports / Forms

N/A

2.2. Error Handling

2.3. Security and Authorization

Stores users will be authorized run the report

7/9
 Functional Specification

2.4. Processing and Operational Considerations

2.4.1. Performance
N/A

2.4.2. Batch Requirements

N/A

2.4.3. Others
N/A

3. Testing Conditions/Requirements

3.1. Key Business related

[Indicate the business level test conditions to use to verify successful operations of the conversion.]

ID Condition Expected results Cycle

Ref.

3.2. Technical related

[Document all technical scenarios associated with this development. Examples would include testing
an error-free run, testing the exception processes, and testing the error handling.]

ID Condition Expected results Cycle

Ref.

4. Appendix

4.1. Glossary of Terms

Term Definition

8/9
 Functional Specification

4.2. Additional Reference Documentation

9/9