GATE PASS SYSTEM

1. FEASIBILITY STUDY
A feasibility study is an evaluation of a proposal designed to determine the
difficulty in carrying out a designated task. Generally, a feasibility study precedes technical
development and project implementation. In other words, a feasibility study is an evaluation or
analysis of the potential impact of a proposed project.

Before starting the process various parameters must be checked like:

 Estimated finance is there or not?

 The man power to operate the system is there or not?
 The man power is trained or not?

All the above conditions must be satisfied to start the project. This is why in depth analysis of
feasibility is carried out.

There are different ways feasibility can be tested

1) Technical Feasibility
2) Economical Feasibility
3) Operational Feasibility
4) Schedule feasibility
5) Resource feasibility

1.1 Feasibility techniques:

Technology and system feasibility

The assessment is based on an outline design of system requirements in terms of Input,

Processes, Output, Fields, Programs, and Procedures. This can be quantified in terms of volumes
of data, trends, frequency of updating, etc. in order to estimate whether the new system will
perform adequately or not. Technological feasibility is carried out to determine whether the
company has the capability, in terms of software, hardware, personnel and expertise, to handle
the completion of the project.

SPB LINCH CE - 1-
 GATE PASS SYSTEM

 This project is technologically feasible because all the software’s, hardware’s and
personnel were present at the point of time it required.

1.2 Economic feasibility

Economic analysis is the most frequently used method for evaluating the effectiveness of a new
system. More commonly known as cost/benefit analysis, the procedure is to determine the
benefits and savings that are expected from a candidate system and compare them with costs.
If benefits outweigh costs, then the decision is made to design and implement the system. An
entrepreneur must accurately weigh the cost versus benefits before taking an action.

Cost Based Study: It is important to identify cost and benefit factors, which can be categorized as
follows: 1. Development costs; and 2. Operating costs. This is an analysis of the costs to be
incurred in the system and the benefits derivable out of the system.

Time Based Study: This is an analysis of the time required to achieve a return on investments.
The benefits derived from the system. The future value of a project is also a factor.

 This project is made after completion of all cost and time analysis. Its benefits outweigh
cost and it is completed within the time period which was estimated before and that is why
it is economically feasible.

1.3 Schedule feasibility

A project will fail if it takes too long to be completed before it is useful. Typically this means
estimating how long the system will take to develop, and if it can be completed in a given time
period using some methods like payback period. Schedule feasibility is a measure of how
reasonable the project timetable is. Given our technical expertise, are the project deadlines
reasonable? Some projects are initiated with specific deadlines. You need to determine whether
the deadlines are mandatory or desirable.

 This project is scheduled very well and it contains four modules and for that it requires
round about 4 months for completion. And according to the schedule this project is
completed and that is why it is schedule feasible.

SPB LINCH CE - 2-
 GATE PASS SYSTEM

1.4 Resource feasibility

This involves questions such as how much time is available to build the new system, when it can
be built, whether it interferes with normal business operations, type and amount of resources
required, dependencies, etc. Contingency and mitigation plans should also be stated here.

 All the software, hardware required for this project is available at the point of development.
Four months are available to build this project and it is completed without any disturbance.
So we can say that this project is resource feasible.

1.5 Cultural feasibility

In this stage, the project's alternatives are evaluated for their impact on the local and general
culture. For example, environmental factors need to be considered and these factors are to be
well known. Further an enterprise's own culture can clash with the results of the project.

1.6 Implementation Feasibility

Under the study of implementation feasibility, we've got to draw the

figure to the certain issues, like:

 Is it possible to install the software within the given environment?

 Whether the system which is being developed will run in the
environment available with us?
 Will the system be approved by the management of the
Organization?
 Will the system cause any harm to the operations of the
Organization?

Operationally the system can be installed and it can work according to

its functionalities. There would be very little barriers in implementation, if
application will be prepared according to the hardware barriers. The
management has already approved the software to be developed and it would in
fact help in user's operation or day-to-day activities.

SPB LINCH CE - 3-
 GATE PASS SYSTEM

2. PROJECT PLAN

2.1 Objectives

Project plan includes description of project tasks, activities and functions, dependencies,
resource requirements and a detailed schedule. This activity results in the software project
management plan for the Annual Maintenance Contract.

Requirement
Analysis

Design

Coding

Testing

 Requirement Analysis:
The requirement analysis activity takes the problem statement and reviews it in
terms of consistency, completeness and feasibility. During this activity, a set of models of the
proposed system is determined by interacting with the clients resulting in the requirement

SPB LINCH CE - 4-
 GATE PASS SYSTEM

model. The main parts of the requirements model are is: The use case model describing the
complete functionality of the system.

 System Design:
The purpose of the system design activities is to devices a system
architecture that maps the analysis model to the chosen target environment. The major part of
the system design phase is design of subsystems, that is, the decomposition of the system with
respect to the chosen target platform. The system design activity also refines the Use cases
from the analysis model and describes in terms of interaction diagrams how the objects
interact in each specific Use-case.

 Implementation:
The focus of this activity is on coding the individual objects described in
the object design document.

 Testing Module:
At the end of each and every phase is on coding the individual objects
described in the object design document.

SPB LINCH CE - 5-
 GATE PASS SYSTEM

2.2 MILESTONES & DELIVERABLES

Managers need information to do their job. Because software is intangible,

this information can only be provided as reports and documents that describe the state of the
software being developed. Without this information, it is impossible to assess how well the work
is progressing, and cost estimates and schedules cannot be updated.
When planning a project, you should establish a series of MILESTONES, where a
milestone is a recognizable end-point of a software process activity. At each milestone, there
should be a formal output, such as a report, that can be presented to management. Milestone
reports need not be large documents. They may simply be a short report of what has been
completed. Milestones should represent the end of a distinct, logical stage in the project.
Indefinite milestones such as ‘coding 80% complete ‘that can‘t be checked the useless for project
management. You can’t check whether this state has been achieved because the amount of code
that still has to be developed is uncertain.
A deliverable is a project result that is delivered to the customer. It is usually
delivered at the end of some major project phase such as specification or design. Deliverables are
usually milestones, but milestones need not be deliverable. Milestone may be internal project
result that are used by the project manager to check project progress but which are not delivered
to the customer.

Requirement Prototype Requirement

Feasibility Study Design Study
Analysis Development Specification

Requirement s Architectural System

Feasibility Report Evaluation Report
Definition Design Requirements

To establish milestones, the software process must be broken down into basic
activities with associated output. For example, Fig. shows possible activities involved in
requirements specification when prototyping is used to help validate requirements. The
milestones in this case are the completion of the output for each activity. The project
deliverables, which are delivered to the customer, are the requirements definition and the
requirements specification.

SPB LINCH CE - 6-
 GATE PASS SYSTEM

MILESTONES PHASE-I
In the milestones table, it is mainly divided into two major phases. In first phases, it will be
sub-divided into five tasks and the completion date for each task is stated as the table below.

No. Tasks Milestone/Date complete

1 Project Identification and Selection 15th Jan, 2011
2 Project Initiation and Planning 1th Feb, 2011
3 Literature Review 19th Feb, 2011
4 Analysis and Design 26th March, 2011
5 Prototype and Report 30th March, 2011

MILESTONES PHASE-II

The second phase of milestones is as shown as below. This second phase is sub-divided into
four tasks and the completion date for each task is as shown.

No. Tasks Milestone/Date complete

1. Review on Preview Project Work 30th March, 2011
2. Update Plan and Requirements 9th April, 2011
System Design (Database & Software
3. 12th March, 2011
Architecture)
4. Final Report 22th April, 2011

2.3 Time Line Chart

SPB LINCH CE - 7-
 GATE PASS SYSTEM

Gate pass System

1 1 1
Week (Tasks) 1 2 3 4 5 6 7 8 9 11 13 15 16
0 2 4
Activity January February March April
Domain
                               
Understanding
Analysis
                               
Requirements
Learning Process                                
Design                                
Coding                                
Documentation                                
Final Documentation                              

2.4 Risk management

 Evaluates which risks identified in the risk assessment process require management and
selects and implements the plans or actions that are required to ensure that those risks are
controlled.
 Identifying risks and drawing up plans to minimize their effect on the project is called risk
management. An important task of a project manager is to anticipate risks, which might affect
the project schedule or the quality of the software being developed, and to take action to avoid
these risks.
 Simplistically, you can think of a risk as a probability that some adverse circumstance will
actually occur. Risks may threaten the project, the software that is being developed or the
organization.

These categories of risk can be defined as follows:

SPB LINCH CE - 8-
 GATE PASS SYSTEM

1. Project risks are risks that affect the project schedule or resources.
2. Product risks are risks that affect the quality or performance of the software being
developed.

The process of risk management is illustrated in the figure below.

Fig: The Risk Management Process

 Risk identification: Possible project, product and business risks are identified.
 Risk analysis: The likelihood and consequences of these risks are assessed.
 Risk planning: Plans to address the risk either by avoiding it or minimizing its effects on the
project are drawn up.
 Risk monitoring: The risk is constantly assessed and plans for risk mitigation are revised as
more information about the risk becomes available.

 Risk communication

Involves an interactive dialogue between stakeholders and risk assessors and risk managers
which actively informs the other processes.

Risk analysis = risk assessment + risk management + risk communication

SPB LINCH CE - 9-
 GATE PASS SYSTEM

 Risk Identification

Risk identification is the first stage of risk management. It is concerned with discovering
possible risks to the project. In principle, these should not be assessed or prioritized at this stage
although, in practice, risks are not usually considered. Risk identification may be carried out as a
team process using a brainstorming approach or may simply be based on a manager’s
experience. These types of risks include:
 Technology risks: Risks that derive from the software or hardware technologies that are
begun used as part of the system being developed.
 People risks: Risks those are associated with the people in the development team.
 Organizational risks: Risks that derive from the organizational environment where the
software is being developed.
 Tools risk: Risks that derive from the CASE tools and other support software used to
develop the system.
 Requirements risk: Risks that derive from changes to the customer requirements and the
process of managing the requirements change.
 Estimation risk: Risks that derive from the management estimates of the system
characteristics and the resources required building the system.

 Risk Planning

The risk planning process considers each of the key risks that have been identified and identifies
strategies to manage the risk. Again, there is no simple process that can be followed to establish
risk management plans. It relies on the judgment and experience of the project manager.

These strategies fall into three categories:

a) Avoidance strategies
Following these strategies means that the probability that the risk will arise will be reduced.
An example of a risk avoidance strategy is the strategy for dealing with defective
components that follows the strategy “Replace potentially defective components with
bought-in components of known reliability”.
b) Minimization strategies
SPB LINCH CE - 10-
 GATE PASS SYSTEM

Following these strategies means that the impact of the risk will be reduced. An example of a
risk minimization strategy is the strategy for staff illness which follows the strategy
“Reorganize team so that there is more overlap of work and people therefore understand each
other’s jobs.

 Risk Monitoring

 Risk monitoring involves regularly assessing each of the identified risks to decide whether or
not that risk is becoming more or less probable and whether the effects of the risk have
changed.

 Of course, this cannot usually be observed directly, so you have to look at other factors which
give you clues about the risk probability and its effects. These factors are obviously dependent
on the types of risk.

 Risk monitoring should be a continuous process and, at every management progress review,
each of the key risks should be considered separately and discussed by the meeting.

2.5 ESTIMATION

Software is the most expensive element of virtually all computer-based systems. For
complex, custom system, a large cost estimation error can make the difference between profits
and lost. Cost overrun can be disastrous for the developer.

Software cost and effort estimation will never be an exact science. Too many variables
human, technical, environment, political can affect the ultimate cost of software and effort
applied to develop it. However, software project estimation can be transformed from a black art
to a series of systematic steps that provide estimate with acceptable risk. To achieve reliable cost
and effort estimates, a number of options arise:

Software Sizing

• Function point sizing

• Standard component sizing

SPB LINCH CE - 11-

 GATE PASS SYSTEM

Problem-Based Estimation

LOC and FP data are used in two ways during software project Estimation:-

• As an estimation variable to size each element of the software and

• As baseline matrices collected from past projects and used in conjunction with
estimation variables to develop cost and effort projections.

Schedules

Obtain an early view of staffing requirements and constraints, and demonstrate the
impact of changing deadlines, understaffing, and staff loading.

Quality

Quantify the impact on defect rates of building to deadlines or reducing staff.

Risk

Fine tune risk levels for all the major types of risk: size, requirements, technology,
maintenance, systems integration, and defects.

SIZE:
 Total number of modules: 25
 Developed with 1 Person in 90 days.

TIME:
 Total time was 90 days for 1 Person so.

EFFORT:

 No. of person : 1
 8 hours of work per day with 64 lines.

SPB LINCH CE - 12-

 GATE PASS SYSTEM

SPB LINCH CE - 13-

 GATE PASS SYSTEM

3. REQUIREMENT ANALYSIS

3.1 STUDY OF CURRENT SYSTEM

The “GATE PASS SYSTEM” is a application intended for users of any kind of
company. The motivation of this project comes from our desire to learn the increasingly growing
field of secure and safe sap gate pass system facilities.

3.2 PROBLEMS AND WEAKNESS OF CURRENT SYSTEM

The current system is quite tedious and time consuming thereby involving a great risk
of errors. At the time of getting information if there is a long queue of the users may have to wait
for a long time and this chaos would create additional burden on the receptionist.

3.3 REQUIREMENTS OF NEW SYSTEM

3.3.1 Functional Requirements:-

As the current company scenario, the gate pass system facilities plays important and
necessary roll for the growth of anytime and anywhere capabilities. In this fastest growing world,
Humans have no time for paper work. As scenario, if we want to make request for gate pass for
ant kind of material, we have to go there and have to fill up the details for the request. It takes
more time. So with gate pass Application, user can fill up the request form in his system only.
Admin can accept the different request in his system itself. .

SPB LINCH CE - 14-

 GATE PASS SYSTEM

3.3.2 Non-Functional Requirements:-

The Non-functional requirement specifies the following requirements which are as
follows:
a) Extensibility:-
Basic goal of any system is to satisfy the user’s requirements any time user can request
for an extra updating or refinements in the software and so our system provides extensibility.

b) Flexibility:-
Our system can execute on any platform or environment and this is just to help the user to
work easily and efficiently.

c) Security:-
Our system helps the clients to provide secure and safe generation of request for material.
And also safe interaction with important database.
d) Maintainability:-
It is necessary to maintain our software because it stores the information about the items
stocked. Information can be like the cost of item, purchase date; issue date etc and this
information can be used or required in future also.
1 System should be user friendly.
2 System should be Reliable, Accurate & Specific.
3 System should be extensible & reusable.

3.3.3 Operational Requirements

This Application has been developed with two parts. 1) Bank Agent Application. 2)
Customer or client Application. In first, As per today’s scenario, A private bank’s provide agent
facilities to their client. Suppose if we do daily transaction with our accounts, then we do not
need to go to the bank. A bank agent will come with us. Agent will take details from us for
transaction and agent will do transaction from their cell phone with details of our account. And

SPB LINCH CE - 15-

 GATE PASS SYSTEM

in second application, A customer or client is able to see report of their accounts. Means full
details of account and also particular transaction within particular date.

3.4 REQUIREMENT ENGINEERING PROCESS

The description of the services and constraints are the requirements for the system and
the process of finding out, analyzing, documenting and checking these services and
constraints is called requirement engineering.
As shown in the diagram on the next page, the requirement engineering flows.

Feasibility
Study

Requirement
Analysis
Feasibility
Report

Requirement
Definition

System
Models Requirement
Specification

Specification of
Requirements

Requirement Specification of
documents Requirements

SPB LINCH CE - 16-

 GATE PASS SYSTEM

 Domain Understanding

To develop a project for real time user’s, to help them to make a gate pass request
easily and in efficient manner. User can also see their request’s report’s also.

 USER REQUIREMENT: -

User are login on the system and make a request for a gate pass for the material of his
department .User can also see his reports.

 SYSTEM REQUIREMENT: -
The developed application must be work on the SAP GUI. The application is user
friendly and also contain the all past reports of all request.

 PRELIMINARY REQUIREMENT ANALYSIS

This phase is actually a base for the whole development effort. Here we meet the
prospective users of the system and analyze the features they demand. A
comprehensive understanding of the users’ needs and writing down features of the
proposed software product are the keys to success in this phase. Different techniques
can be employed for collecting user requirement, which include
 User Meeting & Interviews
 Study of current process
 Questionnaires
By asking the questions and conducting multiple meetings, we refined our requirements.
Some of the questions were like
1. What would be the way of authenticating the users?
2. Who would be administrating the application?

SPB LINCH CE - 17-

 GATE PASS SYSTEM

We gave presentation of proposed system to Project Guide with the purpose of getting
feedback and suggestions that helped us in refining the requirements for the
administration Module.
Software requirement analysis may be divided into five areas of efforts:
i. Problem Recognition
ii. Evaluation and Synthesis
iii. Modeling
iv. Specification
v. Review

3.5 ROLES AND RESPONSIBILITY

.
Task Responsibility

Requirement Analysis Study all the aspects of proposed system

System Design Designing of the Web site

Implementation Coding for all the four modules

Testing Unit Testing, Integral Testing, Loop Testing etc

Requirement Analysis

 As we mentioned, there is only one person in our development team. For proper
understanding the requirements of the end user (Which is the most important part of the
project) I, Jasdeep Singh Bhatia have derived the requirement statement of the end user
by understanding their nature and then asking about what they need by this utility to be
done.

SPB LINCH CE - 18-

 GATE PASS SYSTEM

System Design

 In System design, all the UML diagrams (Class Diagram, Activity Diagram and DFD)
are created by me.

Implementation

 My all modules are implemented in abap and implements on client side and server side.

Testing

 Testing is the process through which the system is considered as the effectiveness of the
output that it will generate in different combination of inputs by the end user.

 ROLES & RESPONSIBILITIES

ROLE NAME RESPONSIBILITY

Project Guide Mr. Hitesh Patel

Defining scope
Providing required resources
Project tracking and monitoring.
Analysis and Effort Estimation.
Coordination between teams.
Jasdeep Singh Designing
Bhatia
Coding
Reporting to Project Guide
Documentation

SPB LINCH CE - 19-

 GATE PASS SYSTEM

3.6 USER CHARACTERISTICS

Analyzing user characteristics is an important aspect of any project. It allows the team to clearly
define and focus on who the end users are for the project. Also, it allows the team to check the
progress of the project to ensure the team is still writing the product for the correct users.

This Application is mainly used by three users

 Store Admin
 Normal member
 Gate man

 Store Admin
Store Admin after login in can easily see all the request for gate pass. Admin
Can make gatepass easily, also he can see the all kind of reports. He can see all past
reports. Also he can edit in request form after material has been received.

 Normal member

. Normal member after login in can make gate pass request. He can fill the
request form for gatepass for the particular material. Also he can see all reports of his
department.

 Gate man

Gate man can easily do edit in the request form in status field. He can
update the status of the material at every state.

SPB LINCH CE - 20-

 GATE PASS SYSTEM

3.7 Constraints

Identify the project constraints and risks in order to help a team to define the parameters of the
application deployment project and develop the project plan.

Defining Project Constraints

To prioritize and define the scope of the application deployment project, gather information
about the constraints of your project. Constraints often include:

Resources. Identify the equipment, software, staff, and space that are available for the project.

Time. Identify the date by which the application deployment project must be completed, and
how the application testing process fits into the larger deployment project.

Organizational issues. If the project will not involve the entire organization, identify which
groups in your organization will be affected by it. Additionally, determine if a particular group in
the organization needs the new operating system sooner than others. If so, you might decide to
perform a staged rollout.

Access to developers. Identify applications that were developed in-house or especially for your
organization. Access to the developers of these applications is critical during the testing and
issue resolution phases of the project. Such access also can be an invaluable aid with retail
applications.

Technical Constraints

Technical constraints stem from FS relationships. Most often within an IT project, tasks will be
logically sequential to get from the start to the end. These constraints are the simplest and most
likely the ones you’ll find in a project. The technical constraints you may encounter when
building your network diagram fall into two major categories:

 Discretionary constraints These constraints allow the project manager to change the
relationship between activities based on educated guesses. Imagine two tasks that are
scheduled to run concurrently
 Resource constraints A project manager may elect to schedule two tasks as FS rather
than SS based on a limitation of a particular resource

SPB LINCH CE - 21-

 GATE PASS SYSTEM

Date Constraints

Often in project management, projects have preset deadlines that require project managers to
work backward from the assigned completion date. The problem is that the person establishing
the deadline may not realize the work required to complete a project by that given date.
Unfortunately, this is often the way project management works: you’re assigned a deadline and
then you have to figure out how to complete the tasks by that date

Management Constraints

Management constraints are dependency relationships imposed because of a decision by

management—this includes the project manager. For example, a project manager is overseeing
the development of a web-based learning management system. The web site will allow students
to register for classes, check grades, and pay for their tuition, all online. T

Organizational Constraints

Within your organization there may be multiple projects that are loosely related. The completion
of another project may be a key milestone for your own project to continue. Should another
project within your organization be lagging, it can impact your own project’s success.

3.8 REQUIREMENT VALIDATION

 The basic and initial criteria in my project are of username and password for any user.
The user can not access full application or say the user can not access any of the
functionality without searching seeing of the application without logging in. Until and
unless the user gives right username and right password, the user can not access any of
the functionality of the system.

 Each of the request being done in the company is having many details and all the details
are required to be entered in the database.

 The Software will be user friendly. It will check for various validation criterions and
processes will work perfectly or not as expected under normal circumstances. If the

SPB LINCH CE - 22-

 GATE PASS SYSTEM

validations are not met then the appropriate messages will be given. The user has to select
from various processes the work he requires to do. Validation Criteria is most important
property because of using this no one can enters the invalid data.

3.9 USECASE DIAGRAM

Use case diagram describe functionality of the system and users of the system. This diagram
contain following element.
Actor: It represents users of the system; include human user and other system.
User Cases: It represents functionality or service provided by a system to user.

SPB LINCH CE - 23-

 GATE PASS SYSTEM

Request Form

Make a Gate Pass

Repairs and Replace

Normal Member

Admin
Get Reports

Request Status

Gate Man

3.10 SOFTWARE AND HARDWARE REQUIREMENT

 Hardware Requirement:

SPB LINCH CE - 24-

 GATE PASS SYSTEM

Hardware Minimum Requirement

Processor Pentium 4
Ram 1 GB
Hard disk 160 GB
CPU Speed 2 GHZ
Server IBM Server

 Software Requirement:

Software Requirement
Operating system Windows XP
Front End SAP GUI 7.2
RDBMS ORACLE 9i

SPB LINCH CE - 25-

 GATE PASS SYSTEM

4. SYSTEM DESIGN

4.1 DESIGN STRATEGY

SAP R/3

SAP R/3 is the former name of the main enterprise resource planning software produced by SAP
AG. It is an enterprise-wide information system designed to coordinate all the resources,
information, and activities needed to complete business processes such as order fulfillment or
billing.

SAP R/3 Client /Server Architecture

In SAP terminology, a service means a service provided by a software component
(software-oriented view) This component can consist of a process(compare work process) or a
group of processes (compare application server) and is then called a server for that service
.Software components that use this service were called clients. at that same time ,clients can also
be servers for specifics devices.A server often also means a computer (host) on which software
components that provide specific services are running (hardware-oriented view).
Every SAP R/3 system consists of one database server and one or more application server. In a
typical SAP R/3 scenario, each user connects to an application server by starting the SAPGUI
program on his or her local machine.
The resulting 3-tier architecture is shown in figure 2.it requires a pc as a client. The
presentation layer executes the SAPGUI program, providing users with GUI to access the system
without any built –in business logic. The application layer is where application software
execution actually takes place.

SPB LINCH CE - 26-

 GATE PASS SYSTEM

Each system can consist of several application servers communicating with the others,
running on UNIX, AS/400, or Windows NT platforms. One centralized database layer .The three
layers can be located on one or several servers .though users can install all layers on one system
usually this is used for demonstration purpose .typically these systems are configured without
terminal server .users run SAPGUI on their workstation using it to connect to the application
server .the application server and the database may be distributed on different machines but there
is typically one application servers are added on other machines to increase the performance of
the R/3 system.

Architecture of SAPGUI:
SAPGUI is the user interface to SAP R/3 .it performs the following functions:
 Finds and connects to an application server
 Provides several windows for the user
 Displays data sent from the application server
 Sends user data to the application server
 Communicates with application running on the local computer

These tasks are implemented by the architecture shown in figure shown below

SPB LINCH CE - 27-

 GATE PASS SYSTEM

SAPGUI implemented in three steps .the user starts a program called SAPLogon.exe.it searches
for an application server on the desired SAP R/3 system and starts Sapgui.exe.Sapgui.exe
maintains the TCP/IP connection to the R/3 application server.front.exe is then launched .it
opens a window called “main mode” where applications operate. Several windows can be
opened at one time.Sapgui.exe multiplexes the data from each window, sending it to the
application server using the same TCP/IP connection. SAPGUI is not only used for user input
and displaying data, it is also the interface for the R/3 application server to the user’s
workstation. It communications with other process running on the workstations such as
Microsoft Office applications .it is also possible to integrate ActiveX Controls into SAPGUI a
modern look and feel .this feature is only available in modern versions of SAPGUI ,which are
only available for Windows 98/95/NT and partially ,for java.

System Requirements for SAPGUI:

 64 MB of RAM minimum(128 MB of RAM recommended)
 45 MB of available disk space for SAPGUI installer
 100 MB of available disk space for SAPGUI software
 Netscape 4.5 or higher (Netscape 4.78 is recommended)
 MIT Certificates

SPB LINCH CE - 28-

 GATE PASS SYSTEM

4.2 DataFlow Diagram

A data flow diagram (DFD) is a graphical representation of the "flow" of data

through an information system . A data flow diagram can also be used for the
visualization of data processing (structured design). It is common practice for
a designer to draw a context-level DFD first which shows the interaction
between the system and outside entities. This context-level DFD is then
"exploded" to show more detail of the system being modeled .

A data flow diagram illustrates the processes, data stores, and

external entities in a business or other system and the connecting data flows.
The four components of a data flow diagram (DFD) are :

Shapes Description
This symbol is used for dataflow in the

diagram.

This symbol is used for process in the

diagram.
This symbol is used for source and destination

processes.
This symbol is used for data storage in the

diagram.

CONTEXT LEVEL DFD

SPB LINCH CE - 29-

 GATE PASS SYSTEM

LOGIN DETAIL, MAKE GATE

PASS DETAILS,REPAIR AND
REPLACE DETAILS GATE REPORT
GATE PASS MODULE
NORMAL MEMBER
ADMIN
GATE REPORT
LOGIN DETAILS,
REQUEST DETAILS

LOGIN DETAILS , MATERIAL STATUS

MATERIAL STATUS

GATE MAN

SPB LINCH CE - 30-

 GATE PASS SYSTEM

1ST LEVEL DFD

SPB LINCH CE - 31-

 GATE PASS SYSTEM

1.0 Login Details

Login
User_Name, Master
Normal Password
Login Login Details
Member
Process

User_Name,
Password

Sucessful / Unsucessful
Login

User_Name,
Password
Admin

Succesful / Unsucessful
Login

Repair and Replace

Details

GatePass
Details
GatePass_Master

GatePass
Details
Gate Pass Details, Repair Repair and
and Replace Details Replace
Details
2.0
Request_Master
Request
Details
Manage Process
Material Status
Request Details
Normal
Member Material Status

Material Status
Gate
Man

2ND LEVEL DFD

SPB LINCH CE - 32-

 GATE PASS SYSTEM

Gate Pass
Gate Pass 3.1 Details
Details
GatePass_Master
Gate Pass
Process Gate Pass
Gate Pass Details
Details

Repair and
Replace
Details
Request_Master

Repair and
Replace 3.2
Details
Admin Repiar and
Register
Repair and
Process
Replace Details Repair and
Replace
Details

3.3

Request Details Request

Normal Member Request Details
Process

Material Status Details 3.4

Material Status Details

Gate Man Material
Material Status Status
Details Process
Material Status
Details

4.3 Data dictionary

SPB LINCH CE - 33-

 GATE PASS SYSTEM

As a system data model is derived, many named entities, relationships and so forth will be
identified. The names given to the entities should be chosen to give the reader some clues to their
meaning. However, further description of the named entities is usually to make the model
understandable. The description can be informal or formal. Whatever approach is used, it is
always worth collecting al description in a single repository or data dictionary.
A data dictionary is simplistically, a list of names used by the system, arranged
alphabetically. As well as the name, the dictionary should include a description of the
composition. Other information such as the date o creation, the creator and the representation of
the entity may also be included depending on the type of model which is being developed.

Advantages of using data dictionary are:

 It is a mechanism for name management. Many different people who have to invent
names for entities and relationships may develop a large system model. These names
should be used consistently and should not clash with their meaning. The data dictionary
software can check for name uniqueness and tell requirement analysis of name
duplications.

 It serves as a store of organizational information, which cans analysis, design,

implementation and evolution. As the system is developed, information is taken to inform
the development new information is added to it. All information about an entity is one
place.

List of Table:
 Login detail
 Request details
 Company detail
 Department detail
 Gate pass detail
 Commara details

 Table Name: Login detail

SPB LINCH CE - 34-

 GATE PASS SYSTEM

Description: This table contains all the information about the users

 Table Name: Request details

Description: This table provides all the details of the user’s request

.
 Table Name: Company details

Description: This table provides all the details of the Company.

SPB LINCH CE - 35-

 GATE PASS SYSTEM

 Table Name: Department details

Description: This table provides all the details of the Department

SPB LINCH CE - 36-

 GATE PASS SYSTEM

 Table Name: Gate Pass details

Description: This table provides all the details of the Gate Pass.

 Table Name: Commara details

Description: This table provides all the details of the Material number and Company Id.

SPB LINCH CE - 37-

 GATE PASS SYSTEM

4.4 USER INTERFACE DESIGN

Activity Diagram:

Activity diagrams are graphical representations of workflows of stepwise activities and actions
with support for choice, iteration and concurrency. [1] In the Unified Modelling Language, activity
diagrams can be used to describe the business and operational step-by-step workflows of
components in a system. An activity diagram shows the overall flow of control.
Activity diagrams are constructed from a limited repertoire of shapes, connected with arrows. The
most important shape types:

 Rounded rectangles represent activities.

 Diamonds represent decisions.
 Bars represent the start (split) or end (join) of concurrent activities.
 A black circle represents the start (initial state) of the workflow.
 An encircled black circle represents the end (final state).

Arrows run from the start towards the end and represent the order in which activities happen.
 Hence they can be regarded as a form of flowchart. Typical flowchart techniques lack
constructs for expressing concurrency. However, the join and split symbols in activity
diagrams only resolve this for simple cases; the meaning of the model is not clear
when they are arbitrarily combined with decisions or loops

SPB LINCH CE - 38-

 GATE PASS SYSTEM

 Users:

Start

Enter Username and

password

No

Valid?

Yes

Normal Gate Man

Admin
Member

A B C

SPB LINCH CE - 39-

 GATE PASS SYSTEM

 Admin:

SPB LINCH CE - 40-

 GATE PASS SYSTEM

 Normal Member:

Request Reports

Make View

No
Logout

Yes

Stop

SPB LINCH CE - 41-

 GATE PASS SYSTEM

 Gate Man:

Request Status

Edit

No

Logout

Yes

Stop

SPB LINCH CE - 42-

 GATE PASS SYSTEM

E-R DIAGRAM

SPB LINCH CE - 43-

 GATE PASS SYSTEM

5.IMPLEMENTATION PLANNING AND DETAILS

5.1 IMPLEMENTATION ENVIRONMENT

As the “gate pass system” System going to be developed is normal(company)

application, at the time of implementation it should be kept in mind that system it will be used
concurrently. So the development approach would remain for the concurrent use.
The system is completely GUI. This is because today customer feels comfortable while
working with images or pictures. It can be used by any end-user. Thus user should feel
convenient while working with the system. Thus system is user-friendly.

5.2 MODULES SPECIFICATION

There are many modules associated with the system and they are as follows:

1. Request entry

User can fill the request form for gate pass of his material of his department and
also can see his reports .

2. Request Report

User can see all the request made by him for his department and also can check
status of his request.

3. View Request Details

Admin can see all the request for gate pass made by normal member of every
department. Admin can see request of all departments.

SPB LINCH CE - 44-

 GATE PASS SYSTEM

4. View all Report

An Admin can see all the reports according to department,status,date ,user, material
number.

5. Make gatepass
An Admin can easily make gatepass for request companywise

6. Update
An Admin can easily update the request records.

7. Update status
A Gate man can update the status of all requests.

5.3 CODING STANDARDS

The coding standard is the well-defined and standard style of coding. With the help of the
coding standards any person can go into any code and figure out what’s going on and new people
can get up to speed quickly. A coding standard ways of doing several things such as the way
variables are to be named, the code is to be laid out, the comments are to be described, the work
of function are to be carried out.

SPB LINCH CE - 45-

 GATE PASS SYSTEM

6. TESTING

The aim of the testing process is to identify all defects existing in a software product.
Testing a program consists of subjecting the program to as set of test inputs (or test cases) and
observing if the program behaves as expected. If the program fails to behave as expected, then
the conditions under which failure occurs are noted for later debugging and correction. The
following are some commonly used terms associated with testing.

Testing Principle:-

 Testing is a process of executing a program with the intent of finding an error.

 A good test case is one that has a high probability of finding an as yet undiscovered error.

 A successful test is one that uncovers an yet undiscovered error.

Principle #1:- All tests should be traceable to customer requirements.

Principle #2:- Tests should be planned long before testing begins.

Principle #3:- The pareto principle applied to software testing.

Principle #4:- Testing should begin in the small and progress toward testing in large.

Principle #5:- Exhaustive testing is not possible

6.1 TESTING PLAN

The testing process is a process that to a great extent runs in parallel with other processes.
During the development phase of Store project, test cases for separate modules has been made to
check whether system is working properly after developing as stated or generate erroneous
output. As the same thing applied to whole system for testing and once the entire module works
perfectly as desired, at later stage test suite are made to test in integrated environment to check
for proper functioning.

SPB LINCH CE - 46-

 GATE PASS SYSTEM

So the software is tested at various levels by various testing techniques like black box,
white box, Unit testing and Integration testing etc. Initially all the operations are tested separately
while development. This is unit testing and as the developer does it, so it is white box testing.
Once the operations are tested separately the leader of the phase integrates it with the other
classes and he performs Integration cum Black box testing. And he gives remarks to the
developer about any error.

After all at the end to test the software at software validation level we performed test case
based testing. In which inherited test cases from the scenarios of the system developed in the
Analysis phase in Dynamic Model.

In unit testing the testing of programs that make the system is done. Unit testing gives
stress on modules independently one another. Module is tested and necessary modification is
made.

Designed & implementation model Delivered System

System Test

Requirement model
Use Case Subsystem Test
Test

The Testing Process

SPB LINCH CE - 47-

 GATE PASS SYSTEM

 Objectives of Testing

 The main purpose of testing and information system is to find the errors and correct
them. A successful test is one finds an errors.
 To ensure that during the operation the system will perform as per specification.
 To make sure that the system meets user’s requirements during operation.
 To verify that the control incorporated in the system function as intended.
 To see that the when correct inputs are fed to the system, the outputs are correct.
 To make sure that during operations, incorrect inputs, processing and outputs will be
detected.
 Testing is a process of executing a program with the intent of finding an error.
 A good test case is one that has a high probability of finding an undiscovered error.
 A successful test is one that uncovers an undiscovered error.
 To ensure customer satisfaction, enhance business and set a good reputation for the
software developer.

6.2 TESTING SRATEGY

The test strategy is a formal description of how a software product will be tested. A
test strategy is developed for all levels of testing as and when required. The testing team
analysis the requirements, writes the test strategy and reviews the plan with the project team.
The test plan may include test cases, conditions and the test environment, a list of related
tasks, pass/fail criteria and risk assessment.

As we were working in a team it was a bit difficult to check the work done as no
individual was assigned for that particular task or work. Moreover checking the work done
was very important to reduce risk factor. Right from the starting we planned to adopt one
technique called Assessment by rotation. Thus the work done by one member was assessed
by the other for some time and again revolved for other level check reduced the errors.

SPB LINCH CE - 48-

 GATE PASS SYSTEM

6.3 TESTING METHODS

Web based applications need intensive testing, as the applications will always function as
a multi-user system with bandwidth limitations. Some of the testing which should be done are,
Integration testing, Stress testing, Scalability testing, load testing, resolution testing and cross-
browser compatibility testing. Both automated testing and manual testing should be done without
fail. For example it is needed to test fast loading graphics and to calculate their loading time, as
they are very important for any web site.

Testing methods are mainly divided into two parts:

1. Black Box Testing

2. While Box Testing

1) Black Box Testing:

It is the testing without the knowledge of the internal working of the item
being tested. For this testing test groups are often used. Due to the nature of this
testing the test planning can begin as soon as the specifications are written. This
testing has some advantages like it is more effective on larger units of code than
glass box testing, tester needs no knowledge of implementation, including
specific programming languages, tester and programmer are independent of each
other, tests are done from a user’s point of view, will help to expose any
ambiguities or inconsistencies in the specifications, test cases can be designed as
soon as the specifications are complete.

2) White Box Testing:

It is the testing strategy that deals with the internal logic and structure of the
code. White box testing is also called as the glass testing, structural testing, open
testing or the clear box testing. The advantages of the white box testing are that
as the knowledge of internal coding structure is needed, it becomes easy to find

SPB LINCH CE - 49-

 GATE PASS SYSTEM

out which type of input data can help min testing the application effectively. It
helps in optimizing the code helping in removing the extra code which may cause
hidden defects in the system.

The other sub testing techniques are as follows:

 Unit Testing

We have tested our functions of component to check the specification of our components.
We selected input set to test the components like in query process we gave the different kinds of
inputs to examine there output. We test software with sequences that have only a single value.
Each Module Leader will do the Unit Testing and list out all the bugs in the Excel sheet.

 Integration Testing

Performance testing is designed to test the runtime performance of the system within the
context of the system. These tests were performed as module level as well as system level.
Individual modules were tested for required performance. In performance testing we counted the
processing time and response from the server with respect to request.

 Interface Testing

In the system, standards tests for GUIs have been performed, which are as follows.

 Testing the screen control for its position and size.

 The position and related labels for all controls were checked.

 Name of the form in system is given appropriately.

 All menu functions and sub functions were verified for correctness.

 Each menu functions were tested, whether it invokes the corresponding functionality
properly.

 Pull down controls was verified for proper functionality.

SPB LINCH CE - 50-

 GATE PASS SYSTEM

 Whether the non-editable text control is disabling and it was also verified that it doesn’t
exceed the maximum allowed length.

 Whether the system prompts the user with appropriate message as and when invalid
information is entered (validation).

 All required fields aren’t left blank.

 Final Testing (Development Side)

After the Integration of the all the Modules, We deploy whole the application on the
demo server. One of the member of the Development Team will done the testing of the Whole
Application and then create Excel Sheet Of the bugs.

After Completion of this testing, respective team member will solve bugs. And upload
new version of the project. Again, member who test initially are test again.

 Alpha - testing

Alpha testing is done by the person who is not involved in development team. He/She
will test the system from the user perspective. I have done alpha testing of the On System. He
tests the system and generates the bug reports, and then the development team solves those bugs.

 Stress Testing

Stress testing is to test the system for emergent properties such as performance and
reliability. Performance tests have to be designed to ensure that the system can process its
intended load. Here, we checked out the multi-user capability of our system.

A script is made for stress testing which randomly generates random data and inserts it
into the tables to check maximum load that a system can tolerate.

SPB LINCH CE - 51-

 GATE PASS SYSTEM

6.4 TEST CASES

In software engineering the most common definition of a test case is set of conditions
or variables under which a tester will determine if a requirement or use case upon an
application is partially or fully satisfied. In the situation each sub requirement must have at
least one test case. A good test should neither be too simple nor too complex. Testing is a
critical element of its quality assurance and represents the ultimate review or specification,
design and code generation.

Purpose:
The purpose of the test cases is to test the various input and see the output produce any
error or not. There are different test cases according to the system. It is tested with different types
of value like single value, multiple values and sees it can generate expected output.

 Test Cases are defined to find out whether the functionality is running successfully or
not and some of the test cases are mentioned below in table.

APE = As Per Expected

CaseID Test Case Expected Result Actual
Result
CS1 Check all links to other pages. It should call the concerned APE
page
CS2 Verify validations It should prompt user for valid APE
(Live Validation) inputs
CS3 Check whether user Interface is User should be required to APE
according to requirement or not give less input and have
detailed output
CS4 Confirm whether the Admin should have full APE
Administrator is given all the control over the system
control over the system or not
CS5 Make sure output is coming as per Output must be correct with APE
given input or not respect to Input
CS6 Try out response time of each Requested page should not APE
request take much time to be load
CS7 Check Security of System means User must be required to APE
the user should not be allowed to Login before visiting any
visit any restricted page until he is restricted pages
not authenticated
CS8 Check out whether the user is Admin should have more APE
given facilities of system facility of the system compare
according to his/her role to normal user

SPB LINCH CE - 52-

 GATE PASS SYSTEM

7. USER MANUAL

1. NORMAL DEPARTMENT LOGIN WINDOW

-53-
 GATE PASS SYSTEM

2. HOME PAGE OF NORMAL DEPARTMENT

-54-
 GATE PASS SYSTEM

3. NORMAL DEPARTMENT REQUEST FORM

-55-
 GATE PASS SYSTEM

4. NORMAL DEPARTMENT REPORTS

-56-
 GATE PASS SYSTEM

STORE DEPARTMENT

1. STORE DEPARTMENT LOGIN

-57-
 GATE PASS SYSTEM

2. HOME PAGE OF STORE DEPARTMENT

-58-
 GATE PASS SYSTEM

3. MAKE GATEPASS-VENDER SELECTION

-59-
 GATE PASS SYSTEM

4. GATEPASS-COMPANY WISE LIST

-60-
 GATE PASS SYSTEM

5. MAKE GATEPASS-DEVICE

-61-
 GATE PASS SYSTEM

6. FINAL GATEPASS-1

-62-
 GATE PASS SYSTEM

7. FINAL GATEPASS-2

-63-
 GATE PASS SYSTEM

8. ALL REPORTS INPUT

-64-
 GATE PASS SYSTEM

9. RESULT OF GENERAL PARAMETERS

-65-
 GATE PASS SYSTEM

10. SALES REPORTS

-66-
 GATE PASS SYSTEM

11. RESULTS OF SALES

-67-
 GATE PASS SYSTEM

12. STATUS-APPROVED

-68-
 GATE PASS SYSTEM

13. STATUS – DISPATCHED

-69-
 GATE PASS SYSTEM

14. STATUS-RECEIVED

-70-
 GATE PASS SYSTEM

15. MATERIAL RECEVIED UPDATED

-71-
 GATE PASS SYSTEM

16. RESULTS OF GATE NO

-72-
 GATE PASS SYSTEM

17. UPDATE QUANTITY

-73-
 GATE PASS SYSTEM

GATE MAN

1. GATEMAN LOGIN

-74-
 GATE PASS SYSTEM

2. GATEPASS REPAIRS OR REPALCED

-75-
 GATE PASS SYSTEM

3. REPORTS BASE ON GATEID

-76-
 GATE PASS SYSTEM

4. GATEMAN DISPATCH MATERIALS

-77-
 GATE PASS SYSTEM

5. GATEMAN RECEIVED MATERIALS

-78-
 GATE PASS SYSTEM

8. CONCLUSION AND FUTURE WORK

FUTURE ENHANCEMENT

Every system requires changes to keep up with the time. The design of the
system and database is flexible enough to ensure that enhancements can be
easily made without any major changes to the application.
Some functionality scope is as follows:

 Add some more functionality in the system in terms of the need of the USER.

 The maintaince of material quantity can added to the system.

CONCLUSION

This system will be very useful for users as they can easily make request for
materials. An Admin can easily make gate pass for the requests and can easily
see all reports.

-79-
 GATE PASS SYSTEM

9. ANNEXURE

9.1 Glossary of terms and abbreviations

Term or Abbreviation Definition

Abap Advanced Business Application Programming.
The SAP programming language.

SAP R/3 SAP R/3 is the former name of the main enterprise
resource planning software produced by SAP AG.

SAPGUI The SAPGUI is software on your computer that

you use to access and complete transaction in the
SAP system.
SAP Logon The SAP Logon is the windows program that you
see to log on to sap system on windows posit
mediates between the SAP system and SAP GUI
user interface .
ABAP Editor ABAP Workbench tool for creating ABAP
programs. Is called either directly through
transaction code SE38 or is embedded in other
tools such as Object Navigator, Class Builder, or
Function Builder.

ABAP Dictionary (BC-DWB-DIC) Persistent storage for data types that are visible in
all repository objects. In addition, the database
tables of the central database, views, and lock
objects are managed in the ABAP Dictionary -
among other things. The objects of the ABAP
Dictionary are maintained with the same-name
tool of the ABAP Workbench. Call through
transaction code SE11.

SAP Smart Forms

SAP form tool.
SAP Smart Forms combines previously
separate components such as forms and print
programs into a single unit. To print a form,
you only need a program for data retrieval
and a smart form from which an ABAP
function module is automatically generated.

A tool for text management and form

SAPscript
printing.

-80-
 GATE PASS SYSTEM

SAPscript consists of the following

components:
 An editor for entering and editing text,
Styles and forms for designing the print
layout, A composer, which is the central
module for output formatting.
BDC option
Batch data communication option.
BDC options define the processing mode for
a batch input session. Sessions can be
processed in the following modes:
 Display all records,Display for error
dialogs only,Process session in the
background
ALV grid control
The user interface element for displaying
tabular data in applications.
SAP provides functions that allow the user to
sort, filter, and sum data in tables. Depending
on the application, the ALV grid control
includes additional application-specific
functions and hides functions available in the
standard SAP System.

-81-
 GATE PASS SYSTEM

9.2 References and bibliography

REFERENCE BOOKS:

1. Ken Greenwood, “Teach Yourself ABAP/4”,Techmedia

2. SAP Author , BC-ABAP Dictionary, SAP-AG

3. SAP Basis, SAP Tables Reference, SAP-AG

WEBSITES:

1. www.saptechnical.com
2. www.sdnsap.com
3. www.joinerp.com
4. www.ittoolbox.com
5. www.google.com

-82-
 GATE PASS SYSTEM

9.3 About tools and technology

Architecture of SAPGUI:
SAPGUI is the user interface to SAP R/3 .it performs the following functions:
 Finds and connects to an application server
 Provides several windows for the user
 Displays data sent from the application server
 Sends user data to the application server
 Communicates with application running on the local computer

These tasks are implemented by the architecture shown in figure shown below

SAPGUI implemented in three steps .the user starts a program called SAPLogon.exe.it
searches for an application server on the desired SAP R/3 system and starts
Sapgui.exe.Sapgui.exe maintains the TCP/IP connection to the R/3 application
server.front.exe is then launched .it opens a window called “main mode” where applications
operate. Several windows can be opened at one time.Sapgui.exe multiplexes the data from
each window, sending it to the application server using the same TCP/IP connection.
SAPGUI is not only used for user input and displaying data, it is also the interface for the
R/3 application server to the user’s workstation. It communications with other process
running on the workstations such as Microsoft Office applications .it is also possible to

-83-
 GATE PASS SYSTEM

integrate ActiveX Controls into SAPGUI a modern look and feel .this feature is only
available in modern versions of SAPGUI ,which are only available for Windows 98/95/NT
and partially ,for java.

System Requirements for SAPGUI:

 64 MB of RAM minimum(128 MB of RAM recommended)
 45 MB of available disk space for SAPGUI installer
 100 MB of available disk space for SAPGUI software
 Netscape 4.5 or higher (Netscape 4.78 is recommended)
 MIT Certificates

The persons involved in SAP are as follows:

1. Functional Persons.
2. Basis person using SAP basis System application can run on different platforms
with high performance and can be adapted to meet individual user requirements.
3. ABAP Programmer

SAP R/3 Modules:

-84-
 GATE PASS SYSTEM

Startup and Shutdown of the SAP System

Use
Before you can use the SAP System you must log on .when you are finished using
the SAP System, you log off .the first time you log on and at regular intervals
thereafter, you should change you password.

Activities

 Regardless of the tasks you will be performing in the Sap System, you will
always be stating up and shutting down the SAP System.
 You start the SAP System by the selecting the logon icon on your desktop.
 You log on to the SAP System.
 If this is your first time logging on, you will have to changes the initial
password provided by your system administrator .if this is not your first time
logging on, you may have to change your password in accordance with the
security policies at your company.
 When you are finished working with the SAP System you log off.

The SAP Logon

Definition

The SAP Logon is the windows program that you see to log on to sap system
on windows posit mediates between the SAP system and SAP GUI user interface
the SAP Logon displays a list of available SAP Systems and automatically selects
servers with the best current response times. You can add available systems or
servers to this menu.

Use
When you log on to the SAP System, You can:
 Log on to a specific application server
 Log on to a group .in this case application server with the best response time
is selected automatically.

When you log on to the SAP Logon icons are displayed in the system try of the
system taskbar (in the bottom right-hand corner of the screen).you can maximize Or
minimize the SAP Logon by clicking the icon using the left mouse button.

If you click the icon using the right mouse button you can display a list of
connections to SAP Systems that are already open.

-85-
 GATE PASS SYSTEM

This enables you to see all the following information:

 Description of the SAP System and its system ID
 The Group or server
 The System number
 The Message Server
 SAP Routers

Logging On
Prerequisites
Before you log on, make sure you know:
 Your Client Number
 Your user ID
 You’re Password

If you want to work in a language other than English make sure you know the language
key for your desired language .for more information, contact you system administrator.

Logging Off
Procedure
You can log off from the SAP System from any screen. from the menu bar, choose
System ->
Logoff.

-86-
 GATE PASS SYSTEM

1.Click the button at the upper right-hand corner of the screen (if you only have one
session running).
The log off dialog appers (as shown here),informing you that any data you have not
yet saved will be lost if you proceed with logging off.

2. if you are not certain that you have saved all of your data, and you do not want to log off
after all, choose no you return to the screen in which you were working.
If you are certain that you have saved all of the data you want to save, choose yes all of
your SAP System sessions close. You have successfully logged off.
THE SAP WINDOW
Use
The SAP window is the user interface to the SAP System.

-87-
 GATE PASS SYSTEM

The standard toolbar contains buttons for performing common actions such as save and
enter.

BUTTONS NAME FUNCTIONS

Enter Confirms the data you have selected or entered on the
screen. Same function as the enter key. Does not save
your work.
Command Allows you to enter commands such as transaction codes.
Field

Save Saves your works. Same function as save in edit menu.

Back Returns you to the previous screen without saving your

data.
Exit Exits the current function without saving.
Cancel Exists the current task without saving.
First page Scrolls to the first page
Previous Scrolls to the Previous page
page
Next page Scrolls to the Next page
Last page Scrolls to the Last page
Create Create a new SAP session.
Session
Create Allows you to create a desktop shortcut to any SAP
Shortcut Report, transaction, or task.
Layout Allows you to customize the display options.
Menu
ABAP/4 Programs for SAP

ABAP (Advanced Business Application Programming, originally Allgemeiner Berichts-

Aufbereitungs-Prozessor, German for "general report creation processor”), pronounced as
'ah-bop', is a high-level programming language created by the German software company
SAP. It is currently positioned, alongside the more recently introduced Java, as the language
for programming the SAP Application Server, part of its Net Weaver platform for building
business applications. The syntax of ABAP is somewhat similar to COBOL.
ABAP is one of the many application-specific fourth-generation languages (4GLs) first
developed in the 1980s. It was originally the report language for SAP R/2, a platform that
enabled large corporations to build mainframe business applications for materials
management and financial and management accounting
ABAP used to be an abbreviation of Allgemeiner Berichtsaufbereitungsprozessor, the
German meaning of "generic report preparation processor”, but was later renamed to
Advanced Business Application Programming. ABAP was one of the first languages to
include the concept of Logical Databases (LDBs), which provides a high level of abstraction
from the basic database level(s).

The ABAP programming language was originally used by developers to develop the SAP
R/3 platform. It was also intended to be used by SAP customers to enhance SAP
applications – customers can develop custom reports and interfaces with ABAP
programming. The language is fairly easy to learn for programmers but it is not a tool for

-88-
 GATE PASS SYSTEM

direct use by non-programmers. Good programming skills, including knowledge of

relational database design and preferably also of object-oriented concepts are required to
create ABAP programs.
ABAP remains the language for creating programs for the client-server R/3 system, which
SAP first released in 1992. As computer hardware evolved through the 1990s, more and
more of SAP's applications and systems were written in ABAP. By 2001, all but the most
basic functions were written in ABAP. In 1999, SAP released an object-oriented extension
to ABAP called ABAP Objects, along with R/3 release 4.6.
Where does the ABAP program run?
All ABAP programs reside inside the SAP database. They are not stored in separate external
files like Java or C++ programs. In the database all ABAP code exists in two forms: source
code, which can be viewed and edited with the ABAP Workbench tools, and generated
code, a binary representation somewhat comparable with Java byte code. ABAP programs
execute under the control of the runtime system, which is part of the SAP kernel. The
runtime system is responsible for processing ABAP statements, controlling the flow logic of
screens and responding to events (such as a user clicking on a screen button); in this respect
it can be seen as a Virtual Machine comparable with the Java VM. A key component of the
ABAP runtime system is the Database Interface, which turns database-independent ABAP
statements ("Open SQL") into statements understood by the underlying DBMS ("Native
SQL"). The database interface handles all the communication with the relational database
on behalf of ABAP programs; it also contains extra features such as buffering of tables and
frequently accessed data in the local memory of the application server.

To give you a better overview pictures are the various modules of ABAP/4 and SAP
software:
 PP – Production Planning
 MM – Material Management
 SD – Sales and Distribution
 FI – Financial Accounting
 CO- Controlling
 AM-Fixed Assets Management
 PS-Project Systems
 WF-Work Flow
 IS – Industry Solutions
 HR – Human Resources
 PM – Plant Maintenance
 QM-Quality Management

ABAP/4 and SAP and all other enterprise resource software (such as people soft, bean and
Oracle) are hot. The software will not stay the same for long, it must be tweaked, revised,
cut expanded to meet the on going needs of the business.
What will ALV do for me?
ALV ‘s broad functionality lets you emphasize ,hide, and reformat list items :add graphic
elements ;and generally make any ABAP list display a more powerful communications
tool.ALV Grid Control can be used in the SAP GUI for Window TM or the SAP GUI for
JAVA TM environments and can be displayed on the web.ALV functionality lets users:
 Choose fonts and formats text elements to create a more interesting display that’s
easier to understand.
 Apply typical list functions like sorting and filtering without extra programming .

-89-
 GATE PASS SYSTEM

 Apply and modify built-in functions.

 Add a response to a user-action like double-clicking on a display line.
 Prints lists or export them to other application.
 Apply and modify built –in function.
 Define and save custom output settings then select and change from pull-down menu

ALV Grid Control is SAP’s graphical List-viewing tool and is similar in look and feel to
Microsoft Excel.ALV functionality lets SAP end-users.

 Perform common list operations such as summing and filtering.

 Perform graphical functions such as typeface and paragraph formatting.
 Crate, share and maintain a library of output templates.
 Customize data output on the fly.

MATERIAL MANAGEMANT (MM) MODULE

Introductions:
Materials management is the branch of logistics that deals with the tangible
components of a supply chain. Specifically, this covers the acquisition of spare parts and
replacements, quality control of purchasing and ordering such parts, and the standards
involved in ordering, shipping, and warehousing the said parts.
Goals
The goal of materials management is to provide an unbroken chain of components
for production to manufacture goods on time for the customer base. The materials
department is charged with releasing materials to a supply base, ensuring that the
materials are delivered on time to the company using the correct carrier. Materials is
generally measured by accomplishing on time delivery to the customer, on time
delivery from the supply base, attaining a freight budget, inventory shrink
management, and inventory accuracy. The materials department is also charged with
the responsibility of managing new launches.

In some companies materials management is also charged with the procurement of

materials by establishing and managing a supply base. In other companies the
procurement and management of the supply base is the responsibility of a separate
purchasing department. The purchasing department is then responsible for the
purchased price variances from the supply base.

In large companies with multitudes of customer changes to the final product over
the course of a year, there may be a separate logistics department that is responsible
for all new acquisition launches and customer changes. This logistics department
ensures that the launch materials are procured for production and then transfers the
responsibility to the plant materials management to manage

-90-
 GATE PASS SYSTEM

Materials Management Challenges

The major challenge that materials managers face is maintaining a consistent flow of
materials for production. There are many factors that inhibit the accuracy of inventory
which results in production shortages, premium freight, and often inventory adjustments.
The major issues that all materials managers face are incorrect bills of materials, inaccurate
cycle counts, un-reported scrap, shipping errors, receiving errors, and production reporting
errors. Materials managers have strived to determine how to manage these issues in the
business sectors of manufacturing since the beginning of the industrial revolution. Although
there are no known methods that eliminate the afore mentioned inventory accuracy
inhibitors, there are best methods available to eliminate the impact upon maintaining an
interrupted flow of materials for production.

One challenge for materials managers is to provide timely releases to the supply
base. On the scale of worst to best practices, sending releases via facsimile or PDF file is the
worst practice and transmitting releases to the supplier based web site is the best practice.
Why? The flaw in transmitting releases via facsimile or email is that they can get lost or
even interpreted incorrectly into the suppliers system resulting in a stock out. The problem
with transmitting EDI releases is that not all suppliers have EDI systems capable of
receiving the release information. The best practice is to transmit the releases to a common
supplier web base site where the suppliers can view (for free) the releases. The other
advantage is that the supplier is required to use the carrier listed in the web site, must
transmit an ASN (advanced shipping notification), and review the accumulative balances of
the order
THE effective materials management plan builds from and enhances an
institutional master plan by filling in the gaps and producing an environmentally responsible
and efficient outcome. An institutional campus, office, or housing complex can expect a
myriad of benefits from an effective materials management plan. For starters, there are long-
term cost savings, as consolidating, reconfiguring, and better managing a campus’ core
infrastructure reduces annual operating costs. An institutional campus, office, or housing
complex will also get the highest and best use out of campus real estate

Benefits
An effective materials management plan also means a more holistic approach to
managing vehicle use and emissions, solid waste, hazardous waste, recycling, and utility
services. As a result, this means a “greener,” more sustainable environment and a
manifestation of the many demands today for institutions to become more environmentally
friendly. In fact, thanks to such environmental advantages, creative materials management
plans may qualify for LEED Innovation in Design credits.

And finally, an effective materials management plan can improve aesthetics.

Removing unsafe and unsightly conditions, placing core services out of sight, and creating a
more pedestrian-friendly environment will improve the visual and physical sense of place
for those who live and work there.

-91-
 GATE PASS SYSTEM

9.4 About the organization

 COMPANY PROFILE

AJD INFOTECH was started in May 2004. It was founded by Mr. SUNIL
DOSANI looking into growing needs of support and training for various ERPs. The CEO of
the company Mr. SUNIL DOSANI is having a very reach exposure of around 20 year’s in
IT Industry. He has worked in vertical industries like textiles, Engineering and
pharmaceuticals. He was a project manager for SAP implementation and has been working
with SAP since year 1999. He has also provided training to the various types of groups like
top management, departmental heads, key users and operational uses in SAP. He has design,
developed and implemented the integrated applications company wide using oracle and
various development tools.
AJD INFOTECH
About Company
AJD INFOTECH was started in May 2004. It was founded by Mr. SUNIL DOSANI
looking into growing needs of support and training for SAP in Gujarat. We are providing
quality and cost effective services on SAP on AMC basis or on call basis. We have a team
of four people including BASIS / ABAP / SD / MM consultant and freelancers working on
sap projects. Our area of services is
1. SAP Onsite / Offsite Helpdesk and Post implementation support
2. Corporate Training (Groups of IT Users/Key Users/End Users)
3. Project Management and Co-ordination (Acting as coordinator for any project related to
SAP with the external service providers/Vendors to ensure optimum utilization of services)
4. Process Improvement and Functional Consultancy in SAP / ERP
5. Application Development in SAP using ABAP and Advance ABAP Tools
6. Providing Training in Management institutes like NIRMA / ICFAI on ERP.

Supporting on Modules
 BASIS/ABAP

 MM (Material Management)

 SD (Sales & Distribution)

 PP (Production Planning)

 QM (Quality Management)

-92-
 GATE PASS SYSTEM

 FI (Financial Accounting)

 CO (Controlling)

 PM (Plant Maintenance)

Projects/Assignments undertaken AJD INFOTECH Ahmadabad.

A MNC engineering company using sap version 4.7 With Country India Modules.
From: May 2004 to Till Date
 SAP Helpdesk and Support

 Process Improvement

 Customization and Configuration in SAP related to process Improvement

 Project coordination for up gradation from SAP version 4.0B to 4.7

 CIN upgrading from 2.2A to SAP 4.7 CIN( Country India Version)

 Post Upgrade support on all core modules and CIN

 Project coordination for the implementation of “Six Sigma” being conducted by

NCQM (National Council for Quality Management)

 Application development/ABAP programming

 Training of IT users/Key Users/End Users

Providing other non SAP IT services like Setting up of leased lines, procurement of servers,
upgrading of hardware etc

-93-
 GATE PASS SYSTEM

9.5 INSTITUTE PROFILE

9.5.1 Introduction

Saffrony institute of technology is developed with an aim To continuously strive for the
total development of students by educating them in state-of-the-art technologies and helping
them imbibe professional ethics and social commitment, so that they emerge as competent
professionals to meet global challenges.

Saffrony Institute of Technology aims to continuously strive to make it a center of

excellence in providing professional education and allied services, redefining quality
standards far above the aspirations of the society.

The Saffrony Institute of Technology is committed to inculcate discipline and perseverance

in students and faculty to ensure that they meet and exceed the highest academic standards
and expectations of the society, in general and Industry in particular.

In pursuance of the quality goals, the Management, Faculty and Students of SIT affirm their
commitment to the policy of continuous improvement in their endeavours.

9.5.2 Programms

SPB Patel Engineering College offers four year Bachelor of Engineering degree
programmes in five streams at undergraduate level viz. 
1.      Electronics & Communication Engineering (60 seats)
2.      Computer Engineering (60 seats)
3.      Information Technology (60 seats)
4.      Mechanical Engineering (90 seats)
5.      Civil Engineering (60 seats)

Master of Business Administration (MBA) –Two Years (60 seats)

It is envisaged to make the institute a centre of excellence in professional education adhering to high
quality standards. The institution will provide the effective linkage between professional education and
industry.

-94-