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.
WIP accounting classes
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.
Share this:
Encumbrance / Budgetory Control in Oracle Applications
Navigation: AP or PO —-> Setup–> Organizations –> Financial Options.
In order to use encumbrance accounting or budgetary control, you must install Payables, Purchasing, and General Ledger modules. You may go to encunbrance region to enable encumbrance accounting and to specify the default encumbrance types which Payables module assigns to your invoices, and Purchasing module assigns to your requisitions and purchase orders.
If you enable encumbrance accounting or budgetary control, Purchasing creates
encumbrances when you reserve funds for a requisition or purchase order. If you use the perpetual accrual method in Purchasing, it reverses the purchase order encumbrances when you inspect, accept, and deliver the units. If you are using the periodic accrual method in Purchasing, Payables reverses the purchase order encumbrances when you create accounting entries for invoices. Payables module creates encumbrances when there is a variance between a matched invoice and the purchase order to which it is matched, and when the invoice encumbrance type is different from the Purchasing encumbrance type.
Oracle EBS provides two predefined encumbrance types that you can use to identify requisition, purchase order, and invoice encumbrances:- Commitment and
Obligation. You can define additional encumbrance types in Oracle General Ledger module in the Encumbrance Types window.
1) Use Requisition Encumbrance
You may enable this option to encumber funds for requisitions. If you enable this option, Purchasing creates journal entries and transfers them to General Ledger to encumber funds for purchase requisitions.
If you enable Use Requisition Encumbrance, you must select an encumbrance type by which you can identify your requisition encumbrance journal entries. Purchasing assigns this encumbrance type to the encumbrance journal entries it creates for purchase requisitions. If you enable Use Requisition Encumbrance, you can indicate whether you want requisition preparer to have the option to reserve funds. If you do not enable this option, only requisition approvers will have the option to reserve funds.
2)Use PO Encumbrance
Enable this option to encumber funds for purchase orders, purchase order and receipt matched invoices, and basic invoices (not matched). If you enable this option, Purchasing encumbers funds for purchase orders and Payables encumbers funds for variances during Payables Invoice Validation for purchase order and receipt matched invoices. If you enable this option and enter a non-purchase order matched invoice, Payables will encumber funds for it during Payables Invoice Validation. All Payables encumbrances are reversed when you create accounting entries. If you enable Use Requisition Encumbrance, you must also enable this option.
If you enable Use Purchase Order Encumbrance, select a purchase order encumbrance type by which you can identify your purchase order encumbrance journal entries. Purchasing assigns this encumbrance type to the encumbrance journal entries it creates for purchase requisitions and purchase orders. If you use purchase order encumbrance, select an invoice encumbrance type by which you can identify your invoice encumbrance journal entries. Payables module assigns this encumbrance type to the encumbrance journal entries that it creates. It is recommended that you use an encumbrance type different from the Purchasing encumbrance type so you can identify invoice encumbrances
Share this:
Sys Administrator Setup Tasks
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.
Share this:
Oracle Applications Manager
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.
Share this:
Restricting Access to Responsibilities Based on User’s Web Server
The server trust level indicates the level of trust associated with the Web server.
Currently, three trust levels are supported: 1) administrative, 2) normal, and 3) external.
Web servers marked as “administrative” are typically those used exclusively by system administrators. These servers are considered secure and may contain highly sensitive information. Servers marked as “normal” are those used by employees within a company’s firewall. Users logging in from normal servers have access to only a limited
set of responsibilities. Lastly, servers marked as “external” are those used by customers or employees outside of a company’s firewall. These servers have access to an even smaller set of responsibilities.
Setting the Server Trust Level for a Server
To assign a trust level to a Web server, set the Node Trust Level profile option. The Node Trust Level profile option uses the Server profile hierarchy type, meaning that the value of the profile depends on the particular middle-tier server accessing the profile.
This profile option can be set to either 1, 2, or 3, with the following meanings.
• 1 – Administrative
• 2 – Normal
• 3 – External
To avoid having to set the Node Trust Level profile option for every Web server, you may wish to set it to a default level of trust at the site level, such as level 1. If no value is set for the Node Trust Level profile option for a Web server, the Web server is assumed to have a trust level of 1 (Administrative).
Restricting Access to a Responsibility
To restrict access to a responsibility, set the security-based Responsibility Trust Level (internal name APPL_SERVER_TRUST_LEVEL) profile option value for that responsibility to be the number 1, 2, or 3. Setting this profile value ensures that only Web servers with the same or greater privileged trust level may access that responsibility.
Like the Node Trust Level profile option, the default value for the Responsibility Trust Level is 1.
When fetching the list of valid responsibilities for a user, Oracle Applications checks to find only responsibilities with a Responsibility Trust Level value greater than or equal to the Web server’s Node Trust Level. In this way, a responsibility with Responsibility Trust Level set to 1 would only be available if the Web server has the Node Trust Level set to 1 as well. A responsibility with Responsibility Trust Level set to 2 would only be available if the Web server has Node Trust Level set to either 1 or 2.
Share this: