, , ,

Oracle Apps Fundamentals

Three environments, each with a different URL and different database instance. These are

  • Development environment; where developers usually have System Administrator responsibility and also the apps password. If not System Administrator then at least they should have access to “Application Developer” responsibility.
  • Testing environment; Developers usually do not and must not have apps password to this environment . This is where users sign-off customizations or even setup changes.
  • Production environment; This is where the business runs
When you logs in the user is authenticated against a table named fnd_user for the username and password.
Oracle internally uses a login named GUEST, prior to invoking validation of actual username. Oracle uses a DB User account named applsyspub to which it first connects during validation of LOGIN. This user account has very restricted privileges and has access to below objects (primarily for authentication purposes):-
  1. All the pl/sql packages will be created in APPS Schema
  2. All the views will be created in APPS Schema
  3. For each table in individual schema, there will exist one synonym in APPS schema
  4. Tables are not created in APPS schema, every implementation has at least 1 custom schema, where custom tables are created.
  5. For each custom table created by you, you will need to create a Synonym in APPS schema
Custom tables are generally required in Oracle ERP because:
1. You wish to create a custom screens ( your own screen to capture some info) for a functionality that is not delivered by Oracle.
2. Pre-Interface tables
3. Temp processing
4. Staging of data for third party extract interfaces

To create a new table named, the steps are
Step 1. Create table in custom schema .
Step2. Grant all on schema.table_name to apps
Step 3. connect to apps/apps, and
Create or replace synonym for schema.table_name

Oracle Apps Deployment
  • Any executable that has intense database operations is stored at database tier e.g. oracle reports, sql files, sql*loader.
  • Any executable that has intense UI operations is deployed at forms tier. Examples are Oracle Forms fmx files, jsp files, pll/plx etc.
  • A form that has intense database processing, must handle most of the database processing within pl/sql packages. The api’s that you build in pl/sql must have well defined parameters.
  • Multiple mid-tiers distributes the user load. The user requests are first sent to a load balancer switch, this switch the decides which middle tier to use.
  • You will need to deploy your forms file to each middle tier machine (unles shared APPL_TOP) has been implemented.
  • FMB files delivered by oracle are picked from $AU_TOP/forms/us.
  • All of the pl/sql packages are installed in apps schema.This includes your custom packages and also oracle delivered packages.
  • The forms are attached to form functions and it is the form function that is attached to an application
  • To generate CUSTOM.pll: cd $AU_TOP/resourcef60gen module=$AU_TOP/resource/CUSTOM.pll userid=apps/apps output_file=./CUSTOM.plx module_type=LIBRARY
Optional environments:-
  • CRP environment: Conference room pilot environment is where usually implementation team gets buying to their product offering from user community, during implementation. This environment is usually used for sign off during new implementations.
  • Patching environment: This is where all new Oracle Patches are sanity tested.
  • Support environment: This environment is exclusive to support staff. This environment is usually the most frequently cloned environment in Oracle Apps site that has gone live. Frequent cloning helps the Oracle Applications support staff to reproduce production issues
  • Migration Environment: This is where repeated data migration can take place before migration code gets frozen and ready for UAT. 
0 replies

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply