This chapter describes how to create and maintain capital projects in Oracle Projects. It provides a brief overview of capital projects and explains how to create, place in service, adjust, and account for assets and retirement costs in Oracle Projects.
This chapter covers the following topics:
Using capital projects, you can define capital assets and capture construction-in-process (CIP) and expense costs for assets you are creating. When you are ready to place assets in service, you can generate asset lines from the CIP costs and send the lines to Oracle Assets for posting as fixed assets.
You can also define retirement adjustment assets and capture cost of removal and proceeds of sale amounts (collectively referred to as retirement costs, retirement work-in-process, or RWIP) for assets you are retiring that are part of a group asset in Oracle Assets. When your retirement activities are complete, you can generate asset lines for the RWIP amounts and send the lines to Oracle Assets for posting as adjustments to the accumulated depreciation accounts for the group asset that corresponds to each asset.
You use capital projects to capture the costs of capital assets you are building, installing, or acquiring. You also use capital projects to create retirement adjustment assets that you associate with a group asset in Oracle Assets. You use a retirement adjustment asset to capture the costs of removing, abandoning, or disposing of assets you want to retire. You can set up capital projects to capture capital asset costs only, retirement costs only, or to capture both capital asset costs and retirement costs.
You define and build capital assets in capital projects using information specified in the project work breakdown structure (WBS). You define asset grouping levels and assign assets to the grouping levels to summarize the CIP costs for capitalization.
You can review and adjust capital project costs before and after capitalization. For example, you can allocate costs collected under common tasks to multiple CIP assets before you place them in service. You can also account for additional costs incurred after capitalization, since Oracle Projects allows you to place assets in service before completion of a project.
When a CIP asset is ready to be placed in service, you send the capital project amounts to Oracle Assets as asset lines. Oracle Assets places the asset lines in a holding area where your fixed assets department can post the capital costs in Oracle Assets as fixed assets. You can review detail transactions associated with the asset lines in Oracle Projects and Oracle Assets. If necessary, you can reverse capitalize an asset in a capital project.
You capture retirement costs in a capital project by recording cost of removal and proceeds of sale amounts to a task that is designated as a retirement cost task. To distinguish cost of removal and proceeds of sale amounts, you must enter proceeds of sale amounts using expenditure types that you define to specifically classify these amounts. Oracle Projects automatically classifies amounts for all other expenditure types as cost of removal. For more information, see: Defining Proceeds of Sale Expenditure Types, Oracle Projects Implementation Guide.
Important: When you record proceeds of sale in an expenditure batch, enter the proceeds amounts as negative (credit) values.
To associate retirement costs with a group asset in Oracle Assets, you create a retirement adjustment asset in the capital project and identify it with a specific group asset. As with capital assets, you define asset grouping levels and assign retirement adjustment assets to the grouping levels to summarize the retirement cost amounts for posting to Oracle Assets. For more information, see: Creating a Retirement Adjustment Asset.
When retirement activities are complete, you generate asset lines for the retirement cost amounts and send the lines to Oracle Assets for posting as adjustments to the accumulated depreciation accounts for the group assets. To communicate notice of an asset retirement to Oracle Assets, you can optionally initiate retirement requests in Oracle Projects that are automatically passed to Oracle Assets.
Important: To use Oracle Projects retirement cost processing windows and features, the value of the site-level profile option PA: Retirement Cost Processing Enabled must be set to Yes. For more information, see: Profile Options in Oracle Projects, Oracle Projects Implementation Guide.
The following illustration shows the processing flow for capital projects.
Capital Projects Processing Flow
As illustrated in the diagram Capital Projects Processing Flow, you can charge expenditures for CIP and RWIP amounts to capital projects in Oracle Projects. You can collect supplier costs for your capital projects in Oracle Purchasing and Oracle Payables. You run the process PRC: Interface Supplier Costs in Oracle Projects to interface project-related receipt accrual cost from Oracle Purchasing and project-related supplier costs from Oracle Payables to Oracle Projects. Oracle Projects, Oracle Purchasing, and Oracle Payables create accounting entries for CIP, RWIP, and expensed cost in Oracle Subledger Accounting. In addition, Oracle Projects creates accounting in Oracle Subledger Accounting for supplier cost adjustments that you make in Oracle Projects. Oracle Subledger Accounting transfers the accounting entries to Oracle General Ledger.
Oracle Payables uses the Mass Additions Create process to send non-CIP assets to Oracle Assets. If the non-CIP asset is associated with a capital project, then Oracle Projects sends the asset and asset cost to Oracle Assets.
When you are ready to place a CIP asset in service, you can send the assets and associated CIP asset lines to Oracle Assets to become fixed assets. When you are ready to retire an asset in Oracle Assets, you can send the retirement adjustment asset and associated RWIP asset lines to Oracle Assets and post the lines as group depreciation reserve account adjustments. Oracle Assets creates accounting in Oracle Subledger Accounting to clear CIP and RWIP accounts, and post the asset costs to the appropriate asset or group depreciation reserve account. Oracle Subledger Accounting transfers the accounting entries to Oracle General Ledger.
Related Topics
Integrating with Oracle Purchasing and Oracle Payables (Requisitions, Purchase Orders, and Supplier Invoices), Oracle Projects Fundamentals
Integrating with Oracle General Ledger, Oracle Projects Fundamentals
Integrating with Oracle Assets
Integrating with Oracle Subledger Accounting, Oracle Projects Fundamentals
Specifying a Retirement Date for Retirement Adjustment Assets
Creating and Preparing Asset Lines for Oracle Assets
Sending Asset Lines to Oracle Assets
Processing Pre-Approved Expenditures
Overview of AutoAccounting, Oracle Projects Implementation Guide
Creating and Preparing Asset Lines for Oracle Assets
When you create a purchase order for a capital project in Oracle Purchasing, you can enter a project, task number, and expenditure type for each project-related distribution line. You match this purchase order to an invoice in Oracle Payables, and then send the appropriate lines to Oracle Projects.
You can use the asset category associated with an inventory item to allocate costs to your assets. In Oracle Purchasing, you can associate an asset category with an inventory item and create a purchase order for the inventory item. You can charge the purchase order line to your capital project when the destination type of the distribution line is Expense. After you interface the supplier costs to Oracle Projects, you generate asset lines for your capital project. Oracle Projects assigns the cost to the asset on the project that has the same asset category as the inventory item, if one exists. If more than one asset with the same asset category exists on the project, Oracle Projects uses the asset allocation method for the project to distribute the costs among those assets.
If you assign purchase order distribution lines to asset clearing accounts instead of projects, Oracle Payables matches the purchase order to an invoice and sends the lines to Oracle Assets using the Mass Additions Create process.
If both a project and an asset clearing account are used in the distribution line, the following occurs:
If the project is a capital project:
Oracle Payables posts the costs to the asset clearing account and the costs remain there until you place the asset in service in Oracle Projects.
You can send the costs to Oracle Projects after you validate the invoice and create accounting for the invoice in Oracle Payables.
You cannot send costs to Oracle Assets from Oracle Payables when you run the Mass Additions Create process.
If the project is a contract or indirect project:
Oracle Payables posts the costs to the asset clearing account and, if you have sent the costs to Oracle Projects, Oracle Assets posts the costs to an asset cost account when you create the subledger accounting for the asset. Oracle Subledger Accounting transfers the accounting to Oracle General Ledger.
You can send the costs to Oracle Projects after you validate the invoice and create accounting for the invoice in Oracle Payables.
You can send costs to Oracle Assets from Oracle Payables when you run the Mass Additions Create process.
A distribution line can have both a project and an asset clearing account only if the Account Generator process is set up to create the asset clearing account as the account segment, or if you enter the distribution line manually.
The procedure for sending supplier invoice lines to Oracle Assets depends on whether or not the lines are associated with a capital project.
CIP and RWIP Lines: You cannot send supplier invoice lines directly from Oracle Payables to Oracle Assets if the invoice lines are associated with a capital project and are CIP or RWIP lines. Instead, in Oracle Payables you must do the following:
Create the distribution lines on a supplier invoice
Validate the invoice and create accounting for the invoice in Oracle Payables.
In Oracle Payables, your Account Generator setup determines the default accounts for the invoices. The usual practice is to charge costs for capital projects to asset clearing accounts.
Interface those lines to Oracle Projects
Then, in Oracle Projects, place your CIP assets in service, specify retirement dates for any retirement adjustment assets, and interface the costs to Oracle Assets.
Expense Lines: You can send distribution lines from Oracle Payables directly to Oracle Assets using the Mass Additions Create process. See: Mass Additions Create Program, Oracle Payables User's Guide.
You can send supplier invoice lines that are associated with contract or indirect projects directly from Oracle Payables to Oracle Assets. To do so, use the Mass Additions Create process. See: Mass Additions Create Program, Oracle Payables User's Guide.
Your Account Generator setup in Oracle Payables determines the default accounts for the invoices. The usual practice is to charge costs for contract and indirect projects to an asset clearing account.
You can enter expense reports in Oracle Payables, or enter expense reports in Oracle Internet Expenses and import them in Oracle Payables, that charge project-related expenses to projects. Oracle Payables charges capitalizable expenses for capital projects to a CIP or a RWIP account. Oracle Projects interfaces project-related expense report costs from Oracle Payables.
See also, Integrating Expense Reports from Oracle Payables and Oracle Internet Expenses.
You can enter labor, asset usage, and miscellaneous transactions for your capital projects in Oracle Projects. You can set up Oracle Projects to calculate and record capitalized interest for CIP assets that require an extended amount of time to prepare for their intended use. The Distribute Labor and Distribute Usage and Miscellaneous Costs processes charge the capital project costs to a CIP or RWIP account. Your AutoAccounting setup generates default accounts.
If you define your own detailed accounting rules in Oracle Subledger Accounting, then Oracle Subledger Accounting overwrites default accounts, or individual segments of accounts, that Oracle Projects derives using AutoAccounting. You must ensure that the subledger accounting rules post the accounting to the appropriate CIP or RWIP accounts.
Oracle Projects is the subsidiary ledger for your CIP and RWIP accounts. You can review the details for your CIP and RWIP accounts by querying your capital projects in Oracle Projects.
You enter a date placed in service for the CIP assets that are completed for a capital project. Then, you can run the Generate Asset Lines process, which uses the grouping method and levels you define to summarize all costs (supplier invoice, labor, expense reports, usages, and miscellaneous transactions) into asset lines. You associate these asset lines with one or more assets and send the lines to Oracle Assets to become fixed assets.
You run the Interface Assets process to send asset lines from Oracle Projects to Oracle Assets. This process merges the asset lines into one mass addition line for each asset. The mass addition line appears in the Prepare Mass Additions Summary window in Oracle Assets as a merged parent with a cost amount of zero and a status of MERGED. The line description is identical to the description of the supplier invoice expenditure item in Oracle Projects.
The following table shows an example of asset lines in Oracle Assets for an asset interfaced from Oracle Projects. When you submit the Post Mass Additions process, Oracle Assets assigns the same asset number to these lines. See: Group Supplier Invoices in Project Types: Capitalization Information, Oracle Projects Implementation Guide.
Queue | Description | Cost | Merge Parent | Category |
---|---|---|---|---|
POST | CELL RADIO | 0.00 | Yes | EQUIPMENT. TRANSMISSION |
MERGED | COMPUTER SERVICES | 3,442.00 | No | EQUIPMENT. TRANSMISSION |
MERGED | OTHER EXPENSES | 1,150.00 | No | EQUIPMENT. TRANSMISSION |
MERGED | LABOR | 22,332.00 | No | EQUIPMENT. TRANSMISSION |
MERGED | MATERIAL | 19,251.00 | No | EQUIPMENT. TRANSMISSION |
If you completely defined the asset in Oracle Projects and it is ready for posting, then Oracle Assets places the mass addition in the POST queue. If the asset definition is not complete, then Oracle Assets places the mass addition in the NEW queue. To complete the asset definition, you must enter the additional information in the Prepare Mass Additions window. After the asset definition is complete, you can update the queue status to POST. You do not need to change the queue status for lines with a status of MERGED.
Use the Post Mass Additions process to create fixed assets from your mass addition lines. Oracle Assets creates subledger accounting entries to the appropriate CIP and asset cost accounts. For CIP assets, the CIP account comes from the asset lines generated in Oracle Projects and the asset account comes from the asset category associated with the asset. Oracle Subledger Accounting transfers the final accounting entries to Oracle General Ledger.
The process flow for sending retirement costs to Oracle Assets is similar to that for placing CIP assets in service and sending CIP asset lines to Oracle Assets. When retirement activities are complete and you are ready to interface the retirement cost amounts to Oracle Assets, you must specify a date retired and ensure that a valid Oracle Assets group asset number is specified for the retirement adjustment asset.
You submit the Generate Asset Lines process to create retirement cost lines for each retirement adjustment asset and expenditure type grouping (cost of removal and proceeds of sale). After you generate asset lines, you submit the Interface Assets process to post the retirement adjustment asset lines to the accumulated depreciation accounts for each group asset.
You use AutoAccounting to define the default accounting for your project costs in Oracle Projects. For capital projects, you must define AutoAccounting to account for CIP, RWIP, and expensed costs.
If you define your own detailed accounting rules in Oracle Subledger Accounting, then Oracle Subledger Accounting overwrites default accounts, or individual segments of accounts, that Oracle Projects derives using AutoAccounting. You must ensure that the subledger accounting rules post the accounting to the appropriate CIP or RWIP accounts.
When you use Oracle Projects to track your capital projects, Oracle Projects acts as a subsidiary ledger for CIP and RWIP costs, and Oracle Assets acts as a subsidiary ledger for the capitalized asset costs and the accumulated depreciation account adjustments.
As you charge costs to a capital project, you generate cost accounting events and create accounting for the events in Oracle Subledger Accounting. Oracle Subledger Accounting transfers the accounting entries to Oracle General Ledger. After you interface the costs to Oracle Assets, Oracle Assets creates accounting entries for these transactions in Oracle Subledger Accounting. Oracle Subledger Accounting transfers the accounting entries to Oracle General Ledger.
In this example, a company creates a capital project to capture the costs of building a new clean room and installing air quality monitors. As part of this project, several air quality monitors are being removed and retired from an existing clean room that is being designated for other uses.
The following table shows the supplier invoice and expenditure item amounts charged to the capital project.
Project Cost Details | Amounts |
---|---|
Supplier invoice for architectural drawings | 2,000.00 |
Supplier invoice for building contractor | 5,500.00 |
Supplier invoice for building permit penalty | 200.00 |
Subtotal | 7,700.00 |
Supplier invoice for new air quality monitors | 2,500.00 |
Total supplier invoice costs | 10,200.00 |
Employee labor for construction project management | 1,400.00 |
Usage for use of company car | 55.00 |
Total construction costs | 11,655.00 |
Employee labor for removing old air quality monitors | 500.00 |
Total project costs | 12,155.00 |
You create subledger accounting entries for the supplier invoice transactions from Oracle Payables. Oracle Subledger Accounting transfers the accounting to Oracle General Ledger. The following table shows the supplier costs that you interface to Oracle Projects.
Account | Debit | Credit |
---|---|---|
CIP - Clean Room | 7,700.00 | |
CIP - Air Quality Monitors | 2,500.00 | |
Accounts Payable Trade | 10,200.00 |
You account for the employee labor and usage transactions you enter in Oracle Projects with the journal entry shown in the following table:
Account | Debit | Credit |
---|---|---|
CIP - Clean Room | 1,455.00 | |
RWIP - Air Quality Monitors - Cost of Removal | 500.00 | |
Payroll Liability | 1,900.00 | |
Usage Clearing | 55.00 |
After reviewing the project costs, you determine that you cannot capitalize the building permit penalty that you recorded as part of the journal entry for the supplier invoice transactions. To correct this, you change the original transaction from capitalizable to non-capitalizable. Oracle Projects distributes the supplier cost adjustment, generates cost accounting events, and creates subledger accounting entries for the accounting events. Oracle Subledger Accounting transfers the accounting entries to Oracle General Ledger as shown in the following table:
Account | Debit | Credit |
---|---|---|
Building Permit Penalty Expense | 200.00 | |
CIP - Clean Room | 200.00 |
Note: After you post the adjustment transaction, the total amount in Oracle General Ledger for the CIP - Clean Room account is 8955.00.
Each asset line created by the Generate Asset Lines process has an associated general ledger account. After you post the asset lines in Oracle Assets, you can create accounting in Oracle Subledger Accounting to relieve the CIP or RWIP account, and transfer the amount to the appropriate asset cost or group depreciation reserve account. Oracle Subledger Accounting transfers the final accounting entries to Oracle General Ledger.
After the clean room is complete and the new monitors are installed, you place the assets in service and interface the CIP asset lines to Oracle Assets. After you post the assets in Oracle Assets, you create accounting as shown in the following table:
Account | Debit | Credit |
---|---|---|
Assets - Clean Room | 8,955.00 | |
Assets - Air Quality Monitors | 2,500.00 | |
CIP - Clean Room | 8,955.00 | |
CIP - Air Quality Monitors | 2,500.00 |
After the existing air quality monitors are removed, you specify a retirement date for the retirement adjustment asset and interface the RWIP asset lines to Oracle Assets. After you post the retirement adjustment asset in Oracle Assets, you create accounting as shown in the following table:
Account | Debit | Credit |
---|---|---|
Accumulated Depreciation - Air Quality Monitors - Cost of Removal | 500.00 | |
RWIP - Air Quality Monitors - Cost of Removal | 500.00 |
Note: As the final step in the process of accounting for the asset transactions illustrated in this example, you would initiate an asset retirement transaction in Oracle Assets for the air quality monitors that were removed from the clean room that is being taken out of service. You would then create journal entries to account for the retirement of the group asset cost associated with these monitors. For more information on processing retirement transactions, see: Asset Retirements, Oracle Assets User Guide.
Related Topics
Overview of AutoAccounting, Oracle Projects Implementation Guide
You can create capital assets and retirement adjustment assets using capital projects. When a capital asset is ready for use, you can place it in service in Oracle Projects and send the project asset information and asset cost amounts to Oracle Assets for posting as a fixed asset. When you retire an asset that is associated with a group asset in Oracle Assets, you can enter a retirement date for the retirement adjustment asset in Oracle Projects and send the retirement cost amounts to Oracle Assets for posting as an adjustment to the accumulated depreciation accounts for the group asset.
After you create a capital project, you can create capital assets for assets you want to place in service as fixed assets. You can also create retirement adjustment assets to collect retirement costs for assets you want to retire that are associated with a group asset in Oracle Assets.
You can define capital assets and retirement adjustment assets separately in different projects or together in the same project. You can define assets from either the Capital Projects window or from the Projects, Templates window. For more information, see: Defining Assets.
You create capital assets and accumulate costs for fixed assets you are building, installing, or acquiring. You define an asset in Oracle Projects for each capital asset you want to place in service. To interface a capital asset to Oracle Assets, you must specify an in- service date for the asset in Oracle Projects. For a complete list of attributes you can define for assets, see: Asset Attributes.
You create retirement adjustment assets to collect cost of removal and proceeds of sale amounts for assets associated with a group asset in Oracle Assets that you are retiring, removing, abandoning, or otherwise disposing.
When you define a retirement adjustment asset in Oracle Projects, you must specify a valid Oracle Assets group asset identifier as the target asset. You can create retirement adjustment assets and interface retirement costs to Oracle Assets only for fixed assets that are classified as group assets in Oracle Assets. To interface a retirement adjustment asset to Oracle Assets, you must specify a retirement date for the asset in Oracle Projects. For a complete list of attributes you can define for an asset, see: Asset Attributes.
You can initiate a retirement request in Oracle Projects to identify one or more assets that you are retiring from service. Retirement requests serve as an advice that you can use to notify your fixed asset department about assets that need to be retired in Oracle Assets.
To process a retirement request:
Navigate to the Capital Projects window and choose the Requests button to open the Retirement Requests window.
Choose the Create New Request button to open the Mass Retirements window and specify any combination of asset attributes to find one or more assets you want to retire.
Save your work.
After a retirement request is processed in Oracle Assets, you can return to the Retirement Requests window in Oracle Projects to view the retirement information.
To view retirements:
Navigate to the Capital Projects window and choose the Requests button to open the Retirement Requests window.
Select a retirement transaction you want to view and choose View Retirements.
The following illustration shows the capital projects flow in Oracle Projects before you send asset lines to Oracle Assets. The steps shown in this flow are described in the text that follows the diagram.
To create an asset in Oracle Projects:
Create a new capital project and WBS using a project template whose project type is set up for a capital project. Update project and task details if necessary. You can also create assets when you copy an existing capital project. Assets associated with the existing project are copied to the new project, along with asset assignments. See: Creating a New Project from a Project Template or Existing Project, Oracle Projects Fundamentals.
Update the Transaction Controls, as appropriate, including which transactions can be capitalized by employee, expenditure category, expenditure type, or non-labor resource. See: Specifying Which Capital Asset Transactions to Capitalize.
Collect CIP, RWIP, and expensed costs for your capital project and make adjustments if necessary.
Note: You must create accounting in final mode for the costs before you can generate asset lines for the costs.
Define CIP and retirement adjustment assets if necessary. See: Defining Assets. You can define assets manually or using project asset APIs. For more information see: Oracle Projects APIs, Client Extensions, and Open Interfaces Reference.
Specify asset grouping levels and grouping level types within the WBS. You can then associate assets with the various grouping levels. See: Assigning Assets to Grouping Levels.
Specify the date in service for completed CIP assets or the date retired for retirement adjustment assets. See: Placing an Asset in Service, and Specifying a Retirement Date for Retirement Adjustment Assets.
Optionally, define capital events to control how assets and costs are grouped, and placed in service or retired. See: Creating Capital Events.
Generate Asset Lines. Review asset cost lines and make any necessary adjustments. See: Generating Summary Asset Lines.
Run the Interface Assets process. See: Sending Asset Lines to Oracle Assets.
For capital assets, you must specify whether to capitalize or expense each transaction charged to a capital project. The capitalizable classification is similar to the billable classification for transactions charged to a contract project. The task and transaction controls you define determine the default value for this classification.
Note: You cannot make an election on how to account for retirement costs for retirement adjustment assets. Oracle Projects automatically classifies retirement costs as cost of removal or proceeds of sale based on the expenditure type you use for retirement transactions.
To specify the level at which a capital asset transaction is capitalized:
Decide at which level you want to specify if a transaction can be capitalized, then navigate to the appropriate window, as shown in the following table:
Control Level | Window |
---|---|
Entire Task | Task Details |
Employee | Transaction Controls |
Expenditure Category | Transaction Controls |
Non-Labor Resource | Transaction Controls |
Expenditure Item | Expenditure Items (Tools menu) |
Select the Capitalizable check box for the task control level you want.
Save your work.
Related Topics
Transaction Controls, Oracle Projects Fundamentals
To define a CIP and retirement adjustment assets for a capital project, you enter asset information, such as the asset name, asset number, book, asset category, and date placed in service or date retired. For a complete list of attributes you can define for an asset, see: Asset Attributes.
When you create a capital project type, you can specify whether a complete asset definition is required in Oracle Projects before you can place the asset in service. See: Project Types, Oracle Projects Implementation Guide.
To define assets in the Capital Projects window:
Navigate to the Capital Projects window.
In the Find Capital Projects window, find the capital project for which you want to define assets.
In the Capital Projects window, choose Assets.
In the Assets window, select either the Capital Project Assets Workbench or the Retirement Adjustment Assets Workbench.
Select or enter asset information in each tab of the Assets window.
Tip: To view and enter all attributes for an asset in a single window, choose the Open button on the Assets window to open the Asset Details window.
To create an asset, you must enter at least the Asset Name and Description. To create a retirement adjustment asset, you must also enter a valid group asset identifier in the Target Asset field.
Save your work.
To define assets in the Projects window:
Navigate to the Projects window.
In the Find Projects window, find the capital project for which you want to define assets.
In the Projects, Templates Summary window, choose Open.
The Project, Templates window opens.
For Options, choose Asset Information, Assets.
Enter information for an asset. You can use the down arrow key or Edit, New Record from the menu if you want to enter more than one asset for this capital project.
To create an asset, you must enter at least the Asset Name and Description. To create a retirement adjustment asset, you must also enter a valid group asset identifier in the Target Asset field.
Save your work.
To streamline the definition of multiple project assets that have similar attributes, you can use the Copy Asset option on the Assets and Asset Details windows to copy assets within a project. When you select an asset and choose the copy option, Oracle Projects copies the selected asset to a new row and opens the Copy To window. The Copy To window prompts you to enter values for several key asset attributes that define a unique asset. Oracle Projects prompts you to enter the following attributes on the Copy To page:
Asset Name
Asset Description
Project Asset Type
When you copy an asset, Oracle Projects copies the asset with the same project asset type. For estimated assets, you can optionally copy the asset as an as-built asset.
Asset Date
The date you enter varies according to the project asset type you select. The date can be an estimated date placed in service (Estimated project asset type), actual date placed in service (As-Built project asset type), or a retirement date (Retirement Adjustment project asset type).
Units
Similar to the asset date, the unit amount you enter varies according to the project asset type you select. The unit amount can be estimated units (Estimated project asset type), actual units (As-Built project asset type), or retirement units (Retirement Adjustment project asset type).
Asset Number
When you enter attribute values in the Copy To window, you can also choose whether to copy the asset assignments. However, you cannot use the Copy Assets feature to copy asset lines or other asset information.
You must enter asset information when you define an asset in Oracle Projects. The Interface Assets process sends all asset information to Oracle Assets except for the asset name and estimated date in service. This section describes the attributes you can define for assets in Oracle Projects.
You must define a unique asset name for each asset within a project. You cannot change the asset name after you place the asset in service or specify a retirement date in Oracle Projects.
An asset number uniquely identifies each asset. You can enter a unique asset number, or use automatic asset numbering in Oracle Assets during the Mass Additions process. You cannot update this field after you send the asset to Oracle Assets.
If you enter an asset number, it must be unique and not in the range of numbers reserved for automatic asset numbering in Oracle Assets. You can enter any unique number that is less than the number in the Starting Asset Number field in the System Controls form, or you can enter any non-numeric value.
Use this field to provide a description of the asset you are building. You cannot update this field after you send the asset to Oracle Assets.
The asset category determines the default asset cost account and depreciation rules for the asset after you send the asset to Oracle Assets. You cannot update this field after you send the asset to Oracle Assets.
Oracle Projects provides you with a list of asset category values defined in Oracle Assets and associated with the corporate book of the CIP asset. The asset category you choose here is not displayed in the Asset Lines window.
You can define an asset key to group assets or identify groups of assets independently of the asset category. This field does not have a financial impact.
The Book field defines the corporate depreciation book of the asset. Oracle Assets determines default financial information from the asset category, book, and date placed in service for your asset after you send it to Oracle Assets.
By default, this field displays the asset book defined in Oracle Projects Implementation Options. You can override this value at the asset level. Oracle Projects provides you with a list of corporate book values defined in Oracle Assets which match the Oracle Projects ledger. You can have multiple corporate books associated with one ledger in Oracle Assets.
The location identifies the expected physical location of the asset after it is placed in service. Oracle Projects provides you with a list of valid locations defined in Oracle Assets.
This field identifies whether an asset represents an Estimated or complete, As-Built capital asset, or a Retirement Adjustment asset.
This field identifies the capital event, if any, associated with the asset.
Enter the date you estimate placing an asset in service. Use the Estimated In-Service Date to query and review assets you expect to be in service.
Enter the date you estimate retiring an asset from service. Use the Estimated Retirement Date to query and review assets you expect to be retired.
This date represents the actual date you place an asset in service and begin using it. The date can be in the current or a prior accounting period. You must specify an actual in-service date for a completed asset in order to interface the asset to Oracle Assets. You cannot change this date after you place the asset in service in Oracle Projects.
You may want to begin creating and reviewing asset lines prior to the period you intend to place the asset in service. You can enter a date in a future accounting period.
Note: The Interface Assets process automatically rejects an asset with a future date in service.
Use this field to enter the date you retire an asset from service. You cannot change this date after you interface a retirement adjustment asset to Oracle Assets.
Use this field to capture an estimate of the number of components that make up or are installed for an asset.
The actual number of components for an asset. For example, if you build two assembly machines, enter 2 units for the asset. You cannot update this field after you send the asset to Oracle Assets. Oracle Projects uses the value in this field to allocate unassigned and common costs to assets when you select an asset cost allocation method of Actual Units.
You can use this field to identify a parent asset for assets that you separately track and manage as asset components.
You can use this field to specify an estimated cost for the asset. Oracle Projects uses the value in this field to allocate unassigned and common costs to assets when you select an asset cost allocation method of Estimated Cost.
Use this field to identify the manufacturer of an asset.
Use this field to identify the model number of an asset.
Use this field to capture the serial number of an asset. This number must be unique for the manufacturer in Oracle Assets.
Use this field to enter a user-defined tracking number for an asset. This number must be unique in Oracle Assets.
This field identifies the external asset management asset system from which an asset is imported, if any.
The external asset management system identifier for an asset imported from an external asset management asset system, if any.
The name of the employee responsible for the asset when it is placed in service (not the project owner).
The employee number of the person responsible for the asset when it is placed in service.
You can select this check box to identify an asset you want to reverse.
You can select this check box to prevent any further costs from being charged to the asset.
Check the Depreciate check box if you want to depreciate the asset in Oracle Assets.
Check the Amortize Adjustments check box if you want to amortize the catchup depreciation on a cost adjustment over the remaining life of the asset. If you do not check Amortize Adjustments, Oracle Assets expenses the catchup depreciation expense for the adjustment in one period.
Note: Oracle Projects does not interface the amortization information to Oracle Assets if either of the following conditions apply:
You are interfacing an asset to Oracle Assets for the first time.
The asset is in a period of addition in Oracle Assets.
Otherwise, Oracle Projects interfaces the amortization information that you define for the asset in Oracle Projects to Oracle Assets.
If you check this check box, you cannot deselect it once the asset has been interfaced to Oracle Assets.
Important: If you select this field and reverse capitalize the asset, Oracle Assets will amortize the catch up depreciation on the negative cost adjustment over the remaining life of the asset. Therefore, the depreciation expense per period on the original asset cost will not match the depreciation amount generated per period to account for the asset cost reversal in Oracle Assets.
This field is displayed only for assets with a project asset type of Retirement Adjustment. You must use this field to specify the group asset in Oracle Assets that corresponds to the retirement adjustment asset for which you want to capture retirement costs.
This field identifies the expense account to which you charge depreciation for a capital asset. You must specify a book before you can enter a depreciation expense account. In addition, you must specify a depreciation account for a capital asset before you can interface the asset to Oracle Assets. You can optionally set up the Depreciation Account Override Extension to automatically derive the depreciation expense account based on the book and asset category that you define for the asset. You cannot update this field after you send the asset to Oracle Assets.
Related Topics
Asset Setup Information, Oracle Assets User Guide
Sending Asset Lines to Oracle Assets
When a CIP asset is complete, you place it in service. If your project has more than one CIP asset, you can place each asset in service as it is completed. You do not have to complete the entire project to place an asset in service. You place an asset in service by entering the Actual In-Service Date for the asset. Although you can collect expensed costs for a capital project, you cannot capitalize these costs.
The Actual In-Service Date can be a past, current, or future date. After you enter the date, generate and interface the asset lines. Oracle Assets will calculate and record how much depreciation should have been taken for the asset.
To capitalize CIP asset costs:
Navigate to the Capital Projects window.
Find the capital project whose assets you want to place in service by entering search criteria, such as estimated in service date, project name or number, project type, organization, key member, or class code, in the Find Capital Projects window.
In the Capital Projects window, Oracle Projects displays the summarized expensed, CIP and interfaced project costs for each capital project. The Update Project Summary Amounts process updates expensed, CIP amounts; the Interface Assets process updates the interfaced amount.
Choose the capital project you want and choose the Assets button.
In the Assets window, select the Capital Project Assets Workbench option (if not already displayed), and enter the Actual In-Service Date for the asset you are placing in service.
Compare the Estimated In-Service Date to the Actual In-Service Date. If unreasonable discrepancies exist, verify that the Actual In-Service Date for the asset is correct.
Note: You cannot send assets to Oracle Assets whose actual date placed in service is later than the current Oracle Assets period date.
Enter a complete asset definition for the asset if you have set up Oracle Projects to only allow complete definitions to be sent to Oracle Assets.
For a list of the fields required for a complete asset definition, see: Asset Attributes.
Save your work.
When the activities associated with retiring, removing, abandoning, or disposing of an asset are complete, you can specify a retirement date for the retirement adjustment asset to signify the retirement. Specifying a retirement date enables you to generate asset lines for the retirement costs captured in Oracle Projects. You can then interface the retirement asset lines to Oracle Assets for posting to the accumulated depreciation accounts for the associated group asset. If your project has more than one retirement adjustment asset, you can retire each asset as retirement activities are completed.
To specify a retirement date for retirement adjustment assets:
Navigate to the Capital Projects window.
Find the capital project whose assets you want to retire by entering search criteria, such as project name or number, project type, organization, key member, or class code, in the Find Capital Projects window.
In the Capital Projects window, Oracle Projects displays the summarized expensed, CIP, RWIP, and interfaced project costs for each capital project. The Update Project Summary Amounts process updates expensed and CIP and RWIP amounts; the Interface Assets process updates the interfaced amount.
Choose the capital project you want and choose the Assets button.
In the Assets window, select the Retirement Adjustment Assets Workbench option and enter the Retirement Date for the asset you are retiring.
Compare the Estimated Retirement Date with the actual Retirement Date. If unreasonable discrepancies exist, verify that the Retirement Date for the asset is correct.
Save your work.
After you place your capital assets in service and specify retirement dates for your retirement adjustment assets, you can create, prepare, and send asset lines for the cost amounts to Oracle Assets. First, you must run the Generate Asset Lines process to create summary asset lines from the CIP and RWIP expenditure items and any cost adjustments. Before you run the Interface Assets process, review and adjust your asset lines if necessary. You can perform the following adjustments on your asset lines:
Associate assets with unassigned asset lines
Note: You can set up your capital projects to automatically associate assets with unassigned asset lines by defining an asset cost allocation method. For more information, see: Allocating Asset Costs.
Change which asset is associated with a line
Split an asset line into multiple asset lines and associate the new lines with different assets
Change the line description
Related Topics
Generate Asset Lines, Oracle Projects Fundamentals
Reviewing and Adjusting Asset Lines
You can create periodic and manual capital events to control how capital project assets and costs are interfaced to Oracle Assets over time. You use capital events to group assets and costs before you generate asset lines for capitalization and retirement cost processing.
When you use periodic event processing, you submit a concurrent program that selects unprocessed assets and cost amounts for a project based on the in-service and expenditure item dates you specify in the program parameters. When you use manual event processing, you can specify the assets and costs that you want to include in the event, as well as the in-service and expenditure item dates.
When you submit the Generate Asset Lines concurrent program for a capital project that uses capital events, Oracle Projects automatically generates asset lines for all defined, unprocessed capital events.
You can specify a default event processing method for a capital project type and override it at the project level.
For information on specifying an event processing method in the Capitalization Information tab of the Project Types window, see: Project Types, Oracle Projects Implementation Guide.
To specify an event processing method for a project, select a processing method in the Capital Information window for the project. For information, see: Capital Information, Oracle Projects Fundamentals.
To create a periodic capital event, you must submit the PRC: Create Period Capital Events concurrent program. For information, see: Create Periodic Capital Events, Oracle Projects Fundamentals.
You can create capital events from the Capital Projects window.
To create a capital event:
Navigate to the Capital Projects window.
Find the capital project for which you want to define a capital event in the Find Capital Projects window.
Choose the capital project you want and choose the Capital Events button.
In the Capital Events window, select either the Capital Project Assets Workbench or the Retirement Adjustment Assets Workbench.
Insert a new row to derive the (next) sequential event number, an event name, and optionally select a different asset allocation method.
Save your work.
To select assets for the event, choose the Assets button to open the Event Assets window and choose Attach New Assets.
In the Attach New Asset window, enter selection criteria to find one or more assets to attach to the event and choose OK to return to the Event Assets window.
Note: To detach an asset after it is selected, you can deselect the Include check box for the asset line. You can detach an asset from an event if asset lines have not been generated for the event, or if all asset lines for the event are reversed.
Save your work and close the Event Assets window to return to the Capital Events window.
To select costs for the event, choose the Costs button to open the Event Costs window and choose Attach New Costs.
In the Attach New Costs window, enter selection criteria to find costs to attach to the event and choose OK to return to the Event Costs window.
Note: To detach a cost item after it is selected, you can deselect the Include check box for the cost line. You can detach a cost item from an event if it has not been generated and grouped into an asset line, or if all asset lines for the cost item are reversed.
Save your work and close the Event Costs window to return to the Capital Events window.
To generate asset lines for the event, choose Generate. For more information, see: Generating Summary Asset Lines.
You can view the status of the request in the Events window.
Note: You can optionally reverse all assets for the event by choosing the Reverse button.
The Generate Asset Lines process creates summarized asset lines for capital assets and retirement adjustment assets.
For capital assets, the process generates capital asset lines only from capitalizable expenditure items on tasks that are assigned to a capital asset with an actual date placed in service.
For retirement adjustment assets, the process generates retirement adjustment asset lines only from expenditure items on tasks that are marked as Retirement Cost tasks, and are assigned to a retirement adjustment asset with a defined retirement date.
Oracle Projects creates asset lines based on the asset grouping level you choose within a project and the CIP grouping method you designate for the corresponding project type. The grouping level represents the WBS level at which you assign assets or group common costs.
You determine the grouping level by assigning assets to a WBS component (for example, the project, a top task, or a lowest task), or by designating a WBS component as a grouping level for common costs. For more information on grouping levels, see: Asset Summary and Detail Grouping Options.
The CIP grouping method determines how Oracle Projects summarizes asset costs within an asset grouping level. For example, you can choose to summarize asset costs by expenditure type or expenditure category. For more information on specifying a grouping method, see: Project Types, Oracle Projects Implementation Guide.
The AutoAccounting rules you define for CIP and RWIP costs also influence the amount of summarization. Oracle Projects creates asset lines by summarizing by grouping level, grouping method, and CIP/RWIP account.
If you define your own detailed accounting rules in Oracle Subledger Accounting, then Oracle Subledger Accounting overwrites default accounts, or individual segments of accounts, that Oracle Projects derives using AutoAccounting. The generate asset lines process uses final accounting from Oracle Subledger Accounting to determine the CIP or RWIP accounts for asset lines. To obtain CIP or RWIP account information from Oracle Subledger Accounting, the generate asset lines process uses information from the predefined post-accounting programs that Oracle Projects provides in Oracle Subledger Accounting. For additional information on the post-accounting programs, see: Implementing Oracle Project Costing, Oracle Projects Implementation Guide.
Note: The generate asset lines process obtains the CIP or RWIP accounts from the cost distribution lines in Oracle Projects, and not from Oracle Subledger Accounting, in the following two situations:
The Interface Costs to GL option for the type of cost is set to No in Oracle Projects implementation options.
You import costs from an external non-Oracle system into Oracle Projects as accounted costs. As a result, Oracle Projects does not generate accounting events or create accounting for these costs.
When more than one asset is assigned to a grouping level or common costs are entered for a project, you must define an asset allocation method if you want Oracle Projects to automatically assign all asset costs to assets. Otherwise, you must manually assign any unassigned or common costs. For information on defining an asset allocation method, see Allocating Asset Costs.
The following table describes how Oracle Projects maps costs to assets:
Number of assets assigned to a grouping level | Expected results after running Generate Asset Lines process |
---|---|
One asset assigned to a grouping level | All detail costs charged to that level are automatically mapped to that asset. |
More than one asset assigned to a grouping level, only one asset is placed in service | If the asset allocation method specified for the project has a value of None, then Oracle Projects generates asset lines for all costs, but does not assign an asset to the asset lines. If the asset allocation method is other than None, then Oracle Projects generates asset lines for the grouping level. However, costs are allocated and assigned only to the assets being placed in service. When you use the Asset Assignment client extension to assign asset lines, Oracle Projects assigns the assets placed in service, as well as assets without an in-service date, to the asset lines. |
The cost distribution is for purchased goods from a purchase order which has an inventory item with a default asset category | Costs are mapped to the single asset that matches the default asset category for that grouping level. |
More than one asset has the same asset category as the default asset category for a purchased item | When the asset allocation method specified for the project has a value other than None, Oracle Projects creates asset lines, and allocates costs and assigns assets having the same default asset category to the asset lines. When the asset allocation method has a value of None, the assets are not assigned automatically. |
The generate asset lines process calculates reporting currency amounts for asset lines. For information on the generate asset lines process, see: Generate Asset Lines, Oracle Projects Fundamentals.
For example, assume you assign one asset to a capital project at the project grouping level. As shown in the following table, you charge the following expenditure items to the project, all of which are capitalizable and charged to the same CIP account:
Expenditure Type | Expenditure Category | Amount |
---|---|---|
Supplies | Operating | 5,000.00 |
Supplies | Operating | 20,000.00 |
Professional | Labor | 5,800.00 |
Clerical | Labor | 1,500.00 |
Computer | Service Center | 14,000.00 |
Meals | Travel | 300.00 |
Lodging | Travel | 500.00 |
Air Travel | Travel | 900.00 |
Miscellaneous | Operating | 5,000.00 |
Total Costs | 53,000.00 |
If you use a grouping method of Expenditure Category, Oracle Projects creates the asset lines shown in the following table:
Asset Lines | Amount |
---|---|
Labor | 7,300.00 |
Operating | 30,000.00 |
Service Center | 14,000.00 |
Travel | 1,700.00 |
If you use a grouping method of Expenditure Type, Oracle Projects creates the asset lines shown in the following table:
Asset Lines | Amount |
---|---|
Air Travel | 900.00 |
Clerical | 1,500.00 |
Computer | 14,000.00 |
Lodging | 500.00 |
Meals | 300.00 |
Miscellaneous | 5,000.00 |
Professional | 5,800.00 |
Supplies | 25,000.00 |
If you use a grouping method of All, Oracle Projects creates a single asset line for the total cost amount of 53,000.00.
Note: If expenditures are accounted to separate CIP accounts, then Oracle Projects summarizes the asset lines by CIP account, even when the grouping method is All. Oracle Projects creates asset lines by summarizing by grouping level, grouping method, and CIP/RWIP account.
Prerequisites:
Before you run the Generate Asset Lines process, cost the transactions by running the following processes:
PRC: Distribute Labor Costs
PRC: Interface Supplier Costs
PRC: Distribute Expense Report Adjustments
PRC: Distribute Usage and Miscellaneous Costs
PRC: Distribute Supplier Cost Adjustments
PRC: Distribute Total Burdened Costs (required if you are capitalizing burdened costs and you capture burden cost on the same expenditure item)
PRC: Create and Distribute Burden Transactions (required if you are capitalizing burdened costs and you capture burden as a separate expenditure item)
PRC: Generate Cost Accounting Events
Note: You must run this process for each process category for which you have costs. Alternatively, you can leave the Process Category parameter blank to generate accounting events for all costs.
PRC: Create Accounting
Note: You must run this process for each process category for which you have costs. Alternatively, you can leave the Process Category parameter blank to create accounting events for all costs.
Important: You must run the process PRC: Create Accounting in final mode for the expenditure items before you run the process PRC: Generate Asset Lines. The generate process does not create asset lines for the costs if the corresponding expenditure items are not successfully accounted in final mode.
Run the Update Project Summary Amounts process so you can see the total expensed, CIP, and RWIP amounts in the Capital Projects window.
You can generate asset lines for a single project or capital event, and for a range of projects.
Important: You must create accounting for the costs in final mode before you can generate asset lines for the costs.
To generate summary asset lines for a single project or capital event
Navigate to the Capital Projects or Capital Events window.
For capital events, select either the Capital Project Events Workbench or the Retirement Cost Events Workbench to continue.
Find and select a capital project or capital event for which you want to generate asset lines.
Choose the Generate button.
Enter the Asset Date Through. Oracle Projects creates asset lines from assets with an actual date placed in service/retirement date before and including this date only.
For PA Through Date, enter the last day of the PA period through which you want the costs to be considered for capitalization.
If you enter a date that falls within the PA period, the process uses the period ending date of the preceding period. If the date you enter is the end date of a period, the process uses the end date of that period, as shown in the example in the following table:
Period | Start Date | End Date | You enter... | The process uses... |
---|---|---|---|---|
P1 | 07-Jun-99 | 13-Jun-99 | 19-Jun-99 | 13-Jun-99 |
P2 | 14-Jun-99 | 20-Jun-99 | 20-Jun-99 | 20-Jun-99 |
Choose Include Common Tasks, if you want to create asset lines from costs assigned to a grouping level type of Common Cost.
Choose OK to submit the Generate Asset Lines process. Oracle Projects creates asset lines for your project or event and runs the Generate Asset Lines Report.
Review the Generate Asset Lines Report. See: Generate Asset Lines Report, Oracle Projects Fundamentals.
You can also generate asset lines for a single project or capital event by submitting the PRC: Generate Asset Lines for a Single Project process from the Submit Request window.
To generate summary asset lines for a range of projects:
Choose the PRC: Generate Asset Lines for a Range of Projects process in the Submit Request window. In the Parameters window, enter a project or range of projects, date placed in service/retirement date through, and PA through date. Also indicate if you want to include common tasks. Choose Submit to generate asset lines and run the Generate Asset Lines Report. Review the report to verify the creation of asset lines.
You can specify an asset allocation method to enable Oracle Projects to automatically allocate unassigned asset lines and common costs across multiple assets. Unassigned asset lines typically occur when more than one asset is assigned to an asset grouping level.
You can specify a default asset allocation method for a capital project type and override it at the project level.
For information on specifying an asset allocation method in the Capitalization Information tab of the Project Types window, see: Project Types, Oracle Projects Implementation Guide.
To specify an asset allocation method for a project, select an allocation method in the Capital Information window for the project. For information, see: Capital Information, Oracle Projects Fundamentals.
You can select one of the following asset allocation methods:
Actual Units: Costs are allocated based on the number of actual units specified for each asset in the Assets window. See: Asset Attributes.
Client Extension: Costs are allocated based on the Asset Allocation Basis extension. For information, see: Asset Allocation Basis Extension, Oracle Projects APIs, Client Extensions, and Open Interfaces Reference.
Current Cost: Costs are allocated based on the grouped CIP cost of each asset.
Estimated Cost: Costs are allocated based on the estimated cost specified for each asset in the Assets window. See: Asset Attributes.
Standard Unit Cost: Costs are allocated based on a standard unit cost defined for the asset book and category in the Project Assets Standard Unit Cost window. See: Define Standard Unit Costs for Asset Cost Allocations, Oracle Projects Implementation Guide.
Spread Evenly: Costs are allocated evenly based on the number of assets being capitalized for the project or the event.
Run the Interface Assets process to send valid capital asset and retirement adjustment asset lines to Oracle Assets. Then, in Oracle Assets, you can review the mass addition lines created from the project asset lines in the Prepare Mass Additions window. For Oracle Projects to send asset lines to Oracle Assets, the asset line must meet these specific conditions:
The actual date in service or retirement date must fall in the current or a prior Oracle Assets accounting period
A capital asset or retirement adjustment asset must be associated with the asset line
The process creates one mass addition line in Oracle Assets for each asset line in Oracle Projects, assigning the asset information you entered for the asset in Oracle Projects to the mass addition line in Oracle Assets. You use the Mass Additions process in Oracle Assets to prepare and post these mass additions. If you did not enter all required asset information in Oracle Projects, you must enter it for the line in the Prepare Mass Additions window before you can post it.
The process PRC: Interface Assets to Oracle Assets interfaces both ledger currency amounts and reporting currency amounts for the asset lines to Oracle Assets. For information on how Oracle Projects determines reporting currency amounts for asset lines, see: Generate Asset Lines, Oracle Projects Fundamentals.
In Oracle Assets you can query and review assets posted to Oracle Assets by project number and task number in the Financial Inquiry window.
Prerequisite:
If you are sending cost adjustments for an asset from Oracle Projects to Oracle Assets, ensure that the original mass addition was posted to Oracle Assets. If the mass addition has not become an asset, the Interface process will reject the adjustment line.
To send asset lines for a range of projects:
Choose PRC: Interface Assets process in the Submit Request window and enter the project or range of projects, and the date placed in service/retirement date up to which you want to process capitalized costs. Choose Submit to start the process and run the Interface Assets Report.
Related Topics
Interface Assets, Oracle Projects Fundamentals
Overview of the Mass Additions Process, Oracle Assets User Guide
About the Mass Additions Interface, Oracle Assets User Guide
Mass Additions Reports, Oracle Assets User Guide
This section describes how Oracle Projects summarizes expenditures items into asset lines, how to group asset lines, and how to assign asset lines to assets.
Grouping levels control how Oracle Projects summarizes expenditure items into asset lines. You can group by project, top task, or lowest level task. For example, if you group at the project level, Oracle Projects summarizes all capitalizable costs or retirement costs at all task levels into asset lines at the project level. If you group at a top task level, Oracle Projects summarizes all tasks below that top task into asset lines for that top task. See: Assigning Assets to Grouping Levels.
If you have summarized the top task in the WBS branch, you cannot also summarize at the lowest level. For example, if Top Task 1 is a grouping level, you cannot also group at Task 1.1.1. If Task 2.2.1 is a grouping level, you cannot group at Top Task 2. If you group at the project level, you cannot group at any top or lowest level task.
Note: You also use the grouping method assigned to your project type to summarize expenditure items.
If there is a common asset assignment for the lowest task, then the system selects all assets that are assigned beneath the same parent task, with the exception of parent task. For example, if a common assignment is made at task 2.1, then select any assets assigned to tasks 2.2, 2.3, 2.4, etc, but do not select assets assigned to tasks 3.0, 4.1 and so on, since these tasks are outside the current WBS branch.
Grouping level types determine whether you can associate assets with the grouping level.
For examples of grouping levels and grouping level types, see: Examples of Asset Grouping Levels and Example of Asset Grouping Level Types.
You can change the grouping level type at any time. If you change a grouping level type from Specific Assets to Common Costs, Oracle Projects deletes existing asset assignments from the grouping level. Changing the grouping level after you have interfaced assets does not affect the asset lines previously sent to Oracle Assets.
To specify grouping level types:
Navigate to the Find Projects window and enter selection criteria for a capital project.
Select a project and choose Open.
The Projects, Templates Summary window opens.
To group by project, select Asset Information (in the Options area), select Asset Assignments, and then choose Detail.
To group by task, choose Tasks (in the Options area). In the Find Tasks window, enter selection criteria. In the Tasks window, select a task and then choose Options.
For the project or each task, choose a grouping level type:
Specific Assets: Select this option to associate assets with the project or task. The Generate Asset Lines process generates asset lines from the specific assets and costs you associate with this grouping level.
Common Costs: Select this option to group projects or tasks that capture costs you want to allocate to multiple assets. You cannot associate assets with this grouping level type. If you specify an asset allocation method for the project with a value other than None, then the Generate Asset Lines process can allocate these costs across all project assets. If you specify an asset allocation method of None, then the Generate Asset Lines process creates unassigned asset lines for your common cost grouping levels, and you must manually allocate these common costs across assets.
Save your work.
To associate an asset with project costs, assign the asset to a grouping level.
Oracle Projects associates with the specified asset all the asset lines created from the capital or retirement cost expenditure items for a grouping level. If you associate multiple assets with the same grouping level, then you must specify an asset allocation method (other than None) for the project to enable Oracle Projects to assign or allocate the asset lines to the various assets. Otherwise, you must perform this task manually.
To assign assets to grouping levels:
Navigate to the Find Projects window, find your capital project, and then choose Open.
The Projects, Templates window opens.
Select a project and choose Open.
The Projects, Templates Summary window opens.
To group by project, select Asset Information (in the Options area), select Asset Assignments, and then choose Detail.
To group by task, choose Tasks (in the Options area). In the Find Tasks window, enter selection criteria. In the Tasks window, select a task and then choose Options. Assign a specific asset for each task that is in a Specific Asset grouping level. In the Task Options window, select Asset Assignment.
Note: You can assign assets only to grouping levels with a type of Specific Assets.
Choose the assets you want to assign to the grouping level.
Save your work.
You set up a construction management or an administrative task to capture project management activities. These costs do not apply to any specific asset. When the project is complete, you use a standard procedure to split the costs over all the assets. You associate these tasks with a grouping level so you can create asset lines from them, but you use a grouping level type of Common Costs.
The following four illustrations show four possible variations of asset grouping levels for the same project.
Each illustration shows that the project has two top tasks, Task 1 and Task 2.
Task 1 has two subtasks, 1.1 and 1.2. These are the lowest tasks for Task 1.
Task 2 has two subtasks, 2.1 and 2.2. Task 2.1 is a lowest task, and Task 2.2 has two subtasks, 2.2.1 and 2.2.2.
The following illustration shows grouping at the project level.
The following illustration shows grouping at the top task level (Task 1 and Task 2).
The following illustration shows grouping at the lowest task level (tasks 1.1, 1.2, 2.1, 2.2.1, and 2.2.2).
The following illustration shows grouping at the top task level for the Task 1 branch (at Task 1) and at the lowest task level for the Task 2 branch (at Task 2.1, Task 2.2.1, and Task 2.2.2).
Group at different levels in each WBS
The following illustration shows and example of a capital project.
The illustration Example of a Capital Project shows an example of a capital project with the following breakdown structure:
The project has three top tasks, Task 1, Task 2, and Task 3.
Task 1 has two subtasks, 1.1 and 1.2. These are the lowest tasks for Task 1.
Task 2 has three subtasks, Task 2.1, 2.2, and 2.3. These are the lowest tasks for Task 2.
Task 3 has no subtasks.
All transactions on all tasks, except for Task 2.3, are capitalizable. The following grouping and assignment actions are applicable:
Grouping levels:
You create asset lines for Task 1.1, Task 1.2, Top Task 2, and Top Task 3 grouping levels
You charge expenditure items to Tasks 2.1 and 2.2, and they are grouped together into asset lines for Top Task 2
You can charge expensed transactions only to Task 2.3, because Task 2.3 is not capitalizable
Grouping level types:
Task 1.1, Task 1.2, and Top Task 2 grouping levels are assigned the grouping level type Specific Assets
Top Task 3 has a Common Costs grouping level type. The asset allocation method for the project is Current Cost. Asset lines are created and allocated to the project's assets based on the grouped construction-in-process cost of each asset.
Asset assignments:
You associate Asset 1 with Task 1.1 and Task 1.2 (Single Asset associated with multiple grouping levels)
You associate Asset 1 and Asset 2 with Task 1.2, and Asset 3 and Asset 4 to Top Task 2 (Multiple assets associated with a single grouping level)
Related Topics
Creating a Capital Asset in Oracle Projects
CIP Grouping Client Extension, Oracle Projects APIs, Client Extensions, and Open Interfaces Reference
This section describes how you can adjust asset lines created by the Generate Asset Lines process.
When the Generate Asset Lines process creates asset lines without an asset assignment, you need to manually assign an asset to the line before you can send it to Oracle Assets.
If you choose the Include Common Tasks check box when you generate asset lines, Oracle Projects creates asset lines from common task grouping levels as well as from specific assets grouping levels. Use the Common Costs grouping level type to group together tasks that capture costs you want to allocate to multiple assets.
For more information on generating asset lines and how Oracle Projects maps costs to assets, see: Generating Summary Asset Lines. For information on how to define an asset cost allocation method for a project to automatically allocate common costs across multiple assets, see: Allocating Asset Costs.
You can assign an asset to unassigned asset lines for a project or a capital event from the Asset Lines window.
Note: If unassigned asset lines are associated with an event, you can only assign the lines to an asset that is included in the event.
To assign an asset to unassigned lines:
Navigate to the Capital Projects window, choose the project you want, and choose the Lines button.
Choose Find from the toolbar to open the Find Asset Lines window.
Select No from the Assigned poplist within the Line region, and choose the Find button to find all unassigned asset lines for the project
(Optional) Choose Details to view detail information for an asset line so you can identify the asset to assign.
Assign an asset to the lines by entering the asset Name.
Note: The Asset Category field displays the asset category related to payables invoice items. The field does not display the asset category for assets defined in Oracle Projects.
Save your work.
Note: The Asset Line Details window is a folder. You can create folders to display additional fields.
You can change the asset or description for an asset line in the Asset Lines window. However, you cannot change asset lines you have already sent to Oracle Assets.
You can split an asset line and assign the split costs to multiple assets by using percentages or amounts. You can split lines with and without asset assignments. You can split an asset line for a project or a capital event from the Asset Lines window.
To split an asset line for a project or a capital event:
Navigate to the Asset Lines window for a project or capital event.
To open the Asset Lines window for a project, navigate to the Capital Projects window, select a project, and choose the Lines button.
To open the Asset Lines window for a capital event, perform the following steps in the order listed:
Navigate to the Capital Projects window, select a project, and choose the Capital Events button.
In the Capital Events window, select a workbench option, if any, to display capital events or retirement cost events. Select an event and choose the Assets button.
In the Event Assets window, select an asset and choose the Asset Lines button.
Choose the asset line you want to split.
Choose the Split Line button to open the Split Asset Line window.
Enter the Asset Name and the Amount or Percentage you want to split. The Unassigned fields indicate the amount and percent of the asset line's cost you have not yet assigned to an asset.
Choose OK when you finish splitting the line.
Save your work.
Related Topics
Generate Asset Lines Report, Oracle Projects Fundamentals
You can adjust assets after they have been interfaced to Oracle Assets.
You can adjust expenditure items whose costs are sent to Oracle Assets, and collect new expenditure items for an asset in Oracle Projects after you capitalize or retire an asset, and send the summarized asset lines to Oracle Assets. You process these cost adjustments in Oracle Projects and send them to Oracle Assets as adjusting asset lines.
Your cost adjustments can be either positive or negative. For example, you receive a credit memo from a supplier for a capitalized asset you sent and posted to Oracle Assets. When you send this credit memo to Oracle Projects, you create new negative asset lines, which you can send to Oracle Assets as a negative cost adjustment to the original asset.
Oracle Projects includes the information you enter for the asset on the adjusting asset line you send to Oracle Assets. Thus, if you specify to amortize depreciation adjustments for a capital asset in Oracle Projects, Oracle Assets amortizes any catchup depreciation amount for the adjustment over the remaining life of the asset. Otherwise, it expenses the catchup depreciation for the adjustment in the current period.
Note: You cannot send cost adjustments to Oracle Assets until you have posted the original mass addition line (imported asset line) to Oracle Assets using the Post Mass Additions process.
You can adjust capital project expenditure items associated with an asset you placed in service or sent to Oracle Assets. You can generate new asset lines for these adjusted expenditure items and interface them to Oracle Assets to adjust the original asset cost.
To adjust capital project costs:
Navigate to the Expenditure Items window.
In the Find Expenditure Items window, enter your search criteria. To query by capitalizability or grouping level for your capital project, choose Yes in the Capitalizable poplist for the CIP/RWIP Status option.
Choose the expenditure item you want to adjust.
Use the Tools menu to choose the type of adjustment you want to make. You can choose from the following options:
Capitalizable or Non-Capitalizable to change the capitalizability of a capital asset expenditure item.
Split to split the cost of the expenditure item. You must specify how you want to split the item in the Split Expenditure Item window.
Transfer to transfer the expenditure item to another project or task. You must specify the destination project or task for this transfer in the Transfer Expenditure Item window.
Save your work.
Generate Asset Lines. See: Generating Summary Asset Lines.
If you placed an asset in service in error or sent inappropriate asset costs to Oracle Assets, you can reverse capitalization of the asset in Oracle Projects, and send the reversing line to Oracle Assets as an adjustment.
When you reverse a capitalized asset in Oracle Projects, Oracle Projects creates reversing (negative) asset lines to offset the asset lines previously interfaced to Oracle Assets. The asset remains in Oracle Assets with a value of zero. Oracle Projects does not delete or dispose of the asset in Oracle Assets. You can use functionality within Oracle Assets to retire the asset if you do not ever plan to re-capitalize the reversed asset.
Notes:
If you reverse capitalize an asset in Oracle Assets that was created from Oracle Projects, this transaction is recorded in Oracle Assets only, and not in Oracle Projects. If this happens, you cannot manually update the corresponding asset in Oracle Projects.
You cannot send a reversing line to Oracle Assets until you have posted the original asset using the Post Mass Additions process. You cannot make a negative cost adjustment (reversal) to a mass addition not yet posted to Oracle Assets.
When you choose the action to reverse capitalize an asset, Oracle Projects checks Oracle Assets to determine if the asset was retired previously. If yes, then Oracle Projects issues a warning message and you can either continue processing or cancel the reversal action.
If you reverse capitalize an asset in Oracle Projects, and common cost is assigned to that asset, you can choose to reverse all of the assets associated with the common cost or just the selected asset. If you choose to reverse only the selected asset, then Oracle Projects classifies the common cost assigned to that asset as unassigned cost.
Related Topics
Asset Retirements, Oracle Assets User Guide
Depreciation, Oracle Assets User Guide
Overview of Asset Capitalization
Oracle Assets processes reversal transactions from Oracle Projects as negative cost adjustments to the original asset. If you have begun depreciating this asset, Oracle Assets must reverse the depreciation expense in the period you reverse capitalize the asset.
Important: Before you reverse an asset, ensure that the Amortize Adjustment check box is unchecked for the asset. If you reverse capitalize an asset for which you specify to amortize adjustments, the monthly depreciation on the original cost will not equal the monthly depreciation generated to account for the asset cost reversal in Oracle Assets. Oracle Assets will amortize the catch up depreciation on the negative cost adjustment over the remaining life of the asset.
You can reverse capitalize an asset on a project from the Assets window. If the asset is associated with a capital event, then you must reverse the entire event. You can reverse a capital event from the Capital Events window.
To reverse capitalization of an asset:
Navigate to the Capital Projects window.
Find the project you want and choose Assets to open the Assets window.
Choose the asset you want to reverse capitalize.
Ensure that you do not amortize depreciation adjustments for a capital asset you want to reverse capitalize or recapitalize. You can specify whether to amortize adjustments in the asset definition. See: Defining Assets.
Choose the Reverse button.
Oracle Projects automatically enables the Reverse check box for the asset you want to reverse capitalize.
If you reversed the wrong asset, or you want to unreverse an asset before you run the Generate Asset Lines process, choose the asset and the Reverse button again to deselect the asset for reversal.
Save your work.
Run the Generate Asset Lines process to create reversing entries you can send to Oracle Assets. See: Generating Summary Asset Lines.
Review the Generate Asset Lines Report to verify creation of the reversing lines. See: Generate Asset Lines Process, Oracle Projects Fundamentals.
To reverse capitalization of a capital event:
Navigate to the Capital Projects window.
Find the project you want and choose the Capital Events button.
In the Capital Events window, select a workbench option, if any, to display capital events or retirement cost events.
Select an event and choose the Reverse button.
Save your work.
Run the Generate Asset Lines process to remove the Actual Date In Service or Retirement Date from the assets and create reversing entries you can send to Oracle Assets. See: Generating Summary Asset Lines.
Review the Generate Asset Lines Report to verify creation of the reversing lines. See: Generate Asset Lines Process, Oracle Projects Fundamentals.
If you need to recapitalize an asset, put the new Date Placed in Service in the Assets form in Oracle Projects so new asset lines will be created.
Important: You must also manually change the Date Placed in Service for the asset in the Asset Workbench in Oracle Assets, as the Date Placed in Service cannot be updated through the Mass Additions process.
To recapitalize a reverse capitalized asset:
Navigate to the Capital Projects window.
Find the project you want and choose Assets to open the Assets window.
Enter the Actual Date In Service or Retirement Date for the reverse capitalized asset.
Save your work.
In Oracle Assets, change the date placed in service or retirement date to match the date in Oracle Projects. See: Changing Asset Details, Oracle Assets User Guide.
Generate asset lines to create new lines for the asset. See: Generating Summary Asset Lines.
You can abandon a capital asset at any time.
You can abandon a capital project prior to interfacing to Oracle Assets by changing all transactions from capitalizable to non-capitalizable.
To change transactions from capitalizable to non-capitalizable:
Navigate to the Expenditure Inquiry window.
Select all expenditures for the project where the Capitalizable column is checked.
From the Tools menu, choose Non-Capitalizable. If cost distribution has been run on the expenditures, the Cost Distributed column check box will change to unchecked.
Run the distribute labor, expense report, supplier cost adjustment, and usage costs processes. If you are using burdening, run the PRC: Distribute Total Burdened Costs process.
Run the process PRC: Generate Cost Accounting Events.
Run the process PRC: Create Accounting.
When you run the process in final mode, you can optionally choose to transfer the accounting entries to Oracle General Ledger and to post the journal entries in Oracle General Ledger. When you post the journal entries for the costs, Oracle General Ledger creates entries that transfer these costs from the CIP or RWIP account to the Expense account.
If you have already interfaced the asset you want to abandon, you must reverse capitalize the asset in the Assets window in Oracle Projects. You also need to send the reversing lines to Oracle Assets to account for the abandoned CIP asset.
The Generate Asset Lines process creates reversal lines and the Interface Assets process interfaces them to Oracle Assets.
Related Topics
Specifying Which Capital Asset Transactions to Capitalize
Reversing Capitalization of Assets in Oracle Projects
This section describes how to calculate and record capitalized interest for capital projects.
Capitalized interest (also referred to as Allowance for Funds Used During Construction) is an estimate of the interest cost that enterprises incur when they invest in long-term capital projects. Subject to accounting rules and regulatory guidelines, enterprises can capitalize interest as part of the total cost of acquiring and constructing assets that require an extended amount of time to prepare for their intended use.
To accommodate this business requirement, Oracle Projects enables you to calculate and record capitalized interest for capital projects. To meet the requirements of regulated businesses such as those in the utilities industry that can recognize multiple types of capital interest, you can set up Oracle Projects to separately calculate capitalized interest for multiple interest types such as debt and equity.
Oracle Projects calculates capitalized Interest on open CIP amounts. You can spread the cost for one expenditure item across multiple assets. If you have previously capitalized any of the assets to which the cost is allocated, then Oracle Projects excludes the total item cost from the interest calculation.
The process for generating and recording capitalized interest transactions includes the following tasks:
Defining rate names and rate schedules: You define capitalized interest rate names to represent the interest types you want to capitalize. After you define rate names, you can create and maintain capitalized interest rate schedules to assign rates to each organization. For more information, see: Defining Capitalized Interest Rate Names and Rate Schedules.
Setting up capital projects for capitalized interest: To correctly calculate capitalized interest for all eligible capital projects, you must ensure that the capital information options for each project are defined. You must also assign each project a status that allows capitalized interest. For more information, see: Setting Up Capital Projects for Capitalized Interest.
Generating capitalized interest expenditure batches: To generate interest expenditures, you periodically submit the Generate Capitalized Interest Transactions process. See: Generating Capitalized Interest Expenditure Batches.
Reviewing capitalized interest expenditure batches: After you generate capitalized interest expenditure batches, you can review the transactions for accuracy. If necessary, you can delete or reverse a batch to allow regeneration. See Reviewing Capitalized Interest Expenditure Batches.
To calculate capitalized interest, you must define a rate name for each type of interest you want to capitalize and define rate schedules to assign interest rates to organizations.
You define a unique rate name for each type of interest you want to capitalize. For example, you can define a rate name to maintain interest rates for debt and another to maintain interest rates for equity.
For each rate name, you can define thresholds that determine when the calculation of interest begins for eligible projects. You can select interest calculation basis attributes that determine how interest amounts are calculated. For example, you can select an interest method to specify whether interest is calculated on a simple or compound basis. You can also specify a period rate convention to determine whether interest amounts are spread evenly across accounting periods or are derived based on the number of days in each accounting period.
You can control the CIP balance on which interest is calculated by specifying a current period convention and expenditure type exclusions. The current period convention specifies how much of the current period CIP costs are included in the CIP balance. Expenditure type exclusions enable you to specify types of costs that you want to exclude from the CIP balance.
For more information, see: Capitalized Interest Rate Names, Oracle Projects Implementation Guide.
Note: Create a cost budget that includes only capitalizable cost when the capitalized interest threshold has an amount type of Budget. The budget for the capital project should not include expense or retirement costs. Oracle Projects compares the threshold to the entered budget amount and it does not subtract expense and retirement amounts before performing the comparison.
You define interest rate schedules to create and maintain rates for interest calculation. You maintain rates by organization and rate name. You can specify an interest rate schedule for each project type. The rate schedule you define for a project type is the default rate schedule for all projects you create for the project type. You can optionally allow override of the default rate schedule at the project level.
For more information, see: Capitalized Interest Rate Schedules, Oracle Projects Implementation Guide.
To correctly calculate capitalized interest for all eligible capital projects, you must ensure that the capital information options for each project are defined appropriately, and assign each project a status that allows capitalized interest.
The following fields in the Capital Information options window control the calculation of capitalized interest for a capital project:
Allow Capital Interest: This field defines whether a project is eligible for capitalized interest. By default, Oracle Projects enables this option for all capital projects. You can deselect or select this option at any time.
Capital Interest Schedule: This field displays the default capitalized interest rate schedule specified for the project type, if any. If the Allow Schedule Override option is enabled for the project type, then you can override the default interest rate schedule value at the project level.
Capital Interest Stop Date: You can optionally specify a date beyond which a project is not eligible for capitalized interest. To calculate interest, this field must either be blank or contain a date that is later than the end date of the GL period for which you want to calculate interest.
Note: The Allow Capital Interest and Capital Interest Stop Date fields are also available at the task level. You can use these fields to control the calculation of capitalized interest for individual tasks.
For additional information on defining capital information options for projects and tasks, see: Capital Information, Oracle Projects Fundamentals.
For information on assigning capitalized interest rate schedules to project types, see: Specifying Capitalized Interest Rate Schedules for Project Types, Oracle Projects Implementation Guide.
In addition to defining capital information options to enable the calculation of capitalized interest, you must assign each eligible project a status that allows capitalized interest. For more information, see: Setting Project Status Controls for Capitalized Interest, Oracle Projects Implementation Guide.
To generate and record capitalized interest expenditures, you must submit the PRC: Generate Capitalized Interest Transactions process. This process calculates capitalized interest and generates transactions for eligible projects and tasks. For information on submitting this process and the processing parameters that you can select, see: Generate Capitalized Interest Transactions, Oracle Projects Fundamentals.
When you submit the Generate Capitalized Interest Transactions process, you can specify whether expenditure batches are released automatically. If the expenditure batches are not released automatically, then you must release them manually in the Review Capitalized Interest Runs window. For more information, see: Reviewing Capitalized Interest Expenditure Batches.
The generate process charges interest expenditures to the same tasks as the expenditure items on which interest was calculated. The expenditure organization and expenditure type values for the interest transactions are derived based on the expenditure organization source and expenditure type attributes defined for the interest rate name. For more information, see: Capitalized Interest Rate Names, Oracle Projects Implementation Guide.
After you submit the PRC: Generate Capitalized Interest Transactions process, you can check the status of each run and review the process results in the Review Capitalized Interest Runs window. From this window you can view capitalized interest expenditure batches, transactions, and exceptions.
You can generate, review, and delete draft expenditure batches until you are satisfied with the results. To view transactions that generated successfully, select a batch and choose the Transactions button. If a batch generated with warnings or errors, then you can select the draft and choose the Exceptions button to view the exception details. To record the transactions in an expenditure batch, you must release the batch. You can reverse an expenditure batch after it is released successfully.
Note: You cannot generate a draft expenditure batch if a draft already exists for the same projects and GL period.
The following table describes the possible run statuses displayed in the Review Capitalized Interest Runs window.
Run Status | Description |
---|---|
In Process | The process is not complete. |
Draft Success | The process created draft transactions that are ready for release. |
Draft Failure | The process encountered warnings or errors. Draft transactions may be incomplete. Review the exceptions. If exceptions exist for one or more projects, then you can release the batch to release the successfully generated transactions. After you resolve the exceptions, you can create a new run to process the exception project or projects. |
Release Success | Transactions are released. |
Release Failure | The release process failed. After you resolve the release issues, you can release the batch again. |
The rules for releasing, reversing, and deleting capitalized interest expenditure batches are as follows:
Releasing expenditure batches: You can release batches with the status Draft Success or Release Failure.
Reversing expenditure batches: You can reverse expenditure batches with the status Release Success.
Deleting expenditure batches: You can delete expenditure batches with the status Draft Success, Draft Failure, and Release Failure. You cannot delete batches with the status In Process. In addition, you cannot delete batches after they are reversed or released successfully.