My Oracle Support Banner

Reclassification of Member Asset between Two Groups Causes Process Group Adjustment Failure with ORA-01403: no data found (Doc ID 2971717.1)

Last updated on AUGUST 31, 2023

Applies to:

Oracle Assets - Version 12.2.11 and later
Information in this document applies to any platform.

Symptoms

When attempting to reclass a member asset from its old Group Asset to a new Group Asset, the Process Group Adjustment (FAPGADJ) process fails with this error:

ORA-01403: no data found
Error: function FA_AMORT_PVT.bsRecalculate returned failure
ORA-01403: no data found
Error: function newFA_AMORT_PVT.faxama returned failure
Error: function fa_process_groups_pkg.do_group_reclass returned failure
Error: function fa_process_groups_pkg.do_all_books returned failure
Module FAPGADJ ended with error

If the user then attempts to manually reclass this member or any other member in the source Group Asset, the following error presents on screen:

"A transaction is pending for this asset in another session. Please complete it and try again. Failed to obtain lock on FA_BOOKS row for asset_id 71917 and book ABC BOOK."

NOTE:  In the context of Group Asset functionality, to move a member from Group A to Group B is a reclassification.  It is not a transfer.


The issue can be reproduced at will with the following steps:

Use Fixed Assets Manager responsibility or similar, that has access to the Asset Workbench to perform transactions.  Dates in the below are examples only, but their relationships are important to reproducing this error.  This assumes the open period in Assets is January 2022 at the start of the steps.

1.  Move to the Asset Workbench and choose to add a new asset.  Use the Additions button to create a Group Asset (it will be necessary to update the Asset Type to Group)

 

Use a valid category for your book and a suitable description.

Choose Continue and then set Date Placed in Service (DPIS) to 01-Jan-2000.

2. Next, on the Advanced Rules tab, a typical setup which will trigger this issue is to not use Tracking.

 

Save.

3. Starting again with the Asset Workbench, add another asset.  This one should have Asset Type = Capitalized and the Group Asset field should be populated with the asset number created in step 1.  Date Placed in Service should be 01-Jan-2022, with the Amortization Start Date set to the same.

Save.  This will spawn Process Group Adjustment concurrent request, and it will complete successfully.


4. Move to the Depreciation menu and submit Depreciation with Period Close checked.  Close periods until the open period becomes February 2023.

 

5. Repeat step 3 to add a second member asset with Date Placed in Service as 01-Jan-2022 and Amortization Start Date set to the same.

Save. This will spawn Process Group Adjustment concurrent request, and it will complete successfully.

6. Using the Asset Workbench again, query up the member asset created in step 3.  Using the Books button, modify its Date Placed in Service to 01-Jan-2023 with Amortization Start Date as the same.

Save. This will spawn Process Group Adjustment concurrent request, and it will complete successfully.

7. Using the Depreciation menu (this is the same menu as step 4), run Depreciation with Period Close checked.  Repeat until the open period is May-2023.


8. Query up the second member asset (created in step 5).  Using the Books button, update the Group Asset to be a different group.  Use Amortization Start Date of 01-Jan-2023. 

Save. This will spawn Process Group Adjustment concurrent request, and it will fail.

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.