Preface

Intended Audience

Welcome to Release 12.2 of the Oracle Process Manufacturing Cost Management User's Guide.

This guide assumes that you have working knowledge of your business area's processes, tools, principles, and customary practices. It also assumes that you are familiar with Oracle Process Manufacturing. If you have never used Oracle Process Manufacturing, we suggest you attend one or more of the Oracle Process Manufacturing training classes available through Oracle University.

See Related Information Sources for more Oracle Applications product information.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customer access to and use of Oracle support services will be pursuant to the terms and conditions specified in their Oracle order for the applicable services.

Structure

1  Overview

This topic provides an overview of Oracle Process Manufacturing (OPM) Cost Management.


2  Cost Management Command Center
3  Setting Up

This topic includes procedures and values that you must define before using the application. These basic setups are required regardless of whether you want to use the standard, actual, or lot cost methods. This topic includes setting up in other applications, profile options, and setting the cost calendar and costing periods, cost analysis codes, cost type codes, and cost component classes.

A detailed description on setting up and calculating standard, actual, and lot costs are provided in their topic discussions.


4  Using Standard Costing

This topic describes how to define and use standard costs for production items. These costs include raw materials, overheads, and other costs associated with production. Once defined, you can propagate those costs for use by other organizations within your legal entity and determine the appropriate costs to use for accounting.

Individual ingredient and resource costs must be rolled-up to reflect the total standard cost of the item that is produced. This procedure is detailed in the Standard Cost Rollup discussion.


5  Using Actual Costing

This topic describes how to setup and use actual cost.


6  Using Lot Costing

This topic describes how to set up and use lot costing.


7  OPM - Landed Cost Management Integration
8  Copying Costs

This topic describes copying item, overhead, and resource costs set up for one organization, calendar and period, and category to another period and inventory organization or to all periods and inventory organizations. You can use the copy processes to quickly replicate the cost data setup across several periods and several organizations rather than creating them one at a time in each periods and organizations that can be very time consuming. The copy programs let you copy the costs for a set of items or set of items belonging to a range of Item Categories or automatically modify the copied costs by a percentage or flat value providing additional flexibility in establishing your costs.


9  Period-End Cost Processing

This topic explain how to update (book) item component costs in preparation for export to the proper general ledger accounts. The actual export to the general ledger requires an interface with Oracle General Ledger. This topic provides an outline for period-end processing of standard component costs and actual component costs.


10  Cost Management Reports

This topic describes the available costing reports. Reports are available through the Application's Standard Report Submission window.


11  Accounting Setup

The following chapter describes the accounting setup done in Oracle Subledger Architecture.


12  Accounting Processes and Distributions

This chapter describes the subledger account distribution.


A  Navigator Paths

This topic provides the default navigation path for Accounting Setup and the cost management profile options.


Glossary

Related Information Sources

Integration Repository

The Oracle Integration Repository is a compilation of information about the service endpoints exposed by the Oracle E-Business Suite of applications. It provides a complete catalog of Oracle E-Business Suite's business service interfaces. The tool lets users easily discover and deploy the appropriate business service interface for integration with any system, application, or business partner.

The Oracle Integration Repository is shipped as part of the Oracle E-Business Suite. As your instance is patched, the repository is automatically updated with content appropriate for the precise revisions of interfaces in your environment.

Do Not Use Database Tools to Modify Oracle E-Business Suite Data

Oracle STRONGLY RECOMMENDS that you never use SQL*Plus, Oracle Data Browser, database triggers, or any other tool to modify Oracle E-Business Suite data unless otherwise instructed.

Oracle provides powerful tools you can use to create, store, change, retrieve, and maintain information in an Oracle database. But if you use Oracle tools such as SQL*Plus to modify Oracle E-Business Suite data, you risk destroying the integrity of your data and you lose the ability to audit changes to your data.

Because Oracle E-Business Suite tables are interrelated, any change you make using an Oracle E-Business Suite form can update many tables at once. But when you modify Oracle E-Business Suite data using anything other than Oracle E-Business Suite, you may change a row in one table without making corresponding changes in related tables. If your tables get out of synchronization with each other, you risk retrieving erroneous information and you risk unpredictable results throughout Oracle E-Business Suite.

When you use Oracle E-Business Suite to modify your data, Oracle E-Business Suite automatically checks that your changes are valid. Oracle E-Business Suite also keeps track of who changes information. If you enter information into database tables using database tools, you may store invalid information. You also lose the ability to track who has changed your information because SQL*Plus and other database tools do not keep a record of changes.