Functional Specification

Functional Specification
MM-RP-077
Physical Verification Report

1/8
 Functional Specification

Document History

Techincal Specification
Section I: Object General Information
Title (RICEF No): MM-RP-077 Date: 21.05.2012
Short description: Physical Verification Report

SAP Module/Team: MM

Functional Contact: Subramanian A

Technical Contact Sourav Roychowdhury

Priority: 1
Complexity Level High
Program type Report

Status InProgress /Finished / Released

Reviewer

Role Name Signature Date

JSW SAP Team Uday Acharya
Member
JSW SAP Team Padmanaban
Member
JSW SAP Team Nanda Kumar
Member
JSW SAP Team Abhijat
Member

Approver

Role Name Comments Received Date

JSW SAP Team Uday Acharya
Member
JSW SAP Team Padmanaban
Member
JSW SAP Team Nanda Kumar

2/8
 Functional Specification

Member
JSW SAP Team Abhijat Bajpai
Member

3/8
 Functional Specification

Table of Contents

1. Overview and Scope 4

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

2. Detailed Functional Requirements 5

2.1. Functional Specification for Enhancements 5
2.2. Error Handling 5
2.3. Security and Authorization 5
2.4. Processing and Operational Considerations 5
2.4.1. Performance 5
2.4.2. Batch Requirements 5
2.4.3. Others 6

3. Test Script 6
3.1. Testing Pre-requisite 6
3.2. Test Case 6

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

4/8
 Functional Specification

1. Overview and Scope

1.1. Functional Description

The Physical Verification Report is executed once the Physical Inventory (Stock Count) process is
completed in SAP. When the physical inventory document is created, the Physical Inventory form is
printed which specifies which items are to be counted in the store/yard as part of the stock count.
The physical counting of the items are recorded in this physical inventory document. The entered
count in the physical inventory document are then entered into the system. Later at any point of time
we can run this report to know the details of the Physical Verification.

If the storage location is assigned with Ware house management in SAP, then Inventory count
record needs to be generated for Bins under storage type.

A Physical Verification Report contains, among other things, the following data:

 The plant, storage location and bin in which the count is to take place.
 When the count took place .
 Which materials are to be counted.
 For material handled in batches, which batches are to be counted.

The Physical Verification Report will be a Custom Report.

1.2. Assumptions

 Used for stock items. (Its for all the materials lying in the warehouse.), Consigment stock.
 The Physical Inventory Document with the item to be counted, to be available in the system
with the count entered in it.

1.3. Transaction Volume

Approximate 20,000 documents per year.

1.4. Frequency & Timing

It is real time

1.5. Processing Type

Real Time processing.

5/8
 Functional Specification

1.6. Output Time

The output file is to be in PDF format.

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

Not Applicable.

2. Detailed Functional Requirements

2.1. Functional Specification for Enhancements

Two different programs and layouts needs to be created for JSW Physical Verification Report.
In Inventory Management:
Copy the program RM07IDIF to ZRM07IDIF

In Warehouse Management:
Print report RLLI0400 available in SAP for Warehouse Phy.Inventory Report. The layout needs to be
modified as shown in the respective section.

RELEVANT DOCUMENT SECTION:

One Z transaction code need to be created maintain JSW ABAP naming convention.

Physical Verification
Report Layout.xlsx

The details field descriptions are mentioned in the attachment.

6/8
 Functional Specification

2.2. Error Handling

Not Applicable

2.3. Security and Authorization

Not Applicable

2.4. Processing and Operational Considerations

2.4.1. Performance
Not Applicable

2.4.2. Batch Requirements

Not Applicable

2.4.3. Others

3. Test Script

3.1. Testing Pre-requisite

[Indicate the pre requisite conditions to use to verify successful operations of the conversion.]

Pre-requisite Type Data Element Details

(Master data, Config,
Other Development)

3.2. Test Case

[Document all scenarios associated with this development. Examples would include testing an error-
free run, testing the exception processes, and testing the error handling.]
<Test Case No.XX>

Test Test Step Description T Code Input Data Expected Results Obtained
Step Results
No

7/8
 Functional Specification

4. Appendix

4.1. Glossary of Terms

Term Definition

4.2. Additional Reference Documentation

8/8