Unable to Delete Asset Categories from a Secured Responsibility in r12 Fixed Assets

When attempting to delete a category, which is not in use, from the Asset Category form
the following error occurs:

APP-OFA-48723 You cannot delete setup data from a secured responsibility.
The data may already be in use by assets or books that you do not have access to.
To delete setup data please use a non-secured responsibility.

Steps To Reproduce:

The issue can be reproduced at will with the following steps:
1. Connect to an FA secured responsibility
2. Navigate to the Asset category form
3. Try to delete a category which is not in use
The issue is caused by the secured responsibility :
When you try to delete an asset category , the application checks if it is already in use , meaning whether an asset or a mass addition exist with this category attached.
From a secured responsibility , you could only verify for the assets/books you have access to therefore this functionality is not allowed .

This is intended behavior.

Solution:-

1. Go into an FA non-secured responsibility to delete any Asset Category which is not in use.

You can verify if  a responsibility is not secured with following steps:
Connect to System Administrator responsibility
Navigate to Profile > System
For the FA responsibility , query Profile FA:Security Profile
No value should be assigned.

As a workaround , you could momentarily remove the profile value in order to delete the wrong Asset category and then reset the profile back.

Difference & Use of Fiscal Calendar, Depreciation Calendar and Prorate Calendar

Fiscal year where you define your fiscal year start and end date.

Depreciation calendar is the dividing the fiscal year in to different periods like 12 periods, 24 periods etc. Based on teh number of periods you define in depreciation calendar you need to run depreciation for those many periods

Prorate calendar is used only for internal depreciation calculation purpose like if you want depreciation to be based on by days then your prorate calendar has to be a daily calendar. If you want the depreciation only a monthly basis then it has to be a monthly calendar

APP-OFA-47333: You Cannot Perform this transaction because the asset is fully retired. Choose a book in which you have not yet retired the asset, or reinstate the asset

Issue:

APP-OFA-47333: You Cannot Perform this transaction because the asset is fully retired. Choose a book in which you have not yet retired the asset, or reinstate the asset, and then perform the transaction. If you wish to cancel or undo the retirement, Please query it first.

Solution:-

Reinstate the retired asset.

1. Navigate to Inquiry > Transaction History.

2. Enter the Book & Asset Number of the asset.

3. Press the Find button.

4. Mouseclick the Transaction type field for the retired asset. (It is important to be in the correct field or the Reference Number retreived will not be correct).

5. Make a note of the Reference Number.

6. Go to the Asset Workbench and query the asset.

7. Click the Retirements button.

8. Once the Retirements screen is displayed:

a. Press F11 to query or select Query>Enter on the menu bar.

b. Enter the Reference Number noted above.

c. Press CTRL F11 to perform the query or select Query>Run from the menu bar.

9. Once the information appears on the screen, verify that the information is correct and press the Reinstate button.

10. Run the Calculate Gains and Losses program.

Is it possible to change an account to an Asset Category in oracle r12

Asset Category Accounts can be changed only before a category is used.
Once an asset is assigned to an Asset Category, the accounts can not be changed anymore.

Standard Solution is:
1. Create a new category, with accounts wanted.
2. Reclassify the existing assets with problem category to the new category.
If there is a high volume of assets, use the Mass Reclassification option.

Oracle Assets Profile Options

 

Below profile options are using the oracle asset module.

FA: Allow Swiss Special Assets

FA: Annual Rounding

FA: Archive Table Sizing Factor

FA: Batch Size

FA: Cache Sizing Factor

FA: Custom Generate CCID

FA: Default DPIS to Invoice Date

FA: Deprn Single

FA: Enable Depreciation Override

FA: Generate Asset Level Account

FA: Generate Book Level Accounts

FA: Generate Category Level Accounts

FA: Generate Depreciation Expense Accounts

FA: Japan 2007 Tax Reforms Features

FA: Mass Copy All Cost Adjustments

FA: Maximum Projection Extent

FA: Number of Parallel Requests

FA: Print Debug

FA: Print Timing Diagnostics

FA: Security Profile

FA: Tax Asset Type Category Segment for Japanese Depreciable Assets Tax Report

FA: Use Threshold

FA: Use Workflow Account Generation

FADI: Create Asset Privileges

FADI: Physical Inventory Privileges

You Cannot Expense An Adjustment To An Asset For Which You Have Already Amortized An Adjustment

 

Issue:

You Cannot Expense An Adjustment To An Asset For Which You Have Already Amortized An Adjustment

 

Fix:

 

Since an asset in the reclass group was already amortized, Amortize Adjustments would have to be checked in order for it to work.

An amortized adjustment was already performed for an asset that was being Mass Reclassed with "inherit depreciation rules of new category item" being selected, but not Amortize Adjustments.

 

Submit Mass Reclass with both or neither inherit depreciation rules of new category and the amortize adjustments box being checked (note this will amortized all reclassed assets in the mass transaction)

If there is going to be an adjustment for the group that includes an asset that already has an amortized djustment, then it must be amortized.

-OR-

If you do not wish to amortize all asset in the mass transaction then:

1. Manually reclass the amortized/erring asset

2.  Then retry the Mass Reclass (as it'll no longer include the issue asset)

Manual Cost Adjustment to an Asset OR Credit Memo Adjustment to an asset from Mass Addition process

 

A cost adjustment can be entered manually or posted from the Mass Additions interface table.  Cost adjustments from Mass Additions are typically coming from Accounts Payable or Project Accounting and are beyond the scope of this How To.

To post a manual cost adjustment, navigate as follows:

   Responsibility:  Fixed Assets Manager

   Asset / Asset Workbench

   Query the asset 

   From the Summary screen in the Asset Workbench, select the Books button

   Type in the book or select the book from the popup menu

   Amortize checkbox:

     - do not check this box if depreciation should recalculate from the date placed in service

     - check this box only if depreciation should not be recalculated

   Tab to the lower half of the form and enter the adjusted cost in the cost field

 

   Click on the Done button to save

To post a Mass addition cost adjustment (Credit Memo)

Navigate to Prepare mass addition

1. Query the Credit memo using invoice number (CM #)

2. You can see the status will be “NEW”, click on “add to asset” button

3. Select the original Asset item, which you want to reduce the Costing

  - Amortize adjustment ---->do not check this box if depreciation should recalculate from the date placed in service

  - check this box only if depreciation should not be recalculated

4. click on ‘done’ button, after finishing this the status will be “HOLD”

5. Re-query the assets and change the status queue as ‘POST’ then click ok,

6. After select post queue, the status queue will be show as “COST ADJUSTMENT”

7. Click ‘done’ button

8. Run the post mass addition

9. You can find the concurrent output for the adjustment amount

10. Query the original asset and check the Financial information, there you can see new transaction added as ADJUSTMENT, now the credit memo will be adjusted the costing information

11. Revised depreciation will be take in place from Credit Memo date of services onwards,…

12. You can run the depreciation and check the status for new costing & depreciation information.

Reporting Currency transaction in oracle Assets Financial information screen–12.1.3

Issue:

I am using one primary ledger functional currency as USD and also using Reporting currency INR in “Sub-Ledger Level” balancing.

I added on assets using Assets details Addition but I can’t able to see the reporting currency information in assets view financial information screen.

In the below screen

 

Solution:

This issue is due to lower form version.

Apply patch 16363198:R12.FA.B.

Version should be like below,

Successful patch installation checks: Check the file version , they have to be the same as given below. forms/US/FAXASSET.fmb - 120.208.12010000.113

forms/US/FAXOLFIN.fmb - 120.48.12010000.47

But its lower then recommended

 

Once patch applied successfully, check the above file versions

Now the reporting currency balances are listing in the view financial information screen.

How to - Create, Update, Upload, Rollback and Delete Oracle Asset Impairment Transactions in R12

I) Create Impairment Record:
---------------------------

1. Navigate to Assets responsibility:
(N) Assets> Impairment > Create and Post

2. Click the "New Impairment" button to launch WebAdi for entering impairments.

3. Enter Impairment header information:
Book: Choose book from the list of values (double click the field to invoke LOV)
Impairment Name: Enter impairment name for reference
Impairment Date: Enter a date in the current open period
User Entered date: For reference only

4. Enter Impairment detail information:
Status: Set the status to "Preview" from the LOV for the
"Preview impairments" program to process the row, if it is
left at "New" then the impairment preview will not be processed.
Asset Number: If the impairment information is only for a specific asset
number then select the asset. This can be done by entering
the asset number value or double click the field to invoke LOV.
Cash-Generating Unit (CGU): If the Impairment is made at the
Cash-Generating Unit level then this will have to be selected.
This can be done by entering it directly or double click the
field to invoke LOV.

*Restriction: Use CGU or Asset Number but never both.
Net Selling Price/Value in Use: Enter net selling price and/or Value in Use
Impairment Loss: Enter the amount of impairment loss only if the
Net Selling Price and the Value in Use are null.
Goodwill Amount: Optionally enter goodwill amount and goodwill
asset number for goodwill treatment.

5. Use the top menu to click Oracle > Upload to view upload parameters,
click the "Upload" button to submit the concurrent program.


II) Update Impairments:
-----------------------

1. Navigate to Assets responsibility:
(N) Assets> Impairment > Create and Post

2. Query for existing Impairments by: Book, Cash-Generating Unit,
Impairment Name, Asset Number, Impairment Date, Status.

3. For each Impairment line, the "Update Impairment" button can be pressed to
open WebAdi spreadsheet for updating impairments.

4. Perform necessary changes for the Impairment line.

5. Use the top menu to click Oracle > Upload to view upload parameters,
click the "Upload" button to submit the concurrent program.


III) Upload the Impairments:
-----------------------------

1. Navigate to Assets responsibility:
(N) Assets> Impairment > Create and Post

2. Query for existing Impairments by: Book, Cash-Generating Unit,
Impairment Name, Asset Number, Impairment Date, Status.
The search needs to be made for impairments with the status "Previewed".

3. Use "Select" check box to pick the impairments that needs to be posted.

4. Press "Post" button.


IV) Rollback Impairments:
-------------------------

1. Navigate to Assets responsibility:
(N) Assets> Impairment > Create and Post

2. Query for existing Impairments by: Book, Cash-Generating Unit,
Impairment Name, Asset Number, Impairment Date, Status.
The search needs to be made for impairments with the status "Posted".

3. Use "Select" check box to pick the impairments that need to be rolled back.

4. Press "Rollback" button.


V) Delete Impairments:
----------------------

1. Navigate to Assets responsibility:
(N) Assets> Impairment > Create and Post

2. Query for existing Impairments by: Book, Cash-Generating Unit,
Impairment Name, Asset Number, Impairment Date, Status.
The search needs to be made for impairments with status different
than "Posted".

3. Use "Select" check box to pick the impairments that need to be deleted.

4. Press "Delete" button.

How to Setup Asset Impairments in Oracle R12

I. Setup Cash Generating Unit (CGU):

1. Navigate to Assets responsibility:
(N) Setup > Asset System > Cash Generating Units
2. Define or maintain Cash Generating Units for each book that needs
Impairment functionality.

II. Assign Cash Generating Units to Assets:

There are two possibilities to assign Cash Generating Units:

A) Manually via Asset Workbench:

1. Navigate to Assets responsibility:
(N) Assets > Asset Workbench
2. Query for the existing assets that needs to be assigned to
Cash Generating Units.
3. Press "Books" and select from LOV the book name.
4. Go to Impairment tab and use the LOV from the Cash Generating Unit
field to assign or change CGU assignment.

B) By mass assignment via WEB ADI:

1. Navigate to Assets responsibility:
(N) Assets > Impairment > Assign Cash Generating Units
2. Enter Book , Asset Number and CGU
3. From the main toolbar go Oracle > Upload for uploading the assignment
information to the assets.

III. Setup Impairment Accounts:

Setup Impairment Expense account and Accumulated Impairment
account in the Asset Categories form.

1. Navigate to Assets responsibility:
(N) Setup > Asset System > Asset Categories
2. Query for Asset Categories and Books.
3. Enter the accounting information for Impairment Expense account
and Accumulated Impairment.

How To Transfer Reconciliation References From FA Subledger To GL

Navigation: Setup > Financials > Subledger Accounting > Accounting Methods Builder > Journal Entry Setups > Journal Line Types

1. Query a seeded Journal Line Type and copy it by clicking on the Copy button at the bottom left of the form

2. Give your Journal Line Type code, name, and description a meaningful name.

3. Click on the Accounting Attribute Assignments button at the bottom right of the form

4. Pick a source for the Reconciliation Reference

5. Save.

Navigation: Setup > Financials > Subledger Accounting > Accounting Methods Builder > Methods and Definitions > Journal Line Definitions

6. Link the Journal Line Type just created to the Journal Line Definition. Copy a seeded one and create your own if needed.

7. Assuming that the JLD is already linked to the Application Accounting Definition, validate the Application Accounting Definition either in the form or via the concurrent program 'Validate Application Accounting Definitions'.
Assuming also that the Application Accounting Definition is already linked to the Subledger Accounting Method which in turn is already linked with the ledger, Create Accounting can now be run.

8. Once Create Accounting, Journal Import and the Post program in GL have completed, one can reconcile either manually or run Automatic reconciliation in GL.

Oracle Fixed assets Profile Options

 

Account Generator: Purge    Runtime Data	FA: Number Mass Addition Parallel Requests
FA: Allow Swiss Special Assets	FA: Number of Parallel Requests
FA: Archive Table Sizing Factor	FA: Print Debug
FA: Cache Sizing Factor	FA: Print Timing Diagnostics
FA: Deprn Single	FA: Security Profile
FA: Generate Expense Account	FA: Default DPIS to Invoice Date
FA: Large Rollback Segment   Name	FA: Mass Copy All Cost Adjustments

Account Generator: Purge Runtime Data

Always set this profile option to Yes to ensure that Oracle Workflow has finished generating accounting flexfield code combinations.

Temporarily set this option to No at the user level if you are debugging the account generator. Running the account generator with this option set to No fills up the workflow tables and slows performance.

FA: Allow Swiss Special Assets

Controls whether you can use the Swiss insurance calculation method.

If this profile option is set, when you add insurance details on the Fixed Asset Insurance window, you can check the Special Swiss Assets check box, which signifies that this asset will use the Swiss insurance calculation method.

FA: Archive Table Sizing Factor

This profile option controls the space allotted for the temporary tables created when you archive and purge a book.

The sizing factor specifies how many storage kilobytes to reserve for the initial extent. The default value is 100 kilobytes.

Update this option if you are archiving a large number of records for a fiscal year.

FA: Cache Sizing Factor

This profile option controls the database information retained in the concurrent program for performance improvement. The range is 0 to 25.

FA: Deprn Single

Controls the caching buffer used when you run depreciation. You can set the buffer to either No (20) or Yes (1).

If you set FA: Deprn Single to No, the cache is reset after every 20 assets. If you set FA: Deprn Single to Yes, the cache is reset after every asset.

FA: Generate Expense Account

Allows you to generate the depreciation expense account based on Workflow rules.

When you set this profile option to Yes, Generate Accounts reads the profile option and generates the expense account using Workflow rules. If you do not set this profile option or you set it to No, Generate Accounts uses the expense account entered for an asset in the Assignments window.

FA: Large Rollback Segment Name

This profile option indicates the rollback segment name that Oracle Assets uses for programs requiring large rollback space.

If you do not specify a large rollback segment, Oracle Assets uses the first available rollback segment.

FA: Number Mass Addition Parallel Requests

•Controls the number of requests the Mass Additions Post program will run in parallel. When you run the program, Oracle Assets spawns a parent process with several child processes.

•Enter a number between 1 and 20 to specify the maximum number of parallel requests you want to allow. The parent process is not included in this number.

FA: Number of Parallel Requests

•This profile option controls the number of requests that Oracle Assets programs can run in parallel.

•Enter a number between 1 and 20 to specify the maximum number of parallel requests that you want to allow.

FA: Print Debug

This option indicates whether debug tracing messages are printed in concurrent program log files. Support uses these messages to identify a problem with the code.

FA: Print Timing Diagnostics

This option indicates whether timing diagnostic messages are printed in concurrent program log files. Support. uses these messages to identify a problem with the code.

FA: Security Profile

Restricts access to the organizations defined in the security profile. This option is seeded at the site level with the view–all security profile created for the Startup Business Group.

FA: Default DPIS to Invoice Date

Enables you to use the Future Transactions feature by allowing the default date–placed–in–service to be the invoice date, even when the invoice date is in a future accounting period. If you set this profile option to Yes, Oracle Assets defaults the date–placed–in–service to the invoice date for future transactions. If you set this profile option to No, Oracle Assets does not default the date–placed–in–service to the invoice dates, and you cannot use the Future Transactions feature.

FA: Mass Copy All Cost Adjustments

Allows the Mass Copy program to copy all cost adjustments, even when the un-revalued cost is different in the corporate book and the associated tax books.

How Oracle Assets calculates depreciation for assets using the Following Month (FOL MONTH) Prorate convention and Flat Rate..?

 

Asset Information Example:

Cost : 10000

Date Placed In Service : 01-JUN-2007
Method : Flat Rate 12%
Prorate Convention Code : Following Month
Prorate Date : 01-JUL-2007
The following example calculations will result based on these two scenarios utilizing the 'Depreciate when placed in service' flag during asset depreciation.

1. When 'Depreciate when placed in service' flag is Checked:
- The 'Depreciate when placed in service' is checked for the 'Following Month' Prorate convention:

(N>Setup> Assets System> Prorate Convention)

- Then the value of DEPRN_START_DATE in the table FA_BOOKS will be 01-JUN-2007 as you need to start depreciation from date placed in service.
- Through depreciation run for Jul-07, the system should calculate the depreciation as following:
yearly depreciation = cost * flat rate = 10000 * 0.12 = 1200
yearly depreciation for 2007 (Jul to Dec) = 1200/12 * 6 = 600 (because the prorate is 1-Jul-07)
this yearly depreciation should be divided by 7 periods (Jun-Dec) = 600/7 = 85.71
Depreciation in Jul-07 = Jun depreciation + Jul depreciation = 85.71 + 85.71 = 171.42

2. When 'Depreciate when placed in service' flag is Unchecked:

Now, what should be the value if 'depreciate when placed in service' was unchecked before asset
creation:
- The value of DEPRN_START_DATE in the table FA_BOOKS should be 01-JUL-2007 (prorate date)
- When running Jul-2007 depreciation:
yearly depreciation = cost * flat rate = 1000 * 0.12 = 1200
yearly depreciation for 2007 (Jul to Dec) = 1200/12 * 6 = 600 (because the prorate is 1-Jul-07)
this yearly depreciation should be divided by 6 periods (Jul to Dec) = 600/6 = 100
Depreciation in Jul-07 = 100