This chapter covers the following topics:
You can cost all project-related manufacturing transactions, then capture these costs and transfer them to Oracle Projects. You can associate items and manufacturing business processes with specific projects, and optionally tasks, to track quantity and cost information through these business processes. Project Manufacturing costing enables you to process and cost material, labor, and associated overheads against a specific project or a group of projects for a specific customer.
Define projects and tasks in Oracle Projects. Project tasks make up the Work Breakdown Structure of a project. Projects and tasks can be referenced throughout Oracle Manufacturing Applications.
See: Work Breakdown Structure, Oracle Projects User's Guide and Overview of Projects and Tasks, Oracle Projects User's Guide.
You can use the Cost Collector to pass project-related costs from Oracle Manufacturing Applications to the Transaction Import Interface table in Oracle Projects. These transactions can then be imported from the interface table into Oracle Projects.
The Cost Collector collects costs by project, task, expenditure type, expenditure organization, and expenditure date. See: Project Cost Collector.
Task auto assignment assures that each project transaction has a task, if one has not already been assigned. Task Auto Assignment enables you to manage your manufacturing activities by project and collect manufacturing costs by different tasks.
See: Task Auto Assignment Process, Oracle Project Manufacturing User's Guide.
The cost collection manager updates the transaction information with a specified project, if required. See: Common Project Assignment, Oracle Project Management User's Guide.
Project Manufacturing makes use of all Cost Management reports.
However, if there is more than one cost group in a Project Manufacturing average organization, you should not use the following valuation reports for reconciliation purposes:
Transaction Historical Summary Report
Receiving Value Report
All Inventories Value Report/ Inventory Value Report
Elemental Inventory Value Report
Subinventory Account Value Report
Item Cost Report (also Item Cost window)
The four perpetual costing methods - Standard, Average, FIFO, and LIFO - are supported for Project Manufacturing. The cost group for all perpetual costing methods determines the inventory valuation accounts. Item unit costs are held at the cost group level for Average, FIFO, and LIFO methods. However, standard costs are held at the inventory organization level.
You can cost both project referenced and non-project referenced (common) transactions in the same organization. For example, you can define and transact both non-project or 'common' discrete jobs as well as project jobs.
For a listing of project-referenced transactions, see: Project Manufacturing Costing Transactions
You can perform the following type of inventory transactions for project-referenced inventory:
Miscellaneous Issue
Miscellaneous Receipt
Project Transfer
Borrow and Payback Transfers
Inter-organization Transfer (Direct)
Inter-Org Internal Orders (Instransit)
Cycle Count Adjustment
Physical Inventory Adjustment
Transactions between expense subinventories are not eligible for project cost collection.
You can create project jobs by assigning project and task references to jobs in the Discrete Jobs window in Oracle Work in Process. You can also implement project jobs planned in Master Scheduling/MRP and Supply Chain Planning.
You can define both standard and non-standard project jobs. You can assign different WIP accounting classes to project jobs. You can also define WIP accounting classes to be valid only for a specific cost group if you have associated the WIP class to the project cost group. Doing so makes it possible to keep the WIP costs of projects belonging to the same cost group in specific general ledger accounts. You can also track WIP resource and material transactions to the project job.
You can create project purchase requisitions and project purchase orders directly in Oracle Purchasing. You can implement project purchase orders that are planned in Master Scheduling/MRP and Supply Chain Planning. You can receive items on project purchase orders, or inspect them, and deliver them to project inventory. You can also track the status of all purchase requisitions and purchase orders for a project.
Purchasing-related transactions are the only Project Manufacturing transactions that can capture project material costs at the cost subelement level. Resource and associated overheads charged to WIP are captured at the subelement level. All other material transactions are held at the cost element level.
Cost subelement delineation makes it possible to analyze performance within labor, overhead, material, or other direct costs.
See:
Setting Up Project Manufacturing Costing
Cost Elements, Subelements, and Expenditure Types
Project Manufacturing Transactions
Project Manufacturing Inventory Valuation
Project Manufacturing Cost Variances
You can borrow material from one project and return it using the Project Borrow Payback transaction. The applicable unit cost is moved from the lending project to the borrowing project. Repayment is made to the lending project at the original (borrowed) cost when a replenishment order is received by the borrowing project. The borrowing project absorbs any cost difference between the original and replenished materials.
See: Borrow Payback, Oracle Project Manufacturing User's Guide.
Note: This check box can be enabled if only Oracle Projects is installed. It has no relation to the Project Reference Enabled check box, and it does not depend on installation of Project Management.
To set up Project Manufacturing costing
Associate Expenditure Types with Cost Subelements. See: Associating Expenditure Types with Cost Elements.
See: Overview of Expenditure Classifications, Oracle Projects User's Guide.
Associate expenditure types with cost subelements. See: Defining Material Subelements and Defining Overhead and Resources window in BOM.
Define project cost groups and associate WIP accounting classes with each project cost group. Repeat for all new projects See: Defining Project Cost Groups.
Some Project Manufacturing transactions can capture project cost only at the cost element level. Other transactions support an unlimited number of user-defined cost subelements costs at the subelement level. Cost subelement delineation is required so that you can analyze performance in terms of labor, overhead, material, or other direct costs.
The Cost Collector collects costs by project, task, and expenditure type. Associating expenditure types with cost subelements ensures that Project Manufacturing costs can be collected and transferred to Oracle Projects.
There is a many-to-one relationship between subelements in Manufacturing and expenditure types in Projects; you define these relationships at the organization level. As a result, for any resource, material, or other subelement that you use on multiple projects, the expenditure type is the same across projects. The same is true within the same project, so a resource or purchased item with two different uses in different tasks, for example, would carry the same expenditure type in both tasks. However, you may specify a different expenditure type for each subelement.
To pass detailed data from Manufacturing to Projects, each cost subelement in Manufacturing must correspond to an expenditure type in Projects. This relationship is defined at the organization level on the Resource, Overhead, and Material Subelements windows in Cost Management, and is mandatory if you selected the Project Cost Collection Enabled parameter for this organization. When you define a cost subelement, you must associate it with an expenditure type. The Cost Collector uses this expenditure type to pass the subelement's transaction cost to the appropriate project and task in transactions that cross a project and task boundary.
Cost visibility and reporting, down to the expenditure type level of detail, is available using Oracle Projects.
You can charge cost elements of an item in a project job or locator either to different valuation accounts or all to the same account in Manufacturing. Because Manufacturing passes accounting entries to General Ledger, the account detail that you define determines the level of elemental detail that you are able to see in your General Ledger. Either way, elemental cost visibility is maintained in Manufacturing and that detail is passed to Projects using expenditure types.
If project cost collection is enabled in your Inventory Organization parameters, a prerequisite to running the Cost Collector, each of the five cost elements must have two expenditure types linked to it. Users create these links in the Expenditure Types for Cost Elements window within Cost Management. These expenditure types are used when passing costs to Projects when any material transactions, except those related to purchasing, occur in Manufacturing.
Of the two expenditure types for each cost element, one is used to hold the value of transfers out of projects, the other to hold the value of transfers into projects. Because expenditure types are for a specific use, you may want to choose those types types that are not associated with any cost subelement.
Related Topics
Associating Expenditure Types with Cost Elements
Inventory under Project Manufacturing costing is valued based on the organization's costing method.
For further information about project cost groups and their function, see: Project Cost Groups and Defining Project Cost Groups.
Under Project Manufacturing costing, cost variances are generated in a similar fashion to costing for non-project related transactions. See: Average Cost Variances.
There are, however, a couple of important differences. quantity in the specified inventory organization is driven negative. Under Project Manufacturing costing, cost variances are generated when the total item quantity across all subinventories in a project cost group is driven negative.
Another difference - cost variances generated in non-Project Manufacturing organizations, the organization level Cost Variance account is used. Under Project Manufacturing costing, variances occurring in any project within a cost group are charged to a Cost Variance account defined for that cost group.
Borrow payback variance accounts are set up in the Cost Group window to record variances generated by borrow payback transactions.
See: Borrow Payback, Oracle Project Manufacturing User's Guide.
Invoice Price Variance is the difference between the purchase price and the invoice price paid for a purchase order receipt. Invoice price variances are generated when the invoice is processed and matched to the PO line items. Upon invoice approval, Oracle Payables automatically records this variance to both the invoice price variance and exchange rate variance accounts. IPV is determined and recorded the same under project and non-project costing.
Note: The application prevents IPV transfers to Inventory Valuation for the Landed Cost Management (LCM) enabled parent PO receipts.
Related Topics
Inventory Average Cost Transactions
In Oracle Project Manufacturing, you can have organizations which concurrently manufacture for projects and non-project customer orders. For proper management control purposes, item costs and charges for non-project orders are maintained and tracked distinctly separate from projects. Standard cost organizations have one item cost.
Using Project Manufacturing, you can have many projects active at any one time. You can also have items in common (non-project) inventory at the same time. Using project cost groups, an item may have a different cost in different projects as well as a cost in common inventory, all within the same organization. Item costs can apply to a single project if each project belongs to a distinct cost group or apply to a group of projects assigned to the same cost group. Items in common inventory belong to the organization's default cost group. Items in the organization's default cost group are costed separately from items in projects.
When internal order intransit shipments and internal requisition intransit receipts are performed, items are transferred using the cost from the sending cost group, not the organization's default cost group.
The Project Cost Collector transfers the costs to the Transaction Import Interface table in Oracle Projects, for import into Oracle Projects when material transactions:
Cross a project boundary (i.e. from project to non-project, from non-project to project, and between two different projects)
or
Cross the task boundary of the same project
For transactions within the same project, if no specific task is entered, it is assumed to be a transaction within the same task, and hence transfer to Projects is not required.
Upon transfer by the Project Cost Collector, Projects either:
Increments project cost when material is moved into a project-related entity from a non-project-related entity (e.g. locator, work order, etc.)
Decrements project cost when material is moved out of a project-related entity into a non-project-related entity
Decrements the From project and task and increments the To project and task when a transaction moves material between two projects or tasks
The following table summarizes some important transactions, whether they are or are not transferred to Oracle Projects, their respective debits and credits, and the cost used in the transaction:
Unless otherwise stated, the cost specified for the debit side of the transaction applies also to the credit side.
Note: MOH stands for material overhead. For information on material overhead charges, see Material Overhead Application.
The following tables present Purchasing, Inventory, or Order Management Project Referenced Transactions.
Note: The following accounts are the default accounts for Project Manufacturing Costing. If Subledger Accounting (SLA) is enabled and SLA rules are customized, then the default accounts are not used.
Account and Cost | Debit | Credit | Transfer to Projects |
---|---|---|---|
Receiving Inspection at PO Cost | XX | - | No |
Inventory A/P Accrual | - | XX |
Account and Cost | Debit | Credit | Transfer to Projects |
---|---|---|---|
Cost Group Material at PO Cost | XX | - | Yes |
Receiving Inspection | - | XX |
Account and Cost | Debit | Credit | Transfer to Projects |
---|---|---|---|
Receiving Inspection at PO Cost | XX | - | Yes |
Inventory A/P Accrual | - | XX | |
Cost Group Material at PO Cost | XX | - | |
Receiving Inspection | - | XX |
Account and Cost | Debit | Credit | Transfer to Projects |
---|---|---|---|
Deferred Cost of Goods Sold at Current Cost (in Cost Group) | XX | - | No |
Cost Group Valuation | - | XX |
Receipt into Project Locator | |||
---|---|---|---|
Account and Cost | Debit | Credit | Transfer to Projects |
Cost Group Valuation at Current (in Project Cost Group) or User-specified Cost | XX | - | Yes |
User-specified account | - | XX |
Receipt from Project Locator | |||
---|---|---|---|
Account and Cost | Debit | Credit | Transfer to Projects |
User Specified account at Current (in Project Cost Group) or User-specified Cost | XX | - | Yes |
Cost Group Valuation | - | XX |
No entries | - | - |
Account and Cost | Debit | Credit | Transfer to Projects |
---|---|---|---|
Cost Group Valuation (in Receiving Project) at Current Average Cost (in Cost Group of Sending Project) | XX | - | Yes |
Cost Group Valuation or Expense (in Sending Project) | - | XX |
Account and Cost | Debit | Credit | Transfer to Projects |
---|---|---|---|
Cost Group Valuation or Expense (in Receiving Project) at Current Cost in Cost Group (of Sending Project) | XX | - | Yes |
Cost Group Valuation (in Sending Project) | - | XX |
Account and Cost | Debit | Credit | Transfer to Projects |
---|---|---|---|
Organization Valuation at Current Cost (in Project Cost Group) | XX | - | Yes |
Cost Group Valuation (in Sending Project) | - | XX |
Account and Cost | Debit | Credit | Transfer to Projects |
---|---|---|---|
Cost Group Valuation (in Sending Project) at Current Cost in default Cost Group | XX | - | Yes |
Organization Valuation | - | XX |
Account and Cost | Debit | Credit | Transfer to Projects |
---|---|---|---|
Inventory Adjustment at Current Cost in Cost Group | XX | - | No |
Cost Group Valuation | - | XX |
Account and Cost | Debit | Credit | Transfer to Projects |
---|---|---|---|
Cost Group Valuation at Current Cost in Cost Group | XX | - | No |
Inventory Adjustment | - | XX |
Account and Cost | Debit | Credit | Transfer to Projects |
---|---|---|---|
Cost Group Valuation at User-Defined Cost Increase/Decrease | XX | - | No |
Inventory Adjustment | - | XX |
Account and Cost | Debit | Credit | Notify Projects |
---|---|---|---|
No entries | - | - | No |
Account and Cost | Debit | Credit | Notify Projects |
---|---|---|---|
WIP Inventory at Current Cost (in Project Cost Group) | XX | - | No |
Cost Group Valuation or Expense | - | XX |
Account and Cost | Debit | Credit | Notify Projects |
---|---|---|---|
WIP Inventory at Current Cost (in Project Cost Group) | XX | - | Yes |
Cost Group Valuation or Expense | - | XX |
Account and Cost | Debit | Credit | Notify Projects |
---|---|---|---|
Cost Group Valuation at Cost | XX | - | Yes |
Organization Valuation | - | XX | |
WIP Inventory at Current Cost (in Project Cost Group) | XX | - | |
Cost Group Valuation | - | XX |
Account and Cost | Debit | Credit | Notify Projects |
---|---|---|---|
WIP Resource at Actual Employee Rate or User-Defined Cost | XX | - | Yes |
Resource Absorption | - | XX |
Account and Cost | Debit | Credit | Notify Projects |
---|---|---|---|
WIP Resource at User-Defined Cost | XX | - | Yes |
Resource Absorption | - | XX |
Account and Cost | Debit | Credit | Notify Projects |
---|---|---|---|
WIP Overhead Valuation at User-Defined Cost or Rate | XX | - | Yes |
Overhead Absorption | - | XX |
Account and Cost | Debit | Credit | Notify Projects |
---|---|---|---|
WIP Outside Processing at Purchase Order Cost | XX | - | Yes |
Outside Processing Absorption | - | XX |
Note: Notify Projects: Yes
Account and Cost | Debit | Credit | Notify Projects |
---|---|---|---|
Scrap at Calculated Scrap Value | XX | - | No |
WIP Accounting Class Valuation | - | XX |
Account and Cost | Debit | Credit | Notify Projects |
---|---|---|---|
WIP Accounting Class Valuation | XX | - | No |
Scrap at Calculated Scrap Value | - | XX |
Account and Cost | Debit | Credit | Notify Projects |
---|---|---|---|
Cost Group Valuation at User-Defined or System Calculated + MOH | XX | - | Yes (for MOH amount only) |
WIP Accounting Class Valuation | - | XX | |
Material Overhead Absorption | - | XX |
Account and Cost | Debit | Credit | Notify Projects |
---|---|---|---|
WIP Accounting Class Variance | XX | - | No |
WIP Accounting Class Valuation | - | XX |
Material overhead application is essentially the same for Project Manufacturing, with one difference in the accounting transaction. The account debited is for the project cost group, rather than the organization, as in non-project average costing.
The accounting entry that follows applies to:
Material overhead on deliveries from receiving inspection
Complete assemblies from WIP
Receipt from Intransit (Standard or Project Org) into Project Org (FOB Receipt)
Account | Debit | Credit |
---|---|---|
Cost group MOH account @ MOH cost | XX | - |
Material overhead absorption account | - | XX |
Define material overhead subelements for projects in the same way as in non-project cost organizations. You can define as many material overhead subelements as desired and base their charging in a variety of ways: by item, activity, or lot, or based on total value.
Related Topics
Defining Material Overhead Defaults
You can define material overhead defaults without charge. Defaults may be created to apply at the organization level or at an item category level.
The Project Cost Collector collects the costs of project-related organization's default cost group transactions, then passes these costs by project, task, and expenditure type to the Transaction Import Interface table in Oracle Projects. These transactions can then be imported into Oracle Projects.
You can view and resubmit project transactions that fail to transfer using the Cost function View Material Transactions window.
Prerequisites
Perform project-related cost transactions. See: Project Manufacturing Costing Transactions.
When there is a separate reporting ledger, the Cost Collector collects both functional and reporting currency information. This information is passed to Projects and made available for reporting. A transaction (such as PO, Direct IO) created in a currency other than the functional currency of the organization, is transferred to Projects using the functional currency. For inventory and WIP transactions, the accounting currency is the same as the functional currency.
The Cost Collector collects all Project Manufacturing-related costs and inserts them into the Transaction Import Interface Table of Oracle Projects. Each of these records includes the project, task, and expenditure type reference required by Oracle Projects.
The Cost Collector derives the accounting information from the manufacturing subledger unless the accounting extension is used to customize project accounts. See: Client Extensions.
Note: If you perform Inventory or other manufacturing transactions for a project owned by an operating unit other than the operating unit of the Inventory organization, then you must run the Cost Collector from a responsibility that has the profile option (MO: Operating Unit profile), set to the project owning operating unit.
If Cost Element to Expenditure Type Association is not set up, and the profile option Project Miscellellaneous Transaction Expenditure Type is user defined, then cost collection will take place only for Project Miscellaneous transactions.
Cost collection errors out for any organization that has the cost collection feature turned off. You can turn on Cost Collection if Oracle Projects is installed.
Records in the Transaction Import Interface Table can then be imported into Oracle Projects using Transaction Import in Oracle Projects. See: Transaction Import, Oracle Projects User's Guide.
To collect project related cost
Navigate to the Project Cost Transfer window. Submit a request for the Cost Collection Manager. The Parameters window appears.
Specify the project cost collection time fence, the Number of Days to Leave Costs Uncollected, by entering a whole number of days.
For example, suppose today is Thursday and project costs were collected up through Friday of the previous week. If you enter 4 as the Number of Days, costs will be collected for Saturday and Sunday.
If there are uncosted transaction records in the MTL_MATERIAL_TRANSACTIONS table within the specified time fence, then project costs for these transactions are not collected. You can check to see if transactions are uncosted, as indicated by the costed indicator, through the Material Transactions window. See: Viewing Material Transactions, Oracle Inventory User's Guide.
Uncosted transactions and transactions that lack complete information are flagged Error.
Choose Submit to run the request.
Related Topics
Transaction Import, Oracle Projects User's Guide.
You have the option, at the Inventory organization level, to post Project Manufacturing transactions to Oracle General Ledger, either from Oracle Manufacturing or from Oracle Projects. When you select the option to post the General Ledger in Oracle Projects, you can use Projects Burden Schedules to apply overhead to Project Manufacturing transactions. If you select this option, and continue to apply overhead in Manufacturing, then the overhead amount is imported into Projects as raw (not burden) cost.
If you select the option to post the GL from Projects, then only the transactions that are cost collected are posted to the General Ledger. Transactions that are not cost collected include:
Sales order issues
Work in Process component issues from the same project/task as the project/task on the WIP job
Assembly completions
Average and standard cost updates
Job close and average cost variances
Scrap transactions
This feature is enabled at the Inventory organization level by setting parameters in the Project Manufacturing Parameters window in the Costing tabbed region. You can select these options for an existing Project Manufacturing organization if there are no cost transactions for the open period. Select one of the options for each parameter:
Manufacturing: Transactions are transferred to Oracle Projects as GL accounted and burdened. Non-manufacturing transactions are posted to General Ledger from Oracle Projects.
Projects: All Project Manufacturing and non-manufacturing project transactions are posted to General Ledger from Oracle Projects.
Use AutoAccounting: All accounts are derived using the Accounting Rules Engine in Oracle Projects. Inventory transactions are transferred to Projects as Inventory with No Accounts. Work in Process transactions are transferred as WIP with No Accounts.
Send Accounts to PA: Cost Group and WIP Accounting Class valuation accounts are transferred to Projects. Inventory transactions are transferred to Projects as Inventory with Accounts. Work in Process transactions are transferred as WIP with Accounts.
You have the option at the Inventory organization level, to transfer WIP Resource employee transactions to Oracle Projects as WIP Straight Time. If you select this option, you can include WIP Straight Time hours in Oracle Projects summarization of hours for billing calculations.
You set up this feature at the Inventory organization level in the Project Manufacturing Parameters window in the Costing tabbed region. Enable this feature by checking the parameter box for:
Additionally, if the Account Option parameter is set to one of the selections, the transaction source type has one of the following values:
Use AutoAccounting: WIP Resource transactions with employee name and number are transferred to Oracle Projects as WIP Straight Time with No Accounts.
Send Accounts to PA: WIP Resource transactions with employee name and number are transferred to Oracle Projects as WIP Straight Time with Accounts.