Overview

Purpose
Disposal Management System currently is existed in the local Employee PC as windows application
without work follow and no direct integration with SAP. This process would be built in Sap Fiori
standard Platform
Scope
 Collecting of all scrap materials for sale
 Approval process for materials form
 New portal for Auctions
 Complete sales process need to build till Billing in SAP
 Management the approval from SAP My Approval application.
 Reports & KPI's

Project Information
As of now this process executes with .net system ,Contractor shall develop Disposal
Management System as described in scope ,By using SAP Fiori Platform connected to
ODATA and deployed to SEC SAP gateway
Goals, Objectives, and Scope

1. Automated the scrap process.

2. Zero paper.
3. Improve the User process and productivity

Business

This scrap disposal process is an Revenue to company it this get auctioned with more
visibility in market

Stakeholders
[The Stakeholders statement and table outlines the project stakeholders and their respective roles.]

<<Begin text here>>

NAME DEPARTMENT ROLE
Fahed Al Muharedb
Process Information:
Current process flow diagram with proper approvals

Current Process Description

New Processes or Future Enhancements
New Process Description
The expectation is to receive workable solution better that the current.
[Provide detailed step information about the new processes in the following table, if applicable.]

<<Begin text here>>

# DESCRIPTION USER ISSUES

Requirement Information
High-Level Business Requirements
The system will help the users to track and follow up the prepared lists for non-moving and
excess materials.
EXCESS materials and Nonmoving materials are moved to once location with proper
approval process, Once approved Auction process will start and billing follows on .

System Interfaces- No Interfaces

Infrastructure Requirements – No further Infrastructure is required

Other requirement Information

Product, Organizational, System, and External Requirements
[This section includes details about other requirements that can cover products, organizations, systems (e.g.,
performance, operations), and external requirements (e.g., security).]

<<Begin text here>>

Audience Indicate the users of the system or application
 Security SAP standard security rules and
recommendation for Ui5 /Fiori
development.
Volume and Performance Metrics Indicate system or application volume and
performance metrics to be performed, e.g.,
database records or transactions to be
processed within a certain time period.

Capacity and Scalability Indicate capacity and growth information or

concerns that will have to be met over time.

Support Considerations Indicate system or application support, e.g., who

will support it, hardware / software to support
it, service level agreements or contractual
obligations.

Audit Indicate any system or application audit

requirements or constraints.

Design Constraints Indicate system or application design

constraints, e.g., software languages,
developmental tools, architectural and design
constraints.

Output Indicate reports, files or other export output.

Data Retention Indicate any special data retention

requirements.

Legal or Regulatory Indicate any legal or regulatory requirements

that can impact the system or application.

Usability, Performance, Operations, and Maintenance Requirements

[Provide requirements information related to product usability, system performance, operations, maintenance or
conditions that must be met by the proposed application or system. These requirements can have a more detailed
title / description or be in a numbered list.]
<<Begin text here>>

# FUNCTION DESCRIPTION PRIORITY COMMENTS

Content / Data / Sample Report Requirements

[Include information about reports or data that must be provided or modified, e.g.,
• Samples of all content and data.
 • Examples of input / output files and their schema.
• List all necessary content with a brief description.
• Who will provide the information? List will provide the information and who is responsible for what and
when, e.g., one-time only, other content must be maintained on a regular daily, weekly, or monthly basis.
• Who will maintain the information when the application is operational? ]
<<Begin text here>>
Screen Requirements
[Provide any business rules or information related to screen information that must be included.]

<<Begin text here>>

Element Description Source Requirement Default

Training and Documentation Requirements

[Provide training and documentation information that is required to support the application or system to be
implemented, e.g., training plans, training materials, support documentation, and user documentation.]
<<Begin text here>>
Training Resource Schedule Comments
Session 1
Session 2

Glossary
[List any document terms that may not be fully understood with some explanation.]
<<Begin text here>>

Appendix
[Use this section to include architectural design graphics (e.g., network, server, and system designs), diagrams (e.g.,
entity relational diagrams–ERD), object models, and data dictionaries.]

<<Begin text here>>

Estimated Project Execution Period (in Weeks)

?? Weeks

Estimated Cost
?? SAR

Business Approvals
POSITION NAME SIGNATURE
Department Manager,

Executive Director,