Sunteți pe pagina 1din 90

Central Excise Operation of a Manufacturing Unit

1.1 SYNOPSIS
The Objective of this document is to study and analyze the automation of Central
Excise operations of manufacturing unit in general. CENEX is the Central Excise
Software that aims to take care of all the statutory registers and returns required under the
Central Excise Act and Rules.
The materials purchased by the Manufacturer from his supplier are referred as
Inputs. A document is prepared namely GRN. (Goods Receipt Note) This document
contains all the details of the suppliers invoice and allows the materials in i.e. to the
stores. From stores these materials are directed for production. This GRN is shown to the
Excise authorities. Since it is the receipt of material for production the duty paid against
those materials are treated as material credit
The major change as far as service tax is concerned is that the Supreme Court
Judgment has now been over ruled by amending the law with retrospective effect. The
Central Excise Department can now recover service-tax collected by the users of the
services.
With the result no refund of service-tax paid on the services of goods transport
operators and clearing and forwarding agent would be granted.
A document is prepared namely GRN. (Goods Receipt Note) This document
contains all the details of the suppliers invoice and allows the materials in i.e. to the
stores. From stores these materials are directed for production. This GRN is shown to the
Excise authorities. Since it is the receipt of material for production the duty paid against
those materials are treated as material credit

Central Excise Operation of a Manufacturing Unit

2 ORGANIZATION PROFILE
SRM SOFTSOLUTIONS AND SOFTWARE is a company committed to provide
support to small, medium and large corporations in the development and management of
software essential to their needs over the entire life cycle of a project or system. All
corporations, regardless of size, need to process enormous amounts of data in support of
the day-to-day operation of the company and the dependence on a corporate information
system and up-grade the existing ones. In seeking efficient and cost-effective approaches
to manage change, many companies have found outsourcing to be particularly attractive.
SRM SOFTSOLUTIONS AND SOFTWARE Private Limited has been
established in 1998 with the objective of providing software solutions to the Domestic
and Export markets as well as for developing highly skilled manpower in specialized
areas of Information Technology promoted by a group of highly qualified Engineering
Managers. SRM has its offices at Austin, Boston, Chennai, and in Delhi. Equipped with
the latest Computing Hardware and Software backed by skilled manpower.
SRM provides comprehensive solutions for the industry software development
needs on turnkey basis. The accent of SRM is not merely on new and emerging
technologies. IT professional are more concerned with providing its clients reliable,
flexible and maintainable solutions to their business problem. SRM realizes that the
watchwords of yesterday Leading Edge Technology need to be tempered in favor of
cost containment.
SRM SOFTSOLUTIONS AND SOFTWARE is here to provide expert services
and support for change management in software systems allowing your organization to
focus on its core business. SRM Systems and Software offers the expertise of
experienced individual software consultants, as well as an off - shore facility with a stateof-the-art information technology infrastructure and a well trained and committed staff.
2

Central Excise Operation of a Manufacturing Unit

We at SRM provide our clients the potential for significant savings without
compromises in quality or schedule.

SRM SOFTSOLUTIONS AND SOFTWARE

guarantees that the software services will be delivered to the customer on time, within
budge, in complete conformance means that at SRM, we are indeed Determined to
Make a Difference.

Services Offered
SRM SOFTSOLUTIONS AND SOFTWARE through its Strategic Business Units
offers the following services.

Customized Software Development

Consultancy Services

Corporate training Services

Product Development:

Human Resource Development

Central Excise Operation of a Manufacturing Unit

3.1 SYSTEM CONFIGURATION


HARDWARE CONFIGURATION:
Processor

Pentium IV

RAM

512MB

Monitor size

17SVGA

Extra Device

CD-ROM 52x

Operating System

Windows XP

Keyboard

104 standards Keyboard

SOFTWARE CONFIGURATION:
Operating System

Windows XP Professional

Environment

Visual Studio .Net 2005

.Net Framework

Version 2.0

Language

C#.Net

Web Technology

Active Server Pages.Net

Web Server

Internet information Server 5.0

Back End

Sql Server 2000

Central Excise Operation of a Manufacturing Unit

3.2 ABOUT WINDOWS XP


Windows XP is an operating system that was produced by Microsoft for use on
personal computers, including home and business desktops, laptops, and media centers. It
was first released in August 2001, and is the most popular version of Windows, based on
installed user base. The name "XP" is short for "eXPerience."
Windows XP was the successor to both Windows 2000 and, and was the first
consumer-oriented operating system produced by Microsoft to be built on the and.
Windows XP was released for retail sale on October 25, 2001, and over 400 million
copies were in use in January 2006, according to an estimate in that month by an analyst.
It was succeeded by , which was released to volume license customers on November 8,
2006, and worldwide to the general public on January 30, 2007. Direct and retail sales of
Windows XP ceased on June 30, 2008. Microsoft continued to sell Windows XP through
their System Builders (smaller OEMs who sell assembled computers) program until
January 31, 2009. XP may continue to be available as these sources run through their
inventory or by purchasing Windows 7 Ultimate, Windows 7 Pro, Windows Vista
Ultimate or Windows Vista Business, and then to Windows XP.
The most common editions of the operating system were Windows XP Home Edition,
which was targeted at home users, and Windows XP Professional, which offered
additional features such as support for and , and was targeted at , business and enterprise
clients has additional multimedia features enhancing the ability to record and watch TV
shows, view DVD movies, and listen to music. Was designed to run stylus applications
built using the platform.
Windows XP was eventually released for two additional architectures, for ()
processors and for. There is also, a component version of the Windows XP Professional,
5

Central Excise Operation of a Manufacturing Unit


and editions for specific markets such as Windows XP Starter Edition. By mid 2009, a
manufacturer revealed the first Windows XP powered cellular telephone.
The -based versions of Windows, which are programmed in, and, are known for their
improved stability and efficiency over the versions of. Windows XP presented a
significantly redesigned, a change Microsoft promoted as more user-friendly than
previous versions of Windows. A new software management facility called was
introduced to ameliorate the "" that plagues 9x versions of Windows. It is also the first
version of Windows to use to combat. Windows XP had also been criticized by some
users for security vulnerabilities, tight integration of applications such as and, and for
aspects of its default user interface. Later versions with, and addressed some of these
concerns.
During development, the Whistler", after, as many Microsoft employees skied at the
ski resort.
According to data generated by, as of December 2010, Windows XP is the most
widely used operating system for accessing the Internet in the world with a 47.2% market
share, having peaked at 76.1% in January 2007
Windows XP featured a new task-based graphical user interface. The Start menu and
Taskbar were updated and many visual effects were added, including:

A translucent blue selection rectangle in Explorer

Drop shadows for icon labels on the desktop

Task-based sidebars in Explorer windows ("common tasks")

The ability to group the taskbar buttons of the windows of one application into
one button

The ability to lock the taskbar and other toolbars to prevent accidental changes

The highlighting of recently added programs on the Start menu

Shadows under menus (Windows 2000 had shadows under mouse pointers, but
not menus)

Central Excise Operation of a Manufacturing Unit


Windows XP analyzed the performance impact of visual effects and uses this to
determine whether to enable them, so as to prevent the new functionality from consuming
excessive additional processing overhead. Users can further customize these settings.
Some effects, such as (transparency and fading), are handled entirely by many newer
video cards. However, if the video card is not capable of hardware alpha blending,
performance can be substantially hurt, and Microsoft recommends the feature should be
turned off manually. Windows XP added the ability for Windows to use "Visual Styles" to
change the user interface. However, visual styles must be cryptographically signed by
Microsoft to run. Is the name of the new visual style that ships with Windows XP, and is
enabled by default for machines with more than 64 of? Luna refers only to one particular
visual style, not to all of the new user interface features of Windows XP as a whole. Some
users "patch" the uxtheme.dll file that restricts the ability to use visual styles, created by
the general public or the user, on Windows XP.
In addition to the included Windows XP themes, there is one previously
unreleased theme with a dark blue taskbar and window bars similar to Windows Vista
titled "" available for download, albeit unofficially. Microsoft officially released a
modified version of this theme as the "" theme, to celebrate the launch of its Zune
portable media player in November 2006. The differences are only visual with a new
glassy look along with a black taskbar instead of dark blue and an orange start button
instead of green. Additionally, the Media Center "" theme, which was included in the
Media Center editions, is also available to download for use on all Windows XP editions.
The default wallpaper, is a photograph of a landscape in the outside, with rolling
green hills and a blue sky with and.
The Windows 2000 "classic" interface can be used instead if preferred. Several
third party utilities exist that provide hundreds of different visual styles.

New and updated features

Central Excise Operation of a Manufacturing Unit


Main article:
Windows XP introduced several new features to the Windows line, including:

graphics subsystem

and improvements

A number of new features in

Faster start-up, logon and logoff and sequences.

The ability to discard a newer in favor of the previous one (known as driver
rollback), should a driver upgrade not produce desirable results.

A new, arguably more user-friendly interface, including the framework for


developing for the desktop environment

which allows a user to save the current state and open applications of their
desktop and allow another user to log on without losing that information

The font rendering mechanism, which is designed to improve text readability on


(LCD) and similar monitors

Remote Desktop functionality, which allows users to connect to a computer


running Windows XP Pro from across a network or the and access their
applications, files, printers, and devices.

Support for most modems and connections, as well as networking over, and.

Improved application compatibility compared to Windows 2000

Editions
Main article:

Central Excise Operation of a Manufacturing Unit


Diagram representing the main editions of Windows XP. It is based on the
category of the edition (grey) and code base (black arrow).
The two major editions are Windows XP Home Edition, designed for home users,
and Windows XP Professional, designed for business and power-users. XP Professional
contains advanced features that the average home user would not use. However, these
features are not necessarily missing from XP Home. They are simply disabled, but are
there and can become functional. These releases were made available at retail outlets that
sell computer software, and were preinstalled on computers sold by major computer
manufacturers. As of mid-2008, both editions continue to be sold. A third edition, called
Windows XP Media Center Edition was introduced in 2002 and was updated every year
until 2006 to incorporate new digital media, broadcast television and capabilities. Unlike
the Home and Professional edition, it was never made available for retail purchase, and
was typically either sold through channels, or was preinstalled on computers that were
typically marketed as "media center PCs".
Two different editions were made available, one designed specifically for
Itanium-based workstations, which was introduced in 2001 around the same time as the
Home and Professional editions, but was discontinued a few years later when vendors of
Itanium hardware stopped selling workstation-class machines due to low sales. The other,
called Windows XP Professional x64 Edition supports the x86-64 extension. x86-64 was
implemented first by AMD as "AMD64", found in AMD's

and

chips, and later

implemented by Intel as "" (formerly known as IA-32e and EM64T), found in Intel's and
later chips.
Windows XP Tablet PC Edition was produced for a class of specially designed
notebook/laptop computers called. It is compatible with a pen-sensitive screen,
supporting handwritten notes and portrait-oriented screens.

Central Excise Operation of a Manufacturing Unit

Internet Explorer 6 running in Windows XP Tablet PC Edition


Microsoft also released, an edition for specific consumer electronics, kiosks/,
medical devices, arcade video games, point-of-sale terminals, and Voice over Internet
Protocol () components. In July 2006, Microsoft released a version of Windows XP
Embedded which targets older machines (as early as the original Pentium). It is only
available to customers. It is intended for corporate customers who would like to upgrade
to Windows XP to take advantage of its security and management capabilities, but can't
afford to purchase new hardware.
Editions for specific markets
Is a lower-cost edition of Windows XP available in Thailand, Indonesia,
Philippines, Russia, India, Colombia, Brazil, Argentina, Peru, Bolivia, Chile, Mexico,
Ecuador, Uruguay and Venezuela? It is similar to Windows XP Home, but is limited to
low-end hardware, can only run 3 programs at a time, and has some other features either
removed or disabled by default. Each country's edition is also customized for that
country, including desktop backgrounds of popular locations, help features for those who
may not speak English, and other default settings designed for easier use than typical
Windows XP installations. The Malaysian version, for example, contains a desktop
background of the skyline.
10

Central Excise Operation of a Manufacturing Unit


In March 2004, the fined Microsoft 497 million (US$603 million) and ordered
the company to provide a version of Windows without. The Commission concluded that
Microsoft "broke competition law by leveraging its near in the market for PC operating
systems onto the markets for work group operating systems and for media players". After
unsuccessful appeals in 2004 and 2005, Microsoft reached an agreement with the
Commission where it would release a court-compliant version, Windows XP Edition N.
This version does not include the company's Windows Media Player but instead
encourages users to pick and download their own media player. Microsoft wanted to call
this version Reduced Media Edition, but EU regulators objected and suggested the
Edition N name, with the N signifying "not with Media Player" for both Home and
Professional editions of Windows XP. Because it is sold at the same price as the version
with Windows Media Player included, and have chosen not to stock the product.
However, Dell did offer the operating system for a short time. Consumer interest has been
low, with roughly 1,500 units shipped to, and no reported sales to consumers.
In December 2005, the ordered Microsoft to make available editions of Windows
XP and that do not contain or. Like the European Commission decision, this decision was
based on the grounds that Microsoft had abused its dominant position in the market to
push other products onto consumers. Unlike that decision, however, Microsoft was also
forced to withdraw the non-compliant versions of Windows from the South Korean
market. This decision resulted in Microsoft's releasing "K" and "KN" variants of the
Home and Professional editions in August 2006.
That same year, Microsoft also released two additional editions of Windows XP
Home Edition directed towards subscription-based and pay-as-you-go pricing models.
These editions, released as part of Microsofts initiative, are used in conjunction with a
hardware component to enforce time limitations on the usage of Windows. Its target
market is emerging economies such as Brazil and Vietnam.
Languages
Windows XP was available in many languages. In addition, packs and translating
the user interface were also available for certain languages.
11

Central Excise Operation of a Manufacturing Unit


ATMs and Vendors
(ATM) vendors, and have all adopted Microsoft Windows XP as their migration
path from. Wincor Nixdorf, who has been pushing for standardization for many years,
began shipping ATMs with Windows when they first arrived on the scene.
Diebold initially shipped XP Home Edition exclusively, but, following extensive
pressure from customer banks to support a common operating system, switched to
support XP Professional to match their primary competitor, NCR Corporation and Wincor
Nixdorf.
Vending machines run a modified version of XP designed for the full screen of the
Vending Touch screen and the DVD vending itself.
Service packs
Microsoft occasionally releases for its Windows operating systems to fix
problems and add features. Each service pack is a superset of all previous service packs
and patches so that only the latest service pack needs to be installed, and also includes
new revisions. However if you still have the earliest version of Windows XP on Retail
CD (without any service packs included), you will need to install SP1a or SP2, before
SP3 can be installed. Older service packs need not be manually removed before
application of the most recent one. Windows Update "normally" takes care of
automatically removing unnecessary files.
The service pack details below only apply to the 32-bit editions. Windows XP
Professional x64 Edition was based on Service Pack 1 and claimed to be "SP1" in system
properties from the initial release. It is updated by the same service packs and hot fixes as
the x64 edition of Windows Server 2003

12

Central Excise Operation of a Manufacturing Unit

3.3 Database Management System (DBMS)


A Database Management System (DBMS) is a set of that controls the creation,
maintenance, and the use of a. It allows organizations to place control of database
development in the hands of (DBA) and other specialists. A DBMS is a system software
package that helps the use of integrated collection of data records and files known as
databases. It allows different user application programs to easily access the same
database. DBMS may use any of a variety of the large systems, a DBMS allows users and
other software to store and retrieve data in a way.
Instead of having to write computer programs to extract information, user can ask
simple questions in a. Thus, many DBMS packages provide (4GLs) and other application
development features. It helps to specify the logical organization for a database and
access and use the information within a database. It provides facilities for controlling,
enforcing, managing concurrency, and restoring the database from backups. A DBMS
also provides the ability to logically present database information to users.
A DBMS is a set of that controls the, management, and of in a. DBMS are
categorized according to their data structures or types. The DBMS accepts requests for
data from an application program and instructs to the transfer the appropriate data. The
responses must be submitted and received according to a format that conforms to one or
more applicable protocols. When a DBMS is used, can be changed more easily as the
organization's information requirements change. New categories of data can be added to
the database without disruption to the existing system.
Database servers are dedicated computers that hold the actual databases and run
only the DBMS and related software. Database servers are usually computers, with
generous memory and

disk arrays used for stable storage. Hardware database

accelerators, connected to one or more servers via a high-speed channel, are also used in
large volume transaction processing environments. DBMS are found at the heart of most.

13

Central Excise Operation of a Manufacturing Unit

Relational database management system (RDBMS)


A relational database management system (RDBMS) is a (DBMS) that is based
on the as introduced by. Most popular commercial and open source databases currently
in use are based on the relational database model.
A short definition of an RDBMS may be a DBMS in which data is stored in the form
of tables and the relationship among the data is also stored in the form of tables.
E. F. Codd introduced the term in his paper, published in 1970. In this paper and later
papers he defined what he meant by relational. One well-known definition of what
constitutes a relational database system is. However, many of the early implementations
of the relational model did not conform to all of Codd's rules, so the term gradually came
to describe a broader class of database systems. At a minimum, these systems:

presented the data to the user as

(a presentation in tabular form, i.e. as a

collection of with each table consisting of a set of rows and columns, can satisfy
this property)

provided relational operators to manipulate the data in tabular form

The first systems that were relatively faithful implementations of the relational model
were from the University of Michigan; (1969) and from IBM UK Scientific Centre at
Pete lee; (197072) and its follow on (197379). The first system sold as an RDBMS
was, first sold in 1978. Others have been and.
The most popular definition of an RDBMS is a product that presents a view of
data as a collection of rows and columns, even if it is not based strictly upon. By this
definition, RDBMS products typically implement some but not all of Codd's 12 rules.

14

Central Excise Operation of a Manufacturing Unit


A second, theory-based school of thought argues that if a database does not
implement all of Codd's rules (or the current understanding on the relational model, as
expressed and others), it is not relational. This view, shared by many theorists and other
strict adherents to Codd's principles, would disqualify most DBMS as not relational. For
clarification, they often refer to some RDBMS as Truly-Relational Database Management
Systems (TRDBMS), naming others Pseudo-Relational Database Management Systems
(PRDBMS).
As of 2009, most commercial relational DBMS employ as their. Alternative query
languages have been proposed and implemented, notably the pre-1996 implementation of
Berkeley Ingres QUEL.

15

Central Excise Operation of a Manufacturing Unit

3.4 ABOUT ASP.NET


INTRODUCTION OF VISUAL STUDIO:
In 2002, Visual Studio took the biggest leap in innovation since it was released,
with the introduction of Visual Basic .NET (as it was renamed). After more than a
decade, Visual Basic was overdue for a major overhaul. But .NET goes beyond an
overhaul. It changes almost every aspect of software development. From integrating
Internet functionality to creating object-oriented frameworks, Visual Basic .NET
challenged traditional VB developers to learn dramatic new concepts and techniques.
2005 brings us an enhanced Visual Basic language (renamed this time Visual
Basic 2005). New features have been added that cement this languages position as a true
object-oriented language. With Visual Basic 2005, it is still going to be a challenge for the
traditional VB6 developers to learn, but it is an easy road and books like this are here to
help you on your path.
First, its necessary to learn the differences between Visual Basic 2005 and the
older versions. In some cases, the same functionality is implemented in a different way.
This was not done arbitrarilythere are good reasons for the changes. But you must be
prepared to unlearn old habits and form new ones.
Next, you must be open to the new concepts. Full object orientation, new component
techniques, new visual tools for both local and Internet interfacesall of these and more
must become part of your skill

THE IMPORTANCE OF VISUAL BASIC


Early in the adoption cycle of .NET, Microsofts new language, C#, got the lions
share of attention. But as .NET adoption has increased, Visual Basics continuing
importance has also been apparent. Microsoft
has publicly stated that they consider Visual Basic the language of choice for applications
where developer productivity is one of the highest priorities.
16

Central Excise Operation of a Manufacturing Unit


Future development of Visual Basic is emphasizing capabilities that enable access
to the whole expanse of the .NET Framework in the most productive way, while C#
development is emphasizing the experience of writing code. That fits the traditional role
of Visual Basic as the language developers use in the real world to create business
applications as quickly as possible.
This difference is more than academic. One of the most important advantages of
the .NET Framework is that it allows applications to be written with dramatically less
code. In the world of business applications, the goal is to concentrate on writing business
logic and to eliminate routine coding tasks as much as possible. The value in this new
world is not in churning out lots of codeit is in writing robust, useful applications with
as little code as possible.

An Overview of the .NET Framework


First and foremost, .NET is a framework that covers all the layers of software
development above the operating system level. It provides the richest level of integration
among presentation technologies, component Technologies and data technologies ever
seen on a Microsoft, or perhaps any, platform. Second, the entire architecture has been
created to make it as easy to develop Internet applications as it is to develop for the
desktop.
The .NET Framework actually wraps the operating system, insulating software
developed with .NET from most operating system specifics such as file handling and
memory allocation. This prepares for a possible future in which the software developed
for .NET is portable to a wide variety of hardware and operating system foundations.
VS.NET supports Windows 2003, Windows XP, and all versions of Windows
2000. Programs created for .NET can also run under Windows NT, Windows 98, and
Windows Me, though VS.NET does not run on these systems. Note that in some cases
certain service packs are required to run .NET.

17

Central Excise Operation of a Manufacturing Unit


The framework starts all the way down at the memory management and
component loading level and goes all the way up to multiple ways of rendering user and
program interfaces. In between, there are layers that provide just about any system-level
capability that a developer would need.

Microsoft .NET
At the base is the common language runtime, often abbreviated to CLR. This is
the heart of the .NET Framework it is the engine that drives key functionality. It includes,
for example, a common system of data types. These common types, plus a standard
interface convention, make cross-language inheritance possible. In addition to allocation
and management of memory, the CLR also does reference tracking for objects and
handles garbage collection.
The middle layer includes the next generation of standard system Services such as
classes that manage data and Extensible Markup Language (XML). These services are
brought under control of the Framework, making them universally available and making
their usage consistent across languages.
The top layer includes user and program interfaces. Windows Forms is a new and
more advanced way to do standard Win32 screens (often referred to as smart clients).
Web Forms provides a new Web-based user interface. Perhaps the most revolutionary is
Web Services, which provide a mechanism for programs to communicate over the
Internet, using SOAP. Web Services provide an analog of COM and DCOM for object
brokering and interfacing, but based on Internet technologies so that allowance is made
even for integration to non-Microsoft platforms. Web Forms and Web Services, which
constitute the Internet interface portion of .NET, are implemented by a part of the .NET
Framework referred to as ASP.NET.

FEATURES OF ASP.NET
ASP.NET is the next version of Active Server Pages (ASP); it is a unified Web
development platform that provides the services necessary for developers to build
18

Central Excise Operation of a Manufacturing Unit


enterprise-class Web applications. While ASP.NET is largely syntax compatible, it also
provides a new programming model and infrastructure for more secure, scalable, and
stable applications.
ASP.NET is a compiled, NET-based environment, we can author applications in
any .NET compatible language, including Visual Basic .NET, C#, and JScript .NET.
Additionally, the entire .NET Framework is available to any ASP.NET application.
Developers can easily access the benefits of these technologies, which include the
managed common language runtime environment (CLR), type safety, inheritance, and so
on.
ASP.NET has been designed to work seamlessly with WYSIWYG HTML editors
and other programming tools, including Microsoft Visual Studio .NET. Not only does this
make Web development easier, but it also provides all the benefits that these tools have to
offer, including a GUI that developers can use to drop server controls onto a Web page
and fully integrated debugging support.
Developers can choose from the following two features when creating an
ASP.NET application. Web Forms and Web services, or combine these in any way they
see fit. Each is supported by the same infrastructure that allows you to use authentication
schemes; cache frequently used data, or customizes your application's configuration, to
name only a few possibilities.
Web Forms allows us to build powerful forms-based Web pages. When building
these pages, we can use ASP.NET server controls to create common UI elements, and
program them for common tasks. These controls allow we to rapidly build a Web Form
out of reusable built-in or custom components, simplifying the code of a page.
An XML Web service provides the means to access server functionality remotely.
Using Web services, businesses can expose programmatic interfaces to their data or
business logic, which in turn can be obtained and manipulated by client and server
applications. XML Web services enable the exchange of data in client-server or serverserver scenarios, using standards like HTTP and XML messaging to move data across
firewalls. XML Web services are not tied to a particular component technology or object19

Central Excise Operation of a Manufacturing Unit


calling convention. As a result, programs written in any language, using any component
model, and running on any operating system can access XML Web services
Each of these models can take full advantage of all ASP.NET features, as well as
the power of the .NET Framework and .NET Framework common language runtime.
Accessing databases from ASP.NET applications is an often-used technique for
displaying data to Web site visitors. ASP.NET makes it easier than ever to access
databases for this purpose. It also allows us to manage the database from your code.
ASP.NET provides a simple model that enables Web developers to write logic that
runs at the application level. Developers can write this code in the global.aspx text file or
in a compiled class deployed as an assembly. This logic can include application-level
events, but developers can easily extend this model to suit the needs of their Web
application.
ASP.NET provides easy-to-use application and session-state facilities that are
familiar to ASP developers and are readily compatible with all other .NET Framework
APIs.
ASP.NET offers the IHttpHandler and IHttpModule interfaces. Implementing the
IHttpHandler interface gives you a means of interacting with the low-level request and
response services of the IIS Web server and provides functionality much like ISAPI
extensions, but with a simpler programming model. Implementing the IHttpModule
interface allows you to include custom events that participate in every request made to
your application.
ASP.NET takes advantage of performance enhancements found in the .NET
Framework and common language runtime. Additionally, it has been designed to offer
significant performance improvements over ASP and other Web development platforms.
All ASP.NET code is compiled, rather than interpreted, which allows early binding,
strong typing, and just-in-time (JIT) compilation to native code, to name only a few of its
benefits. ASP.NET is also easily factorable, meaning that developers can remove modules
20

Central Excise Operation of a Manufacturing Unit


(a session module, for instance) that are not relevant to the application they are
developing.
ASP.NET provides extensive caching services (both built-in services and caching
APIs). ASP.NET also ships with performance counters that developers and system
administrators can monitor to test new applications and gather metrics on existing
applications.
Writing custom debug statements to your Web page can help immensely in
troubleshooting your application's code. However, it can cause embarrassment if it is not
removed. The problem is that removing the debug statements from your pages when your
application is ready to be ported to a production server can require significant effort.
ASP.NET offers the Trace Context class, which allows us to write custom debug
statements to our pages as we develop them. They appear only when you have enabled
tracing for a page or entire application. Enabling tracing also appends details about a
request to the page, or, if you so specify, to a custom trace viewer that is stored in the root
directory of your application.
The .NET Framework and ASP.NET provide default authorization and
authentication schemes for Web applications. We can easily remove, add to, or replace
these schemes, depending upon the needs of our application.
ASP.NET configuration settings are stored in XML-based files, which are human
readable and writable. Each of our applications can have a distinct configuration file and
we can extend the configuration scheme to suit our requirements.

THE .NET FRAMEWORK


The .NET Framework is a new computing platform that simplifies application
development in the highly distributed environment of the Internet.

21

Central Excise Operation of a Manufacturing Unit

OBJECTIVES OF. NET FRAMEWORK:


1. To provide a consistent object-oriented programming environment whether
object codes is stored and executed locally on Internet-distributed, or executed remotely.
2. To provide a code-execution environment to minimizes software deployment
and guarantees safe execution of code.
3. 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.

THE COMMON LANGUAGE RUNTIME (CLR):


The common language runtime is the foundation of the .NET Framework. It manages
code at execution time, providing important services such as memory management,
thread management, and removing and also ensures more security and robustness. The
concept of code management is a fundamental principle of the runtime. Code that targets
the runtime is known as managed code, while code that does not target the runtime is
known as unmanaged code.

THE .NET FRAME WORK CLASS LIBRARY


It is a comprehensive, object-oriented collection of reusable types used to develop
applications ranging from traditional command-line or graphical user interface (GUI)
applications to applications based on the latest innovations provided by ASP.NET, such as
Web Forms and XML Web services.
The .NET Framework can be hosted by unmanaged components that load the
common language runtime into their processes and initiate the execution of managed
code, thereby creating a software environment that can exploit both managed and
unmanaged features. The .NET Framework not only provides several runtime hosts, but
also supports the development of third-party runtime hosts.
22

Central Excise Operation of a Manufacturing Unit

Internet Explorer is an example of an unmanaged application that hosts the


runtime (in the form of a MIME type extension). Using Internet Explorer to host the
runtime to enables embeds managed components or Windows Forms controls in HTML
documents.

FEATURES OF THE COMMON LANGUAGE RUNTIME:


The common language runtime manages memory; thread execution, code
execution, code safety verification, compilation, and other system services these are all
run on CLR.
Security.
Robustness.
Productivity.
Performance.

SECURITY:
The runtime enforces code access security. The security features of the runtime
thus enable legitimate Internet-deployed software to be exceptionally featuring rich. With
regards to security, managed components are awarded varying degrees of trust,
depending on a number of factors that include their origin to perform file-access
operations, registry-access operations, or other sensitive functions.

ROBUSTNESS:
The runtime also enforces code robustness by implementing a strict type- and
code-verification infrastructure called the common type system(CTS). The CTS ensures
that all managed code is self-describing. The managed environment of the runtime
eliminates many common software issues.

23

Central Excise Operation of a Manufacturing Unit

PRODUCTIVITY:
The runtime also accelerates developer productivity. For example, programmers
can write applications in their development language of choice, yet take full advantage of
the runtime, the class library, and components written in other languages by other
developers.

PERFORMANCE:
The runtime is designed to enhance performance. Although the common language
runtime provides many standard runtime services, managed code is never interpreted. A
feature called just-in-time (JIT) compiling enables all managed code to run in the native
machine language of the system on which it is executing. Finally, the runtime can be
hosted by high-performance, server-side applications, such as Microsoft SQL Server
and Internet Information Services (IIS).

DATA ACCESS WITH ADO.NET


As you develop applications using ADO.NET, you will have different
requirements for working with data. You might never need to directly edit an XML file
containing data - but it is very useful to understand the data architecture in ADO.NET.
ADO.NET offers several advantages over previous versions of ADO:
Interoperability
Maintainability
Programmability
Performance Scalability

INTEROPERABILITY:
ADO.NET applications can take advantage of the flexibility and broad acceptance
of XML. Because XML is the format for transmitting datasets across the network, any
24

Central Excise Operation of a Manufacturing Unit


component that can read the XML format can process data. The receiving component
need not be an ADO.NET component.
The transmitting component can simply transmit the dataset to its destination
without regard to how the receiving component is implemented. The destination
component might be a Visual Studio application or any other application implemented
with any tool whatsoever.
The only requirement is that the receiving component be able to read XML. SO,
XML was designed with exactly this kind of interoperability in mind.

MAINTAINABILITY:
In the life of a deployed system, modest changes are possible, but substantial,
Architectural changes are rarely attempted because they are so difficult. As the
performance load on a deployed application server grows, system resources can become
scarce and response time or throughput can suffer. Faced with this problem, software
architects can choose to divide the server's business-logic processing and user-interface
processing onto separate tiers on separate machines.
In effect, the application server tier is replaced with two tiers, alleviating the
shortage of system resources. If the original application is implemented in ADO.NET
using datasets, this transformation is made easier.
ADO.NET data components in Visual Studio encapsulate data access
functionality in various ways that help you program more quickly and with fewer
mistakes.

PERFORMANCE:
ADO.NET datasets offer performance advantages over ADO disconnected record
sets. In ADO.NET data-type conversion is not necessary.
25

Central Excise Operation of a Manufacturing Unit

SCALABILITY:
ADO.NET accommodates scalability by encouraging programmers to conserve
limited resources. Any ADO.NET application employs disconnected access to data; it
does not retain database locks or active database connections for long durations.

VISUAL STUDIO .NET


Visual Studio .NET is a complete set of development tools for building ASP Web
applications, XML Web services, desktop applications, and mobile applications In
addition to building high-performing desktop applications, you can use Visual Studio's
powerful component-based development tools and other technologies to simplify teambased design, development, and deployment of Enterprise solutions.
Visual Basic .NET, Visual C++ .NET, and Visual C# .NET all use the same
integrated development environment (IDE), which allows them to share tools and
facilitates in the creation of mixed-language solutions. In addition, these languages
leverage the functionality of the .NET Framework and simplify the development of ASP
Web applications and XML Web services.
Visual Studio supports the .NET Framework, which provides a common language
runtime and unified programming classes; ASP.NET uses these components to create
ASP Web applications and XML Web services. Also it includes MSDN Library, which
contains all the documentation for these development tools.

XML WEB SERVICES


XML Web services are applications that can receive the requested data using
XML over HTTP. XML Web services are not tied to a particular component technology
or object-calling convention but it can be accessed by any language, component model,
or operating system. In Visual Studio .NET, you can quickly create and include XML
Web services using Visual Basic, Visual C#, JScript, Managed Extensions for C++, or
ATL Server.
26

Central Excise Operation of a Manufacturing Unit

XML SUPPORT
Extensible Markup Language (XML) provides a method for describing structured
data. XML is a subset of SGML that is optimized for delivery over the Web. The World
Wide Web Consortium (W3C) defines XML standards so that structured data will be
uniform and independent of applications. Visual Studio .NET fully supports XML,
providing the XML Designer to make it easier to edit XML and create XML schemas.

COMMON LANGUAE SPEGIFICATION (CLS)


Visual Basic.NET is also compliant with CLS (Common Language Specification)
and supports structured exception handling. CLS is set of rules and constructs that are
supported by the CLR (Common Language Runtime). CLR is the runtime environment
provided by the .NET Framework; it manages the execution of the code and also makes
the development process easier by providing services.
Visual Basic.NET is a CLS-compliant language. Any objects, classes, or
components that created in Visual Basic.NET can be used in any other CLS-compliant
language. In addition, we can use objects, classes, and components created in other CLScompliant languages in Visual Basic.NET .The use of CLS ensures complete
interoperability among applications, regardless of the languages used to create the
application.

IMPLEMENTATION INHERITANCE
Visual Basic.NET supports implementation inheritance. This means that, while
creating applications in Visual Basic.NET, we can drive from another class, which is
know as the base class that derived class inherits all the methods and properties of the
base class. In the derived class, we can either use the existing code of the base class or
override the existing code. Therefore, with help of the implementation inheritance, code
can be reused.

CONSTRUCTORS AND DESTRUCTORS


Constructors are used to initialize objects, whereas destructors are used to destroy
them. In other words, destructors are used to release the resources allocated to the object.
In Visual Basic.NET the sub finalize procedure is available. The sub finalize procedure is
27

Central Excise Operation of a Manufacturing Unit


used to complete the tasks that must be performed when an object is destroyed. The sub
finalize procedure is called automatically when an object is destroyed. In addition, the
sub finalize procedure can be called only from the class it belongs to or from derived
classes.

GARBAGE COLLECTION
Garbage Collection is another new feature in Visual Basic.NET. The .NET
Framework monitors allocated resources, such as objects and variables. In addition,
the .NET Framework automatically releases memory for reuse by destroying objects that
are no longer in use. In Visual Basic.NET, the garbage collector checks for the objects
that are not currently in use by applications. When the garbage collector comes across an
object that is marked for garbage collection, it releases the memory occupied by the
object.

OVERLOADING
Overloading is another feature in Visual Basic.NET. Overloading enables us to
define multiple procedures with the same name, where each procedure has a different set
of arguments. Besides using overloading for procedures, we can use it for constructors
and properties in a class.

MULTITHREADING
Visual Basic.NET also supports multithreading. An application that supports
multithreading can handle multiple tasks simultaneously, we can use multithreading to
decrease the time taken by an application to respond to user interaction. To decrease the
time taken by an application to respond to user interaction, we must ensure that a separate
thread in the application handles user interaction.

STRUCTURED EXCEPTION HANDLING


Visual Basic.NET supports structured handling, which enables us to detect and
remove errors at runtime. In Visual Basic.NET, we need to use TryCatchFinally
statements to create exception handlers.

28

Central Excise Operation of a Manufacturing Unit

3.5 ABOUT SQL STRUCTURED QUERY LANGUAGE


FEATURES OF SQL SERVER 2000
The OLAP Services feature available in SQL Server version 7.0 is now called
SQL Server 2000 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 2000 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
SQL-SERVER database consist of six type of objects,
They are,
1. TABLE
2. QUERY
3. FORM
4. REPORT
5. MACRO

Tables
In relational database systems (DBS) data are represented using tables (relations).
A query issued against the DBS also results in a table. A table has the following structure:
Column 1 Column 2 . . . Column n
..
A table is uniquely identified by its name and consists of rows that contain the
stored information, each row containing exactly one tuple (or record). A table can have
one or more columns.
A column is made up of a column name and a data type, and it describes an
attribute of the tuples. The structure of a table, also called relation schema, thus is defined
by its attributes.
29

Central Excise Operation of a Manufacturing Unit


The type of information to be stored in a table is defined by the data types of the
attributes at table creation time.
SQL uses the terms table, row, and column for relation, tuple, and attribute,
respectively. In this tutorial we will use the terms interchangeably.
A table can have up to 254 columns which may have different or same data types
and sets of values (domains), respectively. Possible domains are alphanumeric data
(strings), numbers and date formats. SQL offers the following basic data types:
char (n): Fixed-length character data (string), n characters long. The maximum size for
n is 255 bytes (2000 in Oracle8). Note that a string of type char is always padded on right
with blanks to full length of n. (+ can be memory consuming).
Example: char (40)
varchar2 (n): Variable-length character string. The maximum size for n is 2000 (4000 in
Oracle8). Only the bytes used for a string require storage. Example: varchar(80)
Number (o, d): Numeric data type for integers and reals. o = overall number of digits,
d = number of digits to the right of the decimal point.
Maximum values: o =38, d= 84 to +127. Examples: number (8), number (5,2)
Note that, e.g., number (5,2) cannot contain anything larger than 999.99 without resulting
in an error. Data types derived from number are int [eger], dec [imal], smallint and real.
Date: Date data type for storing date and time.
The default format for a date is: DD-MMM-YY. Examples: 13-OCT-94, 07-JAN-98
Long: Character data up to a length of 2GB. Only one long column is allowed per table.
Further properties of tables are:
The order in which tuples appear in a table is not relevant (unless a query requires an
explicit sorting).
A table has no duplicate tuples (depending on the query, however, duplicate tuples can
appear in the query result).
A database schema is a set of relation schemas. The extension of a database schema at
database run-time is called a database instance or database, for short.
30

Central Excise Operation of a Manufacturing Unit

VIEWS OF TABLE:
We can work with a table in two types,
1. Design View
2. Datasheet View

Design View
To build or modify the structure of a table we work in the table design view. We
can specify what kind of data will be hold.

Datasheet View
To add, edit or analyses the data itself we work in tables datasheet view mode.

QUERY:
A query is a question that has to be asked the data. Access gathers data that
answers the question from one or more table. The data that make up the answer is either
dynast (if you edit it) or a snapshot (it cannot be edited).Each time we run query, we get
latest information in the dynast. Access either displays the dynast or snapshot for us to
view or perform an action on it, such as deleting or updating.

FORMS:
A form is used to view and edit information in the database record by record .A
form displays only the information we want to see in the way we want to see it. Forms
use the familiar controls such as textboxes and checkboxes. This makes viewing and
entering data easy.

31

Central Excise Operation of a Manufacturing Unit

Views of Form:
We can work with forms in several primarily there are two views,
They are,
1. Design View
2. Form View

Design View
To build or modify the structure of a form, we work in forms design view. We can
add control to the form that are bound to fields in a table or query, includes textboxes,
option buttons, graphs and pictures.

Form View
The form view which display the whole design of the form.

4.1 PROBLEM DSCRIPTION


32

Central Excise Operation of a Manufacturing Unit


The Objective of this document is to study and analyze the automation of Central
Excise operations of manufacturing unit in general. CENEX is the Central Excise
Software that aims to take care of all the statutory registers and returns required under the
Central Excise Act and Rules.
Excisable Goods means goods specified in the schedule to the Central Tariff Act,
1985 as being subject to a duty of excise. The basic conditions that must be satisfied by
any good in order to be called as excisable goods are: The goods must be movable. The goods must be marketable i.e. salable in the
market as such goods. Actual sale of goods in the market is not necessary because excise
duty is chargeable on manufacture and not on sales. The goods must be specified in the
Central Excise Tariff Act. Excise Duty has now been renamed as Cenvat (Central Value
Added Tax) from Modvat (earlier terms of reference). A uniform Cenvat has been levied
@ 16 % + other duties. A part from Cenvat, on some selected items, an additional Special
Excise Duty (SED) has been levied at rates of * %, 16 % and 24 % depending on the
nature of the item.
Service Tax the major change as far as service tax is concerned is that the
Supreme Court Judgment has now been over ruled by amending the law with
retrospective effect. The Central Excise Department can now recover service-tax
collected by the users of the services. With the result no refund of service-tax paid on the
services of goods transport operators and clearing and forwarding agent would be
granted.

Cenvat credit can be utilized for the following purposes: 33

Central Excise Operation of a Manufacturing Unit


Towards payment of excise duty on the final product. Towards payment of excise
duty on waste which arises in the course of manufacture of final product.
Towards payment of excise duty on inputs itself where they are cleared for home
consumption. However, credit cannot be taken unless the inputs are accompanied with an
invoice prepared as per Central Excise Rules. Procedures of Central Excise rule
The materials purchased by the Manufacturer from his supplier are referred as
Inputs. A document is prepared namely GRN. (Goods Receipt Note) This document
contains all the details of the suppliers invoice and allows the materials in i.e. to the
stores. From stores these materials are directed for production. This GRN is shown to the
Excise authorities. Since it is the receipt of material for production the duty paid against
those materials are treated as

4.2 NEED FOR COMPUTERIZATION


34

Central Excise Operation of a Manufacturing Unit

EXISTING SYSTEM
The normal existing system in the auctioning is manual system. It is a difficult
and ridiculous one to maintain them without using of online system. In the existing
system for every action, lot of records has been needed for updating.
Disadvantages in the existing system
Enormous amount of time consumption for recording all the activities, added and
updated record is very slow.
This is very much error and more complex
This system is not user friendly

35

Central Excise Operation of a Manufacturing Unit

4.3 PROPOSED SYSTEM


In the existing system the taxes are getting from some other pages and include in
the production master. But here all taxes are include in the project itself and get all taxes
related for production, sales and for scrap.
Initial investigations are important and place a vital role in the system analysis
process. Before staring to design the new system an initial investigation are conducted to
identify the problem with the existing system. The techniques used for information
gathering are interviewing, collection of various input and outputs sample etc., and the
collection information are deeply analyzed and evaluated.
Advantages of proposed system
Updating and adding of records is very fast and good performance.
Not much knowledge is needed for operating this system.
Auctioning product added is very easy with image. Calculation is very easy.
This is very much user friendly
Finding and replacing the records as very easy access.

36

Central Excise Operation of a Manufacturing Unit

5.1 SYSTEM FLOW DIAGRAM

CENTRAL EXCISE OPERATION OF A MANUFACTURING UNIT

Tariff master

Product master

Scrap master
Data Base
Goods Receipt Note Details

GRN supplier

Job work Entry

Sales master

37

Central Excise Operation of a Manufacturing Unit

5.2 DATA FLOW DIAGRAM


Tariff master:
GRN

BED

AED
DATA BASE
SED

CESS

Product master:
Product

Product name

Unit of measurement

DATA BASE

Tariff code

38

Central Excise Operation of a Manufacturing Unit

Scrap master:
Scrap

Product name

Unit of measurement

DATA BASE

Tariff code

Goods Receipt Notes:


GRN

Supplier Name

Supplier Date

Invoice No

Tariff code

Description

Reject
Approved
Accept
39

Central Excise Operation of a Manufacturing Unit

Job work entry:


Job work receipt

Challan No
Challan Date
Consumed qty
Received qty

40

Central Excise Operation of a Manufacturing Unit

5.3 DATA STRUCTURE


Tariff Master:
S.No

Name

Data type

Size( Description

Tar_Code

Varchar

30

Tariff code

Tar_Type

Varchar

30

Tariff type

Tar_Desc

text

16

Tariff description

Tar_BED

int

Basic excise duty

Tar_BED Type

Varchar

30

Tar_SED

int

Basic excise duty in % or


rate
Special excise duty

Tar_SED Type

Varchar

30

Special excise duty in % or


amount

Tar_AED

int

Additional excise duty

Tar_AED Type

Varchar

30

Additional excise duty in %


or amount

10

Tar_CESS

int

CESS

11

Tar_CESS Type

Varchar

30

CESS in % or amount

12

Tar_Status

text

16

Tariff status

13

Tar_Date

Varchar

30

Tariff date

14

Tar_userName

Varchar

30

User name

41

Central Excise Operation of a Manufacturing Unit

Product Master:
S.No

Name

Data type

Size(

Description

Pro_Code

Varchar

30

Product Code

Pro_Name

Varchar

30

Product name

Pro_Desc

Varchar

30

Product description

Pro_Tariff_Code

Varchar

30

Tariff code

Pro_Status

text

16

Product status

Pro_Date

Varchar

30

Product date

Scrap Master:
S.No

Name

Data type

Size(

Description

Scrap_Code

Varchar

30

Scrap code

Scrap_Name

Varchar

30

Scrap name

UOM

Varchar

30

Unit of measurement

Tariff_Code

Varchar

30

Tariff code

Tariff_Desc

Varchar

30

Tariff description

Opening_Stock

Varchar

30

Opening stock

Company_Name

Varchar

30

Company name

42

Central Excise Operation of a Manufacturing Unit

GRN Details:
S.No

Filed Name

Data type

Size(

Description

GRN_NO

Varchar

30

GRN number

GRN_Date

Varchar

30

GRN Date

GRN_item_code

Varchar

30

GRN code

GRN_UOM

Varchar

30

GRN unit of measurement

GRN_Tariff

Varchar

30

Tariff head

GRN_Received_Qty

Int

Received Qty

GRN_Rej _Qty

Int

Reject Qty

GRN_App_ Qty

Int

Approved Qty

GRN_Ret_Qty

Int

Return Qty

GRN supplier:
S.No

Name

Data type

Size(

Description

GRN_NO

Varchar

30

GRN number

GRN_Date

Varchar

30

GRN Date

3
4

GRN_type
Sup_no

Varchar
Varchar

30
30

GRN type
Supplier No

Sup_name

Varchar

30

Supplier name

Sup_DC_No

int

Supplier DC No

Sup_DC_Date

Varchar

30

Supplier DC date

Invoice_no

int

Supplier invoice No

Invoice_Date

Varchar

30

Supplier invoice Date

43

Central Excise Operation of a Manufacturing Unit

Sales Master:
S.No

Name

Data type

Size(

Description

Sales_ret_no

int

Sales no

Sales_ret_date

Varchar

30

Sales date

Party_code

Varchar

30

Party code

Tariff_Head

Varchar

30

Tariff code

Description

Varchar

30

Description

Prod_Code

Varchar

30

Product code

Prod_Name

Varchar

30

Product name

UOM

Varchar

30

Unit of measurement

Rate

int

Rate

10

Sales_Qty

int

Sales Qty

11

Prod_Value

int

Product value

12

Ret_ Qty

int

Return Qty

13

Shortage_

int

Shortage

14

Net_Qty

int

Net Qty

15

Total_Valid

int

Total valid

16

BED

int

Basic excise duty

17

SED

int

Special excise duty

18

AED

int

Additional excise duty

19

CESS

int

CESS

20

Total_SR_Value

int

Total value

6. System Design and Development:


44

Central Excise Operation of a Manufacturing Unit

Modules:
Tariff Master
UOM Master
Product Master
Supplier Report
Scrap Register
Sales Register
Tariff Master:
Tariff master report displays the list of Tariff heads and corresponding percentages
available for each heads. These data are recorded through the tariff master. This is a direct
report.
UOM Master:
UOM master report displays the list of unit of measurement that is commonly
used for your business. These data are recorded through the UOM master. This is a direct
report.
Product Master:
Party master report displays the list of Party names of those who are linked to
your company for establishing business operations. These data are recorded through the
party master. This is a direct report.

Supplier Report:
Supplier master report displays the details and list of suppliers belongs to your
45

Central Excise Operation of a Manufacturing Unit


organization or company. These data are recorded through the supplier master. This is
parameter-based report. The main parameter is date range.
Start Date: The list of suppliers and the items supplied on or after this starting date are
listed. Allowed input is date in the format of DD/MM/YYYY. The start date must be
greater than the financial year start date.
End Date: The name of suppliers and the items supplied on or before this end date are
listed. Allowed input is date in the format of DD/MM/YYYY. The end date must be
greater than the start date.

Scrap Register:
Scrap Register report display the details of accumulated stock as scrap on a given
period.
The issued quantity and closing stock are also displayed in the output. This is parameter
based report. The main parameter is date range.
Start Date: The scraps issued and accrued details on or after this starting date are listed.
Allowed input is date in the format of DD/MM/YYYY. The start date must be greater
than the financial year start date.
End Date: The scrap issued or accrued on or before this end date are listed. Allowed input
is date in the format of DD/MM/YYYY. The end date must be greater than the start
date.

7. SYSTEM TESTING AND MAINTENANCE


46

Central Excise Operation of a Manufacturing Unit


Software testing is an investigation conducted to provide stakeholders with
information about the quality of the product or service under test. Software testing also
provides an objective, independent view of the software to allow the business to
appreciate and understand the risks of software implementation. Test techniques include,
but are not limited to, the process of executing a program or application with the intent of
finding software bugs.
Software testing can also be stated as the process of validating and verifying that a
software program/application/product:

meets the business and technical requirements that guided its design and
development;

works as expected; and

Can be implemented with the same characteristics.

Software testing, depending on the testing method employed, can be implemented


at any time in the development process. However, most of the test effort occurs after the
requirements have been defined and the coding process has been completed. As such, the
methodology of the test is governed by the software development methodology adopted.
Different software development models will focus the test effort at different
points in the development process. Newer development models, such as Agile, often
employ test driven development and place an increased portion of the testing in the hands
of the developer, before it reaches a formal team of testers. In a more traditional model,
most of the test execution occurs after the requirements have been defined and the coding
process has been completed.

Scope
A primary purpose of testing is to detect software failures so that defects may be
discovered and corrected. This is a non-trivial pursuit. Testing cannot establish that a
product functions properly under all conditions but can only establish that it does not
function properly under specific conditions. The scope of software testing often includes
examination of code as well as execution of that code in various environments and
conditions as well as examining the aspects of code: does it do what it is supposed to do
47

Central Excise Operation of a Manufacturing Unit


and do what it needs to do. In the current culture of software development, a testing
organization may be separate from the development team.

Functional vs non-functional testing


Functional testing refers to activities that verify a specific action or function of the
code. These are usually found in the code requirements documentation, although some
development methodologies work from use cases or user stories. Functional tests tend to
answer the question of "can the user do this" or "does this particular feature work".
Non-functional testing refers to aspects of the software that may not be related to
a specific function or user action, such as scalability or security. Non-functional testing
tends to answer such questions as "how many people can log in at once".

Defects and failures


Not all software defects are caused by coding errors. One common source of
expensive defects is caused by requirement gaps, e.g., unrecognized requirements, that
result in errors of omission by the program designer. A common source of requirements
gaps is non-functional requirements such as testability, scalability, maintainability,
usability, performance, and security.
Software faults occur through the following processes. A programmer makes an
error (mistake), which results in a defect (fault, bug) in the software source code. If this
defect is executed, in certain situations the system will produce wrong results, causing a
failure. Not all defects will necessarily result in failures. For example, defects in dead
code will never result in failures. A defect can turn into a failure when the environment is
changed. Examples of these changes in environment include the software being run on a
new hardware platform, alterations in source data or interacting with different software. A
single defect may result in a wide range of failure symptoms

Unit Testing
48

Central Excise Operation of a Manufacturing Unit

In computer programming, unit testing is a method by which individual units of


source code are tested to determine if they are fit for use. A unit is the smallest testable
part of an application. In procedural programming a unit may be an individual function or
procedure. Unit tests are created by programmers or occasionally by white box testers.
Ideally, each test case is independent from the others: substitutes like method
stubs, mock objects, fakes and test harnesses can be used to assist testing a module in
isolation. Unit tests are typically written and run by software developers to ensure that
code meets its design and behaves as intended. Its implementation can vary from being
very manual (pencil and paper) to being formalized as part of build automation.
The goal of unit testing is to isolate each part of the program and show that the
individual parts are correct. A unit test provides a strict, written contract that the piece of
code must satisfy. As a result, it affords several benefits. Unit tests find problems early in
the development cycle.

System Testing
System testing of software or hardware is testing conducted on a complete,
integrated system to evaluate the system's compliance with its specified requirements.
System testing falls within the scope of black box testing, and as such, should require no
knowledge of the inner design of the code or logic.
As a rule, system testing takes, as its input, all of the "integrated" software
components that have successfully passed integration testing and also the software
system itself integrated with any applicable hardware system(s). The purpose of
integration testing is to detect any inconsistencies between the software units that are
integrated together (called assemblages) or between any of the assemblages and the
hardware. System testing is a more limited type of testing; it seeks to detect defects both
within the "inter-assemblages" and also within the system as a whole.

Acceptance Testing
49

Central Excise Operation of a Manufacturing Unit


Acceptance testing generally involves running a suite of tests on the completed
system. Each individual test, known as a case, exercises a particular operating condition
of the user's environment or feature of the system, and will result in a pass or fail, or
Boolean, outcome. There is generally no degree of success or failure. The test
environment is usually designed to be identical, or as close as possible, to the anticipated
user's environment, including extremes of such. These test cases must each be
accompanied by test case input data or a formal description of the operational activities
(or both) to be performed intended to thoroughly exercise the specific case and a formal
description of the expected results.
Acceptance Tests/Criteria (in Agile Software Development) are usually created by
business customers and expressed in a business domain language. These are high-level
tests to test the completeness of a user story or stories 'played' during any sprint/iteration.
These tests are created ideally through collaboration between business customers,
business analysts, testers and developers; however the business customers (product
owners) are the primary owners of these tests. As the user stories pass their acceptance
criteria, the business owners can be sure of the fact that the developers are progressing in
the right direction about how the application was envisaged to work and so it's essential
that these tests include both business logic tests as well as UI validation elements (if need
be).
Acceptance test cards are ideally created during sprint planning or iteration
planning meeting, before development begins so that the developers have a clear idea of
what to develop. Sometimes (due to bad planning!) acceptance tests may span multiple
stories (that are not implemented in the same sprint) and there are different ways to test
them out during actual sprints. One popular technique is to mock external interfaces or
data to mimic other stories which might not be played out during an iteration (as those
stories may have been relatively lower business priority). A user story is not considered
complete until the acceptance tests have passed.
User Acceptance Testing (UAT) is a process to obtain confirmation that a system
meets mutually agreed-upon requirements. A Subject Matter Expert (SME), preferably
the owner or client of the object under test, provides such confirmation after trial or
50

Central Excise Operation of a Manufacturing Unit


review. In software development, UAT is one of the final stages of a project and often
occurs before a client or customer accepts the new system.
Users of the system perform these tests, which developers derive from the client's
contract or the user requirements specification.
Test-designers draw up formal tests and devise a range of severity levels. Ideally
the designer of the user acceptance tests should not be the creator of the formal
integration and system test cases for the same system; however in some situations this
may not be avoided. The UAT acts as a final verification of the required business function
and proper functioning of the system, emulating real-world usage conditions on behalf of
the paying client or a specific large customer. If the software works as intended and
without issues during normal use, one can reasonably extrapolate the same level of
stability in production.
The results of these tests give confidence to the clients as to how the system will
perform in production. There may also be legal or contractual requirements for
acceptance of the system.

Software quality assurance (SQA)


Though controversial, software testing is a part of the software quality assurance
(SQA) process. In SQA, software process specialists and auditors are concerned for the
software development process rather than just the artifacts such as documentation, code
and systems. They examine and change the software engineering process itself to reduce
the amount of faults that end up in the delivered software: the so-called defect rate.
What constitutes an "acceptable defect rate" depends on the nature of the
software; A flight simulator video game would have much higher defect tolerance than
software for an actual airplane.
Although there are close links with SQA, testing departments often exist
independently, and there may be no SQA function in some companies.
Software testing is a task intended to detect defects in software by contrasting a
computer programs expected

Testing artifacts
51

Central Excise Operation of a Manufacturing Unit


Software testing process can produce several artifacts.

Test plan
A test specification is called a test plan. The developers are well aware what test
plans will be executed and this information is made available to management and the
developers. The idea is to make them more cautious when developing their code or
making additional changes. Some companies have a higher-level document called a test
strategy.

Traceability matrix
A traceability matrix is a table that correlates requirements or design documents to
test documents. It is used to change tests when the source documents are changed, or to
verify that the test results are correct.

Test case
A test case normally consists of a unique identifier, requirement references from a
design specification, preconditions, events, a series of steps (also known as actions) to
follow, input, output, expected result, and actual result. Clinically defined a test case is an
input and an expected result. This can be as pragmatic as 'for condition x your derived
result is y', whereas other test cases described in more detail the input scenario and what
results might be expected. The optional fields are a test case ID, test step, or order of
execution number, related requirement(s), depth, test category, author, and check boxes
for whether the test is automatable and has been automated. A test case should also
contain a place for the actual result. These steps can be stored in a word processor
document, spreadsheet, database, or other common repository. In a database system, you
may also be able to see past test results, which generated the results, and what system
configuration was used to generate those results. These past results would usually be
stored in a separate table.

Test script
52

Central Excise Operation of a Manufacturing Unit


The test script is the combination of a test case, test procedure, and test data.
Initially the term was derived from the product of work created by automated regression
test tools. Today, test scripts can be manual, automated, or a combination of both.

Test suite
The most common term for a collection of test cases is a test suite. The test suite
often also contains more detailed instructions or goals for each collection of test cases. It
definitely contains a section where the tester identifies the system configuration used
during testing. A group of test cases may also contain prerequisite states or steps, and
descriptions of the following tests.

Test data
In most cases, multiple sets of values or data are used to test the same
functionality of a particular feature. All the test values and changeable environmental
components are collected in separate files and stored as test data. It is also useful to
provide this data to the client and with the product or a project.

Test harness
The software, tools, samples of data input and output, and configurations are all
referred to collectively as a test harness.

Maintenance:
Software maintenance in software engineering is the modification of a software
product after delivery to correct faults, to improve performance or other attributes.
A common perception of maintenance is that it is merely fixing bugs. However,
studies and surveys over the years have indicated that the majority, over 80%, of the
maintenance effort is used for non-corrective actions (Pigosky 1997). This perception is
perpetuated by users submitting problem reports that in reality are functionality
enhancements to the system.
Software maintenance and evolution of systems was first addressed by Meir M.
Lehman in 1969. Over a period of twenty years, his research led to the formulation of
53

Central Excise Operation of a Manufacturing Unit


eight Laws of Evolution (Lehman 1997). Key findings of his research include that
maintenance is really evolutionary developments and that maintenance decisions are
aided by understanding what happens to systems (and software) over time. Lehman
demonstrated that systems continue to evolve over time. As they evolve, they grow more
complex unless some action such as code recapturing is taken to reduce the complexity.
The key software maintenance issues are both managerial and technical. Key
management issues are: alignment with customer priorities, staffing, which organization
does maintenance, estimating costs. Key technical issues are: limited understanding,
impact analysis, testing, and maintainability measurement.

Software maintenance planning


The integral part of software is the maintenance part which requires accurate
maintenance plan to be prepared during software development and should specify how
users will request modifications or report problems and the estimation of resources such
as cost should be included in the budget and a new decision should address to develop a
new system and its quality objectives .The software maintenance which can last for 5-6
years after the development calls for an effective planning which addresses the scope of
software maintenance, the tailoring of the post delivery process, the designation of who
will provide maintenance, an estimate of the life-cycle costs.

Software maintenance processes


This section describes the six software maintenance processes as:
1. The implementation processes contains software preparation and transition
activities, such as the conception and creation of the maintenance plan, the
preparation for handling problems identified during development, and the followup on product configuration management.
2. The problem and modification analysis process, which is executed once the
application has become the responsibility of the maintenance group. The
maintenance programmer must analyze each request, confirm it (by reproducing
the situation) and check its validity, investigate it and propose a solution,
54

Central Excise Operation of a Manufacturing Unit


document the request and the solution proposal, and, finally, obtain all the
required authorizations to apply the modifications.
3. The process considering the implementation of the modification itself.
4. The process acceptance of the modification, by confirming the modified work
with the individual who submitted the request in order to make sure the
modification provided a solution.
5. The migration process (platform migration, for example) is exceptional, and is not
part of daily maintenance tasks. If the software must be ported to another platform
without any change in functionality, this process will be used and a maintenance
project team is likely to be assigned to this task.
6. Finally, the last maintenance process, also an event which does not occur on a
daily basis, is the retirement of a piece of software.

Tariff master:
using
using
using
using
using

System;
System.Data;
System.Configuration;
System.Collections;
System.Web;

55

Central Excise Operation of a Manufacturing Unit


using
using
using
using
using
using

System.Web.Security;
System.Web.UI;
System.Web.UI.WebControls;
System.Web.UI.WebControls.WebParts;
System.Web.UI.HtmlControls;
System.Data.SqlClient;

public partial class GRNDetails : System.Web.UI.Page


{
ClsDbLayer _objDb = new ClsDbLayer();
DataSet ds;
protected void Page_Load(object sender, EventArgs e)
{
if (IsPostBack.Equals(false))
{
string Query = "select Tar_Code from Tariff";
ds = _objDb.Display(Query);
ddlTariff.DataTextField = "Tar_Code";
ddlTariff.DataValueField = "Tar_Code";
ddlTariff.DataSource = ds;
ddlTariff.DataBind();
ListItem L1 = new ListItem();
L1.Text = "-Select-";
L1.Value = "0";
ddlTariff.Items.Add(L1);
ddlTariff.SelectedValue = "0";

}
}
protected void txtRejectedQty_TextChanged(object sender, EventArgs e)
{
int App = Convert.ToInt32(txtReceiveQty.Text) Convert.ToInt32(txtRejectedQty.Text);
txtAppQty.Text = App.ToString();
}
protected void ImageButton1_Click(object sender, ImageClickEventArgs
e)
{
string Query = "insert into GRN_Detail values('" + txtGRNNo.Text
+ "','" + txtGRNDate.Text + "','" + txtGRNItemCode.Text + "','" +
txtUOM.Text + "','" + ddlTariff.SelectedItem + "','" +
txtReceiveQty.Text + "','" + txtRejectedQty.Text + "','" +
txtAppQty.Text + "','" + txtRetQty.Text + "')";
int i = _objDb.Insert(Query);
if (i != -1)
{
Response.Write("Saved Sucessfully");
}
else
{
Response.Write("Not Saved");
}
}
}

56

Central Excise Operation of a Manufacturing Unit

Product master:
using
using
using
using
using

System;
System.Data;
System.Configuration;
System.Collections;
System.Web;

57

Central Excise Operation of a Manufacturing Unit


using
using
using
using
using
using

System.Web.Security;
System.Web.UI;
System.Web.UI.WebControls;
System.Web.UI.WebControls.WebParts;
System.Web.UI.HtmlControls;
System.Data.SqlClient;

public partial class ProductMaster : System.Web.UI.Page


{
ClsDbLayer _objDb = new ClsDbLayer();
DataSet ds;
protected void Page_Load(object sender, EventArgs e)
{
if (IsPostBack.Equals(false))
{
string Query = "select Tar_Code from Tariff";
ds = _objDb.Display(Query);
ddlTariffCode.DataTextField = "Tar_Code";
ddlTariffCode.DataValueField = "Tar_Code";
ddlTariffCode.DataSource = ds;
ddlTariffCode.DataBind();
ListItem L1 = new ListItem();
L1.Text = "-Select-";
L1.Value = "0";
ddlTariffCode.Items.Add(L1);
ddlTariffCode.SelectedValue = "0";

}
}
protected void ImageButton1_Click(object sender, ImageClickEventArgs
e)

string Query = "insert into ProductMaster values('" +


txtProCode.Text + "','" + txtProName.Text + "','" + txtProDesc.Text +
"','" + ddlTariffCode.SelectedItem + "','" + txtProductStatus.Text +
"','" + txtDate.Text + "')";
int i = _objDb.Insert(Query);
if (i != -1)
{
Response.Write("Saved");
}
else
{
Response.Write("Not Saved");
}
}
}

Scrap master:
using
using
using
using
using

System;
System.Data;
System.Configuration;
System.Collections;
System.Web;

58

Central Excise Operation of a Manufacturing Unit


using
using
using
using
using
using

System.Web.Security;
System.Web.UI;
System.Web.UI.WebControls;
System.Web.UI.WebControls.WebParts;
System.Web.UI.HtmlControls;
System.Data.SqlClient;

public partial class ScrapMaster : System.Web.UI.Page


{
ClsDbLayer _objDb = new ClsDbLayer();
DataSet ds;
SqlDataReader dr;
protected void Page_Load(object sender, EventArgs e)
{
if (IsPostBack.Equals(false))
{
string Query = "select Tar_Code from Tariff";
ds = _objDb.Display(Query);
ddlTariffCode.DataTextField = "Tar_Code";
ddlTariffCode.DataValueField = "Tar_Code";
ddlTariffCode.DataSource = ds;
ddlTariffCode.DataBind();
ListItem L1 = new ListItem();
L1.Text = "-Select-";
L1.Value = "0";
ddlTariffCode.Items.Add(L1);
ddlTariffCode.SelectedValue = "0";
}
}
protected void ddlTariffCode_SelectedIndexChanged(object sender,
EventArgs e)
{
string Query = "select Tar_Desc from Tariff where Tar_Code like
'" + ddlTariffCode.SelectedItem + "'";
dr = _objDb.Select(Query);
if (dr.Read())
{
txtTariffDesc.Text = dr[0].ToString();
}
else
{
Response.Write("No Values");
}
}
protected void ImageButton1_Click(object sender, ImageClickEventArgs
e)
{
string Query = "insert into ScrapMaster values('" +
txtScrapCode.Text + "','" + txtScrapName.Text + "','" + txtUOM.Text +
"','" + ddlTariffCode.SelectedItem + "','" + txtTariffDesc.Text + "','"
+ txtOpeningStock.Text + "','" + txtCompanyName.Text + "')";
int i = _objDb.Insert(Query);
if (i != -1)
{
Response.Write("Saved Sucesssfully");
}

59

Central Excise Operation of a Manufacturing Unit


else
{
}
}

Response.Write("Not Saved");

GRN suppliers:
using
using
using
using
using
using
using
using
using
using
using

System;
System.Data;
System.Configuration;
System.Collections;
System.Web;
System.Web.Security;
System.Web.UI;
System.Web.UI.WebControls;
System.Web.UI.WebControls.WebParts;
System.Web.UI.HtmlControls;
System.Data.SqlClient;

public partial class GRN : System.Web.UI.Page


{
ClsDbLayer _objDb = new ClsDbLayer();
protected void Page_Load(object sender, EventArgs e)
{

e)

}
protected void ImageButton1_Click(object sender, ImageClickEventArgs
{

string Query = "insert into GRN_Supplier values('" +


txtGRNNo.Text + "','" + txtGRNDate.Text + "','" +
ddlGRNType.SelectedItem + "','" + txtSupCode.Text + "','" +
txtSupName.Text + "','" + txtSupDCNo.Text + "','" + txtSupDCDate.Text +
"','" + txtInvoiceNo.Text + "','" + txtInvoiceDate.Text + "')";
int i = _objDb.Insert(Query);
if (i != -1)
{
Response.Write("Saved Sucessfully");
}
else
{
Response.Write("Not Saved");
}
}
}

job work entry:


using System;
using System.Data;
using System.Configuration;

60

Central Excise Operation of a Manufacturing Unit


using
using
using
using
using
using
using
using

System.Collections;
System.Web;
System.Web.Security;
System.Web.UI;
System.Web.UI.WebControls;
System.Web.UI.WebControls.WebParts;
System.Web.UI.HtmlControls;
System.Data.SqlClient;

public partial class JobWorkEntry : System.Web.UI.Page


{
ClsDbLayer _objDb = new ClsDbLayer();
protected void Page_Load(object sender, EventArgs e)
{

e)

}
protected void ImageButton1_Click(object sender, ImageClickEventArgs
{

string Query = "insert into Job_Work_Entry values('" +


txtChaNo.Text + "','" + txtChaDate.Text + "','" + txtItemCode.Text +
"','" + txtUOM.Text + "','" + txtConQty.Text + "','" + txtRecQty.Text +
"')";
int i = _objDb.Insert(Query);
if (i != -1)
{
Response.Write("Saved Successfully");
}
else
{
Response.Write("Not Saved");
}
}
}

Sales master:
using System;
using System.Data;

61

Central Excise Operation of a Manufacturing Unit


using
using
using
using
using
using
using
using
using

System.Configuration;
System.Collections;
System.Web;
System.Web.Security;
System.Web.UI;
System.Web.UI.WebControls;
System.Web.UI.WebControls.WebParts;
System.Web.UI.HtmlControls;
System.Data.SqlClient;

public partial class SalesMaster : System.Web.UI.Page


{
ClsDbLayer _objDb = new ClsDbLayer();
DataSet ds;
SqlDataReader dr;
protected void Page_Load(object sender, EventArgs e)
{
if (IsPostBack.Equals(false))
{
string Query = "select Tar_Code from Tariff";
ds = _objDb.Display(Query);
DropDownList1.DataTextField = "Tar_Code";
DropDownList1.DataValueField = "Tar_Code";
DropDownList1.DataSource = ds;
DropDownList1.DataBind();
ListItem L1 = new ListItem();
L1.Text = "-Select-";
L1.Value = "0";
DropDownList1.Items.Add(L1);
DropDownList1.SelectedValue = "0";
string Query1 = "select Pro_Code from ProductMaster";
ds = _objDb.Display(Query1);
DropDownList2.DataTextField = "Pro_Code";
DropDownList2.DataValueField = "Pro_Code";
DropDownList2.DataSource = ds;
DropDownList2.DataBind();
ListItem L2 = new ListItem();
L2.Text = "-Select-";
L2.Value = "0";
DropDownList2.Items.Add(L2);
DropDownList2.SelectedValue = "0";
}
}
protected void DropDownList1_SelectedIndexChanged(object sender,
EventArgs e)
{
string Query = "select Tar_Desc,Tar_BED,Tar_SED,Tar_AED,Tar_CESS
from Tariff where Tar_Code = '" + DropDownList1.SelectedItem + "'";
dr = _objDb.Select(Query);
if (dr.Read())
{
TextBox4.Text = dr[0].ToString();
TextBox14.Text = dr[1].ToString();
TextBox15.Text = dr[2].ToString();

62

Central Excise Operation of a Manufacturing Unit

TextBox16.Text = dr[3].ToString();
TextBox17.Text = dr[4].ToString();

}
}
protected void DropDownList2_SelectedIndexChanged(object sender,
EventArgs e)
{
string Query = "select Pro_Name from ProductMaster where
Pro_Code like '" + DropDownList2.SelectedItem + "'";
dr = _objDb.Select(Query);
if (dr.Read())
{
TextBox5.Text = dr[0].ToString();
}
}
protected void ImageButton1_Click(object sender, ImageClickEventArgs
e)
{
string Query = "insert into Sales values('" + TextBox1.Text +
"','" + TextBox2.Text + "','" + TextBox3.Text + "','" +
DropDownList1.SelectedItem + "','" + TextBox4.Text + "','" +
DropDownList2.SelectedItem + "','" + TextBox5.Text + "','" +
TextBox6.Text + "','" + TextBox7.Text + "','" + TextBox8.Text + "','" +
TextBox9.Text + "','" + TextBox10.Text + "','" + TextBox11.Text + "','"
+ TextBox12.Text + "','" + TextBox13.Text + "','" + TextBox14.Text +
"','" + TextBox15.Text + "','" + TextBox16.Text + "','" + TextBox17.Text
+ "','" + TextBox18.Text + "')";
int i = _objDb.Insert(Query);
if (i != -1)
{
Response.Write("Saved");
}
else
{
Response.Write("Not saved");
}
}
protected void TextBox8_TextChanged(object sender, EventArgs e)
{
int a = Convert.ToInt16(TextBox7.Text) *
Convert.ToInt16(TextBox8.Text);
TextBox9.Text = a.ToString();
}
protected void TextBox11_TextChanged(object sender, EventArgs e)
{
int b = Convert.ToInt16(TextBox10.Text) Convert.ToInt16(TextBox11.Text);
TextBox12.Text = b.ToString();
}
protected void TextBox12_TextChanged(object sender, EventArgs e)
{
}
protected void Button1_Click(object sender, EventArgs e)
{

63

Central Excise Operation of a Manufacturing Unit


int c = Convert.ToInt16(TextBox7.Text) *
Convert.ToInt16(TextBox12.Text);
TextBox13.Text = c.ToString();
}
protected void Button2_Click(object sender, EventArgs e)
{
int d = Convert.ToInt32(TextBox13.Text) +
Convert.ToInt32(TextBox14.Text) + Convert.ToInt32(TextBox15.Text) +
Convert.ToInt16(TextBox16.Text) + Convert.ToInt16(TextBox17.Text);
TextBox18.Text = d.ToString();
}
}

using System;
using System.Data;
using System.Configuration;

64

Central Excise Operation of a Manufacturing Unit


using
using
using
using
using
using
using
using

System.Collections;
System.Web;
System.Web.Security;
System.Web.UI;
System.Web.UI.WebControls;
System.Web.UI.WebControls.WebParts;
System.Web.UI.HtmlControls;
System.Data.SqlClient;

public partial class TariffMaster : System.Web.UI.Page


{
ClsDbLayer _objDb = new ClsDbLayer();
protected void Page_Load(object sender, EventArgs e)
{
}
protected void Button1_Click(object sender, EventArgs e)
{
string Query = "insert into Tariff values('" + txtTarCode.Text +
"','" + txtTarType.Text + "','" + txtTarDesc.Text + "','" + txtBED.Text
+ "','" + txtBEDType.Text + "','" + txtSED.Text + "','" +
txtSEDType.Text + "','" + txtAED.Text + "','" + txtAEDType.Text + "','"
+ txtTarCESS.Text + "','" + txtTarCESSType.Text + "','" +
rblTarStatus.SelectedItem + "','" + txtTarDate.Text + "','" +
txtTarUserName.Text + "')";
int i = _objDb.Insert(Query);
if (i != -1)
{
Response.Write("Saved Sucessfully");
}
else
{
Response.Write("Not Saved");
}
}
}

Admin Login

65

Central Excise Operation of a Manufacturing Unit


using
using
using
using
using
using
using
using
using
using

System;
System.Data;
System.Configuration;
System.Collections;
System.Web;
System.Web.Security;
System.Web.UI;
System.Web.UI.WebControls;
System.Web.UI.WebControls.WebParts;
System.Web.UI.HtmlControls;

public partial class AdminLogin : System.Web.UI.Page


{
protected void Page_Load(object sender, EventArgs e)
{
}
protected void Button1_Click(object sender, EventArgs e)
{
if (txtUserName.Text == "Admin" && txtPassword.Text == "Admin")
{
Response.Redirect("AdminPage.aspx");
}
else
{
Response.Write("Invalid Login");
}
}
}

User Login:
66

Central Excise Operation of a Manufacturing Unit


using
using
using
using
using
using
using
using
using
using

System;
System.Data;
System.Configuration;
System.Collections;
System.Web;
System.Web.Security;
System.Web.UI;
System.Web.UI.WebControls;
System.Web.UI.WebControls.WebParts;
System.Web.UI.HtmlControls;

public partial class UserLogin : System.Web.UI.Page


{
protected void Page_Load(object sender, EventArgs e)
{
}
protected void Button1_Click(object sender, EventArgs e)
{
if (txtUserName.Text == "srm" && txtPassword.Text == "srm")
{
Response.Redirect("Default.aspx");
}
else
{
Response.Write("Invalid Login");
}
}
}

67

Central Excise Operation of a Manufacturing Unit

Home Page:

68

Central Excise Operation of a Manufacturing Unit

Admin Login:

69

Central Excise Operation of a Manufacturing Unit

Admin Page:

70

Central Excise Operation of a Manufacturing Unit

Tariff Mater:

71

Central Excise Operation of a Manufacturing Unit

User Login:

72

Central Excise Operation of a Manufacturing Unit

User Page:

Product Master:
73

Central Excise Operation of a Manufacturing Unit

Scrap Master:
74

Central Excise Operation of a Manufacturing Unit

GRN Details:
75

Central Excise Operation of a Manufacturing Unit

GRN Supplier:

76

Central Excise Operation of a Manufacturing Unit

Job Work Entry:

77

Central Excise Operation of a Manufacturing Unit

Sales Master:

78

Central Excise Operation of a Manufacturing Unit

Tariff Master:
79

Central Excise Operation of a Manufacturing Unit

80

Central Excise Operation of a Manufacturing Unit

Product Master:
81

Central Excise Operation of a Manufacturing Unit

Scrap Master
82

Central Excise Operation of a Manufacturing Unit

GRN Details
83

Central Excise Operation of a Manufacturing Unit

84

Central Excise Operation of a Manufacturing Unit

Sales

85

Central Excise Operation of a Manufacturing Unit

86

Central Excise Operation of a Manufacturing Unit

GRN Supplier

Conclusion:

87

Central Excise Operation of a Manufacturing Unit


This project entitled Central Excise Operations was successfully completed and
all three phases namely as system analysis, system design and system implementation are
thoroughly tested with live data. This project is validated using unit testing.

The project is fully menu driven one. So, any one with little knowledge of
computer can handle the software and the requirements for the user are fully completed.
The project is simple and suitably designed for end users.

BIBLIOGRAPHY

88

Central Excise Operation of a Manufacturing Unit


Active Server Page Unleashed, Stephen Walther, Second Edition,
Sums Publishing 2003
Active Server Page 2.0, Richard Launcher, Second Reprint, Queue
2003
Roger S.Pressman, 1997, Software Engineering A Parishioners
Approach,

Fourth Edition, McGraw-Hill International


MS SQL Server 2000, Kaleen Delaney JOE Cellos SQL for
smartens, JOE

Cello The Gurus Guide to Transact SQL, Ken Henderson


Websites:
http://www.dotnettutorials.com
http://www.csharpcorner.com
http://www.w3schools.com

89

Central Excise Operation of a Manufacturing Unit

90

S-ar putea să vă placă și