SUPPLY CHAIN MANAGEMENT

A PROJECT REPORT


Submitted by

S.B.ARAVIND(41502104007)
M.KARTHIKEYAN(41502104044)



in partial fulfillment for the award of the degree

of

BACHELOR OF ENGINEERING

IN

COMPUTER SCIENCE AND ENGINEERING


S.R.M ENGINEERING COLLEGE



ANNA UNIVERSITY : CHENNAI 600 025


APRIL 2006











ANNA UNIVERSITY : CHENNAI 600 025



BONAFIDE CERTIFICATE


Certified that this project report SUPPLY CHAIN MANAGEMENTis the bonafide
work of S.B.ARAVIND, M.KARTHIKEYAN who carried out the project work under
my supervision.


SIGNATURE: SIGNATURE:

Prof.S.S.SRIDHAR , Mrs.B.SREEDEVI,
HEAD OF THE DEPARTMENT SUPERVISOR

COMPUTER SCIENCE AND COMPUTER SCIENCE AND
ENGINEERING ENGINEERING
S.R.M.Engineering College S.R.M.Engineering College
Kattankulathur-603203 Kattankulathur-603203
Kancheepuram District Kancheepuram District



ACKNOWLEDGEMENT


Our foremost and profound gratitude to our Director Dr.T.P.Ganesan and our
Principal Prof.R.Venkataramani for making available to us state of art laboratories and
a highly equipped library for our research and the successful implmentation of our
project.

Our sincere thanks and respects to Prof.S.S.Sridhar,M.S(Ph.D), Head of the
Department of Computer Science and Engineering Department for giving us the freedom
to explore and for providing us with a highly qualified team for guiding us in our project.

Our heartfelt gratitude to our Project coordinators Mrs.D.Malathy,M.E,(Ph.D),
and Mrs.C.Lakshmi,M.E,(Ph.D) for guiding us in choosing our area of intrest and
enabling an in-depth research of the project by sharing their expertise.

We would like to thank our Project guide Mrs.B.Sreedevi,B.E,(M.Tech). for the
constant guidance and encouragement in helping us to overcome the obstacles in our
project and for putting us on the right track whenever necessary.







ABSTRACT


The traditional concept of business is now obsolete. Companies, both
manufacturing and service, are creators of value, not simply makers of products.
This can be implemented through supply chain management system. Supply chain
management (SCM) is the process of planning, implementing, and controlling the
operations of the supply chain with the purpose to satisfy customer requirements as
efficiently as possible. Supply chain management spans all movement and storage of raw
materials, work-in-process inventory, and finished goods from point-of-origin to point-
of-consumption.
Supply chain management is a consideration of all possible occurring events
and factors that can cause a disruption in a supply chain. With SCM possible scenarios
can be created and solutions can be planned. The major components of Supply Chain
Management namely, Plan, Source, Make, Deliver, Return, each have numerous
process underlying them.
The main aim of Supply Chain software will be to integrate these
components to successfully optimize costs and maximize profit by making the best
decisions.






iv

TABLE OF CONTENTS

CHAPTER NO. TITLE PAGE NO.

ABSTRACT iii
LIST OF TABLE vi
LIST OF FIGURES vi

1. INTRODUCTION 1
1.1 About the project 1
1.2 Supply Chain 2
1.3 Need for SCM 3
2. LITERATURE REVIEW 4
2.1 Project Description 4
2 .2 Components of SCM 9

3. SYSTEM REQUIREMENTS 11
3.1 Hardware Requirements 11
3.2 Software Requirements 11
3.3 Software Description 12
3.4 Installation Procedure 14
4. SYSTEM DESIGN 15
4.1 Input Design 17
4.2 Output Design 18
4.3 Table Structure 19
5. TESTING AND IMPLEMENTATION 21
5.1 System Testing 21
5.2 Testing Techniques 21
5.2.1 Unit Testing 22
5.2.2 Integration Testing 22
5.2.3 Validation Testing 22
5.2.4 Output Testing 23
5.2.5 User Acceptance Testing 23
5.3 Implementation 24
5.3.1 Module Details 24

6. APPENDIX 26
6.1Sample Output Forms 26
6.2Sample Source Code 30

7. BENEFITS AND USES 65
8. CONCLUSION 66
9. REFERENCES 67












LIST OF TABLES


CHAPTER NO TITLE PAGE NO

4.3 Table Structure 19



LIST OF FIGURES

CHAPTER NO TITLE PAGE NO


3.2 Interaction Between Components 11

4 General View of the System 15

4 System Flow Diagram 16










CHAPTER 1
INTRODUCTION

1.1 ABOUT THE PROJECT
Supply Chain Management is the management of resources to design,
procure, fabricate, produce, assemble, store, distribute, use, maintain, recycle, and
dispose of goods and services. Supply Chain Management focuses on globalization
and information management tools which integrate procurement, operations, and
logistics from raw materials to customer satisfaction. Communication and
analytical skills are the key to supply chain success.

Future managers are prepared to add product value, increase quality, reduce costs,
and increase profits by addressing the needs and performance of: supplier relations,
supplier selection, purchasing negotiations, operations, transportation, inventory,
warehousing, benchmarking, third-party vendors, electronic commerce, recycling, supply
chain electronic software, and customer relations.
Supply chain software promises to integrate the working of a supply
chain by optimizing costs and maximizing profits. Supply chain management
can also lead to collaborations among suppliers, customers and
manufacturing units which are beneficial to all parties.

Supply Chain Management is a business approach that focuses on integration, and
partnerships, in order to meet customers needs on a timely basis, with relevant and high
quality products, produced and delivered in a cost effective manner. It aims at improving
the processes of the supply chain to optimize costs and increase profit. Companies, both
manufacturing and service, are creators of value, not simply makers of products. A
"supply chain" consists of interconnected components required to transform ideas into
delivered products and services. Supply Chain Management focuses on globalization and
information management tools which integrate the supply chain operations to transform
ideas into delivered products and services.

1.2 SUPPLY CHAIN

Supply chain is a network of facilities that perform the function of
procurement of materials, transformation of these materials into intermediate and
finished products and distribution of these finished to the customers. It involves all
those processes that are involved in the transformation of raw materials to the final
finished product. These include procurement, design, fabrication, production,
storage, distribution, recycling and disposal. Therefore, the supply chain is the heart
of any manufacturing organization.

1.3 NEED FOR SUPPLY CHAIN MANAGEMENT

Take an example of a company producing cars. The supply chain includes
various departments like Production, Purchasing, Spare parts, Research &
Development, Distribution, etc. Each department has its own objectives and targets
to achieve. But the activities of each department depend directly or indirectly on the
functioning of other departments. For example, the Purchasing department verifies
with the Production and Spare parts department before making purchases.
Sometimes the objectives of different department conflict and this results in each
department making the decisions independently. For example, the natural conflict
between a customer service department that gives incentives to maximize customer
satisfaction and a distribution center that focuses on maximizing profits. In general,
the challenge is to combine the various departments functions while keeping in
mind each department has its own objectives and goals. Supply Chain Management
aims at integrating the core functions of the organization to aid the decision making
process.
In the present world scenario, every company is aiming to grow at a global
level. This means interacting with vendors, suppliers and customers to purchase and
markets goods and services on a global basis. Relentless focus on time, cost and
quality have sharpened the need to coordinate and cooperate with business partners
around the world in order to meet and exceed customers needs and wants.




CHAPTER 2
LITERATURE REVIEW

2.1 PROJECT DESCRIPTION
The concept is appearing in various industries and is moving to moving into smaller
companies. Start to understand what it is, and what it means to you. Supply Chain
Management is a dynamic paradigm driving through companies. Articles on supply chain
management appear in many different publications, national and international, with
different target audience. While many of the stories relate to large companies who supply
large retailers or grocers, the attention SCM is getting is phenomenal. Add in the global
impact of customers, competitors and suppliers; and the magnitude of the supply chain is
very significant.
What It Is All About. Supply Chain Management is a reverse of prior practices where
manufacturers supplied product to customers and they wanted to. Now customers tell
suppliers how and when they want their inventory delivered. The driver behind Supply
Chain Management is to remove inefficiencies, excess costs and excess inventories from
the supply pipeline which extends from the customer back through his suppliers and
through his suppliers' suppliers and so on back. By having the program driven by the
customer, it is hoped that inventories, caused by uncertainties and slow response, will be
significantly eliminated. While there are sales incentives to major suppliers with the
carrot of category management or similar programs, the success of supply chain
management rests with logistics.
The Five Key Issues of Logistics Effectiveness are core to Supply Chain Management--
Movement of Product
Movement of Information
Time / Service
Cost
Integration, both internal and external, both organizations and systems
Supply chain management requires a logistics model based on quick order to delivery
response. A model which focuses from vendors' doors through to delivery to customers'
doors. The model must meet the customers' demanding and specific requirements. It
requires organizational flexibility and responsiveness, internal and external teamwork and
demands the use of processes and technology. A common practice which causes
inefficiencies, excess inventories and high costs is forward-buying. On the surface, it
looked like a way to purchase at a low price. But in reality, this practice is inefficient and
results in additional, higher costs and negative impact throughout the supply chain.
Forward-buying strains the capabilities of suppliers to respond and for the distribution
department of customers to handle the products. It creates an operational and cost
inefficiency for both supplier and customer. By forcing excess sales through the supply
chain, then the hidden costs of manufacturing and distribution valleys, after the huge
peak caused by the forward-buy can be significant. Supply Chain Management is about
what the customer demands. It is not about what the supplier is capable of doing at
present.


The customer requirements may vary by customer, but they do have certain consistencies
to logistics--
Quick response to orders from order receipt through shipment to invoicing
Complete and accurate orders / no backorders
Delivery windows or appointments
Special shipment preparation as to packaging, marking, labeling, stenciling, slip
sheets or pallets, etc.
Bar coding
EDI
Carrier selection
Effects of Supply Chain Management. The initial benefits of supply chain management
accrue to the customer, the initiator of his supply chain. He earns the reduction in
inventories by driving out excesses inventories which he must purchase, store and be
responsible for. The impact of supply chain management to the supplier may be more
difficult to classify, initially, as benefits. They may vary, but may include--
Fewer orders initially while the customer draws down excess inventories.
Small and more frequent orders.
Vendor carries inventory, not the customer.
Higher warehousing costs for picking smaller and more orders.
Higher freight costs for shipping smaller order and more orders.
Penalties for not meeting the customer's requirements.
Possible loss of business for not meeting the customer's requirements.
Additional capital expenditure to satisfy the need for information and technology
to provide the base for SCM responsiveness. Supply chain management success
dictates new ways of doing business for suppliers. There is no "standard" practice;
no "standard" way of doing business. Instead, there is a practice for each
customer.
If a company has one hundred customers, he may have one hundred customer
practices. Adjusting this way challenges traditional management concepts.
Impediments. There are impediments to supply chain success. Emphasis is
presently on the initial customer-supplier link. It is not coordinated through the
supply chain. Instead as the effects ripple through the supply chain, it is more like
a "whisper down the lane" impact, where suppliers are not clear as to their role
and what they must do. Responding to supply chain demands is not easy. There
are issues which must be recognized and dealt with, such as--
Accounting Silos. Supply chain management is a leading-edge technique. Yet the
traditional cost measurements used by companies goes back to the Model A.
Meeting Generally Accepted Accounting Principles is one thing; measuring the
costs and benefits of logistics and supply chain management is something quite
different.
Logistics has a difficulty with having its costs properly identified, captured and
measured properly. Some costs, such as freight, show on the P&L. Some, such as
inventory, show on the balance sheet. And the driver to supply chain
management, service, does not appear on any financial document. As a result,
suppliers may have difficult seeing the cause-effect of supply chain management
to them and the gain-sharing benefits as you progress with it. Activity-Based
Costing is the closest approach to measuring the effects of supply chain
management on an organization. With ABC, you can develop cost information
based on the activities required to the logistics service.
Functional Silos. Supply chain management is a process which requires integrated
teamwork. Its goal is customer order-response-satisfaction. Yet traditional
organizations, with their responsibilities and goals, may not be teamwork
enhancers. Each function may have its own internal goals which run counter to
effective logistics performance necessary for supply chain management success.
Look at the underlying driver of supply chain management, the customer. In
developing a tailored process to meet the needs of each customer, who is
responsible for it? Sales--after all, it is one of their customers?
Logistics, since they are on the front-line for making supply chain management
work? Manufacturing who must be able to adapt to the dynamics of point-of-sale
or other production drivers? Or consider that the company uses tools such as MRP
to drive its production planning; yet supply chain management is a pull, not a
push approach. How does this shift in a company's practice be absorbed? Who is
responsible then for a company's supply chain management? The answer is
everyone in the company is responsible; yet the organization has often dictated
that one group be responsible.
Reactionary Practices. Since supply chain management is a process, it takes time,
focus and discipline to make the necessary changes to the way a company does
business. It is not reacting to an order; it is responding to a customer. "Fighting
fires" and other reacting events are anti-process and, while it seems like it is
customer-focused, it is not. Instead reacting to crises and other emergencies keeps
a company for doing what must be done to implement the needed process for
supply chain management. At the end of day of crises, the company is often no
closer to implementing the necessary integrated process.
Tactical versus Strategic Role for Logistics. Supply chain success depends upon
logistics. To develop the necessary programs for supply chain management, the
logistics organization must be involved in the planning activity from the
beginning. Other groups cannot meet without logistics, decide what logistics must
do, give logistics orders and think there will be supply chain success. If that
approach is used, then the likelihood of meeting the customer requirements and
implementing the technology and teamwork needed will likely not be there.
Unclear Mission. Supply chain management requires a rethinking of the company
and the logistics mission. Is it customer or is it cost? These can be conflicting
goals. Saying the mission is service, then measuring it by cost can cause
organizations to lose focus on what must be done. Supply chain management is a
new concept and requires a reassessment of the what the company is doing, where
it is going and how it wants to get there.
2.2 COMPONENTS OF SUPPLY CHAIN MANAGEMENT
Plan The main portion of Supply Chain Management is planning. In
order to effectively manage all resources in meeting the customers
demands, an efficient strategy is to be evolved. This strategy should
involve a set of metrics that can monitor the supply chain so that it is
efficient.
Source The suppliers who will provide the raw materials, products
or services that is required to produce the final product form the source.
It is required to develop a set of pricing, delivery and payment
processes with suppliers and create metrics for monitoring and
improving relationships. It is also important to develop a set of
processes managing the inventory of goods and services received from
suppliers. This helps in economizing the sourcing.
Make This is the manufacturing step or the production step. The
activities necessary for production, testing, packaging and preparation
for delivery need to be scheduled efficiently because this step is the
most metric-oriented process. The measure of quality level,
production output and worker productivity, talk volumes of the
success of the Supply Chain Management process and the company.
Deliver This is a very crucial step of logistics. The activities like
receipt of orders from customers, maintaining a good network of
warehouses, and setting up an invoicing system to receive payments
play an important role in customer service relationships.
Return The most sensitive part of the supply chain is handling of
defective products. It is necessary to create a strong network for
receiving defectives products and also excess products or unsold
products from outlets. This step has a big impact in the customer
service relationships. It also builds up dealer and customer
confidence.

CHAPTER 3
SYSTEM REQUIREMENTS
3.1 HARDWARE REQUIREMENTS
Processor PENTIUM IV
RAM 256 MB
Hard Disk 40 GB
Cache Memory 11,011,968 Bytes
Virtual Memory 64 MB

3.2 SOFTWARE REQUIREMENTS
Web Server BEA Web Logic Server
Browser Internet Explorer
Server Side Scripting J SP, Servlets
Database Oracle9i
Client Side Scripting HTML,J SP

The figure1 illustrates the links between various components involved in this system:




FIGURE 1

Figure 1
3.3 SOFTWARE DESCRIPTION

HTML

Html is the hypertext markup language. It is the fundamental coding
language of the Internet. The original internet of the html specification was to allow web
authors to describe the structure of a page.
This language is used to layout pages that are capable of displaying all the
diverse kinds of information that the web contains.
Html provides everything needed to develop and design
world-class documents that are provided by World Wide Web. It presents variety of
features to be user oriented, goal driven guide that win change the way of its documents.
The Internet is exploded into a technological to retrieve information around the world.

Java Server Pages:

A J SP page is a text-based document that describes how to process a
request to create a response. J SP is a java based technology that simplifies the process of
developing dynamic web sites. With J SP, web designers and developers can quickly
HTML AND
A A SC
JAVA

SERVLET DATABA
incorporate dynamic elements into web pages using embedded J ava and simple markup
tags. These tags provide the html designer with a way to access data and business logic
stored and inside J ava objects.
J ava Server Pages are text files with the extension .jsp, which take the
place of traditional HTML pages. J SP files contain traditional HTML along with
embedded code that allows the developer to access data from the java code running on
the server.

ENTERPRISE JAVA BEANS

Enterprise J ava Bean is a Server Component Model for J ava and is
a specification for creating server side, scalable, transactional, multi-user and secure
enterprise level applications. Most importantly, EJ Bs can be deployed on top of
existing transaction processing systems including traditional transaction processing
monitors, web servers, database servers,
A major highlight of the EJ B specification is the support for ready
made components. This allows you to plug and work with off the shell EJ Bs without
having to develop or test them or have any knowledge of their inner workings.

ORACLE


Oracle is a high performance, relational database management system for
developing online applications. The collection of tools, utilities & applications allows us
to manipulate an oracle database many of these products are 4-GL tools & they let us to
use interactive screens to create application programs.
Oracles unique clustering techniques for storing data are main performance gain.
A variety of auditing commands and journalizing ease error detection and tracking tasks.
Finally, professional oracle stores the DBMS kernel in extended memory, so more
memory is available for other applications.





3.4 INSTALLATION PROCEDURE

Install softwares such as oracle9i, Bea WebLogic Server and Windows
2000 professional.
Open the SCM application in the BEA Web Logic Server
Select the server for the application namely BEA WebLogic Server 8.1
Build the application to update the changes made to the tables.
Start both the weblogic and oracle servers.
Open the console window of the web logic server to perform the linking.
Create the connection pool and configure new J DBC connection pool by
selecting the database type as oracle and database driver as type4 version
8.1.7.
Define the connection properties by specifying the host name, port number
and the user name.
Specify the connection pool name and select the driver and specify the
same in the URL.
Now the connection is successfully established.
Select the CGI Server in the window and click the Create And Deploy
button.
Now configure a new J DBC Data Source and select the pool name which
have been already specified in the preceding steps.
Deploy a new application, upload your files with the extension (*.jar).
Success should appear in the last column of the table that appears in the
next window and this shows the connection has been established
successfully.


CHAPTER 4
SYSTEM DESIGN

Design is an iterative process through which requirements are translated
into a blueprint for constructing the software. The design is essentially the bridge
between requirements specification and final solution for satisfying the requirements.
Figure 2 illustrates the modules that are needed for the system, the
specifications of the modules and how the modules should be interconnected.

GENERAL VIEW OF THE SYSTEM



Response Request



Response Request



Figure 2








Presentation layer
with jsp and html
Business Logic layer
Database

SYSTEM FLOW DIAGRAM


















Figure 3


The above shown figure 3 explains the overall flow of events inside the system.


4.1 Input Design:
Input design is the bridge between users and information system. It is a part of
overall design, which requires very careful attention.
The pages which has inputs in the system is discussed below:
Login
Input
Links containing
History,
Customers,
Suppliers,
Products and View
New Customer,
New Supplier,
Customer Order,
Supplier Order,
Administration.
Administration
module
checking
Process
Updating
product list
stockstatus
print invoice
print challan
payment
Customer Order
Customer Data entry
Process
Customer
Data Entry
Output
Customer
Details
A
A
Supplier Details
Supplier Data
Process update
Supplier Details
Print
Supplier
Details
New user registration
Order form
Issues
Quotations
LOGIN FORM:
The customer gives the input for login into the system. The inputs are
customer/supplier id and password. If they are valid he enters into the system.
NEW USER REGISTRATION:
New customer gives their information like name, password, address, e-mail, etc.
ORDER FORM:
The customer must select the product and enter the number of quantity required
and also specify the model.

ISSUES FORM:
The customer can enter the problems they face with the particular component they
had purchased. The issue will be sent to the corresponding supplier



QUOTATIONS:
The supplier enters the amount and the other charges for the particular product
required by the company.

4.2 OUTPUT DESIGN:
The output is an essential element of any system. As the output can be presented
in many different ways, the appropriate method should be used while presenting the user
with the output that is convenient for them. So output is the prime element designed in
the system.
According to the requirements of the system, various types of outputs are as
desired and designed as follows.

ITEM DETAILS:
This is used to display the items that are being supplied by the supplier to the
company.

PRODUCT DETAILS:
The products that are available for the customer to purchase are displayed by this
form.

BILL DETAILS:
This displays the bill generated for the order placed by the customer to buy the
products.

ISSUES:
This is used to display the issues about the product given by the supplier to the
customer.

4.3 TABLE DETAILS

CUSTOMER DETAILS

Field Name Data Type Constraints
Customer Name Text Not Null
Customer Id Number Primary key
Address Text Not Null
Telephone Number Number Not Null
Mobile Number Number Not Null
Contact Person Text Not Null
Credit Facility Char Not Null
Credit Limit Number Not Null
Special-Discount Number Not Null
Online Balance Number Not Null

SUPPLIER DETAILS

Field Name Data Type Constraints
Supplier Name Text Not Null
Supplier Id Number Primary key
Address Text Not Null
Telephone Number Number Not Null
Mobile Number Number Not Null
Contact Person Text Not Null
Credit Facility Char Not Null
Credit Limit Number Not Null

ITEM MASTER

Field Name Data Type Constraints
Item Name Text Not Null
Item Id Number Primary key
Quantity on hand Number Not Null
Reorder Level Number Not Null
Maxmum Quantity Number Not Null

ISSUES
Field Name Data Type Constraints
Product Name Text Not Null
Issue Id Number Primary key
Issue Text Not Null
Date of purchase Date Not Null

QUOTATIONS

Field Name Data Type Constraints
Product Name Text Not Null
Product Id Number Primary key
Number of item Number Not Null
Price per item Number Not Null
Company Name Text Not Null

CHAPTER - 5
TESTING AND IMPLEMENTATION

5.1 SYSTEM TESTING :

System testing is the stage of implementation, which is aimed at ensuring that the
system works accurately and efficiently before live operation commences. Testing is vital
to the success of the system. System testing makes a logical assumption that all the parts
of the system are correct; the goal will be successfully achieved. The candidate system is
subject to a variety of tests: on-line response, volume, stress, recovery, and security and
usability tests.
An elaborate testing of data is prepared and the system is tested using that test
data. While testing, errors are noted and corrections are made. The users are trained to
operate the developed system. Both hardware and software securities are made to run the
developed system successfully in future.
5.2 TESTING TECHNIQUES :

Unit testing
Integration testing
Validation testing
Output testing
User acceptance testing


5.2.1 UNIT TESTING:

Unit testing focuses verification efforts on the smallest unit of software design,
the module. This is also known as Module Testing. The modules are tested separately.
The testing is carried out during programming stage itself. In this testing step each
module is found to be working satisfactorily as record to the expected output from the
module.


5.2.2 INTEGRATION TESTING:

Integration testing focuses on the design and the construction of the software
architecture . Data can be lost across an interface; one module can have adverse effect on
another sub function and so on. Thus integration testing is a part that the software meets
all functional, behavioral and performance requirements the errors, which are uncovered
during integration testing, are corrected during this phase.

5.2.3 VALIDATION TESTING:

Errors discovered where corrected prior to completion of this project with help of
the user by negotiating to establish a method of resolving deficiencies. Thus the proposed
system under consideration has been tested by using validation testing and found to be
working in satisfactorily

5.2.4 OUTPUT TESTING:

After performing the validation testing the next step is output testing of the
proposed system since no of system could be useful if it does not produce the required
output in the specific format. The output generated or displayed by the system under
consideration is tested asking the users about the format required by them. Here, the
output is considered in to two ways one is the screen and the other is printed format. The
output format on the screen is found to be correct as the format designed according to the
user needs. For the hard copy also, the output comes out as a specified by the user. Hens
output testing does not result in correction in the system.

5.2.5 USER ACCEPTANCE TESTING:

User acceptance of a system is the key factor for the success of any system.
The system under vconsideration is tested for user acceptance by constantly keeping it
touch with the prospective system user at the time of developing and making changes
wherever required. This is done with regard to the following points.
Input screen design
Output screen design
On-line message to guide the user
Menu driven system
Format of ad-hoc reports and other outputs.

5.3 IMPLEMENTATION
Implementation is a process of converting design process into coding in
particular programming language. Normally, a specific project is split into number of
modules and each module is split into number of sub modules. Then each module
contains separate classes. Then, the classes are integrated to perform a specific task. The
integrated parts together forms the main module.

This project was implemented using the WebLogic server and the bean
component will be created using the Enterprise J ava Beans. In this project, several pre-
defined and user-defined classes were used to implement the functions most effective.

5.3.1 MODULE DETAILS :
This project is divided into three modules. They are
Client Side Data Access And Recovery
Middle Tier Layer Distribution
Database Server Application

Client Side Data Access And Recovery: -

In this module, the customer will place an order and an entire order
will process. Here J SP page will be created which take all the validations and customer
will make the valid request order and the items. This order would be passed to the next
layer, which will be the transaction/router layer.

Middle Tier Layer Distribution: -

This is the core of the project where the bean component is created
and deployed. This bean component will locate the database server irrespective or the
remote locations and this bean component will process request from the server and pass it
onto the client. Indirectly, it is routing the calls.
Database Server Application: -
In this module, the bean component processes the client request
and takes part the data to the client or rather route the request to the client.
Finally, the data are updated at a single transaction using bean
component. Thus, we are ensuring both distributed processing as well as centralized
control.







CHAPTER - 6
APPENDIX
6.1 SAMPLE FORMS































6.2 SAMPLE SOURCE CODE
HOME PAGE:
<%@ page language="java" contentType="text/html;charset=UTF-8"%>
<%@ taglib uri="netui-tags-databinding.tld" prefix="netui-data"%>
<%@ taglib uri="netui-tags-html.tld" prefix="netui"%>
<%@ taglib uri="netui-tags-template.tld" prefix="netui-template"%>
<netui:html>
<head>
<title>
Web Application Page
</title>
</head>
<link rel="stylesheet" type="text/css" href="<%=request.getContextPath()
%>/resources/css/Styles.css">
<body background='<%=request.getContextPath()%>/resources/images/Dc225.jpg>
<jsp:include page="title.jsp" />
<form >
<center>
<a href="Login1.jsp">Customers</a><br><br>
<a href="Login_sup1.jsp">Suppliers</a><br><br>
<a href="admin.jsp">Administartor</a><br><br>
</center>
</form><br><br>
<jsp:include page="Footer.jsp" />
</body>
</netui:html>
CUSTOMER LOGIN:

<!--Generated by WebLogic Workshop-->
<%@ page language="java" contentType="text/html;charset=UTF-8"%>
<%@ taglib uri="netui-tags-databinding.tld" prefix="netui-data"%>
<%@ taglib uri="netui-tags-html.tld" prefix="netui"%>
<%@ taglib uri="netui-tags-template.tld" prefix="netui-template"%>
<netui:html>
<head>
<title></title>
</head>
<link rel="stylesheet" type="text/css" href="<%=request.getContextPath()
%>/resources/css/Styles.css">
<body background='<%=request.getContextPath()
%>/resources/images/Dc225.jpg'>
<form method="post" name="loginform" action="Authentication1.jsp"
ONSUBMIT ="return login_check(this)">
<table align="center"border="0">
<TBODY>
<tr align="center">
<td class="MainTitle">CUSTOMER LOGIN</td>
</tr>
</TBODY>
</table>

<br><br><br>
<table border="1" align="center">
<TBODY>
<tr>
<td class="Labels">UserName</td>
<td>
<input type="text" name="usertxt" class ="Controls">
</td>
</tr>
<tr>
<td class="Labels">Password</td>
<td>
<input type=password name="passtxt" class="Controls">
</td>
</tr>
<tr>
<td class="Labels">User Type</td>
<td>
<select name="user_typetxt"
class="Controls"><option>Customer</option></select>
</td>
</tr>
</TBODY>
</table><br><br>
<table align="center" border="0" cellpadding="2" cellspacing="2" >
<TBODY>
<tr align="center">
<td><input type="submit" value="Login" width="120"
class="ThemeButtons" accesskey="S" style="width:70px">
</td>
<td><input type="reset" value="Reset" width="120"
class="ThemeButtons" accesskey="R" style="width:70px">
</td>
</tr>
</TBODY>
</table>
<br><table align="center"><TBODY><tr><td><a
href="New_Customer.jsp?name=customer">Sign Up as New
Customer</a></td></tr></TBODY></table>
</td></tr></TBODY></table>
</form>
<jsp:include page="Footer.jsp" />
<script src="/DCRWeb/resources/css/Validation.js">
</script>
</body></netui:html>

ADD PRODUCTS:

<!--Generated by WebLogic Workshop-->
<%@ page language="java" contentType="text/html;charset=UTF-8"%>
<%@ taglib uri="netui-tags-databinding.tld" prefix="netui-data"%>
<%@ taglib uri="netui-tags-html.tld" prefix="netui"%>
<%@ taglib uri="netui-tags-template.tld" prefix="netui-template"%>
<netui:html>
<head>
<link rel="stylesheet" type="text/css"
href="/DCRWeb/resources/css/Styles.css">
<title>
Web Application Page
</title>
</head>
<body>
<form name="add_form" action="Product_Update.jsp" >
<table align="center" border="0">
<tbody><tr><td class="MainTitle" align="center">AddNew
Products</td></tr></tbody>
</table><br><br>
<table align="center" border="0"cellpadding="2" cellspacing="2">
<tbody>
<tr class="FieldTopLabels">
<td align="right">Vendor Name</td>
<td><select name="vname" class="Controls">
<option>---Select---</option>
<option>Samsung</option>
<option>Sony</option>
<option>LG</option>
<option>IBM</option>
</select>
</td>
</tr>
<tr class="FieldTopLabels" style="DISPLAY:NONE">
<td align="right">Product Image</td>
<td><input type="text" name="p_imagetxt"
class="Controls"></td>
</tr>
<tr class="FieldTopLabels">
<td align="right"><strong>Product Name</strong></td>
<td><input name="pname" class="Controls"
type="text"></td>
</tr>
<tr class="FieldTopLabels">
<td align="right">Unit of Mesurements</td>
<td><select name="unit_mesurementtxt" class="Controls">
<option value="Units">Units</option>
<option value="Kgms">Kgms</option>
</select>
</td>
</tr>
<tr class="FieldTopLabels">
<td align="right">Price/Quantity</td>
<td><input type="text" name="pricetxt"
class="Controls"></td>
</tr>
<tr class="FieldTopLabels">
<td align="right">Produt Description</td>
<td><textarea name="pdesctxt" cols="26" rows="3"
class="Controls"></textarea></td>
</tr>
<tr class="FieldTopLabels">
<td align="right">Quantity in Hand</td>
<td><input type="text" name="qhandtxt"
class="Controls"></td>
</tr>
<tr class="FieldTopLabels">
<td align="right">Minimum Quantity</td>
<td><input type="text" name="min_quntxt"
class="Controls"></td>
</tr>
<tr class="FieldTopLabels">
<td align="right">Maximum Quantity</td>
<td><input type="text" name="max_quntxt"
class="Controls"></td>
</tr>
<tr class="FieldTopLabels">
<td align="right">Reorder Level</td>
<td><input type="text" name="reodertxt"
class="Controls"></td>
</tr>
</tbody>
</table>
</form>
</body></netui:html>


PRODUCT LIST:

<html>
<HEAD>
<link rel="stylesheet" type="text/css"
href="/DCRWeb/resources/css/Styles.css">
</HEAD>
<body background='<%=request.getContextPath()
%>/resources/images/Dc225.jpg'>
<p>&nbsp;</p>
<form>
<table width="100%" border="0" cellspacing="3" cellpadding="3">
<TBODY>
<tr class="GridNormalRow">
<td><a href="Item_View.jsp?name=printer"
target="mainFrame">Printer</a></td>
</tr>
<tr class="GridNormalRow">
<td><a
href="Item_View.jsp?name=HardDisk"target="mainFrame">Hard
Disk</a></td>
</tr>
<tr class="GridNormalRow">
<td><ahref="Item_View.jsp?name=cdrom"target="mainFrame" >CD
ROM</a></td>
</tr>
<tr class="GridNormalRow">
<td><a href="Item_View.jsp?name=keyboard" target="mainFrame"
>Key Board</a></td>
</tr>
<tr class="GridNormalRow">
<td><a href="Issues.jsp" target="mainFrame" >Issues</a></td>
</tr>
<tr class="GridNormalRow">
<td><a href="Sales_order_cancel1.jsp" target="mainFrame" >Order
Cancelation</a></td>
</tr>
<tr class="GridNormalRow">
<td><a href ="Main2.jsp" target="_parent" >Logout</a></td>
</tr>
</TBODY>
</table>
</form></body><script></script></html>

PRODUCT UPDATE:

<!--Generated by WebLogic Workshop-->
<%@ page import="EJ BNew.ProductRemoteHome"%>
<jsp:useBean id="data" class="Data_con.J dbc_Con" scope="application"/>
<%@ taglib uri="netui-tags-databinding.tld" prefix="netui-data"%>
<netui:html>
<head>
<title>
Web Application Page
</title>
</head>
<link rel="stylesheet" type="text/css"
href="/DCRWeb/resources/css/Styles.css">
<body>
<form>
<%! String id ="P101";%>
<%
try{
java.sql.Statement st =data.Connect_J dbc();
ResultSet rs =st.executeQuery("select p_code from
product_master");
int t1 =100;
while(rs.next()){
int t =Integer.parseInt(rs.getString("p_code").substring(1,4));
if(t>=t1){
t1 =t;
}
}
id ="P"+(t1+1);
data.con_close();

}catch(Exception ex){
out.println(ex);
}
InitialContext ctx =new InitialContext();
Object obj =ctx.lookup("product_jndi");

ProductRemoteHome homeobj =
(ProductRemoteHome)PortableRemoteObject.narrow(obj,ProductRemoteHo
me.class);
ProductRemote remoteobj =homeobj.create(id); %>
<p class="MainTitle">Your Item:<i><%=id%></i>added</p>
</form>
</body>
</netui:html>



PURCHASE ORDER:

<%@page import="java.sql.Connection" errorPage="Errors.jsp"%>
<%@page import="java.sql.DriverManager"%>
<%@page import="javax.naming.*"%>
<%@page import="javax.sql.DataSource"%>
<html>
<head>
<link rel="stylesheet" type="text/css"
href="/DCRWeb/resources/css/Styles.css">
</head>
<body>
<script language="javascript">
function chkValues(){
if (document.frmProd.id.value=="Select"){
alert("Select a Product ID");
return false;
}else
document.frmProd.submit();
}
function confirmCancel(){
if (document.frmProd.id.value=="Select"){
alert("Select a Sales Order");
return false;
}else {
if (confirm("Are u sure to Cancel.\n Press OK to Continue or
press Cancel.")==true)
document.frmProd.submit();

</tr><%
}
rs.close();
st.close();

}catch(Exception e){}
%>
</table>
<form action="New_Purchase_Order1.jsp" name="frmProd">
<%!ResultSet rs;%>
<table border="1" align="center">
<tr class="GridCaptionRow">
<td class="Labels">Select your Product ID</td>
<td><select name="id" class="Controls">
<option value="Select">--Select--</option>
<%
try{
Context ct =new InitialContext();
DataSource ds =
(DataSource)ct.lookup("data_source");
Connection con =ds.getConnection();

while(rs.next()) {
String id=rs.getString(1);
%>
<option value="<%=id%>"><%=id%></option>
<% }
st.close();
}
catch(Exception e){
out.print(e);
}
%>
</select>
</td>
<td><input type="submit" value="Order Now"
name="b_name" class="ThemeButtons" onclick="return
chkValues();"></td>
</tr>
</table>
</form>
</body>
</html>

BILLING:
<jsp:useBean id="data" class="Data_con.J dbc_Con" scope="application"/>
<%@ page language="java" contentType="text/html;charset=UTF-8"%>
<%@page import="java.sql.ResultSet"%>
<%@ taglib uri="netui-tags-template.tld" prefix="netui-template"%>
<netui:html>
<head>
<link rel="stylesheet" type="text/css" href="<%=
request.getContextPath() %>/resources/css/Styles.css">
<script src="/DCRWeb/resources/css/Validation.js"></script>
<title>
Pending Order
</title>
</head>
<body>
<form action="Update.jsp" method="post">
<table align="center" border="1" class="title_table">
<tbody><tr><td><strong>RECEIPT</strong></td></tr></tbody>
</table><br><br>
<table align="center"><tbody>
<%
float total =0;
float tax =0;
String desc =",",td =null;
String pcode =",",n =",";
try{
Statement st =data.Connect_J dbc();
ResultSet rs =st.executeQuery("select
s_no,p_code,p_name,p_desc,no_qty,price,amount from cart");
ResultSetMetaData rsmd =rs.getMetaData();
%>
<tr bgcolor="#d7912d">
<%
for(int i=1;i<=rsmd.getColumnCount();i++) {
%><td style="font-family:verdana;color:#0000ff;border-
color:#ff6633;border-width:2px;font-
size:10pt;"><strong><%=rsmd.getColumnLabel(i).toUpperCase()%>
</strong>g></td><%
}
%>
</tr>
<%
while(rs.next()) {
int t =0;
%>
<tr bgcolor="#CDCDDA">
<td><%=rs.getString("s_no")%></td>
<td><%String c =rs.getString("p_code"); pcode +=c +
",";%><%=c%></td>
<td><%=rs.getString("p_name")%></td>
<td><%td =rs.getString("p_desc"); desc +=td
+",";%><%=td%></td>
<td><%String tn =rs.getString("no_qty"); n
+=tn+",";%><%=tn%></td>
<td><%=rs.getString("price")%></td>
<td><% t =rs.getInt("amount");total +=t;
%><%=t%></td>
</tr><%
}
tax =(float)0.2*total;

total +=tax;
%> bgcolor="#f9c20c"><strong>Tax</strong><td
bgcolor="#f9c20c"><strong><%=tax%></strong></td></tr>
bgcolor="#f9c20c"><strong>Total</strong><td
bgcolor="#f9c20c"><strong><%=total%></strong></td></tr>
</tbody>
</table>
<%
rs.close();
st.close();
data.con_close();
}catch(Exception e){}
%>
<input type="hidden" name="descr" value="<%=desc%>">
<input type="hidden" name="amt" value="<%=total%>">
<input type="hidden" name="codes"
value="<%=pcode%>">
<input type="hidden" name="no" value="<%=n%>">
<table align="right"><tbody><tr><td><input type="submit"
value="Finish"></td></tr></tbody></table>
</form>
</body>
</netui:html>


ITEM ISSUES:

jsp:useBean id="data" class="Data_con.J dbc_Con" scope="application"/>
<%@page import="java.sql.ResultSet"%>
<%@page import="java.sql.Statement"%>
<html>
<head>
<link rel="stylesheet" type="text/css"
href="/DCRWeb/resources/css/Styles.css" >
<script src="/DCRWeb/resources/css/Validation.js"></script>
</head>
<body>
<FORM method="post" name="issue_form"
action="Issues_Update.jsp">
<TABLE align="center" border="1">
<TBODY>
<TR><td class="PageTitle">Item
Issues</td></TR>
</TBODY>
</TABLE>
<br><br>
<TABLE align="center" cellpadding="2" cellspacing="2"
border="1">
<TBODY>
<TR class="Controls">
<TD><strong>Customer Name</strong></TD>
<TD><strong><%=session.getAttribute("uname")%></strong></TD>
</TR>
<TR class="Controls">
<TD><strong>Item Code</strong></TD>
<td><select name="i_code" class="Controls">
<%
try{
Statement st =data.Connect_J dbc();
ResultSet rs=st.executeQuery("select
p_code,p_name from product_master");
while(rs.next()) {
String id=rs.getString(1);
String sProdName=rs.getString(2);
%><option value="<%=id%>"><%=id %>-
<%=sProdName%></option>
<% }
rs.close();
st.close();
data.con_close();
}catch(Exception e){
out.print(e);
}
%>
</select>
</TR>
<TR class="Controls">
<TD><strong>Date of Purchase</strong></TD>
<td><select name="datetxt" class="Controls">
<%for(int i=1;i<=31;i++){
%><option><%=i%></option><%
}
</select>
<select name="monthtxt" class="Controls">
<%for(int i=1;i<=12;i++){
%><option><%=i%></option><%
}
%>
</select>
<select name="yeartxt" class="Controls">
<%for(int i=2000;i<=2030;i++){
%><option><%=i%></option><%
}
%>
</select>
</td>
</TR>
<TR class="Controls">
<TD><strong>Issues</strong></TD>
<TD><textarea name="issuestxt" rows="5"
cols="16" class="Controls"></textarea></TD>
</TR>
<TR></TR>
<TR></TR>
</TBODY>
</TABLE><BR>
<TABLE align="CENTER" >
<TBODY>
<TR>
<TD><input type="submit" value ="Send"
class="ThemeButtons" style="width:70px">
<input type =reset class="ThemeButtons"
style="width:70px"></TD>
</TR>
</TBODY>
</TABLE>
</FORM> </BODY></HTMl>

ISSUES UPDATE:

%@ page language="java" contentType="text/html;charset=UTF-8"%>
<jsp:useBean id="data" class="Data_con.J dbc_Con" scope="application"/>
<%@page import="EJ BNew.IssuesHome"%>
<%@ taglib uri="netui-tags-databinding.tld" prefix="netui-data"%>
<%@ taglib uri="netui-tags-html.tld" prefix="netui"%>
<%@ taglib uri="netui-tags-template.tld" prefix="netui-template"%>
<netui:html>
<head>
<title>
Web Application Page
</title>
</head>
<body>
<form>
<%
String code ="I101";
int t1 =100;
try{
java.sql.Statement st1 =data.Connect_J dbc();
ResultSet rs1 =st1.executeQuery("select i_no from issues");

while(rs1.next()){
int t =Integer.parseInt(rs1.getString("i_no").substring(1,4));

if(t>=t1){
t1 =t;
}

}


code ="I"+(t1+1);
InitialContext ctx =new InitialContext();
Object obj =ctx.lookup("issues_jndi");
IssuesRemoteHome rhome =
(IssuesRemoteHome)PortableRemoteObject.narrow(obj,IssuesRemoteHome
.class);
IssuesRemote re =rhome.create(code);
int y =Integer.parseInt(request.getParameter("yeartxt"));
re.setP_name(request.getParameter("inametxt"));
re.setPurchase_date(dt);
re.setIssues(request.getParameter("issuestxt"));
}catch(Exception e){
out.println(e);
}
%>
<h1>Issues send</h1>
</form>
</body>
</netui:html>


PURCHASE ORDER UPDATE:

<!--Generated by WebLogic Workshop-->
<jsp:useBean id="data" class="Data_con.J dbc_Con" scope="application"/>
<%@ page language="java" contentType="text/html;charset=UTF-8"
errorPage="Errors.jsp"%>
<%@page import="EJ BNew.Purchase_OrderRemote"%>
<%@page import="EJ BNew.Purchase_OrderRemoteHome"%>
<%@page import="java.sql.ResultSet"%>
<%@ taglib uri="netui-tags-template.tld" prefix="netui-template"%>
<netui:html>
<head>
<title>
Web Application Page
</title>
</head>
<link rel="stylesheet" type="text/css" href="/DCRWeb/resources/css/Styles.css">
<body>
<form>
String code ="PO101";


java.util.Date d =new java.util.Date();
java.util.Date dt =new java.util.Date();
int y =d.getYear();
int m =d.getMonth();
int dd =d.getDate();
dt =new Date(y,m,dd);
try{
java.sql.Statement st1 =data.Connect_J dbc();
ResultSet rs1 =st1.executeQuery("select p_no from
purchase_order");
int nInit =100;
int t=0;
int nPNo=0;
while(rs1.next()){
nPNo=Integer.parseInt(rs1.getString("p_no").substring(2,5));
if(nPNo >=nInit){
nInit =nPNo +1;
}

}
code ="PO"+(nInit);
rs1.close();
st1.close();
data.con_close();
InitialContext ctx =new InitialContext();


Object obj =ctx.lookup("porder_jndi");
Purchase_OrderRemoteHome rhome =
(Purchase_OrderRemoteHome)PortableRemoteObject.narrow(obj,Purchase_OrderRemot
eHome.class);
Purchase_OrderRemote robj =rhome.create(code);

robj.setPorder_date(dt);
robj.setQuotation("NotSend");
ctx.close();
data.con_close();
}catch(Exception e){
out.print(e);
}
<table align="center" border="0" width="75%">
<tr>
<td class="PageTitle" align="center">Purchase Order No


<%=code%>updated
</td>
</tr>
</table>
</form>
</body>
</netui:html>





QUOTATIONS :

<jsp:useBean id="data" class="Data_con.J dbc_Con" scope="application"/>
<%@ taglib uri="netui-tags-databinding.tld" prefix="netui-data"%>
<%@ taglib uri="netui-tags-html.tld" prefix="netui"%>
<%@ taglib uri="netui-tags-template.tld" prefix="netui-template"%>
<html>
<head>
<link rel="stylesheet" type="text/css"
href="/DCRWeb/resources/css/Styles.css">
</head>
<body>


<%! String p_no,p_code,p_name,company_name,porder_date;%>
<%! int no_qty;%>
<form method="post" action="Quatation_Update.jsp">
<table align="center"border="1">
<TBODY>
<tr align="center">
<td class="MainTitle">Quatation</td>
</tr>
</TBODY>
</table>
<%
try{
Statement st =data.Connect_J dbc();
ResultSet rs =st.executeQuery("select
p_no,porder_date,company_name,p_code,p_name,no_qty from
purchase_order where p_no='"+request.getParameter("id")+"'");
while(rs.next())
{
p_no=rs.getString("p_no");
porder_date=(String)rs.getString("porder_date");
company_name=rs.getString("company_name");
p_code=rs.getString("p_code");
p_name=rs.getString("p_name");
no_qty=rs.getInt("no_qty");
}
}
catch(Exception e)
{
out.println(e);
}
%>
<table align="center" border="1" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td class="FieldTopLabels"><strong>Purchase Order
No</strong></td>
<td><strong><input type="text" name="pordernotxt"
value="<%=p_no%>" class="Controls"></strong></td>
<td class="FieldTopLabels"><strong>Purchase Order
Date</strong></td>
<td><input type="text" name="podatetxt"
value="<%=porder_date%>" class="Controls"></td>
</tr>
<tr>
<td class="FieldTopLabels"><strong>Vendor</strong></td>
<td><input type="text" name="vendortxt"
value="<%=session.getAttribute("uname")%>"
class="Controls">
<td class="FieldTopLabels"><strong>Company

Name</strong></td>
<td><input type="text" name="cnametxt"
value="<%=company_name%>" class="Controls"></td>
</tr>
<tr>
<td class="FieldTopLabels"><strong>Product
Code</strong></td>
<td><input type="text" name="pcodetxt"
value="<%=p_code%>" class="Controls"></td>
<TD class="FieldTopLabels"><strong>Product
Name</strong></TD>
<TD>
<input type="text" name="pnametxt"
value="<%=p_name%>" class="Controls">
</TD>
</tr>
<tr>
<td align="right"
class="FieldTopLabels"><strong>Quantity</strong></td>
<td><input type="text" name="qtytxt"
value="<%=no_qty%>" class="Controls"></td>
</tr>
<tr>
<td align="right"



class="FieldTopLabels"><strong>Price</strong></td>
<td><input type="text" name=pricetxt class="Controls"
onChange="amounttxt.value=qtytxt.value * pricetxt.value">
</tr>
<tr>
<td align="right"><strong>Amount</strong></td>
<td><input type="text" name=amounttxt class="Controls"
onFocus="taxtxt.value=0.05 * amounttxt.value" ></td>
</tr>
<tr>
<td align="right"
class="FieldTopLabels"><strong>Tax</strong></td>
<td><input type="text" name="taxtxt"
class="Controls"></td>
</tr>
<tr>
<td align="right" class="FieldTopLabels"><strong>Shipping
Charges</strong></td>
<td><input type="text" name="schargetxt"
class="Controls"></td>
</tr>
<tr>
<td align="right"
class="FieldTopLabels"><strong>Discount</strong></td>
<td><input type="text" name="discounttxt"


class="Controls"></td>
</tr>
<tr>
<td><input type="submit" value="Send" style="width:70px"
class="ThemeButtons"></td>
<td align="right"
class="FieldTopLabels"><strong>Total</strong></td>
<td><input type="text" name="totaltxt"
onFocus="totaltxt.value=(parseInt(amounttxt.value) +
parseFloat(taxtxt.value) +parseInt(schargetxt.value))+((parseInt(amounttxt.value) +
parseFloat(taxtxt.value) +
parseInt(schargetxt.value))*(parseInt(discounttxt.value)/100))"></td>
</tr>
</tbody>
</table>
</form>
</body>
</html>
CHAPTER - 7
BENEFITS AND USES OF SCM

Increased user confidence by making the process more transparent and
flexible.
Enhanced version management capability, reducing hours of manual work.
The customer was able to get the supply chain elements like cost and
performance visibility though a centralized system.
Improvement in service level.
Improvement in forecast accuracy.
A roadmap for future enhancements.
Enhanced version management capability, reducing hours of manual work
Flexible process to manage historical data cleansing and accounting for future
promotions
The clients experiences significant improvements in customer service,
increased sales and higher profits.
It integrates seamlessly with our QuickBooks enterprise accounting
application.
It supports multiple warehouse locations, item transfer, and easy drop
shipment processing.
CHAPTER - 8
CONCLUSION
Supply chain management is here. It is not about shipping orders; it is not
about making product then pushing it out the door. Supply chain management is
about developing a process to respond to the different requirements of each
customer. Customers are driving suppliers' practices. Being successful requires
logistics effectiveness. Customers, competitors and vendors are global. This is an
exciting challenge and opportunity for companies who see the potential and make
it happen.
Supply chain management must addresses the following problems

Distribution Network Configuration: Number and location of suppliers,
production facilities, distribution centers, warehouses and customers

Distribution Strategy: Centralized versus decentralized, direct shipment,
cross docking, pull or push strategies, third party logistics.

Information: Integrate systems and processes through the supply chain to
share valuable information, including demand signals, forecasts, inventory
and transportation.

Inventory Management: Quantity and location of inventory including raw
materials, work-in-process and finished goods


CHAPTER - 9
REFERENCES

[1] The Effective Incident Response Team, by J ulie Lucas, Brian Moeller
[2] Your 802.11 Wireless Network Has No Clothes. Arbaugh, W.A., Shankar, N., and
Wan, Y.C., March 30, 2001
[3] Designing Enterprise Applications with the J 2EE Platform, Second Edition by
Inderjeet Singh, Beth Stearns, Mark J ohnson, the Enterprise Team
[4] Norton, P. and Stockman, M. Peter Nortons Network Security Fundamentals. 2000.
[5] Stallings, William. (2000) Network Security Essentials: Applications and Standards,
Upper Saddle River, N.J ., Prentice Hall, c2000.
[6] Information assurance in computer networks: methods, models, and architectures for
network security: international workshop MMM-ACNS 2001, St. Petersburg, Russia,
May 21-23, 2001 / Vladimir I. Gorodetski, Victor A. Skormin, Leonard J . Popyack (eds.)
[7] Computer Security: Art and Science by Matt Bishop
[8] Web Security, Privacy & Commerce, 2nd Edition by Simson Garfinkel
[9] http://www.itp.net
[10] Best Practices for Preventing DoS
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/security/bestprac/do
satack.asp
[11] Applied SOAP: Implementing .NET XML Web Services by Kenn Scribner,
Mark C. Stiver
[12] Implementing a Secure Virtual Private Network http://www.rsasecurity.com