1

CHAPTER 1
INTRODUCTION
1.1 OVERVIEW
An enterprise resource planning (ERP) project is a large enterprise program, both from a
business and technology point of view. It generates huge changes and often involves calling into
question many traditional functions within the company, for which people are seldom well
prepared. It often requires the implementation of several new systems and their integration with
existing systems and often represents one of the larger IT projects certainly one of the highly
critical ones in most companies, Cooperation between business and IT extends to a global
collaboration between many business units and several entities of the IT department.
The aim of this project to developing an ERP Sales, Purchase and Inventory Management
System (SIMS) for a departmental store. This system can be used to store the details of the
inventory, stock maintenance, update the inventory based on the sale details, generate sales and
inventory reports periodically etc.This project is to categorize individual aspects for sales and
inventory managements system, in this system we are solving various problem affecting to direct
sales managed by RSM (Regional Sales Manager), ASM (Area Sales Manager) and SO(Sales
Officer) who those are monitoring our team response in term of target on various industrial
products.

1.2 PROBLEM DEFINITION

The first step of the software development life cycle is the identification of the problem
.as the success of the system depends largely on how accurately a problem is identified. The
prior process of the company details, the contact details and the customer details are maintained
without filtering process in a complicated way. And many duplicate contacts can be managed
which makes the search complicate and consuming lot of time for a particular details.
Today some application like excel sheet are generally used by many of the RSM, ASM,
SO and Distributor this system are quite tedious, time consuming and less efficient and less
accurate as comparison with the computerized system. All work are done in excel sheet because
of some times the output will not get properly and the main problem is calculation. Because of
many distributors the particular information will be handle of each and every distributor were
difficult to the SO. So this was quite tedious and time consuming.

1.3 EXISTING SYSTEM

The existing process deals with manual calculation for the customer maintenance is
difficult and also it take large time for identify customer details. It is a time consuming process to
calculate and to maintain the large amount of details.
The existing system has following disadvantages,
Does not support the newer version operating system &office suite
Does not support data migration.
Requires continuous maintenance information updating, and system upgrading
costly.
Requires additional work inputting data.

In previous software the higher authority person are enable to get detail their lower
authorized person. Then because the company target will not achieved correctly.
Following are some disadvantage use of Excel sheet:
1) Time Consuming
2) Less accurate
3) Less efficient
4) Lot of Excel sheet work
5) Slow data processing
6) Not user friendly environment
7) Difficult to keep old record.

1.4 PROPOSED SYSTEM

The proposed system is to automate sustainable customer management system. The
customer details are managed using the database.
The proposed system has following advantages,
Supports all operating system.
Make call center more efficiently.
Increases customer revenues.
Supports data migration.
Provides better customer service.
This system is developed in such way that even new users can also operate the system
easily. The calculation are made quickly and the record are directly saved into the database can
be maintain for longer period of time. Each record can be retrieved and can be verified for future
transaction. Also this system provide high level of security of data leaking for only the admin

people can access the database no changes can be made in it until the verified the user login id
and password

CHAPTER 2
SYSTEM ANALYSIS
2.1 FEASIBILITY STUDY
Technical Feasibility
Technical feasibility centers on the existing system and what is to be extended to support
the proposed system. This involves financial consideration to accommodate technical
enhancements. In this project, ASP.NET is used to develop the web application and MS-SQL is
used to create and maintain the database to overcome the drawbacks of the existing system.
Economic Feasibility
Economic feasibility deals with the analysis of costs against benefits (i,e.,) whether the
benefits to be enjoyed due to new system are worthy when compared for the costs to be spend on
the system. The cost of the system is not high when compared to the existing system. In this
project is to consider a windows based client/server system with MS-SQL Server as the backend
and ASP.NET as the front end.
Operational feasibility
The extent to which the project would fulfill the operation needed in the organization was
found to be good. The proposed system covered all the aspects of the working system and the
working model of the proposed system was also found to be at an advantage in many ways. It
was also determined that the proposed system was easy to operate with a basic knowledge.

2.2 SOFTWARE REQUIREMENT SPECIFICATION

2.2.1 SOFTWARE REQUIREMENTS

OPERATING SYSTEM

Windows 8.1

ENVIRONMENT

Visual Studio .NET 2013

NET FRAMEWORK

Version 4.0

LANGUAGE

C# .NET, ASP .NET, ANGULAR.JS

BACK END

SQL

2.2.2 HARDWARE REQUIREMENTS

PROCESSOR

Intel i5

RAM

2GB RAM

MONITOR

14 COLOR

HARD DISK SPACE

20 GB

KEYBOARD

STANDARD 102 KEYS

MOUSE

3 BUTTONS

2.2.3 LANGUAGE SPECIFICATION

C# .NET Framework is used as a front end.
ABOUT .NET FRAMEWORK
The .NET Framework is a new computing platform that simplifies application development in
the highly distributed environment of the Internet.
OBJECTIVES OF .NET FRAMEWORK

To provide a consistent object-oriented programming environment whether object codes

is stored and executed locally on Internet-distributed, or executed remotely.

To provide a code-execution environment to minimizes software deployment and

guarantees safe execution of code.

Eliminates the performance problems.

There are different types of application, such as Windows-based applications and Web-

based applications. To make communication on distributed environment to ensure that code be

accessed by the .NET Framework can integrate with any other code.

ABOUT C#.NET
C# is a general-purpose, object-oriented programming language. Its development team is
led by Anders Hejlsberg. The most recent version is C# 6.0, which was released on July 20,
2015.C# (pronounced

as see

language encompassing strong

sharp)

is

a multi-paradigm

programming

typing, imperative,declarative, functional, generic, object-

oriented (class-based), and component-oriented programming disciplines. It was developed

by Microsoft within its .NET initiative and later approved as a standard by Ecma (ECMA-334)
and ISO (ISO/IEC 23270:2006). C# is one of the programming languages designed for
the Common Language Infrastructure.

BACK END
Microsoft SQL server is a backend
Features of SQL-SERVER

Microsoft SQL Server is a relational model database server produced by Microsoft. Its
primary query languages are T-SQL and ANSI SQL.The OLAP Services feature available in
SQL Server version 10.0 is now called SQL Server 2008 Analysis Services. The term OLAP
Services has been replaced with the term Analysis Services. Analysis Services also includes a
new data mining component. The Repository component available in SQL Server version 7.0 is
now called Microsoft SQL Server 2008 Meta Data Services. References to the component now
use the term Meta Data Services. The term repository is used only in reference to the repository
engine within Meta Data Services. Microsoft SQL Server 2008 features includes internet
integration, scalability, availability, enterprise-level database features, ease of installation,
deployment, and use data warehousing.
2.2.4 TECHNICAL REQUIREMENTS
PERFORMANCE
Performance requirements define acceptable response for system functionality.The load
time for user interface screens shall talk no longer than five seconds. The verification for login
information will not take more than five seconds.
SCALABILITY
In this system administrator can add and update the details in very easy manner. This
system provides the report to the administrator within five seconds. It is a stand alone
application. Therefore it is very scalable for maintaining the computer application information
details.

SECURITY
The system verifies the username and password and then allows administrator to access
the data if only the username and password is correct otherwise it will display the error message.
It provides more security to administrator for accessing the data.
MAINTAINABILITY
This system is being developed using vb.net that support all type of datas in different
format. Therefore you will be able to maintain all datas in easy manner. Admin can able to view
the details of the instructor. Maintenance of the system is very flexible and cost effect
effectively.
AVAILABILITY
This system is available any time to access those data. The application can run without
internet connection. Any number of instructor details can store into the system at a time without
any interrupt. The system has the capacity to maintain all details.

10

CHAPTER 3
SYSTEM DESIGN
3.1 MODULE DESCRIPTION
The project entitled as ONLINE ENTERPRISE RESOURCE PLANNING is used to
The project contains the following modules:

Sales details

Purchase details

Inventory

3.1.1 SALES DETAILS:

This module provides the details of the customer which includes the contact number of
the customer, company details of the customer, email address, and the address of the customer
and also includes the description to describe the customer type in detail. The sales details include
the direct sales, sales report, sales quotation, sales return, sales order and sales delivery.

3.1.2 PURCHASE DETAILS:

This module holds the accounts of the customer. It defines the customer type and the
company type. It provides the contact details of one company and the details of the employee
who work for the company. The purchase detail includes the purchase report, purchase return,
purchase order and purchase delivery

3.1.3 INVENTORY:

11

Opportunity describes the sales prospects, their requested product and services, the sales
prospects budget, the potential sales volume and an estimated sales probability, this information
becomes concrete in the course of the sales cycle, and can be displayed and evaluated in the
system. The inventory shows the supply chain management which describes the stock maintain,
product sales and return.

3.2 DATA FLOW DIAGRAM

Admin

Login

Maintain

Sales

Sales

Purchase

Purchase

Inventory

Inventory

12

3.3 ER DIAGRAM

13

3.4 TABLE DESIGN

3.4.1 Customer Table:
COLUMN_NAME

DATA_TYPE

LENGTH

CONSTRAINT

Customer_id

Int

10

Primary key

Customer_name

Varchar

50

Not Null

Contact No

Varchar

50

Not Null

Address

Datetime

10

Not Null

Table No: 3.1 Customer details Table

3.4.2 Supplier Table:
COLUMN_NAME

DATA_TYPE

LENGTH

CONSTRAINT

Sid

Int

10

Primary key

Sname

Varchar

50

Not Null

Adrs

Varchar

50

Not Null

Cno

Datetime

10

Not Null

Mail

Varchar

50

Not Null

Table No: 3.2 Supplier details Table

14

3.4.3 Purchase Order Table:

COLUMN_NAME

DATA_TYPE

LENGTH

CONSTRAINT

Item_id

Int

10

Primary key

Req_qty

Varchar

50

Not Null

Vend_id

Varchar

50

Not Null

Req_date

Datetime

10

Not Null

Po_id

Varchar

50

Not Null

Po_date

Date

Net_amt

Varchar

Not null
20

Not null

Table No: 3.3 Purchase details Table

3.4.4 Sales Order Table:
COLUMN_NAME

DATA_TYPE

LENGTH

CONSTRAINT

Net_amt

Int

10

Primary key

Gross_amt

Varchar

50

Not Null

Price

Varchar

50

Not Null

Item_id

Datetime

10

Not Null

So_date

Date

So_no

Int

Cust_id

Varchar

50

Not Null

Table No: 3.4 Sales order details Table

3.4.5 Payment Table:

COLUMN_NAME

DATA_TYPE

LENGTH

CONSTRAINT

Pay_amt

Double

10

Primary key

Pay_date

Date

Bill_nos

Varchar

50

Not Null

Vend_id

Int

10

Not Null

Not Null

15

Table No: 3.5 Payment details Table

3.4.6 Receipt Tables:
COLUMN_NAME

DATA_TYPE

LENGTH

CONSTRAINT

Rec_amt

Int

10

Primary key

Bill_no

Varchar

50

Not Null

Cheque_dd_no

Varchar

50

Not Null

Bank_name

Datetime

10

Not Null

Rec_mode

Varchar

50

Not Null

Cust_id

int

10

Not Null

Rec_date

date

Rec_id

id

Not Null
10
Not Null

Table No: 3.6 Receipt Table

CHAPTER 4
SYSTEM TESTING
Software testing is any activity aimed at evaluating an attribute or capability of a program
or system and determining that it meets its required results. The purpose of testing is to discover
errors. It provides a way to check the functionality of components, sub-assemblies, assemblies
and/or a finished product. There are various types of test. Each test type addresses a specific
testing requirement.

4.1 UNIT TESTING

Unit testing used to verify functionality of a specific section of code. It referred as functional
testing or component testing. This functional testing helps to make sure that each module works on its
own, independent of the other unit. The test scenarios written for major modules such as user

16
authentication, account handling, admin module, contact module, customer Management,Email
Reminder,task provider, meetings and calendar. Then each scenario tested individually and outputs are
verified. Likewise we can test each and every functionality. This testing needs each module runs
independently.
Sub module such as Add account,edit account, view contacts, view tasks and meetings. These test
cases are executed when test scenarios for the major module get executed. This testing approach is helpful
to find bugs involved in any particular module easily and quickly.

4.2 INTEGRATION TESTING

Integration testing is the phase in software testing in which individual software modules
are combined and tested as a group. It occurs after unit testing and before validation testing.
Integration testing takes as its input modules that have been unit tested, groups them in larger
aggregates, applies tests defined in an integration test plan to those aggregates, and delivers as its
output the integrated system ready for system testing.
The modules developed are integrated with each other and tested. After integration it is
worked as expected and will provide the predefined output.

4.3 VALIDATION TESTING

Validation Testing is the different set of activities which ensures that the software that has
been built is traceable to the client requirements.
In entry screens, Admin Name, Mobile Number, Account id and ticker symbol and dates
are validated individually. All the text box fields are checked thoroughly with various given
inputs.

4.4 TEST CASES

The project is integrated and tested very carefully so that it meets the system
requirements as intended.The test cases for which this condition must be met are:

When customer logged in the application, there should validate their email id.

17

The mail will be send to the registered user if they need to know about the offer details.
Try to insert already inserted field or row, error message will be shown.
There may have a chance to enter invalid data instead of number, it shows a message.
The system should trigger a constraint for the date, which has date format like DD-MM-

YY.
While pressing button without selecting list of options from the views, it shows an error

message and reload the same page again.

If it has no data in database, the message will be shown in the loading page.

4.5 TEST CASE

Test Case
ID

Test Objective

Test Data

Expected
Result

Actual Result

Test Result

TC_001

Check User
name

Demo

Accept

Accept

Pass

TC_002

Check User
name

Demo

Show error

Show error
(Invalid username)

Failed

TC_003

Check User
name

Demo12

Show error

Show error
(Invalid username)

Failed

TC_004

Check User
name

NULL

Show error

Show error
(Enter user name)

Failed

TC_005

Check
Password

NULL

Show error

Show error
(Enter password)

Failed

TC_006

Check
password

*****(correct
password match for
user name)

Successfully
login

Successfully login

Pass

TC_007

Item name

Select from

Accepts

Accepts

Pass

18

Dropdown
TC_008

Item name

NULL

Show error

Show error
Failed

TC_009

Select Store

Select value from

dropdown

Accept

Accept

Pass

TC_010

Select Store

NULL

Show error

Show error

Failed

TC_011

Tax Form

Select option from

dropdown

Accept

Accept

Pass

TC_012

Tax Form

NULL

Show error

Show error

Failed

TC_013

Save

On click the save

button
(After filling all
data)

Accept

Saved
Successfully

Pass

TC_014

Save

On click the save

button
(if incomplete form)

Show error

Show error

Failed

CHAPTER 5
SYSTEM IMPLEMENTATION
Implementation is the stage in the project where the theoretical design is turned into
working system. This is the most crucial stage in achieving a new successful system and in
giving confidence of the new system for the users that it will work efficiently. Implementation of
software refers to the final installation of the package in its real environment, to the satisfaction
of the intended users and the operations of the system. In many organizations someone who will
not be operating it, will commission the software development project. The people who are not
sure that the software is meant to make their job easier. In the initial stage they doubt their
software but we have to ensure that the resistance does not build up as

The active user must be aware of the benefits of using the system.
Their confidence in the software is build up.

Proper guidance is imparted to the user so that he is comfortable in using

the application.

5.1 Implementation of Code

19

Coding starts immediately after design phase. Coding is the conversion of the abstract designs to
clear-cut programs, which confirms the user specification. Using the code design rules the code
is implemented.

5.1.1 Steps Involved in Deployment

Integrate all scenarios that are developed as an exe file

Install the Microsoft visual studio2010
Execute the exe file in the Microsoft visual studio2010
Install the SQL server and connected to the exe file
Thus the automation software deployed and found to work properly

CHAPTER 6
CONCLUSION & FUTURE ENHANCEMENT
6.1 CONCLUSION
The customer relation management system manages all the record of the company in the
systematic manner. The admin can add, update, delete accounts and records in the database and
status of the company such as calls and meetings are viewed easily for particular days by
calendar. This system is highly interactive and user friendly .Report generation satisfies the user
requirements to the maximum extent possible. The system provides accurate data updating, data
validation, and integrity.
The system has been designed and developed according to the current requirements of the
user, which may subject to the changes in the near future. The system can be upgraded all
modifications can be incorporated in a flexible manner so as to reflect the new requirements.

6.2 FUTURE ENHANCEMENT

The project provides a best support to interact between system and user.The
application become useful if the below enhancement are made in future.

20

The customer can easily know about the shares provided by the company.A forum can
be created so that the customer can discuss their queries about the shares with the
company members.

APPENDICES

A. SAMPLE CODE:
using MixERP.Net.ApplicationState.Cache;
using MixERP.Net.Common;
using MixERP.Net.Common.Helpers;
using MixERP.Net.Entities.Office;
using MixERP.Net.FrontEnd.Data.Helpers;
using MixERP.Net.FrontEnd.Data.Office;
using MixERP.Net.i18n;
using MixERP.Net.i18n.Resources;
using Serilog;
using System;
using System.Collections.Generic;
using System.Collections.ObjectModel;
using System.Globalization;
using System.Linq;
using System.Web.UI;
using System.Web.UI.HtmlControls;
using System.Web.UI.WebControls;
namespace MixERP.Net.FrontEnd
{
public partial class SignIn : Page

21

{
protected void Page_Init(object sender, EventArgs e)
{
using (HtmlLink stylesheet = new HtmlLink())
{
string path = "";
if (CultureManager.IsRtl())
{
path = path.Replace("css", "");
}
stylesheet.Href = path;
stylesheet.Attributes["rel"] = "stylesheet";
stylesheet.Attributes["type"] = "text/css";
stylesheet.Attributes["media"] = "all";
this.Page.Header.Controls.Add(stylesheet);
}
this.CreateControls(this.Placeholder1);
this.CreateDimmer(this.Placeholder1);
this.AddJavascript();
}
protected void Page_Load(object sender, EventArgs e)
{
this.CheckDbConnectivity();
PageUtility.CheckInvalidAttempts(this.Page);
if (this.branchSelect.Items.Count.Equals(0))
{
this.Response.Redirect("~/Installation/Default.aspx");
}
if (!this.IsPostBack)
{
if (this.User.Identity.IsAuthenticated)
{
long globalLoginId = Conversion.TryCastLong(this.User.Identity.Name);
if (globalLoginId > 0)
{
AppUsers.SetCurrentLogin();
this.RedirectToDashboard();
}
}

22

}
}
private void BindCompanies()
{
string catalogs = ConfigurationHelper.GetDbServerParameter("Catalogs");
string defaultCatalog = AppUsers.GetCurrentUserDB();
if (!string.IsNullOrWhiteSpace(catalogs))
{
List<string> list = catalogs.Split(',').Select(p => p.Trim()).ToList();
this.companySelect.DataSource = list;
this.companySelect.DataBind();
this.companySelect.SelectedValue = defaultCatalog;
}
}
private void BindBranches()
{
try
{
this.BindBranchDropDownList();
}
catch
{
//Could not bind the branch office dropdownlist.
//The target database does not contain mixerp schema.
//Swallow the exception
//and redirect to application offline page.
this.RedirectToOfflinePage();
}
}
private void BindBranchDropDownList()
{
IEnumerable<DbGetOfficesResult> offices =
Offices.GetOffices(AppUsers.GetCurrentUserDB());
this.branchSelect.DataSource = offices;
this.branchSelect.DataBind();
}
private void CheckDbConnectivity()
{

23

Log.Verbose("Checking if database server is available.");

if (!ServerConnectivity.IsDbServerAvailable(AppUsers.GetCurrentUserDB()))
{
Log.Warning("Could not connect to database server.");
this.RedirectToOfflinePage();
}
}
private void RedirectToDashboard()
{
this.Response.Redirect("~/Modules/Sales/DirectSales.mix?View=grid", true);
}
private void RedirectToOfflinePage()
{
Log.Debug("Redirecting to offline page.");
this.Response.Redirect("~/Site/offline.html");
}
private void AddJavascript()
{
string challenge = Guid.NewGuid().ToString().Replace("-", "");
this.Session["Challenge"] = challenge;
string script = JSUtility.GetVar("challenge", challenge);
script += JSUtility.GetVar("shortDateFormat", CultureManager.GetShortDateFormat());
script += JSUtility.GetVar("thousandSeparator",
CultureManager.GetThousandSeparator());
script += JSUtility.GetVar("decimalSeparator", CultureManager.GetDecimalSeparator());
script += JSUtility.GetVar("currencyDecimalPlaces",
CultureManager.GetCurrencyDecimalPlaces());
PageUtility.RegisterJavascript("SignInPage_Vars", script, this.Page, true);
}
#region IDispoable
private bool disposed;
private HtmlSelect branchSelect;
private DropDownList companySelect;
public override sealed void Dispose()
{
if (!this.disposed)

24

{
this.Dispose(true);
GC.SuppressFinalize(this);
base.Dispose();
}
}
protected virtual void Dispose(bool disposing)
{
if (!disposing)
{
return;
}
if (this.branchSelect != null)
{
this.branchSelect.Dispose();
this.branchSelect = null;
}
if (this.companySelect != null)
{
this.companySelect.Dispose();
this.companySelect = null;
}
this.disposed = true;
}
#endregion
#region Controls
private void CreateDimmer(Control container)
{
using (HtmlGenericControl pageDimmer = new HtmlGenericControl("div"))
{
pageDimmer.Attributes.Add("class", "ui page dimmer");
using (HtmlGenericControl content = new HtmlGenericControl("div"))
{
content.Attributes.Add("class", "content");
using (HtmlGenericControl center = new HtmlGenericControl("div"))
{
center.Attributes.Add("class", "center");

25

using (HtmlGenericControl header = new HtmlGenericControl("div"))

{
header.Attributes.Add("class", "ui yellow huge icon header");
using (HtmlGenericControl icon = new HtmlGenericControl("i"))
{
icon.Attributes.Add("class", "ui inverted yellow setting loading icon");
header.Controls.Add(icon);
}
using (Literal literal = new Literal())
{
literal.Text = Titles.SigningIn;
header.Controls.Add(literal);
}
using (HtmlGenericControl subHeader = new HtmlGenericControl("div"))
{
subHeader.Attributes.Add("class", "ui yellow sub header");
subHeader.InnerText = Labels.JustAMomentPlease;
header.Controls.Add(subHeader);
}
center.Controls.Add(header);
}
content.Controls.Add(center);
}
pageDimmer.Controls.Add(content);
}
container.Controls.Add(pageDimmer);
}
}
private void CreateControls(Control container)
{
using (HtmlGenericControl signInForm = new HtmlGenericControl("div"))
{
signInForm.Attributes.Add("id", "signin-form");
this.CreateLogo(signInForm);
this.CreateForm(signInForm);

26

container.Controls.Add(signInForm);
}
}

#region Form

private static void AddExceptionField(HtmlGenericControl container)

{
using (HtmlGenericControl exceptionField = new HtmlGenericControl("div"))
{
exceptionField.Attributes.Add("class", "exception field");
container.Controls.Add(exceptionField);
}
}

private static void AddPasswordField(HtmlGenericControl container)

{
using (HtmlGenericControl field = new HtmlGenericControl("div"))
{
field.Attributes.Add("class", "field");
using (HtmlGenericControl label = HtmlControlHelper.GetLabel(Titles.Password,
"PasswordInputPassword"))
{
field.Controls.Add(label);
}
using (HtmlInputPassword passwordInputPassword = new HtmlInputPassword())
{
passwordInputPassword.ID = "PasswordInputPassword";
passwordInputPassword.Attributes.Add("placeholder", Titles.Password);
field.Controls.Add(passwordInputPassword);
}
container.Controls.Add(field);
}
}
private static void AddRememberMeField(HtmlGenericControl container)
{
using (HtmlGenericControl field = new HtmlGenericControl("div"))

27

{
field.Attributes.Add("class", "field");
using (HtmlGenericControl toggleCheckBox = new HtmlGenericControl("div"))
{
toggleCheckBox.Attributes.Add("class", "ui toggle checkbox");
using (HtmlInputCheckBox rememberInputCheckBox = new
HtmlInputCheckBox())
{
rememberInputCheckBox.ID = "RememberInputCheckBox";
toggleCheckBox.Controls.Add(rememberInputCheckBox);
}
using (HtmlGenericControl label =
HtmlControlHelper.GetLabel(Titles.RememberMe))
{
toggleCheckBox.Controls.Add(label);
}
field.Controls.Add(toggleCheckBox);
}
container.Controls.Add(field);
}
}
private static void AddSignInButtonField(HtmlGenericControl container)
{
using (HtmlGenericControl field = new HtmlGenericControl("div"))
{
field.Attributes.Add("class", "field");
using (HtmlInputButton signInButton = new HtmlInputButton())
{
signInButton.ID = "SignInButton";
signInButton.Value = Titles.SignIn;
signInButton.Attributes.Add("title", "CRTL + RETURN");
signInButton.Attributes.Add("class", "ui teal button");
field.Controls.Add(signInButton);
}
container.Controls.Add(field);

28

}
}
private static void AddUserIdField(HtmlGenericControl container)
{
using (HtmlGenericControl field = new HtmlGenericControl("div"))
{
field.Attributes.Add("class", "field");
using (HtmlGenericControl label = HtmlControlHelper.GetLabel(Titles.UserId,
"UsernameInputText"))
{
field.Controls.Add(label);
}
using (HtmlInputText usernameInputText = new HtmlInputText())
{
usernameInputText.ID = "UsernameInputText";
usernameInputText.Attributes.Add("placeholder", Titles.UserId);
usernameInputText.Attributes.Add("autocapitalize", "off");
usernameInputText.Attributes.Add("autocorrect", "off");
field.Controls.Add(usernameInputText);
container.Controls.Add(field);
}
}
}
private void CreateForm(HtmlGenericControl container)
{
using (HtmlGenericControl form = new HtmlGenericControl("div"))
{
form.Attributes.Add("class", "ui form segment");
form.Attributes.Add("style", "padding:24px 48px;");
CreateHeader(form);
AddUserIdField(form);
AddPasswordField(form);
AddRememberMeField(form);
AddExceptionField(form);
AddSignInButtonField(form);
container.Controls.Add(form);
}
}

29

private static void CreateHeader(HtmlGenericControl container)

{
using (HtmlGenericControl header = new HtmlGenericControl("div"))
{
header.Attributes.Add("class", "ui large header");
header.Attributes.Add("style", "8px 0;");
header.InnerText = Titles.SignIn;
container.Controls.Add(header);
}
}
private static Collection<ListItem> GetLanguages()
{
string[] cultures = ConfigurationHelper.GetParameter("Cultures").Split(',');
Collection<ListItem> items = new Collection<ListItem>();
foreach (string culture in cultures)
{
string cultureName = culture.Trim();
foreach (
CultureInfo infos in
CultureInfo.GetCultures(CultureTypes.AllCultures)
.Where(x => x.TwoLetterISOLanguageName.Equals(cultureName)))
{
items.Add(new ListItem(infos.NativeName, infos.Name));
}
}
return items;
}
#endregion
#endregion
}
}

30

B SCREENSHOTS
LOGIN PAGE:

Figure: B.1 Login page

31

DIRECTSALE:

Figure: B.2 Direct sale page

32

Sales Quatation Page:

Figure: B.3 Sales Quatation page

33

Sales Order Page:

Figure: B.4 Sales order page

34

Sales Delivery Page:

Figure: B.5 Sales delivery page

35

Direct Purchase Page:

Figure: B.6 Direct purchase page

36

Purchase Order:

Figure: B.7 Purchase order page

37

Goods Receipt Node Page:

Figure: B.8 Goods receipt node page

38

Stock Transfer Journal Page:

Figure: B.9 Stock transfer journal page

39

StoreType Page:

Figure: B.10 Store Type page

40

Account Statement Page:

Figure: B.11 Account statement page

41

REFERENCES
BOOKS
Beginning ASP.NET 4: in C# and VB, by ImarSpaanjaars.
Professional ASP.NET 4 in C# and VB, by Bill Evjen,
Scott Hanselman, Devin Rader.
jQuery for ASP.NET Developers, by Joe Brinkman.

WEBSITES
http://w3.school.com/asp.net
http://w3.school.com/c#.net

42

http://www.asp.net/web-forms
https://www.sugarcrm.com
https://msdn.microsoft.com/en-us/library/gg328261.aspx