Sub Ledger Accounting Architecture and Inquiries

1. Oracle Assets is fully integrated with SLA, which is a common accounting platform for Sub Ledgers.

2. Customers can use the seeded Account Derivation definitions or modify them as required.

3. Continue to support Account Generator functionality for existing Asset Books.

4. New SLA Accounting report and online account inquiry.

Enhanced Mass Additions for Legacy conversions

1. Enhancements have been made to the FA_MASS_ADDITIONS table. New Attributes have been added viz,

• Asset Life
• Depreciation Method
• Prorate Convention
• Bonus Rule Ceiling Name
• Depreciation Limit Plus others

2. Customers can populate the values for the new attributes directly in the FA Mass Additions interface table rather than accepting default values from the asset category.

3. Legacy conversion can be completely automated

4. Web ADI has also been upgraded to include the new Attributes

New Automatic Preparation of Mass Additions

1. This new feature consists of default rules and Public APIs that can be used by customers to complete the preparation of mass addition lines automatically.

2. Auto populate required fields such as Expense Account, Asset Category etc.

3. Avoid manual intervention during the Mass Additions prepare process

4. Avoid customization and use public APIs to effect custom business logic

Assets now uses Flexible Reporting using XML publisher

1. Major Asset Transaction reports have been modified to support XML publisher. 

2. Users can modify or use new templates to view report output.

3. XML reporting is available for the following thirteen asset reports:

1. Asset Transfers Report
2. Transaction History Report
3. Asset Reclassification Report
4. Mass Additions Create Report
5. Cost Adjustment Report
6. Cost Summary Report
7. CIP Summary Report
8. Reserve Summary
9. Journal Entry Reserve Ledger
10. Asset Additions Report
11. CIP Capitalization Report
12. Mass Additions Posting
13. Asset Retirements

Automatic Depreciation Rollback

1. Depreciation is rolled back automatically by the system when any transaction is performed on an asset if the following conditions are met:

• Depreciation has been processed in that period
• The period is not closed

2. It is no longer required to run depreciation rollback program manually.

3. Depreciation rollback is executed only on select assets as required and not on the entire Asset Book this enhances performance of the program.

4. Since release 11i, users have been able to run depreciation for an asset book without closing the period. If additional adjustments are required in the current period, then the user submits a process to roll back depreciation for the entire book, performs the necessary adjustment(s) and then resubmits the depreciation program.

5. In Release 12 the intermediate manual step of rolling back depreciation
for the entire book in order to process further adjustments on selected assets is no longer necessary. As before users may submit depreciation for the entire book prior to closing the period. If it becomes necessary to process financial
adjustments on one or more assets, the user may proceed with the transaction
normally via the asset workbench or mass transactions.

6. Oracle Assets automatically rolls back the depreciation on just the selected assets(instead of the whole book) and allows the transaction(s) to be processed normally. The asset(s) for which depreciation was rolled back is automatically picked up during the next depreciation run or at the time that the depreciation period is finally closed. 

 

Enhanced functionality for Energy Industry

1. Energy Units of Production Method for Group Assets

• Allow Production method for Group Assets
• Allow Production upload to Group Assets

2. Energy Straight line Method

• Net Book Value / Remaining Life

Enhanced Asset Tracking in Payables

1. Enhanced Asset Tracking in Payables

• Item Description
• Manufacturer
• Model
• Serial Number
• Warranty Number

2. Enhanced Mass Additions

• Asset Book
• Asset Category
• IPV/ERV distributions

3. With Release 12, Payables is introducing invoice lines into the invoice model. This entity has been added between the header and distributions and allows Payables to capture a third level of information. This new layer of data relates to the actual goods and services listed on the physical (or electronic) invoice document, including quantity, unit of measure, unit price, item description, manufacturer, model, serial number, and warranty number. Now that this information is stored for the invoice line, Oracle Payables can transfer it over to Oracle Assets where the information is an essential part of asset tracking. (For example, a single invoice line might be for a quantity of three computers, but each of these computers belongs to a different department represented by a cost center, so the one line consists of three distributions. The line can be distributed across the three departments, and each distribution represents the expense charged to each of those departments.)

4. The Create Mass Additions process has been enhanced to transfer these new fields into the interface table, FA_MASS_ADDITIONS. Invoice distributions are still the entity that gets transferred from Payables to Assets, but now the new asset tracking fields are included. Two additional changes to the Create Mass Additions process concern the Asset Book and Asset Category. In prior releases, these two values were available for PO/RCV matched distributions however the fields were not exposed in Payables, so no update was allowed in the Purchasing-Payables-Assets flow. In Release 12, Asset Book and Asset Category are new fields at the line and distribution levels (Asset Book only, not Asset Category) of an invoice.

5. Finally, Create Mass Additions has been enhanced to group the Invoice Price Variance and Exchange Rate Variance distributions to their corresponding item distributions since, in Release 12, these two expenses are tracked as separate distributions rather than being stored as columns on the item distribution, as in prior releases.