Overview of the Perform Periodic Mass Copy Process

Run the Perform Periodic Mass Copy process each period to keep your tax book up to date with your corporate book.

Oracle Assets copies new assets and transactions entered in the corporate book during one accounting period in the current fiscal year into the open period of the tax book. You can run the Perform Periodic Mass Copy process as often as necessary. If you run the process daily, tax books can be synchronized daily with the corporate book activity.

If you have a large volume of transactions to be copied to the tax book, you can set up Assets to submit multiple Perform Periodic Mass Copy processes, which will run in parallel. This reduces processing time.

Note: You can run the Perform Periodic Mass Copy process sequentially without skipping periods. When running the Perform Periodic Mass Copy process, only the last period run and the following period are available in the period list of values.

When running the Perform Periodic Mass Copy process, you must consider the impact of:

Fiscal years
Period date ranges

Fiscal Years

Associated tax books can have different fiscal years than their corporate books. For example, the corporate book can have a fiscal year from January through December, but the associated tax book can have a fiscal year from April through March.

Retirements and reinstatements are not allowed if a retirement with a transaction date in the current fiscal year in the corporate book falls into a prior year in the fiscal year of the tax book.

For example, consider the following retirement scenarios:

Book	Fiscal Year
Corporate	July to June
Tax	January to December

In these scenarios, the books are synchronized in March 2010.

Scenario 1: In the corporate book in March 2010, an asset retirement is backdated to December 2009 (fiscal 2010).

This transaction is possible because both December 2009 and March 2010 are in same fiscal year in the corporate book.
Scenario 2: In the tax book in March 2010, the retirement from scenario 1 is copied to the tax book by the Perform Periodic Mass Copy process.

This transaction fails because December 2009 and March 2010 are not in the same fiscal year in the tax book. Therefore, the retirement crosses a fiscal year boundary in the tax book, which is not currently allowed.

Note: Retire the asset as of January 2010 in the tax book. Because January is the first period of the open fiscal year in the tax book, January is the earliest period to which a retirement can be backdated in the tax book.

Consider the following reinstatement scenario:

Book	Fiscal Year
Corporate	July to June
Tax	January to December

In this scenario, the books are synchronized in December 2009.

Book	Date	Action
Corporate	December 2009	Retire asset.
Tax	December 2009	Copy retirement to the tax book by using the Perform Periodic Mass Copy process.
Corporate	January 2010	Reinstate the retirement.
Tax	January 2010	Copy reinstatement to tax book by using the Perform Periodic Mass Copy process.

The transaction fails because December 2009 and January 2010 are not in the same fiscal year in the tax book. Therefore, the reinstatement crosses a fiscal year boundary in the tax book, which is not allowed.

Note: A reinstatement is not possible in this case. The cost can be manually adjusted to effectively reinstate the cost, but the retirement transaction, including gain or loss and reserve, cannot be reversed.

Period Date Ranges

If the tax book has a different date range than the corporate book for individual periods, the gap between the periods can cause certain transactions to be ignored. Transactions that do not have a transaction date within or prior to the tax period into which they are being copied are rejected. For example, transactions dated in February cannot be mass copied into a tax book in which the open period ends in January. The transactions can be copied into a subsequent month in the tax book. These scenarios can be managed by the sequence and periods for which mass copy is run.

The following is an example of a future transaction in which the corporate period overlaps the tax period:

Books are synchronized in January 2010.
Corporate book period range: December 29, 2009 through February 1, 2010
Tax book period range: January 1, 2010 through January 31, 2010

Book	Date	Action
Corporate	January 2010	Add, adjust, or retire an asset with a transaction date of February 1, 2010. Any transaction subject to mass copy will be affected.
Tax	January 2010	Run the Perform Periodic Mass Copy process for January 2010.

The January period in the tax book ends on January 31, 2010, so transactions dated on February 1, 2010, are not copied. After closing the January 2010 period in the tax book, rerun the Perform Periodic Mass Copy process for the January 2010 period (copy January 2010 from the corporate book into February 2010 in the tax book). The Perform Periodic Mass Copy process picks up the previously rejected transactions dated February 1, 2010, because these transactions now fall into the current open tax period.

Note: The January 2010 rerun of the Perform Periodic Mass Copy process must be completed before running the process again for February 2010. The first time that you run the Perform Periodic Mass Copy process for February 2010, January 2010 will no longer be available in the parameters.

The following is an example of a future transaction in which the tax period overlaps the corporate period:

Books are synchronized in January 2010.
Corporate book period range:
- January: January 1, 2010, through January 31, 2010
- February: February 1, 2010, through February 28, 2010
Tax book period range:
- January: December 30, 2009, through February 1, 2010
- February: February 2, 2010, through March 1, 2010

Book	Date	Action
Corporate	January 2010	Perform transactions for the month of January.
Tax	January 2010	Run the Perform Periodic Mass Copy process for January 2010. The two previous transactions to which mass copy applies are successfully copied because the transaction dates are through January 31, 2010, which is included in the open tax period.
Corporate	January 2010	Close period. (Leave the period in the tax book open.) At this stage, you would normally close the tax book to keep the periods synchronized. However, the tax period extends through February 1, 2010. To copy the February 1, 2010, transactions into the corporate book, complete the following two actions.
Corporate	February 2010	Enter transactions dated on February 1, 2010.
Tax	January 2010	Because the Perform Periodic Mass Copy process is allowed for the open corporate period, run the Perform Periodic Mass Copy process and copy the February corporate book into the January tax book immediately after the transactions for February 1, 2010, are complete in the corporate book. Transactions with a transaction date of February 1, 2010, are copied to the January tax period.

The following is an example of a transaction sequence in which the corporate period overlaps the tax period:

Books are synchronized in January 2010.
Corporate book period range: December 29, 2009, through February 4, 2010
Tax book period range: January 1, 2010, through January 31, 2010
An existing asset was added in the prior year to both books.

Book	Date	Action
Corporate	January 2010	Adjust the cost of the asset with a January 31, 2010, transaction date.
Corporate	January 2010	Adjust the cost of the asset with a February 1, 2010, transaction date.
Corporate	January 2010	Retire the asset with a January 31, 2010, transaction date.
Tax	January 2010	Run the Perform Periodic Mass Copy process for January 2010.

The January period in the tax book ends on January 31, 2010, so transactions dated on February 1, 2010, will not copy. Therefore, the transaction on line 2 fails to copy, and the transactions on lines 1 and 3 copy successfully.

Because the cost adjustment on line 2 was not copied, the result is that the retirement on line 3 is applied to a different cost in the tax book than in the corporate book. This distribution occurs because multiple transactions are entered in the overlap period with transaction dates that do not all fall into the same tax period. You can avoid this result by changing the transaction sequence.

Note: If all of the transactions were entered with transaction dates backdated prior to the end date of the open tax period, then all transactions would copy, and there would be no issue with the transaction sequence.

The following is an example of transaction grouping:

Typically each transaction in the corporate book that is subject to mass copy is copied as a separate transaction into the tax book. In the case of addition transactions, the state of the asset in the corporate book as of the close of the period of addition is used to create a single addition transaction in the tax book.

The ability to run the Perform Periodic Mass Copy process before the period is closed means that the addition can be copied before adjustments in the period of addition. Therefore, depending on the timing and the number of times that the Perform Periodic Mass Copy process is run, the tax book may reflect a different number of transactions than the corporate book.

Consider these transaction grouping details:

Books are synchronized in January 2010
Corporate book period: January
Tax Book Period: January

Book	Date	Action
Corporate	January 2010	Add asset.
Tax	January 2010	Run the Perform Periodic Mass Copy process for January 2010.
Corporate	January 2010	Perform cost adjustment 1.
Corporate	January 2010	Perform cost adjustment 2.
Corporate	January 2010	Perform cost adjustment 3.
Tax	January 2010	Run the Perform Periodic Mass Copy process for January 2010.

If the Perform Periodic Mass Copy process is run after each cost adjustment, then the tax book reflects all three of the adjustments. If the Perform Periodic Mass Copy process is run after several adjustments (as in the previous example), then the adjustments are grouped in the tax book into a single adjustment transaction.