Importing Your Asset Information
During this phase, use SQL*Plus to move your asset data into the FA_MASS_ADDITIONS table. Run the Mass Additions Status Report and the Unposted Mass Additions Report to check your data. Then prepare the assets using Prepare Mass Additions if necessary and post them using Mass Additions Post.
Once you have set up Oracle Assets, you are ready to import your asset information.
If you are importing asset information from another payables system, load the FA_MASS_ADDITIONS table directly. Then use Prepare Mass Additions and Mass Additions Post to add your assets to Oracle Assets.
If you are converting asset information from another assets system, use SQL*Plus to move the asset information from the interim table into the FA_MASS_ADDITIONS table. After you load and confirm the FA_MASS_ADDITIONS table, run Mass Additions Post to post your assets to Oracle Assets.
1. Load you asset data into the FA_MASS_ADDITIONS table.
You use SQL*Plus to load your asset information into the FA_MASS_ADDITIONS table from the interim table. Be sure to check the table after each SQL*Plus script to ensure that the script updated the table correctly. Also load the LAST_UPDATE_
DATE column and all the other columns that are the same for all your assets.
Suggestion: Load your data into the FA_MASS_ADDITIONS table in stages, posting and cleaning the table, to avoid exceeding tablespace allocations.
2. Load expense code combination IDs.
Use SQL*Plus to match expense account information in your interim table with the correct segments of the GL_CODE_COMBINATIONS table. To do this, you must first determine the mapping between segment numbers and segment names. Find the name of your chart of accounts using the Define Set of Books window to query on the set of books that you entered for the depreciation book in the Book Controls window. When you know the chart of accounts, perform the following SQL*Plus script:
select segment_name, application_column_name
from fnd_id_flex_segments
where id_flex_code = 'GL#'
and enabled_flag = 'Y'
and id_flex_num in (
select id_flex_num
from fnd_id_flex_structures
where id_flex_structure_name =
Your Chart of Accounts Name
and id_flex_code = 'GL#')
Match the information you have in the interim table with the appropriate segments to determine the correct code combination id for each asset. You might have only an account in your interim table, or you might have a company, division, and cost center that you need to match with segments in the GL_CODE_COMBINATIONS table. Make certain that your SQL*Plus script selects only one code combination id for each asset.
You can create the combinations you need using the Account Flexfield Combinations window.
The asset category determines many of the accounts to which each asset belongs. The category and date placed in service also determine the depreciation method, prorate convention, and other depreciation rules for the asset based on default values you defined for each category. Unless the interim table contains explicit information about the category to which each asset belongs, you must use all the information you have about each asset to determine its category. Asset account and reserve account are often useful in determining an asset's major category.
You need to determine the name of the category flexfield structure using the System Controls window. When you know the name of the category flexfield, perform the following SQL*Plus script:
select segment_name, application_column_name
from fnd_id_flex_segments
where id_flex_code = 'CAT#'
and enabled_flag = 'Y'
and id_flex_num in (
select id_flex_num
from fnd_id_flex_structures
where id_flex_structure_name =
Your Category Flexfield Name
and id_flex_code = 'CAT#')
Match the information you have with the corresponding columns in the FA_CATEGORIES table, the FA_CATEGORY_BOOKS table, and the FA_CATEGORY_BOOK_DEFAULTS table. These tables join using the CATEGORY_ID column in each. The FA_CATEGORY_BOOKS table contains information about a category that is specific to a book, e.g. accounts. The FA_CATEGORY_BOOK_DEFAULTS table contains information about a category that is specific to a book and date placed in service range, e.g. depreciation method. The FA_CATEGORIES table contains information about a category that is common for all books, including the category flexfield segment values. You can match on segments the same way you do for the Expense Code Combination ID if you have enough information in the interim table.
You can set up categories using the Asset Categories window.
Use SQL*Plus to match location information in your interim table with the location segments in the FA_LOCATIONS table. To do this, you need to determine the mapping between segment names and segment numbers. Determine the name of the location flexfield structure you defined on the System Controls window and then perform the following SQL*Plus script:
select segment_name, application_column_name
from fnd_id_flex_segments
where id_flex_code = 'LOC#'
and enabled_flag = 'Y'
and id_flex_num in (
select id_flex_num
from fnd_id_flex_structures
where id_flex_structure_name =
Your Location Flexfield Name
and id_flex_code = 'LOC#')
Match the location information in your interim table with the location segments in the FA_LOCATIONS table. Load the LOCATION_ID of the matching location record into the FA_MASS_ADDITIONS table. Be certain you select only one location id for each asset.
You can set up locations using the Locations window.
5. Load supplier information.
If you have supplier information for your assets, use SQL*Plus to match the supplier name in the interim table with the PO_VENDOR_NAME column in the PO_VENDORS table. Load the PO_VENDOR_ID of the matching record into the FA_MASS_ADDITIONS table.
You need to set up suppliers in the Suppliers window if you are not using Oracle Payables or Oracle Purchasing. Note that PO_VENDOR_ID is the unique internal identifier, and not the same as the external identifier supplier number.
6. Prepare mass additions for posting.
Once the FA_MASS_ADDITIONS table is loaded, you must change the POSTING_STATUS column to HOLD for any assets that have a date placed in service after the end of the conversion period. For most conversions, the conversion period is the last period of the previous fiscal year.
When you are ready to post the FA_MASS_ADDITIONS table, use the Send Mass Additions to Oracle Asset program to run Mass Additions Post. This program moves your assets into Oracle Assets.
Run the Mass Additions Status Report to see the results. Compare this report with the expected results, and investigate missing or incomplete items. Check the PERIOD_FULLY_RESERVED column in FA_BOOKS for fully reserved assets.
For assets that you placed in service after the conversion period, you can run Mass Additions Post after you have opened the appropriate period. For example, if your fiscal year ends December 31, December is your conversion period. If you have some assets that you placed in service in January, set the posting status to ON HOLD for the January assets while you post the first time. After you run depreciation for December, then you set the posting status of the January assets to POST and run Mass Additions Post again.
During this step you fix all the exceptions which were not properly imported using Mass Additions. You only need to perform these steps if they apply to your import:
- Assets With Multiple Distributions:
If you want some of your assets to have multiple distribution lines, then you need to use the Assignments window to correct the distribution information for each of these assets.
- Assets With Investment Tax Credits:
After you have posted your assets with Mass Additions, use the Assign Investment Tax Credit window to add ITC information.
- Leased Assets And Leasehold Improvements:
After you have posted your assets with Mass Additions Post, use the Asset Details window to add leasing information for your leased assets and your leasehold improvements. Verify that the life of your leasehold improvements is correct when you run depreciation.
- Assets With Parent Or Child Assets:
After you have posted your assets using Mass Additions Post, use the Asset Details to add parent asset information to each child asset.
- Units of Production Assets:
If you want to load a large number of units of production assets, please use the production interface instead of the mass additions interface. See: Using the Production Interface
See Also
About the Mass Additions Interface
Planning Your Import
Defining Oracle Assets for Mass Additions
FA_MASS_ADDITIONS Interface Table
Loading Your Asset Data
Finishing Your Import
