What is ERP (Enterprise Resource Planning) ERP stands for enterprise resource planning.

In an organization, ERP is not only utilized for mechanizing business transactions and complicated business processes, but also for redesigning wor management system. !ttaining inno"ation and higher le"el impro"ements in business process performance becomes a complicated tas without measuring the capability of ERP. With the help of ERP, organizations can impro"e coordination and information access throughout the organizational units and this in turn leads to successful management of tas interdependence. ERP pro"ides combined business software modules which acts as a base and supports the functional units of an enterprise. it follows a process oriented approach and considers the core processes such as order fulfillment, materials procurement, preparation of balance sheet etc.

ERP is #. $ultifunctional system, which acts as a business model for planning, control and global optimization for the whole supply chain by ma ing use of the I% technology which pro"ides satisfactory ser"ices to all the parties in"ol"ed. &. !n integrated suite of application software modules, which pro"ide operational, managerial and strategic information for an enterprise, so that an enterprise can impro"e the standards of 'uality, producti"eness and efficiency to withstand the competition,. (. an important element through which an enterprise can balance its resources li e human resources, materials, money on so to compete internationally. ). Process oriented and cross functional approach ERP can introduce business process re*engineering and can bring in radical changes in an organization. ERP pro"ides following functions #. +uman resources &. ,orporate finance (. Production Planning and ,ontrol ). $aterials $anagement -. .uality $anagement, /ales $anagement 0. Plant $aintenance 1. /ales and 2istribution etc.

ERP is important in the business because3 #. It helps in automating the processes in the business as it consists of in*built cross functional integration, and triggers the interdependent acti"ities which are set by the business rules leading to effecti"e business process automation in terms of efficient producti"ity, manpower producti"ity, lowering in"entory carrying cost, etc. &. ERP helps in a"ailing right information at right time, which enables business intelligence capability in ta ing effecti"e decisions leading to effecti"e performance in the organization. (. It has transformations effect on the business. 4asic 5eatures of ERP3 #. Process oriented &. ,ross functional approach (. Radical changes ). top*down concept -. I% as a powerful enables 0. Integrated suite of application software $odules 1. Pro"ides "alue*added ser"ices

ERPs available in market

6 /!P 6 7racle !pplications o People /oft o /iebel o 82 Edwards 7racle applications are used to capture 4usiness functionality information of the organization. 6 Instances o 2e"elopment 9 2e"elopment : 2e"elopment /tage # : 2e"elopment /tage & o %esting 9 %esting o Production 9 ,lient %esting Roles in"ol"ed in 7racle !pplications and their responsibilities in brief #. 24!* 2atabase administrator a) Installation of 7racle !pplications b) !pplying patches c) $aintaining $ultiple Instances &. 5unctional ,onsultant a) Interaction with client b) ;athering the re'uirement for de"elopment<customization c) !bout 7racle applications what a"ailable and what wasn=t a"ailable. d) E>ample in"oice form 9 fields 9 7r de"elop an in"oice form from scratch e) Preparation of 522 (5unctional 2esign 2ocument) (. %echnical ,onsultant 9 Input 522 a) ;o through the 522 b) Prepare %22 ( %echnical 2esign 2ocument) 9 ?ogic, %ables, Procedures, 5orms, $enus, Pac ages 9 appro"al c) 2e"elopment of ,omponent

d) %est the ,omponent e) 2eli"er to the client !ll these sessions will go through the below mentioned ,omponents R I , E 9 ,omponents for de"elopment 1@A 6 R * Reports * Reports 0i 6 I * Interfaces * Programs, /.?,P?</.? 6 , * ,on"ersions * Programs, /.?,P?</.? 6 E * E>tensions * 5orms0i 5unctions Bnowledge (@A 6 Purchase 7rder $odule 6 !ccounts Payable $odule In"entory $odule 6 7rder $anagement $odule

Types of Projects in oracle apps:

Implementation Project: ,lient will be using software to maintain the business solutions. Cow the client wants to ha"e oracle data con"ersions, gap analysis, and functions documents preparation from the scratch 9 first time.

Customization Project: ,lient was already using 7racle !pplications, now the client would li e to ha"e few more modules to co"er the business, for that we will customize new modules to co"er the business, for that we will customize new modules and integrate with e>isting modules.

Migration or Up-gradation Project: ,lient was already using 7racle !pplications older "ersion now client would li e to mo"e new "ersion of 7racle !pplications that time we will migrate older "ersion obDects in to new "ersion.

Support or Maintenance: 7nce the implementation, customization, and migration are o"er, then supporting proDect will be started where we will gi"e supporting for the proDects which were already de"eloped, customized, and migrated.

Oracle Applications Architecture:

%he 2es top %ier %he client interface is pro"ided through +%$? for +%$?*based applications, and "ia a 8a"a applet in a Web browser for the traditional 5orms*based applications.

In 7racle !pplications Release #&, each user logs in to 7racle !pplications through the E*4usiness /uite +ome Page on a des top client web browser. %he E*4usiness /uite +ome Page pro"ides a single point of access to +%$?*based applications, 5orms*based applications, and 4usiness Intelligence applications. 7nce logged in "ia the E*4usiness /uite +ome Page, you need not sign on again to access other parts of the system. 7racle !pplications does not prompt again for user name and password, e"en when you na"igate to other tools and products. 7racle !pplications also retains preferences as you na"igate through the system. 5or e>ample, if you registered in the E*4usiness /uite +ome Page that ;erman is your preferred language, this preference carries o"er whether you access 5orms*based or +%$?*based applications. %he !pplication %ier %he application tier has a dual role3 hosting the "arious ser"ers and ser"ice groups that process the business logic, and managing communication between the des top tier and the database tier. %his tier is sometimes referred to as the middle tier. 5our ser"ers or ser"ice groups comprise the basic application tier for 7racle !pplications3 E Web ser"ices E 5orms ser"ices

E ,oncurrent Processing ser"er E !dmin ser"er %he 2atabase %ier %he database tier contains the 7racle database ser"er, which stores all the data maintained by 7racle !pplications. %he database also stores the 7racle !pplications online help information. $ore specifically, the database tier contains the 7racle data ser"er files and 7racle !pplications database e>ecutable that physically store the tables, inde>es, and other database obDects for your system. %he database ser"er does not communicate directly with the des top clients, but rather with the ser"ers on the application. APPS Schema /chema is a physical location in the database which holds the same set of database obDects. %he !PP/ schema has access to the complete 7racle E*4usiness /uite data model. It is analogous to the /F/%E$ schema, which has access to the entire database. 7racle !pplications responsibilities connect to an !PP/ schema and the en"ironment "ariable 5C2C!$ is set to the name of the !PP/ schema. !PP/ and 4ase Product /chemas !ll data obDects for a product are owned by a schema for that product, nown as a base product schema. 7ne schema, called !PP/, owns all the code obDects for the 7racle E*4usiness /uite, and has access to all data obDects. %here is one !PP/ schema for e"ery product installation group. %he following code obDects are installed in the !PP/ schema3 E Pac ages E Procedures E 5unctions E %riggers E Giews E $aterialized "iews E 8a"a classes E .ueues %he following obDects are installed in the base product schemas3 E %ables E /e'uences E Inde>es E ,onstraints E .ueues In addition, there are grants from the tables and se'uences to the !PP/ schema, as well as synonyms from the !PP/ schema to those obDects.

!PP/ /chema 4enefits %he !PP/ schema impro"es the reliability of and reduces the time needed for installation, upgrade, and patching by eliminating the need for cross*product grants and synonyms. Htilizing a single schema that has access to all obDects eliminates cross*product dependencies, and creates a hub*and*spo es access model rather than a spiderIs web. ,ustom /chema !ccess In some circumstances, you may wish to create a schema that has limited or read*only access to 7racle !pplications data. Warning3 /ince the !PP/ schema has all pri"ileges to all 7racle !pplications obDects, you should ne"er gi"e users direct access to this schema. Fou will need to grant access on obDects to the user schema from the base product schema. Cote3 Fou may need to re*grant access if the underlying obDect is dropped and recreated.