11i NEW FEATURES IN

FIXED ASSETS
An Oracle White Paper
February 2003

11i NEW FEATURES IN FIXED ASSETS

Overview .............................................................
Introduction ..........................................................................................................
Minipack 11i.FA.A (Patch No. 1345671) ........................................................
Bonus Rule Depreciation................................................................................
Bonus Rules Scenarios................................................................................
Bonus Rules Accounts................................................................................
Enhanced Unplanned Depreciation .........................................................
Major Features.............................................................................................
Re-Runnable Create Journal Entries ........................................................
Minipack 11i.FA.B (Patch No. 1405177) ........................................................
Amortize Net Book Value Over Remaining Useful Life...........................
Account Generator Enhancements ..............................................................
Including The Function .............................................................................
New Profile Options ..................................................................................
Minipack 11i.FAC (Patch No. 1483543) .........................................................
Future Effective Dated Asset Transactions Enhancement .......................
Future Transactions ....................................................................................
Minipack 11i.FA.D (Patch No. 1509971 ).......................................................
Mrc: Rollback Depreciation Enhancements For Mrc ................................
Minipack 11i.FA.E (Patch No. 1584277) ........................................................
Automatic Lease Payments: Payables Integration.......................................
New Messages For Tax Interface..................................................................
New Messages Needed For The Validation In Tax Book Upload Interface.
Enhancements To Transaction Approval....................................................
Rollback Depreciation Enhancements For Mrc Enabled Books .............
Enhancement To Add New Accounts To Fagda Processing ...................
Tax Interface Enhancement...........................................................................
Minipack 11i.FA.F (Patch No. 1794240).........................................................
Enhancement For Account Generator Errors............................................
New Message Fa_Post_Gl_Invalid_Period.................................................
Enhancement To The Discard/Purge Process Of A Hierarchy Batch...
New Tools Menu Function Security In Prepare Mass Additions ............
End User Steps To Disable 'Post All', 'Hold All', And 'Delete All':..
Asset Reclass Api For Network Logistics....................................................
Enhancement For Annual Rounding ...........................................................
Adding Mass External Retirements To Core Oracle Assets .....................
Minipack 11i.FA.H (Patch No. 2115788)........................................................
Enhancement To Mass Transfers To Accept Partial Values For 'To Expense Account'
Modifications To Transaction Approval......................................................
Minipack 11i.FA.I (Patch No.2117740)...........................................................

White Paper Title

4
4
4
4
5
5
5
6
7
8
8
8
8
9
10
10
10
11
11
11
11
12
12
12
13
13
14
14
14
15
15
15
15
16
17
17
18
18
18
18

Page 2

Creating One-Off Patch Of New Lease Forms..........................................

Implementing One-Step Rollback Journal Entries.....................................
Enhancing Basic Messaging ...........................................................................
Minipack 11i.FA.J (Patch No.2230269)...........................................................
Facility To Enter Sale Proceeds Or Cost Of Removals.............................
Fixing Vendor Sites Lov In Non-Multi-Org Setup ....................................
FA Depreciable Basis Features ......................................................................
Depreciable Basis Formula -- New Feature ............................................
New Message For Clarifying Large Rollback Segment ..............................
Minipack 11i.FA.K (Patch No.2398923) .........................................................
Parallelized Mass Transactions ......................................................................
New User Interface For Mass Retirements .................................................
Enhanced Mass Change..................................................................................
MRC Inquiry Window Hook To Financial Inquiry Form.........................
Depreciation Override Need..........................................................................
Depreciation Override -- New Feature....................................................
Conclusion.............................................................................................................

18
18
19
19
19
19
19
19
19
20
20
20
20
21
21
21
21

White Paper Title

Page 3

NEW FEATURES AT EACH MINIPACK LEVEL 11i

OVERVIEW

This White paper is intended for Analysts and users who would like to understand the new
features and/or enhancements added at each minipack level.
INTRODUCTION

Every minipack released by Oracle contains the solution to the bugs reported internally and by
the analysts but also includes the new features or enhancements to the existing features.
This White paper is intended to briefly describe the new features and enhancements at each
minipack level.
Minipack 11i.FA.G (patch no. 1974812) is obsoleted and replaced with 11i.FA.H (patch no.
2115788). Hence any new features or functionalities included in minipack G is discussed along
with Minipack H.
MINIPACK 11I.FA.A (PATCH NO. 1345671)
Bonus Rule Depreciation

Depreciation can be computed based on the Bonus Rule defined under Depreciation Method.
With the bonus rules enhancements, Oracle Assets will be able to support German Special
Depreciation
The Mass Change feature can now support Italian Accelerated Depreciation
Japanese Special Depreciation can also be supported with the enhancements made in this
minipack.
The following enhancements are covered:
Expansion of the situat ions in which Bonus Rules can be used.
Tracking Bonus Rule depreciation in separate accounts.

White Paper Title

Page 4

Bonus Rules Scenarios

The following uses of bonus rules are allowed:

You can use bonus rules with corporate books as well as tax books.
You can use bonus rules with straight-line and table-based depreciation methods.
You can use negative bonus rule rates.

Bonus Rules Accounts

You can set up Oracle Assets to charge bonus depreciation expense to a different account from
that of normal depreciation expense.
You can also set up Oracle Assets to charge accumulated depreciation from bonus rules to a
special bonus depreciation reserve account, instead of including it in the standard accumulated
depreciation account.

Enhanced Unplanned Depreciation

Unplanned depreciation is a feature used primarily to comply with special depreciation

accounting rules in Germany and the Netherlands. However, you also can use this feature to
handle unusual accounting situations in which you need to adjust the net book value and
accumulated depreciation amounts for an asset without affecting its cost.
In 11.0, unplanned depreciation is supported for the following methods:
Rate source

Depreciation Basis

STL

Cost

Flat

Cost

Production

N/A

With this minipack, Unplanned depreciation can now use Flat rate and NBV based methods as
well.
Alternative Flat Rate Depreciation Method?? Does this mean that we now support this
Depreciation method also, if so, add to statement above.

White Paper Title

Page 5

Major Features

Using Flat-rate methods, the calculation basis for the depreciation is set to the following :
Calculation
Basis

Timing

Amount

Cost

Initial

Recoverable Cost

Cost

After Expensed Adjustment

Recoverable Cost

Cost

After
Amortized
Adjustments
with No change (it will continue to
Amortization Start Date in current period
use the same amount that was
used before the adjustment).

Cost

After
Amortized
Adjustments
with NBV as of the amortization
Amortization Start Date not in current period start date

NBV

Initial

NBV

NBV

After Expensed Adjustment

NBV as of the current period

NBV

After
Amortized
Adjustments
with NBV as of the amortization
Amortization Start Date in current period
start date (current period)

NBV

After
Amortized
Adjustments
with NBV as of the amortization
Amortization Start Date not in current period start date

Once you enable this feature, the calculation basis will be modified to the following: - How do
you enable this feature?
Calculation
Basis

Timing

Amount

Cost

Initial

Recoverable Cost

Cost

After Expensed Adjustment

Recoverable Cost

Cost

After
Amortized
Adjustments
with Recoverable Cost
Amortization Start Date in current period

Cost

After
Amortized
Adjustments
with Recoverable Cost
Amortization Start Date not in current period

NBV

Initial

NBV (Recoverable Cost)

NBV

After Expensed Adjustment

NBV as of the beginning of

the current fiscal year

NBV

After
Amortized
Adjustments
with NBV as of the beginning of
Amortization Start Date in current period
the fiscal year of the
amortization start date

NBV

After
Amortized
Adjustments
with NBV as of the beginning of
Amortization Start Date not in current period
the fiscal year of the
i i
d

White Paper Title

Page 6

amortization start date

Re-runnable Create Journal Entries

Oracle Assets creates journal entries for depreciation expense, asset cost, and other accounts.
Oracle Assets automatically creates transaction journal entries for your general ledger, if you
have set up the journal entry category for that transaction type for that book.
Oracle Assets creates journal entries that summarize the activity for each account for each
transaction type. Oracle Assets allows you to run the Create Journal Entries program multiple
times before closing the depreciation period. You can post journal entries to Oracle General
Ledger for all transactions that have occurred thus far in an open depreciation period. If
additional transactions occur during the open period, you need to rerun Depreciation, then you
can rerun the Create Journal Entries program. Oracle Assets also allows you to roll back journal
entries in an open depreciation period, as long as those journals have not already been posted to
General Ledger. After you make the necessary adjustments, you run the Create Journal Entries
program once again and post the journals to General Ledger.

White Paper Title

Page 7

MINIPACK 11I.FA.B (PATCH NO. 1405177)

Amortize Net Book Value over Remaining Useful Life

Oracle Assets now supports straight-line depreciation over remaining useful life. This method
employs the net book value as the depreciable basis. Assets subjected to this method of
depreciation in legacy systems can continue to use this method in Oracle Assets. This feature
eliminates the effort of changing the cost basis during legacy asset data conversions.
Account Generator Enhancements
Including the Function

Oracle Assets uses Account Generator which is implemented using workflow rules and
procedures to generate code combinations for all the account types. Some of the account types
for which Oracle Assets creates code combinations are Asset Cost Account, Asset Clearing
Account, Depreciation Expense Account, and Depreciation Reserve Account etc. Oracle Assets
utilizes a concurrent program called Generate Accounts, which generates all the code
combinations for all the distributions in a book and stores it in a table called
FA_DISTRIBUTION_ACCOUNTS. Account Generator is called repeatedly to generate the
combinations for each account type and subsequently all transactions and concurrent programs,
such as Depreciation and Create Journal Entries, check if a combination already exists in
FA_DISTRIBUTION_ACCOUNTS and uses the combination if it exists.
There are performance issues associated with using Account Generator. Generate Accounts
was designed to alleviate the performance issues by retrieving the needed account from the
FA_DISTRIBUTION_ACCOUNTS table instead of calling Workflow for each transaction. It
can be run ahead of critical month end processes thereby significantly speeding up month end
close. The code to generate code combinations using Account Generator in Oracle Assets is
contained in the package FA_GCCID_PKG, which is shipped in the file FAFBGCB.pls. This
package contains a function called fafbgcc, which calls the workflow process to generate code
combinations. Oracle Assets will now provide a PL/SQL package and stub function, which a
customer can modify to generate code combinations without using Account Generator.
A profile option, FA: Use FA_CUSTOM_GEN_CCID_PKG to Generate CCID, when
enabled will allow FA_GCCID_PKG.fafbgcc to call the stub package instead of calling Oracle's
Workflow to generate code combinations. All the logic required to generate a code combination
must be placed in this stub package. No changes must be made to the logic in
FA_GCCID_PKG.

White Paper Title

Page 8

New Profile Options

FA: Use Recoverable Cost for FLAT rate COST based method
FA:Generate Asset Level Account
FA:Generate Book Level Accounts
FA:Generate Category Level Accounts

FA: Use Recoverable Cost for FLAT rate COST based method

Setting the Profile Option to 'YES' at the Application Level will result in Recoverable Cost
being used for depreciation calculation for dated amortized adjustments and as the depreciable
basis for periodic depreciation for assets assigned to a FLAT rate COST based method. When
this profile option is not set or set to 'NO', Oracle Assets will set the depreciable basis to the
Net Book Value, which is the standard functionality without this profile option.
Only when the profile is set to 'YES' will Recoverable Cost be used as depreciable basis. Be
sure that setting this meets your requirements. Once you set this profile option to 'YES', this
should not be changed. Otherwise recoverable cost or net book value will be used as the
depreciable interchangeably based on the value of the profile at the time of the adjustment. This
is not desirable and must not be done.
This is relevant for FLAT rate COST based methods and amortized adjustments on assets
assigned to such methods.
FA:Generate Asset Level Account
FA:Generate Book Level Accounts
FA:Generate Category Level Accounts

Setting any of these profiles to 'NO' will prevent the Generate Accounts Program FAGDA)
from pre-generating any of the associated accounts. In general, they should be left NULL or set
to 'YES'. The value 'NO' should only be used in cases where the FA Workflow has been
customized so that one or more accounts for a single asset and distribution may change over
time. For example, when a segment value is determined by an asset's retirement type which can
not be known at the time of addition.
NOTE: Excluding one or more account types from processing by the Generate Accounts
program will have significant performance impacts as Workflow will be called for each account
as needed. This is especially important in the case of mass transactions and batch processing
such as Depreciation. By default, these profiles should be left as NULL or set to 'YES'.

White Paper Title

Page 9

MINIPACK 11I.FA.C (PATCH NO. 1483543)

FUTURE EFFECTIVE DATED ASSET TRANSACTIONS ENHANCEMENT

Future Transactions

Oracle Assets supports one open asset accounting period. However, Oracle Assets allows you to
enter transactions for future accounting periods. When you enter a future transaction, it is
temporarily stored in the FA_MASS_ADDITIONS interface table. This pending transaction
does not become effective until the transaction date for the transaction is within the current
open period in Oracle Assets. For example, if the current open period is May 2000, and you
enter an adjustment transaction with a transaction date of 01-Sep-2000, the transaction does not
become effective until Sep-2000 is the current open period.
When you open a new accounting period, the Process Pending Transactions concurrent
program runs and automatically processes all pending transactions with a transaction date that
falls within the open period. You do not need to enter any further transaction detail to complete
the transaction in the effective open period.
The Process Pending Transactions program looks up the transaction date of each pending
transaction. If the transaction date falls within the current open period of the corporate book,
the program processes that transaction. Any exceptions are written to the log file.
It is not necessary to enter future transactions in chronological order. The Process Pending
Transactions program automatically processes pending transactions in chronological order.
You can also add assets from invoice lines from Oracle Payables, and provide a future date
placed in service. These invoices must first be posted to future General Ledger periods from
Oracle Payables and satisfy all other mass addition criteria to be successfully interfaced from
Oracle Payables to Oracle Assets.

Refer Note : 125950.1

In the Mass Additions Prepare (FAXMADDS) form, it now gives customers the option to enter
future lines. The Mass Additions Post (FAMAPT) program will only pick up lines in the current
period. So, Development has added an additional Mass Addition Post job in the Depreciation
request set. When Depreciation runs and opens the next period, a Mass Additions Post job will
automatically be submitted.

White Paper Title

Page 10

This additional Mass Additions Post program is the Process Pending Transactions (FAPPT)
program.
Refer : Oracle Assets Future Transactions Documentation Supplement

MINIPACK 11I.FA.D (PATCH NO. 1509971 )

MRC: ROLLBACK DEPRECIATION ENHANCEMENTS FOR MRC

In order to run depreciation in the primary set of books in a MRC environment, it is necessary
to run depreciation and close the period in the reporting sets of books. Once the period is
closed, the customer is unable to rollback depreciation. It is a very common situation that a
customer would not know that he needed to rollback depreciation in his reporting set of books
until he ran depreciation in his primary set of books. So we need the ability to be able to
rollback depreciation in all sets of books prior to closing the primary set of books period

MINIPACK 11I.FA.E (PATCH NO. 1584277)

AUTOMATIC LEASE PAYMENTS: PAYABLES INTEGRATION

Manage your asset leases from Oracle Assets to ensure on-time payments. You can select
specific payment lines for multiple leases and export them to the Oracle Payables system. You
also have the flexibility to direct these payments to different accounts at the payment line level.
The basic functionality of Automatic Lease Payments is to enable users to integrate the Oracle
Assets Lease Payments information with Oracle Accounts Payable. By automating the lease
payment functionality, users can more accurately and easily manage lease payments and reduce
cost by eliminating administrative overhead.
Automatic Lease Payments implementation requires Oracle Forms 6 for modifications to the
Lease forms, Rxi reports and Oracle Reports for preview and review reports, and a PL/SQL
program to populate information from Oracle Assets into Accounts Payable interface tables.
Once the information is added to their tables, Accounts Payable can run the AP Invoice Import
program and the invoices are created.
Automatic Lease Payments for Oracle Assets fits into the following business flow:

White Paper Title

Page 11

Setup Lease

Create new asset &

associate with lease

Setup lease payment

schedule

Send lease
payment info to
AP for invoice
creation each
period

Figure 1 : Automatic Lease Payaments for Oracle Assets

NEW MESSAGES FOR TAX INTERFACE

New messages needed for the validation in Tax Book Upload Interface.

FA_NO_ITC_FOR_CEILING - You cannot use an ITC ceiling without assigning ITC.

FA_NO_RESERVE_FOR_PROD - You cannot upload ytd or reserve information for UOP
assets.
FA_NO_TAX_UPLOAD_CIP - You cannot upload tax information for CIP assets.
FA_NO_TAX_UPLOAD_DEPRN_ASSETS - You cannot upload tax information for assets,
which have been depreciated.
FA_NO_RSV_IN_FIRST_PERIOD - You cannot assign reserve to an asset with a DPIS in the
current period.
FA_NO_BONUS_WITH_NON_FLAT - You cannot assign bonus rules to assets using nonflat methods.
FA_EXP_CEILING_NOT_ALLOWED - You cannot assign an expense ceiling as they are
not allowed in this book.
FA_INVALID_BONUS_RULE - Unable to select bonus rule from FA_BONUS_RULES
FA_ASSET_NUMBER_NOT_EXIST - The asset number specified can not be found in
FA_ADDITIONS.
FA_TAXUP_GET_ASSET_INFO -Tax upload failed to select financial information for this
asset.
FA_NO_ITC_CEILINGS- ITC ceilings are not allowed for this category.
FA_TAXUP_ASSET_SUCCESS -Asset number: &NUMBER processed.
FA_TAXUP_ASSET_FAILURE - Asset number: &NUMBER ===> ***FAILED***.
FA_AMORT_DATE_LESS_CONV_DATE - For short tax year assets, the amortization date
must fall after the conversion date.
FA_CACHE_ITC_RATES - Error retrieving ITC rate information.

ENHANCEMENTS TO TRANSACTION APPROVAL

White Paper Title

Page 12

Previously, transactions could be performed on CIP assets where associated tax books allowed
the cip-in-tax feature even if those tax book had processes running on them. This created a
problem (It effects only 11.0 and 11i) and was resolved in this minipack by disallowing
transactions to be performed when processes were running.

ROLLBACK DEPRECIATION ENHANCEMENTS FOR MRC ENABLED BOOKS

MRC-enabled customers can now utilize the rollback depreciation functionality in both primary
and reporting books. One-step processing must be used to use the new functionality. The
depreciation run form's restriction that disallows depreciation to be run on the primary book if
the reporting has not been closed is still in effect. General one-step processing is detailed in a
document located under the MRC technical libraries section on Metalink.
In short, the new functionality works as follows:
1) Run the one-step depreciation process "MRC: Depreciation Run in all sets of books" on a
given book (selecting 'No' for the close period parameter). This will run depreciation without
closing the books on all reporting and primary books.
2) At this point, you can review reports, etc. Should you choose to rollback depreciation for any
reason including corrective or additional transactions, simply run the one-step rollback process
"MRC: Rollback Depreciation in all sets of books". Primary and reporting books will now be
back at their pre-depreciation run state. Transactions can be performed before depreciation is
run again. These steps can be performed as many times as desired until any of the reporting
books have depreciation submitted with the close_period parameter set to 'Yes'. At that point,
you will be unable to perform any transactions until the remaining reporting books as well as the
primary are closed and the periods are again in sync.

ENHANCEMENT TO ADD NEW ACCOUNTS TO FAGDA PROCESSING

Account Generator builds the general ledger account combinations used to generate the general
ledger journals by Oracle Assets. The enhanced messaging capability helps you troubleshoot
problems encountered during the process, such as invalid account segments. Online error
messages precisely indicate the Asset Book, Account Type, Concatenated Segments and
Distribution information necessary for troubleshooting.
The profile option FA: Print Debug must be turned on for these messages to appear in the
logfile or on the form.
New accounts like Bonus Expense & Bonus Reserve have not been added in FAGDA. Also,
the deferred_deprn_reserve, deferred_deprn_expense, deprn_adjustment accounts have been
added.

White Paper Title

Page 13

TAX INTERFACE ENHANCEMENT

The basic functionality of the Tax Book Upload Interface is to enable users, consultants and
other implementation specialists to upload values into the tax books that are not handled by
Mass Copy. Also, the new functionality will enable users to manage situations where different
values are required in the corporate book and the tax book. Since we are now enabling different
cost values to be maintained in the corporate book and tax book, we need to modify Periodic
Mass Copy by removing the current restriction that requires cost to be the same in both books
in order for PMC to occur.
The Tax Book Upload Interface implementation will not require Oracle Forms: no form will be
created for this feature.
The new interface table created from the
FA_SHORT_TAX_RESERVES table will be called FA_TAX_INTERFACE. Users will be
expected to populate this table via SQL*PLUS or SQL*LOADER, as there will be no form to
access FA_TAX_INTERFACE otherwise. A concurrent request will also be created and
identified as the Upload Tax Book Information process in the Submit Requests Screen. This
concurrent request will simply be a PL/SQL program that uploads the information in
FA_TAX_INTERFACE into FA_BOOKS.

The Tax Book Upload Interface feature fits into the following flow:

Setup Corp Book

and Assets

Run Depreciation

Mass Copy
to Tax Book

Tax Book Information is now

uploaded from the interface table
into the appropriate tax book

Using SQL,
populate the
tax interface table

Run the Upload Tax Book Information

Concurrent Process

Figure 2 Tax Book Upload Interface

MINIPACK 11I.FA.F (PATCH NO. 1794240)

ENHANCEMENT FOR ACCOUNT GENERATOR ERRORS

This minipack enhances error handling when Account Generator errors in PL/SQL based
programs and form level transactions.
Additional error messaging was desired to make diagnosing flex failures easier. Displaying the
XVAL rule being violated or the disabled segment as well as the concatenated segments are just
a few of the new examples of the new error messaging..

White Paper Title

Page 14

<remove paragraph not needed>

NEW MESSAGE FA_POST_GL_INVALID_PERIOD

Created the following which will be displayed in the event that the period specified doesn't exist
or is not postable.
NAME:

FA_POST_GL_INVALID_PERIOD

Text: The specified period is not a postable period in GL. The period must exist in the
associated set of books and the status must either be Open or Future Enterable.
ENHANCEMENT TO THE DISCARD/PURGE PROCESS OF A HIERARCHY BATCH

Review hierarchy batch screen gets locked for Discard of larger batches. The form updates the
batch details to discarded, through the Review Hierarchy Batches form. This locked the form
for very large batches. Now the user only updates the batch header to discarded. Then they run
a separate Purge process to purge the batch details for the discarded batch headers.
NEW TOOLS MENU FUNCTION SECURITY IN PREPARE MASS ADDITIONS

Implemented in Prepare Mass Additions form, logic that can help customers enable or disable
the three options 'POST ALL', 'HOLD,ALL, 'DELETE ALL' in the tools menu .The
functionality is dependant on data setup in AOL's functions-, menus- and responsibility-forms.
Default logic is that the three options always are enabled. The three functions are already added
to the Form Functions form found under the Application Developers responsibility and these
are:
-FAX_FAXMADDS_POST_ALL
-FAX_FAXMADDS_HOLD_ALL
- FAX_FAXMADDS_DELETE_ALL
- These three functions are added to the FA_MASS_ADDITIONS menu (and also to
CRL_MASS_ADDITIONS menu for CRL).
- Prepare Mass Additions form is modified to take advantage of these functions.

END USER STEPS TO DISABLE 'POST ALL', 'HOLD ALL', and 'DELETE ALL':
Steps to restrict access to any of the three Tools menu options 'Post All',

'Hold All', 'Delete All' (note, all three are enabled by default):
Login to application using the System Administrator's responsibility.

White Paper Title

Page 15

- Navigate to the Define Responsibilities form through the menu path

Security/Responsibility/Define
- Query up the responsibility that you want to restrict access to. For instance: "Fixed Assets
Manager".
- Under the Menu Exclusions tab, choose Type=Function and enter the name of the function
you want to disable. For instance: "Mass Additions: Delete All".
- Then Save.
Login to the responsibility and navigate to the Prepare Mass Additions form. Enter the Mass
Additions main window; clicking on the Tools menu should now reflect the intended changes.
In our example the Delete All option, should be disabled.

ASSET RECLASS API FOR NETWORK LOGISTICS

This is a new enhancement where a customer can reclass an asset through an API. This is in
addition to reclassing an asset through the Application.
The major features of this API are:
PL/SQL API: FA_MODIFY_CATEGORY_PKG.modify_category()
Ability to automate reclass transactions instead of needing to manually perform the transactions
through Oracle Applications.
Option to include or exclude fully reserved assets to reclassed.
Option to copy the category descriptive flexfield from the old category of the asset to the new
category.
Option for the asset to inherit the default depreciation rules of the new category.
Option to treat the reclass as either an amortized adjustment or an expensed adjustment.
The API will have the following limitations:
The user will NOT be able to do prior period reclasses.
Reclasses will only be able to be performed on corporate books and not tax books.
The API only processes one asset at a time. It will process a range of assets.
The API only accepts internal IDs for the asset parameters and category parameters. The user
of the interface must derive the correct asset_id and category_id instead of using asset_number,
category, or any other descriptive field.
The API does not support using global flexfield information in the transaction.

White Paper Title

Page 16

When determining whether to use the option to copy the category descriptive flexfield
information from the old category to the new one, the user of the interface must be aware of the
following scenarios:
1. The category descriptive flexfield is required for the new category and was not required for
the old category and was not populated for the old category.
2. The category descriptive flexfield was not setup in the new category or was setup in a
different way than the old category descriptive flexfield. (For example, there may be three
segments in the old category but only two segments in the new category.)
3. When copying from the old category to the new category, the category flexfield information
no longer makes sense from a functional standpoint. For example, copying the license
information from a CAR category to the acres field in the LAND category may not make sense.
Depending on the exact scenario, some of the transactions will error while others will be
successful even if the information no longer makes sense from a business standpoint. At this
point, it is the users' of the interfaces responsibility for the validity of the information in the
flexfield and their responsibility to make the user aware of this possibility.

ENHANCEMENT FOR ANNUAL DEPRN ROUNDING

fadpdp.lpc ,FACDES.pls, FACDEB.pls files were changed to enable annual variance rounding
for all cases; including the assets which have gone through adjustments, transfers, revaluations
and so on. The annual rounding is now available for projections and what-if analysis.
ADDING MASS EXTERNAL RETIREMENTS TO CORE ORACLE ASSETS

Oracle Assets allows you to perform mass retirements on a set of assets by populating an
external interface table with these assets and processing them in a batch. To use the Mass
External Retirements feature, you need to install minipack F.
Submit the Post Mass External Retirements concurrent process. Oracle Assets does not allow
partial unit retirements and can only be grouped using a Batch Number, which restricts you
from fully utilizing the benefit of the Oracle Assets Mass Retirements features. Oracle Assets
does allow partial cost retirements.
Added the Mass External Retirements functionality to Oracle Assets core functionality, through
adding access to the Prepare External Retirements" form from the Mass Transactions submenu
and providing access to the Post Mass External Retirements program from the Submit Requests
form. We've added the concurrent program to Assets requests groups, and added menu entries
to the FA_MASS_TRX submenu.

White Paper Title

Page 17

MINIPACK 11I.FA.H (PATCH NO. 2115788)

ENHANCEMENT TO MASS TRANSFERS TO ACCEPT PARTIAL VALUES FOR 'TO EXPENSE

ACCOUNT'

This enhancement requires the 'Expense Account To' field in the Mass Transfer form to accept
valid individual segment values and treat these as the range/selection criteria when assigning
accounts. If the new combination does not exist, then create one if dynamic insertion is turned
on.
MODIFICATIONS TO TRANSACTION APPROVAL

Enhancement to streamline transaction approval more. When we created the faxcrb function for
reporting books, it was a bit simplistic in that it only checked the overall book status. It did not
perform specific checks based on whether it was an asset/mass transaction. Added asset_id and
close_period flags as parameters so that only the relevant checks are performed for a given call

MINIPACK 11I.FA.I (PATCH NO.2117740)

CREATING ONE-OFF PATCH OF NEW LEASE FORMS

This patch has been created to resolve wrong Key Flex Num handling in 'Lease Details' and
'Lease Payment Push to Payables' forms.
A number of Multi-ORG related issues which occurred in Lease Details form and
Lease Payment Push To Payables form have been resolved.

IMPLEMENTING ONE-STEP ROLLBACK JOURNAL ENTRIES

We one-stepped create journals, but as the rollback journals process was a feature added post
11i, it was not immediate one-stepped and thus users would have to rollback for each primary
and reporting book via individual responsibilities This needs more detailed explanation
customers will not know what one-stepped means.
In this patch a new procedure has been added to the one-step package to rollback journals in all
Sets of Books

White Paper Title

Page 18

ENHANCING BASIC MESSAGING

Improvements have been made to the text of the common FA error message stack. New
enhancements have been provided so as to provide the user with more understandable error
messages.

MINIPACK 11I.FA.J (PATCH NO.2230269)

FACILITY TO ENTER SALE PROCEEDS OR COST OF REMOVALS

The functionality to enter Proceeds of Sale and Cost of Removal has been added and processes
similar to that of Mass Retirements. These amounts are prorated based on the cost retired for
the assets in the Hierarchy Retirement Batch.

FIXING VENDOR SITES LOV IN NON-MULTI-ORG SETUP

A fix was created to correct the vendor sites LOV issue in non-multi-org setup
When multi-org is not set up, there is no default organization id populated in the vendor sites
table. This behavior is different from that of multi-org setup. Hence, enhancements have been
made so as to provide for non-multi-org configuration within the vendor site record group.

FA DEPRECIABLE BASIS FEATURES

Depreciable Basis Formula -- New feature

This feature is provided to apply special rules to the depreciation. You use the Depreciation
Methods window to apply the depreciable basis rule when you setup the depreciation methods.
When you create the transactions, the depreciable basis of the asset is calculated following
depreciable basis rules. This feature is provided only for Flat Based-Method and the provided
rules are only for Japan.
NEW MESSAGE FOR CLARIFYING LARGE ROLLBACK SEGMENT

A new warning message has been added for instances when the System Profile option FA: Large
Rollback Segment is not set. The new message says that the user can ignore the error, and any

White Paper Title

Page 19

previous related error messages, because this is just a warning that the profile option is not set.
These messages do not indicate a failure in this concurrent program. Rather, they just indicate
that FND was unable to retrieve a value from the large rollback profile option, and that no
explicit rollback segment will be used.
MINIPACK 11I.FA.K (PATCH NO.2398923)

Parallelized Mass Transactions

Speed up processing time by taking advantage of multiple parallel processors when performing a
mass transaction. Specify how many processors you have, and when you run any mass
transaction, it will automatically be split across those processors. This can be done with Mass
Additions, Generate Accounts, Depreciation, and has been enabled for the following mass
transaction processes:
Mass Copy
Mass Retirement
Mass Transfer
Calculate Gains and Losses
Mass Reclassification
Mass Change
Upload Tax Book Interface

New User Interface for Mass Retirements

Mass Retirements now offers more versatile features. Create and review mass retirements and
reinstatements before actually posting them to the system. This allows more flexibility and
accuracy when performing mass retirements and reinstatements.

Enhanced Mass Change

You can now perform backdated amortized adjustments through the Mass Change form and
Mass Copy Continue Despite Errors. Mass Copy will now continue processing all included
assets as specified by the user despite errors. The program will list all those transactions, which
fail to be copied and allow the user to make corrections on the failed transactions.

White Paper Title

Page 20

MRC INQUIRY WINDOW HOOK TO FINANCIAL INQUIRY FORM

New Currency detail window to Financial Inquiry form, accessible from the books window tools
menu, that displays reporting books amounts.
In the books window, when reporting books exists, access to the new window is from the tools
menu. There is also an icon enabled on the toolbar. The new window show same data as
normally is viewed from the financial inquiry form from a reporting responsibility. The purpose
is that reporting books data can be viewed without switching responsibility.

DEPRECIATION OVERRIDE NEED

Depreciation Override -- New feature.

This feature allows users to manually override the system calculated depreciation amounts and
bonus amounts with the amounts users provided in the interface table.
This feature is enabled only when the profile option "FA: Enable Depreciation Override" is set
to 'Yes'.
Users can override the depreciation and bonus amounts for depreciations, projections, what-if
analysis and adjustments. But for amortized adjustments, bonus amounts cannot be applied
because of the current FA design.
CONCLUSION

This white paper will be re-visited by the authors if required, after a new minipack is being
released.

White Paper Title

Page 21

11i New Features

February 8, 2003
Authors: Sridhar Yelisetty, G. Hari Narayanan, Swati Malik and Muralidharan Raghavan
Contributing Authors:
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065
U.S.A.
Worldwide Inquiries:
Phone: +1.650.506.7000
Fax: +1.650.506.7200
www.oracle.com
Oracle is a registered trademark of Oracle Corporation. Various
product and service names referenced herein may be trademarks
of Oracle Corporation. All other product and service names
mentioned may be trademarks of their respective owners.
Copyright 2001 Oracle Corporation
All rights reserved.