Skip to main content

PRODUCT DIRECTORY STRUCTURE in Oracle Apps






Oracle Applications installs in a machine it creates a base directory with the name ORACLE. This is the base directory for accessing the application.

Oracle Applications supplied in three flavors

1. Production Oracle Applications: used for implementing in any organization.

2. Vision Oracle Applications: used for Demonstration or Training purpose.



3. Test Oracle Applications: used for R&D purpose

Product Directory Structure of Oracle Applications

VISDB: Consists of Oracle 8i / Oracle 9i / Oracle 10g Database executable files.

VISORA: Captures 8.0.6 / 9iAS / 10giAS middleware Database executable files.

VISCOMM: Captures Control Script files, which are used to Start or Stop the
Application Services.

VISDATA: Captures all .DBF files.

VISAPPL: Captures all Module Specific Directories and Some Special Directories.




GL_TOP: (APPL_TOP/GL/11.5.0) is one of the Module Directory of Oracle Applications.It consists of a release directory (i.e. 11.5.0) under which Forms, Reports, BIN, LIB, SQL,etc.,

GL_TOP/11.5.0/Forms/US has formed directory to store all.FMX (Compiled) Form files of a specific module.

GL_TOP/11.5.0/Reports/US is a reports directory to capture all the.RDF (Compiled) Report files of a specific module directory.

The US is a language specific directory.

GL_TOP/11.5.0/BIN will capture the C, C++, PRO*C, SQL *LOADER etc., files.

GL_TOP/11.5.0/LIB will capture all.OBJ files of C, C++ or JAVA CLASS files.

GL_TOP/11.5.0/Message will capture all.MSB message body files.

GL_TOP/11.5.0/LOG will capture all.LOG files.

GL_TOP/11.5.0/OUT will capture all.OUT files.

GL_TOP/11.5.0/SQL will capture all .SQL script files.

GL_TOP/11.5.0/HTML will capture all .HTML, .HTM web files.

GL_TOP/11.5.0/FND is a Special Directory known as Application Object Library (AOL) directory. It is used to capture all Modules Application Executable Files.

GL_TOP/11.5.0/AU is an Application Utility (AU) Directory. It consists of an application release b‐Directory, which consists of Forms and Resource directories. It is used to store all.FMB and.PLL and PL/SQL Library files.

GL_TOP/11.5.0/AU/11.5.0/Forms/US will capture.FMB Form files of all Modules.

GL_TOP/11.5.0//AU/11.5.0/Resource is used to store.PLL and.PL/SQL Library files of Oracle Applications.



DATA MODEL
When we install Oracle Database by default system will create SYS and SYSTEM schemas. These consist of all Data Dictionary Tables. Like this, if we install Oracle Applications System will automatically create schemas of all Modules (i.e. GL, AR, AP, etc.) with the respective module name as User and Password. Along with these schemas some special Schemas i.e. APPS, APPLSYS, APPLSYSPUB will be created for the special purpose.


APPLSYS Schema: This is a special Schema consists of the files starts with FND, ALR, WF, and AD.

APPLSYSPUB Schema: This schema is a collection of public synonyms of all FNDTables, which are used for User verification. This is the Gate Way User ID of OracleApplications.

Note:
1. When we are changing the APPS Schema password, first we have to change in the backend for both APPS and APPLSYS Schemas.
2. Password for both APPS and APPLSYS should be same.
3. Change the password of both the Schemas in Front‐End and Back‐End.
4. Drop the Concurrent Manager Services and re‐create the Concurrent Manager
Service with the Password as APPS Password.


Labels:

Comments

Post a Comment

Popular posts from this blog

AP, AR, GL, INV, PA, FA, PO, TCA, Workflow - Interface and Base table in Oracle Apps R12

Main Interface and Base table in Oracle Apps R12 GL Module (General Ledger Module tables in Oracle Apps R12) Interface Table Base Table gl_interface gl_budget_interface gl_je_batches gl_je_headers gl_je_lines gl_je_sources gl_je_categories gl_sets_of_books gl_daily_rates gl_balances gl_periods gl_period_sets gl_code_conbinations AR Module (Account Receivable Module  tables  in Oracle Apps R12) Interface Table Base Table ra_customers_interface_all   ra_contact_phones_int_all ra_customer_profiles_int_all hz_parties hz_cust_accounts hz_cust_acct_sites_all hz_cust_sit_use_all hz_party_sites hz_locations hz_party_site_uses hz_customer_profiles hz_organization_profiles hz_person_profiles ra_interface_lines_all ra_interface_distributions_all ra_interface_salescredits_all ra_customer_trx_all ra_customer_trx_lines_all ra_cust_trx_line_gl_dist_all ra_cust_trx_types_all ar_payment_schedules_all ra_batch_sources_All ar_vat_tax_all ra_terms ar_periods ar_perio
2 comments
Read more

Error: - APP-PER-50022: Oracle Human Resource Could Not Retrieve a Value For The User Type Profile Option. Please ensure it is set property for your responsibility

Error: - APP-PER-50022: Oracle Human Resource Could Not Retrieve a Value For The User Type Profile Option. Please ensure it is set the property for your responsibility. Solution-:      (1)  Go to System administrator > Profile > System       (2) Now Search “ HR: User Type ” Profile option at Responsibility level with Respective Responsibility. And Click On FIND Button. Now Select HR: User Type Value “HR with Payroll User” (you can choose another option as well accordingly). And SAVE. Now check your responsibility, error removed. Go ahead with your next step and enjoy Oracle Apps. For More Information Visit on www.OracleAppsGuide.com Or Subscribe your email-id on OracleAppsGuide.
3 comments
Read more

Definition of Lookup in Oracle Apps R12 Or What is Lookup in Oracle Apps R12? Or What is the main purpose of lookups in Oracle Apps R12?

Definition of Lookup in Oracle Apps R12 Or What is Lookup in Oracle Apps R12? Or What is the main purpose of lookups in Oracle Apps R12? The main purpose of a lookup is to keep programs flexible and easier to configure. Lookups are an approach of creating a configurable “list of values” in E-Business Suite. One of the simplest examples of a lookup type is gender. A “gender lookup” will have definitions as shown next: Code       Meaning M             Male F              Female U             Unknown Suppose that there is a table for employees named PER_ALL_PEOPLE_F and it has the following columns: FIRST_NAME LAST_NAME DATE_OF_BIRTH GENDER The screen that displays an employee’s gender will display a value of Male, Female, or Unknown. However, the database column PER_ALL_PEOPLE_F table. GENDER will store a value of M, F, or U. Hence, the screen displays the meaning, whereas the database columns reference the lookup via a lookup code. If in the future your organization wants the users to s
Post a Comment
Read more