Monday, February 19, 2018

Oracle EBS Asset Model and Reporting

EBS FA is an old model and the application is widely deployed in most of EBS sites.

Almost all companies has assets and need to report their assets in their accounting reports.

While many people, including Oracle, has provide some reporting solutions for EBS FA, I think that doing it right in a most optimal way is often.  It affects the time required for monthly or year end period closing and a reporting solution that allows the deploying company to quickly see the change they made and continue working is essential for their business.

Historical Information

EBS FA stores asset historical information. 
The other EBS application that stores a lot of historical image of data is EBS HR.  EBS FA has a typical design that when any transaction or depreciation process affect the value of the asset, it keep the original value and create a new record to represent the new value.  It makes the old record deactivated by entering an DATE_INEFFECTIVE value.

The dates are different tables may be entered in a different time and thus a range join between the tables is the way for getting the historical images of data for any given date.

Multiple Books

Like other subledger products such as AR and AP, which has the OU and each OU posts to one Ledger, EBS FA partition the data by FA Books.

OU in other subledger is hard stripping of the data, sharing the data across OUs are under limited circumstances.

EBS FA, on the other hand, shares data across Corporate Book and Tax Book.  The asset distributions are entered against distribution source books and are shared across tax books that use the same distribution source books.

Sharing historical data across periods

While in many cases, the historical data are entered with an explicit DATE_INEFFECTIVE date, the depreciation process is not always run for every period and when reporting the depreciation data, the data from prior depreciation run has to be used for the specific AS WAS point in time.

The lack of the end date or end period is not a unique challenge.  In many applications, such as PeopleSoft Applications, they only have the EFFDT. 


Integration with AP

Integration with PO

Integration with Item Master

Integration with Asset Instance








No comments: