Loading Your Asset Data
This section describes how to define, load, and confirm your interim asset table. In many cases you have to load asset information into the Oracle7 tables from a non-Oracle file system. This section shows you how to use SQL*Loader to import your information. Complete the following steps to load your asset data:
Note: If you are using Multiple Reporting Currencies (MRC), when loading the FA_MASS_ADDITIONS table with data from a legacy system (a feeder system other than Oracle Payables or Oracle Projects), you must also load the FA_MC_MASS_RATES table. For each mass addition line in FA_MASS_ADDITIONS, you need to provide exchange rate information in the FA_MC_MASS_RATES table for each reporting set of books associated with the corporate book into which the assets will be added. See: Multiple Reporting Currencies in Oracle Applications.
1. Define your interim table in the Oracle database.
Use a single interim table if possible. You can use multiple tables if the data exists in multiple tables or files in the old asset system. In either case, you must eventually place the data in a single table, the FA_MASS_ADDITIONS table.
If you wish, you may load data directly into FA_MASS_ADDITIONS, but it is more difficult due to the complexity of the table.
2. Load your interim table (Using SQL*Loader if asset data is external).
Use SQL*Loader to import information from outside your Oracle database. SQL*Loader accepts a number of input file formats and loads your old asset data into your interim table.
If the data already resides within an Oracle database, there is no need to use SQL*Loader. Simply consolidate the asset information in your interim table using SQL*Plus or import, and go directly to the next step.
Follow these steps if you plan to use SQL*Loader:
- Get the asset information in text form
Most database or file systems can output data in text form. Usually you can generate a variable or fixed format data file containing comma or space delimiters from the existing system. If you can't find a way to produce clean text data, try generating a report to disk, using a text editor to format your data. Another option is to have SQL*Loader eliminate unnecessary information during its run. If there is a large volume of information, or if the information is difficult to get in a loadable format, you can write your own import program. Construct your program to generate a SQL*Loader readable text file.
- Create the SQL*Loader control file
In addition to the actual data text file, you must write a SQL*Loader control file. The control file tells SQL*Loader how to import the data into your interim table. Be sure to specify a discard file if you are planning to use SQL*Loader to filter your data.
- Run SQL*Loader to import your asset data
Once you have created your asset data file and SQL*Loader control file, run SQL*Loader to import your data. SQL*Loader produces a log file with statistics about the import, a bad file containing records that could not be imported due to errors, and a discard file containing all the records which were filtered out of the import by commands placed in the control file.
3. Compare record counts and check the SQL*Loader files.
Check the number of rows in the interim table against the number of records in your original asset data file or table to ensure that all asset records are imported.
The log file shows if records were rejected during the load, and the bad file shows which records were rejected. Fix and re-import the records in the bad file.
4. Spot check interim table.
Check several records throughout the interim table and compare them to the corresponding records in the original asset data file or table. Look for missing or invalid data. This step ensures that your data was imported into the correct columns and that all columns were imported.
See Also
About the Mass Additions Interface
Planning Your Import
Defining Oracle Assets for Mass Additions
FA_MASS_ADDITIONS Interface Table
Importing Your Asset Information
Finishing Your Import
