apps basics session 1

7/25/2019 Apps Basics Session 1

1/6

What is Oracle E-Business Suite: it is known on the market by various names such as OracleEnterprise Resource Planning (ERP! Oracle "pps! Oracle "pplications! Oracle #inancials$ %t isengineere& to work as an integrate& system on a common %' inrastructure$

The product offering in E-Business Suite is organized into product families.

Some of the key product families are as follows:

#inancialsProcurement)ustomer Relationship *anagement ()R*Pro+ect *anagementSupply )hain Planning an& *anagement,iscrete *anuacturingProcess *anuacturing

Or&er *anagementuman Resources *anagement System (R*S"pplications 'echnology

%n E-Business Suite! each pro&uct amily usually consists o in&ivi&ual applications$ #ore.ample! some o the applications that make up the Oracle #inancials pro&uct amily are /eneral0e&ger! Payables! Receivables! )ash *anagement! iReceivables! iE.penses! an& others$

History of Oracle pps:

When the Oracle ERP pro&uct was initially launche&! the screens were built in character mo&e$

'he en& users interacte& with the system through &umb terminals! which provi&e& a character-base& interace that connecte& to the back en& server$ Both Oracle #orms (then known asS102#orms an& Oracle ,atabase were run at the back en& tier$ %nitially! the R34$5 version oOracle "pplications ran in character mo&e! as &i& all the previous releases$

When Oracle release& its /6% version calle& Smart)lient! the Smart)lient screens were builtwith Oracle #orms 7$8 an& ran at the &esktop client tier! accessing the &atabase over the network$"lthough Smart)lient provi&e& a better user e.perience! it was &iicult to maintain! as sotwareup&ates nee&e& to be &istribute& on every in&ivi&ual client &esktop$ 0ast in that release! Oracleannounce& R34$5 9)" (9etwork )omputing "rchitecture! which was an attempt to integratethe latest web technologies into Oracles business applications using three-tier architecture!inclu&ing &atabase an& applicationservers; en& users interacte& with the system using the browser rom their client &esktops$

'he latest releases o E-Business Suite! R33i an& R3

*ost o the screens in Oracle E-Business Suite were initially &evelope& using Oracle #orms$owever! over the last ew years! Oracle has starte& to &eliver new screens using pure web-base&technology$ 'hese web-base& screens &o not run within a =ava applet! unlike #orms-base&


2/6

screens$ %nstea&! the '*0-base& screens are run with a browser such as #ireo. or %nternetE.plorer$ Oracle initially starte& &eveloping '*0-base& pages in E-Business Suite primarily toprovi&e a light ootprint application or Sel-Service>base& applications$

)ommitment to the open in&ustry stan&ar&s usually lea&s to the increase& pro&uct

interoperability$ " pure '*0-base& web application is lightweight an& it runs without the nee& or a

=ava applet in the browser$

"n a&option o the new components an& emerging technologies such as "="?! Rich

%nternet "pplications (R%"! an& others ensures a better en& user e.perience$

"s a result o the prece&ing actors! even the new back oice screens are now being &evelope&as '*0-base& pages using Oracle "pplication #ramework (O" #ramework$

9owa&ays! Oracle E-Business Suite &evelopers in& themselves working with both Oracle #ormsan& O" #ramework! as the current releases (Release 33i an& Release 3


3/6

system coniguration an& setup! this is the irst option to look at as it provi&es the saest way tochange the system$

!ustomizations and E$tensions: certain business reAuirements cannot be met through thepro&uct coniguration an& personali@ation! the technical &evelopment team is reAuire& either to

e.ten& the e.isting pro&uct unctionality or intro&uce completely new custom mo&ules thatseamlessly integrate with the stan&ar& pro&uct an& unctionality$

E-Business Suite En%ironments:'he installations can be either on the same machine or on&ierent physical machines$ Each such installation is calle& an instance or an environment oOracle E-BusinessSuite an& consists o E-Business Suite sotware! an Oracle &atabase inclu&ing the &ata iles! an&Oracle server sotware$

&aster en%ironment'his environment is use& or the main coniguration setup o the system$"lthough it &oes not contain any transactional &ata! it is important that the master environment ismanage& by a very strict change control as this environment contains pro&uction (master setup$

'e%elopment en%ironment'his is where &evelopers &esign an& buil& e.tensions an&customi@ations$ 'he &evelopers are usually grante& very powerul access rights or both E-Business Suite an& the operating system that hosts the system$ #or instance! the &evelopers maybe grante& System "&ministrator or "pplication ,eveloper responsibilities$

Testing en%ironment(also known as 6"' ,evelopers usually &o not have an "PPS &atabaseschema passwor& to this environment$ 'his is where users sign o on customi@ations an&coniguration changes$

'eployment en%ironmentOnce the users have inishe& their 6ser "cceptance 'esting on a 6"'instance! patchesCscripts can then be promote& to a ,eployment instance or inal checks$Eectively! applying patches on a ,eployment instance is a &ry run beore applying co&echanges to a Pro&uction instance$

#atching en%ironmentOracle &elivers their co&e changes! bug i.es! an& pro&uct up&atesthrough patches$ 'he patches can be &ownloa&e& rom the Oracle Support website an& applie&by E-Business Suite &atabase a&ministrators ("pps ,B"s$ "pps ,B"s can use the patchingenvironment to perorm sanity checks or patches &elivere& by Oracle$

Support en%ironmenti a user reports an issue on the pro&uction system! it is a goo& i&ea torepro&uce the problem on a copy o the pro&uction system$ Such copie& instances are reerre& to

as clones$ 'he support environment is e.clusive to the support sta! where &evelopers &o notmake changes &irectly$ 'his environment is usually the most reAuently clone& environment incases where E-Business Suite implementation is running a live pro&uction instance$ #reAuentcloning helps the E-Business Suite support sta to repro&uce pro&uction issues$

!(# en%ironment'he conerence room pilot environment is where someone! usually animplementation team! gets buy-in to their pro&uct oering rom the wi&er user an& business


4/6

community &uring an implementation$ 'his environment is usually use& or sign-o &uring newimplementations$

&igration en%ironment#or new implementations o Oracle "pplications! &evelopers are taske&with migration o &ata rom the ol& legacy systems into Oracle E-Business Suite$ 'his is where

repeate& &ata migration can take place beore the migration co&e gets ro@en an& rea&y or usertesting$

#roduction en%ironment'his is where the business runs its &ay-to-&ay operations$

%n very simple terms! the lie cycle o e.tensions an& customi@ations coul& be summari@e& asollows: the &eveloper perorms the &evelopment an& unit testing in the &evelopmentenvironment! an& the co&e gets promote& to the testing environment$ #ollowing successultesting! the changes are applie& to the pro&uction environment$ 'here can be more than one&evelopment environment or any implementation as well as a live site! especially when some othe bigger mo&ules are being implemente& with &ierent timelines$ 9evertheless! the changes in

each &evelopment environment shoul& i&eally be teste& on a common test (6"' environment$

Shared 'ata &odel: simplie& view o &ata sharing between the mo&ules in Oracle "pplications$


5/6

E$ample of 'ata Sharing


6/6

System !omponents for Both ()) and ()* in Oracle pps:

!oncurrent #rogram:"ter you have &eine& the logic or your program! you must &eine aconcurrent program that you call rom your orms or rom Stan&ar& ReAuest Submission$ Douirst &eine a concurrent program e.ecutable that tells the application where to in& your programlogic$ Dou then &eine as many concurrent programs as you nee& that use your concurrentprogram e.ecutable$ Dou can &eine which concurrent programs are incompatible with yourconcurrent program! an& i you use Stan&ar& ReAuest Submission! you &eine the parametersuse& by your e.ecutable$ Dou can speciy vali&ation inormation or your parameters to controlthe values users select on the Submit ReAuest orm$

To develop or customize a report in a Purchasing module, assuming the executable name isXXPOPRINT.rdf, ou need to register the executable !ith the XXPO application. "ence, thisR#$ must be transferred to director %home%oracle%apps%appl%xxpo%reports%&'(). *hen theend user runs this report from the application, Oracle +pps !ill identif the executableXXPOPRINT as being attached to the XX Purchase Order application. This application !illhave a short name of XXPO and !ill be mappedto director %home%oracle%apps%appl%xxpo%reports%'( for reports, !hich is !here the leXXPOPRINT.rdf resides on the server. "ence, the name of the application !ill help the Oracle+pps environment locate the executable le on the server.

apps basics session 1

Documents