ORACLE APPLICATIONS

WHITE PAPER

MASS ADDITIONS

Product Design and Architecture

White paperMass Oracle/Client Confidential - For internal use only

ii

Contributors

Name Position

Nancy A. Lanning Sr. Technical Analyst, Fixed Assets Support,Orlando

Change Record

Author

Version

Change Reference

White paperMass Oracle/Client Confidential - For internal use only

iii

Contents

INTRODUCTION ............................................................................................................................ 1Objective.................................................................................................................................. 1Scope ....................................................................................................................................... 1Background.............................................................................................................................. 1

THE BIG PICTURE......................................................................................................................... 2CREATE MASS ADDITIONS (FAMACR)......................................................................................... 3EXTERNAL SOURCES .................................................................................................................... 4PREPARE MASS ADDITIONS (FAXMADDS) .................................................................................. 5POST MASS ADDITIONS (FAMAPT).............................................................................................. 6

Behind The Scenes ................................................................................................................... 6DELETE MASS ADDITIONS (FAXMADEL).................................................................................... 7PURGE MASS ADDITIONS (FAXMAPUR)...................................................................................... 8MASS ADDITIONS REPORTS .......................................................................................................... 9INFORMATION SOURCES ............................................................................................................. 10

White paper Introduction 1Mass Oracle/Client Confidential - For internal use only

Introduction

Objective

To provide an overview of the Mass Additions Process in Fixed Assetswith the hopes of giving the reader a good understanding of the differentsteps involved in Mass Additions.

Scope

This paper will cover the functional and technical side of Mass Additions.It will describe the steps of Create Mass Additions, Prepare MassAdditions, Post Mass Additions, Delete Mass Additions and Purge MassAdditions. It will show you the reports that are available within OracleAssets to help you in these processes.

Background

Mass Additions consists of five separate programs. Three of theseprograms (Create, Prepare, and Post) were all designed for inputting thedata and then massaging the data to get it in the correct format so that itcan be posted in Oracle Assets to become an Asset. The Delete and PurgeMass Additions programs were designed as a cleanup mechanism for theFA_MASS_ADDITIONS table.

White paper The Big PictureMass Oracle/Client Confidential - For internal use only

2

The Big Picture

Data can come into Oracle Assets via the FA_MASS_ADDITIONS tablefrom the following sources: external sources (i.e. legacy systems), ProjectAccounting (PA), Accounts Payable (AP). Once the data is in theFA_MASS_ADDITIONS table, the user must then perform Prepare MassAdditions on the data to add additional information such as the expenseaccount, location, etc., After the Prepare Mass Additions has beenperformed, the data can then be posted in Oracle Assets. After Post MassAdditions has completed, the data is then considered to be a true asset.There are Delete and Purge Mass Additions programs that can be used tocleanup the data from the FA_MASS_ADDITIONS table

White paper Create Mass Additions (FAMACR)Mass Oracle/Client Confidential - For internal use only

3

Create Mass Additions (FAMACR)

The Mass Additions Create Program (FAMACR) is submitted fromAccounts Payable (AP). From Project Accounting (PA), the InterfaceAssets process (PAXCPCAL) calls the Mass Additions Create Program.

When assets are created from AP they are created from invoice distributionlines and associated discounts. You can enter purchase orders in OraclePurchasing and receive invoices in Oracle Payables. When you want toimport invoice lines from a new invoice entered in Oracle Payables, youmust charge the distribution to a clearing account that is already assignedto an asset category. You can also easily integrate Oracle Assets withother Payables systems.

The assets created from PA are created from capitalized project lines. Youcan track all expenses during construction and capitalize completedprojects. You process construction-in-process (CIP) assets by adding,building and capitalizing them. CIP assets are not ready for use becausethey are still being built and are non-depreciable. CIP assets can only beadded to Corporate books.

The data is inserted into the FA_MASS_ADDITIONS table. This tableacts as an interface for the Oracle Assets product. The asset lines that aresent to Oracle Assets are inserted as one mass addition line. Once the dataresides in this table, the Post component can then be used to move the assetinformation from the FA_MASS_ADDITIONS table to Oracle Assets.You can then use the Post Mass Additions program to perform the dataimport.

In 10.7, the FA_MASSADD_DISTRIBUTIONS table was introduced tosupport multi-distributed assets. Four database triggers maintain this table.The triggers are:• FA_MASS_ADDITIONS_INSERT_DIST - Inserts a row into

FA_MASSADD_DISTIBUTIONS when a row has been inserted withdistribution information into FA_MASS_ADDITIONS.

• FA_MASS_ADDITIONS_UPDATE_DIST - Updates

FA_MASSADD_DISTRIBUTIONS when distribution information hasbeen updated in FA_MASS_ADDITIONS.

• FA_MASS_ADDITIONS_DELETE_DIST - Deletes rows inFA_MASSADD_DISTRIBUTIONS when the correspondingFA_MASS_ADDITIONS row has been deleted.

• FA_MASS_ADDITIONS_INSERT_NAME - Inserts intoFA_MASSADD_DISTRIBUTIONS when you manually insertFA_MASS_ADDITIONS rows with distribution sets.

White paper External SourcesMass Oracle/Client Confidential - For internal use only

4

External Sources

It is possible to load data into Oracle Assets via External Systems such asLegacy subledgers. This can be done in two different ways.

1) SQL*Loader – Use the SQL*Loader utility to upload your data intothe FA_MASS_ADDITIONS table. For more information on this, see Oracle Applications Open Interfaces Manual (available on MetaLink).

2) Applications Desktop Integrator (ADI) – This is an Oracle Applicationsproduct that is Excel based and allows you to enter and validate yourdata in an Excel spreadsheet and upload it to Oracle Assets. It willload your data into the FA_MASS_ADDITIONS table.

Once your data resides in the FA_MASS_ADDITIONS table, you canmove onto the next step, Prepare Mass Additions.

White paper Prepare Mass Additions (FAXMADDS)Mass Oracle/Client Confidential - For internal use only

5

Prepare Mass Additions (FAXMADDS)

Once the data resides in FA_MASS_ADDITIONS, you must go into thePrepare Mass Additions form in Oracle Assets to enter additionalinformation to each line in preparation for it to become an asset. You cando the following in the Prepare Mass Additions form:

• Enter additional source, descriptive and depreciation information.

• Assign the mass addition to one or more distributions, or changeexisting distributions in the Assignments window.

• Adjust the cost of a mass addition

• Merge a mass addition into another mass addition.

• Split a multiple-unit mass addition into several single-unit massadditions.

• Add mass addition lines to existing assets such as a cost adjustment.

After adding and/or updating your information, you then assign a massaddition queue to specify whether it is ready for posting. Only massaddition lines in the POST or COST ADJUSTMENT queue can be posted.

For further explanation of the mass addition's queues, see the Oracle AssetsUser's Guide - Mass Additions Process (available on MetaLink).

White paper Post Mass Additions (FAMAPT)Mass Oracle/Client Confidential - For internal use only

6

Post Mass Additions (FAMAPT)

The posting process creates assets from mass addition lines in the POSTqueue using the data you entered. It also adds mass additions in the COSTADJUSTMENT queue to existing assets. You can run this program asoften as you want during a period.

Behind The Scenes

When you run Post Mass Additions, Oracle Assets creates rows in thefollowing tables:

FA_TRANSACTION_HEADERS – A '(CIP) ADDITION' row and a'TRANSFER IN' row

FA_ADDITIONS – Descriptive information about the asset

FA_ASSET_HISTORY – Descriptive information about the asset

FA_ASSET_INVOICES – Information about the mass addition

FA_INVOICE_TRANSACTIONS – A 'MASS ADDITION' row

FA_BOOKS – Financial Information (defaulted from category)

FA_DISTRIBUTION_HISTORY – Assignment information

FA_DEPRN_SUMMARY – A single 'Books' row

FA_DEPRN_DETAIL - A 'B' row for each distribution line

White paper Delete Mass Additions (FAXMADEL)Mass Oracle/Client Confidential - For internal use only

7

Delete Mass Additions (FAXMADEL)

Delete Mass Additions is part of the “Clean Up” process that is supplied byOracle Assets. When reviewing your mass additions lines, you can placelines that should not become assets in the DELETE queue. The DeleteMass Additions program will take the following mass additions and placethem in the interim table FA_DELETED_MASS_ADDITIONS and deletethem from the FA_MASS_ADDITIONS table.

• Mass additions in the SPLIT queue for which you have already postedthe child mass addition lines created by the split.

• Mass additions in the POSTED queue that have already become assets.

• Mass additions in the DELETE queue.

White paper Purge Mass Additions (FAXMAPUR)Mass Oracle/Client Confidential - For internal use only

8

Purge Mass Additions (FAXMAPUR)

The Purge Mass Additions from Oracle Assets program removes massadditions from the interim table FA_DELETED_MASS_ADDITIONS.The items in the interim table are the audit trail from the mass additionlines that you marked DELETE and removed using Delete Mass Additions.When you purge the interim table, you lose your audit trail. For security,the Purge Mass Additions from Oracle Assets program can only beaccessed through the Fixed Assets Administrator standard responsibility.

White paper Mass Additions ReportsMass Oracle/Client Confidential - For internal use only

9

Mass Additions Reports

See the Oracle Assets Reference Manual, available on MetaLink, for moredetails on these reports.

Report Name Report ExecutableMass Additions Create Report FAS822Mass Additions Delete Reports FAS829Mass Additions Invoice Merge Report FASMAIMRMass Additions Invoice Split Report FASMAISPMass Additions Posting Report FAS824Delete Mass Additions Preview Report FAS828Mass Additions Purge Report FAS826Mass Additions Status Report FAS823Unposted Mass Additions Report FAS833

White paper Information SourcesMass Oracle/Client Confidential - For internal use only

10

Information Sources

Information from this paper came from the following sources:

Oracle Assets Reference Manual, Release 10Oracle Assets Users Guide, Release 11FA For Support Manual