erp in management information system

7/30/2019 Erp in Management Information System

1/64

1

AMITY INSTITUTE OF INFORMATION TECHNOLOGY (AIIT)

AMITY UNIVERSITY, UTTAR PRADESH

PROJECT REPORT ON

ERP IN MANAGEMENT INFORMATION SYSTEM

A Project report

to be submitted by

Khushbu

A1004911035

B.Sc-IT(V)

Submitted to-

Ms. Deepa Gupta

Internal Guide

Asst.Professor,AIIT


2/64

2

INTERNAL GUIDE CERTIFICATE

This is to certify that Khushbu ,student of Amity Institute of Information Technology(Enrollment no: A1004911035) has successfully completed the project report titled

ERP in MIS. This is authentic work carried out by her under my guidance. This

project report has not been awarded before for obtaining degree or diploma in any

course to the best of my knowledge and belief.

Guide/supervisor :

Designation :

Date :

Place :


3/64

3

ACKNOWLEDGEMENT

My first experience of project has been successful, I am thankful to my project

guide Mrs Navita Dubal, IT Manager, REC under whose guidelines I was able to

complete my project. I am wholeheartedly thankful to her for giving me her

valuable time & attention & for providing me a systematic way for completing my

project in time.

I am also thankful to Mr. Prasantha Mukhopadhyay, Head of IT Deptt. REC and

all training and development members for providing me assistance in various

hardware and software problems encountered during the course of my project.

I also convey my thanks to TCS staff for helping and guiding me in my project.

Special thanks to Mr. P.J Thakkar, Director(Technical),REC and Mr. Bal

Mukand, Ex-Director(technical),REC for giving me such an opportunity and

allowing me to work on this project.

I also thank my faculty guide Ms. Deepa Gupta for her cooperation and support.


4/64

4

STUDENT CERTIFICATE

I, Khushbu, a student of Bachelor of Science-Information Technology (IT), in the

Department of Information and Technology, Amity Institute of Information and

Technology, Amity University, Noida, under class Roll No.A1004911035, for the

session 2011-14, hereby, declare that the project entitled ERP in Management

Information System has been completed by me in the Summer Training II. I

hereby declare, on behalf of myself, that the matter embodied in this project is an

original work and has not been submitted earlier for award of any degree or

diploma to the best of my knowledge and belief. Moreover, the project report does

not breach any existing copyright or any other third party rights.


5/64

5

ABSTRACT

Rural Electrification Corporation Limited (REC), a NAVRATNA Central Public Sector

Enterprise under Ministry of Power, was incorporated on July 25, 1969 under the

Companies Act 1956. Its main objective is to finance and promote rural electrification

projects all over the country. It provides financial assistance to State Electricity Boards,

State Government .

The purpose of MIS in ERP is to facilitate the flow of information between all business

functions inside the boundaries of the organization and manage the connections to

outside stakeholders. These reports include near-real-time performance of cost centers

and projects with detail sufficient for individual accountability.

Project Scope: It covers only ERP application covering the corporate offices and its

project offices.

Tools: Oracle SQL ,Toad,Oracle Report Builder,XML Oracle Desktop Publisher:

Development Platform: Microsoft Windows XP professional

Deployment Platform: Microsoft Windows XP professional


6/64

6

Table of contents

Company Certificate

Internal Guide Certificate

Acknowledgement

Student Certificate

Abstract

1.Introduction to Organization .................................................................................................... 7-8

2.Introduction to Project ............................................................................................................ 9-11

2.1 Objective ........................................................................................................................... 9

2.2 Problem Definition ......................................................................................................... 10

2.3 Scope ............................................................................................................................... 10

2.4 Definitions, Acronyms, and Abbreviations .................................................................... 10

2.5 Technologies and Tools to be used ........................................................................... 10-11

3.Software Requirement Specification .......................................................................................... 12

4.Architecture.......13-27

4.1 Design and Development ......................................................................................... 18-21

4.2 Application Structure ................................................................................................ 22-27

5.Validation Checks ...................................................................................................................... 28

5.1 Format check ................................................................................................................ 28

5.2 Limit check ..................................................................................................................... 28

5.3 Range Check ...................................................................Error! Bookmark not defined.

6.Testing .................................................................................................................................. 29-30

7.Maintenance ............................................................................................................................... 31

8.Limitation of the Project ............................................................................................................. 32

9.Scope of the Project .................................................................................................................... 33

10.Glossary .............................................................................................................................. 34-35

11.Bibliography ............................................................................................................................. 36

12.Screenshots ......................................................................................................................... 37-64


7/64

7

INTRODUCTION TO ORGANIZATION

Rural Electrification Corporation Limited, a NAVRATNA

Central Public Sector Enterprise under Ministry of Power, was incorporated on July 25,

1969 under the Companies Act 1956. REC a listed Public Sector Enterprise

Government of India with a net worth of Rs. 12,789 Crore as on 31.03.11. Its main

objective is to finance and promote rural electrification projects all over the country. It

provides financial assistance to State Electricity Boards, State Government Departments

and Rural Electric Cooperatives for rural electrification projects as are sponsored by

them.

REC provides loan assistance to SEBs/State Power Utilities for investments in rural

electrification schemes through its Corporate Office located at New Delhi and 17 field

units (Project Offices), which are located in most of the States.

The Project Offices in the States coordinate the programmes of RECs financing with

the concerned SEBs/State Power Utilities and facilitate in formulation of schemes, loan


8/64

8

sanction and disbursement and implementation of schemes by the concerned SEBs/State

Power Utilities.

Mission & Vision:

a .To facilitate availability of electricity for accelerated growth and for enrichment of

quality of life of rural and semi-urban population.

b.To act as a competitive, client-friendly and development-oriented organisation for

financing and promoting projects covering power generation, power conservation,

power transmission and power distribution network in the country.


9/64

9

INTRODUCTION TO PROJECT

Enterprise resource planning (ERP) is a cross-functional enterprise system driven by

an integrated suite of software modules that supports the basic internal business

processes of a company. ERP gives a company an integrated real-time view of its core

business processes such as production, order processing, and inventory management,

tied together by ERP applications software and a common database maintained by a

database management systems. ERP systems track business resources (such as cash, raw

materials, and production capacity) and the status of commitments made by the business

(such as customer orders, purchase orders, and employee payroll), no matter which

department (manufacturing, purchasing, sales, accounting, and so on) has entered the

data into the system. ERP facilitates information flow between all business functions

inside the organization, and manages connections to outside stakeholders.

Enterprise system software is a multi-billion dollar industry that produces components

that support a variety of business functions. IT investments have become the largest

category of capital expenditure in United States-based businesses over the past decade.

Enterprise systems are complex software packages that offer the potential of integrating

data and processes across functions in an enterprise. Although the initial ERP systems

focused on large enterprises, there has been a shift towards smaller enterprises also

using ERP systems.

Organizations consider the ERP system a vital organizational tool because it integrates

varied organizational systems and enables flawless transactions and production.

However, an ERP system is radically different from traditional systems

development. ERP systems can run on a variety ofcomputerhardware and networkconfigurations, typically employing a database as a repository for

information.

2.1 OBJECTIVE:

The purpose of MIS in ERP is to facilitate the flow of information between all business

functions inside the boundaries of the organization and manage the connections to

outside stakeholders. These reports include near-real-time performance of cost centersand projects with detail sufficient for individual accountability.
http://en.wikipedia.org/wiki/Computer_hardwarehttp://en.wikipedia.org/wiki/Computer_hardwarehttp://en.wikipedia.org/wiki/Computer_networkhttp://en.wikipedia.org/wiki/Databasehttp://en.wikipedia.org/wiki/Databasehttp://en.wikipedia.org/wiki/Computer_networkhttp://en.wikipedia.org/wiki/Computer_hardwarehttp://en.wikipedia.org/wiki/Computer_hardware


10/64

10

2.2 PROBLEM DEFINITION

The first step in doing Systems Analysis and Design is Problem Definition.

Problem Definition process includes:

To get the requirements of user Discuss the actual inputs and outputs demanded in particular format. Outline a Strategy for developing the required reports to make them live on front

end.

2.3 SCOPE

It covers ERP of production.

2.4 Definitions, Acronyms, and Abbreviations:

SQL (Structured Query Language): It is used to create query for database. Oracle Reports: It is suite of programs that allows your organization to

centralize report processing and to better manage reporting.

ERP (enterprise resource planning): It is an industry term for the broad set ofactivities that helps a business manages the important parts of its business.

XML (Extensible Markup Language): Itis a markup language that defines aset of rules for encoding documents in a format that is both human-readable and

machine-readable.

2.5 Technologies and Tools to be used:

Front End:Oracle Apps 11i:An industry term for the broad set of activities that helps a

business manage the important parts of its business.

Back End:RDBS Oracle:The Oracle Database is an object-relational database

management system (ORDBMS) produced and marketed by Oracle Corporation.

Languages/Tools:Oracle SQL: It is used to create query for database.

Toad: Oracle Database Tool for SQL Development and Administration

Oracle Report Builder: A query builder with a visual representation of the

specification of SQL statements to obtain report data


11/64

11

XML Oracle Desktop Publisher: The engine can format any well-formed

XML data, allowing integration with any system that can generate XML,

including Web Servicesor any data source available through JDBC.


12/64

12

SOFTWARE REQUIREMENT SPECIFICATION

Complete understanding of software requirements is essential to the success of asoftware development effort. Requirement analysis is a process of discovery,

refinement, modeling and specification. Models of the required data, information and

control flow, and operational behavior are created.

A number of requirement activities are there like:

Requirement understanding-understood the reporting needs of the user Detailed discussion with user to gather requirements Reading their original reports.---old report formats Structure and Layout planning Developed initial reports and got it treated by user before converting to final Test case generation

In oracle reports, analysis lies in knowing the complete information about the

user requirement. The reports are :

1. REC DVAT Payment Report.2. REC Scheme General Details Report.3. REC Project Status Report.4. REC Scheme wise Disbursement Report.


13/64

13

ARCHITECTURE

The reports have been developed on the basis of following requirements.

This report gives the user details of the Dvat payment under various project categories

along with the vendor name and its vendor registration number. Invoice Amount,

Invoice date, Tax Amount, Tax Rate, Invoice number are also shown.

Input: Combination of effective dates for period.

Output: To obtain vendor name, vendor registration number, Invoice Amount, Tax

Amount, Tax Rate, Invoice number Invoice dateand the combination of effective dates

entered.

Table name: REC DVAT PAYMENT REPORT

Serial

No.

Inputs / Outputs

Description

Data type Comment

1. Vendor Name Character Name of the project2. Vat Registration

Num

Varchar2 Registration number

3. Project Number Varchar2 Project Number

4. Project Name Varchar2 Name of the project

5. Tax Amount Varchar2 Tax Amount of the vendor

6. Invoice Date Date Date of the creation of invoice

7. Invoice Amount Varchar2 Invoice amount sanctioned to the

vendor

8. Customer Varchar2 Customer to whom loan is sanctioned

9. Tax Rate Varchar2 Tax sanctioned rate

10. Invoice Num Varchar2 Invoice number sanctioned to the

customer


14/64

14

FORMAT:

REC DVAT PAYMENT REPORT

From date-

To date-

2. This report gives the user details of the Scheme General Report under various project

categories over the last five financial years along with the Scheme codeand its Schemename. Scheme location, Borrower name, Date of Documentation, Scheduled cod date

and Revised cod date are also shown.

Input: Combination of effective dates for period.

Output: To obtain Scheme code, Scheme name, Scheme location, Borrower name,

Date of Documentation, Scheduled cod date, Revised cod date and combination of

effective dates entered.

Table name:REC SCHEME GENERAL DETAILS REPORT

Vendor

Name

Vat

Registration

Number

Invoice

Date

Invoice

Amount

Tax

Amount

Tax Rate Invoice

Number

Invoice

Date

Serial

No.

Inputs / Outputs

Description

Data type Comment

1. Scheme code Character Code of the project

2. Scheme name Varchar2 Scheme name of the project


4. Project Name Varchar2 Name of the project5. Scheme location Varchar2 Location of the scheme

6. Borrower name Character Date of the creation of invoice

7. Date of

Documentation

date Date of the scheduled documentation


9. Scheduled cod date Date Scheduled Cod date

10. Revised cod date Date Revised Cod date


15/64

15

FORMAT:

REC SCHEME GENERAL DETAILS REPORT

From date-

To date-

Scheme

code

Scheme

name

Scheme

location

Borrower

name

Date of

Documentation

Scheduled

cod date

Revised

cod date

Borrower

name

3. This report facilitates the user to know the number of Projects of a particular project

type in a particular status and the other important details associated with the project.

Input: Project type and Project Status Name are entered by user

Output: To obtain Project Number, Project ID, Project Name, Date Created, Major

Category, Minor Category, Customer, Sanctioned Date, Loan Amount Sanctioned

according to the user entered project type & project status name, from the specified

database.

Table name: REC Project Status Report

Serial

No.

Inputs / Outputs

Description

Data type Comment

1. Project Type Character Type of the project

2. Project Status

Name

Character Status of the project


4. Project Name Varchar2 Name of the project

5. Date Created date Date of the project beginning6. Major category Varchar2 Major category in which the project

exist

7. Minor category Varchar2 Minor category in which the project

exist


9. Sanctioned Date date Loan sanctioned date

10. Loan amount

Sanctioned

Varchar2 Loan amount sanctioned to the

customer


16/64

16

FORMAT:

REC Project Status Report

Project Type:

Project Status Name:

4.This report gives the user, details of the disbursement under various project categoriesover the last five financial years along with the name of state and its customer. Scheme

Code, Date of Sanction, Amount Sanctioned are also shown.

Input: Minor Category is needed to be entered by the user.

Output: To obtain State name, Utility, Scheme Code, Minor Category, Date of

Sanction, amount Sanctioned, Disbursement Years- 2008-09, 2009-10,2010-11,2011-

12,2012-13 from the specified database.

Table name: REC Scheme wise Disbursement Report

Project

Number

Project

Name

Date

Created

Major

category

Minor

Category

Customer Sanctioned

Date

Loan

Amount

Sanctioned

Serial

No.

Inputs / Outputs

Description

Data type Description

1. Statename Varchar2 Name of the state

2. Utility Varchar2 Name of the

customer

3. Scheme Code Varchar2 Code of the scheme

4. Minor Category Varchar2 Project Minor

Category5. Date of sanction Varchar2 Date of sanction of

loan amount

6. Disb 08-09 Varchar2 Disbursed amount

during year 2008-09

7. Disb 0910 Varchar2 Disbursed amount

during year 2009-10


during year 2010-11


during year 2011-12


during year 2012-13


17/64

17

FORMAT:

REC Scheme wise Disbursement Report

Minor Category-

Statename Utility Scheme

Code

Minor

Category

Date of

Sanction

Amount

Sanctioned

Disb

08-09

Disb

09-10

Disb

10-11

Disb

11-12

Disb

12-13


18/64

18

DESIGN AND DEVELOPMENT

1. Table Columns-

Vendor name, vendor registration number, Invoice Amount, Tax Amount, TaxRate,Invoice number, Invoice date.

User inputs-

From Date, To Date

Report-

REC Dvat payment Report

User input-

From Date, To Date

Oracle

Database

Process

(Sql, Rdf,

Xml, Rtf)


19/64

19

2.Table Columns-

Scheme code, Scheme name, Scheme location, Borrower name, Date of

Documentation, Scheduled cod date, Revised cod date

User inputs-

From Date, To Date

Report-

REC Scheme General Details Report

User input-

From Date, To Date

Oracle

Database

Process

(Sql, Rdf,

Xml, Rtf)


20/64

20

3.Table Columns-

Project ID, Project Name, Date Created, Major Category, Minor Category,

Customer, Sanctioned Date, Loan Amount Sanctioned

User inputs-Project Type, Project Status Name

Report-


User input-

Project Type,

Project Status Name

Oracle

Database

Process

( Sql, Rdf, Xml,

Rtf)


21/64

21

4.Table Columns-

Statename, Utility, Scheme Code, Minor Category, Date of Sanction, Amount

Sanctioned, Disbursement years 2008-09, 2009-10, 2010-11, 2011-12, 2012-13

User inputs-

Minor category.

Report-

REC Scheme Wise Disbursement Report

User input-

Minor Category

Oracle

Database

Process

(Sql, Rdf,

Xml, Rtf)


22/64

22

APPLICATION STRUCTURE

SQL

Structured Query Language Standard language Can be pronounced as S-Q-L or as sequel

(which refers to an antiquated dialect)

Language common to many modern databases MySQL PostgreSQL Oracle Microsoft SQL Server

Most SQL databases are relational Relationships between sets of data link them together Other types: hierarchical (MUMPS), object oriented Also usually handles concurrency (simultaneous

access from multiple locations)

Why we use relational databases?

Reduce redundancy and associate different kinds of data Example: training class

Instructor table has names of instructors

Students table has names/info of students

Each class then links instructors and students with other unique information

Most data exists in only one location, so changing it is easy Data storage is much smaller


23/64

23

Database Definitions

Field (Column) Piece of data to store

Row unique set of fields

Table Set of rows with fields in the same order

Database Disk set aside for a set of tables Access control for users

Instance Memory and CPU allocated to multiple databases

Data Types

Numercal Integer and floating point

String (Text)

Variable or fixed length

Time/Date Date Time Year

Enum (set of named options) Binary (BLOB)

SQL Command Types

Definition Create/Modify/Delete structure that data will go into.

Manipulation Add, update, or remove rows or row data

Retrieval Get data from database


24/64

24

No change to values Transaction

Wrap several statements into one block Useful to back out if a statement fails

Control Access control for users or groups

Other Some databases extend SQL or allow user defined functions

Definition

CREATE

Creates a new table in a database DROP

Deletes an existing table from a database Any data stored is deleted as well

ALTER Alter parts of an existing table Remove or add fields Modify field data types Change storage engine Can be done on-the-fly, but be aware of Consequences

Manipulation

INSERT Add new row to a table

UPDATE Change contents of row(s) that already exist in table

DELETE Remove row(s)

Retrieval

SELECT


25/64

25

Get data from table(s) Can be constrained by:

Which fields get returned Logic operations on row contents (less than, greater than, equal to, etc.)

Can also include JOIN clauses to search across multiple tables in onestatement

Transaction

Ensures that multiple events happen at one time.

Canonical example is a financial transaction Transfer of money from one person to another can't be interrupted while

in process

Either money goes from person A to person B or nothing happens Another example is correcting mistakes or backing out of an error

START TRANSACTION Defines start of a block of transactions Data changes are not seen by other users until transaction is committed

COMMIT All changes are made permanent

ROLLBACK Undo all changes made during course of transaction

COMMIT and ROLLBACK end the transaction

SQL Functions

COUNTnumber of rows in result SELECT COUNT(*) ;

SUMadd numbers together SELECT SUM( 4 + 5 );


26/64

26

CURRENT_DATEreturn current date SELECT CURRENT_DATE();

MIN Returns the minimum value of an expression.

MAX Returns the maximum value of an expression.

IN Reduce the need to use multiple OR conditions.

SQL Conditions

"AND" Condition Allows to create an SQL statement based on 2 or more conditions being

met. It can be used in any valid SQL statement - select, insert, update, or

delete.

"OR" Condition Allows to create an SQL statement where records are returned when any

one of the conditions are met. It can be used in any valid SQL statement

- select, insert, update, or delete.

LIKE Condition Allows to use wildcards in the where clause of an SQL statement. This

allows you to perform pattern matching. The LIKE condition can be used

in any valid SQL statement - select, insert, update, or delete.

BETWEEN Condition

Allows to retrieve values within a range.

EXISTS Condition Considered "to be met" if the subquery returns at least one row.

Union Query

Allows you to combine the result sets of 2 or more "select" queries. Itremoves duplicate rows between the various "select" statements.


27/64

27

Union All Query

Allows you to combine the result sets of 2 or more "select" queries. Itreturns all rows (even if the row exists in more than one of the "select"

statements).

Each SQL statement within the UNION ALL query must have the samenumber of fields in the result sets with similar data types.

Intersect Query

Allows you to return the results of 2 or more "select" queries. However, it onlyreturns the rows selected by all queries. If a record exists in one query and not in

the other, it will be omitted from the INTERSECT results.

Each SQL statement within the INTERSECT query must have the same numberof fields in the result sets with similar data types.

Minus Query

Returns all rows in the first query that are not returned in the second query.


28/64

28

VALIDATION CHECKS

1. Format check

Checks that the data is in a specified format (template), e.g., dates have to be in the

format DD/MM/YYYY. Regular expressions should be considered for this type of

validation.

2. Limit check

Unlike range checks, data is checked for one limit only.

3. Range checkChecks that the data lie within a specified range of values, e.g., the user input dates

should be in between the mentioned range.


29/64

29

TESTING

Software testing is a critical element of software quality assurance and represents the

ultimate review of specification, design, and code generation.

Unit Testing

Unit testing focuses verification effort on the smallest unit of software designthe

software component or module. Using the component-level design description as a

guide, important control paths are tested to uncover errors within the boundary of the

module. The relative complexity of tests and uncovered errors is limited by the

constrained scope established for unit testing. The unit test is white-box oriented, and

the step can be conducted in parallel for multiple components.

1) Testing of Report 1:

1. Inputs:

From Date: 1-Jan-2013

To Date : 31-Jan-2013

Output: REC Dvat Payment Report generated correctly for above inputs.

2. Inputs:

From Date : 1-Jan-2013

To Date : 31-mar-2013

Output: REC Dvat Payment Report generated correctly for above inputs.


1. Inputs:

From Date: 1-jan-2013

To Date : 31-jan-2013


30/64

30

Output: REC Scheme General Detail Report generated correctly for above

inputs.

2. Inputs:

From Date: 1-jan-2013

To Date : 31-mar-2013

Output:REC Scheme General Detail Report generated correctly for above

inputs.


1. Inputs:Project Type: ****** Project Status: Ongoing

Output: REC Project status Report generated correctly for above inputs.

2. Inputs:Project Type: ****** Project Status: Appraisal

Output: REC Project status Report generated correctly for above inputs.


1. Inputs:

SPA: PE

Output: REC Scheme wise Disbursement Report is correctly developed.

2. Inputs:SPA:PE

Output: REC Scheme wise Disbursement Report is correctly developed


31/64

31

MAINTENANCE

Software Maintenance in software engineering is the modification of a softwareproduct after delivery to correct faults, to improve performance or other attributes.

A common perception of maintenance is that it merely involves fixing defects.

However, one study indicated that the majority, over 80%, of the maintenance effort is

used for non-corrective actions. This perception is perpetuated by users submitting

problem reports that in reality are functionality enhancements to the system.

Software maintenance and evolution of systems was first addressed by Meir M. Lehman

in 1969. Over a period of twenty years, his research led to the formulation ofLehman's

Laws (Lehman 1997). Key findings of his research include that maintenance is really

evolutionary development and that maintenance decisions are aided by understanding

what happens to systems (and software) over time. Lehman demonstrated that systems

continue to evolve over time. As they evolve, they grow more complex unless some

action such as code refactoring is taken to reduce the complexity.

The key software maintenance issues are both managerial and technical. Key

management issues are: alignment with customer priorities, staffing, which organization

does maintenance, estimating costs. Key technical issues are: limited understanding,

impact analysis, testing, and maintainability measurement. Maintenance activities can

be classified into four types:-

Adaptivedealing with changes and adapting in the software environment Perfectiveaccommodating with new or changed user requirements which concern

functional enhancements to the software

Correctivedealing with errors found and fixing it Preventiveconcerns activities aiming on increasing software maintainability and

prevent problems in the future

MIS in ERP is a long term project. Following the above mentioned detail,

maintenance will be done time to time.
http://en.wikipedia.org/wiki/Software_engineeringhttp://en.wikipedia.org/wiki/Software_bughttp://en.wikipedia.org/wiki/Software_evolutionhttp://en.wikipedia.org/wiki/Meir_M._Lehmanhttp://en.wikipedia.org/wiki/Software_evolution#Lehman.27s_Laws_of_Software_Evolutionhttp://en.wikipedia.org/wiki/Software_evolution#Lehman.27s_Laws_of_Software_Evolutionhttp://en.wikipedia.org/wiki/Code_refactoringhttp://en.wikipedia.org/wiki/Change_impact_analysishttp://en.wikipedia.org/wiki/Change_impact_analysishttp://en.wikipedia.org/wiki/Code_refactoringhttp://en.wikipedia.org/wiki/Software_evolution#Lehman.27s_Laws_of_Software_Evolutionhttp://en.wikipedia.org/wiki/Software_evolution#Lehman.27s_Laws_of_Software_Evolutionhttp://en.wikipedia.org/wiki/Meir_M._Lehmanhttp://en.wikipedia.org/wiki/Software_evolutionhttp://en.wikipedia.org/wiki/Software_bughttp://en.wikipedia.org/wiki/Software_engineering


32/64

32

LIMITATION OF THE PROJECT

User cannot change the report at its end. Only any technical person has the authority to change the report. In this project, work is done only on the Management Information System of

Enterprise Resource Planning.


33/64

33

SCOPE OF THE PROJECT

In this project, reports are being developed according to the requirement of user to

obtain the data from Oracle database. Here requirements keep modifying, so regular

development of such reports is necessity.

For development, finance management and information management are essential parts.

These get included in ERP. In the MIS in ERP project, queries and reports are

developed to get the right data in right format with a proper management of time.

On the front end, user can easily access all the reports generated according to his

requirement, without knowing the backend work.

Management Information System involves three primary resources: people, technology,

and information or decision making. Since its involvement is in the three most

important resources, so its scope will remain till the management of these resources will

be required.

Enterprise Resource Planning has become essential part of todays management. With

the development, there will be more need of such management and planning system.

Thats why this project holds alot of scope in future till the need of such management .


34/64

34

GLOSSARY

MIS/Management Information System

A management information system (MIS) provides information that is needed to

manage organizations efficiently and effectively. Management information systems

involve three primary resources: people, technology, and information or decision

making. Management information systems are distinct from other information systems

in that they are used to analyze operational activities in the organization. Academically,

the term is commonly used to refer to the group of information management methods

tied to the automation or support of human decision-making, e.g. decision support

systems, expert systems, and executive information systems.A successful MIS supports

a business' long range plans, providing reports based upon performance analysis in areas

critical to those plans, with feedback loops that allow for titivation of every aspect of

the enterprise, including recruitment and training regimens. MIS not only indicates how

things are going, but also why and where performance is failing to meet the plan. These

reports include near-real-time performance of cost centers and projects with detail

sufficient for individual accountability.

ERP (Enterprise Resource Planning)

is an industry term for the broad set of activities that helps a business manage the

important parts of its business. The information made available through an ERP system

provides visibility for key performance indicators (KPIs) required for meeting corporate

objectives. ERP software applications can be used to manage product planning, parts

purchasing, inventories, interacting with suppliers, providing customer service, and

tracking orders. ERP can also include application modules for the finance and human

resources aspects of a business. Typically, an ERP system uses or is integrated with a

relational database system.

SQL (Structured Query Language)

is a computer language for accessing and manipulating databases. The fundamental

concept is to think of the data as being stored in one or more tables. When a request is

made to retrieve from these tables, which is called query, the resultant output is also

presented in as table.


35/64

35

Oracle RDBMS

The Oracle Database (commonly referred to as Oracle RDBMSor simply as Oracle) is

an object-relational database management system (ORDBMS) produced and marketed

by Oracle Corporation.

XML (EXtensible Markup Language)

A document format for the Web that is more flexible than HTML. While HTML uses

only predefined tags to describe elements within the page, XML allows tags to be

defined by the developer of the page. Thus, tags for virtually any data items such as

product, sales rep and amount due, can be used for specific applications, allowing Web

pages to function like database records. XML is a subset of the SGML documentlanguage, and HTML is a document type of SGML.


36/64

36

BIBLIOGRAPHY

[1.] www.techonthenet.com

[2.] www.oracle.com

[3.] www.google.com

[4.] www.wikipedia.com

[5.] Introduction to Oracle9i: SQL by Nancy Greenberg and Priya Nathan

[6.] Basic SQL and Database Theory by David Hummel


37/64

37

SCREENSHOTS

DVAT Payment Report

Objective- Development of DVAT Payment Report.

QUERY:

SELECT c.vendor_name,c.vat_registration_num,a.invoice_date,a.invoice_amount,SUM

(b.tax_amount)tax_amount,d.tax_rate,a.invoice_num

FROM

ap_invoices_all a,

jai_ap_tds_inv_taxes b,

po_vendors c,

ja_in_tax_codes dWHERE

a.invoice_id=b.invoice_id

AND a.vendor_id=c.vendor_id

-- and c.vendor_id=d.vendor_id

AND b.section_type = 'WCT_SECTION'

AND d.vendor_id=216

AND b.actual_tax_id=d.tax_id

AND a.cancelled_date IS NULL

and invoice_date between :start_date and :end_date

GROUP BY

a.invoice_num,a.invoice_amount,a.invoice_date,c.vendor_name,d.tax_name,d.tax_rate,

c.VAT_REGISTRATION_NUM

ORDER BY c.vendor_name;


38/64

38

sql query using toad application and pl/sql application.

Generating reports using Oracle Report Builder.


39/64

39

Making data model of the sql query.


40/64

40

Adding parameters.

Generating xml file


41/64

41

Rtf of REC DVAT Payment Report

Tagging different fields


42/64

42

Loading xml data


43/64

43


44/64

44

Final pdf of the report


45/64

45

REC SCHEME GENERAL DETAILS REPORT

QUERY

select a.segment1 as schemecode,

a.name as scheme_name,

b.city as scheme_location,

xx_pa_common.P_CUSTOMER_NAME(a.project_id)as borrower_name ,

xx_pa_common.P_DOCUMENTTATION(a.project_id) as date_of_documentation,

xx_pa_common.P_COMPLETION_DATE(a.project_id) as scheduled_COD_date,

xx_pa_common.P_REVISED_COMPLETION_DATE(a.project_id)as revised_COD_date

from pa_projects_all a,

pa_locations b

where xx_pa_common.P_DOCUMENTTATION(a.project_id) between

nvl(:from_date,xx_pa_common.P_DOCUMENTTATION(a.project_id)) and

nvl(:to_date,xx_pa_common.P_DOCUMENTTATION(a.project_id))

and b.city = nvl(:state_name,b.city)

Preparing the data model


46/64

46


47/64

47

Defining parameters


48/64

48

Generating xml file

File> generate to file> xml

Parameters form


49/64

49

Progress of the report

Xml file of the data


50/64

50

Rtf of REC Scheme General Detail Report

Tagging of parameters


51/64

51

Tagging of fields

Loading the xml data


52/64

52


53/64

53

Pdf of the final report


54/64

54


select

a.segment1 PROJECT_NUMBER,

a.project_id PROJECT_ID,a.name PROJECT_NAME,

To_char(a.creation_date, 'fm DD Month YYYY') DATE_CREATED,

xx_pa_common.P_CLASS_CATEGORY(a.project_id) MAJOR_CATEGORY,

xx_pa_common.p_class_code(a.project_id) MINOR_CATEGORY,

xx_pa_common.P_CUSTOMER_NAME(a.project_id) CUSTOMER,

To_char(xx_pa_common.P_ISSUE_OF_SANCTION_LETTER(a.project_id), 'fm DD

Month YYYY') SANCTIONED_DATE,

xx_pa_common.P_LOAN_AMT_SANC(a.project_id)

LOAN_AMOUNT_SANCTIONED

from

pa_projects_all a,

pa_project_statuses s

where

a.project_status_code=s.project_status_code

and a.project_type= :proj_type

and s.project_status_name= :p_status_name


55/64

55

Making data model

Double click on Data Model icon-> SQL -> click on blank area to get queryinput box


56/64

56

Import or write the SQL query of your requirement

Connect the system with database, by clicking on Connect tab and enter Username, Password, Database to which you want to connect ->

Then click on connect.


57/64

57

After connecting,query will be created, like this ->

Then go to Program -> Compile-> All

When compiling is successful then check if query is running

Program-> RunNow, if you want to run the report with layout click on Yes.

Fill in the user parameters


58/64

58


59/64

59

REC SCHEMEWISE DISBURESMENT REPORT

Double click on Data Model icon-> SQL -> click on blank area to get queryinput box


60/64

60

Import or write the SQL query of your requirement.

Connect the system with database, by clicking on Connect tab and enter Username, Password, Database to which you want to connect ->

Then click on connect.


61/64

61

After connecting,

query will be created, like this ->

Then go to Program -> Compile-> AllWhen compiling is successful then check if query is running

Program-> Run

Now, if you want to run the report with layout click on Yes.


62/64

62

Though for live environment, preference is given to develop your own layout of report. For

that purpose XML Desktop Publisher is being used.For that purpose firstly we generate Xml file

from Report Builder

File-> Generate to file-> XML

Then file is saved->


63/64

63

Rtf

Now for live working environment

Microsoft word-> Add-ins-> Load-> Load XML data


64/64

To view the output

Add-ins->preview->excel

erp in management information system

Documents