Error-APP-OFA-48392 in FA

This forum is to discuss different features/issues of Oracle Financials modules ( GL - General Ledger, AP - Accounts Payable, AR - Accounts Receivable, FA - Fixed Assets & CM - Cash Management ).
Post Reply
M123
Posts: 42
Joined: Fri Nov 07, 2008 12:02 pm
Location: Sri Lanka

Error-APP-OFA-48392 in FA

Post by M123 »

I am getting an error when trying to add a new asset.

Error-APP-OFA-48392- Unable to get the concurrent request status using procedure fnd_concurrent.get_request_status .

Can anyone figure out the probles.Pls reply.


MPH
oteixeira
Posts: 451
Joined: Wed Aug 27, 2008 12:34 pm
Location: Portugal

Post by oteixeira »

Hello.

Did you have a look on Metalink Note:275200.1 ?

Octavio
oracleapps1983
Posts: 256
Joined: Thu Aug 07, 2008 3:48 am
Location: USA

Post by oracleapps1983 »

Mr MH

Can you clearly let me know on what occasion i.e. what you are telling i am not clear

Whether adding asset is through Mass Additions or under detail/quick additions.
oteixeira
Posts: 451
Joined: Wed Aug 27, 2008 12:34 pm
Location: Portugal

Post by oteixeira »

Hello.

The Note may not apply to your problem.
It was just a hint.
Octavio
M123
Posts: 42
Joined: Fri Nov 07, 2008 12:02 pm
Location: Sri Lanka

Post by M123 »

Hi everyone thanks a lot for all of your replies,

I found an article in metalink relating to this issue.And today I sat with a technical person and got the issue sorted out.We did exactly the same thing in the article.

The article is given below,Hope this would help for you all,


Subject: APP-OFA-48392 Error When Adding a New Asset in the Asset Workbench
Doc ID: NOTE:275200.1 Type: PROBLEM
Last Revision Date: 04-DEC-2008 Status: PUBLISHED

The information in this article applies to:
Oracle Assets - Version: 11.5.9
This problem can occur on any platform.
FAXASSET - Asset Workbench
Symptoms
When adding a new asset in Asset Workbench, in the Assignments window, when
clicking Done, an error message appears:

APP-OFA-48392: Unable to get the concurrent request status using procedure.
Cause
Invalid depreciation run status showing as 'Submitted'.
Fix

Change the Status to 'Error', resubmit Run Depreciation and let it complete
normally, rollback depreciation, then enter new assets.

1) Refresh a TEST instance with the Production data when experiencing this issue.

2) Run this update:

update fa_book_controls
set deprn_status = 'E'
where book_type_code = '&book'
and deprn_status = 'S';
commit;

3) Resubmit Run Depreciation WITHOUT Close Period option.

4) Rollback Depreciation.

Always TEST results prior to implementing in a Production database.

"Octavia Thanx you are correct.Its the same article you are refering to."

MPH
Post Reply

Who is online

Users browsing this forum: No registered users and 0 guests