ERP - Functional Specification
ERP - Functional Specification
For
Reviewed by:
This document contains proprietary and confidential information of AIO Technologies. All data submitted to the
recipient is provided in reliance upon its consent not to use or disclose any information contained herein except in
the context of its business dealings with AIO Technologies. The recipient agrees to inform present and future
employees and or parties involved with the recipient who view or have access to its content of its confidential nature
that they are to abide to these rules also. The recipient agrees to instruct each employee that they must not disclose
any information concerning this document to others except to the extent those matters are generally known to, and
are available for use by, the public. The recipient also agrees not duplicate or distribute or permit others to duplicate
or distribute any material contained herein without express written and formal consent from AIO Technologies.
Nov 01, 2015 FUNCTIONAL SPECIFICATION DOCUMENT – ENTERPRISE RESOURCE PLANNING
SIGN-OFF SHEET:
TABLE OF CONTENTS:
TABLE OF CONTENTS:.............................................................................................................................. 4
1: PRE-AMBLE:......................................................................................................................................... 5
2: BUSINESS REQUIREMENTS:................................................................................................................. 7
5: Functionalities ..................................................................................................................................... 8
7: Retail seller / shop admin features ...................................................... Error! Bookmark not defined.
7: BACK end / Super ADMIN user Functionalities .................................... Error! Bookmark not defined.
1: PRE-AMBLE:
The solution described in this document covers all the requirements of the project in terms of functionality and
design. There will be 2 documents to follow the customer requirements specification document which includes (FSD
and SRS). The customer requirements specification document is a high-level requirements list that has been built up
over time both verbally and in writing. This document will allow AIO Technologies to analyse the best solution for the
project. The requirements set-out in this documentation are written in stone and will not be changed once the first
line of code is written, unless mutually agreed by both parties.
The purpose of this document is to describe the requirements of Enterprise Resource Planning in detail. Further to
this, the document goes to explain each functionality in terms of process flows.
This document covers all the requirements and suggested ideas of the Enterprise Resource Planning System.
Once the project manager approves this document, it will serve as the definitive statement and basis for our
proposed solution, which will in-turn be the foundations of development for the system. It will override all the verbal
and written communications within the AIO Solutions.
Since this document will also serve as the scope document, any modifications or changes to the project
requirements or specifications after this document sign-off will be entertained via a change control procedure.
Provide a list of contractual or task level assumptions and/or constraints that are preconditions to the preparation of
the SRS and final solution. Assumptions are future situations beyond the control of the project, whose outcomes
influence the success of a project.
Nov 01, 2015 FUNCTIONAL SPECIFICATION DOCUMENT – ENTERPRISE RESOURCE PLANNING
1.5: ASSUMPTIONS:
ASSUM-1.1 The system will be using MySQL for its all database requirements.
ASSUM-2.1 The system will have a backend logic developed using Java language.
ASSUM-3 The test domain name and hosting will have already been acquired.
Nov 01, 2015 FUNCTIONAL SPECIFICATION DOCUMENT – ENTERPRISE RESOURCE PLANNING
2: BUSINESS REQUIREMENT S:
Please find below a low-level synopsis of the background and business requirements for Enterprise Resource
Planning System and the messages they are looking to achieve.
2.1 BACKGROUND:
Enterprise resource planning (ERP) is a cross-functional enterprise system driven by an integrated suite of software
modules that supports the basic internal business processes of a company. ERP gives a company an integrated real-
time view of its core business processes such as production, order processing, and inventory management, tied
together by ERP applications software and a common database maintained by a database management system. ERP
systems track business resources (such as cash, raw materials, and production capacity) and the status of
commitments made by the business (such as customer orders, purchase orders, and employee payroll), no matter
which department (manufacturing, purchasing, sales, accounting, and so on) has entered the data into the system.
ERP facilitates information flow between all business functions inside the organization, and manages connections to
outside stakeholders.
Enterprise systems are complex software packages that offer the potential of integrating data and processes across
functions in an enterprise. Although the initial ERP systems focused on large enterprises, there has been a shift
towards smaller enterprises also using ERP systems.
Organizations consider the ERP system a vital organizational tool because it integrates varied organizational systems
and enables flawless transactions and production. However, an ERP system is radically different from traditional
systems development. ERP systems can run on a variety of computer hardware and network configurations, typically
employing a database as a repository.
3: GENERAL SCOPE:
3.1: LANGUAGE:
The Enterprise Resource Planning System should support only two languages:
English (British)
Arabic
User interface of the website, logo and the overall theme has to be created according to the standard preferences.
First of all, we will create home page design options and the logo options by following the planed instructions and
share it for approval. Once we agree on a specific design, then we’ll create some more pages to cover all design
elements of the system. Once approved, HTML and CSS will be created for all the designs.
Nov 01, 2015 FUNCTIONAL SPECIFICATION DOCUMENT – ENTERPRISE RESOURCE PLANNING
1024 X 768
Ideal Site Resolution:
(Fits almost all screen sizes)
Colour Scheme
Red, Green, Black, Orange, Grey and White
preferences:
http://aio.ae/erpsystem.php?page=services
Reference websites:
5: DESIGN ARCHITECT
Following are the system’s functionalities explained against the business logic. The system can be divided into
following sections:
Presentation layer
Business Logic Layer (Further divided into business logic classes and services classes)
Data Access Layer
The front end user is the common user on the system who can access ERP from the front end and can perform all the
functionalities accessible on the front end. Below is a list of all such features explained in detail with their functional
details.
i. Access
The ERP System has a standard authorization process.
New User
Nov 01, 2015 FUNCTIONAL SPECIFICATION DOCUMENT – ENTERPRISE RESOURCE PLANNING
Sign in
System will verify users to log in and the system will verify user id, password
and URN required code. If the id, password and URN required code
provided by the user doesn’t match with a valid ID, password and URN
required code combination; our system will show an error message to the
user.
Log out
This option will allow the user to log out of our system ending the user’s
current session on the system. There will be two ways to Sign Out/Log Out.
Either close the browser window in which the user is logged in or click the
‘Sign out’ link in the top header.
Forgot password
Only the administrator has the rights to reset or change the password of
any user.
Session Time-out
This functionality logs-out the user automatically if user doesn’t perform
any activity for some time.
Right Panel
Nov 01, 2015 FUNCTIONAL SPECIFICATION DOCUMENT – ENTERPRISE RESOURCE PLANNING
iii. Dashboard
Fiscal Income statement
Definitions: A fiscal year (or financial year, or sometimes budget year) is a
period used for calculating annual ("yearly") financial statements in
businesses and other organizations
Description: Accounting period in bookkeeping is the period with reference
to which accounting books of any entity are prepared.
It is the period for which books are balanced and the financial statements
are prepared. Generally, the accounting period consists of 12 months.
However the beginning of the accounting period differs according to the
jurisdiction. For example one entity may follow the regular calendar year,
i.e. January to December as the accounting year, while another entity may
follow April to March or July to June as the accounting period.
Real Estate
1. Property
I. Properties
II. Components
III. Units
V. Legal
It will be dependent on ‘Legal Details’ which will include ‘Legal Group’, and
‘Effective Date’ etc.
2. Offer Form
3. Contract
I. Contracts
N/A
‘Gross Details’ will be dependent on the person who will receive the
payment, and ‘Other Charges’, ‘Total’ etc.
There will be shown all the cancelled contracts which can be viewed.
HR
1. HR Policies
I. Attendance Policy
II. Leave Policy
III. Working Shifts
IV. Holiday & Work off
V. Grade
VI. Department & Branches
VII. Designation
2. Personal Affair
I. Company
II. Person
III. Person Bank
IV. Job Template
V. Job Assignment
VI. Document Handover
VII. Asset Usage
VIII. Memo & Warning
3. Payroll
I. Payroll Elements
Nov 01, 2015 FUNCTIONAL SPECIFICATION DOCUMENT – ENTERPRISE RESOURCE PLANNING
II. My Payroll
III. Payroll Execution
IV. Pay Commit & WPS
V. Employee Loan
4. Attendance
I. My Attendance
II. Attendance Information
III. Assign Shift
5. Leave
I. Apply Leave
II. Leave Control
Accounts
1. General Ledger
The central task of G/L Module is to provide a complete overview for Financial
Accounts. Recording all business transactions (primary postings as well as
settlements from internal accounting) that is fully integrated with all the other
operational areas of a company ensures that the accounting data is always
complete and accurate
Essentially, the general ledger serves as a complete record of all business
transactions. It is the Centralized, up-to-date reference for the rendering of
accounts.
General Ledger is a program which controls all the Transactions that are
entered from other Modules, and Link data without the need to enter
information more than once and thus able financial Controllers to tighten
control over the system users to review and audit and avoid errors.
This Module handles all the accounting system and will help to extracts the
trial balance and balance sheet.
a. Chart of Account & Segment values.
b. Budget Processing & Control.
c. Journal Processing (Actual, Budget, Encumbrance).
d. Journal Approval Workflow.
e. Adjustments and posting
Nov 01, 2015 FUNCTIONAL SPECIFICATION DOCUMENT – ENTERPRISE RESOURCE PLANNING
I. Calendar Manager
Definitions:
Calendar year “starts from 1st of Jan and ends on 31st Dec every year”.
A fiscal year (or financial year, or sometimes budget year) is a period used
for calculating annual ("yearly") financial statements in businesses and
other organizations
Description:
Definitions:
Description:
The COA is used to produce the Profit and Loss report, the Balance Sheet
report, the Budget report and the Prior Year reports. It is also used when
you run your Year End. The Year End facility refers to the COA to see which
accounts make up the Profit and Loss report. These are cleared down
during the Year End procedure. For more information, see Running the Year
End on page 300.
Sage 50 Accounts offers several COA designed for different organizations.
The first time you access Sage 50 Accounts, you choose which one you
would like to install. For more information see The Active Setup Wizard on
page 4. To ensure the selected COA suits your business it needs to be
reviewed and possibly modified. This is explained in the following sections.
Note: For those wanting to produce more than one Profit and Loss report
showing a variation of business results, you can add more than one COA to
achieve this.
IV. Combinations
V. Category
2. Bank
I. Bank
II. Cheque Book
Nov 01, 2015 FUNCTIONAL SPECIFICATION DOCUMENT – ENTERPRISE RESOURCE PLANNING
3. P2P
I. Product Service
The System will Enter a unique product code (Auto generated Code) using
its own built in codes the Admin can change the codes as per their business
requirement.
Enter the product name or description here.
Unit of Measurement defines one unit or measures of the product (how the
quantity is measured). (Any division of quantity accepted as a standard of
measurement or exchange).
There user can select various option as per the desired need of the product
nature. The admin can define any new units as per the business needs.
Enter here the code you want to be used as the default for Inventory when
you create a new product record which will be used while purchase and sale
transaction and respective debit and credit to This Inventory Account
Use the drop-down button (Look-up Mirror) to select an existing code.
The System will by default create a code (An Analysis Account) of Inventory
Account (Natural Account) or Asset Account (Natural Account) or An
Expense Account (natural Accounts ) depending the selection of Natural
Account
Before GRN during Tender and quotation the system can use the supplier
code(A/p Account) and inventory Account but the it will be validated after
GRN ,which will be then posted to general ledger Accounts of sales,
inventory and Cost of sales.
The system will post actual entries after GRN preparation
Stock items in the Store of an enterprise could include any or all of:-
a. raw materials
b. components (parts)
c. spare parts
d. partly finished work (sub-assemblies, work in progress)
e. materials for maintenance
Nov 01, 2015 FUNCTIONAL SPECIFICATION DOCUMENT – ENTERPRISE RESOURCE PLANNING
f. consumables
g. tools, jigs and gauges
h. finished products packaging materials
i. scrap and by-products of production
j. damaged, substandard or obsolete items
k. Finished goods
II. Stores
An area set aside into which all the items and materials required for
production and/or for sale/distribution are received, where they are
housed for safekeeping, and from which they will be issued as required.
The store work involves:
i) receiving items and materials, including the inspection of them;
ii) storing the various stock items in the most appropriate fashion, binning
and/or racking them
The store is categorized in different storage type’s storage sections and bin
types
1. Storage types i.e. Bulk storage, open storage, high rack
storage, picking area etc.
2. Storage sections i.e. heavy parts, bulky materials, fast-
moving items &slow-moving items etc.
3. Bin types i.e. High bin, low bin and medium bin etc.
The storage bin is the smallest available unit of space in a store. And the
system can easily give the dimensions by entering the length breadth and
height of the bin which will result in proper allocating the space for
inventory. Each bin can be given a unique number which can easily trace
the items and will expedite the ordering process.
IV. Supplier
If you buy goods or services from any vendors you can add vendors with
their business details, name and addresses, in order to get historical
information about the past purchases and get many reports.
V. Tender
VI. Quotation
The process starts when a Call of Bid (tender) is issued. In response to the
Call of Bid (tender), quotations are sent from various potential suppliers.
After that the one best suited for the organization is selected.
The sales quotation can either be rejected or transferred into a purchase
order.
With this business process you can assure your business that you will
receive a certain product configuration and quantity at a specific time and
price.
The purchase order act as a written record of your order, providing more
accuracy than a verbal order might offer and is issued by purchasing
department .The purchase order is a contract that confirms your intent to
buy. It lists items, quantities, and prices, along with related charges. The
order also states your billing and shipping addresses, and the credit terms
you have negotiated with the supplier. Purchase orders may originate from
requisitions, or can be created directly.
A purchase order does not actually affect any of your accounts. Once items
begin arriving, you use the GRN task to receive items on the purchase
orders.
During Goods receiving Note (GRN) the quality control inspection will be
conducted. So if any discrepancy found the system will automatically adjust
and reconcile it. The discrepancy may be in terms of quantity, quality or
else, The Reconciliation and matching will be done with purchase orders so
this screen will be a default screen no manual entries will be done . It will
further enunciate the debit note to inform the supplier about the
discrepancy that the supplier books will be adjusted.
X. Debit Note
XI. Payments
After receiving Goods in stores the goods can be used in our business so
there will be proper issuing of goods and can be only issued against a
Nov 01, 2015 FUNCTIONAL SPECIFICATION DOCUMENT – ENTERPRISE RESOURCE PLANNING
4. Cash
I. Payment Request
II. Direct Payment
III. Petty Cash
5. Fixed Assets
6. Loan
I. Loan Information
II. EIBOR
III. Collateral Detail
IV. EMI
7. Pont of Sale
8. Budget