, , , ,

System Administrator – Configuration

A system administrator is involved in setting up an Oracle Applications installation, controlling access, and ensuring smooth ongoing operation. The tasks involved in these functions are described in the Oracle Applications System Administrator’s Documentation Set, in these three volumes.

  1. Configuration
  2. Security
  3. Maintenance

This Oracle Applications System Administrator’s Guide – Configuration volume describes the tasks involved in setting up and configuring Oracle Applications. These tasks may be done once upon installation, or may also be done as needed, such as setting up a printer or customizing online help files.
Oracle Applications Tablespace Model and the Tablespace Migration Utility
The new Oracle Applications Tablespace Model (OATM) has fewer, consolidated tablespaces (twelve, including three system tablespaces: temporary, system and undo segments). Locally managed tablespaces are also supported.
The Tablespace Migration Utility is a menu-based Perl program that enables you to estimate future space requirements for the tablespaces and to migrate the Applications  database to OATM.

/by
, , , , ,

Oracle Applications Architecture(Sys Admin)

The Oracle Applications Architecture is a framework for multi-tiered, distributed computing that supports Oracle Applications products. In this model, various servers or services are distributed among three levels, or tiers.
A tier is a logical grouping of services, potentially spread across more than one physical machine. The three-tier architecture that comprises an Oracle E-Business Suite installation is made up of the database tier, which supports and manages the Oracle database; the application tier, which supports and manages the various Applications components, and is sometimes known as the middle tier; and the desktop tier, which provides the user interface via an add-on component to a standard web browser.

Centralizing the Oracle Applications software on the application tier eliminates the need to install and maintain application software on each desktop client PC, and also enables Oracle Applications to scale well with an increasing load. Extending this concept further, one of the key benefits of using the Shared Application Tier File System model (originally Shared APPL_TOP) is the need to maintain only a single copy of the relevant Applications code, instead of a copy for every application tier machine.
The Desktop Tier
The client interface is provided through HTML for HTML-based applications, and via a Java applet in a Web browser for the traditional Forms-based applications.

In Oracle Applications Release 12, each user logs in to Oracle Applications through the E-Business Suite Home Page on a desktop client web browser. The E-Business Suite Home Page provides a single point of access to HTML-based applications, Forms-based applications, and Business Intelligence applications.
Once logged in via the E-Business Suite Home Page, you need not sign on again to access other parts of the system. Oracle Applications does not prompt again for user name and password, even when you navigate to other tools and products. Oracle Applications also retains preferences as you navigate through the system. For example, if you registered in the E-Business Suite Home Page that German is your preferred language, this preference carries over whether you access Forms-based or HTML-based applications.
The Forms client applet is a general-purpose presentation applet that supports all Oracle Applications Forms-based products, including those with customizations and extensions. The Forms client applet is packaged as a collection of Java Archive (JAR)
files. The JAR files contain all Java classes required to run the presentation layer of Oracle Applications forms.
The Application Tier
The application tier has a dual role: hosting the various servers and service groups that process the business logic, and managing communication between the desktop tier and the database tier. This tier is sometimes referred to as the middle tier.
Four servers or service groups comprise the basic application tier for Oracle Applications:

  • Web services
  • Forms services
  • Concurrent Processing server
  • Admin server

Note: In Release 12, the Web and Forms services are provided by  Oracle Application Server (OracleAS) 10g. They are no longer servers in the sense of being a single process, as was the case in previous Applications releases.  It is advisable to avoid using a mixture of different platforms on your application tier. This makes maintenance easier, since only one set of patches needs to be downloaded.

The Database Tier
The database tier contains the Oracle database server, which stores all the data maintained by Oracle Applications. The database also stores the Oracle Applications online help information.
More specifically, the database tier contains the Oracle data server files and Oracle Applications database executables that physically store the tables, indexes, and other database objects for your system. The database server does not communicate directly with the desktop clients, but rather with the servers on the application tier, which mediate the communications between the database server and the clients.

/by
, , , , ,

R12 Installed base Setups

 All All the functionalities of installed base module can be accessed with Installed Base User responsibility. And to access the’ Installed Base User’ responsibility’ the user must be assigned to CSI_NORMAL_USER role.
Follow the below setups to assign the required roles to Installed Base Users

1. Login to the instance with sysadmin user and select CRM HTML Administration responsibility
2. Navigate to Setup : Users : Registration: user Maintenance
3.  Query the user name, click on the hyperlink for the user
4.  Add the CSI_NORMAL_USER role. Update.
The responsibility “Install Base User” is obsolete in Release 12.  The new responsibility is called ‘Oracle Installed Base Agent User’
Notice that the Role assignment via CRM HTML administrator is for Oracle Installed Base User responsibility (ie. JTT page). Oracle Install Base Agent User responsibility is a new one in R12.

Profile Options
 The Important Profile Options which needs to be set at the site level are
Service: Inventory Validation Organization
CSI: Default Instance Status

/by
, , ,

Installed Base in R12


Oracle Installed Base is an item instance life cycle tracking application that facilitates enterprise-wide life cycle item management and tracking capability.
You specify which items you want to track in the Master Item list in Oracle Inventory. Subsequently, when a particular real-world instance of the item is created, an item instance record is created in Oracle Installed Base. Any significant changes to the item instance will also be recorded in Oracle Installed Base.

Tangible Items
Item instances can be used to track tangible items, that is, physical, real-world objects, that can be assembled and shipped, such as computers, engines, machine parts, and so on.
Intangible Items
Item instances can be used to track intangible items such as software, services, licenses, and agreements. For example, a telephone number can have different services such as call waiting and conference call. These can all be defined and tracked as components of the telephone service.
Serialized Items
When a trackable item is defined in Oracle Inventory as serialized, each item instance derived from that item requires a unique serial number and individual tracking. The item instance will always have a quantity of 1.
Non-Serialized Items
When a trackable item is defined in Oracle Inventory as non-serialized, it is typically for smaller objects whose real-world instances do not require individual tracking. For example, a screw could be defined as a non-serialized, trackable item; an order for 100 screws would result, after order shipping, in the creation of one item instance, with  quantity 100.
/by
, , , ,

What document can be viewed after running purchasing document open interface with records rejected?

Check the process_code in the po_headers_interface and po_lines_interface, if it is ‘REJECTED’,

select process_code from po_headers_interface;
select process_code from po_lines_interface;

please do the following:
Run the program – Purchasing Interface Errors Report
choose parameter : PO_DOCS_OPEN_INTERFACE

The report will list all the errors you have during importing. You can fix the data, then reset process_code = Null in both interface tables, rerun the Purchasing Document Open Interface.

update po_headers_interface set process_code = null
where process_code = ‘REJECTED’;
update po_lines_interface set process_code = null
where process_code = ‘REJECTED’;

/by