Standard costing is used by Customers who employ predetermined costs for valuing inventory and for charging material, resource, overhead, period close, and job close and schedule complete transactions. Differences between standard costs and actual costs are recorded as variances.

Manufacturing industries typically use standard costing. Costs of items can be shared across organizations using standard costing.

The unit cost of any item is the sum of the costs of all the cost elements.
There are 5 cost elements, which are defined as follows:

1. Material — The raw material/component cost at the lowest level of the bill of
material determined from the unit cost of the component item.

2. Material Overhead — The overhead cost of material, which can be used for any costs attributed to direct material costs.

3. Resource — Direct costs, such as people (labor), machines, space, or miscellaneous charges, required to manufacture products.

4. Overhead — The overhead cost of resource and outside processing, which is
used as a means to allocate department costs or activities.

5. Outside Processing — This is the cost of outside processing purchased from a supplier.

Sub-elements can be used as smaller classifications of the cost elements. Each cost element must be associated with one or more sub-elements. An amount or rate is attached to each sub element.

An accounting class is a group of various General Ledger accounts which allows you to arrive at job cost, production cost and maintenance costs.

The following are different accounting classes in Oracle WIP:

1) Standard discrete
Standard discrete accounting classes can be used to group job costs for building subassemblies and finished goods on shop floor. You can define and attach this accounting classes so that you can separately value and report the costs associated with subassembly and finished goods production.

2) Asset non standard discrete
If you use non-standard discrete jobs to track production costs as assets, you can define and assign an accounting class with a type of asset non-standard. Asset non-standard discrete jobs are costed the same as standard discrete jobs. Valuation accounts are charged when material is issued to a job and final costs and variances are calculated and posted to the appropriate variance and valuation accounts when the job is closed.

3) Expense non-standard discrete
Non-standard discrete accounting classes can be used to group and report various types of non-standard production costs, such as field service repair. For example to track recurring expenses – machine maintenance or engineering projects- with non-standard jobs, you can define and assign an accounting class with a type of expense non-standard to these jobs. The valuation accounts carry the costs incurred on these expense jobs as an asset during the period and automatically writes them off to the variance accounts at period close.

4) Repetitive accounting class
Repetitive accounting classes are used to group production costs and must be assigned to each repetitive line/assembly association that is created. Every repetitive schedule for that assembly on that line uses these accounts.

5) Standard Lot based
Standard lot based jobs control the material, resources, and operations required to build an assembly and collect costs. When you build lot based jobs, the standard lot based accounting class is used to separately value and report costs associated with yielded production at each individual operation on the routing.

6) Expense non standard lot based
Expense non-standard lot based accounting class jobs control material and collects costs for miscellaneous activity. These jobs are used for expense work orders for testing, prototypes, and rework where operation yield costing is not considered. You can perform all transactions (moves, jumps, scrap, splits, and update assemblies or routings) with the exception of job merge.

7) Maintenance accounting class
Maintenance accounting classes are used to group costs for work orders used in Oracle Enterprise Asset Management (eAM) Module . For example, if you are creating work orders for plant maintenance activities, you can define your accounting classes to separately value and report the costs related to asset.

The following valuation and variance accounts are associated with each accounting class.

Valuation accounts
1) Material account
2) Material overhead
3) Resource
4) Overhead
5) Outside Processing

Variance accounts
1) Material account
2) Material overhead
3) Resource
4) Overhead
5) Outside Processing
6) Standard cost
7) Bridging
8) Expense

Standard cost account is applicable to only standard costing method and Bridging and Expense accounts are applicable to average costing method only. Rest all accounts are applicable to both standard and average costing methods.


After you log on to Oracle System Administrator, complete the following steps to set up your Oracle Applications:

Create Accounts for Implementors to Complete Setting Up
Create individual Oracle Applications accounts for users who will be completing the implementation of your Oracle Applications. Assign these users the full access responsibilities for the products they will be implementing.
Create New Responsibilities (Optional)
A responsibility in Oracle Applications is a level of authority that determines how much of an application’s functionality a user can use, what requests and concurrent programs the user can run, and which applications’ data those requests and concurrent programs can access. Oracle Applications provides a set of predefined responsibilities that you can use. You can also define your own responsibilities if the ones provided do not meet your needs.
Set Up Oracle Applications Manager
Oracle Applications Manager (OAM) allows you to configure and maintain many components of the Oracle Applications system.
Define Your Concurrent Managers (Optional)
Concurrent Processing is a feature of Oracle Applications that lets you perform multiple tasks simultaneously. Oracle Applications Concurrent Processing lets you run long, data-dependent functions at the same time as your users perform online operations. Concurrent managers are components of concurrent processing that monitor and run your time-consuming tasks without tying up your computers.
Oracle Applications automatically installs one standard concurrent manager that can run every request. You may want to take advantage of the flexibility of concurrent managers to control throughput on your system.
You can define as many concurrent managers as you need. Keep in mind, however, that each concurrent manager consumes additional memory.
You can specialize each of your concurrent managers so that they run all requests, requests submitted by a particular user, requests submitted by a particular application, or other constraints, or any combination of these constraints.
If you are using Parallel Concurrent Processing in a cluster, massively parallel, or homogeneous networked environment, you should register your Nodes and then assign your concurrent managers to primary and secondary nodes. You can spread your concurrent managers, and therefore your concurrent processing, across all
available nodes to fully utilize hardware resources.
Use the Define Concurrent Manager form to define new concurrent managers
Define Request Sets (Optional)
A request set is a group of reports or programs which you submit with one request. To define and maintain request sets, use the Request Sets form.
Specify Preferences for Oracle Workflow Notifications (Required)
The SYSADMIN user is the default recipient for some types of notifications in Oracle Applications, such as error notifications. You need to specify how you want to receive these notifications by defining the notification preference and e-mail address for the SYSADMIN user.
By default, the SYSADMIN user has a notification preference to receive e-mail notifications. To enable Oracle Workflow to send e-mail to this user, navigate to the Users window and assign SYSADMIN an e-mail address that is fully qualified with a valid domain. However, if you want to access notifications only through the Oracle
Workflow Worklist Web page, then you should change the notification preference for SYSADMIN to “Do not send me mail” in the Preferences page. In this case you do not need to define an e-mail address.
Set Up AuditTrail (Optional)
If you want to keep track of the changes made to your data by application users, you should set up AuditTrail for the relevant tables.
Defining AuditTrail for your site involves defining Audit Groups, which are groups of tables and columns for which you intend to track changes. You then define Audit Installations to instruct AuditTrail which ORACLE IDs you want to audit. Finally, you run the Audit Trail Update Tables Report, which allows your AuditTrail definitions to take effect.
Set Up Your Printers
You must define any printer types used at your site that are not shipped with Oracle Applications, then register each printer with its name as determined by your operating system.
For every custom printer type or specialized print style you define, use the Printer Drivers form to assign a printer driver to use with each print style used by a printer type Specify Your Site-level and Application-level Profile Options
Use the System Profile Values form (Profile > System) to set site-level and other profile optons..
Optionally set your Site Name profile option to your site name. Many profile options are set by AutoConfig and their values can be reviewed in Oracle Applications Manager.
Define Internationalization Options (Optional)
Optionally define settings for internationalization features.
Modify Language Prompts (Optional) : If you want to modify the field name displayed in the Translations window, you should change the Description value for the language you want to modify in the Languages window.
Modify Territory LOV Values (Optional) : If you want to modify the territory value displayed in LOVs, you should change the Description value for the territory you want to modify in the Territories window.


Oracle Applications Manager (OAM) allows administrators to manage Oracle E-Business Suite systems from an HTML console. Utilities available from OAM include Oracle Workflow Manager, Patch Wizard, and Concurrent Processing monitoring tools.
With Oracle Applications Manager, system administrators can view information on general system activity including the statuses of the database, concurrent managers and other services, concurrent requests, and Oracle Workflow processes. OAM provides a summary of configuration changes, infrastructure usage, performance, required
maintenance activities, potential security issues, status of business flows, and diagnostic test results. In addition, they can manage downtime and patching. System administrators can also start or stop services, and submit concurrent requests.
Using Oracle Workflow Manager, administrators can control Workflow system services, such background engines, the Notification Mailer, agent listeners, queue propagation, and purging obsolete Workflow data. OAM utilities are generally available from two main screens: the Applications Dashboard and Site Map
Oracle Applications Manager uses with Oracle Application Object Library’s function security model. You can create custom responsibilities and menus to control access to specific OAM features. These features can thus be directly available from the E-Business Suite Home Page.
Configuring the Login Page for Oracle Applications
Oracle Applications uses a configurable login page, which can be tailored to suit the needs of different organizations
Users log in to Oracle Applications using a client web browser. From the Oracle Applications Login page, users access the E-Business Suite Home Page, which provides a single point of access to HTML-based applications, forms-based applications, and Business Intelligence applications. Users access the Oracle Applications Login page from the following URL: http://<server:port>/OA_HTML/AppsLogin
For example, http://r121.oracleerpappsguide.com:8000/OA_HTML/AppsLogin
From this URL, you will be redirected to the central login page, “AppsLocalLogin.jsp”.
The following features are displayed in the default login page: Username field,  Password field, Login button, and the Language Picker (if more than one language is installed).
The following user interface features can be turned on or off through the Local Login Mask profile option:
 Hints for username/password
* Register URL – this link allows the user to perform self-service registration in User
Management
 * Forgot Password URL – allows the user to have a password reset
 Language Picker
 Corporate Policy message
* Oracle User Management must be installed for “Register URL” and “Forgot Password URL” to be enabled.
The ICX login page (http://server:port/OA_HTML/US/ICXINDEX.htm) redirects the user to the central login page, “AppsLocalLogin.jsp”. If, in a previous release, you customized the ICX login page previously with a custom logo, you should make a copy of the new ICX login page and replace the existing image with your custom image in the copied file. The location for the company logo is $OA_MEDIA/FNDSSOCORP.gif.
Ensure that the image is appropriately size. Also, you should change the text of the message ‘FND_ORACLE_LOGO’ in Message Dictionary to the appropriate text. The following login URL is supported, but no new features are being added to it: http://server:port/OA_HTML/jtflogin.jsp
If the Oracle Applications instance is Single Sign-On enabled, the servlet directs the user to the Single Sign-On login page.
AdminAppServer Utility
Because Release 12 is deployed in a multi-tier configuration, the security model includes authentication of application servers to the database servers they access. When this layer of security is activated, the application server passes server IDs (similar to passwords) to the database server. If the database server recognizes the server ID, it grants access to the database. The server IDs are created using a Java script called AdminAppServer.
The application server security system is by default not activated; if it you must activate it after installation, if required. The application servers are not assigned server IDs and the database servers do not check for server IDs.